Apr 30, 2015 - 2 Comments - Office 365 -

Office 365 ProPlus Click to Run Deployment Gotchas – Part 1

I’m using SCCM 2012 R2 to deploy Skype for Business (I’m just gonna type SfB from now on, because brevity) as an available install for my users that want to try it (they don’t currently have Lync or anything similar).  I’ve run into a few hurdles so far.

Part 1 – Post-Install Licensing Oddities

After reading through the documentation on configuring the configuration.xml and downloading the source files to a share, I went on to create a SfB installation xml, like so:

<Configuration>
<Add SourcePath=”” OfficeClientEdition=”32″ >
<Product ID=”LyncRetail”>
<Language ID=”en-us” />
</Product>
</Add>
</Configuration>

SfBlicenseThis successfully installed the SfB client, but the licensing wouldn’t jive when I went to log in.  The way I’d done it, Windows only shows SfB as an installed program and not Office 365 ProPlus.  Apparently the Microsoft licensing service is too dumb to realize that it is part of the suite for which I do have a license, and just won’t let you use it.  So, the “proper” way to only install one part of Office, is to actually install all of Office, but specifically exclude every part of it you don’t want.

 

<Configuration>
<Add SourcePath=”” OfficeClientEdition=”32″ >
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us” />
<ExcludeApp ID= “Access” />
<ExcludeApp ID= “Excel” />
<ExcludeApp ID= “Groove” />
<ExcludeApp ID= “InfoPath” />
<ExcludeApp ID= “OneNote” />
<ExcludeApp ID= “Outlook” />
<ExcludeApp ID= “Powerpoint” />
<ExcludeApp ID= “Project” />
<ExcludeApp ID= “Publisher” />
<ExcludeApp ID= “SharePointDesigner” />
<ExcludeApp ID= “Visio” />
<ExcludeApp ID= “Word” />
</Product>
</Add>
<Display Level=”None” AcceptEULA=”TRUE” />
<Logging Path=”%temp%” />
</Configuration>

Makes perfect sense.

2 Responses to Office 365 ProPlus Click to Run Deployment Gotchas – Part 1

  1. Office 365 ProPlus Click to Run Deployment Gotchas - Part 2 - The Billable Life

    […] up my test VM, made sure the new GPO applied to it, and started installing Skype for Business (see Part 1 for more info on that) from my available deployments via SCCM’s Software Center.  It’s […]

    1 May 2015 - Reply
  2. Office 365 ProPlus Click to Run Deployment Gotchas

    […] is sort of an addendum to Part 1.  In my case, my users have Academic E1 licensing for o365 (note that elsewhere in the o365 […]

    17 Jun 2015 - Reply

Leave a Reply

Your email address will not be published. Required fields are marked *