Office 2019 Office 2016 Office 2013 When you install a volume license version of Office Standard or Office Professional Plus on a new PC, you might be prompted with a Let's get started screen each time you start Office. This can happen if you don't uninstall the pre-installed version of Office on your new PC before installing a volume license version of Office. To stop the prompts for activation, make sure your Office uses volume licensing and then update the registry. Verify that your Office version uses volume licensing Volume license versions of Office are typically used by large organizations. Here's how to check if your version of Office uses volume licensing. Important: This task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly.
Therefore, make sure that you follow these steps carefully. For added protection, before you modify it. Then, you can restore the registry if a problem occurs. Close the activation window and all Office apps.
Provides methods to stop Office for Mac 2011 from repeatedly prompting you to enter the product key when you start an Office 2011 application. You are repeatedly prompted to enter your product key when you try to start any Office for Mac 2011 application.
Right-click the Start button on the lower-left corner of your screen, and select Run. Type regedit, and then press Enter.
Select Yes when prompted to open the Registry Editor. On the left side of the Registry Editor, under Computer, navigate to the following key in the registry: HKEYLOCALMACHINE SOFTWARE Wow6432Node Microsoft Office 16.0 Common OEM.
Right click the OEM value and click FileExport. Save the key. After the key is backed up, select EditDelete.
Repeat steps 3-6 for the following key: HKEYLOCALMACHINE SOFTWARE Microsoft Office 16.0 Common OEM. Close the Registry Editor and start Office again.
My company has Office 365, an E3 agreement. All of our clients run Office ProPlus 2013 (the office 365 deployment). We completed our rollout in either late Feb or early March of this year. Recently, we have had an uncommon amount of turnover / new hires / department moves. I would say in the last month, we have had 4 people leave the company, 3 new hires, and someone change departments.
In most of these situations, the machine was not wiped clean and started fresh, simple because the new people / transfer were basically replacing the people that left. Because of this, the office 365 installation on these machines was originally activated under the accounts for the person that left.
The past 2 days we have had issues with these people opening an office app, and it says that it couldn't activate. When we try to enter in credentials again (We use Dirsync, with no ADFS), it says there was a problem with the account. We end up having to run an onilne repair, which takes sometime and is very inconvenient to get it to work again. Can anyone shed some light as to what is going on here? All of my office activation problems have been resolved by closing all office applications and either going into any office application (it doesn't matter which one just make sure it is the only one running) and going to file Office Account and logging out the current user and logging in the new one. If that doesn't fix it close the application and right click and run as an administrator and then do the same thing. I have not noticed any problems related to the original office accounts license status.
Just as long as the new account has an E3 it works. My company has a lot of turn over and new hires so I am very frequently changing the users associated with the office pro plus install and I have not encountered any client side problems that those two steps haven't resolved. I hope that helps. Ok, I think I have this one figured out. I had a GPO setting set called 'Block Signing in to Office' (User SettingsAdmin TemplatesMicrosoft Office 2016Miscellaneous). Once I set that to not configured, I am now able to start and activate Office without admin privileges and without anything freezing. I had originally set that GPO because I didn't want anyone to be able to access OneDrive or SharePoint online directly from the Office apps since we don't use them at all.
The description of the GPO said that the setting doesn't affect the ability to license/activate the product, but clearly it does since when I had the setting Enabled, the Activation dialog box would say 'This setting has been disabled by your administrator'. In earlier version of Office ProPlus, when I ran an Office app without admin rights before activation, the Office app would just crash with no useful error message.
If I ran the app as an admin, it would allow me to activate, so I just assumed admin rights were required for activation. More recent versions do not crash and show the dialog box with the message I mentioned. That is what finally led me to this setting. Thanks for the help. Yeah - my process is similar. I disable the account and move them to a Disabled Users OU. With my dirsync, I filter out what is actually sync'd - and I don't include that Disabled OU.
This ends up in the user being removed from our Users in the O365 portal. They get moved to the Deleted users area. I believe they are kept there for 30 days, and automatically removed. That being said, I just checked one of the deleted users and it still shows a license tied to this user.
Very interesting. I may have to modify my powershell script to disable the user and remove the O365 license.And see what happens. All of my office activation problems have been resolved by closing all office applications and either going into any office application (it doesn't matter which one just make sure it is the only one running) and going to file Office Account and logging out the current user and logging in the new one. If that doesn't fix it close the application and right click and run as an administrator and then do the same thing. I have not noticed any problems related to the original office accounts license status. Just as long as the new account has an E3 it works.
My company has a lot of turn over and new hires so I am very frequently changing the users associated with the office pro plus install and I have not encountered any client side problems that those two steps haven't resolved. I hope that helps. Thanks for all of the wonderful input. Unfortunately (really?!?) I haven't had this issue pop up since my original post. Out of curiosity, in your environments, are you running just dirsync or ADFS? I know it is out of the scope of this original post - but, we are looking at ADFS for other (exchange) related concerns. But I think I have seen where, if we do use ADFS, our users should never be prompted for any activation of O365 - it just knows because of the federation?
Any idea if this is correct? Thanks again guys! We are currently only running Dirsync.
While testing ADFS and Centrify for a single sign on agent all of my test systems running office365 pro plus kept requiring me to 'Verify' who I was so I had to enter my office365 credentials some times multiple times a day even though I was not being logged out. Because of this we just opted to go with DirSync. My opinion is ADFS is overly complicated and to expensive to not have single points of failure. Centrify makes a ADFS cloud solution that is much easier and is free (or it was) So I would consider that if you are considering ADFS.