Category Archives: Migration

Un-Encrypted PST Import (Network Upload) to Office 365

This is a complete step-by-step for using the Office 365 Import Service to upload an un-encrypted PST File to Office 365.

Please review the Microsoft documentation for this process for updates or changes to this process.

https://technet.microsoft.com/en-us/library/mt644809.aspx

Pre-Requisites

Mailbox Import Export Role – In order to perform the import, the account doing the import needs to be assigned the Mailbox Import Export role. This is easily accomplished by adding the role to the Organization Management role group (as seen in the screen shot). Alternatively, you can create a new role group and assign your account permissions.

Open Exchange Admin Center

(1) Click Permissions

(2) Click Admin Roles

(3) Double Click Organization Management

(4) Click + Roles

(5) Select Mailbox Import Export

(6) Click Add ->

(7) Click OK

(8) Click Save

PST File Share – The PST file(s) that are being imported (because you can import more than one at a time), need to be stored on a network file share, or a file share on your local PC. Note the syntax in the later steps with AZCopy.exe.

Storage Key and Upload URL – During the process below, you are given a storage key and an upload URL. Keep these secure and treat the just like a password. If they fall into the wrong hands, anyone can upload to your tenant.

 

Step-by-Step Process for an Un-Encrypted PST Import (Network Upload) to Office 365

 

  • Download Network Upload Tool (AzCopy.exe)

In order to upload PST files to Microsoft, you must download and install the AzCopy.exe tool. Follow the process below to download and install the tool.

Navigate to https://protection.office.com

Sign in with a Global Admin account for your organization

(1) Click Data Management

(2) Click Import

(3) Click Go to the Import Service

(4) Click

(5) Click Upload Files Over the Network

On the popup page, click Download Tool (Azure AzCopy tool)

Click Run

Click Next

Agree to the EULA

Click Next

Accept the default install location

Click Next

Click Install

Click Yes

Click Finish

  • Storage Key and Upload URL

Before we can use the AzCopy tool to upload the PST file(s) to Office 365, we need to get the upload secure key and the URL. Please use the steps below to get the key and URL specific to your tenant.

Open the Import Data to Office 365 page that we had open the the prvious step

Click the icon

***NOTE*** This is a secure key and URL. Treat this like a password and make sure that it’s kept secure.

Click Copy Key (note this this process can take up to 5 minutes to complete)

Click Show URL for PST Files

Copy the key and URL for use in the next step

  • Upload the PST File(s) to Office 365

Now that we have the AzCopy tool downloaded and installed and we have the secure key and URL, can now upload the PST file(s) to Office 365. Follow the steps below to upload the PST file(s) to Office 365.

Open a command prompt as an admin (on the machine where you installed AzCopy)

Open the directory where you installed AzCopy

Run the following command to start the PST File(s) upload

AzCopy.exe /Source:\\SERVER01\PSTshare /Dest:<URL COPIED FROM STEP ABOVE>/SERVER01/PSTshare/ /Destkey:<SECURE KEY COPIED FROM STEP ABOVE> /S /V:C:\PSTshare\Uploadlog.log

\\SERVER01\PSTshare This denotes the share in which your PST File(s) are placed. If there are multiple PST Files in this location, AzCopy will upload them all.

<URL COPIED FROM STEP ABOVE> This denotes the URL that we got from Office 365 in the step above.

<SECURE KEY COPIED FROM STEP ABOVE> This denotes the secure key that we got from Office 365 in the step above.

C:\PSTshare\Uploadlog.log This denotes a location on the local machine where the verbose log file can be written

If you need additional help or need further explanation on the command above, please use this Microsoft site. https://technet.microsoft.com/en-us/library/mt644809.aspx

 

  • Create the PST Mapping File

Now that the PST File(s) are uploaded to Office 365, we need to create a CSV file that will map the PST file to the mailbox in Office 365. Follow the steps below to create the CSV file.

Download the PST Mapping Template File from Microsoft

Complete the CSV file with your specific information, filling in as many lines as needed. One line per PST file uploaded.

***Note **** If you need additional help or need further explanation on the PST Mapping File, please use this Microsoft site.

Save the PST Mapping File

 

  • Create the Office 365 Import Job

Now that we have the data uploaded and the PST mapping file saved, we can create the import job in Office 365 that will take the mapping file and import the PST files to the mailboxes specified. Follow the steps below to complete the process.

