Office 365SCCM

Package Office 365 with SCCM 1702


SCCM Current Branch 1702 introduces “Office 365 ProPlus Installer” (this feature was seen in technical previews).The Office 365 ProPlus installer allows you to specify your Office 365 ProPlus settings (exclude apps, update channels etc), download the Office 365 ProPlus files, create the Application, Deployment Type, and deploy the application if you choose to.

Before this feature was released, you needed to use the Office Deployment Tool (ODT) to download the Office 365 ProPlus and create an XML with the Office 365 configuration settings, then create an Application in SCCM.

This post will show how you can leverage the new Office 365 Installer in SCCM Current Branch version 1702 to create, download and deploy an Office 365 ProPlus package without having to use the Office Deployment Tool.

Open the SCCM console go to Software Library node, then expand Office 365 Client Management folder, click on the Office 365 Installer


Give it a name and content location:

You can use an existing XML with the Office 365 ProPlus configuration you have created, or manually create one using this wizard. I have chosen to manually create the XML:

Specify your settings. I have chosen the Office 365 ProPlus suite, and have chosen to exclude the old Groove OneDrive for Business client.

Select your architecture. I am using 32bit, and have chosen to use the Deferred channel.

I have said Yes to deploy the application.

Chosen my collection to deploy it to

Added my distribution point

I am deploying mine as Available

Settings here are left as default.

Default again

Default again


Click next to start downloading the Office 365 ProPlus files

After it has finished, you can now see there is now an Application created with a deployment type and deployed to the collection specified earlier.



Office 365

Office 365 Migration Overview


Why you should make the move to Office 365

Take into account your Infrastructure, how many Servers do you have that manage your mail?

There is at least one for Exchange, one for Mail Archiving and one for Backups. All Servers will need to be maintained, patched and in some cases they will even be migrated to a VM and the OS upgraded.

By migrating your Mail to Office 365 you will be able to eliminate the need for that resource as Microsoft will be managing all of it.

Before making the move to Office 365

You will need to think about how much data is going to be used when your Mail is being managed by Office 365.

Do you have the bandwidth to migrate your data to the cloud?

Are your network speeds adequate enough for use while the migrations are taking place?

What migration method will you use when moving your mailboxes to the cloud?

Infrastructure Evaluation

So you have decided to take the plunge and migrate your Mail to Office 365!

You will need to do an evaluation on your current Infrastructure to see if your system supports Office 365. Certain operating systems and Versions of Exchange will limit your progress so you may need to upgrade or patch them to be able to go ahead with your plans to move into the Cloud.

You may even need to upgrade the software and patch your client devices to ensure they meet Microsoft’s Office 365 requirements.

I have added the System Requirements for Office 365 below.


 Operating system Windows 10, Windows 8.1, Windows 8, Windows 7 Service Pack 1
Windows 10 Server, Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2
 Browser Safari, Chrome, and Firefox – current version
Microsoft Edge – latest version
Internet Explorer – current or immediately previous version
Email client software Office/Outlook 2016
Office/Outlook 2013 with SP1
Office/Outlook 2010 with SP2
Outlook for Macintosh – Office for Mac2016
Computer and processor 1 GHZ or faster x86 or 64-bit processor with SSE2 instruction set
1 GB RAM (32-bit)
Memory 2 GB RAM (64-bit) recommended for graphics features, Outlook Instant Search & certain advanced functionality
Disk space 3 gigabytes (GB)
Monitor resolution 1024 x 768
Exchange ActiveSync must be supported for Office 365
Mobile devices BT Business Email Lite (powered by Microsoft Office 365) requires POP to be supported
Using Outlook Web App on smartphones and tablets For the best experience use the integrated web browser of these devices, Windows 8 tablet, iOS 6 or later versions for iPhone4s or later versions or iOS 6 or later versions for iPad2 or later versions


After you have done your Infrastructure examination you will be able to determine your licensing needs, below i have added Microsoft’s Current Licensing Plan as of February 2018, here is a link to the PDF.

Microsoft Plans and Licensing

Please note: You are now able to Mix and Match Licensing depending on your requirements, which could be a huge cost saving benefit to your business.

Migration Options

Remote Move Migration

You will use this type of migration if you wish to have a hybrid style solution, where you will still have an on-premise exchange to help manage your mailboxes. The reason you would opt for this option is if you wish to migrate mailboxes over a long period of time and slowly phase out your old Infrastructure.

Staged Migration

You will use this if you need to move your mailboxes over a period of time, the difference is that this only supports Exchange 2003 and 2007.

Cur over Migration

This is a short term migration, you would use this if you want to move every Mailbox to the cloud in one go.

IMAP Migration

This is used for other types of mailbox solutions such as AOL or Google Mail.

Ingest Servers

This is an option step, this server will assist you during your migration. Its purpose is to reduce the load or in most cases eliminate it from your main system.

It will process the mail and upload it directly to your Office 365 Service.

When do i remove my old servers?

You will complete this step once you have done your final cut-over to Office 365. Once all mailboxes have been migrated and there are no issues.

Please feel free to comment or contact me directly via LinkedIn for any enquiries.