My copy was the volume license edition downloaded from MS VLSC. The VLSC says there is no key required, but deploying the msi files alone via GPO results in an installation with no product key on a 60-day trial period.
I referred to the notes posted for Expression Studio 3.x. The process is basically the same but the file names have changed.
The correct key is in the WebStudioManifest.xml file, which is in the WebStudioManifest.cab file. The key is the value of the PROOFOFPURCHASE property.
Use Orca to open the Web_en.msi file and create a .mst file. Create an mst file to overwrite the exisiting PROOFOFPUCHASE value with the key found above.
Use GPO to deploy the Web_en.msi and Design_en.msi with the .mst file to change the key.
My 4.x copy comes from package requestor, and I could not find the WebStudioManifest.cab file. Instead, I found it in ExpressionStudioManifest.cab. All the rest is the same.
Apply this PROOFOFPURCHASE Property to any .msi files that would request a license. After install, you will notice they're fully licensed.
Questions & Answers related to Microsoft Expression Studio
Blogs (0)
Blog posts related to Microsoft Expression Studio
Links (0)
Links related to Microsoft Expression Studio
Reviews (0)
Reviews related to Microsoft Expression Studio
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ
