Ive tried creating a logoff script that copies the licence key from the file server and a logon script to copy it back to the terminal server they are using at the moment.When i use my script to copy the whole Temp folder to the file server and back they dont get the activation screen, but over time the temp folders have become almost 3 gig per user.
![]() That also cause the users to have a very slow login and logon time. Office 365 Keeps Ag For Activation How To Solve ThisDoes anyone have the same issue or has a idea how to solve this Thanks. Now, its been a long time since I ran a Terminal Server, but it seems like I had the same issue one time. And IIRC, I logged in with an admin account and was able to finally get Office to activate once and for all. Now this was likely Office 2010 so obviously O365 is a whole nother animal. This is included with Office 365 E3, E5 and the appropriately named ProPlus plan. With the Business and Business Premium plans you only get the Standard version. Office 365 Keeps Ag For Activation Install Office OnSecond, you need to install Office on the server with shared computer activation, using the Office Deployment Tool. Follow this guide from Microsoft: Deploy Office 365 ProPlus by using Remote Desktop Services. So the licence and sharedlicence installation are correct by the looks of it. You need to install office from the Office Deployment Tool not from double clicking. You need to configure your config.xml to include the applications you want and the shared activation component covered in the links in Tulios post. Or when you have been set to the other terminal server as the day before. This would make a best effort attempt to login your users to Office 365 with their AD credentials automatically. Otherwise its probably time to open a support ticket, there may be some GPO or configuration specific to your environment that is interfering with activation. The question was answered already, its up to OP to implement it. My guess is that it looks too daunting so he is hoping for something simpler, which doesnt exist. This is the better way to go about it in load-balancing RDS farms. First way to configure this is on the ODT configuration.xml file: SCLCacheOverride and SCLCacheOverrideDirectory properties. My preferred way is to use GPOs, get the latest Administrative Templates here. In your list of external articles Ive seen no mention of UPD. The users on the terminal servers with Office 365 do use a UPD but it doesnt seem to do much.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |