Deploy Microsoft Office as a service

Objective

During this lab, you will prepare for, deploy, and manage a Microsoft^® Office 365™ ProPlus deployment.

Estimated time to complete: 90 minutes

Before You Begin

To complete this lab, you need to have already signed up for a Microsoft Office 365 Enterprise E3 or E5 trial tenant. The hosted labs environment should have provided this tenant to you.

If necessary, you can sign up for a free trial tenant at one of the following URLs:

https://products.office.com/en-us/business/office-365-enterprise-e3-business-software

https://products.office.com/en-us/business/office-365-enterprise-e5-business-software

What You Will Learn

After completing the exercises, you will be able to:

• Use the Telemetry Dashboard to set up the telemetry components.

• Configure the Telemetry Agent via Group Policy.

• Verify that previous Office clients are providing data via the Telemetry Dashboard.

• Download the Office 365 ProPlus Click-to-Run source files.

Provision a new Office 365 user.

Scenario

You are an IT pro preparing to pilot Office 365 ProPlus. You need to understand the files and Office solutions that are actively used, and determine an appropriate pilot user group for the pilot deployment. Then you need to deploy Office 365 ProPlus.

You will use Office 365 pilot data to simulate a deployment that has been in place for a few weeks. You now need to familiarize yourself with the Telemetry Log and Dashboard so that you can report on the status of the pilot deployment. In addition, you will need to determine whether there are any blocking issues or solutions that should be addressed within the environment.

Virtual Machines

1. CLIENT01
2. CLIENT02
3. DC01

Exercise 1: Deploying and Configuring Office Telemetry Components

In this exercise, you have installed Office 365 ProPlus on a workstation computer and you will use the new Office Telemetry tools to configure and deploy the Telemetry Database. The database will be used to gather data from a computer running an earlier version of Office to help determine which documents and solutions are most used in the current environment. This data will help you determine what is critical and what needs to be tested as your company starts deploying Office　365 ProPlus. You will distribute and configure the Telemetry Agent to targeted clients that have Office 2010 installed. The Telemetry Agent will collect Office file and solution usage from clients running earlier versions of Office.

You must already have an Office 365 E3 or E5 tenant in order to complete this lab. One should be provided as part of this online lab.

1. Switch to CLIENT01
   Switch to CLIENT01.
2. Sign in as Contoso\Administrator
   Sign in to CLIENT01 as Contoso\Administrator with a password of Pa$$w0rd.
3. Open the Command Prompt (Admin)
   Right click Start and then click Command Prompt (Admin).
   You may see a Command Prompt window open. Do not close this window. It is running a script to set up data for later exercises in this lab.
4. Change directory to the MS Office 16 folder
   At the command prompt, type the following, and then press Enter:
   CD C:\Program Files (x86)\Microsoft Office\Office16
   To save time, you can use the Type Text [A] icon whenever it is available to automatically type text or Windows PowerShell commands instead of typing them manually. The Type Text feature is located to the left of the Done button in the task view screen. Always review the typed text before continuing or pressing Enter.

   CD C:\Program Files (x86)\Microsoft Office\Office16

5. Rearm Microsoft Office 2016
   At the command prompt, type the following and then press Enter:
   OSPPREARM.exe
6. Close the Command Prompt
   Wait for Office 2016 to rearm and then close the Command Prompt window.
7. Open the Telemetry Dashboard for Office 2016
   Click Start and, on the Start menu, click the Telemetry Dashboard for Office 2016 tile.
   The tile is located in the third tile group.
8. Close the Activate Office window
   Close the Activate Office window.
9. Click Let’s get started
   On the left navigation menu, click Let’s get started.
   If the links in the spreadsheet do not work properly, you may need to rearm Microsoft Office again.
   1. Close Excel.
   2. Perform the steps outlined earlier in this lab to open an elevated command prompt and run OSPPREAM.exe.
   3. Open the Telemetry Dashboard and retry this step.
10. Click step 1 Set up prerequisites
    Click step 1 Set up prerequisites.
11. Review the prerequisite information
    Review the prerequisite information. You will use Microsoft SQL Server® 2012 which is already installed on CLIENT01.
    Click Set up prerequisites to collapse step 1.
12. Click step 2 Install Telemetry Processor
    Click step 2 Install Telemetry Processor.
