More menu improvements in Google Docs and Slides

/in

Based on usage data and your feedback, we’re making some changes to the menus and toolbars in Google Docs and Slides on the web. These are similar to some previous changes we made and will make it easier to find certain items. Among other things, these changes include:

To add a line or page break in Docs:
Before: Insert > Page break or Column break
After: Insert > Break > Page break or Column break
See Help Center for more details: Add, edit, or remove a link, bookmark, or page break.

To add Alt text to a shape in Docs or Slides:
Before: Select shape > Format > Alt text. This option will be removed from the menu.
After: Right click on shape > Alt text. This is the new way to add alt text to a shape.
See Help Center for more details: Make your document or presentation accessible.

To change a shape in Slides:

Before: Select shape > Format > Change shape. This option will be removed from the menu.
After: Right click on shape > Change shape. This is the new way to change a shape.

The HTML view in Slides is being removed from the menu.
Before: View > HTML
After: Ctrl+Alt+Shift+P
See Help Center for more details: Make your document or presentation accessible.

These changes will only affect the visual menu. All options will still be available via keyboard shortcuts and the search box in the Help menu.

Launch Details
Release track:
Launching to Rapid Release, with Scheduled Release coming in two weeks

Editions:
Available to all G Suite editions

Rollout pace:
Gradual rollout (up to 15 days for feature visibility)

Impact:
All end users

Action:
Change management suggested/FYI

 

Reference by Google.com

How to create own Bundle file from CRT Files

/in

How do I make my own bundle file from CRT files?

Answer: You may do this using your favourite text editor or by using the command line.

Example:

# Root CA Certificate – AddTrustExternalCARoot.crt
# Intermediate CA Certificate 1 – ComodoRSAAddTrustCA.crt OR ComodoECCAddTrustCA.crt
# Intermediate CA Certificate 2 – ComodoRSADomain/Organization/ExtendedvalidationSecureServerCA.crt OR ComodoRSAECCDomain/Organization/ExtendedvalidationSecureServerCA.crt
# Intermediate CA Certificate 3 – ComodoSHA256SecureServerCA.crt
# Your SSL Certificate – yourDomain.crt

Note: You will not need your SSL certificate for this exercise.

 

There are two ways to create ca bundle file.

1.Using GUI Text Editor

1. Open All files in a text editor. (Remember, not your domain certificate.)
2. Create a new blank text file.
3. Copy contents of all files in reverse order and paste them into the new file.
Example: Intermediate 3, Intermediate 2, Intermediate 1, Root Certificate.
4. Save the newly created file as ‘yourDomain.ca-bundle‘ or ‘yourDomain.ca-bundle.crt’.

 

2.Using Command Line

Linux or UNIX-like Operating Systems:
— cat ComodoRSAAddTrustCA.crt ComodoRSADomain/Organization/ExtendedvalidationSecureServerCA.crt AddTrustExternalCARoot.crt > yourDomain.ca-bundle

Or

— cat ComodoSHA256SecureServerCA.crt AddTrustExternalCARoot.crt > yourDomain.ca-bundle

Windows or DOS:
— copy ComodoRSAAddTrustCA.crt + ComodoRSADomain/Organization/ExtendedvalidationSecureServerCA.crt + AddTrustExternalCARoot.crt yourDomain.ca-bundle

Or

— copy ComodoSHA256SecureServerCA.crt + AddTrustExternalCARoot.crt yourDomain.ca-bundle

Note: ‘yourDomain.ca-bundle‘ is only a placeholder file name. You may call it anything you want.

 

 

how to migrate emails from cPanel to Gsuite accounts

/in

The following is the step to do email migration from cPanel to Gsuite

 

  1. In Linux cPanel check for mx entry . There keep email routing setting as Local mail exchange server
  2. Check whether all username and password given to you is correct or not. If not do correction of the password.
  3. Open Customer’s Google Admin console (at admin.google.com) with super admins rights
    Go to Data migration.
    Select the Email option and click Continue.
    On the Email Migration screen:
    From the Migration source list, select I don’t know/Other IMAP server.
    From the Connection protocol list, select IMAP, then choose an option:
    Enter the IMAP server name (for example, imap.yourdomain.com).
    Enter the IMAP server name and port number in this format: Name: Port.
    Enter the email address and password for your role account(use email id from where you want to migrate ).
    Tip: For help with this, see Connection information for common webmail providers.

Click Connect.
(Optional) If the connection fails, verify that the role account and connection protocol information is correct. Then, click Connect again.
In the Migration start date and Migration options sections, accept the default options or choose to exclude data that doesn’t need to be migrated.
Click Select Users.
Next: Go to Migrate email for a single user or Migrate email for multiple users.

All migration will be completed without fail.

 

 

How to install SSL in IIS 7.x

/in

The Following is the step to install SSL certificate in ISS  7.0

 

1. Open Internet Information Services Manager (IISM) to the appropriate Server
Start -> Administrative Tools -> IISM -> Server Name

2. Open the Server Certificates icon.

3. Open ‘Complete Certificate Request’ Wizard

From the ‘Actions’ Menu on the right select ‘Complete Certificate Request’

4. Proceed to Complete Certificate Request’ Wizard

Fill out all appropriate information. You may need to browse to the location of the certificate or you may enter it in the provided box. The friendly name is not part of the certificate itself, but is used by the server administrator to easily distinguish the certificate.

Note: There is a known issue in IIS 7 giving the following error: “Cannot find the certificate request associated with this certificate file. A certificate request must be completed on the computer where it was created.” You may also receive a message stating “ASN1 bad tag value met”. If this is the same server that you generated the CSR on then, in most cases, the certificate is actually installed. Simply cancel the dialog and press “F5” to refresh the list of server certificates. If the new certificate is now in the list, you can continue with the next step. If it is not in the list, you will need to reissue your certificate using a new CSR (see our CSR creation instructions for IIS 7). After creating a new CSR, login to your Comodo account and click the ‘replace’ button for your certificate.

Assign to Website

1. Navigate back to the root of the appropriate website. The center of the window should say “Default Website Home” or whatever the name of the website is.

2. Select ‘Bindings’ from the ‘Edit Site’ sub menu.

3. Add Port 443

In the ‘Site Bindings’ window, click ‘Add’. This will open the ‘Add Site Binding’ window.

Under ‘Type’ choose https. The IP address should be the IP address of the site or All Unassigned, and the port over which traffic will be secured by SSL is usually 443. The ‘SSL Certificate’ field should specify the certificate that was installed using the above steps.

Click ‘OK’ to save changes.

Note: There may already be an ‘https’ entry in this area. If so, click ‘https’ to highlight it. Then click ‘Edit’ and in the ‘SSL certificate’ area select the friendly name that was generated earlier. Click ‘OK’ to save changes.

 

Click ‘OK’ on the ‘Web Site Bindings’ Window to complete the install.

Important: You must now restart IIS / the website to complete the install of the certificate.

Configure Junk E-Mail Filter Settings With Junk E-Mail Options

/in

Set junk e-mail filter level

The junk E-mail Filter in Outlook is turned on by default, and its protection level is set to No Automatic Filtering. If you feel that Outlook moves too many incoming messages, or too few to the Junk E-mail folder, you can take the follow steps to adjust the filter sensitivity of Outlook:

1. In Outlook 2010/2013, click Home > Junk > Junk E-mail Options.

doc-configure-junk-email-1

Note: In Outlook 2007: click Actions > Junk E-mail > Junk E-mail Options.

2. The Junk E-mail Options dialog will then show up. There are four different levels of junk mail filter settings, please choose the level you want and click OK.

doc-configure-junk-email-6

Notes:

  • • No Automatic Filtering: This option can block messages from addresses which have been added to the Blocked Senders list.
  • • Low: This level will only filter the most obvious junk.
  • • High: Filters all messages suspected as junk.
  • • Safe Lists Only: Any message that is sent from someone not on your Safe Senders list or to a mailing list on your Safe Recipients list is automatically considered as junk email.

Create Junk- E-mail filter lists

There are five different junk e-mail filter lists in the Junk E-mail Options that can determine whether the emails will be moved to the junk folder or not.

  • • Safe Senders List: Email addresses and domain names of the senders in this list are never treated as junk.
  • • Safe Recipients List: You can add addresses and domain names from the mailing lists and distribution lists to this list so that they will never be marked as spam.
  • • Blocked Senders List: If you add an email address or domain to this list, messages will automatically sent to the Junk Email folder.
  • • Blocked Top-Level Domains List: You can add country/region codes to this list to block messages from another country or region.
  • • Blocked Encodings List: To block messages that contain special encoding or character set, you can add encodings to this list.

To set these junk e-mail filter lists, you can do as follows:

1. Click Home > Junk > Junk E-mail Options in Outlook 2010/2013, and click Actions > Junk E-mail > Junk E-mail Options in Outlook 2007.

2. In the pop up Junk E-mail Options dialog box, click Safe Senders tab, and click Add button to add the address or domain that you don’t want to treat as spams. See screenshot:

xdoc-configure-junk-email-2

 

 

 

Making Google prompt the primary choice for 2-Step Verification

/in

