Office 2019 Commercial Preview Program

Office 2019 Commercial Preview program


Summary


Thank you for your interest in the Microsoft Office 2019 Commercial Preview program. This preview program is intended only for organizations that plan to deploy the perpetual (volume licensed) version of Office 2019 when it’s released later this year. For more information, see the Tech Community blog post.

Prerequisites


To join the Office 2019 Commercial Preview program, you or your company must be registered with Microsoft Collaborate. If you’re not able to sign in to the Microsoft Collaborate portal, follow the instructions at Microsoft Collaborate: Documentation and guidance.

If you need support with Microsoft Collaborate, see How to get support and troubleshoot common Issues.

Join the Office 2019 Commercial Preview Program


The Preview program is available through Microsoft Collaborate, which is the only location for joining, accessing deployment packages and documentation, and providing feedback.

To join the program, follow these steps:

  1. Sign in to https://aka.ms/collaborate.
  2. On the Overview page in your dashboard, select Engagements to view engagements that are available to join.
    Select Engagements
  3. Find the Office 2019 Commercial Preview engagement, select Join, accept the Terms of Use, and then select Join again.
    Join
  4. If you no longer want to participate in the Preview program, select Leave.
    Click Leave

How to download packages


  1. From the dashboard, select Packages to go to the Packages page, where you will see all packages that are associated with the engagement.
  2. Select a package to view the details and the list of files that are included in the package.
    Select package
  3. Select the download icon to download the file.
    Download

Submit feedback


To submit feedback during the program, select Feedback in the dashboard. You can view all feedback that you submitted to the Office engineering team on the Feedback page.

The value of the State column indicates the state of your feedback:

  • New – New submission.
  • Resolved – The Office team has taken appropriate action and resolved the issue.
  • Closed – The issue is closed. No more action will be taken.

To submit new feedback, follow these steps:

  1. On the All Feedback page, select Submit New Feedback.
    Submit feedback
  2. If you participate in multiple engagements, select the engagement for which you want to provide feedback.
    Select engagement
  3. On the Office 2019 Commercial Preview feedback page, complete the required fields in the feedback template. Provide as much detail as possible, including thorough reproduction steps, and then select Save.
    Save

Updates to your feedback will appear in the feedback item until the issue is resolved, such as the status is changed to “Closed.”

Microsoft Azure Cloud Administrator

Looking to master the core principles of operating a Microsoft Azure-based cloud infrastructure? This learning path is for any technology professional who wants to be involved in the operation and administration of Azure-based solutions and infrastructure. You will learn the fundamentals of implementing, monitoring, and maintaining Microsoft Azure solutions, including major services related to Compute, Storage, Network, and Security. By the end of this learning path, you will be able to implement, monitor, and manage the most commonly used Microsoft Azure services and components, as configured for the most common use cases.

To go deeper follow the deep dive series below.

Azure Cloud Administrator

Primary Skills

Application Management Series

1 hr 6 min

3 hr

2 hr

1 hr

1 hr

3 hr

2 hr

1 hr

1 hr

1 hr

1 hr

Cloud Management Series

15 min

13 min

11 min

1 hr 17 min

1 hr 8 min

4 hr

12 min

6 min

1 hr 18 min

13 min

3 min

52 min

14 min

Device Management Series

1 hr

1 hr 20 min

1 hr 6 min

1 hr 6 min

1 hr 17 min

Identity Management Series

1 hr 5 min

30 min

1 hr 16 min

1 hr 16 min

3 hr

Secondary Skill

Architecture Series

8 hr

7 hr

55 min

Infrastructure – Hybrid/Private Cloud Series

1 hr 20 min

1 hr 10 min

2 hr

2 hr

34 min

5 hr

1 hr 15 min

1 hr 18 min

1 hr 10 min

Infrastructure – Open Source Series

7 min

17 min

11 min

3 hr

1 hr

Infrastructure – Public Cloud Series

3 hr

7 hr

 

1 hr

2 hr

Security & Privacy Series

1 hr 15 min

1 hr 12 min

1 hr

5 hr

3 hr

1 hr

20 min

1 hr

1 hr

2 hr

1 hr

4 hr

DevOps Series

25 min

29 min

59 min

36 min

38 min

30 min

3 hr

4 hr

30 min

4 hr

48 min

7 hr

1 hr 15 min

If you have been following these series and completed it then its time for Microsoft Certification Path. Join our MVA courses on https://mva.microsoft.com and start your cloud career.

Use Microsoft Authenticator with Office 365

If your organization is using 2-step verification for Office 365, the easiest verification method to use is Microsoft Authenticator. It’s just one click instead of typing in a 6-digit code. And if you travel, you won’t incur roaming fees when you use it.

Download and install Microsoft Authenticator app

https://i2.wp.com/is5.mzstatic.com/image/thumb/Purple128/v4/c1/2f/06/c12f06f4-b2b5-6ed7-3acd-3bf8759a92d5/source/175x175bb.jpg https://i0.wp.com/www.androidpolice.com/wp-content/uploads/2016/08/nexus2cee_MS-auth-hero.pnghttps://www.windowscentral.com/sites/wpcentral.com/files/styles/xlarge/public/field/image/2016/06/microsoft-authenticator-1.png?itok=4dPmJ7iL https://www.thurrott.com/wp-content/uploads/2016/07/auth-apps-1024x576.jpg

Set up the Microsoft Authenticator app

Step 1: Choose the mobile app

Open a browser on your computer and go to portal.office.com. Sign in to your Office 365 for business account.

Use these steps if you see this screen:

Click Set it up now.

  1. Click Set it up now.
  2. Choose Mobile app from the dropdown.
  3. Make sure “Receive notifications for verifications” is selected. Click Set up.

Use these steps if you see this screen:

Choose Settings

  1. Choose Settings Office 365 Settings button > Office 365.
  2. Choose Security & Privacy > Additional security verification > Update my phone numbers used for account security.
  3. In the drop down box under What’s your preferred option, choose Notify me through app.
  4. Check the box for Microsoft Authenticator app, click Configure.

Step 2: Wait for configuration pop-up box.

You should see a window on your computer that looks like this.

Follow the steps on your screen.

Step 3: Add account to Microsoft Authenticator

  1. Open the Microsoft Authenticator app on your phone.

  2. Tap the + > Work or school account.
  3. Use your phone to scan the QR square that is on your computer screen.

    Note: If you can’t use your phone camera, you’ll have to manually enter the 9 digit code and the URL.

  4. Your account will be added automatically to the app and will display a six-digit code.
Tap the + sign int the Azure Authenticator app.

Step 4: Confirm activation status on your computer

  1. Switch back to your computer and click Done.
  2. Now wait for the Checking activation status text to finish configuring your phone.
  3. When it’s complete, you’ll be able to click the Contact me button on the right.

    Note: If configuration fails, just delete retry the previous steps again.

Click Contact Me

Step 5: Approve sign in on your phone

  1. Switch back to your phone and you’ll see a notification for a new sign in.

  2. Go to the Microsoft Authenticator app.
  3. Tap Approve to allow it.
Tap Approve to allow sign in.

Step 6: Finish set up

  1. Back on the computer, follow any prompts that you might see such as adding a mobile number.

  2. You’re good to go!

From now on, whenever you have a new sign in or add your Office 365 work or school account to an app, you’ll open the Authenticator app on your phone and tap Approve.

Checkmark

Configuring Multi-Factor Authentication on Client/ User side

After you have enabled MFA on your tenant, your users can follow these instructions to set up their second sign-in method for Office 365:

Step 1: Set up 2-step verification for Office 365

Once your admin enables your organization with 2-step verification (also called multi-factor authentication), you have to set up your account to use it.

By setting up 2-step verification, you add an extra layer of security to your Office 365 account. You sign in with your password (step 1) and a code sent to your phone (step 2).

  1. Sign in to Office 365 with your work or school account with your password like you normally do. After you choose Sign in, you’ll see this page:

    First Sign in screen

  2. Choose Set it up now.
  3. Select your authentication method and then follow the prompts on the page. Or, watch the video to learn more.

    Choose your authentication method and then follow the prompts on the screen.

  4. Once you complete the instructions to specify how you want to receive your verification code, the next time you sign in to Office 365, you’ll be prompted to enter the code that is sent to you by text message, phone call, etc.

    To have a new code sent to you, press F5.

    When you sign in with 2-step verification, you'll be prompted for a code.

We strongly recommend setting up more than one verification method. For example, if you travel a lot, consider setting up Microsoft Authenticator for your verification method. It’s the easiest verification method to use, and a way to avoid text or call charges.

