Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Troubleshooting SCVMM 2012 SP1

Windows Customization did not finish successfully

The reason could be, one of the customization parameter is wrong. There could also be multiple reasons to it:

  • The License key specified is not correct.
  • Template was not created properly. Make sure that it is sealed.
  • The customization is taking more time than configured in scvmm.conf.

To resolve the time issue, change the following parameters in scvmm.conf to:
CustomizationSleepTimeSec=240, CustomizationRetryCount=20

For troubleshooting purposes, the best way is to:

  • Set a flag within the scvmm.conf file within the <RSCD-DIR>/daal/Implementation/BMC_SCVMM_win64/win64 directory on the SCVMM server.
  • Change the following setting - set RetainVMInCaseOfCustomizationFailure=true and collect setupapi.log inside the VM for more troubleshooting.

How do I verify the contents of the sysprep / unattend file being passed

There are a few ways one can access the sysprep / unattend file. These are mentioned below: While the Virtual Guest Job is running (during customization of the Guest OS), one can browse to <RSCD-DIR>/daal/Implementation/BMC_SCVMM_win64/win64 directory on the SCVMM server, and look for a temp directory with the VM's name within it. The sysprep / unattend file would be present in this directory. You can copy this into a different directory for analysis

⚠️

Warning!
The temporary directory, along with its contents, is deleted as part of the job. Thus one might want to copy it while available

During customization, Static IP settings are not being applied to either one or all of the NIC's on the target VM!

Double check the procedure for creating the template. We have seen that templates which have not been created properly / those that have been started post the sysprep seal give this problem. Create a new Template from the new VM and try again

Windows 2008 R2 customization not working - Hangs with message - "setup is updating registry"

Product key is wrong, provide correct product key and try again.

Windows 2008 domain join not working

Check the credentials used for domain join, make sure that user name is now <domainname>\<admin user>, it should be just <Admin user>

Network Issues One physical NIC of a Hyper-V host is trunked to two VLANs (one VLAN is assigned to one VM Network, and another is assigned to one more VM Network).Both these VM Networks are connected to a physical NIC of the host

When you provision a Linux guest using a template with 2 NICs with the above given configuration, it just picks up one VLAN and assigns an IP address and the other NIC doesn’t exists post that. Resolution:You need delete the normal network adapters from the source template and add the legacy network adapters to it.
 OR In the VGP/VGJ, Advanced tab, you need to select the NIC type as "Emulated".

Network Issues The NIC of the VM gets to status Not Connected, when you provision a VM with VM Network and VLAN ID assigned to it. Due to this issue the CLM provisioning job fails

The VM Network must be configured to use the VLAN. In the Logical Network properties associated with this VM Network, under Network Site, provide the VLAN details to be used. See the screenshot below.

Network Issues Cannot ping to Windows/Linux VMs from outside

There could be multiple reasons for it. check if:

  • Firewall is off (for linux iptables & selinux)
  • The VMNetworks are functional
  • If ping by IP works but by hostname/ fqdn doesn’t work mostly its DNS issue. flush dns, register dns and try ping again
  • If IP points to some random hostname or vice versa, it can be DNS caching issue.
  • If IP is not assigned at all to VM, problem can be with DHCP server/configuration files in template are not proper.
  • If static ip is assigned & ping doesn’t work, we should verify IP was working before. Nslookup should confirm mapping with hostname even before we deploy VM.
  • DNS & domain name should be both auto or both static. Else ping doesn’t work. (for linux VMs)
  • While pinging from outside network, sometimes, domain name of VM is not added in outside network’s machine’s DNS search list.

VGJ Job failed with following error - “Error while creating NIC Exception in Powershell Invoke - Unable to find a default VMNetwork for Logical Network (<Switch name>) (Error ID: 25163); Please specify a VMNetwork or create a VMNetwork of type NoIsolation for the logical network”

VM Network is not configured. Make sure that there is at least one VM Network with NoIsolation type.

VGJ Job failed with following error - Error while creating Template based VM The specified virtual switch does not exist. Virtual switch: <Switch name> #34 - Virtual Switch

Template has a switch which does not exist any more.

If VM joins domain, ping is possible with <hostname>.<domain>. It does not ping  only with <hostname>

Ensure there is a IP versus Hostname entry in DNS Server. Only then hostname resolution works.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*