Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Deploying Office 2016 using SCM 2012 R2 SP1 - multi-user PCs
We are using O365 with clients currently running Office 2013 and are looking at upgrading our clients to Office 2016. I can find quite a bit of information on how to push this out using SCCM, which we are currently on SCCM 2012 R2 SP1.
However, we have many workstations that have multiple users that log in and work on them depending on the day and shift. When we deployed 2013 there was a multi-user install as well as a registry change you had to make after you launched the app for the initial time for each user but before activating the app for that particular user.
Does anyone know how I can install Office 2016 on these same computers? Is Office 2016 done differently, and if so, how? If not, how can I accomplish this in SCCM 2012 R2 SP1?
However, we have many workstations that have multiple users that log in and work on them depending on the day and shift. When we deployed 2013 there was a multi-user install as well as a registry change you had to make after you launched the app for the initial time for each user but before activating the app for that particular user.
Does anyone know how I can install Office 2016 on these same computers? Is Office 2016 done differently, and if so, how? If not, how can I accomplish this in SCCM 2012 R2 SP1?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
It shouldn't be a problem at all.
Tutorial is here: https://www.systemcenterdudes.com/sccm-2012-office-2016-deployment/
Tutorial is here: https://www.systemcenterdudes.com/sccm-2012-office-2016-deployment/
Thanks. I did see something similar. The issue we had with the last roll out is that it seems users have to activate every time they login to use O365 unless we make this registry entry below. And it seems the timing has to be they open office, then put this key in, and then they login. I'm hoping there's a way to avoid this. Any thoughts?
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Softwar
"NoDomainUser"=dword:00000
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Softwar
"NoDomainUser"=dword:00000
Sorry, I didn't catch that issue in your initial question --
That NoDomainUser registry entry was due to a problem with Federated Credentials not being able to contact the credential server. It shouldn't be a problem anymore because of the way that multi-user computers now activate Office by using a token that stays on the machine once they log in the first time.
Details about it are here: https://technet.microsoft.com/en-us/library/dn782860.aspx
That NoDomainUser registry entry was due to a problem with Federated Credentials not being able to contact the credential server. It shouldn't be a problem anymore because of the way that multi-user computers now activate Office by using a token that stays on the machine once they log in the first time.
Details about it are here: https://technet.microsoft.com/en-us/library/dn782860.aspx
Premium Content
You need an Expert Office subscription to comment.Start Free Trial