Step 2: Create an app password for Office 365

An app password is a code that gives an app or device permission to access your Office 365 account.

If your admin has turned on set up 2-step verification for your organization, and you’re using apps that connect to your Office 365 account, you’ll need to generate an app password so the app can connect to Office 365. For example, if you’re using Outlook 2016 or earlier with Office 365, you’ll need to create an app password.

  1. Check whether your Office 365 admin has turned on 2-step verification for your account. If they haven’t, when you try to do these steps you won’t see the options in Office 365.
  2. If you haven’t already done so, set up your account to use 2-step verification.
  3. Sign in to Office 365 using your password and verification code.
  4. Choose Settings Office 365 Settings button > Office 365.
  5. Choose Security & Privacy > Additional security verification.

    Choose Additional security verification.

  6. Choose Update my phone numbers used for account security. This will display the following page:

    Choose app passwords

  7. At the top of the page, choose App Passwords.
  8. Choose create to get an app password.
  9. If prompted, type a name for your app password, and click Next.
  10. Choose copy password to clipboard. You won’t need to memorize this password.

    Choose copy to your clipboard.

    Tip: If you create another app password, you’ll be prompted to name it. For example, you might name it “Outlook.”

  11. Go to the app that you want to connect to your Office 365 account. When prompted to enter a password, paste the app password in the box.

To use the app password in Outlook

You’ll need to do these steps once.

  1. Open Outlook, such as Outlook 2010, 2013, or 2016.
  2. Wherever you’re prompted for your password, paste the app password in the box. For example, if you’ve already added your account to Outlook, when prompted paste the app password here:

    Paste your app password in the Password box.

  3. Or, if you’re adding your Office 365 account to Outlook, enter your app password here:

    Enter your app password in both Password boxes.

  4. Restart Outlook.

Step 3: Change how you get 2 step verification

Depending on how your Office 365 admin set up 2-step verification for your organization, you might be able to change how you get your codes.

Tip: Before you can do these steps, your admin needs to set up multi-factor authentication for your account.

  1. Sign in to Office 365 using your password and verification code.
  2. Choose Settings Office 365 Settings button > Office 365.
  3. Choose Security & Privacy > Additional security verification.
  4. Choose Update my phone numbers used for account security. This will display the following page:

    additional security verification page

  5. Choose how you want to get your verification code. Although all options are listed, your admin may not make them all available; you’ll get a message if you choose one your admin didn’t enable.
  6. Follow the prompts on the page.

Configure Multi-Factor Authentication (MFA) for Office 365 users

Set up multi-factor authentication in the Office 365 admin center

  1. Go to the Office 365 admin center.
  2. Navigate to Users > Active users.

    Active users in Office 365 admin center

  3. In the Office 365 admin center, click More > Setup Azure multi-factor auth.

    Set up multifactor authentication

  4. Find the user or users who you want to enable for MFA. In order to see all the users, you might need to change the Multi-Factor Auth status view at the top.

    The views have the following values based on the MFA state of the users:

    • Any    Displays all users. This is the default state
    • Enabled    The user has been enrolled in multi-factor authentication, but has not completed the registration process. They will be prompted to complete the process the next time they sign in.
    • Enforced    The user may or may not have completed registration. If they have completed the registration process then they are using multi-factor authentication. Otherwise, the user will be prompted to complete the process at next sign-in.
  5. Check the check box next to the users you want to enable.

    Users selected for MFA.

  6. On the right user info pane, under quick steps you’ll see Enable and Manage user settings. Choose Enable.
  7. In the dialog box that opens, click enable multi-factor auth.

Allow MFA users to create App Passwords for Office client applications

Important: App passwords are not supported for Office 365 operated by 21Vianet.

Multi-factor authentication is enabled per user. This means that if a user is enabled for multi-factor authentication and they are attempting to use non-browser clients, such as Outlook 2013 with Office 365, they will be unable to do so. An app password allows this to occur. An app password, is a password that is created within the Azure portal that allows the user to bypass the multi-factor authentication and continue to use their application.

All the Office 2016 client applications support multi-factor authentication through the use of the Active Directory Authentication Library (ADAL). This means that app passwords are not required for Office 2016 clients. However, if you find that this is not the case, make sure your Office 365 subscription is enabled for ADAL. Connect to Exchange Online PowerShell and run the Get-OrganizationConfig | Format-Table name, *OAuth* command.

If you need to enable it, run Set-OrganizationConfig -OAuth2ClientProfileEnabled:$true .

  1. Go to the Office 365 admin center.
  2. Navigate to Users > Active users. Your screen should look like one of the following:

    Active users in Office 365 admin center

  3. In the Office 365 admin center, click More > Setup Azure multi-factor auth.

    Set up multifactor authentication

  4. In the multi-factor authentication page, choose service settings.

    MFA service settings.

  5. Under app passwords, choose Allow users to create app passwords to sign into non-browser applications.

    This allows users to use client Office applications, but they will have to enter a password of their choosing first.

  6. Click Save, and then Close.
Manage MFA user settings
  1. In the multi-factor authentication page, check the box next to the user or users you want to manage.
  2. In the user info pane on the right, you’ll see two options: Enable and Manage user settings. Choose Manage User settings.
  3. In the Manage user settings dialog, check one or more of the options: Require selected users to provide contact methods again, Delete all existing app passwords generated by the selected users, or Restore Multi-Factor Authentication on all remembered devices.
  4. Click Save.
Bulk-update users in MFA

You can bulk update the status for existing users using a CSV file. The CSV file will be used only for enabling or disabling multi-factor authentication based on the user names present in the file. It is not used to create new users.

  1. In the multi-factor authentication page, click bulk update.
  2. Browse for the file that contains the updates. The column headings in your file must match the column headings in the following example:

    bulk update CSV sample file

On Premises Exchange Cutover migration to Office 365

Before you begin:

As part of an Office 365 deployment, you can migrate the contents of user mailboxes from a source email system to Office 365. When you do this all at one time, it’s called a cutover migration. Choosing a cutover migration is suggested when:

  • Your current on-premises Exchange organization is Microsoft Exchange Server 2003, Microsoft Exchange Server 2007, Microsoft Exchange Server 2010, or Microsoft Exchange Server 2013.
  • Your on-premises Exchange organization has fewer than 2,000 mailboxes.

    Note: Even though cutover migration supports moving up to 2000 mailboxes, due to length of time it takes to create and migrate 2000 users, it is more reasonable to migrate 150 users or less.

     

Plan for migration

Things to consider

Setting up an email cutover migration to Office 365 requires careful planning. Before you begin, here are a few things to consider:

  • You can move your entire email organization to Office 365 over a few days and manage user accounts in Office 365.
  • A maximum of 2,000 mailboxes can be migrated to Office 365 by using a cutover Exchange migration. However, it is recommended that you only migrate 150 mailboxes.
  • The primary domain name used for your on-premises Exchange organization must be an accepted as a domain owned by you in your Office 365 organization.
  • After the migration is complete, each user who has an on-premises Exchange mailbox also will be a new user in Office 365. But you’ll still have to assign licenses to users whose mailboxes are migrated.
Impact to users

After your on-premises and Office 365 organizations are set up for a cutover migration, post-setup tasks could impact your users.

  • Administrators or users must configure desktop computers         Make sure that desktop computers are updated and set up for use with Office 365. These actions allow users to use local user credentials to sign in to Office 365 from desktop applications. Users with permission to install applications can update and set up their own desktops. Or updates can be installed for them. After updates are made, users can send email from Outlook 2013, Outlook 2010, or Outlook 2007.
  • Potential delay in email routing        Email sent to on-premises users whose mailboxes were migrated to Office 365 are routed to their on-premises Exchange mailboxes until the MX record is changed.

How does cutover migration work?

The main steps you perform for a cutover migration are shown in the following illustration.

Process for performing a cutover email migration to Office 365

  1. The administrator communicates upcoming changes to users and verifies domain ownership with the domain registrar.
  2. The administrator prepares the servers for a cutover migration and creates empty mail-enabled security groups in Office 365.
  3. The administrator connects Office 365 to the on-premises email system (this is called creating a migration endpoint).
  4. The administrator migrates the mailboxes and then verifies the migration.
  5. Grant Office 365 licences to your users.
  6. The administrator configures the domain to begin routing email directly to Office 365.
  7. The administrator verifies that routing has changed, and then deletes the cutover migration batch.
  8. The administrator completes post-migration tasks in Office 365 (assigns licenses to users and creates an Autodiscover Domain Name System (DNS) record), and optionally decommissions the on-premises Exchange servers.
  9. The administrator sends a welcome letter to users to tell them about Office 365 and to describe how to sign in to their new mailboxes.

