This entry is part 3 of 3 in the series Sequencing Adobe CS6 for App-V

With any luck if you have followed the previous instructions to the letter you should now have a perfectly working App-V package for any of the Adobe CS6 applications, to confirm that the licence is applying correctly you should see a command prompt window appear just before any of the Adobe applications load just as you see in the series of screen shots above.

So the question that everyone is asking – how on earth does this work?

Well basically….
The script that we included in the OSD file tells App-V to run a mini application that licences the Adobe Application every time it launches. This in turn overcomes the way that CS6 binds its self to a machines hardware ID when licenced.

So simple really! If you are having more problems with getting Adobe stuff through App-V check those prerequisites again as this is a common cause of issues!

VN:F [1.9.22_1171]
Thumbs up if this article helped you 🙂
Rating: +6 (from 6 votes)
Sequencing Adobe CS6 for App-V – Part 3, the testing/how/why, 100% based on 6 ratings
Series Navigation<< Sequencing Adobe CS6 for App-V – Part 2, the sequencing

5 Responses to Sequencing Adobe CS6 for App-V – Part 3, the testing/how/why

  • Lost says:

    Any recommendations if we aren’t seeing that command prompt window appear? I can’t get it to work for the life of me…

  • zx6dude says:

    Thank you. Very helpful.
    I’m using HREF instead of SCRIPTBODY as HREF does not need to create a temporary .bat file on the App-V client and in theory it should be more efficient due to that. I also use the utility HSTART to hide the activation script, that way users do not see the command prompt window pop-up. HSTART will not work if SCRIPTBODY is used as the command prompt comes up anyway.

    Thank you again, you saved me a lot of investigating.

Leave a Reply to Greta Cancel reply

Your email address will not be published.