13. Click Save the x64 Telemetry Processor MSI
    Click Save the x64 Telemetry Processor MSI.
14. Save the Office Telemetry Processor installer
    In the Save Office Telemetry Processor installer package window, browse to C:\LabFiles, and then click Save.
    The Telemetry Processor architecture corresponds to the client or server operating system architecture, not the Office architecture on the client.
15. In File Explorer, browse to C:\LabFiles
    In the taskbar, click File Explorer and then browse to C:\LabFiles.
16. Verify that the Telemetry folder is present
    In C:\LabFiles verify that the folder named Telemetry is present.
    This folder was created during the development of this lab.
    This folder will be used later as the sharing location for the telemetry data that will be collected.
17. Double-click osmdp64.msi
    In File Explorer, in C:\LabFiles, double-click osmdp64.msi.
18. On the Welcome Page, click Next
    In the Microsoft Office Telemetry Processor (x64) Setup, on the Welcome page, click Next.
19. In the UAC dialog box, click Yes
    In the User Account Control dialog box, click Yes.
20. Click Finish
    On the Completed the Microsoft Office Telemetry Processor (x64) Setup Wizard page, verify that the Run the Office Telemetry Processor settings wizard now check box is selected, and then click Finish.
21. In the UAC dialog box, click Yes
    In the User Account Control dialog box, click Yes
22. On the Getting Started page, click Next
    In the Office Telemetry Processor settings wizard, on the Getting Started page, review the configurations that will be performed using the wizard, and then click Next.
    You may need to click the Office Telemetry Processor settings wizard in the taskbar if it is not visible.
23. Connect to the local SQL server
    On the Database Settings page, click the SQL Server menu, click (local), and then click Connect.
24. Type ‘Dashboard’, then click Create
    In the SQL database box, type Dashboard and then click Create.
    Wait for the database to be created.

    Dashboard

25. Click Next
    Click Next.
26. Click Yes
    In the Office Telemetry Processor settings wizard dialog box, click Yes.
27. Type ‘C:\LabFiles\Telemetry’ and click Next
    On the Shared Folder page, in the Path box, type C:\LabFiles\Telemetry, and then click Next.
    This will create the \\CLIENT01\Telemetry share.

    C:\LabFiles\Telemetry

28. Click Yes
    In the Office Telemetry Processor settings wizard dialog box, read the information provided for sharing permissions, and then click Yes.
29. Click Next
    On the Microsoft Customer Experience Improvement Program page, click Next.
30. Click Finish
    On the Configuration Successful page, click Finish.
31. Close File Explorer
    Close File Explorer.
32. Click step 3 Deploy Telemetry Agent
    In the Telemetry Dashboard, click step 3 Deploy Telemetry Agent.
33. Click Save the x64 Telemetry Agent MSI
    Read the step 3 information and then click Save the x64 Telemetry Agent MSI.
34. Browse to C:\LabFiles and click Save
    In the Save Office Telemetry Agent installer package window, browse to C:\LabFiles, and then click Save.
35. Switch to CLIENT02
    Switch to CLIENT02
36. Sign in as Contoso\Administrator
    If necessary, sign in as Contoso\Administrator with a password of Pa$$w0rd.
37. Right-click Start and then click Run
    Right-click Start and then click Run.
38. Type ‘\\CLIENT01\C$\LabFiles’ and click OK
    In the Open box, type \\CLIENT01\C$\LabFiles and then click OK.

    \\CLIENT01\C$\LabFiles

39. In File Explorer, double-click osmia64.msi
    In File Explorer, double-click osmia64.msi.
40. In the UAC dialog box, click Yes
    In the User Account Control dialog box, click Yes.
    The installer window will close automatically.
    The Office Telemetry Agent is built into Office Professional 2016 and Office 365 ProPlus. The agent can be delivered silently to client computers using standard software distribution options, such as Microsoft System Center or deployment scripts. The agent does not take action until configured with Group Policy settings or direct configuration updates.
41. Close File Explorer
    Close File Explorer.
42. Switch to CLIENT01
    Switch to CLIENT01 and the Telemetry Dashboard.
43. Click step 4 Configure Telemetry Agent
    Click step 4 Configure Telemetry Agent.