Navigate to https://protection.office.com

Sign in with a Global Admin account for your organization

(1) Click Data Management

(2) Click Import

(3) Click Go to the Import Service

(4) Click

(5) Click Upload Files Over the Network

(6) Check * I’m done uploading my files

(7) Check * I have access to the mapping file

(8) Click Next

(9) Enter a Job Name

(10) Click Next

(11) Click + to Add the Mapping File

(12) Validate the Mapping File (Under 100 rows)

(13) Agree to the terms and conditions

(14) Click Finish

(15) Click Closed

The import will now start. You can check the status of the import by going to the Office 365 Admin Center and opening the Import tab. Use the refresh button to get the updated status.

Monitor the status column for completion or error. My upload below completed with skipped items. Clicking on the job and the selecting View Details will allow you to troubleshoot the status message. With my example below, I had one corrupted mail item and this was discovered with a detailed log provided with the upload.

 

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps Office365 MVP

Email Me Follow me on Twitter Connect with me on LinkedIN

Migrating AD FS 2.0 to AD FS 3.0 for Office365 Single Sign-On

I’ve been getting quite a few requests to write a BLOG post that details the process of migrating your legacy AD FS infrastructure to AD FS 3.0 (released with Windows Server 2012 R2). The step-by-step below details one method.

 

Migration Paths

There are a couple different paths when migrating AD FS from version 2.0 to AD FS 3.0. The one that I am going to detail below is a parallel install, exporting the AD FS 2.0 configuration and importing to AD FS 3.0. There are other methods of completing this task, but prefer this method, because you can build the whole AD FS 3.0 solution, test the complete solution and then cutover to it by updating DNS. There is no user impact. Please visit this Microsoft site for all the supported methods. This method will only work if ADFS 2.0 is in a farm configuration. If you are not in a farm configuration, you must do a manual migration. See the links below.

http://technet.microsoft.com/en-us/library/dn486815.aspx

http://technet.microsoft.com/en-us/library/dn486787.aspx

 

Assumptions

  1. Base build new AD FS 3.0 server with Windows Server 2012 R2
  2. Add server to the local domain
  3. Export SSL certificate on AD FS 2.0 server (with private key)
  4. AD FS service account and password that was used to deploy AD FS 2.0
  5. Directory Sync is running

 

Import SSL Certificate

 

***NOTE*** It’s very important to use the same SSL certificate as you used in your AD FS 2.0 deployment.

***NOTE*** Microsoft recommends that you go to the AD FS 2.0 server and export the SSL certificate (with private key) to be sure that it’s the same one

 

I assume that you have exported the SSL certificate and this is the procedure on how to import it.

Open the Start Screen


Type MMC

 Click the MMC app


MMC opens


Click File

Click Add/Remove Snap-in

Select Certificates

Click Add>


Select Computer Account

Click Next


Select Local Computer

Click Finish


Click OK


Expand Certificates

Expand Personal

Right Click Certificates

Select Import


Select Local Machine

Click Next


Browse to the Exported Certificate

Click Next


Enter Password

Mark the key as exportable

Click Next


Place in the Personal certificate store

Click Next


Click Finish


Successful


 

 

Install AD FS Role on Windows Server 2012 R2

 

Login to the AD FS 3.0 Server

Open Server Manager

Click Local Server

Click Manage

Click Add Roles and Features

 

Click Next

 

Click Next

 

Click Next

 

Select Active Directory Federation Services

Click Next

 

Click Next

 

Click Next

 

Click Install

Installation starts

 

Install completed. Don’t close and continue to the next step

 

 

Configure AD FS 3.0

 

Click Configure the federation service on this server

 

Select Create the first federation server in a federation farm

Click Next

 

Use an account with Domain Admin rights to perform the install. Please note that this is not the service account. That comes later in the setup.

Click Next

 

Select the certificate that we imported in the previous step. WARNING – This MUST be the same SSL certificate used in the AD FS 2.0 farm

Enter the Federation Service Display Name. WARNING – This MUST match the AD FS 2.0 Farm Name

Click Next

 

Specify the AD FS Service Account. WARNING – This has to be the same AD FS Service account that is used in the AD FS 2.0 farm. No exceptions

Enter Password

Click Next

 

Select the default (Windows Internal Database) – Unless you want to use SQL, but don’t use the same database as the AD FS 2.0 farm.

Click Next

 

Click Next

 

Click Configure

 

Configuration started

 

Configuration Finished

 

If you navigate to the AD FS Management, you will notice that our Relying Party Trusts does not include Office365.

 

 

Export the AD FS 2.0 Configuration

 

Login to the AD FS 2.0 Server

Insert or mount the Windows Server 2012 R2 DVD into the server

Run PowerShell as Administrator

Navigate to \support\adfs on the Windows Server 2012 R2 DVD

Execute the Script

.\export-federationconfiguration.ps1 –path c:\adfs_export”

This will export the AD FS 2.0 configuration and dump it to a folder called adfs_export on the root of C: drive.

Export completed

Copy the ADFS_Export folder to Windows Server 2012 R2 AD FS Server

Import the AD FS Configuration to AD FS 3.0

Login to the AD FS 3.0 Server

Open PowerShell as an Administrator

Navigate to \support\adfs on the Windows Server 2012 R2 DVD

Execute the Import-FederationConfiguration.ps1 script with the path parameter to the exported contents of the AD FS 2.0 configuration

.\import-federationconfiguration.ps1 –path C:\ADFS_Export

    

Import started

Note the warnings that this will remove all existing claims providers and relying party trusts on the target server. So make sure that you are on the right server.

Imported successfully

Verify the Import in AD FS Management

Testing Single Sign-On

 

From a PC connected to the domain, edit the hosts file and add the IP address of the AD FS 3.0 server that points to the AD FS 3.0 Federation Farm

 

Navigate to the IDP Initiated Sign-on page – https://sts.DOMAIN.com/adfs/ls/IdpInitiatedSignon.aspx . You can tell right away that this is the AD FS 3.0 server by the way the web page looks.

Test signing in

 

Once this is completed, then you can test logging into the Microsoft Office365 Portal.

 

Adding Redundancy and WAP Servers

Keep in mind that when you add more AD FS servers to the farm or add the Web Authentication Servers (AD FS Proxy Servers) to this new farm, that you will add the servers directly to the farm. There is no need to repeat the process above once you have the first AD FS 3.0 server setup in the new farm. Also note that if you have not changed DNS to point at the new farm, you will most likely need to use hosts files on the new servers to make sure that are you adding to the new farm. Internal DNS is still set to the AD FS 2.0 farm.

 

Production Cut Over

When the AD FS 3.0 solution has been completed, update internal and external DNS to point at the new AD FS 3.0 farm.

 

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps Office365 MVP

Technical Consultant

Concepps Group

Email Me Follow me on Twitter Connect with me on LinkedIN

Setting up Directory Synchronization with the NEW Office 365

Now that we have the AD FS and the AD FS Proxy Servers setup, we need to setup Directory Synchronization. Directory Sync gives you the ability to synchronize (one way to the cloud) your local Active Directory (or a portion of) to your Office 365 Account. This is a critical piece of the single sign-on solution for Office 365 as it works together with AD FS. Directory Sync is installed as a single server and cannot be made highly available.

We have AD FS setup already and we have base built the Directory Sync server with Windows Server 2012. The server has a static IP address and is domain joined.

Activate Directory Synchronization

Before we can setup and use the Directory Sync software, we need to activate it in the Office 365 Admin Center

  1. Open Internet Explorer

     

  2.  

  3. Click Users and Groups

     

  4. Click the Activate link next to Active Directory® synchronization

This process can take up to 24 hours.

 

Install Directory Sync Software

We need to download and install the Directory Sync software from the Office 365 Admin Center. This is a 64bit installer.

  1. Login to the Directory Sync Server with an Administrator account

     

  2. Open Internet Explorer

     

  3.  

  4. Click Users and Groups

     

  5. Click the Set up link next to Active Directory® synchronization

     

  6. Skip down to step 4 and click download

     

  7. Navigate to the downloaded file (dirsync.exe) and open it

     

  8. Click Next

     

  9. Accept the License Agreement

     

  10. Click Next

     

  11. Choose an install location

     

  12. Click Next

     

  13. Installing – This process takes a while, so be patient.

     

  14. Install complete, click Next

     

  15. Uncheck Start Configuration Wizard now

     

  16. Click Finish

     

  17. REBOOT the Directory Sync server before running the Configuration Wizard

 

Configure Directory Sync

Picking up from the last setup, we can now configure Directory Sync.

  1. Login to the Directory Sync Server with an Administrator account

     

  2. Open the Configuration Wizard from the Desktop shortcut

     

  3. Run the Wizard while logged in with an Administrator account.

     

  4. Click Next

     

  5. Enter a cloud account (@domain.onmicrosoft.com) that has Global Administrator role assigned in Office 365.

     

    ***Note*** I create an unlicensed service account in Office 365 for AD FS and Directory Sync. Assign these accounts Global Administrator role and set the passwords to not expire. This will prevent issues if the password changes or the

     

  6. Click Next

     

  7. Enter an Enterprise Administrator account

     

    *** Note*** Running the Wizard needs Enterprise Administrator credentials. Once the Wizard has completed, the credentials will not be used again.

     

  8. Click Next

     

  9. Enable Exchange Hybrid Deployment

     

    ***Note*** If Directory Sync detects that you have at least once Exchange 2010 SP1 or newer server in your Active Directory, you will be prompted to Enable Exchange Hybrid Deployment.

     

  10. Click Next

     

  11. The wizard will start the configuring process

     

  12. Completed click Next

     

  13. Uncheck Synchronize now (if you plan to implement OU filtering)

     

    ***Note*** If you want to filter the OUs that get synchronized to Office 365, then follow this BLOG post, Directory Synchronization – Filtering OUs to Synchronize to Office 365. Do not start the synchronization until you have setup OU filtering. This will prevent cleanup in Office 365.

     

    If you don’t want to do OU filtering, then leave this option checked.

     

  14. Click Finish

     

 

Force Synchronization to Office 365

 

Since we stopped the initial sync job in the last step, we need to manually start the first sync job. This is done automatically, if you give Directory Sync more time, or we can force it with PowerShell.

  1. Login to the Directory Sync Server with an Administrator account

     

  2. Open DirSyncConfigShell.psc1 (C:\Program Files\Microsoft Online Directory Sync\)

     

    ***Note*** I create a short cut to this file on my desktop

     

  3. Type Start-OnlineCoexistenceSync

     

  4. Press enter to execute the command

Successful synchronization can be confirmed in the Application Log on the Directory Sync server

You can also verify that the users are now shown in the Office 365 Admin Center. You will notice that the users status is now ‘Synced with Ac’, rather than ‘In cloud’.

 

Now that we have Federation and Directory Sync setup, we can test single-sign on with Office 365.

 

Getting to know the NEW Office 365

  1. Does Microsoft have FREE training for the NEW Office 365?
  2. Signing up for the NEW Office 365
  3. Adding and Verifying a Domain for the NEW Office 365
  4. Creating Cloud Users for the NEW Office 365
  5. Configuring Desktops for the NEW Office 365
  6. Exchange 2003 Cutover Migration to the NEW Office 365
  7. Exchange 2007 Cutover Migration to the NEW Office 365
  8. Setting up AD FS and Enabling Single Sign-On to the NEW Office 365
  9. Setting up AD FS Proxy Servers for Single Sign-On to the NEW Office 365
  10. Setting up Directory Synchronization with the NEW Office 365
  11. Activating and Licensing a Synchronized User in the NEW Office 365
  12. Testing Single Sign-on to the NEW Office 365
  13. Making the Single Sign-On Solution Highly Available
  14. Exchange Hybrid Deployment with the NEW Office 365

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps

Office 365 MVP

Email Me Follow me on Twitter Connect with me on LinkedIN Facebook Me

Exchange 2007 Cutover Migration to the NEW Office 365

I covered this topic in a BLOG post for MS Press. Please click the link below and you will be re-directed there.

From the MVPs: Exchange 2007 Cutover Migration to the NEW Office 365

 

Complete Series:

Getting to know the NEW Office 365

  1. Does Microsoft have FREE training for the NEW Office 365?
  2. Signing up for the NEW Office 365
  3. Adding and Verifying a Domain for the NEW Office 365
  4. Creating Cloud Users for the NEW Office 365
  5. Configuring Desktops for the NEW Office 365
  6. Exchange 2003 Cutover Migration to the NEW Office 365
  7. Exchange 2007 Cutover Migration to the NEW Office 365
  8. Setting up AD FS and Enabling Single Sign-On to the NEW Office 365
  9. Setting up AD FS Proxy Servers for Single Sign-On to the NEW Office 365
  10. Setting up Directory Synchronization with the NEW Office 365
  11. Activating and Licensing a Synchronized User in the NEW Office 365
  12. Testing Single Sign-on to the NEW Office 365
  13. Making the Single Sign-On Solution Highly Available
  14. Exchange Hybrid Deployment with the NEW Office 365

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps

Office 365 MVP

Email Me Follow me on Twitter Connect with me on LinkedIN Facebook Me

Exchange 2003 Cutover Migration to the NEW Office 365

A cut over migration is the simplest way to get all your existing email into Office 365. As the name implies, it’s a cutover from one service to another. Cutover migrations are supported for Exchange 2003, 2007 and 2010; for organizations with fewer than 1000 mailboxes. The setup and process is straight forward and nothing complicated. With any successful migration, some planning and testing of existing infrastructure is invaluable. Make sure that you plan and test the migration prior to trying to implement.

 

PLANNING

Before we can attempt the migration, we need to know what we are going. Microsoft has done a great job of providing good quality information for administrators to use, to plan the migration to Office 365. I always use the Exchange Deployment Assistant as a guide for all my migrations. This site is up to date and will cover most of all the migrations scenarios to Office 365

  1.  

  2. Once the site is launched, you are presented three options. Since I am doing a simple cutover migration from Exchange Server 2003, I am going to use the Cloud Only option

     

  3. Click Cloud Only

     

  4. You are now asked a series of questions on end state goals and existing setup

     

  5. Answer all the questions

     

  6. Click the next arrow

     

  7. The Exchange Deployment Assistant will generate a step by step guide for you to follow. Make sure to read and understand what you are doing.

 

TESTING EXISTING SETUP

 

Using our guide from the Exchange Deployment Assistant, we need to make sure that our Exchange 2003 infrastructure supports RPC over HTTP and Outlook Anywhere. Use the guide to verify the Exchange 2003 setup. Once the setup is verified to be correct, use the Microsoft Remote Connectivity Analyzer to verify RPC over HTTP and Outlook Anywhere.

  1.  

  2. Select the Outlook Anywhere (RPC over HTTP) test

     

  3. Click Next

     

  4. Enter all the information that is requested. Keep in mind that with Exchange 2003, using autodiscover to detect the settings will not work. Exchange 2003 doesn’t support autodiscover. These values will have to be entered manually

     

  5. Enter the Verification code

     

  6. Click Perform Test

     

  7. The test will start

     

  8. Once the test is successful, you can continue to the next step. If it’s successful with warnings, review the warnings and correct them if needed. I get a warning here, because I am using a multi-name UCC certificate. If the test fails, use the report generated and the guide (Exchange Deployment Assistant) to resolve the issues.

 

CONFIGURE CUTOVER MIGRATION

 

  1.  

  2. Open Exchange Admin Center

     

  3. Click Migration

     

  4. Click the drop down menu and select Migrate to Exchange Online

     

  5. Select Cutover migration (supported by Exchange Server 2003 and later versions

     

  6. Click Next

     

  7. Enter on-premises account credentials

     

  8. Click Next

     

  9. Enter the on-premise Exchange Server

     

  10. Enter the RPC Proxy Server

     

  11. Click Next

     

  12. Enter a name for the New Migration Batch

     

  13. Click Next

     

  14. Select a user from Office 365 to get a report once the migration is completed. You can choose to automatically strat the batch or manually start the batch later.

     

  15. Click New

     

  16. The new migration batch is created and the status is set to syncing

 

This is where we wait for the migration to happen. Depending on the number of accounts and the ammount of data, this can take some time. You can view the migration details, by clicking View Details under the Maibox Status.

You will see the accounts provisionig on the Office 365 account and then start to sync from Exchange 2003 to Office 365.

Provisioning

Syncing

 

COMPLETE THE MIGRATION

 

When all the accounts are provisioned and the sync from Exchange 2003 to Office 365 is completed, you will get a report emailed to you. Once you get the report, you can complete the migration process.

  1. Migrate Public Folders – Microsoft has released a whitepaper for the companies that have public folders to migrate to Office 365. Migrate from Exchange Public Folders to Microsoft Office 365
  2. Assign Office 365 licenses to all the users. Use this BLOG post and jump to the section about assigning licenses – Creating Cloud Users for the NEW Office 365
  3. Verify that all the DNS records are updated and pointed towards Office 365 services. Use the DNS section in this BLOG post – Adding and Verifying a Domain for the NEW Office 365.  WARNING – Once you change the MX record to point at Office 365, there is some DNS replication time. During this time email will be delivered to either Exchange 2003 or Office 365. It’s important to keep your migration batch job running for up to 72 hours after switching the MX record.
  4. Configure the desktops to use Office 365 services – Use this BLOG post – Configuring Desktops for the NEW Office 365
  5. Once you are comfortable that all the email is migrated to Office 365 and the MX record DNS replication is completed, you can stop the migration batch job.

 

At this point the migration is complete and you can retire your Exchange 2003 services. Everyone should be happy cloud users.

Complete Series:

Getting to know the NEW Office 365

  1. Does Microsoft have FREE training for the NEW Office 365?
  2. Signing up for the NEW Office 365
  3. Adding and Verifying a Domain for the NEW Office 365
  4. Creating Cloud Users for the NEW Office 365
  5. Configuring Desktops for the NEW Office 365
  6. Exchange 2003 Cutover Migration to the NEW Office 365
  7. Exchange 2007 Cutover Migration to the NEW Office 365
  8. Setting up AD FS and Enabling Single Sign-On to the NEW Office 365
  9. Setting up AD FS Proxy Servers for Single Sign-On to the NEW Office 365
  10. Setting up Directory Synchronization with the NEW Office 365
  11. Activating and Licensing a Synchronized User in the NEW Office 365
  12. Testing Single Sign-on to the NEW Office 365
  13. Making the Single Sign-On Solution Highly Available
  14. Exchange Hybrid Deployment with the NEW Office 365

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps

Office 365 MVP

Email Me Follow me on Twitter Connect with me on LinkedIN Facebook Me

REPLAY – Back to Basics: Setting Up Office 365 – Lync and Learn

Thank you to everyone who attended my Lync and Learn Session. In case you missed it, you can view the Lync recording here or watch the video below. Look for more Office 365 webcast sessions by following the Office 365 Technical blog.

http://community.office365.com/en-us/blogs/office_365_technical_blog/archive/2012/12/12/back-to-basics-setting-up-office-365-lync-and-learn.aspx

Back to Basics: Setting Up Office 365 – Lync and Learn

 

Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see.

Kelsey Epps

Office 365 MVP

Email Me Follow me on Twitter Connect with me on LinkedIN Facebook Me


Back to Basics: Setting Up Office 365 – Lync and Learn

I am excited to announce that I am going to be doing a Lync and Learn session for the Microsoft Office 365 User Community.

 http://community.office365.com/en-us/blogs/office_365_technical_blog/archive/2012/12/12/back-to-basics-setting-up-office-365-lync-and-learn.aspx

 Audience:

Office 365 for professionals and small businesses
Office 365 for enterprises

Lync and Learn is an online session led by Office 365 Product Managers and Community Grid members. Lync and Learn sessions address different Office 365 subjects and scenarios and is beneficial to anyone who wants to learn more and expand their knowledge of the Office 365 suite. View past Lync and Learn sessions here.


Office 365 provides convenience in the cloud through a great set of productivity and collaboration tools. In this Lync and Learn session, Kelsey Epps will provide some convenience of his own through helping us set up Office 365. We’ll get back to the basics and dive into setting up Office 365. In this Lync and Learn Webcast we will cover the following:

  • Sign-up for the trial
  • Adding a domain and verifying it
  • DNS records
  • Create Users and Assign licenses
  • Setup Desktop PC for User
  • Accessing Office 365 Services from the Desktop and Internet
  • Purchasing Additional Licenses
  • Open a service request

Kelsey Epps is a Senior Systems Engineer with a background in Microsoft Clustering, Exchange Server, Lync Server and Windows Server.

Download the calendar invite below and join us on December 20th at 10:00 AM Pacific Time for this great session.

Interested in being our next Lync and Learn presenter? Learn how to join the Office 365 Grid and become an Office 365 Lync and Learn presenter.

———————————————————————————————————————————————————

Presenter: Kelsey Epps, Technology Consultant with HP and Concepps Group, and Office 365 Grid member.

Date/Time: Thursday December 20th, at 10:00 AM Pacific Time. (1 Hour presentation)

Live Meeting Information:
Join online meeting
https://join.microsoft.com/meet/v-joshto/F00T8BQY
Join by Phone
+18883203585
Find a local number

Conference ID: 27579341
Forgot your dial-in PIN? |
First online meeting?
[