Save yourself a lot of pain and frustration and just create a new 2008R2 VM and DCPromo it. Transfer any FSMO roles that the old DC has to one of the 2008R2 DCs and demote the old one when done. Make sure both your VM DCs are pointing to a reliable external time source (not getting time from...
So, I am not a group policy maven at all but I need to set a system environment variable and the value will be based on the username. For example:
Username / System Variable / Value
MJones / workstation / 1
BSmith / workstation / 2
CEdwards / workstation / 3
etc...
None of the users are, nor...
I seem to average between 3.75-4TB / hr writing to my 6 X LTO6 drive library. Much faster than what most people would get with a backup to disk target which is typically not an SSD array but more often some array of NL-SAS drives.
Granted reading and restoring from disk is considerably faster...
Seems like your boot partition got jacked up as part of your process. Did you change the controller perhaps to/from paravirtual/lsi logic or something when you changed the drive size?
Regardless, your best hope is to try to rebuild your boot record:
1.Boot Windows 2008 R2 CD
2.Select repair...
*-flat.vmdk is the actual virtual disk file itself. It is not visible from the datastore browser of the vSphere Client. The file that you see when you browse a datastore and see your servername.vmdk is just metadata about the virtual disk such as sector information, size, alignment etc. It...
If you have 1 VM at version 10 and all the others are 4, 7, 8, vmx9 and you really want the 1 other to match one of those other versions, you can try to V2V the troublesome using the VMware Standalone Converter and during the process you will be asked what hardware version you want.
If 5.5...
You converted your host. You upgraded your VM and you updated your vCenter and now you want to downgrade one or all? Not exactly clear. Bottom line though is that 5.5 is the last vSphere version that will have any form of the old C# vSphere Client and it is all web going forward, so you might...
Here is the description of RVTools from the website. Even if it doesn't suite your particular need, I am certain that every VMware Admin can make great use of it.
RVTools is a windows .NET 2.0 application which uses the VI SDK to display information about your virtual machines and ESX hosts...
Check out RVTools from http://www.robware.net/ You can run it against your stand alone boxes as well as your vCenter to capture all the info for those hosts and VMs managed by vCenter.
It is an awesome tool and yes it is FREE!!!
It will capture information about your hosts and VMs right down...
VMware HA does great with your typical application / web / file / print etc servers. You lose a host, within 60-90 seconds the VMs that were on the lost host are running again on a different host, provided you are N+1 or better. Database servers like Exchange, SQL, Oracle etc will not be as...
If you are snapshoting your DC you are just asking for trouble. I set all my virtualized DCs vmdk's to be independant persistent and therefore un-snapshotable. I don't even want anyone to possibly even consider the idea of snapping a DC and then reverting back at some point later. Talk about...
vSphere 5.1 is just barely a year old. If you are moving the VM from 5.1 to 5.5, which was just released about a month ago, and I assume you do not have vCenter and are just using stand alone servers, than your best method would probably be to schedule an outage and shutdown the VM. Browse the...
Can you be a little more detailed as to what you mean by an "Old VM" and "New VM"? If you are asking if you can migrate a VM from vSphere 4.1 (old) to 5.1 (newer) than yes, that is a very simple process. If you are asking if you can migrate a VM from GSX (oldest) to 5.5 (newest) well that will...
Your line of thinking on how virtualization works in vSphere is a bit off base.
Let's start with CPU.
Best practice would say to start with 1 vCPU per VM and increase as needed from there. Since you only have 2 VMs on this host I would say that your are OK with the 4 per that you are...
Regarding your NIC issue, this is because the NIC in v5 is different from the NIC in 2.5 and Windows still sees the original NIC with its static IP. I know you are saying "I looked in Windows networking and there is just the 1 new NIC. I even looked in Device Manager and there is just the 1...
It sounds like you are probably running on some pretty old hardware, based on the versions of VMware you are running. You would be best off verifying that everything is on the 5.1 Hardware Compatibility List from your servers to storage to HBAs to NICs etc. That would be step one in my book.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.