In order to use the virtual machines in Lab Manager on a domain you have to do some customization.
For starters – the templates themselves can *NOT* be on a domain, LM Tools will not install on a machine already joined to a domain.
If you already have a custom ISO created in Lab Manager, delete it. On the VMware Lab Manager server edit the sysprep.inf file here: C:\Program Files\VMware\VMware Lab Manager Server\Tools\LMTools\Sysprep\Win2k3
Remove the line that says “ComputerName” – this is added automatically by LM Tools when the machine is deployed. If you do not remove this line you may end up with 2 seperate ComputerName fields and only the first one will be used which may cause the machine to be named something unexpected(There is a VMware KB regarding this).
Under “Identification” remove the line that mentions workgroup and add 3 new lines:
JoinDomain=domainname
DomainAdmin=domain\user
DomainAdminPassword=password
Save the file and then recreate the custom LM Tools ISO in Lab Manager. Once that is done boot up the template and if LM Tools were already installed, un-install them, reboot and then re-install the LM Tools so that the updated sysprep.inf file will be used.
Note: This method is if you want all machines to use the same sysprep.inf file, if you only want certain (or a single) template to join to a domain you can disregard editing the sysprep.inf on the Lab Manager server, as well as deleting and re-creating the LM Tools ISO and instead edit the sysprep.inf directly on the template instead. Installing LM Tools on the template is what copies the sysprep files from the Custom LM Tools ISO which is copied from the Lab Manager server at the time the LM Tools ISO is created.
Popularity: 1% [?]
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.
About mike
My Popular Posts