In July, we began inviting users to try Google prompt as their 2-Step Verification (2SV) method, instead of SMS text messages. Google prompt is an easier and more secure method of authenticating an account, and it respects mobile policies enforced on employee devices.

Sign In- Google Prompt

With that in mind, we’re now making Google prompt the first choice when users turn on 2SV (previously, SMS was the primary choice). Once 2SV is enabled, users will still have the option to set up SMS, the Google Authenticator app, backup codes, or Security Keys as their alternative second step.

My Account

This will only impact users who have not yet set up 2SV. Current 2SV users’ settings will be unaffected. In addition, if a user attempts to set up 2SV but doesn’t have a compatible mobile device, he or she will be prompted to use SMS as their authentication method instead.

Users can set up 2SV from their My Account page.

A few things to note:

  • A data connection is required to use Google prompt.
  • Users with iOS devices will need to install the Google app in order to use Google prompt.
  • G Suite Enterprise domains can choose to enforce Security Keys to meet more advanced security requirements.
Launch Details
Release track:
Launching to both Rapid Release and Scheduled Release

Editions:
Available to all G Suite editions

Rollout pace:
Gradual rollout (up to 15 days for feature visibility)

Impact:
All end users

Action:
Change management suggested/FYI

Time for a refresh: meet the new Google Calendar for web

/in

Check your schedule. Starting today, a fresh look and new features are coming to Google Calendar on the web to help you manage your time more efficiently and get more done.

We’re taking a lot of what you know and love from Calendar’s mobile application, like the modern color palette and sleek design, and bringing it to the web with a responsive layout that auto-adjusts to your screen size. We’ve also added more features for enterprises to help teams schedule and prepare for meetings.

EventDetails-05 (1)

Over the years, you’ve shared valuable feedback on how we can enhance Calendar to better fit your needs and we’re excited to bring new improvements. Now, it’s even easier to manage your schedule at your desk. In the new Calendar for web, you can:

  • See conference room details when booking a room. G Suite admins can now enter detailed information about their organization’s meeting rooms—so employees know where a conference room is located, how large it is, and whether it has audio/video equipment or is wheelchair accessible. Employees can simply hover over the room name in Calendar when they want to book a space, and a hovercard will pop up with details about the conference location and resources.
    CalendarSRI-blog (2)
  • Add rich formatting and hyperlinks to your Calendar invites. Link to relevant spreadsheets, documents or presentations in your Calendar invite and open them directly from the new “Event Detail” view. This can help you create more detailed agendas and ensure all materials are in one place before your meeting starts.
    MeetingDetails
  • Manage multiple calendars side by side in “Day” view. Now you can view and manage calendars in separate columns. This makes it easier for employees who manage multiple calendars, like administrative assistants, to schedule meetings on behalf of their teams. Click “Day” view and select the calendars you want to compare.
    DayView
  • There are a number of other changes in Calendar, too. Now you can see contact information of meeting participants when you hover over their names in a Calendar invite. There’s also a new way to view and restore deleted items in one place in case you accidentally delete a meeting invite. Additionally, “Day,” “Week,” and “Month” views are now more accessible, featuring better compatibility with screen readers. For more detail on changes, check out this post.Additional information for G Suite admins

    To help you and your users transition to the new Calendar web UI, we’re offering two rollout options to choose from (see the Help Centerfor more information):

    • Automatic—Automatic is the default option. Starting Nov. 14, 2017, for Rapid Release domains and Nov. 28, 2017, for Scheduled Release domains, we will gradually transition your users to the new UI. The transition will take about 8 weeks (including opt-in and opt-out stages). No action is required on your part for the Automatic option.
    • Manual—Alternatively, you can choose to manually control when to move your users to the new UI in the Google Admin console. For example, though we’ve worked with the developers of the most popular Calendar Chrome extensions to prepare for the new UI, you might have users who depend on an extension that hasn’t been updated yet. Or you might like to check out the new UI in your test domain or organizational unit (OU).

    To choose the Manual option, go to Apps > G Suite > Calendar > New Calendar. Here, you can set by organizational unit when you’d like your users to access the new version of the Calendar UI. If you choose the Manual rollout option, please plan to transition all your users to the new UI before Feb. 28, 2018. Any users who are still accessing the old Calendar UI on Feb. 28, 2018, will be transitioned to the new UI, with no ability to opt out.

    We recommend sharing this guide, as well as the resources below, with your users to help them understand the new layout changes.

    For more information on how to add structured data to your rooms and resources, check out the Help Center. Note that this feature will work with both the classic Calendar UI and the new Calendar UI.

     
    Launch Details
    New Calendar web UI, rich formatting for invites, side-by-side “Day” view
    • Automatic rollout option (recommended) to start on Nov. 14, 2017 for Rapid Release and Nov. 28, 2017 for Scheduled Release
    • Manual rollout option available starting today for admins on both Rapid Release and Scheduled Release

    Structured room and resource data

    • Rolling out gradually over the coming weeks for admins on both Rapid Release and Scheduled Release to start uploading

    Editions:
    Available to all G Suite editions

    Rollout pace:
    Extended rollout (potentially longer than 15 days for feature visibility)

    Impact:
    Admins and end users

    Action:
    Admin action suggested/FYI

