Lab Answer Key: Module 1: Preparing for Office 365

Lab A: Setting up the Lucerne Publishing Datacenter

Environment

Exercise 1: Set Up and Configure the Lucerne Publishing Data

Center Environment

Task 1: Sign up for a Windows Live Account

1. Log on to LUC-CL1 with a user name of Student1 and a password of Pa$$w0rd.

2. In the Start screen, click Desktop.

3. On the desktop task bar, click Internet Explorer.

4. In the address bar, enter http://live.com and press ENTER.

5. Click Sign up now.

6. Under Name, enter your first and last name.

7. In User name, select a user name that is not currently in use.

8. Leave the domain name as outlook.com.

9. In Create password and Reenter password, enter a suitable 8-character or longer

password. Make a note of this password.

10. Under Country/Region, select your local region.

11. Enter any additional information, such as ZIP code or post code.

12. Enter a Birthdate.

13. Select your Gender.

14. Under Country code, select the country code for your mobile device.

15. In Phone number, enter the number of your mobile phone.

16. In Alternate email address, enter your existing email address.

17. Under Enter the characters you see, type in the letters and numbers displayed. Click
New for a different combination if required.

18. Click to deselect the Send me promotional offers from Microsoft, you can
unsubscribe at any time option.

19. Click Create account.

Task 2: Sign up for a Windows Azure trial

1. In Internet Explorer, click New Tab or press Ctrl+T.

2. In the address bar, type www.windowsazure.com and press ENTER.

3. Click Free Trial.

4. Click Try it now.

5. Sign in as your Windows Live account with the password you entered.

6. In About you, confirm that your details are correct.

7. Under Mobile verification, ensure that Send text message is selected, then select the
country you are in now and enter your own mobile phone number.

8. Click Send text message.

9. Check your mobile device for text messages and then type the code into the box to the
left of Verify code.

10. Click Verify code.

Note: Although a valid credit card is required, you will not be charged for the trial.

11. Under Payment Information, enter the details of your credit card.

12. Check the option for I agree to the Windows Azure Agreement, Offer Details, and
Privacy Statement.
13. Click Sign up.

14. Close the Windows Azure trial window.

15. You should now have confirmatory email messages in your new Windows Live account
about your Windows Azure free trial.

Task 3: Build the Lucerne Publishing Datacenter using Windows Azure

PowerShell.

1. On LUC-CL1, press the Windows key.

2. On the Start page, right-click Windows Azure PowerShell, and then click Run as
administrator.

3. At the User Account Control dialog box, click Yes.

4. At the Windows Azure PowerShell prompt, type the following command, and press
ENTER:

CD E:\Setupfiles

5. At the Windows Azure PowerShell prompt, type the following command, and press
ENTER:

Set-ExecutionPolicy Unrestricted

6. Press ENTER to confirm the execution policy change.

7. At the Windows Azure PowerShell prompt, type the following command, and press
ENTER:

Import-Module Azure

8. At the Windows Azure PowerShell prompt, type the following command, and press
ENTER:

Get-AzurePublishSettingsFile

9. In Internet Explorer, sign in with the Live ID associated with your Azure Trial; this
should be [email protected], (where [email protected] is the email
 address you used to sign up for the Office 365 trial in Module 1, Lab A, Exercise 1,
Detailed Steps 7 and 8).

10. At the Internet Explorer save file dialog box, click the Save drop-down, and then click
Save as.

11. Note the name of your publish settings file:

____________________

12. In the Save As dialog box, navigate to E:\Setupfiles, and click Save.

13. Switch to the Windows Azure PowerShell prompt, type the following command, and
press ENTER:

Import-AzurePublishSettingsFile -PublishSettingsFile "E:\Setupfiles\name of your

downloaded file"

14. At the Windows Azure PowerShell prompt, type the following command, and press
ENTER:

Get-AzureLocation

15. Make a note of a location that provides both the Storage and PersistentVMRole services;
your Instructor may suggest an appropriate location for your classroom.

Location: _________________________

16. To run the first provisioning script, at the Windows Azure PowerShell prompt, type the
following command, and press ENTER:

. .\BuildStorageAndNetwork.ps1

Important: The command starts with dot space dot backslash.

17. When prompted, enter a number corresponding to the Windows Azure datacenter
location to use, and press ENTER.

18. When prompted, enter the 5 digit number for your Learning Center, and press ENTER.
Your instructor will inform you of this number.
19. When prompted, enter your 2 digit student number, and press ENTER. Your instructor
will inform you of this number.

20. Make a note of your "unique suffix" from the Window Azure prompt, as you will need
this in later in this lab:

____________________

21. The script will take several minutes to complete; if you get red script errors, you can stop
the script execution by pressing Ctrl + C, and then refer to the Build Environment
Recovery Steps section at the end of this lab.

22. When the script has completed, verify that the following information is displayed:

Label: lucstorage<suffix>(where suffix is the "unique suffix" number you recorded in

step 20 above)

AffinityGroup: LUC-AFFINITYGROUP

Name: LUC-VIRTUALNETWORK

DnsServers: {LUC-DNS}

Subnets: {Subnet-1}

Your current subscription must match the Azure subscription type that you are using.

If your display does not include the above information, you will need to remove Azure
objects, and then rerun the BuildStorageAndNetwork.ps1 script; refer to the Build
Environment Recovery Steps section at the end of this lab for detailed steps.

Important: Do not proceed to the next step until BuildStorageAndNetwork.ps1

has successfully completed.

23. To run the next provisioning script, at the Windows Azure PowerShell prompt, type the
following command, and press ENTER:

. .\BuildDC.ps1

24.
 If you get any red script errors, stop the script execution by pressing Ctrl + C, and then
refer to the Build Environment Recovery Steps section at the end of this lab.

25. The script will take 15-30 minutes to complete; when the script has completed, verify
that the following information is displayed:

ServiceName: LUC-CLOUD-<suffix>(where suffix is the "unique suffix" number

you recorded in step 20 above)

Name: LUC-DC1

IPAddress: 10.0.0.4

InstanceStatus: ReadyRole

PowerState: Started

If your display does not include the above information, you will need to remove Azure
objects, and then rerun the BuildDC.ps1 script; refer to the Build Environment Recovery
Steps section at the end of this lab for detailed steps.

Important: Do not proceed to the next step until BuildDC.ps1 has successfully
completed.

26. On LUC-CL1, on the Taskbar, click File Explorer.

27. Navigate to E:\RDP_files, and verify that LUC-DC1.rdp exists.

28. Double-click LUC-DC1.rdp.