Running Cutover Migration:

Prepare for a cutover migration

Before you migrate mailboxes to Office 365 by using a cutover migration, there are a few changes to your Exchange Server environment you must complete first.

Note: If you have turned on directory synchronization, you need to turn it off before you can perform a cutover migration. You can do this by using PowerShell. For instructions, see Turn off directory synchronization for Office 365.

  1. Configure Outlook Anywhere on your on-premises Exchange Server     The email migration service uses Outlook Anywhere (also known as RPC over HTTP), to connect to your on-premises Exchange Server. Outlook Anywhere is automatically configured for Exchange 2013. For information about how to set up Outlook Anywhere for Exchange 2010, Exchange 2007, and Exchange 2003, see the following:
  2. You must use a certificate issued by a trusted certification authority (CA) with your Outlook Anywhere configuration in order for Office 365 to run a cutover migration. For cutover migration you will to add the Outlook Anywhere and Autodiscover services to your certificate. For instructions on how to set up certificates, see:
  3. Optional: Verify that you can connect to your Exchange organization using Outlook Anywhere     Try one of the following methods to test your connection settings.
    • Use Outlook from outside your corporate network to connect to your on-premises Exchange mailbox.
    • Use the Microsoft Exchange Remote Connectivity Analyzer to test your connection settings. Use the Outlook Anywhere (RPC over HTTP) or Outlook Autodiscover tests.
    • Wait for the connection to automatically be tested when you connect Office 365 to your email system later in this procedure.
  4. Set permissions     The on-premises user account that you use to connect to your on-premises Exchange organization (also called the migration administrator) must have the necessary permissions to access the on-premises mailboxes that you want to migrate to Office 365. This user account is used when you connect Office 365 to your email system later in this procedure.
  5. To migrate the mailboxes, the admin must have one of the following permissions:
    • The migration administrator must be assigned the FullAccess permission for each on-premises mailbox.

      or

    • The migration administrator must be assigned the Receive As permission on the on-premises mailbox database that stores user mailboxes.

    For instructions about how to set these permissions, see Assign Exchange permissions to migrate mailboxes to Office 365

  6. Disable Unified Messaging (UM)     If UM is turned on for the on-premises mailboxes you’re migrating, turn off UM before migration. Turn on UM or the mailboxes after migration is complete. For how-to steps, see Disable Unified Messaging for users for Exchange 2007.
  7. Create security groups and clean up delegates    Because the email migration service can’t detect whether on-premises Active Directory groups are security groups, it can’t provision any migrated groups as security groups in Office 365. If you want to have security groups in Office 365, you must first provision an empty mail-enabled security group in Office 365 before starting the cutover migration.

    Additionally, this migration method only moves mailboxes, mail users, mail contacts, and mail-enabled groups. If any other Active Directory object, such as user mailbox that is not migrated to Office 365 is assigned as a manager or delegate to an object being migrated, you must remove them from the object before migration.

Step 1: Verify you own the domain

During the migration, the Simple Mail Transfer Protocol (SMTP) address of each on-premises mailbox is used to create the email address for a new Office 365 mailbox. To run a cutover migration, the on-premises domain must be a verified domain in your Office 365 organization.

  1. Sign in to Office 365 with your work or school account.
  2. Go to the Domains page.
  3. On the Domains- page, click Add domain to start the domain wizard.

    Choose Add domain

  4. On the Add a domain page, type in the domain name (for example, Contoso.com) you use for your on-premises Exchange organization, and then choose Next.
  5. On the Verify domain page, select either Sign in to GoDaddy (if your DNS records are managed by GoDaddy) or Add a TXT record instead for any other registrars > Next.
  6. Follow the instructions provided for your DNS hosting provider. The TXT record usually is chosen to verify ownership.

    You can also find the instructions in Create DNS records for Office 365 when you manage your DNS records.

    After you add your TXT or MX record, wait about 15 minutes before proceeding to the next step.

  7. In the Office 365 domain wizard, choose done, verify now, and you’ll see a verification page. Choose Finish.

    If the verification fails at first, wait awhile, and try again.

    Do not continue to the next step in the domain wizard. You now have verified that you own the on-premises Exchange organization domain and are ready to continue with an email migration.

Step 2: Connect Office 365 to your email system

A migration endpoint contains the settings and credentials needed to connect the on-premises server that hosts the mailboxes you’re migrating with Office 365. The migration endpoint also defines the number of mailboxes to migrate simultaneously. For a cutover migration, you’ll create an Outlook Anywhere migration endpoint.

  1. Go to the Exchange admin center.
  2. In the Exchange admin center, go to Recipients > Migration.
  3. Choose More More icon > Migration endpoints.

    Select Migration endpoint.

  4. On the Migration endpoints page, choose New New icon .
  5. On the Select the migration endpoint type page, choose Outlook Anywhere > Next.
  6. On the Enter on-premises account credentials page, enter information in the following boxes:
    • Email address     Type the email address of any user in the on-premises Exchange organization that will be migrated. Office 365 will test the connectivity to this user’s mailbox.
    • Account with privileges     Type the user name (domain\user name format or an email address) for an account that has the necessary administrative permissions in the on-premises organization. Office 365 will use this account to detect the migration endpoint and to test the permissions assigned to this account by attempting to access the mailbox with the specified email address.
    • Password of account with privileges     Type the password for the account with privileges that is the administrator account.
  7. Choose Next and do one of the following:
    • If Office 365 successfully connects to the source server, the connection settings are displayed. Choose Next.

      Confirmed connection for Outlook Anywhere endpoint.

    • If the test connection to the source server isn’t successful, provide the following information:
      • Exchange server     Type the fully qualified domain name (FQDN) for the on-premises Exchange Server. This is the host name for your Mailbox server. For example, EXCH-SRV-01.corp.contoso.com.
      • RPC proxy server     Type the FQDN for the RPC proxy server for Outlook Anywhere. Typically, the proxy server is the same as your Outlook Web App URL. For example, mail.contoso.com, which is also the URL for the proxy server that Outlook uses to connect to an Exchange Server
  8. On the Enter general information page, type a Migration endpoint name, for example, Test5-endpoint. Leave the other two boxes blank to use the default values.

    Migration endpoint name.

  9. Choose New to create the migration endpoint.

    To validate your Exchange Online is connected to the on-premises server, you can run the command in Example 4 of Test-MigrationServerAvailability.

Step 3: Create the cutover migration batch

In a cutover migration, on-premises mailboxes are migrated to Office 365 in a single migration batch.

  1. In the Exchange admin center, go to Recipients > Migration.
  2. Choose New New icon > Migrate to Exchange Online.

    Select Migrate to Exchange Online

  3. On the Select a migration type page, choose Cutover migration > next.
  4. On the Confirm the migration endpoint page, the migration endpoint information is listed. Verify the information and then choose next.

    New migration batch with confirmed endpoint.

  5. On the Move configuration page, type the name (cannot contain spaces or special characters) of the migration batch, and then choose next. The batch name is displayed in the list of migration batches on the Migration page after you create the migration batch.
  6. On the Start the batch page, choose one of the following:
    • Automatically start the batch     The migration batch is started as soon as you save the new migration batch with a status of Syncing.
    • Manually start the batch later     The migration batch is created but is not started. The status of the batch is set to Created. To start a migration batch, select it on the migration dashboard, and then choose Start.
  7. Choose new to create the migration batch.

    The new migration batch is displayed on the migration dashboard.

Step 4: Start the cutover migration batch

If you created a migration batch and configured it to be started manually, you can start it by using the Exchange admin center.

  1. In the Exchange admin center, go to Recipients > Migration.
  2. On the migration dashboard, select the batch and then choose Start.
  3. If a migration batch starts successfully, its status on the migration dashboard changes to Syncing.

    Micgration batch is syncing

Verify the synchronization worked

  • You’ll be able to follow the sync status on the migration dashboard. If there are errors, you can view a log file that gives you more information about them.
  • You can also verify that the users get created in the Office 365 admin center as the migration proceeds.

    After the migration is done, the sync status is Synced.

Optional: Reduce email delays

Although this task is optional, doing it can help avoid delays in the receiving email in the new Office 365 mailboxes.

When people outside of your organization send you email, their email systems don’t double-check where to send that email every time. Instead, their systems save the location of your email system based on a setting in your DNS server known as a time-to-live (TTL). If you change the location of your email system before the TTL expires, the sender’s email system tries to send email to the old location before figuring out that the location changed. This location change can result in a mail delivery delay. One way to avoid this is to lower the TTL that your DNS server gives to servers outside of your organization. This will make the other organizations refresh the location of your email system more often.

Most email systems ask for an update each hour if a short interval such as 3,600 seconds (one hour) is set. We recommend that you set the interval at least this low before you start the email migration. This setting allows all the systems that send you email enough time to process the change. Then, when you make the final switch over to Office 365, you can change the TTL back to a longer interval.

The place to change the TTL setting is on your email system’s MX record. This lives on your public-facing DNS system. If you have more than one MX record, you need to change the value on each record to 3,600 seconds or less.

If you need some help configuring your DNS settings, see Create DNS records for Office 365 when you manage your DNS records.

Step 5: Route your email directly to Office 365

Email systems use a DNS record called an MX record to figure out where to deliver emails. During the email migration process, your MX record was pointing to your source email system. Now that the email migration to Office 365 is complete, it’s time to point your MX record at Office 365. This helps make sure that email is delivered to your Office 365 mailboxes. Moving the MX record will also let you turn off your old email system when you’re ready.

For many DNS providers, there are specific instructions to change your MX record. If your DNS provider isn’t included, or if you want to get a sense of the general directions, general MX record instructions are provided as well.

It can take up to 72 hours for the email systems of your customers and partners to recognize the changed MX record. Wait at least 72 hours before you proceed to the next task: Delete the cutover migration batch.

Step 6: Delete the cutover migration batch

After you change the MX record and verify that all email is being routed to Office 365 mailboxes, notify the users that their mail is going to Office 365. After this you can delete the cutover migration batch. Verify the following before you delete the migration batch.

  • All users are using Office 365 mailboxes. After the batch is deleted, mail sent to mailboxes on the on-premises Exchange Server isn’t copied to the corresponding Office 365 mailboxes.
  • Office 365 mailboxes were synchronized at least once after mail began being sent directly to them. To do this, make sure that the value in the Last Synced Time box for the migration batch is more recent than when mail started being routed directly to Office 365 mailboxes.

When you delete a cutover migration batch, the migration service cleans up any records related to the migration batch and then deletes the migration batch. The batch is removed from the list of migration batches on the migration dashboard.

  1. In the Exchange admin center, go to Recipients > Migration.
  2. On the migration dashboard, select the batch, and then choose Delete.

    Note: It can take a few minutes or the batch to be removed.

  3. In the Exchange admin center, go to Recipients > Migration.
  4. Verify that the migration batch is no longer listed on the migration dashboard.
Step 7: Assign licenses to Office 365 users

Activate Office 365 user accounts for the migrated accounts by assigning licenses.    If you don’t assign a license, the mailbox is disabled when the grace period ends (30 days). To assign a license in the Office 365 admin center, see Assign licenses to users in Office 365 for Business.

Complete post migration tasks

After migrating mailboxes to Office 365, there are post-migration tasks that must be completed.

  1. Create an Autodiscover DNS record so users can easily get to their mailboxes.    After all on-premises mailboxes are migrated to Office 365, you can configure an Autodiscover DNS record for your Office 365 organization to enable users to easily connect to their new Office 365 mailboxes with Outlook and mobile clients. This new Autodiscover DNS record has to use the same namespace that you’re using for your Office 365 organization. For example, if your cloud-based namespace is cloud.contoso.com, the Autodiscover DNS record you need to create is autodiscover.cloud.contoso.com.

    If you keep your Exchange Server, you should also make sure that Autodiscover DNS CNAME record has to point to exOffice365 in both internal and external DNS after the migration so that the Outlook client will to connect to the correct mailbox.

    Note:  In Exchange 2007, Exchange 2010, and Exchange 2013 you should also set Set-ClientAccessServer AutodiscoverInternalConnectionURI to Null.

    Office 365 uses a CNAME record to implement the Autodiscover service for Outlook and mobile clients. The Autodiscover CNAME record must contain the following information:

    • Alias:    autodiscover
    • Target:    autodiscover.outlook.com

    For more information, see Create DNS records for Office 365 when you manage your DNS records.

  2. Decommission on-premises Exchange Servers.    After you’ve verified that all email is being routed directly to the Office 365 mailboxes, and no longer need to maintain your on-premises email organization or don’t plan on implementing a single sign-on solution, you can uninstall Exchange from your servers and remove your on-premises Exchange organization.

    For more information, see the following:

    Note: Decommissioning Exchange can have unintended consequences. Before decommissioning your on-premises Exchange organization, we recommend that you contact Microsoft Support.

    Disclaimer: This article has been published for the learning purpose only for the real-time migration consult with your IT team and Exchange professional or expert near you. If there is any issue which you caused by doing anything wrong will be your responsibility.

Get Office 365 Education for free

Teachers want to save time and help their student get more done in the classroom and life. Office 365 Education is Microsoft’s classroom offering built for teachers and students, completely free, and full of powerful tools to organize in one place, engage students in new ways, and individualize student learning. Office 365 is fully integrated set of tools, to help students and teachers complete all important school tasks online, offline, or on mobile devices.

OneNote provides one place to organize lessons and distribute assignments, while bringing students together in a collaborative space or giving them individual support in private notebooks. With Learning Tools, built-in reading and writing tools improve learning outcomes for all students. Office Online offers you web versions of familiar Word, PowerPoint, Excel, OneNote and more that work in all modern browsers. And it’s available everywhere for free with nothing to install. Collaborate with anyone and see what your co-authors type as it’s happening. You can move smoothly from light work and collaboration in Office Online to heavy-duty creation in the Office desktop application without ever leaving your document or losing your formatting.

Sway is new digital storytelling app from Office that is great for project or problem-based learning. Teachers can create interactive web-based lessons, assignments, project recaps, newsletters, and more right from a phone, tablet, or browser. Students can collaborate and use Sway to create engaging reports, assignments, projects, study materials, and portfolios. Sways are easy to share with the class or the world and look great on any screen.

Get Office 365 Education for free at Microsoft Education Partner program.

 

Cloud Adaptation and SharePoint Server Test Lab Guide for IT Professionals

Use these cloud adoption Test Lab Guides (TLGs) to set up demonstration or dev/test environments for Office 365, Enterprise Mobility + Security (EMS), Dynamics 365, and Office Server products.

TLGs help you quickly learn about Microsoft products. They’re great for situations where you need to evaluate a technology or configuration before you decide whether it’s right for you or before you roll it out to users. The “I built it out myself and it works” hands-on experience helps you understand the deployment requirements of a new product or solution so you can better plan for hosting it in production.

TLGs also create representative environments for development and testing of applications, also known as dev/test environments.

Test Lab Guides in the Microsoft Cloud

See these additional resources before diving in:

Use these articles to build your Office 365 dev/test environment:

  • Base Configuration dev/test environment

    Create a simplified intranet running in Microsoft Azure infrastructure services. This is an optional step if you want to build a simulated enterprise configuration.

  • Office 365 dev/test environment

    Create an Office 365 Enterprise E5 trial subscription, which you can do from your computer or from a simplified intranet running in Azure infrastructure services.

  • DirSync for your Office 365 dev/test environment

    Install and configure Azure AD Connect for directory synchronization with password synchronization. This is an optional step if you want to build a simulated enterprise configuration.

For your Office 365 dev/test environment, use these articles to demonstrate enterprise features of Office 365:

Create a dev/test environment for Microsoft 365 Enterprise scenarios with these articles:

Add a Dynamics 365 trial subscription and test Office 365 and Dynamics 365 integrated features and scenarios with these articles:

Create a dev/test environment that includes all of Microsoft’s cloud offerings: Office 365, Azure, EMS, and Dynamics 365. See The One Microsoft Cloud dev/test environment for the step-by-step instructions.

You can create a cross-premises dev/test environment, which includes an Azure virtual network and a simulated on-premises network, with these articles:

Here are additional cloud-based dev/test environments that you can create in Azure infrastructure services:

Join the discussion

