Our SCCM team has been tasked to deploy Acrobat Standard in an automated package. Unfortunatly someone bought 280+ individual licenses and each one is a different license key. This is also 280 different locations which would make manual installation even more difficult and time consuming. Not cost effective at all.
When customizing the package in Acrobat tuner, we left the license key out thinking we could have the end user punch that in upon 1st run. This is not the case - the installer fails with error code 1603 because the key is blank.
Is there a correct way around this?
Regards,
Dave
1
Reply
AdChoices