That is debatable. It is the first time that I am aware of specifically, however, the tech showed me a similar VM that had an install but doesn't know who installed it or how it got there, so the answer is a definite maybe.
In our testing it works against machines unders the Microsoft virtualisation offerings (Virtual PC, Virtual Server and Hyper-V) but we haven't specifically tested VMWare ESX 3.5. I'm pretty much sure that this isn't the issue though - it's more likely to be related to security permissions or some other config difference.
One of the first things that the installer does is to install an "installer only" license for the CompAndSync DLL. This is necessary to make the CompAndSync component work.
Do you have another clean ESX 3.5 machine to try this on to start working out what the differentiating factor might be?
Hi, and sorry for waking a thread that's been dead this long :)
I'm currently evaluating Packager Plus as a tool to create easy to use upgrade packages to our partners and customers.
Apart from a few other issuses I'm having, I also have this problem with the packaged installer asking for a license when run. I get the license question on a couple of different Windows 2003 R2 Servers running on VMWare Workstation 6.5.3.
Later tonight I will also try the installer on a VMWare ESXi 3.5, and will report back here if the license question occur on that server as well.