Contact us Description
What cloud adoption content do you need? We are creating content for cloud adoption that spans multiple Microsoft cloud platforms and services. Let us know what you think about our cloud adoption content, or ask for specific content by sending email to cloudadopt@microsoft.com.
Join the cloud adoption discussion If you are passionate about cloud-based solutions, consider joining the Cloud Adoption Advisory Board (CAAB) to connect with a larger, vibrant community of Microsoft content developers, industry professionals, and customers from around the globe. To join, add yourself as a member of the CAAB (Cloud Adoption Advisory Board) space of the Microsoft Tech Community and send us a quick email at CAAB@microsoft.com. Anyone can read community-related content on the CAAB blog. However, CAAB members get invitations to private webinars that describe new cloud adoption resources and solutions.
Get the art you see here If you want an editable copy of the art you see in this article, we’ll be glad to send it to you. Email your request, including the URL and title of the art, to cloudadopt@microsoft.com.

Free Step by Step SharePoint Server 2013 Lab Guides by Microsoft

This Post contains a bunch of Free Step by Step SharePoint Server 2013 Lab Guides that Microsoft gives for free on its Download Center. Usually I post them together with the other free resources that Microsoft offers, however this is a Test Lab Guide (TLG) only post, and the rest of the resources will come later in the month.

Free Step by Step SharePoint Server 2013 Lab Guides by Microsoft

Microsoft Download Center

  1. Test Lab Guide: Configure SharePoint Server 2013 in a three-tier farm
  2. Test Lab Guide: Configure intranet and team sites for SharePoint Server 2013
  3. Test Lab Guide: Demonstrate permissions with SharePoint Server 2013
  4. Test Lab Guide: Demonstrate profile synchronization for SharePoint Server 2013
  5. Test Lab Guide: Demonstrate Social Features for SharePoint Server 2013
  6. Test Lab Guide: Demonstrate SAML-based Claims Authentication with SharePoint Server 2013
  7. Test Lab Guide: Demonstrate forms-based claims authentication for SharePoint Server 2013
  8. Test Lab Guide: Configure eDiscovery for SharePoint Server 2013
  9. Test Lab Guide: Create a Business Intelligence Baseline Environment
  10. Test Lab Guide: Configure Secure Store
  11. Test Lab Guide: Configure Excel Services
  12. Test Lab Guide: Configure the Excel Services unattended service account
  13. Test Lab Guide: Configure Excel Services data refresh by using an embedded connection
  14. Test Lab Guide: Configure Excel Services data refresh by using an external connection
  15. Test Lab Guide: Configure Visio Services
  16. Test Lab Guide: Configure the Visio Services unattended service account
  17. Test Lab Guide: Configure Visio Services data refresh using an external connection
  18. Test Lab Guide: Configure PerformancePoint Services
  19. Test Lab Guide: Configure data access for PerformancePoint Services
  20. Test Lab Guide Mini-Module: Configuring a Second SharePoint Server 2013 Farm 
  21. Test Lab Guide: Configure a Highly Available SharePoint Server 2013 Search Topology
  22. Test Lab Guide: Configure an Integrated Exchange, Lync, and SharePoint Test Lab

A very nice Poster from Microsoft that resumes the above http://www.microsoft.com/en-ca/download/details.aspx?id=39298
Teched North America

  1. Configuring Office Web Applications for Microsoft SharePoint 2013 
  2. Configuring Social Features in Microsoft SharePoint 2013 
  3. Extending the Search Experience in Microsoft SharePoint 2013 
  4. Introduction to Web Content Management in Microsoft SharePoint 2013 
  5. Designing a Microsoft SharePoint 2013 Site 

Migrate Google G-Suite mailboxes to Office 365

Migrate your IMAP mailboxes to Office 365 gives you an overview of the migration process. Read it first and when you’re familiar with the contents of that article, return to this topic to learn how to migrate mailboxes from G Suite (formerly known as Google Apps) Gmail to Office 365. You must be a global admin in Office 365 to complete IMAP migration steps.

Looking for Windows PowerShell commands? See User PowerShell to perform an IMAP migration to Office 365.

Want to migrate other types of IMAP mailboxes? See Migrate other types of IMAP mailboxes to Office 365 .

Migration from G Suite mailboxes using the Office 365 admin center

You can use the setup wizard in the Office 365 admin center for an IMAP migration. See IMAP migration in the Office 365 admin center for instructions.

IMPORTANT: IMAP migration will only migrate emails, not calendar and contact information. Users can import their own email, contacts, and other mailbox information to Office 365. See Migrate email and contacts to Office 365 for Business to learn how.

Before Office 365 can connect to Gmail or G Suites, all the account owners need to create an app password to access their account. This is because Google considers Outlook to be a less secure app and will not allow a connection to it with a password alone. For instructions, see Prepare your G Suite account for connecting to Outlook and Office 365. You’ll also need to make sure your G Suite users can turn on 2-step verification.

Gmail Migration tasks

The following list contains the migration tasks given in the order in which you should complete them.

Step 1: Verify you own your domain

In this task, you’ll first verify to Office 365 that you own the domain you used for your G Suite accounts.

Notes:

  • Another option is to use the your company name.onmicrosoft.com domain that is included with your Office 365 subscription instead of using your own custom domain. In that case, you can just add users as described in Create users in Office 365 and omit this task.
  • Most people, however, prefer to use their own domain.

Domain verification is a task you will go through as you setup Office 365. During the setup Office 365 setup wizard provides you with a TXT record you will add at your domain host provider. See Verify your domain in Office 365 for the steps to complete in Office 365 admin center, and choose a domain registrar from the two following options to see how to complete add the TXT record that your DNS host provider.

  • Your current DNS host provider is Google.    If you purchased your domain from Google and they are the DNS hosting provider, follow these instructions: Create DNS records when your domain is managed by Google.
  • You purchased your domain from another domain registrar.    If you purchased your domain from a different company, we provide instructions for many popular domain hosting providers.

Step 2: Add users to Office 365

You can add your users either one at a time, or several users at a time. When you add users you also add licenses to them. Each user has to have a mailbox on Office 365 before you can migrate email to it. Each user also needs a license that includes an Exchange Online plan to use his or her mailbox.

Important: At this point you have verified that you own the domain and created your G Suite users and mailboxes in Office 365 with your custom domain. Close the wizard at this step. Do not proceed to Set up domain, until your Gmail mailboxes are migrated to Office 365. You’ll finish the setup steps in task 7, Route Gmail directly to Office 365.

Step 3: Create a list of Gmail mailboxes to migrate

For this task, you create a migration file that contains a list of Gmail mailboxes to migrate to Office 365. The easiest way to create the migration file is by using Excel, so we use Excel in these instructions. You can use Excel 2013, Excel 2010, or Excel 2007.

When you create the migration file, you need to know the password of each Gmail mailbox that you want to migrate. We’re assuming you don’t know the user passwords, so you’ll probably need to assign temporary passwords (by resetting the passwords) to all mailboxes during the migration. You must be an administrator in G Suite to reset passwords.

You don’t have to migrate all Gmail mailboxes at once. You can do them in batches at your convenience. You can include up to 50,000 mailboxes (one row for each user) in your migration file. The file can be as large as 10 MB.

  1. Sign in to G Suite admin console using your administrator username and password.
  2. After you’re signed in, choose Users.

    List of users in the Google admin center.

  3. Select each user to identify each user’s email address. Write down the address.

    User details in the Google apps admin center

  4. Sign in to the Office 365 admin center, and go to Users > Active users. Keep an eye on the User name column. You’ll use this information in a minute. Keep the Office 365 admin center window open, too.

    User Name column in the Office 365 admin center.

  5. Start Excel.
  6. Use the following screenshot as a template to create the migration file in Excel. Start with the headings in row 1. Make sure they match the picture exactly and don’t contain spaces. The exact heading names are:
    • EmailAddress in cell A1.
    • UserName in cell B1.
    • Password in cell C1.

      Cell headings in the Excel migration file.

  7. Next enter the email address, user name, and password for each mailbox you want to migrate. Enter one mailbox per row.
    • Column A is the email address of the Office 365 mailbox. This is what’s shown in the User name column in Users > Active users in the Office 365 admin center.
    • Column B is the sign-in name for the user’s Gmail mailbox—for example, alberta@contoso.com.
    • Column C is the app password for the user’s Gmail mailbox. Creating the app password is described in Migration from G Suite mailboxes using the Office 365 admin center.

      A completed sample migration file.

  8. Save the file as a CSV file type, and then close Excel.

    Shows the Save As CSV option in Excel.

Step 4: Connect Office 365 to Gmail

