Rubeck's Accepted Solutions

The vSwitches does not have any L3 capabillities, Im afraid... You will need to create a 802.1Q VLAN trunk on your pSwitch if you want multiple networks forwarded to a single pNIC... ... See more...
The vSwitches does not have any L3 capabillities, Im afraid... You will need to create a 802.1Q VLAN trunk on your pSwitch if you want multiple networks forwarded to a single pNIC... /Rubeck
Is this article releated in any way? http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c00828673〈=en&cc=us&taskId=101&prodSeriesId=428936&prodTypeId=15351 /Rubeck
Hi Z. Virtual Machine/ Configuration/ Rename its what you need... /Rubeck
Hmm.. Wierd ... Well.. Gparted is also an option.. See guide: http://searchvmware.techtarget.com/tip/0,289483,sid179_gci1324177,00.html# /Rubeck
You dont have to worry about ranges... As long as you got a portgroup with the correct VLAN ID, you're good to go. IP on portgroups only exists on SC and VMkernel connections.. The range yo... See more...
You dont have to worry about ranges... As long as you got a portgroup with the correct VLAN ID, you're good to go. IP on portgroups only exists on SC and VMkernel connections.. The range you've might have seen is "observed Ip ranges" which just is a list of detected network paackets seen by pNICs... /Rubeck
http://itknowledgeexchange.techtarget.com/virtualization-pro/making-virtualcenter-depend-on-ms-sql/ You just need to specify MSSQL$SQLEXP_VIM as the service name when running Express.. ... See more...
http://itknowledgeexchange.techtarget.com/virtualization-pro/making-virtualcenter-depend-on-ms-sql/ You just need to specify MSSQL$SQLEXP_VIM as the service name when running Express.. /Rubeck
Hi.. Have you tried removing the template from inventory and re-register..? /Rubeck
Try to see if you have a "de" folder in your VI Client program directory..... If yes, try rename this. /Rubeck
INDEEED! /Rubeck
I think that would require the VM to be running on a 3.5 host, which is not possible as the 3.5 host cant run a VM on a VMFS2 volume. (VMFS2 is read-only from a 3.5 host point of view) /Ru... See more...
I think that would require the VM to be running on a 3.5 host, which is not possible as the 3.5 host cant run a VM on a VMFS2 volume. (VMFS2 is read-only from a 3.5 host point of view) /Rubeck
You could also do a BSOD on a M$ VM, by adding a reg- key: Key:[HKEY_LOCAL_MACHINE \System\ CurrentControlSet\Services\i8042prt\Parameters] Value Name: CrashOnCtrlScroll Data Type: REG_DWORD... See more...
You could also do a BSOD on a M$ VM, by adding a reg- key: Key:[HKEY_LOCAL_MACHINE \System\ CurrentControlSet\Services\i8042prt\Parameters] Value Name: CrashOnCtrlScroll Data Type: REG_DWORD Data:(1 = enabled) Once you reboot your machine, you will be able to hold down the right control key and click the Scroll Lock key twice to make your machine Blue Screen. /Rubeck
vmware-vim-cmd hostsvc/net/portgroup_unset removes everything exept for Linkstate Failover.. soo close. (Funny that portgroup_unset is not listed as an option) /Rubeck
Have you tried to restart the hostd management service? (service mgmt-vmware restart) /Rubeck
Ohh ...this guide may be easier http://itknowledgeexchange.techtarget.com/virtualization-pro/making-virtualcenter-depend-on-ms-sql/ /Rubeck
VMotion requires shared storage.... During VMotion no .vmdk files are being moved around... so it's required that all hosts have access to the same storage. /Rubeck
Hi Kallex.. I havn't got much experience with 3i, but dosn't the setup guide describe on how to do this? http://www.vmware.com/pdf/vi3_35/esx_3i_e/r35u2/vi3_35_25_u2_3i_setup.pdf (Chapter 10... See more...
Hi Kallex.. I havn't got much experience with 3i, but dosn't the setup guide describe on how to do this? http://www.vmware.com/pdf/vi3_35/esx_3i_e/r35u2/vi3_35_25_u2_3i_setup.pdf (Chapter 10, page 113) /Rubeck
From http://technet.microsoft.com/en-us/library/cc753703.aspx scrub: Removes volume mount point directories and registry settings for volumes that are no longer in the system. This prevents v... See more...
From http://technet.microsoft.com/en-us/library/cc753703.aspx scrub: Removes volume mount point directories and registry settings for volumes that are no longer in the system. This prevents volumes that were previously in the system from being automatically mounted and given their former volume mount point(s) when they are added back to the system. /Rubeck
Just point the Virtual Infrastructure Client.to the IP of the VC server instead of the ESX host.... (Just make sure that the Virtual Center service is running on the VC host) /Rubeck
Cant think of any special setting other than pressing ESC when powering on, which allows you to select another boot- device. (or entering the VM BIOS and select the CDROM as primary boot device) ... See more...
Cant think of any special setting other than pressing ESC when powering on, which allows you to select another boot- device. (or entering the VM BIOS and select the CDROM as primary boot device) /Rubeck
Not a problem at all.... Just make sure you're running VC v. 2.5 before adding 3.5 hosts. /Rubeck