Skip to main content

Office 2013 users are getting PoP up to upgrade to office 2016


Perhaps the purpose is to prevent the users from receiving banner to upgrade to Office Pro Plus 2016?

If yes, following steps by modifying registry could help to achieve this.

Kindly help to run Regedit from windows search box to open Registry Editor.

Please help to go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun\Updates

Please locate registry key UpgradeAdvertised and change its value to 0

If perhaps this registry key cannot be found, please help to create a new one with UpgradeAdvertised as its name and enter 0 as its value.


User computer may need to be restarted to make this configuration effective.

 I have done some research, here are some articles I found for your reference:

keep on running Office 365 ProPlus 2013
https://support.microsoft.com/en-us/kb/3097292

Turn off the "upgrade to Office 2016" or "get the new Office" pop-up notification 

 https://support.office.com/en-gb/article/Turn-off-the-upgrade-to-Office-2016-or-get-the-new-Office-pop-up-notification-1f32be31-5aea-42bb-ba3e-c753fc748d8b?ui=en-US&rs=en-GB&ad=GB



Labels:

Comments

Post a Comment

Popular posts from this blog

Error - QuarantinedAttributeValueMustBeUnique

Case History. 1. Client already had users created in office 365 2. Client wanted to setup SSO for office 365 users Approach for requirement fullfilment   1. Deployed and configured Azure AD connect      95% users were synced and soft match was successfully done  5% users were getting error - QuarantinedAttributeValueMustBeUnique  (to view the sync issues -  https://aad.portal.azure.com/#blade/Microsoft_Azure_ADHybridHealth/AadHealthMenuBlade/SyncErros )  When we checked 2 users were found under Active users  1. one in Cloud (this was created earlier/ already existed ) with active licenses and Mailbox 2. one unlicensed synced with AD Solution - 1. Delete the unwanted user in Azure or AD as per this document.  https://blogs.msdn.microsoft.com/hkong/2017/03/23/how-to-fix-attributevaluemustbeunique-error-message-when-trying-to-sync-an-object-from-on-premises-active-directory-to-office-365/ ...
Post a Comment
Read more

Error - AttributeValueMustBeUnique in Azure AD connect sync

My customer had already created accounts in office 365 and managing them in Azure, however due to some changes in business they wanted to sync AD with Azure to sync Password and Manage Identity form AD. Solution - Deploy Azure AD connect on ADDC, and post that it will do a Soft Match. However there were error with some users, their identities did not sync and their status still reflected as Azure AD. Error -  Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services: [ProxyAddresses SMTP:user@domain.com;].  Correct or remove the duplicate values in your local directory.  Please refer to http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values. Tracking Id: b8367c95-ae67-46e1-xxxx-xxxxxxxxxx ExtraErrorDetails: [{"Key":"ObjectId","Value":["cd088468-bb6a-4...
4 comments
Read more

Microsoft office 365 product shows as not activated after few days.

Solution Opened CMD Navigated to Path - cd C:\Program Files (x86)\Microsoft Office\Office16\14\15 To view the installed product key, execute cscript ospp.vbs /dstatus To uninstall an installed product key, execute cscript ospp.vbs /unpkey:XXXXX Replace the XXXXX with the last five character of the currently installed product key (found in step 3). Last 5 digits only To activate Office with the new product key, execute cscript ospp.vbs /act
2 comments
Read more