To migrate Gmail mailboxes successfully, Office 365 needs to connect and communicate with Gmail. To do this, Office 365 uses a migration endpoint. Migration endpoint is a technical term that describes the settings that are used to create the connection so you can migrate the mailboxes. You create the migration endpoint in this task.

  1. Go to the Exchange admin center.
  2. In the EAC, go to Recipients > Migration > More More icon > Migration endpoints.

    Select Migration endpoint.

  3. Click New New icon to create a new migration endpoint.
  4. On the Select the migration endpoint type page, choose IMAP.
  5. On the IMAP migration configuration page, set IMAP server to imap.gmail.com and keep the default settings the same.
  6. Click Next. The migration service uses the settings to test the connection to Gmail system. If the connection works, the Enter general information page opens.
  7. On the Enter general information page, type a Migration endpoint name, for example, Test5-endpoint. Leave the other two boxes blank to use the default values.

    Migration endpoint name.

  8. Click New to create the migration endpoint.

Step 5: Create a migration batch and start migrating Gmail mailboxes

You use a migration batch to migrate groups of Gmail mailboxes to Office 365 at the same time. The batch consists of the Gmail mailboxes that you listed in the migration file in the previous task.

Tips:

  • It’s a good idea to create a test migration batch with a small number of mailboxes to first test the process.
  • Use migration files with the same number of rows, and run the batches at similar times during the day. Then compare the total running time for each test batch. This helps you estimate how long it could take to migrate all your mailboxes, how large each migration batch should be, and how many simultaneous connections to the source email system you should use to balance migration speed and Internet bandwidth.
  1. In the Office 365 admin center, navigate to Admin centers > Exchange.

    Go to Exchange admin center.

  2. In the Exchange admin center, go to Recipients > Migration.
  3. Click New New icon > Migrate to Exchange Online.

    Select Migrate to Exchange Online

  4. Choose IMAP migration > Next.
  5. On the Select the users page, click Browse to specify the migration file you created. After you select your migration file, Office 365 checks it to make sure:
    • It isn’t empty.
    • It uses comma-separated formatting.
    • It doesn’t contain more than 50,000 rows.
    • It includes the required attributes in the header row.
    • It contains rows with the same number of columns as the header row.

    If any one of these checks fails, you’ll get an error that describes the reason for the failure. If you get an error, you must fix the migration file and resubmit it to create a migration batch.

  6. After Office 365 validates the migration file, it displays the number of users listed in the file as the number of Gmail mailboxes to migrate.

    New migration batch with CSV file

  7. Click Next.
  8. On the Set the migration endpoint page, select the migration endpoint that you created in the previous step, and click Next.
  9. On the IMAP migration configuration page, accept the default values, and click Next.
  10. On the Move configuration page, type the name (no spaces or special characters) of the migration batch in the box—for example, Test5-migration. The default migration batch name that’s displayed is the name of the migration file that you specified. The migration batch name is displayed in the list on the migration dashboard after you create the migration batch.

    You can also enter the names of the folders you want to exclude from migration. For example, Shared, Junk Email, and Deleted. Click Add Add icon to add them to the excluded list. You can also use the edit icon Add icon to change a folder name and the remove icon Remove icon to delete the folder name.

    Move configuration dialog

  11. Click Next
  12. On the Start the batch page, do the following:
    • Choose Browse to send a copy of the migration reports to other users. By default, migration reports are emailed to you. You can also access the migration reports from the properties page of the migration batch.
    • Choose Automatically start the batch > new. The migration starts immediately with the status Syncing.

      Micgration batch is syncing

Note: If the status shows Syncing for a long time, you may be experiencing bandwidth limits set by Google. For more information, see Bandwidth limits.

Verify that the migration worked

  • In the Exchange admin center, go to Recipients > Migration. Verify that the batch is displayed in the migration dashboard. If the migration completed successfully, the status is Synced.
  • If this task fails, check the associated Mailbox status reports for specific errors, and double-check that your migration file has the correct Office 365 email address in the EmailAddress column.

Verify a successful mailbox migration to Office 365

  • Ask your migrated users to complete the following tasks:
    • Go to the Office 365 sign-in page, and sign in with your user name and temporary password.
    • Update your password, and set your time zone. It’s important that you select the correct time zone to make sure your calendar and email settings are correct.
    • When Outlook Web App opens, send an email message to another Office 365 user to verify that you can send email.
    • Choose Outlook, and check that your email messages and folders are all there.

Optional: Reduce email delays

Although this task is optional, doing it can help avoid delays in the receiving email in the new Office 365 mailboxes.

When people outside of your organization send you email, their email systems don’t double-check where to send that email every time. Instead, their systems save the location of your email system based on a setting in your DNS server known as a time-to-live (TTL). If you change the location of your email system before the TTL expires, the sender’s email system tries to send email to the old location before figuring out that the location changed. This can result in a mail delivery delay. One way to avoid this is to lower the TTL that your DNS server gives to servers outside of your organization. This will make the other organizations refresh the location of your email system more often.

Most email systems ask for an update each hour if a short interval such as 3,600 seconds (one hour) is set. We recommend that you set the interval at least this low before you start the email migration. This setting allows all the systems that send you email enough time to process the change. Then, when you make the final switch over to Office 365, you can change the TTL back to a longer interval.

The place to change the TTL setting is on your email system’s mail exchanger record, also called an MX record. This lives in your public facing DNS. If you have more than one MX record, you need to change the value on each record to 3,600 seconds or less.

Don’t worry if you skip this task. It might take longer for email to start showing up in your new Office 365 mailboxes, but it will get there.

If you need some help configuring your DNS settings, see Create DNS records for Office 365 when you manage your DNS records.

Step 6: Update your DNS records to route Gmail directly to Office 365

Email systems use a DNS record called an MX record to figure out where to deliver email. During the email migration process, your MX record was pointing to your Gmail system. Now that you’ve completed your email migration to Office 365, it’s time to point your MX record to Office 365. After you change your MX record following these steps, email sent to users at your custom domain is delivered to Office 365 mailboxes

For many DNS providers, there are specific instructions to change your MX record, see Create DNS records for Office 365 when you manage your DNS records for instructions. If your DNS provider isn’t included, or if you want to get a sense of the general directions, general MX record instructions are provided as well. See Create DNS records at any DNS hosting provider for Office 365 for instructions.

  1. Sign in to Office 365 with your work or school account.
  2. Go to the Domains page.
  3. Select your domain and then choose Fix issues.

    The status shows Fix issues because you stopped the wizard partway through so you could migrate your Gmail email to Office 365 before switching your MX record.

    Domain that needs to be fixed.

  4. For each DNS record type that you need to add, choose What do I fix?, and follow the instructions to add the records for Office 365 services.
  5. After you’ve added all the records, you’ll see a message that your domain is set up correctly: Contoso.com is set up correctly. No action is required.

It can take up to 72 hours for the email systems of your customers and partners to recognize the changed MX record. Wait at least 72 hours before you proceed to stopping synchronization with Gmail.

Step 7: Stop synchronization with Gmail

During the last task, you updated the MX record for your domain. Now it’s time to verify that all email is being routed to Office 365. After verification, you can delete the migration batch and stop the synchronization between Gmail and Office 365. Before you take this step:

  • Make sure that your users are using Office 365 exclusively for email. After you delete the migration batch, email that is sent to Gmail mailboxes isn’t copied to Office 365 This means your users can’t get that email, so make sure that all users are on the new system.
  • Let the migration batch run for at least 72 hours before you delete it. This makes the following two things more likely:
    • Your Gmail mailboxes and Office 365 mailboxes have synchronized at least once (they synchronize once a day).
    • The email systems of your customers and partners have recognized the changes to your MX records and are now properly sending email to your Office 365 mailboxes.

When you delete the migration batch, the migration service cleans up any records related to the migration batch and removes it from the migration dashboard.

Delete a migration batch

  1. In the Exchange admin center, go to Recipients > Migration.
  2. On the migration dashboard, select the batch, and then click Delete.

How do you know this worked?

  • In the Exchange admin center, navigate to Recipients > Migration. Verify that the migration batch no longer is listed on the migration dashboard.
Step 8: Users migrate their calendar and contacts

After your migrate their email, users can import their Gmail calendar and contacts to Outlook:

SharePoint 3-tier On Premises installation

This post is a complete solution for setting up SharePoint 2016 on-premise. Most of the documents available online do not provide a complete solution/steps to install SharePoint 2016 with all of the prerequisites to be installed manually. Also, troubleshooting steps are provided for some of the most common mistakes done while installing.

The Three-Tier Architecture

https://i-technet.sec.s-msft.com/dynimg/IC378512.gif

This post is based on the setup on to a virtual machine based environment and will guide you how to set up the SharePoint server 2016 in your VM environment. If you are looking for the similar setup into your physical machines then please do consider checking hardware and software requirements required, supported system, storage system and finally networking.