29. If a Remote Desktop Connection warning message appears, click Dont ask me again
for connections to this computer and click Connect.

30. Connect as LUCERNE\LucAdmin, password: Pa$$w0rd.

31. If another Remote Desktop Message appears, click Dont ask me again for connections
to this computer and click Yes.

32. On LUC-DC1, in Server Manager, click Tools and then click Active Directory Users
and Computers.
33. In the Lucerne Publishing domain, verify that there are empty Accounts and Sales
OUs.

34. Minimize the RDP session.

If you cannot connect to LUC-DC1 using RDP, or Active Directory has not been
properly configured, you will need to remove the Azure virtual machine, and then rerun
the BuildDC.ps1 script; refer to the Build Environment Recovery Steps section at the end
of this lab for detailed steps.

Important: Do not proceed to the next step until you have a properly configured
LUC-DC1 Azure virtual machine.

35. To run the next provisioning script, at the Windows Azure PowerShell prompt, type the
following command, and press ENTER:

. .\BuildExchangeServer.ps1

36. If you get any red script errors, stop the script execution by pressing Ctrl + C, and then
refer to the Build Environment Recovery Steps section at the end of this lab.

37. The script will take 30-40 minutes to complete; when the script has completed, verify
that the following information is displayed:

ServiceName: LUC-CLOUD-<suffix>(where suffix is the "unique suffix" number

you recorded in step 20 above)

Name: LUC-EX1

IpAddress: 10.0.0.5

InstanceStatus: ReadyRole

PowerState: Started

If your display does not include the above information, you will need to remove Azure
objects, and then rerun the BuildExchangeServer.ps1 script; refer to the Build
Environment Recovery Steps section at the end of this lab for detailed steps.
 Important: Do not proceed to the next step until BuildExchangeServer.ps1 has
successfully completed.

38. On LUC-CL1, switch to the LUC-DC1 RDP session.

39. On LUC-DC1, in Active Directory Users and Computers, in the Lucerne Publishing
domain, verify that the Computers OU contains the LUC-EX1 computer.

40. Minimize the LUC-DC1 RDP session.

41. On LUC-CL1, switch to File Explorer.

42. In E:\RDP_files, verify that LUC-EX1.rdp exists.

43. Double-click LUC-EX1.rdp.

44. If a Remote Desktop Connection warning message appears, click Dont ask me again
for connections to this computer and click Connect.

45. Connect as LUCERNE\LucAdmin, password: Pa$$w0rd.

46. If another Remote Desktop Message appears, click Dont ask me again for connections
to this computer and click Yes; verify that this machine starts in Desktop Experience
mode.

47. On the Windows Start screen, click File Explorer, and verify that there is a 50 GB F:
drive (ExDB), and a 10GB G: drive (ExLogs).

48. In File Explorer, verify that that C:\Temp contains ExchangeUserNames.csv,

SetupExchange.ps1, and Variables.ps1, as well as the executables used to install Filter
Pack and UCMA Exchange pre-requisites.

49. Press the Windows key to go to the Start screen.

50. Open Control Panel, then click Programs, and then click Programs and Features, and
verify that the following Exchange pre-requisite software are installed:

Microsoft Filter Pack 2.0

Microsoft Lync Server 2013, Bootstrapper Prerequisites Installer Package

Microsoft Server Speech Platform Runtime (x64)

 Microsoft Server Speech Recognition Language TELE (en-US)

Microsoft Server Speech Text to Speech Voice (en-US, Helen)

Microsoft Speech Platform VXML Runtime (x64)

Microsoft Unified Communications Managed API 4.0, Runtime

Microsoft Visual C++ 2012 Redistributable (x64) 11.0.50727

51. Minimize the LUC-EX1 RDP session.

If LUC-EX1 has not been joined to the domain, or you cannot connect to LUC-EX1
using RDP, or the file system has not been properly configured, or the Exchange pre-
requisites have not been installed, you will need to remove the Azure virtual machine,
and then rerun the BuildExchangeServer.ps1 script; refer to the Build Environment
Recovery Steps section at the end of this lab for detailed steps.

Important: Do not proceed to the next step until you have a properly configured
LUC-EX1 Azure virtual machine.

52. To run the next provisioning script, at the Windows Azure PowerShell prompt, type the
following command, and press ENTER:

. .\BuildADFSServer1.ps1

53. If you get any red script errors, stop the script execution by pressing Ctrl+C, and then
refer to the Build Environment Recovery Steps section at the end of this lab.

54. The script will take 10-15 minutes to complete; when the script has completed, verify
that the following information is displayed:

ServiceName: LUC-CLOUD-<suffix>(where suffix is the "unique suffix" number

you recorded in step 20 above)

Name: LUC-SV1

IpAddress: 10.0.0.6

InstanceStatus: ReadyRole
 PowerState: Started

If your display does not include the above information, you will need to remove Azure
objects, and then rerun the BuildADFSServer1.ps1 script; refer to the Build Environment
Recovery Steps section at the end of this lab for detailed steps.

Important: Do not proceed to the next step until BuildADFSServer1.ps1 has

successfully completed.

55. On LUC-CL1, switch to the LUC-DC1 RDP session.

56. On LUC-DC1, in Active Directory Users and Computers, click Action, then click
Refresh, then in the Lucerne Publishing domain, verify that the Computers OU
contains the LUC-SV1 computer.

57. Minimize the LUC-DC1 RDP session.

58. On LUC-CL1, switch to File Explorer.

59. In E:\RDP_files, verify that LUC-SV1.rdp exists.

60. Double-click LUC-SV1.rdp.

61. If a Remote Desktop Connection warning message appears, click Dont ask me again
for connections to this computer and click Connect.

62. Connect as LUCERNE\LucAdmin, password: Pa$$w0rd.

63. If another Remote Desktop Message appears, click Dont ask me again for connections
to this computer and click Yes; verify that you can successfully connect to this
machine.

64. Close the LUC-SV1 RDP session.

If LUC-SV1 has not been joined to the domain, or you cannot connect to LUC-SV1
using RDP, you will need to remove the Azure virtual machine, and then rerun the
BuildADFSServer1.ps1 script; refer to the Build Environment Recovery Steps section at
the end of this lab for detailed steps.
 Important: Do not proceed to the next step until you have a properly configured
LUC-SV1 Azure virtual machine

65. To run the next provisioning script, at the Windows Azure PowerShell prompt, type the
following command, and press ENTER:

. .\BuildADFSServer2.ps1

66. If you get any red script errors, stop the script execution by pressing Ctrl + C, and then
refer to the Build Environment Recovery Steps section at the end of this lab.

