While attempting to activate your Office 2010 clients in your environment you find that some of your machines fail to activate against KMS with the following ERROR CODE: 0x80070005. Feb 27, 2017 - I have been trying to figure out how to deploy Office 2016 for Mac to the students. It will install the Office suite and also be activated and not require it. For the first time with a network account and launching Word or Excel you get. The serializer to run after imaging to make sure it would need activation!
Hi, Regarding of the issue, please provide us more information to assist you better. Which version Of Office do you use?
Office 2013 or Office 2016 for mac. How did you activate the Office via Volume License?. Was there any error message? As far as I know, the Volume Licensing customers will be able to download Office 2016 for Mac from their Volume Licensing Service Center in early August.
If you use Office 2016 for Mac, I recommend you give a call to Volume Licensing Service Center and they'll help you re-activate Office 2016 for Mac If you use Office 2013, please try to use the following methods: Use the Office Software Protection Platform script ( ospp.vbs) to check the states of Volume License first. You can then run ospp.vbs /ddescr together with the error code to see the text of the error message.
The text will help you better understand the issue and what to do to fix it. Another way to obtain an error code is to run ospp.vbs /act on the client computer to manually activate Office. If activation fails, an error code will be shown.
Reference: If you have any update, I'm glad to help and follow up your reply. Regards, George Zhao TechNet Community Support It's recommended to download and install, which is developed by Microsoft Support teams.
Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office programs. Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]. Hi, Regarding of the issue, please provide us more information to assist you better. Which version Of Office do you use? Office 2013 or Office 2016 for mac. How did you activate the Office via Volume License?.
Was there any error message? As far as I know, the Volume Licensing customers will be able to download Office 2016 for Mac from their Volume Licensing Service Center in early August. If you use Office 2016 for Mac, I recommend you give a call to Volume Licensing Service Center and they'll help you re-activate Office 2016 for Mac If you use Office 2013, please try to use the following methods: Use the Office Software Protection Platform script ( ospp.vbs) to check the states of Volume License first.
You can then run ospp.vbs /ddescr together with the error code to see the text of the error message. The text will help you better understand the issue and what to do to fix it. Another way to obtain an error code is to run ospp.vbs /act on the client computer to manually activate Office. If activation fails, an error code will be shown. Reference: If you have any update, I'm glad to help and follow up your reply. Regards, George Zhao TechNet Community Support It's recommended to download and install, which is developed by Microsoft Support teams.
Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office programs. Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]. Unfortunately this doesn't work. All the apps still have the little bar saying 'Activate Office to create and edit' and then want you to buy it or sign in to an account that has bought it. The only fix is removal and re-install.
No idea why this is happening on clone, and only in about 50% of instances. However, it does seem to be a new issue, so I'm kinda banking that one of the updates in the last 3 weeks caused this problem which is now preventing cloning systems.
In which case, this is a serious impact to our workflow and will cost us a ton of time manually installing and updating Office on every system we deploy. If MS actually changed the licensing to prevent cloning, that's a massive backhand to IT everywhere. The problem has nothing to do with which version of the OS you're running. I've observed it in Yosemite, and several subversions of El Capitan. The problem is caused when two conditions are met: the user must have Outlook365 as his/her email system, and he/she must attempt to SIGN IN to any other component of Office.
Unfortunately, When you run any component for the first time, you get a window with a HUGE Sign In button, and an itty-bitty teeny tiny fine print 'Skip this step' link at the bottom of the window (it's not even a button just a link!) Clients click the sign in button, are walked through creation of a Microsoft Account – which then realizes the client doesn't have a license for Office 365, and disables the Existing VL Office 2016. If you are already past that point, and click the login in the upper left of the New Document window, the same problem occurs. As you noted, the only fix so far is to uninstall and reinstall. I work at a major University with a Faculty and Staff numbering nearly 3000. We've been using Office 2016 without a hitch for a year – until we began transitioning staff members to Outlook365. ONLY people who've been migrated to Outlook365 develop this issue.
That's where the problem began. Microsoft needs to fix this, or my full-time job will be uninstalling and reinstalling MS Office!
The reddit for Mac Professionals. Please keep all content and discussions professional. Community Resources. ##osx-server on. Useful Tools.
Make OS images. Third-party update retrieval. Manage AutoPkg with a GUI.
Mac imaging. OS.pkg installer. User creation.pkg.
Reposado GUI. Software Update deployment.
Manage Munki with a GUI. Munki reporting. Easily do stuff at login/boot. Advanced packaging Tool.
Cache Apple software updates. Package Analyzer. At my work we're using a volume license to activate Office 2016 for Mac. The way we install office is downloading the entire Office installer from Microsoft's website here: We then push it out to clients via Munki. In order to activate office we were able to use a serializer.pkg from microsoft to license / activate Office for Mac 2016 and this.pkg has worked up until 16.16. Today, I noticed that updating to 16.17 via our normal method prompts the user to activate MS Office again and our serializer.pkg isn't working.
![]()
Is anyone else having issues the same issue or have advice? Thanks in advance.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |