dt3itsteam
asked on
VMware .vmx and windows 2003 Active Directory
Hi,
Below is a "historic" .vmx configuration file which up until USB support was added to he guest (then subsequently removed) has been experiencing Windows 2003 failing with critical DNS errors, which can only be resolved by "physically" powering off the guest image (within the vm console) and rebooting.
Historic .vmx file:-
--------------------------
config.version = "8"
virtualHW.version = "4"
numvcpus = "2"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "2048"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "master.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "auto detect"
ide1:0.deviceType = "cdrom-raw"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.wakeOnPcktRcv = "FALSE"
usb.present = "FALSE"
sound.present = "FALSE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
svga.autodetect = "TRUE"
mks.keyboardFilter = "allow"
displayName = "No-Worries SBS Server"
guestOS = "winnetenterprise"
nvram = "Windows Server 2003 Enterprise Edition.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibi
tools.upgrade.policy = "useGlobal"
scsi0:1.present = "TRUE"
scsi0:1.fileName = "slave.vmdk"
ide1:0.autodetect = "TRUE"
floppy0.present = "FALSE"
isolation.tools.hgfs.disab
ide1:0.startConnected = "TRUE"
ethernet0.addressType = "generated"
uuid.location = "56 4d b9 59 2d 6f d4 ce-2e 25 d4 54 02 7a e8 9b"
uuid.bios = "56 4d b9 59 2d 6f d4 ce-2e 25 d4 54 02 7a e8 9b"
scsi0:0.redo = ""
scsi0:1.redo = ""
ethernet0.generatedAddress
ethernet0.generatedAddress
checkpoint.vmState = ""
ethernet0.connectionType = "custom"
tools.syncTime = "FALSE"
ethernet1.present = "TRUE"
ethernet1.wakeOnPcktRcv = "FALSE"
ethernet1.addressType = "generated"
ethernet1.generatedAddress
ethernet1.generatedAddress
ethernet1.connectionType = "custom"
ethernet0.vnet = "VMnet0"
ethernet1.vnet = "VMnet2"
scsi0:2.present = "FALSE"
scsi0:2.fileName = "D:\vmware\No Worries SBS Server\slave.vmdk"
priority.grabbed = "normal"
priority.ungrabbed = "normal"
autostart = "poweron"
autostop = "softpoweroff"
workingDir = "."
autostart.order = "10"
autostop.order = "10"
usb.autoConnect.device0 = "path:1/4/6/0 autoclean:1"
--------------------------
Recreating a new .vmx file, appears (so far) to have fully resolved the AD dNS issue, below is the "new" .vmx file:-
config.version = "8"
virtualHW.version = "4"
numvcpus = "2"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "1024"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "D:\vmware\No-Worries SBS Server\master.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "auto detect"
ide1:0.deviceType = "cdrom-raw"
floppy0.fileName = "A:"
Ethernet0.present = "TRUE"
displayName = "No Worries SBS 2003 Server"
guestOS = "winnetenterprise"
autostart = "poweron"
autostop = "softpoweroff"
priority.grabbed = "normal"
priority.ungrabbed = "normal"
ide1:0.autodetect = "TRUE"
floppy0.present = "FALSE"
scsi0:1.present = "TRUE"
scsi0:1.fileName = "D:\vmware\No-Worries SBS Server\slave.vmdk"
Ethernet1.present = "TRUE"
Ethernet0.connectionType = "custom"
Ethernet0.vnet = "VMnet0"
Ethernet1.connectionType = "custom"
Ethernet1.vnet = "VMnet2"
scsi0:0.redo = ""
scsi0:1.redo = ""
ethernet0.addressType = "generated"
ethernet1.addressType = "generated"
uuid.location = "56 4d d8 a8 30 0f 38 24-e7 72 b7 43 d5 e2 d2 b3"
uuid.bios = "56 4d d8 a8 30 0f 38 24-e7 72 b7 43 d5 e2 d2 b3"
autostart.order = "10"
autostop.order = "10"
ethernet0.generatedAddress
ethernet0.generatedAddress
ethernet1.generatedAddress
ethernet1.generatedAddress
tools.syncTime = "FALSE"
--------------------------
Any obvious issues bewteen the two? Any insight would be very useful!
Below is a "historic" .vmx configuration file which up until USB support was added to he guest (then subsequently removed) has been experiencing Windows 2003 failing with critical DNS errors, which can only be resolved by "physically" powering off the guest image (within the vm console) and rebooting.
Historic .vmx file:-
--------------------------
config.version = "8"
virtualHW.version = "4"
numvcpus = "2"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "2048"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "master.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "auto detect"
ide1:0.deviceType = "cdrom-raw"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.wakeOnPcktRcv = "FALSE"
usb.present = "FALSE"
sound.present = "FALSE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
svga.autodetect = "TRUE"
mks.keyboardFilter = "allow"
displayName = "No-Worries SBS Server"
guestOS = "winnetenterprise"
nvram = "Windows Server 2003 Enterprise Edition.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibi
tools.upgrade.policy = "useGlobal"
scsi0:1.present = "TRUE"
scsi0:1.fileName = "slave.vmdk"
ide1:0.autodetect = "TRUE"
floppy0.present = "FALSE"
isolation.tools.hgfs.disab
ide1:0.startConnected = "TRUE"
ethernet0.addressType = "generated"
uuid.location = "56 4d b9 59 2d 6f d4 ce-2e 25 d4 54 02 7a e8 9b"
uuid.bios = "56 4d b9 59 2d 6f d4 ce-2e 25 d4 54 02 7a e8 9b"
scsi0:0.redo = ""
scsi0:1.redo = ""
ethernet0.generatedAddress
ethernet0.generatedAddress
checkpoint.vmState = ""
ethernet0.connectionType = "custom"
tools.syncTime = "FALSE"
ethernet1.present = "TRUE"
ethernet1.wakeOnPcktRcv = "FALSE"
ethernet1.addressType = "generated"
ethernet1.generatedAddress
ethernet1.generatedAddress
ethernet1.connectionType = "custom"
ethernet0.vnet = "VMnet0"
ethernet1.vnet = "VMnet2"
scsi0:2.present = "FALSE"
scsi0:2.fileName = "D:\vmware\No Worries SBS Server\slave.vmdk"
priority.grabbed = "normal"
priority.ungrabbed = "normal"
autostart = "poweron"
autostop = "softpoweroff"
workingDir = "."
autostart.order = "10"
autostop.order = "10"
usb.autoConnect.device0 = "path:1/4/6/0 autoclean:1"
--------------------------
Recreating a new .vmx file, appears (so far) to have fully resolved the AD dNS issue, below is the "new" .vmx file:-
config.version = "8"
virtualHW.version = "4"
numvcpus = "2"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "1024"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "D:\vmware\No-Worries SBS Server\master.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "auto detect"
ide1:0.deviceType = "cdrom-raw"
floppy0.fileName = "A:"
Ethernet0.present = "TRUE"
displayName = "No Worries SBS 2003 Server"
guestOS = "winnetenterprise"
autostart = "poweron"
autostop = "softpoweroff"
priority.grabbed = "normal"
priority.ungrabbed = "normal"
ide1:0.autodetect = "TRUE"
floppy0.present = "FALSE"
scsi0:1.present = "TRUE"
scsi0:1.fileName = "D:\vmware\No-Worries SBS Server\slave.vmdk"
Ethernet1.present = "TRUE"
Ethernet0.connectionType = "custom"
Ethernet0.vnet = "VMnet0"
Ethernet1.connectionType = "custom"
Ethernet1.vnet = "VMnet2"
scsi0:0.redo = ""
scsi0:1.redo = ""
ethernet0.addressType = "generated"
ethernet1.addressType = "generated"
uuid.location = "56 4d d8 a8 30 0f 38 24-e7 72 b7 43 d5 e2 d2 b3"
uuid.bios = "56 4d d8 a8 30 0f 38 24-e7 72 b7 43 d5 e2 d2 b3"
autostart.order = "10"
autostop.order = "10"
ethernet0.generatedAddress
ethernet0.generatedAddress
ethernet1.generatedAddress
ethernet1.generatedAddress
tools.syncTime = "FALSE"
--------------------------
Any obvious issues bewteen the two? Any insight would be very useful!
ASKER
Thanks I see that,
But any idea why Active Directory and DNS services are failing? But ceases with the new configuration file?
But any idea why Active Directory and DNS services are failing? But ceases with the new configuration file?
can you post the specific windows events that come up when you power up the computer. I think this might be related to some kind of conflict because of that said entry in the vmx file. The VMX file entries are more like devices detected in the BIOS.
ASKER
Historic DNS entry:-
--------------------------
The description for Event ID 4015 from source DNS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
--------------------------
Historic Directory Service event log:-
The description for Event ID 1126 from source NTDS General cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
3200c89
9852
No DNS servers configured for local system.
--------------------------
Note both of the above have "completely" dissapeard since the implementation of the new .vmx file
--------------------------
The description for Event ID 4015 from source DNS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
--------------------------
Historic Directory Service event log:-
The description for Event ID 1126 from source NTDS General cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
3200c89
9852
No DNS servers configured for local system.
--------------------------
Note both of the above have "completely" dissapeard since the implementation of the new .vmx file
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
your historical vmx file has these two following entries
usb.present = "FALSE"
usb.autoConnect.device0 = "path:1/4/6/0 autoclean:1"
i think the second line is something that is recommended for connecting a VOIP phone.
http://www.dslreports.com/forum/r19265669-Virtual-Machine-recommendations
This might have been added to otherwise for the active sync component.
bhanu