67. The script will take 10-15 minutes to complete; when the script has completed, verify
that the following information is displayed:

ServiceName: LUC-CLOUD-<suffix>(where suffix is the "unique suffix" number

you recorded in step 20 above)

Name: LUC-SV2

IpAddress: 10.0.0.7

InstanceStatus: ReadyRole

PowerState: Started

If your display does not include the above information, you will need to remove Azure
objects, and then rerun the BuildADFSServer2.ps1 script; refer to the Build Environment
Recovery Steps section at the end of this lab for detailed steps.

Important: Do not proceed to the next step until BuildADFSServer2.ps1 has

successfully completed.

68. On LUC-CL1, switch to the LUC-DC1 RDP session.

69. On LUC-DC1, in Active Directory Users and Computers, click Action, then click
Refresh, then in the Lucerne Publishing domain, verify that the Computers OU
contains the LUC-SV2 computer.

70. Minimize the LUC-DC1 RDP session.

71. On LUC-CL1, switch to File Explorer.

72. In E:\RDP_files, verify that LUC-SV2.rdp exists.

73. Double-click LUC-SV2.rdp.

74. If a Remote Desktop Connection warning message appears, click Dont ask me again
for connections to this computer and click Connect.

75. Connect as LUCERNE\LucAdmin, password: Pa$$w0rd.

76. If another Remote Desktop Message appears, click Dont ask me again for connections
to this computer and click Yes; verify that you can successfully connect to this
machine.

77. Close the LUC-SV2 RDP session.

If LUC-SV2 has not been joined to the domain, or you cannot connect to LUC-SV2
using RDP, you will need to remove the Azure virtual machine, and then rerun the
BuildADFSServer2.ps1 script; refer to the Build Environment Recovery Steps section at
the end of this lab for detailed steps.

Important: Do not proceed to the next step until you have a properly configured
LUC-SV2 Azure virtual machine

78. To run the next provisioning script, at the Windows Azure PowerShell prompt, type the
following command, and press ENTER:

. .\BuildADFSProxy.ps1

79. If you get any red script errors, stop the script execution by pressing Ctrl + C, and then
refer to the Build Environment Recovery Steps section at the end of this lab.

80. The script will take 10-15 minutes to complete; when the script has completed, verify
that the following information is displayed:

ServiceName: LUC-CLOUD-<suffix>(where suffix is the "unique suffix" number

you recorded in step 20 above)

Name: LUC-SV3
 IpAddress: 10.0.0.8

InstanceStatus: ReadyRole

PowerState: Started

If your display does not include the above information, you will need to remove Azure
objects, and then rerun the BuildADFSProxy.ps1 script; refer to the Build Environment
Recovery Steps section at the end of this lab for detailed steps.

Important: Do not proceed to the next step until BuildADFSProxy.ps1 has

successfully completed.

81. On LUC-CL1, switch to the LUC-DC1 RDP session.

82. On LUC-DC1, on the Taskbar, click Windows PowerShell.

83. At the Windows PowerShell prompt, type the following command, and press ENTER:

Ping 10.0.0.8

84. Verify that the Ping is successful, and there is a response from 10.0.0.8.

85. Minimize the LUC-DC1 RDP session.

86. On LUC-CL1, switch to File Explorer.

87. In E:\RDP_files, verify that LUC-SV3.rdp exists.

88. Double-click LUC-SV3.rdp.

89. If a Remote Desktop Connection warning message appears, click Dont ask me again
for connections to this computer and click Connect.

90. Connect as LUCERNE\LucAdmin, password: Pa$$w0rd.

91. If another Remote Desktop Message appears, click Dont ask me again for connections
to this computer and click Yes; verify that you can successfully connect to this
machine.

92. Close the LUC-SV3 RDP session.

 If LUC-DC1 cannot ping LUC-SV3 (by address 10.0.0.8), or you cannot connect to
LUC-SV3 using RDP, you will need to remove the Azure virtual machine, and then
rerun the BuildADFSProxy.ps1 script; refer to the Build Environment Recovery Steps
section at the end of this lab for detailed steps.

Important: Do not proceed to the next step until you have a properly configured
LUC-SV3 Azure virtual machine

93. To run the next provisioning script, at the Windows Azure PowerShell prompt, type the
following command, and press ENTER:

. .\BuildClient2.ps1

94. If you get any red script errors, stop the script execution by pressing Ctrl + C, and then
refer to the Build Environment Recovery Steps section at the end of this lab.

95. The script will take 15-25 minutes to complete; when the script has completed, verify
that the following information is displayed:

ServiceName: LUC-CLOUD-<suffix>(where suffix is the "unique suffix" number

you recorded in step 20 above)

Name: LUC-CL2

IpAddress: 10.0.0.9

InstanceStatus: ReadyRole

PowerState: Started

If your display does not include the above information, you will need to remove Azure
objects, and then rerun the BuildClient2.ps1 script; refer to the Build Environment
Recovery Steps section at the end of this lab for detailed steps.

Important: Do not proceed to the next step until BuildClient2.ps1 has

successfully completed.

96. On LUC-CL1, switch to the LUC-DC1 RDP session.

97. On LUC-DC1, in Active Directory Users and Computers, click Action, then click
Refresh, then in the Lucerne Publishing domain, verify that the Computers OU
contains the LUC-CL2 computer.

98. Minimize the LUC-DC1 RDP session.

99. On LUC-CL1, switch to File Explorer.

100. In E:\RDP_files, verify that LUC-CL2.rdp exists.

101. Double-click LUC-CL2.rdp.

102. If a Remote Desktop Connection warning message appears, click Dont ask me again
for connections to this computer and click Connect.

103. Connect as LUCERNE\LucAdmin, password: Pa$$w0rd.

104. If another Remote Desktop Message appears, click Dont ask me again for connections
to this computer and click Yes; verify that you can successfully connect to this machine, and
that this machine starts in Desktop Experience mode.

105. Close the LUC-CL2 RDP session.

If LUC-CL2 has not been joined to the domain, or you cannot connect to LUC-CL2 using
RDP, you will need to remove the Azure virtual machine, and then rerun the BuildClient2.ps1
script; refer to the Build Environment Recovery Steps section at the end of this lab for detailed
steps.

Important: Do not proceed to the next step until you have a properly configured
LUC-CL2 Azure virtual machine
106. To run the next provisioning script, at the Windows Azure PowerShell prompt, type the
following command, and press ENTER:

. .\BuildClient3.ps1

107. If you get any red script errors, stop the script execution by pressing Ctrl + C, and then
refer to the Build Environment Recovery Steps section at the end of this lab.