44. Review the information
    Review information for configuring the Telemetry Agent. The administrative templates package has already been downloaded to C:\LabFiles\AdminTemplates.
45. Switch to DC01
    Switch to DC01
46. Sign in as Contoso\Administrator
    In the top navigation of the hosted lab UI, click Commands and then click Ctrl+Alt+Delete.
    Sign in as Contoso\Administrator with a password of Pa$$w0rd.
47. Right-click Start then click Run
    On DC01, right-click Start and then click Run.
48. Open AdminTemplates
    In the Open box, type \\CLIENT01\C$\LabFiles\AdminTemplates and then click OK.
49. Double-click admintemplates_x64_4297-1000_en-us
    In File Explorer, double-click admintemplates_x64_4297-1000_en-us.exe.
50. Accept the Microsoft Software License Terms
    In the Microsoft Office 2016 Administrative Templates window, read the license terms. Select the Click here to accept the Microsoft Software License Terms check box, and then click Continue.
51. Browse for LabFiles
    In the Browse For Folder window, expand This PC, expand Local Disk (C:), click LabFiles, and then click OK.
52. Click OK
    In the Files extracted successfully dialog box, click OK.
53. In File Explorer, browse to C:\LabFiles\admx
    In File Explorer, browse to C:\LabFiles\admx.
54. Copy the files in the admx. folder
    Press Ctrl+A to select all files in the folder and then press Ctrl+C to copy all files.
55. Paste files into the PolicyDefinitions folder
    Browse to C:\Windows\PolicyDefinitions, and then press Ctrl+V to paste the copied files into the PolicyDefinitions folder.
56. Close File Explorer
    Close File Explorer.
57. Right-click Start, and then click Run
    Right-click Start, and then click Run.
58. Type gpmc.msc then click OK
    In the Open box, type gpmc.msc and then click OK.

    gpmc.msc

59. Click the Accounts node
    In the console tree, expand Forest: Contoso.local, expand Domains, expand contoso.local, and then click Accounts. 
    Accounts is a custom organizational unit (OU) created for user accounts in this lab.
60. Create and link a GPO in the Accounts OU
    Right-click Accounts and then click Create a GPO in this domain, and Link it here…
61. Type a GPO name and then click OK
    In the New GPO dialog box, in the Name box, type Office 2016 Telemetry Agent Settings and then click OK.

    Office 2016 Telemetry Agent Settings

62. Click Office 2016 Telemetry Agent Settings
    In the console tree, expand Accounts, and then click Office 2016 Telemetry Agent Settings.
63. Click OK
    In the Group Policy Management Console dialog box, click OK.
64. Edit the Office 2016 Telemetry Agent Settings
    Right-click Office 2016 Telemetry Agent Settings and then click Edit.
65. Browse to Telemetry Dashboard
    In the Group Policy Management Editor window, in the console tree under User Configuration, expand Policies, expand Administrative Templates, expand Microsoft Office 2016, and then click Telemetry Dashboard.
66. Edit the telemetry data collection
    In the results pane, right-click Turn on telemetry data collection and then click Edit.
67. Click Enable and then click OK
    In the Turn on telemetry data collection window, click Enabled and then click OK.
68. Edit the Turn on data uploading for Office…
    In the results pane, right-click Turn on data uploading for Office Telemetry Agent and then click Edit.
69. Click Enable and then click OK
    In the Turn on data uploading for Office Telemetry Agent window click Enabled and then click OK.
70. Edit the Specify the UNC path to store...
    In the results pane, right-click Specify the UNC path to store Office telemetry data and click Edit.
71. Click Enable
    In the Specify the UNC path to store Office telemetry data window, click Enabled.
72. Type ‘\\CLIENT01\Telemetry’ and click OK
    In the UNC path to store Office telemetry data box, type \\CLIENT01\Telemetry and then click OK.

    \\CLIENT01\Telemetry

73. Edit the Specify custom tags for Office telemetry
    In the results pane, right-click Specify custom tags for Office telemetry data and then click Edit.
74. Click Enable
    In the Specify custom tags for Office telemetry data window, click Enabled.
75. In the Tag 1 box, type 'Pilot' and then click OK
    In the Tag 1 box, type Pilot and then click OK.

    Pilot

76. Close the Group Policy Management Editor window
    Close the Group Policy Management Editor window.
77. Close the Group Policy Management Console
    Close the Group Policy Management Console.
78. Switch to CLIENT02
    Switch to CLIENT02.
79. Run gpupdate /force
    Right-click Start and then click Run.
    In the Open box, type gpupdate /force and then press Enter.
    Wait for the Group Policy update to complete.

    gpupdate /force

80. Sign out of Administrator
    Click Start, click Administrator, and then click Sign out.
81. Click the lock screen and click Other user
    Click the lock screen and then click Other user.
82. Sign in as Alex
    Sign in as Alex with a password of Pa$$w0rd.
83. Right-click Start and click Run
    Right-click Start and then click Run.
84. Type regedit and then press Enter
    Type regedit and then press Enter.

    regedit

85. Click Yes
    In the User Account Control dialog box, click Yes.
86. Browse to osm reg key
    In the console tree, expand HKEY_CURRENT_USER, expand SOFTWARE, expand Policies, expand Microsoft, expand office, expand 16.0, and then click osm.
    Review the registry information created by Group Policy.
87. Create new DWORD (32-bit) Value
    In the console tree, Right-click osm, point to New, and then click DWORD (32-bit) Value.
88. Type 'AgentInitWait' and press Enter
    In the New Value #1 box, type AgentInitWait, and then press Enter.

    AgentInitWait

89. Create new DWORD (32-bit) Value
    In the navigation pane, right-click osm, point to New, and then click DWORD (32-bit) Value.
90. Type 'AgentRandomDelay' and press Enter
    In the New Value #1 box, type AgentRandomDelay, and then press Enter.
    The registry settings will expedite telemetry processing in the lab environment by eliminating any delay in data collection. These settings should not be implemented in a production environment.
    AgentRandomDelay: To avoid affecting network or client performance, decrease this value in test environments only. This setting adjusts the maximum random delay, in minutes. The agent randomly waits between 0 and AgentRandomDelay minutes, in addition to the AgentInitWait value, before it starts to scan or upload telemetry data. If the AgentRandomDelay key does not exist, the agent waits between 0 minutes to 240 minutes. In test environments, you can specify 0 to remove the random delay for testing. Value: x = Random delay in minutes

    AgentRandomDelay

91. In the results pane double-click AgentInitWait
    In the results pane, double-click AgentInitWait.
92. In the Value data box, type 1 and click OK
    In the Edit DWORD (32-bit) Value window, in the Value data box, type 1, and then click OK. 
    AgentInitWait: To avoid affecting network or client performance, decrease this value in test environments only. This setting adjusts the time that the agent waits before it scans a client and uploads data to the telemetry shared folder. If this key does not exist, the default wait time is 10 minutes (600 seconds). In test environments, you can specify 1 second to remove the delay for testing Windows 7 and earlier clients. We recommend setting this to at least 60 seconds for computers running Windows 10. Value: x = Wait time in seconds
93. Close the Registry Editor window
    Close the Registry Editor window.
94. Sign out of Alex Darrow
    Click Start, click Alex Darrow, and then click Sign out.
95. Sign in as Alex Darrow
    Sign in as Alex with a password of Pa$$w0rd.
96. Open File Explorer and browse to C:\LabFiles
    Open File Explorer and browse to C:\LabFiles.
97. Open Northwind Acquisition Outline.pptx
    Double-click Northwind Acquisition Outline.pptx.
98. Cancel the Office Activation wizard
    In the Office Activation wizard, click Cancel.
99. Open Northwind Acquisition Proposal.docx
    Switch to File Explorer and double-click Northwind Acquisition Proposal.docx.
100. Open Northwind Financials.xlsx
     Switch to File Explorer and double-click Northwind Financials.xlsx.
     The documents are being opened to create Telemetry Agent data.
101. Browse to the Telemetry folder
     Switch to File Explorer, and browse to C:\Users\Alex\AppData\Local\Microsoft\Office\16.0\Telemetry.
     This folder contains the telemetry data files that are added to the telemetry database. The AppData folder is hidden by default.
102. Close File Explorer and all open documents
     Close File Explorer and all open documents.
103. Click Start
     Click Start.
104. In the search box, type Task Scheduler
     In the I’m Cortana. Ask me anything box, type Task Scheduler.
105. Click Task Scheduler
     In the search results, click Task Scheduler.
