I meant to post this a few weeks ago, but anyhow… Microsoft released an updated ODT which removes the “Match Current OS” option from the language options list. That seems to work fine. However, the Project Online client has an issue with the Detection Rule being the same as Office 365 ProPlus. So the install (deployment) on a machine with O365 Pro Plus (latest/same version) causes the Project deployment to think it’s already installed. Just change the detection rule and it works. The Visio Pro deployment uses a different detection rule and seems to work fine.
As for Shared Computer Activation deployments, there are at least two (2) ways to go. One is supported, the other is unknown (at this point). The first is to simply build a new deployment, which sounds like a waste of storage space (compared with traditional O365 ProPlus deployment builds using ODT and XML files) but if you have deduplication turned on for the content source location it shouldn’t be a concern. The other (semi/un-supported) way is to manually copy the “configuration.xml” and make a Shared Activation flavor of it, then add a new deployment type, set some sort of condition to control the scope of that deployment type, and go that route. A little more convoluted, but possible.
While working with a customer to deploy Office 365 ProPlus, with SCCM 1806, we discovered a bug in the OCT that has been confirmed by Microsoft and hopefully fixed soon. The bug is related to the language selection “Match the Current OS” with respect to (English-US) platforms. That selection, for some reason, does not download the required language pack files for the deployment source, and causes the deployments to fail with an error that mentions “missing files”.
The catch here is it won’t return an error when it fails via SCCM. The deployment fails but still returns “success” (exit code 0), and writes the registry key which is shown in the Detection Method configuration. To see the error, we had to execute the setup.exe with /configure and the relevant .xml file from the client cache folder. This is actually two (2) “bugs” as far as I can tell.
The fix/workaround is to simply select the actual language (e.g. “English (United States)”) rather than use the default “Match the Current OS”.
Someone asked if that surgeon on the left is Johan. I cannot confirm, but it wouldn’t surprise me.
- System Center Configuration Manager current branch 1807+
- Basic knowledge about how to use ConfigMgr
- Office 365 / ProPlus licensing
- A really bad attitude
- Create an Application and Deployment in ConfigMgr
- Target a Collection (devices or users)
- Drink coffee
- Punch someone in the face and go home (no, don’t do that)
- During the process of building and deploying the Office configuration, the ConfigMgr console will be locked out from making changes. You can still make it visible, but no scrolling/selecting is allowed. Therefore, if you intend to deploy the configuration at the end of the procedure below, you should prepare the target collection in advance.
- This will require access to the Internet in order to download the content for building the O365 deployment source. If you don’t have access to the internet, you may want to look for a new job.
- I posted a summary version of this using ConfigMgr 1806 on another blog here. But this one has french fries.
- Open the ConfigMgr admin console. This is important.
- Navigate to Software Library > Office 365 Client Management
- On the Office 365 Client Management dashboard, scroll over to the far right until you see that high-quality icon with “Office 365 Client Installer” caption. Click on it like you mean it. (Just kidding about the icon, it really is nice)
- Give the Application a name (e.g. “Office 365 ProPlus with Visio and Project and Fries – 64-bit”)
- Enter a Description (optional)
- Enter the UNC source location path (the folder must exist, but the content will be populated at the end of this exercise). It must be a UNC path. Drive letters are for losers.
- On the “Office Settings” page, click “Go to the Office Customization Tool” (or “Office Customisation Tool” for you non-American folks). NOTE: If you do not already have the latest version of OCT installed, it will prompt you to download and extract it somewhere. Then it will continue on. Otherwise, it will just continue on.
- The OCT home page uses a layout designed by Stevie Wonder. It’s very spread out, so, on a low-res display, expect some finger exercise workouts on your mouse or trackpad. Anyhow, look for “To create or update a configuration file, click Next” and click on (you guessed it:) Next.
- The Software and Languages page will open first.
- Enter the Organization Name and select the Version (32 or 64 bit), then click Add. IMPORTANT: Pay attention to the ADD and UPDATE buttons throughout this exciting journey, there is a reward at the end. I’m just kidding, there is no reward, and no Santa Claus either. Note also that while you’re making selections and changes, the information is being updated along the right-most column of the OCT form.
- Select the Software Suite or Product “Office 365 ProPlus” from the drop-down menu, and click Add
- Select the drop-down again, and choose “Visio Pro for Office” and click Add again.
- Select the drop-down again, and choose “Project Online Desktop Client” and click Add one more time.
- The Software section on the right-hand settings column should show all three selections.
- Scroll down to Languages. You HAVE to select an option here. It is not optional. The default choice for most situations will be “Match Operating System“, however, you can add more languages if you like, or just to have some fun with users by dropping unfamiliar languages on them.
- Scroll back up so you can view the navigation menu at top-left again. Then select “Licensing and display settings”
- For most situations, the KMS or MAK options will be disabled, with KMS automatically selected. If yours is different, who cares, I’m writing this crappy blog post, not you. So there.
- Under “Additional Properties“, you can select options to enable Shared Computer Activation, Automatically accept the EULA, and Pin Icons to Taskbar. It’s worth noting that there is no longer a warning label about the taskbar icons, so it would appear to work on Windows 10.
- There is no “Add” or “Update” button to click for this part, so calm down, we’re almost there.
- Scroll up to the navigation menu again and select “Preferences“. This is where you may spend the rest of your life clicking on things, because there’s a lot to click on. Or you may choose to ignore all of it and instead blame configuration issues on whoever handles GPO and MDM settings. If that’s you, well, it sucks to be you. Choose wisely.
- Take a moment to review your settings along the right-hand “Configured Settings” column. Take a moment also to reflect on your poor choices in life, those missed opportunities, that last vacation trip, and how dysfunctional your family is (or could be). Now, when you’re done with that, and put the loaded gun and liquor bottle back in the bottom drawer, and…
- Click “Submit” at the very top right.
- After you click Submit, you will be returned to the Application wizard. Click Next.
- On the Deployment page, it will ask if you want to deploy the application now. If you have a target collection ready to go, you can go for it. YOLO.
If you choose Yes, you will be prompted for typical deployment configuration settings, otherwise, you’ll click Next two more times and then…
- Wait for the content to download and the deployment source to be prepared.
- Don’t forget to distribute the content to your DPs.
- Don’t forget to populate the target collection.
- Don’t forget to allow time for policy updates, etc.
- You can also modify Office 365 Client Installations by using the “Import” feature at the top-right of the OCT form.
I’d ask for feedback/comments on this, but nobody ever posts feedback or comments.