

- HOW TO ACTIVATE MICROSOFT OFFICE 2016 ON NEW DELL COMPUTER HOW TO
- HOW TO ACTIVATE MICROSOFT OFFICE 2016 ON NEW DELL COMPUTER INSTALL
Entering the product keyĪs part of that installation, you’ll have to enter the product key. You won’t uninstall Office from computer A just yet.
HOW TO ACTIVATE MICROSOFT OFFICE 2016 ON NEW DELL COMPUTER INSTALL
First, install Office on computer B using that original media. So, let’s assume that Office 2010 is on computer A and you want it on computer B. You will need the original installation media that you used to install Office 2010 the first time. You’re allowed to have Office installed on one computer at a time. "%ProgramFilesPath%\Microsoft Office\OfficeXX\OSPPREARM.EXE"Ĭ:\Windows\system32\cscript.exe "%ProgramFilesPath%\Microsoft Office\OfficeXX\ospp.vbs" /act set ProgramFilesPath=%ProgramFiles(x86)%Ĭ:\Windows\system32\cscript.exe "%ProgramFilesPath%\Microsoft Office\OfficeXX\ospp.vbs" /act REG ADD "HKLM\Software\Microsoft\Office\XX.Most licenses allow you to do pretty much what you’ve described. Reg query HKLM\Software\Microsoft\Office\XX.0\Common\OSPPREARM if %errorlevel%=1 (goto RUN) else (goto END) In this script, replace XX with the appropriate value, based on your Office version: You can run the following startup script on these computers to rearm Office and generate new, unique Office IDs. Rearm a volume licensed version of Office that's included in an operating system image.
HOW TO ACTIVATE MICROSOFT OFFICE 2016 ON NEW DELL COMPUTER HOW TO
This indicates that the Office rearm was skipped even though the base operating system image may have been generated.īefore Sysprep prepares the image, make sure that you run one of the following commands, based on your Office bit version, to guarantee a unique Office CMID.Ĭ:\Program Files (x86)\Microsoft Office\Office16\ospprearm.exeĬ:\Program Files\Microsoft Office\Office16\ospprearm.exeįor detailed information about how to rearm the Office installation, see the following articles: In this example, notice that Ignite5 and ignite1 have the same CMID (930bd202-a335-4c7e-bd9d-7305361f0d37). For example, you see entries that resemble the following: If you've more than five computers that are trying to activate, and you still see this error message, check the KMS host logon Event Viewer on the KMS server. Therefore, computers may have the same client computer ID (CMID) for Office. If you use System Preparation (Sysprep) in your environment, it's possible that Office wasn't rearmed before the image creation. When the Office KMS pool contains five or more client computers, try to activate Office by using the Office activation wizard, OSPP.vbs, or VAMT. If the Office KMS count value is less than 5, Office clients won't activate. Search for Office to find your Office KMS host installation details. Go to c:\temp (or any custom location where you put the output), and then open KMSInfo.txt. To determine how many client computers are currently in the Office KMS pool on the KMS host, run the following command in an elevated Command Prompt window from c:\windows\system32, and then press Enter:Ĭscript slmgr.vbs -dlv all >c:\temp\KMSInfo.txt