106. In the console tree browse to Office
     In the console tree, expand Task Scheduler Library, expand Microsoft, and then click Office.
107. Run the Task
     In the results pane, right-click OfficeTelemetryAgentLogOn2016, and then click Run.
     You may need to expand the Name column to see the task names.
108. Run the scheduled task again
     Run the scheduled task again to ensure the data has been collected.
     This is done for lab purposes only. The task may take a few minutes to complete.
109. Close the Task Scheduler
     Close Task Scheduler.
110. Switch to CLIENT01
     Switch to CLIENT01 signed in as Contoso\Administrator.
111. On the desktop, click Start
     On the desktop, click Start.
112. Click Administrator then click Switch account
     On the Start screen, click Administrator, and then click Switch account.
113. Click Other user
     Click Other user.
114. Sign in as Robin
     Sign in as Robin with a password of Pa$$w0rd.
115. Right-click Start, and click Run
     Right-click Start and then and click Run.
116. Type regedit and click OK
     In the Open box, type regedit, and then click OK.

     regedit

117. In the UAC dialog box, click Yes
     In the User Account Control dialog box, click Yes.
118. Browse to osm reg key
     In the console tree, expand HKEY_CURRENT_USER, expand SOFTWARE, expand Policies, expand Microsoft, expand office, expand 16.0, and then click osm.
119. Right-click osm and click DWORD (32-bit) Value
     In the console tree, right-click osm, point to New, and then click DWORD (32-bit) Value.
120. Type 'AgentInitWait' and press Enter
     In the New Value #1 box, type AgentInitWait, and then press Enter.

     AgentInitWait

121. Right-click osm and click DWORD (32-bit) Value
     In the navigation pane, right-click osm, point to New, and then click DWORD (32-bit) Value.
122. Type 'AgentRandomDelay' and press Enter
     In the New Value #1 box, type AgentRandomDelay and then press Enter.

     AgentRandomDelay

123. Double-click AgentInitWait
     In the results pane, double-click AgentInitWait.
124. In the Value data box, type 1 and click OK
     In the Edit DWORD (32-bit) Value window, in the Value data box, type 1, and then click OK.
125. Close the Registry Editor window
     Close the Registry Editor window.
126. Click Start
     Click Start.
127. Sign out of Robin Counts
     On the Start screen, click Robin Counts, and then click Sign out.
128. Click the lock screen
     Click the lock screen.
129. Sign in as Robin
     Sign in as Robin with a password of Pa$$w0rd.
130. Open File Explorer and browse to C:\LabFiles
     Open File Explorer and browse to C:\LabFiles.
131. Open Acquisition Strategy.doc
     In C:\LabFiles, double-click Acquisition Strategy.doc.
     Close the Activate Office window.
     In the First things first dialog box, click Accept.
     The open document will populate the telemetry data, which will be uploaded to the telemetry database.
132. Close the document and close File Explorer
     Close the open document and then close File Explorer.
133. Open the Task Scheduler
     Click Start, type Task Scheduler and then click Task Scheduler.
134. In the console tree, browse to Office
     In the console tree, expand Task Scheduler Library, expand Microsoft, and then click Office.
135. Run the OfficeTelemetryAgentLogOn2016
     In the results pane, right-click OfficeTelemetryAgentLogOn2016 and then click Run.
     You may need to expand the Name column to see the task names.
136. Run the OfficeTelemetryAgentLogOn2016 again
     Run the scheduled task again to ensure the data has been collected.
     This is done for lab purposes only.
     The Status should indicate that the task is Ready after clicking Refresh in the Actions pane. The task may take a few minutes to complete.
137. Close the Task Scheduler
     Close the Task Scheduler.
138. Sign out of Robin Counts
     Click Start, click Robin Counts, and then click Sign out.
139. Sign in as Contoso\Administrator
     Sign in as Contoso\Administrator with a password of Pa$$w0rd.
140. Click SQL Server Management Studio
     Click Start start and then click the SQL Server Management Studio tile.
     The SQL Server Management Studio tile is located in the third tile group.
141. Connect to CLIENT01
     In the Connect to Server dialog box, verify that CLIENT01 is listed in the Server Name box, and then click Connect.
142. In the Object Explorer pane, browse to Tables
     In the Object Explorer pane, expand Databases, expand Dashboard, and then expand Tables.