108. The script will take 10-15 minutes to complete; when the script has completed, verify that
the following information is displayed:

ServiceName: LUC-CLOUD-<suffix>(where suffix is the "unique suffix" number you

recorded in step 20 above)

Name: LUC-CL3

IpAddress: 10.0.0.10

InstanceStatus: ReadyRole

PowerState: Started

If your display does not include the above information, you will need to remove Azure
objects, and then rerun the BuildClient3.ps1 script; refer to the Build Environment Recovery
Steps section at the end of this lab for detailed steps.

Important: Do not proceed to the next step until BuildClient3.ps1 has successfully
completed.

109. On LUC-CL1, switch to the LUC-DC1 RDP session.

110. On LUC-DC1, in Active Directory Users and Computers, click Action, then click
Refresh, then in the Lucerne Publishing domain, verify that the Computers OU contains the
LUC-CL3 computer.

111. Close the LUC-DC1 RDP session.

112. On LUC-CL1, switch to File Explorer.

113. In E:\RDP_files, verify that LUC-CL3.rdp exists.

114. Double-click LUC-CL3.rdp.

115. If a Remote Desktop Connection warning message appears, click Dont ask me again
for connections to this computer and click Connect.

116. Connect as LUCERNE\LucAdmin, password: Pa$$w0rd.

117. If another Remote Desktop Message appears, click Dont ask me again for connections
to this computer and click Yes; verify that you can successfully connect to this machine, and
that this machine starts in Desktop Experience mode..

118. Close the LUC-CL3 RDP session.

If LUC-CL3 has not been joined to the domain, or you cannot connect to LUC-CL3 using
RDP, you will need to remove the Azure virtual machine, and then rerun the BuildClient3.ps1
script; refer to the Build Environment Recovery Steps section at the end of this lab for detailed
steps.

Important: Do not proceed to the next step until you have a properly configured
LUC-CL3 Azure virtual machine
Note: The total build process takes approximately 60-70 minutes to complete. Please let your
instructor know when you have reached this point.

Task 4: Upload Labfiles to LUC-DC1

1. On LUC-CL1, in File Explorer, navigate to E:\Labfiles.

2. Verify that the following files exist in E:\Labfiles\Lab01:

AdministrationConfig-EN.msi

msoidcli_64.msi

3. Verify that the following files exist in E:\Labfiles\Lab04:

admintemplates_32.exe

4. Verify that the following files exist in E:\Labfiles\Lab10:

AdministrationConfig-EN.msi

ADModify_2.1.zip

IdFix.zip

5. Verify that the following files exist in E:\Labfiles\Lab11:

AdministrationConfig-EN.msi

msoidcli_64.msi

O365-Fed-MetaData-Update-Task-Installation.ps1

6. Verify that the following files exist in E:\Labfiles\Lab12:

MOSDAL x64 (en-us).zip

7. Inform your instructor if any of the above files are missing; note that some of these
folders also contain other files.

8. On LUC-CL1, in E:\RDP_files, right-click LUC-DC1.rdp, and then click Edit.

9.
 In Remote Desktop Connection, click the Local Resources tab, and in the Local
devices and resources section, click More.

10. In Local devices and resources, expand Drives, select Allfiles (E:), and click OK.

11. In Remote Desktop Connection, click Connect.

12. If a Remote Desktop Connection warning message appears, click Dont ask me again
for connections to this computer and click Connect.

13. Connect as LUCERNE\LucAdmin, password: Pa$$w0rd.

14. If another Remote Desktop Message appears, click Dont ask me again for connections
to this computer and click Yes.

15. In LUC-DC1, on the taskbar, click File Explorer, expand Computer, click E on LUC-
CL1, and then right-click Labfiles, and click Copy.

16. In File Explorer, right-click Local Disk (C:), and then click Paste.

17. The upload may take 15-30 minutes to complete, depending on the local uplink speed.
You can proceed with the next task while this is going on.

18. Close the RDP connection to LUC-DC1.

Task 5: Download Exchange Server 2013

1. On LUC-CL1, switch to the LUC-EX1.rdp session.

2. On LUC-EX1, on the taskbar, click Server Manager.

3. In Server Manager, in the navigation pane, click Local Server.

4. In the Properties for LUC-EX1, next to IE Enhanced Security Configuration, click

On.

5. In the Internet Explorer Enhanced Security Configuration dialog box, select Off for
Administrators, and then click OK.

6. Close Server Manager.

7. On LUC-EX1, press the Windows key to go to the Start screen, and then click Internet
Explorer.

8. At the Windows Internet Explorer 10 dialog box, select Use recommended security
and compatibility settings, and then click OK.

9. If you get an Internet Explorer dialog box, click Yes.

10. In the address box, type http://technet.microsoft.com/en-

us/evalcenter/hh973395.aspx, and then press ENTER.

11. On the Download Microsoft Exchange Server 2013 page, click Get Started Now.

12. On the Sign in page, type [email protected], (where [email protected] is

the email address you used to sign up for the Office 365 trial in Module 1, Lab A,
Exercise 1, Detailed Steps 7 and 8), and then click Sign in.

13. On the Profile Center pages, enter appropriate information, and then click Continue.

14. At the Akamai NetSession Interface dialog box, click download the installer, and then
in the Internet Explorer download bar, click Run.

15. At the Akamai NetSession Interface License Agreement dialog box, click I Agree,
and then click Next.

16. At the Save As dialog box, navigate to C:\Temp, and then click Save; the download
may take 4-5 minutes to complete.

17. At the Akamai NetSession Interface Installation Complete dialog box, click Close.

18. When the download is complete, on the taskbar, click File Explorer, navigate to
C:\Temp, and then double-click Exchange-x64.

19. In the Choose Directory for Extracted Files dialog box, ensure that C:\Temp is
selected, and then click OK

Note: The extraction process will take several minutes to complete; you can proceed to
the next exercise while the files are being extracted.

20. Wait until you get the Extraction Complete dialog box, and then click OK.
Task 6: Obtain your Student DNS Domain Name

1. On LUC-CL1, switch to the Windows Azure PowerShell prompt, then type the following
command, and press ENTER:

.\GetIPAddress.ps1

2. Note the public IP address of the Lucerne Publishing datacenter:

3. Note: You will require this address in several of the following labs, so you might want to
save it in a text file onto your desktop.

4. On LUC-CL1, on the taskbar, click Internet Explorer.

5. In the address box, type http://www.O365Ready.com, and then press ENTER.

6. Under Generate Student Lab Number, type your public IP address from Step 2 above,
and then click Submit.

