I just succeed to rebuild bcd with the link below.
But nothing changed. Windows is starting
and failing by resetting itself. log-on page doesn't appear.
http://pcsupport.about.com/od/fixtheproblem/ht/rebuild-bcd-store-windows.htm
I just succeed to rebuild bcd with the link below.
But nothing changed. Windows is starting
and failing by resetting itself. log-on page doesn't appear.
http://pcsupport.about.com/od/fixtheproblem/ht/rebuild-bcd-store-windows.htm
Issue was fixed by copying VM to vCenter server, and converting from there.
I have the hard drive connected via usb. I cannot connect it directly to the motherboard as it is an old drive using IDE, and my motherboard only supports SATA connections, but I had already looked into that. I have another USB external hard drive that shows up in the converter options, which is why I was confused as to why the old drive isn't showing up.
In the powered off machine options, it only lets you convert from other virtual machines, and existing vmware files. I could just be doing this wrong, as this is my first attempt at converting P to V.
Yes, I tried bootrec /fixmbr, bootrec /fixboot and bootrec /rebuildbcd in order.. But it says "Total identified windows installations=0"
When I restart, it crashes an rebooting again and again.
The only one chance then is to play with bcdedit - there is a set of commands to create new bcd.
HTH
OK, let me first correct a mistake I've made - Workstation does allow you to create a VM with an external drive. However it needs to be connected before starting WS (I've been trying the other way yesterday).
Also, let me restate that - you cannot do a P2V with this disk without booting from it. Converter has to recognize the system volume and do reconfiguration; it just can't happen when you convert your local machine. You can try V2V though by creating a wrapper VM in Workstation. I don't know whether you have WS. If not, I am not sure whether Player can do this trick. You may need to check that.
Actually there is a way for Converter to see external disks - there is an option in converter-worker.xml (thanks to POCEH for reminding me that, I have forgotten). Look for plugins/converter_agent/skipRemovableDisks; it needs to be set to 'true' and then worker service restarted. converter-worker.xml can be found in "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone"
And last (but not least), there is something suspicious in the other USB drive showing up and the XP one not showing. Either the above option is off and Converter has somehow detected it as local (quite strange) or the option is on (unlikely?) and the XP disk is damaged and can't be read. Run a check if needed.
HTH and regards,
Plamen
Addendum: Hmm, after trying that with a flash stick it occurred that the conversion failed in the beginning of cloning with 'Unable to open source disk'. Unfortunately I have no idea why :-(
Pity, it looked like a nice hack...
Hi,
when I start Installation of VMWare converter (filename: VMware-converter-en-6.1.1-3533064.exe) I get (under Win10 64) a red popup saying that Smartscreen hindered the Installation.
Provider is "unknown". I downloaded it directly from vmware.
Is this normal/OK ? (Sorry,if I am too paranoid - but locky is potentially around the Corner)
Thanks and best regards
Oliver
All-
We are currently moving our SQL environment from a Microsoft Failover Cluster to VMWare running on Nutanix. It is going from a SAN to local drives. What is the best way to approach this with minimal downtime? What is the best way to set up SQL in the new environment.
My initial thought for the data move would be to take a full backup of the databases and move them to the new instance. Then when it's done, take a DIFF Backup, stop access to them on the source and restore them on the destination. This seems like a feasible plan.
My question is more for the VMWare side of it and how to configure the HA VMWare instances. I'm sure this has been discussed in length so a point in the right direction would be great.
Thanks
Jeff
Well Plamen,
I don't know why it didn't work for you, but that was exactly what I needed. After I changed that to true, it worked just fine, and I was able to create the VM. Thanks so much!
Jason
Hi Jeff,
It seems failover clustering is supported on Nutanix running ESXi.
However as there is no block storage available, the quorum has to be a fileshare witness.
I would suggest setting up an empty 2 node cluster and then backup and restore SQL as you had planned.
VMware on Nutanix provides no additional HA features than vSphere already does (like HA and FT).
Once the 2 nodes are up and running you will create a DRS rule called separate virtual machines. this will make sure that the two nodes are always running on different ESXi hosts all the time and you have high availability from hardware failure.
DRS Rules for Microsoft 2 Node cluster.
Microsoft failover cluster on Nutanix
Microsoft Failover Cluster Configuration with Nutanix - StevenPoitras.com StevenPoitras.com
Is there any way to exclude files or folders while performing P2V for a Windows box?
Regards
marius
Using the vCenter converter standalone there is not.
you can choose which drives to convert
Glad it worked with you. Thanks for the feedback.
Regards,
Plamen
Hi - I have gone thru the many many post for this same issue but none of the suggestions have provided a solution...
Cloning a Physical Windows 8.1 PC to create an image on the source PC.
Converter Version is 5.5.3
UAC is disabled,
Both a Domain admin account and local admin account has been tried.
Converter is being been launched with 'Run as Administrator'
Converter has been uninstalled and reinstalled (Several times)
VMware services have been stopped and started.
GUI Log reports '2016-03-02T14:52:51.510+11:00 [03152 error 'wizardController'] Must be administrator to access physical computer'
Both accounts tried are in the administrator group.
Source Physical PC has been rebooted and started using both types of admin accounts and each connection scenarios tried.
Converter continues to report same Permission Denied error.
Hi,
the problem might be with the grub-install. new version of converter use grub2-install which is not available. I tried ln -s grub2-install to grub-install and managed to resolve this.
BR,
Petar
for source: powered-on Win7 PC, target vCenter/vConverter 5.5 - I also had to enable the source's local 'administrator' account (disabled by policy). Really odd.
Already tried:
- domain admin account (inherently local admin on source and target, can otherwise do anything)
- source-local non-domain custom admin account
- turned off UAC on source
- launched Converter as administrator
Have you try with Converter 6.1?
Hello,
I've done a P2V conversion of my Ubuntu Server 10.04 LTS with VMware vCenter Converter 6, to my ESXi 5.5.
The job works perfectly in the software, completed without any error message...
The problem is now when I boot the freshly created VM, I have the following error message on the prompt :
Have you any idea about how to resolve this ?
I've tried to reinstall grub with a boot repair disk but it doesn't work
Thanks for you help.
Thank you for taking the time to read this.
Trying to convert physical server to virtual
Physical server is Windows Server 2008 R2 64 bit
Running ESXi 5.5 cluster
Using VMware Stand Alone Converter version 6.1.1 installed onto the physical machine itself.
During the convert machine process the program stops at 98% with message unable to reconfigure machine.
I checked the datastore and did find the vmdk was there.
I then tried to configure machine with only the 'reconfigure destination virtual machine' option selected and I get a failed message during the "Updating the boot sectors of the destination machine" process...
Error: An error occurred during the reconfiguration.
Status: FAILED: A general system error occurred: InternalError
Trying to boot the VM gives a 7B BSOD which is "INACCESSIBLE_BOOT_DEVICE bug check frequently occurs because of a boot device failure."
I have read that this can occur because of LSI Logic SAS issues.
Here is what I have tried so far.
I manually and successfully built a 2K8 R2 VM using an install media ISO and booted into the OS so I know that my process and my cluster work correctly.
I used the newly created and working 2K8 R2 VM and restored a server backup image I took from the physical server. I now get the 7B boot BSOD on this once working VM
I created another new 2K8 R2 VM and pointed it to the VMDK of the converted VM. I get the 7B BSOD
After some reading and research online, I copied the following files from a good running 2K8 R2 VM into the non functioning converted VM's \Windows\System32\drivers location
LSI_SAS.sys
LSI_SAS2.sys
LSI_SCSI.sys
Into the system registry I imported the following reg keys which I first exported from the working 2K8 R2 VM
LSI_SAS.reg
LSI_SAS2.reg
LSI_SCSI.reg
I also verified that each of these Values had their REG_DWORD = 0
The last thing I tried was to take a ghost image of the physical machine, and then restore the ghost image to the hard drive of a newly created 2K8 R2 VM. I was actually very surprised that I could do this in the first place. But upon booting the ghosted VM I once again get the 7B BSOD.
So now I have come here as I am not sure what to try next.
Before I post all the logs is there something simple I am missing? I've converted systems before without issue but never a 2K8 R2 server/
Thanks in advance
Could you upload log bundle?