143. Select the top 1000 rows
     Right-click dbo.Computers and then click Select Top 1000 Rows.
144. Review the data selected from the table
     On the results tab, review the data selected from the table. Note the ComputerName column results.
     This task provides visibility into the data flow and collection. The actual review of the data will be provided by the Office Telemetry Dashboard.
145. Select the top 1000 rows
     In the navigation pane, right-click dbo.UsersOnComputers, and then click Select Top 1000 Rows.
146. Review the LastScanTime column
     In the results tab, scroll right, and review the LastScanTime column to verify the collected data was recently updated.
147. Close Microsoft SQL Server Management Studio
     Close Microsoft SQL Server Management Studio.
     Any user account that needs to use the Telemetry Dashboard needs to have the td_readonly role membership associated with their SQL login. A login can be created for an Active Directory® user account or group. All users who need to access the database with Telemetry Dashboard must be assigned to this role.
148. In the Telemetry Dashboard, click step 5
     In the Telemetry Dashboard, click step 5 Connect to the database to view telemetry data.
149. Click Connect to Database
     Click Connect to Database.
150. Verify the Data connection settings
     In the Data connection settings dialog box, in the SQL database box, verify that Dashboard is listed, and then click Connect.
151. On the dashboard menu, click Documents
     After the query is complete, on the dashboard menu, click Documents.
152. In the Total users column, click the 1 link
     Notice the documents reported. Next to Northwind Acquisition Outline.pptx, in the Total users column, click the 1 link.
     Review the information collected for the document that was opened.
153. On the dashboard menu, click Solutions
     On the dashboard menu, click Solutions.
154. Review the add-ins
     Review the add-ins that have been reported as installed. Scroll right to see which add-ins are built into the application.
155. Close Microsoft Excel
     Close Microsoft Excel.
156. Click Don’t Save
     In the Microsoft Excel dialog box, click Don’t Save. 

Exercise 2: Deploying Office 365 to a Pilot Computer

In this exercise, you will provision a pilot user in the Office 365 portal. This can be done through the Office 365 Admin Center or using the Microsoft Online Service Module for Windows PowerShell®.

Deploying Office Professional 2016 Click-to-Run (C2R) requires an active Office 365 account to sign in and use. Account provisioning is one the first things you do when you begin to pilot Office and the service. This functionality represents a significant difference compared to the traditional practices of downloading installation files and distributing them. Active user accounts provide the basis for receiving software and services for all of the devices a person uses. With Office 365 ProPlus, an administrator can still install on behalf of the organization's users, but the administrator cannot activate the product on their behalf. Office 365 ProPlus activation is linked to the user account, so the account needs to be provisioned and configured to access Office 365 ProPlus services for Office programs to remain in an activated state. The Microsoft Online Services Sign-In Assistant and the Windows Azure Active Directory Module for Windows PowerShell have been pre-installed on CLIENT01 for the purposes of this lab.

1. Open Windows PowerShell
   On CLIENT01, on the desktop, double-click Windows Azure Active Directory Module for Windows PowerShell.
2. Connect to Microsoft Online Services
   At the Windows PowerShell command prompt, type the following and then press Enter:
   Connect-MSOLService

   Connect-MSOLService

3. Sign in using your Office 365 admin credentials
   In the Enter Credentials dialog box, type your Office 365 administrator user name and password and then click OK.
4. Review the MSOL accounts
   At the Windows PowerShell command prompt, type the following and then press Enter:
   Get-MsolAccountSku | FL
   Note the available license AccountSkuId information for your domain.

   Get-MsolAccountSku | FL

5. Create an Office 365 user account
   At the Windows PowerShell command prompt, type the following and then press Enter:
   New-MsolUser -FirstName Alex -LastName Darrow -UserPrincipalName Alex@yourtenantdomain.onmicrosoft.com -DisplayName "Alex Darrow" -Password 'Pa$$w0rd' -ForceChangePassword $false -LicenseAssignment yourtenantdomainAccountSkuID -UsageLocation US
   If you use the Type Text feature to run the command in this step, be sure to edit the command with the correct tenant domain name and Account Sku ID.
   For example: New-MsolUser -FirstName Alex -LastName Darrow -UserPrincipalName Alex@contoso.onmicrosoft.com -Password 'Pa$$w0rd' -DisplayName “Alex Darrow” –ForceChangePassword $false -LicenseAssignment contoso:ENTERPRISEPREMIUM -UsageLocation US.

   New-MsolUser -FirstName Alex -LastName Darrow -UserPrincipalName Alex@yourtenantdomain.onmicrosoft.com -DisplayName "Alex Darrow" -Password 'Pa$$w0rd' -ForceChangePassword $false -LicenseAssignment yourtenantdomainAccountSkuID -UsageLocation US

