- #ADOBE ACROBAT 2015 CUSTOMIZATION WIZARD SERIAL#
- #ADOBE ACROBAT 2015 CUSTOMIZATION WIZARD SOFTWARE#
- #ADOBE ACROBAT 2015 CUSTOMIZATION WIZARD CODE#
So if you want to have a Dutch Acrobat installation, purchase a Dutch license (licenses in other languages appear to be more expensive then native English). If you have supplied alternative languages in the Adobe Acrobat Customization Wizard DC, you will need to provide and purchase a license in the desired language. However there was one oddity happening which we have recently discovered. This situation resolved the activation issues with the customer. The activation is machine based, however make sure people cannot start Adobe Acrobat more times then you have licenses for. This will resolve the “sign-in required” screen in your user sessions. We have created a job that after every boot or reboot the command line above is executed against every machine Adobe Acrobat is installed on.
#ADOBE ACROBAT 2015 CUSTOMIZATION WIZARD CODE#
The command line to use the prov.xml is: adobe_prtk.exe” –tool=VolumeSerialize –provfile=”prov.xml” –streamĪgain if everything is successful the Return Code will be “0”. This “prov.xml” file on it’s turn can be used to stream the activation of Adobe Acrobat against machines that are non-persistent such as a VDI work-space, Citrix XenApp MCS or PVS etc. After running the command above a prov.xml is generated.
#ADOBE ACROBAT 2015 CUSTOMIZATION WIZARD SERIAL#
To do this we will need the following things: Now we where able to activate and stream the license (that’s the way Adobe works) to the machines.
#ADOBE ACROBAT 2015 CUSTOMIZATION WIZARD SOFTWARE#
So after a quick chat with Adobe support and the software distributor, the client purchased a volume license based on the English language (since this was cheaper). Adobe is software that cannot be easily fooled around with (which is a good thing from a anti-piracy standpoint). This solution can be found by using adobe_prtk.exe which is part of the Adobe Provisioning Toolkit.įirst of all we discovered the customer had a single user license, which will get you nowhere if you want to activate the product for multiple users. This to me is just unfeasible in a SBC or non-persistent environment, I guess that’s why this application gets packaged into a Microsoft App-V or VMware thinapp so often.īut since we haven’t got these tools to our possession we needed a different solution. Upon starting Adobe Acrobat, the program closes itself and you are prompted with the following screen: Using a product such as Adobe Acrobat DC requires activation for every single user that uses it, perhaps you have encountered it before.
Lets just say Adobe isn’t that keen on using its software in a SBC environment or VDI infrastructure. Or you might say they still have the perception of the traditional stand alone work-space. So, yeah recent events at a customer lead me to writing this article for my own purposes of documenting what I did and sharing this with you to prevent the frustration I’ve encountered.