This document is a simplified guide written to cover all aspects and scenarios encountered while setting up the prerequisites for SharePoint 2016, system requirements, errors and problems faced during set up.

In this guide we will use Windows 2k12 R2 server as an example and explain the detailed procedure.

Prerequisites:

1. A Windows 2k12 server file (Windows_server_2012_r2_with_update_x64_dvd.iso)

According to your requirement and the installation scenario use the below configurations:

Installation scenario Deployment type and scale RAM Processor Hard disk space
Single server role that uses SQL Server Development or evaluation installation of SharePoint Server 2016 with the minimum recommended services for development environments. Use the Single-Server farm role that will let you choose which service applications to provision. For additional information on Single-Server farm role, see Overview of MinRole Server Roles in SharePoint Server 2016 16 GB 64-bit, 4 cores 80 GB for system drive100 GB for second drive
Single server role that uses SQL Server Pilot or user acceptance test installation of SharePoint Server 2016 running all available services for development environments. 24 GB 64-bit, 4 cores 80 GB for system drive100 GB for second drive and additional drives
Web server or application server in a three-tier farm Development or evaluation installation of SharePoint Server 2016 with a minimum number of services. 12 GB 64-bit, 4 cores 80 GB for system drive80 GB for second drive
Web server or application server in a three-tier farm Pilot, user acceptance test, or production deployment of SharePoint Server 2016 running all available services. 16 GB 64-bit, 4 cores 80 GB for system drive80 GB for second drive and additional drives
https://technet.microsoft.com/en-us/library/cc262485(v=office.16).aspx#Anchor_1

2. Active Directory Server in the same Domain where you will be installing SharePoint 2016 Server

3. SQL Server 2014 (SQLServer2014SP2-Full-x64-ENU.iso)

4. SharePoint server 2016 with license (SharePoint_server_2016_x64_dvd_8419458.iso)

Note: Here in this lab I have used SharePoint 2016 180 days trial licenses and into windows servers I have used my MSDN licenses but in your environment you may have different types of licenses so take a brief look at its limitations as well before using them.

Install Windows 10, and Windows Server 2012 R2 update: April 2016.

All the steps are explained in detail with pictures below:

Step 1:

As we are using Windows Server 2012 R2 in our example, let’s update the server with all the latest available updates, the updates can vary depending upon the win2k12 r2 iso file you have.

It’s recommended to install all the latest available updates from Microsoft.

updates_windows2k12

Once the system is updated restart the server.

Step 2:

Install the Active Directory server on Win2k12 R2 server. The step by step procedure to set it up is given here: https://support.rackspace.com/how-to/installing-active-directory-on-windows-server-2012/.

AD server is one of the prerequisites which needs to be installed on the same domain where the SharePoint server will be installed.

Once AD is installed properly the System is ready for step 3.

Step 3

In order to install and configure SQL server 2014 you need to install .NET framework 3.5 first, which can be installed as shown below.

* Click on Server Manager–>Manage–>Add Roles and Features–>Select Features tab as shown below.

DOTNET3.5 install * Select .NET Framework 3.5 Features and include the (.NET 2.0 and 3.0) by clicking on the check boxes and click –>Next–>Install

* The installation will take around 1 – 3 minutes.

Step 4

After installing the .NET Framework 3.5, which is a requirement for SQL2014, begin installing the SQL 2014 server on the Win2k12 Server.

  • Mount the SQLServer2014SP2-Full-x64-ENU.iso and click on “Setup” application.

Install SQL2014

  • Now a popup screen appears in which you have to select the option “Installation –>New SQL server stand alone installation or add features to an existing installation”.

Click on New

  • The next popup will ask for entering product key or Evaluation i.e. free period of 180 days, select which ever is suitable for you and click Next.

product key

  • Read and accept the License terms then Click Next.
  • Once you click on Next it will check for the prerequisites of SQL 2014, verify if all the prerequisites are met and continue by clicking Next.
  • Click on Next for all the screens till Feature selection, leaving the settings to default, ignore few warnings.
  • In Feature selection, you need to select “Database Engine Services” and “Management Tools complete” then click Next as shown below.

management tools and database engine

  • The next screen is for the configurations, leave it to default which is the Feature Rules, Click on Next.
  • In the Server Configuration section, provide the Account name as your Windows login name and set to automatic. If the credentials are correct you can go to the next screen, or it will throw an error after clicking on Next.

Server config

  • Once you move on to next screen you need to do the database configurations. We need to specify authentication mode for the Database engine which is Windows authentication mode. Select on “Add current User” to add a user under specify SQL server admin section. Click Next.

DB config

  • We are almost done for the installation, now check the summary in Ready to install Window and Click on Install.
  • The installation of SQL Server 2014 will begin, check the progress which will take 10-15 minutes.

SQL 2014installation

  • Check for the success status after installation and Click on the close button to finish the installation.
  • Now let’s do a few changes to the SQL server instance installed on the server. Go to –>SQL server management studio–>Connect using Windows Authentication, which connects to the SQL Server 2014 installed on the server.

connect to SQL studio

  • Right click on the Server Name –>Properties from the Object Explorer, as shown below.
  • Click on Security–>Logins–>Right Click on the Windows login and select server roles. Assign roles “dbcreator” and “securityadmin” check boxes and click OK.

Set server roles

  • Assign the roles “dbcreator, securityadmin, and sysadmin” for “NT Authority\SYSTEM” i.e system account and the same for SQL server “NT SERVICE\MSSQLSERVER”.
  • This completes the SQL Server 2014 installation.

Step 5

Once the SQL 2104 Server is installed we are ready to start with the SharePoint Server 2014 installation.

There are some prerequisites for the SharePoint 2016 which need to be installed before directly installing SharePoint 2016. Follow the steps below which will make it easy for installing all the required components.

  • First mount the file. (SharePoint_server_2016_x64_dvd.iso)
  • There are different methods to install the prerequisites for SharePoint 2016 which may be running the ready prerequisites installer or the offline method. Normally I would prefer using the offline method because using the ready prerequisites installer will not always work fine and also not reliable. So, let’s follow the Offline method of installing the prerequisites.
  • Before proceeding with the Offline SharePoint 2016 installer, let’s try running the installer that is available with the SharePoint_server_2016_x64_dvd.iso mounted file. The prerequisiteinstaller looks like as shown in the image below.

mounted files sharepointserver2016

  • Run the installer prerequisiteinstaller application which will try to install all of the necessary components required for SharePoint 2016. The prerequisite components include the components below:

• Application Server Role, Web Server (IIS) Role
• Microsoft SQL Server 2012 Native Client
• Microsoft ODBC Driver 11 for SQL Server
• Microsoft Sync Framework Runtime v1.0 SP1 (x64)
• Windows Server AppFabric
• Microsoft Identity Extensions
• Microsoft Information Protection and Control Client 2.1
• Microsoft WCF Data Services 5.6
• Microsoft .NET Framework 4.6
• Cumulative Update Package 7 for Microsoft AppFabric 1.1 for Windows Server (KB3092423)
• Visual C++ Redistributable Package for Visual Studio 2012
• Visual C++ Redistributable Package for Visual Studio 2015

  • Click on Next in the installer and accept the License terms then proceed. Normally this fails to get installed and the error which appears as given below:

prereq error

  • Now, do not worry if this prerequisiteinstaller throws an error. Let’s start with the Offline method for installing SharePoint 2016 prerequisites.
  • There is a slight difference in the prerequisites in SharePoint 2016 when compared to SharePoint 2013.
  • let’s first download all of the prerequisites which are listed above in Step 5 and as shown in the above diagram.
  • First, let’s run the setup file from the mounted location of SharePoint 2016.iso.
  • This step will help us understand the prerequisites required to continue the installation of SharePoint 2016. The image below will give us a clear picture of what prerequisites are still required by the installer.

Setup_Run_for_prereq

  • There are 6 components which need to be installed as a prerequisite before triggering the actual SharePoint 2016 installation process. Now, let’s download the required components using a PowerShell script, which will directly download from the Microsoft trusted site.
  • The Script can be downloaded from the link below. Save the file as .ps1 file. (powershell executable file)

Download-SP2016PreReqFiles

Open PowerShell as administrator and run the command as shown in the figure below:

Run the PoweerShell script from the location where the file is saved. Ex: ” Desktop>.\Download-SP2016PreReqFiles.ps1 ”

runscript

 

Note: Before running the script, create a folder inside C:\ or any desired folder where you want to download the prerequisites file, once the download is completed you will see all of the files in the folder you have given. (here C:\Pre is the folder name)

download complete_prereq

The above picture shows successful completion of the prerequisites and all components downloaded into the given folder.

Note: The script does not include 2 components, they are: Microsoft WCF Data Services 5.6 and Cumulative Update Package 7 for Microsoft AppFabric1.1 Windows Server (KB3092423), which can be downloaded from the trusted Microsoft locations https://www.microsoft.com/en-in/download/details.aspx?id=39373 and https://www.microsoft.com/en-us/download/details.aspx?id=49171 respectively.

  • Download and keep all of the components in a single folder and let’s begin with the installation of the components individually.
  • Except for Windows AppFabric and its patch, all the components can be manually installed by double tapping on those applications. To install Windows AppFabric and patch, we need to run a command which will be covered below.
  • Let’s begin first by installing the MicrosoftIdentityExtensions-64 as shown below.

Microsoft identity applications

  • After Microsoft Identity Extensions installation, install the Microsoft Sync framework Runtime.

Sync framework runtime install

  • Now install the third component i.e MSIPC (Active Directory Rights Management Services)

MSIPC install

  • Reboot the Win2k12 R2 server after all of the components are installed.
  • Let’s install the forth component i.e Windows Server AppFabric using the PowerShell script as given below.
.\WindowsServerAppFabricSetup_x64.exe /i CacheClient","CachingService","CachingAdmin /gac

windowsserverAppfabricAfter installation, restart the Win2k12 R2 server.

  • After restarting the server, install the AppFabric update7 patch by double clicking on the application as shown below. Before installing the AppFabric application –>Right click–>Unblock the file. This is a mandatory step which needs to be done before installing a file which is downloaded from outside.

Appfabric patch update7

  • Now again restart the Win2k12 R2 server.
  • After reboot now install WCF data services by double clicking on the application directly. Before installing the WCF application –>Right click–>Unblock the file. This is a mandatory step which needs to be done before installing a file which is downloaded from outside.

WCF data services

  • After installing the components, restart the Windows2k12 R2 server and again run the Setup to confirm if all the prerequisites are met. If the screen appears as below then all the prerequisites are met.

Valid Produck Key

Note: Most of the prerequisites like sqlncli and .NET framework 4.6 will be installed when Windows update is performed, hence update is a necessary step which takes care of most of the prerequisites.

  • Enter a valid Product key and then accept the license terms. Accept and click on Continue–>Install.
  • Installation of Microsoft SharePoint Server 2016 will take 10 -15 minutes.

SharePoint2016 installation progress

  • After the installation is successful, click on Finish and a configuration wizard appears as below.

Welcome to sp config

  • Read the information and click on Next, then select Create new server farm from the next window, Click Next.
  • Specify the configuration Database settings as shown below by providing the server ip address (Database server), Database name of your choice and then username and password for database login. Then click Next.

Sharepoint config wizard

  • Once the port is configured, specify a server role, here we use Single-Server Farm, then click Next.

Sharepoint config

  • Specify the port for the web application and configure security settings as NTLM or Kerberos for authentication and then Next.

ConfigureSP central admin web app

  • Verify the configuration and click Next.

Completing the Configuration settings

    • Click on Next after verifying and the configuration will begin which will take around 10-15 minutes to finish.

Configuring

Note: Troubleshooting: If the configuration fails with the following failure message as shown below, then while installing WCF data services and AppFabric you have not unblocked the files. Now unblock both the files and reinstall them. Restart the Win2k12 R2 server and begin the configuration again.

Config failed-troubleshooting

  • Once the configuration is successful, Click on Finish as shown below. After which a window appears in the browser which asks for authentication. Enter the username and password provided as authentication for database and Click OK.

authentication

  • After successful authentication, a Welcome screen appears as shown below.

Sharepoint site welcome screen

  • Start the Wizard and select “use existing managed account” and click Next. After clicking on next this will take a while to set it up. (10-15 mins)

Use existing account

  • Finally a Create Site Collection screen appears in which you can create your desired site. Then click OK.

Sitecreation window

  • This step successfully completes the Farm configuration. SharePoint 2016 installation and configuration is completed click Finish.

Finish

This is the final step for the SharePoint 2016 server setup. These steps are tested on a virtual machine environment with 100% success rate more than 10 times. So there is a maximum chance for the above provided steps to work on your environment. Also some of the troubleshooting steps are mentioned in the article which will help you to handle the problem.

Feel free to post any comments on this or if you get stuck between any steps.

You can take the following MVA courses if you are stocked at any time.

https://mva.microsoft.com/en-US/training-courses/initial-implementation-of-sharepoint-server-10342?l=zofRht16_505095253

https://mva.microsoft.com/en-US/training-courses/developing-sharepoint-server-core-solutions-jump-start-8262?l=bSwfjnKy_8204984382

https://mva.microsoft.com/en-US/training-courses/developing-sharepoint-server-advanced-solutions-jump-start-8238?l=D2NU8mJy_9804984382

https://mva.microsoft.com/en-US/training-courses/plan-and-configure-user-access-for-sharepoint-2013-11323?l=7XG3wN5CB_9105095253

https://mva.microsoft.com/en-US/training-courses/deep-dive-building-blocks-and-services-of-sharepoint-8933?l=H1H3ZFC3_2704984382

Reference links:

https://technet.microsoft.com/en-us/library/cc262485%28v=office.16%29.aspx#section4

https://technet.microsoft.com/en-IN/library/cc262957.aspx

For High Availability you may consider looking at the below picture for system reference

https://www.sharepointeurope.com/media/387321/a_high_availability_architecture_550x343.jpg

This poster describes the SharePoint Online, Microsoft Azure, and SharePoint on-premises configurations that business decision makers and solutions architects need to know about.

Item Description
SharePoint Online, Azure, and SharePoint on-prem configurations

PDF file PDF  |  Visio file Visio

This poster describes four architectural models:

  • SharePoint Online (SaaS) – Consume SharePoint through a Software as a Service (SaaS) subscription model.
  • SharePoint Hybrid – Move your SharePoint sites and apps to the cloud at your own pace.
  • SharePoint in Azure (IaaS) – You extend your on-premises environment into Microsoft Azure and deploy SharePoint 2016 Servers there. (This is recommended for High Availability/Disaster Recovery and dev/test environments.)
  • SharePoint On-premises – You plan, deploy, maintain and customize your SharePoint environment in a datacenter that you maintain.

This poster shows the recommended MinRole topologies in a SharePoint on-premises environment.

Item Description
Click to view and download this poster about SharePoint Server MinRole topologies.

PDF file PDF  |  Visio file Visio

This poster shows the different recommended MinRole topologies that can be deployed in a SharePoint Server 2016 environment. It also shows the associated services that are provisioned with each role type.

This poster shows the databases that support SharePoint Server 2016.

Item Description
This is a thumbnail fo the SharePoint Server 2016 databases poster.

PDF file PDF  |  Visio file Visio

This poster is a quick reference guide to the databases that support SharePoint Server 2016. Each database has the following details:

  • Size
  • Scaling guidance
  • I/O patterns
  • Requirements

The first page contains the SharePoint system databases and the service applications that have multiple databases.

The second page shows all of the service applications that have single databases.

For more information about the SharePoint Server 2016 databases, see Database types and descriptions in SharePoint Server 2016

These posters describe search architectures in SharePoint Server 2016.

Item Description
Search Architectures for SharePoint Server 2016

Poster with an overview of the search components and search databases, how they interact, and an example of a search architecture built of these components and databases.

PDF file PDF  |  Visio file Visio

This poster gives an overview of the search architecture in SharePoint Server 2016. It describes the search components and databases in the search architecture and how these interact. It also shows an example of a medium-sized search farm.
Enterprise Search Architectures for SharePoint Server 2016

Poster describing the search components and databases, three model architectures for enterprise search, hardware requirements and scaling considerations.

PDF file PDF  |  Visio file Visio

This poster gives an overview of enterprise search architecture in SharePoint Server 2016. It shows sample search architectures for small, medium, and large-sized enterprise search farms. It also gives scaling considerations and hardware requirements.
Internet Sites Search Architectures for SharePoint Server 2016

Poster describing the search components and databases, a model architecture for Internet sites search, hardware requirements, scaling considerations, and performance considerations.

PDF file PDF  |  Visio file Visio

This poster gives an overview of the search architecture for Internet sites in SharePoint Server 2016. It shows a sample search architecture for a medium-sized search farm. It also gives performance considerations and hardware requirements.