7. Note down your 5 digit O365Ready Lab DNS domain:

lab______________.o365ready.com

8. Note: You should use this number in all subsequent labs wherever you see
labXXXXX.o365ready.com in the instructions.

9. Switch back to the Windows Azure PowerShell prompt, type Resolve-DNSName

labXXXXX.o365ready.com (replacing XXXXX with the number from Step 6 above)
and press ENTER.

10. Check that the returned IP address value matches the one you recorded in Step 2.

Task 7: Install Exchange 2013 into your Domain

1. Switch back to the LUC-EX1 remote desktop session.

2. On LUC-EX1, press the Windows key to go to the Start screen.

3. On Start screen, type PowerShell.

4. Right-click Windows PowerShell, and then click Run as administrator.

5. At the Windows PowerShell prompt, type the following command, and press ENTER:

CD C:\Temp

6. At the Windows PowerShell prompt, type the following command, and press ENTER:

Set-ExecutionPolicy Unrestricted

7. Press ENTER to confirm the execution policy change.

8. At the Windows PowerShell prompt, type the following command, and press ENTER:

.\SetupExchange.ps1

9. At the What is your 5 digit O365Ready Lab UPN number prompt, enter the number
you were assigned in the previous task (where XXXXX is your unique O365ready.com
number)

10. Your lab UPN is displayed.

11. Wait until you see the "Exchange setup is complete" message before proceeding; the
installation takes approximately 45-50 minutes. (Ignore any error messages relating to
user accounts that already exist).

12. Close the RDP session.

13. On LUC-CL1, switch to the Windows Azure PowerShell prompt.

14. At the Windows Azure PowerShell prompt, type the following command, and press
ENTER:

.\RestartExchange.ps1

15. Wait until you see the "Exchange environment is ready" message before proceeding.

Task 8: Verify the Exchange Server Installation

1. On LUC-CL1, switch to the RDP connection to LUC-DC1.

2. In Server Manager, click Tools, and click Active Directory Domains and Trusts.
3. In Active Directory Domains and Trusts, in the console tree, right-click Active
Directory Domains and Trusts, and click Properties.

4. In the Active Directory Domains and Trusts dialog box, verify that the UPN suffix is
LabXXXXX.o365ready.com (where XXXXX is your unique O365ready.com number).

5. Close the Active Directory Domains and Trusts dialog box, and then close Active
Directory Domains and Trusts.

6. In Server Manager, click Tools and click Active Directory Users and Computers.

7. In the Accounts OU, verify that there are 15 user accounts.

8. In the Sales OU, verify that there are 2 accounts.

9. Double-click one of the user accounts, and on the Account tab, verify that the logon
name is in the form <name>@LabXXXXX.o365ready.com (where XXXXX is your
unique O365ready.com number).

10. Close the user properties dialog box, and then close Active Directory Users and
Computers.

11. Minimize the LUC-DC1 RDP session.

12. On LUC-CL1, double-click LUC-EX1.rdp, and connect as LUCERNE\LucAdmin,

password: Pa$$w0rd.

13. On the Start screen, click Exchange Management Shell.

14. At the Exchange Management Shell prompt, type the following command, and press
ENTER:

Get-ExchangeServer |Select Name, ServerRole

15. Verify that the Mailbox and ClientAccess roles are enabled on this server.

16. At the Exchange Management Shell prompt, type the following command, and press
ENTER:

Get-Mailbox -OrganizationalUnit Accounts

17. Verify that there are 15 mail-enabled users.

18. On LUC-EX1, on the Start screen, start Internet Explorer, and in the Address bar, type
https://luc-ex1/ecp.

19. Log in as LUCERNE\LucAdmin with a password of Pa$$w0rd.

20. Confirm that you can see the Exchange admin center.

21. Minimize the LUC-EX1 RDP session.

22. On LUC-CL1, switch to Internet Explorer.

23. In the address box, type https://IPaddress/owa (where IPaddress is the public IP address
you obtained in step 2 of the Obtain your Student DNS Domain Name task), and then
press ENTER.

24. On the There is a problem with this website's security certificate page, click
Continue to this website.

25. Log in as LUCERNE\LucAdmin with a password of Pa$$w0rd.

26. On the Outlook Web App page, under Language, select English (United States) and
under Time zone, select (UTC) Coordinated Universal Time, and click save.

27. Click new mail and in the To box, type [email protected], (where
[email protected] is the email address you used to sign up for the Office 365
trial in Module 1, Lab A, Exercise 1, Detailed Steps 7 and 8).

28. Add a subject line and some body text.

29. Click SEND.

30. If the message bounces back, forward it to [email protected]

and your IP address should be delisted within 24 hours.

Note that you will not get a response to the delisting request as incoming DNS has not
yet been configured.

Results: You have a working on-premises environment hosted in Windows Azure. You
have downloaded the installation file for Exchange Server ready to run the setup process.
Exercise 2: (If Required): Build Environment Recovery Steps

Task 1: Recovery from Storage and Network Build Errors

1. In LUC-CL1, on the Taskbar, click Internet Explorer.

2. In the address bar, type http://manage.windowsazure.com, and press ENTER.

3. Sign in with the Live ID associated with your Azure Trial; this should be
[email protected], (where [email protected] is the email address you
used to sign up for the Office 365 trial in Module 1, Lab A, Exercise 1, Detailed Steps 7
and 8).

4. In the Windows Azure portal, click STORAGE and on the bottom bar, click DELETE;
if no storage is listed, go to step 7.

5. At the confirmation prompt, click YES.

6. Wait until the deletion has completed.

7. In the Windows Azure portal, click NETWORKS and on the bottom bar, click
DELETE; if no virtual network is listed, go to step 10.

8. At the confirmation prompt, click YES.

9. Wait until the deletion has completed.

10. In the Windows Azure portal, on the networks page, click DNS SERVERS and on the
bottom bar, click DELETE; if no DNS is listed, go to step 13.

11. At the confirmation prompt, click YES.

12. Wait until the deletion has completed.

13. In the Windows Azure portal, click SETTINGS, then click AFFINITY GROUPS, and
then, on the bottom bar, click DELETE.

14. At the confirmation prompt, click YES.

15. Wait until the deletion has completed.

16.
 Return to detailed step 16 in the Build the Lucerne Publishing Datacenter using
Windows Azure PowerShell task.

Task 2: Recovery from Domain Controller Build Errors

1. In LUC-CL1, close the LUC-DC1 RDP session.

2. On the Taskbar, click Internet Explorer.

