Background: I work for an employer that uses Trend OfficeScan throughout the enterprise. I utilize VMs extensively in my environment Company policy dictates that I have to use Trend, and I am not in the group that decided to go with other vendors
That being said, Trend has a utility called ImgSetup.exe which creates a unique Trend GUID on boot from a sysprepped machine. It works well for what I need, however it only works in a x86 environment, and we are now pushing x64. If you run the utility on a x64 box, it states it only works in an x86 environment, and then errors out. I would like to know if anyone has any insight how the GUID is created. On a 32-bit box, when you run the utility, it creates an entry in the "runonce" section of the registry. The parameter created calls ImgSetup.exe, and passes in the MAC address of the machine the utility is being run on. After rebooting, you end up with a HEX formatted GUID in the registry that looks along the lines of: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx Any ideas? Klint ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