6. Review the MSOL users
   At the Windows PowerShell command prompt, type the following and then press Enter:
   Get-MsolUser
   Verify that the new user was created.

   Get-MsolUser

7. Close Windows PowerShell
   Close the Windows Azure Active Directory Module for Windows PowerShell window.
8. Open the Command Prompt
   Right-click Start, and then click Command Prompt.
9. Browse to OfficeDeploymentTools
   At the command prompt, type the following and then press Enter:
   CD C:\LabFiles\OfficeDeploymentTools

   CD C:\LabFiles\OfficeDeploymentTools

10. Show commands
    At the command prompt, type the following and then press Enter:
    Setup.exe /?

    Setup.exe /?

11. Open File Explorer, browse to the Demo folder
    Open File Explorer, and then browse to C:\LabFiles\OfficeDeploymentTools\Demo.
12. Double-click Download.xml
    Double-click Download.xml.
13. Open the file in Notepad
    In the How do you want to open this type of file (.xml)? dialog box, click Notepad and click OK.
    When using the /download parameter with Setup.exe, the SourcePath attribute in the download.xml file specifies the location where the Office 365 ProPlus source files will be downloaded. When the version is specified, an administrator can download a specific version of the Office ProPlus source files. If the version is specified, the v32 or v64_version.cab files need to be renamed to v32.cab or v64.cab before deploying.
14. Close Notepad
    Close Notepad.
15. In C:\LabFiles, browse to Data
    In File Explorer, browse to C:\LabFiles\Office365ProPlus\Office\Data.
    Notice the files that have already been downloaded. 
    The downloaded Office 365 ProPlus installation files on this virtual machine were downloaded previously to save time during the lab. The version of Office 365 ProPlus is unlikely to be the most current release due to the dynamic nature of the subscription service. This will not cause the lab to fail.
16. Swtich to CLIENT02
    Switch to CLIENT02 signed in as Alex Darrow.
17. Right-click Start and then click Run
    Right-click Start and then click Run.
18. Type \\CLIENT01 and then click OK
    In the Open box, type \\CLIENT01 and then click OK.

    \\CLIENT01

19. Open the command window
    Press Shift+right-click OfficeDeploymentTools and then click Open command window here.
20. Change to the Demo directory
    At the command prompt, type the following and then press Enter:
    CD Demo
21. Open the Install.xml
    At the command prompt, type the following and then press Enter:
    Install.xml
22. Open the xml file with Microsoft Edge
    In the How do you want to open this file dialog box, click Microsoft Edge and then click OK.
23. Review the .xml elements
    Review the , , , and elements
    The SourcePath reflects the installation and client edition.
24. Close Microsoft Edge
    Close Microsoft Edge.
25. Change directory
    At the command prompt, type the following and press Enter:
    CD..

    CD..

26. Review the Setup.exe
    At the command prompt, type the following and press Enter:
    Setup.exe /?
    Notice the /configure parameter which is used to add, remove, or configure an Office 2016 installation. If not specified, http://officecdn.microsoft.com is used as the installation source.

    Setup.exe /?

27. Run Setup.exe using the install configuration
    At the command prompt, type the following and press Enter:
    Setup.exe /configure .\Demo\install.xml

    Setup.exe /configure .\Demo\install.xml

28. In the UAC dialog box, click Yes
    In the User Account Control dialog box, click Yes.
29. Open the Task Manager
    Right-click the Taskbar and then click Task Manager.
30. Click More details
    In Task Manager, click More details.
31. Find the OfficeClicktoRun processes
    Click the Details tab and then find the OfficeClicktoRun processes.
    Office Click-to-Run is the process that handles C2R streaming. The existence of this process is an indicator Office setup is streaming.
32. Close Task Manager
    Close Task Manager.