3. In the address bar, type http://manage.windowsazure.com, and press ENTER.

4. Sign in with the Live ID associated with your Azure Trial; this should be
[email protected], (where [email protected] is the email address you
used to sign up for the Office 365 trial in Module 1, Lab A, Exercise 1, Detailed Steps 7
and 8).

5. In the Windows Azure portal, click VIRTUAL MACHINES.

6. In the virtual machines list, click LUC-DC1, and on the bottom bar, click DELETE, and
then click Delete the attached disks.

7. At the confirmation prompt, click YES.

8. Wait until the deletion has completed.

9. In the Windows Azure portal, click CLOUD SERVICES, and on the bottom bar, click
DELETE.

10. At the confirmation prompt, click YES.

11. Wait until the deletion has completed.

12. Return to detailed step 23 in the Build the Lucerne Publishing Datacenter using
Windows Azure PowerShell task.

Task 3: Recovery from Exchange Server Build Errors

1. In LUC-CL1, close the LUC-EX1 RDP session.

2. On the Taskbar, click Internet Explorer.

3. In the address bar, type http://manage.windowsazure.com, and press ENTER.

4. Sign in with the Live ID associated with your Azure Trial; this should be
[email protected], (where [email protected] is the email address you
used to sign up for the Office 365 trial in Module 1, Lab A, Exercise 1, Detailed Steps 7
and 8).

5. In the Windows Azure portal, click VIRTUAL MACHINES.

6. In the virtual machines list, click LUC-EX1, and on the bottom bar, click DELETE, and
then click Delete the attached disks.

7. At the confirmation prompt, click YES.

8. Wait until the deletion has completed.

9. Switch to the LUC-DC1 RDP session.

10. In LUC-DC1, in Active Directory Users and Computers, in the Lucerne Publishing
domain, in the Computers container, right-click the LUC-EX1 computer, and then click
Delete.

11. In the Active Directory Domain Services dialog box, click Yes.

12. If you get a Confirm Subtree Deletion dialog box, click Yes.

13. Minimize the LUC-DC1 RDP session.

14. Return to detailed step 35 in the Build the Lucerne Publishing Datacenter using
Windows Azure PowerShell task

Task 4: Recovery from AD FS Server 1 Build Errors

1. In LUC-CL1, close the LUC-SV1 RDP session.

2. On the Taskbar, click Internet Explorer.

3. In the address bar, type http://manage.windowsazure.com, and press ENTER.

4. Sign in with the Live ID associated with your Azure Trial; this should be
[email protected], (where [email protected] is the email address you
used to sign up for the Office 365 trial in Module 1, Lab A, Exercise 1, Detailed Steps 7
and 8).

5. In the Windows Azure portal, click VIRTUAL MACHINES.

6. In the virtual machines list, click LUC-SV1, and on the bottom bar, click DELETE, and
then click Delete the attached disks.

7. At the confirmation prompt, click YES.

8. Wait until the deletion has completed.

9. Switch to the LUC-DC1 RDP session.

10. In LUC-DC1, in Active Directory Users and Computers, in the Lucerne Publishing
domain, in the Computers container, right-click the LUC-SV1 computer, and then click
Delete.

11. In the Active Directory Domain Services dialog box, click Yes.

12. If you get a Confirm Subtree Deletion dialog box, click Yes.

13. Minimize the LUC-DC1 RDP session.

14. Return to detailed step 52 in the Build the Lucerne Publishing Datacenter using
Windows Azure PowerShell task

Task 5: Recovery from AD FS Server 2 Build Errors

1. In LUC-CL1, close the LUC-SV2 RDP session.

2. On the Taskbar, click Internet Explorer.

3. In the address bar, type http://manage.windowsazure.com, and press ENTER.

4. Sign in with the Live ID associated with your Azure Trial; this should be
[email protected], (where [email protected] is the email address you
 used to sign up for the Office 365 trial in Module 1, Lab A, Exercise 1, Detailed Steps 7
and 8).

5. In the Windows Azure portal, click VIRTUAL MACHINES.

6. In the virtual machines list, click LUC-SV2, and on the bottom bar, click DELETE, and
then click Delete the attached disks.

7. At the confirmation prompt, click YES.

8. Wait until the deletion has completed.

9. Switch to the LUC-DC1 RDP session.

10. In LUC-DC1, in Active Directory Users and Computers, in the Lucerne Publishing
domain, in the Computers container, right-click the LUC-SV2 computer, and then click
Delete.

11. In the Active Directory Domain Services dialog box, click Yes.

12. If you get a Confirm Subtree Deletion dialog box, click Yes.

13. Minimize the LUC-DC1 RDP session.

14. Return to detailed step 65 in the Build the Lucerne Publishing Datacenter using
Windows Azure PowerShell task

Task 6: Recovery from AD FS Proxy Server Build Errors

1. In LUC-CL1, close the LUC-SV3 RDP session.

2. On the Taskbar, click Internet Explorer.

3. In the address bar, type http://manage.windowsazure.com, and press ENTER.

4. Sign in with the Live ID associated with your Azure Trial; this should be
[email protected], (where [email protected] is the email address you
used to sign up for the Office 365 trial in Module 1, Lab A, Exercise 1, Detailed Steps 7
and 8).

5. In the Windows Azure portal, click VIRTUAL MACHINES.

6. In the virtual machines list, click LUC-SV3, and on the bottom bar, click DELETE, and
then click Delete the attached disks.

7. At the confirmation prompt, click YES.

8. Wait until the deletion has completed.

9. Return to detailed step 78 in the Build the Lucerne Publishing Datacenter using
Windows Azure PowerShell task

Task 7: Recovery from Client 2 Build Errors

1. In LUC-CL1, close the LUC-CL2 RDP session.

2. On the Taskbar, click Internet Explorer.

3. In the address bar, type http://manage.windowsazure.com, and press ENTER.

4. Sign in with the Live ID associated with your Azure Trial; this should be
[email protected], (where [email protected] is the email address you
used to sign up for the Office 365 trial in Module 1, Lab A, Exercise 1, Detailed Steps 7
and 8).

5. In the Windows Azure portal, click VIRTUAL MACHINES.

6. In the virtual machines list, click LUC-CL2, and on the bottom bar, click DELETE, and
then click Delete the attached disks.

7. At the confirmation prompt, click YES.

8. Wait until the deletion has completed.

9. Switch to the LUC-DC1 RDP session.

10. In LUC-DC1, in Active Directory Users and Computers, in the Lucerne Publishing
domain, in the Computers container, right-click the LUC-CL2 computer, and then click
Delete.

