14) Save the Proof.xml file. In Windows Vista/7, you may need to take ownership and grant full access permission to yourself before able to modify the file.

C:\ProgramData\Microsoft\OFFICE\DATA (for Windows 7 and Vista)

Disclaimer

VBScript to Convert Microsoft Office Files (Word Excel .

Ross Mistry is a best-selling author, community champion and seasoned architect. He has a tremendous amount of experience designing and deploying technology solutions for internet startups and Fortune 100 organizations located in the Silicon Valley. He is known in the world-wide community for his expertise in SQL Server, Windows, Exchange, Virtualization and Private Cloud. Ross frequently speaks at technology conferences around the world and has published many books, whitepapers, and magazine articles. His recent books include; Introducing SQL Server 2012, Windows Server 2008 R2 Unleashed, and SQL Server 2008 Management and Administration. Ross is currently a Principal Enterprise Architect with Microsoft working out of the Microsoft Technology Center in Silicon Valley logiciel detection wifi

Office 2016 Shared Computer Activation on Windows Server .

· · ·

Jalapeno

OP

For anyone interested who might come across this, I have come up with a work around for this.

Option 1

Use script\GPO to delete the contents of %localappdata%\Microsoft\Office\16.0\Licensing when a user logs in. This will then stop the error message from coming up and when they open an Office application it will automatically verify licensing status and create new authString and signingCert files without any intervention (assuming password is saved or AD FS).

Option 2

I found a couple of interesting registry entries under HKLM\Software\Microsoft\Office\ClickToRun\Configuration

Those were SCLCacheOverride and SCLCacheOverrideDirectory. I couldn't find any info on these registry settings from searching however I decided to test if SCL stood for Shared Computer Licensing and it does.

If I set SCLCacheOverride value to 1 and SCLCacheOverrideDirecotry to something like %localappdata%\Microsoft\Office\16.0\Licensing\%computername% then launch an Office application I can see the authString.txt and signingCert.txt files are created under the path specified in SCLCacheOverrideDirectory. Essentially by setting these for each RD Session Host in the farm, when the user logs in it to a particular RD Session Host will create a new sub-folder in the Licensing folder using the computer name. This avoids the error message form coming up in my original post.

1

· · ·

Jalapeno

OP

Thanks for this post -- I have experienced the same issue. Generally the issue comes about because the token expires after 72 hrs of inactivity/they're signing into a different instance of the RDS Host.

Question about Option 1: is that on the RDS Host or on the user/client workstation/vm Or rather, is it in the users roaming profile

Does Outlook throw any additional errors

0

· · ·

Jalapeno

OP

Sorry for the delay in getting back to you.The solutions I included both did not really work as it required users to sign in each time. However it was from their roaming profile.

This issue went away when I updated to version 16.0.7167.2040. However not long after that some users seemed to be getting the Activate Office prompt on an ad-hoc basis. There didn't seem to be any real pattern to it. The fix I've had in place now that seems to have eradicated the issue permanently is to disable Modern Auth for Office 2016, this then reverts to the older Activate Office login screen (the same as 2013) which allows for the "Keep me signed in" option which stores the users credentials in Windows Credentials Manager.

To disable Modern Auth for Office 2016, I added the following reg value for each user (using GPO).

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity

"EnableADAL"=0x00000000

After that setting is in place the user will be presented with the older Activate Office prompt next time they launch Office. I set the registry setting to deploy only at login (not a background refresh) to avoid potential issues for anyone who was still using and Office app.

0

· · ·

Pimiento

OP

I have been tasked with replacing Office 2016 MSI on our RDS Collections(10 servers) with C2R versions of Office 365 ProPlus.  Right now everything from activation to patching with WSUS works perfectly using MSI.  We are using UPDs as roaming profiles in multi server collections.

I am terrified of moving to C2R on RDS.  Is this working any better in Feb 2017  I do not want my users to get continuous activations prompts when using Office C2R across multiple RD session host collections.  We use AD Connect to sync passwords and have also recently enabled SSO feature.

Also how are you handling updates to the Office 365 apps on C2R installs with RDS  Can a user kick off an update mid day like they can on a workstation client

We use GPOs to control updates on C2R installed workstations.  The user has the ability to kick these off manually and they also receive popups.  We don't want those types of behaviors on RDS.

Any problems with installation  Do you still use change user /install to install C2R

0

· · ·

Jalapeno

OP

I wouldn't. "If it ain't broke, don't fix it."

0

· · ·

Pimiento

OP

I wish.  But as of May 2016 you cannot legally using an E3 subscription to access MSI installed office on an RDS server.  So i either need to purchase VL for office 2016 for all my users or figure out how to get the C2R version of Office 365 installed a terminal server.  

0

· · ·

Jalapeno

OP

This has been working ok for us now since that update was released, as long as we don't use the Deferred channel and disable ADAL as shown in my earlier post. First release for Deferred does have the fix and is what we've had to use. The only time users see the activate office prompt now is when they change their password, however if you could configure AD FS then they would never see the prompt when ADAL is left enabled.

In regard to updates, I completely disable updates for Office via GPO and do these manually as they are released after testing. Users do not receive prompts and cannot kick off an update manually. I still use change user /install when doing installs and/or updates of Office C2R. For deploying updates, I just update our Office 365 C2R deployment share and run the install again on the RD Session Hosts.

MSI based install would definitely be my preference, but unfortunately at present we need to work with what we have, same as yourself. C2R has a risk in that the activation information needs to be verified periodically and if MS have issues with that service or you have connectivity issues to Office 365 then you could end up with staff running Office in reduced functionality mode, however that is something the business should be made aware of to assess if mitigating the risk is worth the cost of volume licensing for Office 2016.

0

· · ·

Jalapeno

OP

I was just looking at the updates released this month for Office 2016, and it looks like Deferred channel will now be caught up enough to not have this issue anymore as well.

0

· · ·

Jalapeno

OP

We use C2R. The activation information usually needs to be verified on Mondays, or after 72 hours of token inactivity.

VL is a pia afaik.

0

· · ·

Pimiento

OP

Ok so I built a 2 server collection with Office 2016 C2R First Release for Deferred Channel.  So far I have not encountered any major issues and I have not had to do any hacks or disable ADAL.  We don't have ADFS but we use ADConnect SSO.  There is 1 or 2 extra prompts about activation the first time but so far so good.  No further prompts switching servers and I left my test users logged our for 3 days and then logged them back in and no prompts for reactivation or anything like that.  Seems this is working better than it did a year or two ago...

0

· · ·

Pimiento

OP

We're seeing the issue here a well, looks like users need to login to activate the C2R license every time they're opening a Office2016 app on a different RDS session host.

I am considering to switch off modern authentication ADAL like Cris-dma has confirmed will mitigate the issue.  

I just came across a Office support article at https://support.office.com/en-us/article/How-modern-authentication-works-for-Office-2013-and-Office-... which explains the modern authentication is switched off by default on Exchange online, and a linked article desicribes how to turn it on.  Could this be the cause of the issue, and has anybody tried to turn on modern auth (ADAL) support for exchange online to see if it helps

1

· · ·

Jalapeno

OP

Switching on ADAL for Exchange online will only affect authentication against Exchange Online, not Office Activations. They are two different services. If you turn it on you will see a similar login screen when connecting to Exchange Online as you do for Office activations, instead of the traditional windows credentials prompt with the remember my password checkbox. The advantage of ADAL for Exchange Online is that it supports true Single Sign On when AD FS is implemented.

When using Office 2016, the default configuration is to use ADAL for Office Activations. You'll see the main difference is that an activation prompt using ADAL will not have a remember my password or keep me signed in check box, whereas if ADAL is disabled it will have that checkbox.

Note that disabling ADAL via the registry for Office as I have shown would also disable ADAL when connecting to Exchange Online from Outlook.

The only other way, that I know of, to get around this issue would be to implement AD FS. That way you can leave ADAL enabled for Office and the user should not get a prompt to login to activate Office because it will be handled via Also with AD FS.

1

· · ·

Pimiento

OP

When using ADAL, ADFS 2012 R2, the activation window will still pop-up from time to time. You only need to enter your email and the activation will happen "auto" from there on.. This really is a lousy product for RDS/VDI enviroments, unless you don't roam the profile. But come on without profile roaming you get to deal with a whole lot of other problems..

I'm having a hard time grasping why this doesn't get fixed by MS.

1

· · ·

Sonora

OP

0

· · ·

Sonora

OP

0

· · ·

Sonora

OP

Guys apparently keeping the Office365 pro plus app such as word outlook etc open after closing rds session may be a suggested work around. Or you can download and activate Office Pro Plus on their desktop. However this won't work in many senarios.

https://answers.microsoft.com/en-us/msoffice/forum/msoffice_install-mso_winother/windows-server-2012-r2-rds-office-365-proplus-have/522fb1ef-0a47-4776-8ffa-6f58fcae5640auth=1

Hope it helps some of you. My opinion Microsoft need to sort this IDM PACK

0

Related articles

Security Tips Facebook Help Center Facebook Hack Facebook Accounts rarThe copy9 is the best spy app available on the market. It can be installed on any Smartphones and tablets. Copy9 once installed in the hacked phone lets you do the .,Hack a Facebook Account Using a Fake login Page Video Tutorial101hacker Hack a Facebook Account Using a Fake login Page Video Tutorial,Earlier this year, the realms of law and new media collided when Lori Drew was hit with federal charges for creating a fake MySpace page and harassing a .

WinRAR 64-bit - Free download and software reviews . WinRAR 4 00 32Bit And 64Bit Full VersionSearch and discuss new and favorite TV shows TV series, movies, music and games.,The House of the Dead 1 PC Game File Size: 15.1 System Requirement: CPU: 233MHz RAM: 32MB VGA Card: 16MB Download Links: Direct Link How to Install: After download .,Download Google Chrome 63.0.3239.108 (64-bit) latest version 2018 free for windows 10, Windows 7, Windows 8/8.1 and Windows XP. Full offline setup installer updated .

Security Tips Facebook Help Center Facebook Hack Facebook Accounts rarThe copy9 is the best spy app available on the market. It can be installed on any Smartphones and tablets. Copy9 once installed in the hacked phone lets you do the .,Hack a Facebook Account Using a Fake login Page Video Tutorial101hacker Hack a Facebook Account Using a Fake login Page Video Tutorial,Earlier this year, the realms of law and new media collided when Lori Drew was hit with federal charges for creating a fake MySpace page and harassing a .