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?
Rick GoodmanNetwork AdministratorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
It shouldn't be a problem at all.

Tutorial is here:
Rick GoodmanNetwork AdministratorAuthor Commented:
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
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
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:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Rick GoodmanNetwork AdministratorAuthor Commented:
Thanks. Do you know if that's true if we're not using ADFS? We're not at this time.
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I don't know why it wouldn't be -- the activation service has nothing at all to do with ADFS.
Rick GoodmanNetwork AdministratorAuthor Commented:
OK, thanks. I just deployed it today to a test PC and am going to test the shared PC option tomorrow. Thanks. for the help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.