Autograph 3.3 Virtualized

[funscott]

Hi dont worry we have a site license.

We have 3.02 running virtualized using microsoft application Virtualization (works a treat) and saves a lot of time installing onto desktops/upgrades etc. our problem is we now have version 3.3 and are in the process of making all out application available this way. but 3.3 doesnt want to play. we can create the sequence on our software build machine (vmware desktop) and we can active the site license. however once we finalise packing the app and deploy we get unregistered version. Is there a pre build OSD for this or a method of installing a site license version without requiring contacting an activation server / network share?

thoughts on a post card

[Stephen_Whipp]

Hi,

There are a few possibilities here

1) You are using the licencing service built into your virtualisation software as you would have for 3.02. Autograph 3.3 has its own licencing system which does not and cannot make use of the built in systems of such. You need to setup our licence using the admin install as described in steps 1-15 of our network installation guide as found on http://www.autograph-maths.com/downloads...ws/network
you can then virtualise the resulting admin package to install Autograph

2) The admin install hasn\'t successfully activated the licence this can be down to a number of things. The most usual pitfalls are that
a) the instakllation has been run with a remote server as the target for the licence share. The current installer doesn\'t support this, it is required to run locally on the licence server and the path to the share should be a local path, not a mapped drive.
b) The permissions on the licence share do not provide read/write permissions for everyone who needs to run Autograph
c) the virtual machines haven\'t picked up the registry location during installation. This is located at HKLM\\Software\\Eastmond Publishing Ltd.\\Autograph\\Version 3.20\\LicenceLocation. Where LicenceLocation is string value containing the UNC path to the share. A mapped drive reference here would probably work, but we recommend giving the precise path to the share itself.

I hope this helps