Sheridan Posted September 18, 2018 Posted September 18, 2018 We've got a base image with CS6 on it - since deploying it with a new W10 image users are always prompted to 'Sign In' when they first run any of the applications (not CC just local apps)I've tried the Adobe Licensing Fix Tool, and also created a Serialize package with AAMEE but neither have worked, is this a sign I'll have to reinstall every single one? (about 50!)
3s-gtech Posted September 18, 2018 Posted September 18, 2018 I did get this with our first deployments on Windows 10. I made sure that my serialisation package was okay, then ran the serialise too on startup using GP: \\server\shares\cs6\serialization\AdobeSerialization.exe --tool=VolumeSerialize. No problems since.
Jawloms Posted September 18, 2018 Posted September 18, 2018 Got Impero? If so, I did all mine using a mimic script.
Sheridan Posted September 18, 2018 Author Posted September 18, 2018 No impero, but I'll try running it as a batch file on startup to see if it sorts it before the users log in
Sheridan Posted September 18, 2018 Author Posted September 18, 2018 (edited) This is weird - if I run this directly in a command prompt I get 'Return Code=0' in the log file which I guess means its worked: "\\server\Adobe CS6 2018\Adobe CS6 Serialise\Serialise\AdobeSerialization.exe" –-tool=VolumeSerialize –-provfile="\\server\Adobe CS6 2018\Adobe CS6 Serialise\Serialise\prov.xml" > "\\server\Adobe CS6 2018\Adobe CS6 Serialise\Serialise\log.txt" However if I paste that into a batch file and run that I get 'Return Code=1' and it displays the Usage list (I can see this if I run the batch file from the command line) Have I got the syntax wrong somewhere along the line here? Edited September 18, 2018 by Sheridan
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now