Disk Imaging

[cmabie]

Any special requirements when deploying by disk imaging?  Most programs have a command line, or other tool for unique registration with command and control servers.

[Che Johnson]

What console are you using?

[cmabie]

What console are you using?

I'm using the AEA " avast enterprise administration" console, but do the different console types have an affect on disk imaging?

[jhowzr]

We are using the EA console too and are preparing our images for deployment this summer. Could you tell us, please, is there a command line application or procedure we need to do to "generalize" our client install for imaging?

Our idea is to include the customized avast workstation setup package in our base image, sysprep it, and then take a disk image of the system. Will it cause issues with our enterprise console when the computer comes online post imaging? My fear is that it will have a unique identifier associated with the original computer and that we'll be duplicating that identifier to all subsequently imaged machines.

Thank you for your help.

[steveinbuffalo]

We've been doing this.  It appears to grab a new license under the new machine name.. but you can get multiple used if you do something like come up as a workgroup machine, then join the domain while avast is installed.. you end up with 2 entries and I assume 2 licenses in use in the server.  It seems to clear if you delete the dupes from the console.

[zlloyd]

We are interested in the proper procedure as well.  From what I've read in the other forums, one must run "aswimgpr.exe" prior to imaging in order to clear the GUID.  I cannot find that executable, however.

[zlloyd]

It appears Windows XP machines can be imaged with no problem.  However, after imaging two Windows 7 machines, only one of them showed up in the administration console and the IP address of that entry swapped between the two computers.

How do we clear the GUID prior to imaging?