Solved

vSphere Cloning Windows 7 Guest Customisation vSphere 5

Posted on 2012-04-05
8
1,300 Views
Last Modified: 2012-05-09
I am trying to clone a windows 7 VM and configure the guest using a script specified in the guest specification manager. I am trying to set the name of the computer to be the same as the VM (works fine) and add the computer to our internal network domain. I have filled in the domain Administrator username and password [and I have set the username to be Administrator @XXXX.com (fully qualified domain Name) and the domain login to be <user>@domain_FQDN].
Once the cloning processes completes,  I turn on the network adapter and start the VM and then windows goes through a setup process (windows shows Setup is Applying System Settings) at the end of which I am logged into the system automatically (presumably this uses the Administrator account details that i supplied in the Guest Specification manager script) . I can see that the computer name has been changed to match the VM, but the domain hasn't been changed, its still on the default workgroup WORKGROUP.  I can go in and add the computer manually to the domain but of course this is what I am trying to avoid. Any ideas what I am doing wrong or where I could start looking? I dont see any errors in the C:/windows/TEMP/vmware-imc/guestcust file. The vSphere logs dont show up anything either.

For a start, should the first restart post cloning be connected to the network or not?
0
Comment
Question by:johnwryan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
8 Comments
 
LVL 120
ID: 37810277
Have you made sure that you are specifify the domain credentials correctly, with an account that has access, to join the computer to the domain.

there is no need to specify Admin username and password to login automatically, unless you have a requirement to do so.
0
 

Author Comment

by:johnwryan
ID: 37810393
Hi, the Account I am using is the domain Administration account. I can go in manually after the cloning process is complete and manually add the VM to the domain. I am supplying the domain administration account in the format Administrator@XXX.com i.e. the fully qualified name. I will remove that auto login.
Is there any place that I can see some sort of log that would tell me what is going wrong?
0
 
LVL 120
ID: 37810598
guest customization log, should provide information.

use <domainname>\username format
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 

Author Comment

by:johnwryan
ID: 37810778
ok I did change to <domain>\Administrator. Performed a clone. Started the VM up, was able to login with localhost Administrator and I could see that the Computer name was an automatically generated Computer Name. I rebooted and Windows setup went through a customisation process. When that was complete I could not login with either <Domain>\Administrator or with the local Administrator account, in other words the VM was useless to me as there was no way of logging in. (and of course I cant get to see the customisation file). Should I be connecting to the network at the first reboot after cloning or should I be waiting until the second or does it matter?
0
 
LVL 120
ID: 37812512
You need to wait for the process to complete.

When the Server Boots, it will execute a schedule task script, and run the process to change VM name, and then join domain.
0
 

Accepted Solution

by:
johnwryan earned 0 total points
ID: 37831525
I have resolved this issue. The process had completed alright. I found a log file in C:/windows/Debug called NetSetup. This file seems to log all the attempts made connecting to the Domain etc. In this file, you can see that it was failing to join the domain because of the domain name and/or login credentials. In the case of the domain name I was using the fully qualified domain name. For anyone looking at this sort of problem in the future, I suggest the following 2 links -

http://social.technet.microsoft.com/Forums/sa/mdt/thread/6b634900-78d6-418d-86c6-c369a01e373e

http://communities.vmware.com/thread/230610 - This  gives a good overview I think of the process that is gone through under the hood by vSphere when it is performing the guest customization

I notice that in a number of places including a vmware KB article that its stated that the FQDN should be used for the  account used to add the computer to the domain for Windows 2008 but also tits states that this applies to Windows 7 . I found this not to be the case for me but then perhaps this has something to do with the network setup. In our case I was connecting a Windows 7 computer to a windows 2003 domain.

Thanks for your assistance.
0

Featured Post

To Patch or not to Patch? That is the question!

Don't get caught out like thousands of others around the world in the recent Ransomware Fiasco!
Discuss..
- Why it's not a good idea to wait before Patching
- Sensible approaches to Patching discussed
- Add your feedback, comments and suggestions

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
VPN  services - questions and recommendations 7 56
Outlook 2016 processing loop 4 49
VMFS datastore running very slow ? 18 85
Scripting 4 33
Giving access to ESXi shell console is always an issue for IT departments to other Teams, or Projects. We need to find a way so that teams can use ESXTOP for their POCs, or tests without giving them the access to ESXi host shell console with a root …
The Windows functions GetTickCount and timeGetTime retrieve the number of milliseconds since the system was started. However, the value is stored in a DWORD, which means that it wraps around to zero every 49.7 days. This article shows how to solve t…
This Micro Tutorial walks you through using a remote console to access a server and install ESXi 5.1. This example is showing remote access and installation using a Dell server. The hypervisor is the very first component of your virtual infrastructu…
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question