App-V & Autograph

[GSmith]

Hello, has anyone successfully virtualised Autograph?

 

Giles.

[saundersmatt]

Can't say I have. Are you using the 4.6 SP1 version of the sequencer? I've found it a lot more forgiving than pervious versions.

 

Matt

[GSmith]

hello Matt, yes we're using 4.6 sp1, the problem i'm having is that the streaming process goes fine and the app runs etc etc but when run on the station it doesn't like the .lic saying it's invalid

 

Giles.

[saundersmatt]

I'm talking complete nonsense. I have 3.10, it was sequenced by a colleague. Are you struggling with the same version?

 

Matt

[jamesfed]

We've got it running here with no issues - will take a look at the package tomorrow when I'm in and see if anything stands out.

[pritchardavid]

Same here, we have it running also (version 3.1 of Autograph) no problems. A far as I remember, it installs the product key into the registry, which as long as you don't delete any autograph or even any registry items after the software as been sequenced (advanced mode) you should be fine

[GSmith]

it also has a .lic file that it saves to all users appdata so we may have a permissions issue, going try moving it to a network share and changing the registry entries before capture.

[cscott]

We've got it running as well via app-v - create the package a while back no issues that I can recall, other then when we used to use thin clients, had to turn off the Data Execution Prevention on the terminal servers

[sister_annex]

We have it working fine here, I did the network install which creates a separate installer as per the instructions and then app-v'd the newly created one.

 

Our licence is a site one which is read from a server share UNC path.