POSTED ON November 22, 2022 12:24 am
Office 2019 KMS Activator Ultimate 1.0 Serial Key
the office activation script is then run as a batch job or manually by you. once the office activation script is run, the office activation components will be initialized and the appropriate activation code will be inserted and the necessary files will be generated and placed on the desktop, if not already there, in the following locations:
the office kms activation components need to be reinitialized if the office 2013 kms activation code is changed. the office kms key and activation is replaced with the office kms key and activation. the office activation components will be reinitialized and the office activation code will be replaced. all the files generated in the office 2013 activation process must be replaced and re-generated. if you are re-generating the files, you must also set the new office activation code.
the office 2019 kms activator ultimate 1.0 will create two files, one in the kmsdir folder and one in the scripts folder. the kmsdir file tells our startup script to run officeactivate.cmd. the one in the scripts folder tells it to do the office365 stuff which is really just replacing the store.
if you will choose not to activate using a script and the version of the office product you want to deploy is different from the version your installer installs by default, you can change the version using the ospp.vbs script (office software protection platform).
for example, to change the visio premium version installed by the visio installer to visio 2010 pro use the kms key for that version and run the following cmd at an administrative cmd prompt:
c:program filesmicrosoft officeoffice14ospp.vbs /inpkey:7mcw8-vrqvk-g677t-pdjcmq8tcp
this will change the version of visio to visio professional so that the first time it is set and activated it will work. if the first application fails, our testing shows that further activation can fail as well.
the citrix office activation script (officeactivate.cmd) has all of these commands built in for all office products using office 2010, office 2013 and office 2016. use the appropriate command for your situation.
these scripts are available in the gold image tools version 5.x and later.
if you are using these tools, just run the app layering optimization builder utility and choose which office applications are installed in the layer. the script will handle entering the product key and activating all the office applications included in the layer.
use gpos to configure user settings. user settings are not captured in an application layer.
licensing can be automated using the ospp.vbs script. it is recommended that you read the script in order to fully understand what it is doing. when using the ospp.vbs script you must make sure you have a full understanding of the script, the xenapp and windows components that it uses and what they need to be configured correctly. the ospp.vbs script will replace the following:note: office 365 has a ‘disabling fast start’ setting. this will prevent the installation from having a startup experience as it did in previous versions of office. if you disable this feature you will need to use the /arch switch to prevent the installation of the 64bit version on a 32 bit platform. if this is not done the script will fail.in order to keep the license working properly, when using the ospp.vbs script, you must ensure that the msolservice license is registered, that the license key is correctly stored in the registry, and that the license version in the registry is not outdated. these last two items are not easily detected by the script if you are not familiar with the registry or the msolservice license service, which is why we recommend using our activator ultimate license management tool.
after installing the office applications, the office activation script will be run automatically by the app layering optimizer tool. after the script is run, the office activation components will be initialized. at this point the appropriate activation code is inserted and the necessary files are generated and placed on the desktop, if not already there, in the following locations:c:windowssystem32sppstore2.0data.datc:windowssystem32sppstore2.0tokens.dat