11. In the Active Directory Domain Services dialog box, click Yes.

12. If you get a Confirm Subtree Deletion dialog box, click Yes.
13. Minimize the LUC-DC1 RDP session.

14. Return to detailed step 93 in the Build the Lucerne Publishing Datacenter using
Windows Azure PowerShell task.

Task 8: Recovery from Client 3 Build Errors

1. In LUC-CL1, close the LUC-CL3 RDP session.

2. On the Taskbar, click Internet Explorer.

3. In the address bar, type http://manage.windowsazure.com, and press ENTER.

4. Sign in with the Live ID associated with your Azure Trial; this should be
[email protected], (where [email protected] is the email address you
used to sign up for the Office 365 trial in Module 1, Lab A, Exercise 1, Detailed Steps 7
and 8).

5. In the Windows Azure portal, click VIRTUAL MACHINES.

6. In the virtual machines list, click LUC-CL3, and on the bottom bar, click DELETE, and
then click Delete the attached disks.

7. At the confirmation prompt, click YES.

8. Wait until the deletion has completed.

9. Switch to the LUC-DC1 RDP session.

10. In LUC-DC1, in Active Directory Users and Computers, in the Lucerne Publishing
domain, in the Computers container, right-click the LUC-CL3 computer, and then click
Delete.

11. In the Active Directory Domain Services dialog box, click Yes.

12. If you get a Confirm Subtree Deletion dialog box, click Yes.

13. Minimize the LUC-DC1 RDP session.

14.
 Return to detailed step 106 in the Build the Lucerne Publishing Datacenter using
Windows Azure PowerShell task.

Lab B: Preparing for Office 365

Exercise 1: Planning a FastTrack Pilot

Task 1: Extracting Customer Information

The headings that Alain would use are as follows.

Services - what Office 365 services do you want to Pilot?

Users what do they do and where do they work?

Devices what devices do users have and is there a bring-your-own-device policy in place?

IT delivery - how does the company currently deliver IT and how is this service viewed
and managed?

Workloads what workloads does the company have that cant be migrated to Office 365?

Pilot users how many do there need to be and in which departments?

Management support what is the attitude to the cloud within the company and do we
have executive support?

Success Criteria how will you define success and how will you measure it?

Feedback - how are you going to capture feedback about the pilot?

The answers from the Lucerne Publishing team are set out below: Services - what Office 365
services do you want to Pilot?

Everything except Project and Visio

 Definitely moving from Exchange Server on-premises to Exchange Online.

Keep in-house document management but evaluate SharePoint.

Very interested in Lync dont currently have it.

Yes to SkyDrive

Yes to Yammer

Users what do they do and where do they work?

Executive team of 50, spread all over the world, including the heads of the remote
headquarters.

Below them are 255 management level personnel, who work either here at HQ or in the
regional offices.

Around 1,600 employees, some at HQ, some in the regional offices, and a few working
from home occasionally.

Over 2,500 freelancers who work from home, but theyre not going to be part of this phase.

Devices what devices do users have and is there a bring-your-own-device policy in place?

Senior Execs can use whatever they like

Some of them are on iPads, some on Android tablets, a few more on Windows RT devices
and some with PCs.

Same BYOD policy for management, although they do tend to be more PC-based and more
static in terms of their locations.

Employees are all provided with PCs, either workstations or laptops.

Associates use whatever they want as long as it is compatible with the companys file
formats.
IT delivery - how does the company currently deliver IT and how is this service viewed and
managed?

IT is very much a centralized function.

Main corporate data center here in Switzerland. The company doesnt actually say where
its physically located, but they do have very good network connectivity from HQ. The
architecture is based on Microsofts private cloud design, although they havent fully
virtualized all the workloads yet.

Workloads what workloads does the company have that cant be migrated to Office 365?
The company has the following workloads that cannot be migrated at the moment.

Content management system (although that may migrate to SharePoint later) together with
its SQL Server database

The ERP system

The HR system and database

Everything else could potentially migrate to the cloud.

Pilot users how many do there need to be and in which departments? 5% of users results in
around 100 pilot users. These users should be a representative sample from the departments,
but not include mission-critical users such as Helpdesk staff. Management support what is
the attitude to the cloud within the company and do we have executive support? The CEO does
not deal with that level of technical detail any more. However, the COO is keen to move the
project forward. Success Criteria how will you define success and how will you measure it?
Success will come from the pilot users. If they like the experience of using Office 365 and let
the company know, then the company will consider the pilot a success. How are you going to
capture feedback about the pilot?
The company already has a web-based feedback system setup. This internally-designed system
records and collates the information on the pilot.

Task 2: Identifying Activities within the FastTrack Pilot

A FastTrack Pilot should include the following activities:

Sign up for Office 365.

Set up the pilot domain for Lucerne Publishing (for example,

lucernepublishing.onmicrosoft.com).

Add the pilot users.

Connect their existing email accounts.

Set up a team collaboration site for your pilot.

Prepare the pilot users.

Test the pilot configuration with the pre-pilot users.

Run the pilot.

Complete the pilot and prepare to move to the Deploy phase.

Results: Lucerne Publishing have signed off on the FastTrack Pilot and want to test Office
365 in their environment. They have been provided with a connectivity testing plan and a
deployment timetable for the Office 365 implementation.

Exercise 2: Provisioning the Tenant Account

Task 1: Gathering the Required Information

1. The information that Heidi needs to provide to set up the tenant account is as follows:
 a. Country

b. First name

c. Last name

d. Email

e. Address 1

f. Postal code

g. City

h. Canton abbreviation

i. Phone:

j. Organization name

k. User ID

l. Administrator Password

m. Text verification option

2. In response, Heidi provides the following information:

a. Country: Switzerland

b. First name: Heidi

c. Last name: Leitner

d. Email: Heidis Windows Live account

e. Address 1: Rue Le-Royer

f. Postal code: 1211

g. City: Geneva

h. Canton abbreviation: GE

i. Phone: Heidis mobile phone number, including international code

 j. Organization name: Lucerne Publishing

k. User ID: [email protected]

l. Administrator Password: Pa$$w0rd

3. Text verification options: Your mobile phone number

Task 2: Creating the Tenant Account

1. On LUC-CL1, logged on as Student 1, on the Task bar, click Internet Explorer.

2. In the Address bar, type http://office.microsoft.com/en-us and press ENTER.

3. Click Products, then next to See options for, click Enterprise.

4. On the Office 365 Enterprise E3 page, click Free trial.

5. In the start your free 30-day trial page, complete the following fields. Regardless of
your location, use the following information:

a. Country: Switzerland

b. First name: Heidi

c. Last name: Leitner

d. Email: (use your new Windows Live account that you created earlier)

e. Address 1: Rue Le-Royer

f. Postal code: 1211

g. City: Geneva

h. Canton abbreviation: GE

i. Phone: Your mobile phone number, including international code for your current
country

6. Organization name: Lucerne Publishing

7. In the User ID field, enter hleitner

8. Note the @LucernepublishingXXX.onmicrosoft.com value (where XXX is a number)
that you are allocated.

MAKE A NOTE OF THE XXX NUMBER AFTER LUCERNEPUBLISHING. You will

use this in all subsequent labs and enter it whenever you are asked to supply an
@lucernepublishingXXX.onmicrosoft.com logon or web site URL.

9. Enter Pa$$w0rd in the Password and Confirm password fields.

10. In Verify your phone number, under Phone number, from the drop-down box, select
the code for the country that you are now in.

11. In the Mobile phone number box, enter your correct mobile phone number.

12. Ensure that the Send text message option is selected, and then click Sent text message.

13. When you receive the confirmatory text on your mobile, enter that in the Verification
code box.

14. Under Microsoft Online Services may contact me with information about their products,
services and events, click to deselect Email and Phone.

15. Click create my account.

Task 3: Checking the Office 365 Service Status

1. Review the information under current health. Note that at this point, services will still
be initializing.

2. Under current health, click view details and history (information displayed may vary).

3. Review any service interruption records or additional information in the status page.

4. Click the RSS button. A new Internet Explorer tab opens.

5. Click Subscribe to this feed.

6. In the Subscribe to this feed dialog box, click Add to Favorites Bar and click
Subscribe.

7. Note how the new Favorites Bar button lists incidents and planned maintenance.
8. Close Internet Explorer.

9. If prompted, click Close all tabs.

Results: You have successfully provisioned the Office 365 tenant account for Lucerne
Publishing.

Exercise 3: Preparing to Manage Office 365

Task 1: Configuring a Management Computer

1. Switch to the LUC-CL1 virtual machine.

2. Press the Windows key to go to the Start screen.

3. On the Windows Start screen, press Ctrl+Tab to show the All apps page, and then click
Control Panel.

4. In Control Panel, click Programs.

5. In Programs, under Programs and Features, click Turn Windows features on or off.

6. In the Windows Features dialog box, select the .NET Framework 3.5 check box, and
click OK.

7. On the Windows Features page, click Download files from Windows Update.

8. When the update is complete, on the Windows Features page, click Close.

9. Close Control Panel

10. Press the Windows key, and click File Explorer.

11. In File Explorer, navigate to E:\Labfiles\Lab01.

12. Double-click msoidcli_64.

13.
 In the Microsoft Online Services Sign-in Assistant Setup wizard, on the License
Terms page, click I accept the terms in the License Agreement and Privacy
Statement, and click Install.

14. In the User Account Control dialog box, click Yes.

15. On the Completed the Microsoft Online Services Sign-in Assistant Setup Wizard
page, click Finish.

16. In File Explorer, in E:\Labfiles\Lab01, double-click AdministrationConfig-EN.

17. In the Windows Azure Active Directory Module for Windows PowerShell Setup
wizard, on the Welcome page, click Next.

18. On the License Terms page, click I accept the terms in the License, and click Next.

19. On the Install Location page, click Next.

20. On the Ready to Install page, click Install.

21. In the User Account Control dialog box, click Yes.

22. On the Completing the Windows Azure Active Directory Module for Windows
PowerShell Setup page, click Finish

Task 2: Checking Client Connectivity

1. On LUC-CL1, on the Task Bar, click Internet Explorer.

2. In the Address bar, enter https://testconnectivity.microsoft.com/.

3. In the Microsoft Remote Connectivity Analyzer page, click the Office 365 tab.

4. In the Office 365 tab, click Office 365 Exchange Domain Name Server (DNS)
Connectivity Test, and click Next.

5. Under Domain Name, enter lucernepublishingXXX.onmicrosoft.com (where XXX is

your student Office 365 domain).

6. Under Verification, enter the characters that you can see into the verification field, and
click Verify. Note that the verification code is not case-sensitive.
7. Click Perform Test.

8. When you see Connectivity Test Successful, under Test Details, expand Test Steps
and review the checks that have been made against the Exchange Online domain.

9. Click Start Over.

10. In the Office 365 tab, click Office 365 Lync Domain Name Server (DNS)
Connectivity Test, then click Next.

11. In the Sign-in address field, enter [email protected]

(where XXX is your student Office 365 domain), then click Perform Test.

12. When you see Connectivity Test Successful, under Test Details, expand Test Steps
and review the checks that have been made against the Lync Online domain.

13. Click Start Over.

14. In the Office 365 tab, under Microsoft Exchange ActiveSync Connectivity Tests, click
Exchange ActiveSync, then click Next.

15. In Exchange ActiveSync, select Use Autodiscover to detect server settings, then
under Email Address, enter [email protected]
(where XXX is your student Office 365 domain).

16. In Microsoft Account, enter [email protected]

(where XXX is your student Office 365 domain).

17. In Password and Confirm password, enter Pa$$w0rd.

18. Check Ignore Trust for SSL.

19. Check I understand that I must use the credentials of a working account from my
Exchange domain to be able to test connectivity to it remotely. I also acknowledge
that I am responsible for the management and security of this account.

20. Click Perform Test.

21. When you see Connectivity Test Successful, under Test Details, expand Test Steps
and review the checks that have been made against Exchange ActiveSync.

22. Click Start Over.

23. Under Microsoft Office Outlook Connectivity Tests, click Outlook Anywhere (RPC
over HTTP), then click Next.

24. In Outlook Anywhere (RPC over HTTP), in Email Address and Microsoft Account,
enter [email protected] (where XXX is your student
Office 365 domain).

25. In Password and Confirm password, enter Pa$$w0rd.

26. Select Use Autodiscover to detect server settings.

27. Check I understand that I must use the credentials of a working account from my
Exchange domain to be able to test connectivity to it remotely. I also acknowledge
that I am responsible for the management and security of this account.

28. Click Perform Test.

29. When you see Connectivity Test Successful with Warnings, under Test Details,
expand Test Steps and review the checks that have been made against Outlook
Anywhere. Note in particular the Audiscover steps that fail.

30. Under Run Test Again at the top right, note that you can copy this test to the clipboard,
or save it as XML or HTML.

31. Close Internet Explorer.

Results: Lucerne Publishing has installed the management tools onto a client computer and
tested client connectivity.