33. Click Start and then click All apps
    Click Start and then click All apps.
34. Click Word 2016
    As Office is streamed to the client computer, the applications will appear in the Start menu. Click Word 2016 when the tile becomes available.
    Any Microsoft Word 2016 features not currently available on the computer are streamed on demand.
35. In the Microsoft Word dialog box, click OK
    In the Microsoft Word dialog box, click OK.
    You may receive a temporary server issue dialog box or a prompt to restart Microsoft Word if the features needed are not yet installed. Restart Word. If you are still unable to start Word, wait until the installation has completed.
36. Type Alex’s email address and click Next
    In the Type your email address or phone number box, type Alex@yourtenantdomain.onmicrosoft.com and then click Next.
    Replace yourtenantdomain with your Office 365 tenant domain name.
37. In the Password box, type Pa$$w0rd
    In the Password box, type Pa$$w0rd.
    If you receive a Security Alert dialog box, click Yes.
    If the Sign in window does not display correctly, close the window and then close Word 2016. Open Word 2016 again.

    Pa$$w0rd

38. Click Sign in
    Click Sign in.
39. In the Account Updated dialog box, click OK
    In the Account Updated dialog box, click OK.
    The computer information for the local installation is now added to the account properties for this user in the Office 365 portal.
    If Office 365 ProPlus is not able to be activated, it may be that the user’s license is still being replicated in the Office 365 service. Close Word 2016 and wait 2-3 minutes and then retry activating Office 365 ProPlus.
    If you are unable to activate office using Alex’s credentials, you can use your Office 365 administrator credentials. If you use the administrator credentials, replace references to Alex in the following steps.
40. Close any messages and close Microsoft Word
    Close or accept any dialog boxes and then close Microsoft Word.
    Users will need to sign-in to Office 365 Pro Plus once per device. If Office 365 cloud IDs are used (for example, Username@orgname.onmicrosoft.com), users will have a separate ID from their domain user name to sign in to Office. Alternatively, organizations that sync their existing Active Directory user accounts to Office 365 to facilitate same sign in or utilize Active Directory Federation Services to establish single sign-on (SSO) can eliminate the need for end users to manage multiple user accounts. The scope of this lab will leverage cloud identities only. The cloud identity credentials are cached and the user will not be required to provide Office 365 credentials to use Office until the password is changed in the service or it expires.
41. Click Start and the click All apps
    Click Start and then click All apps.
42. Click All Excel 2016
    Click Excel 2016.
    Verify that Excel® 2016 does not prompt for user credentials.
    In the upper-right corner, notice that Alex is signed in using his Office 365 credentials.
43. In Excel 2016, click Blank workbook
    In Excel 2016, click Blank workbook.
44. Click File and then click Account
    Click File and then click Account.
45. Click Manage Account
    On the right side, under Product Information, click Manage Account.
    This is located below the Office product icons.
46. Sign in using Alex Darrow’s credentials
    Sign in as Alex@yourtenantdomain.onmicrosoft.com with a password of Pa$$w0rd.
47. Click Manage installs and review the information
    Under Install status, click Manage installs and then review the installation information.
    Expand CLIENT02 and review the additional information.
    You may need to refresh the browser page if it does not display properly.
48. Close Internet Explorer
    Close Internet Explorer.
49. Close Microsoft Excel
    Close Microsoft Excel.
50. In File Explorer, browse to C:\LabFiles
    Open File Explorer and then browse to C:\LabFiles.
51. Open the Northwind Acquisition Proposal.docx
    Double-click Northwind Acquisition Proposal.docx.
52. Click Start and then click All apps
    Click Start and then click All apps.
53. Open Microsoft Word 2010
    In the Start menu, scroll down, click Microsoft Office, then click Microsoft Word 2010.
    Close any activation prompts and accept license agreements. 
54. Click File and then click Open
    In Microsoft Word 2010, click File, and then click Open.
55. Open the Northwind Acquisition Proposal.docx
    In the Open window, browse to C:\LabFiles, click Northwind Acquisition Proposal.docx, and then click Open.
    When Microsoft Office 2016 is installed, the File Type Associations (FTAs) are rewritten to launch Office 2016 applications by default. The legacy Office 2010 applications can still be launched manually and used side-by-side with the Office 2016 suite.