Reference by Google.com

KRACK WiFi WPA2 security vulnerability threatens all networks

/in

Security researchers have found a devastating flaw in WPA2 WiFi encryption protocol that makes it possible for hackers to intercept your sensitive information. This vulnerability named KRACK (Key Reinstallation Attack) affects Wi-Fi protocol and not a specific product or impentation. An attacker within range of a victim can exploit these weaknesses.

KRACK targets the third step in a four-way authentication “handshake” performed when a WI-FI client attempts to connect to a protected network. This can lead to stealing of information by the attackers including your credit card and confidential data.

To protect against this flaw, major OSes and routers are working round the clock to provide a patch. Apply the patch as soon as possible. Meanwhile, do not share any personal or confidential information on a non secure website and only use secure or HTTPS sites.

Also avoid using free hotspots or use a secure VPN or connection like GajShield Enterprise Cloud, if you must use a Wifi network.

Our research team is working in our labs to gain more information about the latest KRACK attacks and will keep you updated on future course of action. Until then keep a close tab on any latest updates or patches released for your affected products and apply them as soon as possible

 

Reference by gajshield.com

Google Drive reporting will show activity-based metrics in the Admin console

/in

As a G Suite admin, it’s important that you have a clear, reliable understanding of the actions taking place within your domain. Today, we are making changes to reporting in the Admin console to better reflect the Google Drive activity happening in your domain. First, we are shifting the definition of the metrics shown to reflect the change in file activity, such as “Google Documents added,” instead of absolute counts, such as total “Google Documents owned.” This change affects any dashboard or metric in the Admin console that reports on Drive files.

 

Aggregate Reports

We are also adding sharing visibility metrics to Admin console reporting. File sharing reports will now highlight which files have been shared outside of your domain vs. internally.

File Sharing Activity

These metrics were introduced earlier this year, but were only available through the Admin SDK Reports API; they’re now available from within the Admin console. This new presentation of metrics provides the most reliable and recent information available, directly in the Admin console.

Find more information on the changes to individual reports in the Help Center.

Launch Details
Release track:
Launching to both Rapid Release and Scheduled Release

Editions:
Available to all G Suite editions

Rollout pace:
Full rollout (1–3 days for feature visibility)

 

Reference by Google.com

 

Turning down the in-app passcode feature in Google Drive, Docs, Sheets, and Slides on iOS

/in

In the past, we’ve heard feedback that customers want more security for the files on their iOS devices, which led us to enable an in-app passcode feature specifically for the Google Drive, Docs, Sheets, and Slides iOS apps. Over time, however, we’ve come to learn that it’s not just the content within Google Drive that’s valuable to you. Your contacts, calendars, and emails—it’s important that all of this is secure as well.

As a result, we began putting particular emphasis on supporting mobile device management (MDM) on iOS. For example, recent launches give G Suite admins greater visibility and control over enterprise-deployed iOS devices. In fact, with MDM, admins can enforce a passcode on all iOS devices that access corporate data, and they can wipe account data on a device if it’s compromised.

Owing to this increased investment in security on iOS devices, we’re ending support for the in-app passcode feature in Google Drive, Docs, Sheets and Slides on iOS devices signed in with G Suite accounts. Support will end on December 4th, 2017, and we’ll remove the feature entirely no earlier than January 8th, 2018.

We highly recommend that administrators use MDM to deploy passcode requirements at the system level on all of their iOS devices by following these instructions. This will provide better security than the in-app passcode feature in two key ways:

  • These passcode policies protect all of the content on your managed devices, including photos, contacts, and other content besides Google Drive, Docs, Sheets, and Slides content.
  • These passcode policies give you more control over passcode type, strength, expiration, and failure cases. See this Help Center article for more details.

Beginning on December 4th, 2017, any user signed in with a G Suite account who has this feature will see a message asking them to either acknowledge and turn off the functionality or to ignore the message temporarily. Beginning on January 8th, 2018, all new versions of the Google Drive, Docs, Sheets, and Slides iOS apps will no longer contain in-app passcode functionality.

 

Reference by Google.com