Hello theire,
hm strange. normally Administrators having access to this ProgramData.
could you please check the Permissions directly? Also the Advanced Permissions.
Worst Case is that the ACL is damaged and need to reforced to that Folder recursivly. (with icacls).
what about UAC? you started the Installer with "Run as Administrator" ?
thx
Max
Madmax01, you hit the nail on the head. Once I got really anal about the permissions, everything worked the way it should when I ran it as an Administrator.
Many thanks for the suggestion/solution.
Many thanks!! That was exactly the problem I was having. The host I was trying to convert wasn't resolving the FQDN for the VMware host that the converter had chosen as a destination. Once I fixed that (by changing the DNS primary entry in the nic configuration on the host I was trying to convert) all worked well!
Good morning,
My boss is bringing me up to speed on virtualization of our systems and we are migrating servers from vMware 4.1 to a new 5.5 server. He has been converting them by installing the vCenter converter software on the 4.1 vm and selecting "physical machine" (even though its a vm) to send it to our 5.5 server. I on the other hand wished to install the vCenter software on my local PC and convert the 4.1 vm using the VMWare infrastructure option to send it to our 5.5 server. Are there any benefits or declines to either way versus another?
Specifically I'm curious of if infrastructure mode is slower than "physical machine" as the 4.1 server must upload to the 5.5 server through my machine, or if those two servers are transmitting between themselves and my local machine just setup the job and is able to monitor its progress.
Thanks,
Colin
VM runing in vSphere 4.1 environment is either Virtual Hardware version 4 or virtual hardware 7 VMs.
both of those hardware version is compatible with vSphere 5.5 environment, so if you could present datastore being used by your ESXi 4.1 host to ESXi 5.5 host too and power off VMs from current host, remove them from inventory and register them into ESXi 5.5 host. Power them on. If you want to upgrade hardware version, while VM is off on new host, first upgrade hardware version and then power them on.
Hello. Colin
There are two things you should consider:
- first is the difference between P2V and V2V. Although the 'P' in P2V used to stand for 'physical' it really means 'powered on' (this is what it actually reads in Converter UI for a few versions now). So you can P2V virtual machines but they have to be powered on. V2V OTOH requires them to be powered off.
- the second difference is how the traffic flows. In the case of P2V, the source machine pushes the data directly to the destination ESX host (Windows source) or the destination VM pulls the data directly from the source machine (Linux source); see user guide pp.11,12. In case of V2V however, the data traffic flows from the source VM through the Converter server to the destination VM. This may result in performance decrease. If your local machine is in a distant or slow network, this decrease may be dramatic.
HTH
Plamen
Hi theire,
please don't upgrade vHW then on 5.5 at First step. please make then Vmware Tools Upgrade before doing that. As because in Worst Case you could loose the IP Address.
VMware KB: Upgrading a virtual machine to the latest hardware version (multiple versions)
thx
Max
Thank you all for your input as this has helped me a lot and I was able to successfully migrate this server with only having to resetup network settings!
Ha. Never saw that message without any Error Related. As i see you have already latest Patch Level that's fine. Maybe that's a Bug of the Version. you have 2 nic's per vSwitch?.
could you test if you see something over Powercli?
$myhost=get-vmhost "myhost"
and to check if something back on
$myhost.extensiondata.configStatus
$myhost.extensiondata.OverallStatus
$myhost.extensiondata.ConfigIssue
thx
Max
Also could you check if that Message exist over Webclient and once you direct connect to esxi through normal client.
thx
Max
Hello.
I'm an IT admin and recently my company inherited a particular old server running Windows 2003.
My only concern is the HW failing on me so my immediate thought was to convert the server into a VM, which is something I last did 4 or 5 years ago, but the process is now a bit different. The VCC Standalone is now a small client software/agent that is installed on the physical server. No more Converter CD to boot the server in offline mode.
This way I have to install something on the server and I void the contract. If anything goes bad they will cut my head off...
Is there any way I can somehow create a boot CD with VCC standalone? This way I wouldn't install anything on the server (not voiding the contract).
*** Read just in case you're wondering why I need this ***
A two company merger made me responsible for a hand full of old physical servers, most of them still on Windows 2003.
These servers are out of support from both OS vendor and hardware vendor!
For now, our biggest concern is with theirs (now ours too...) accounting server. We are forced by national law to maintain accounting records for 15 years and we can be held responsible if we fail to do so. They can penalize us very hard and can shut us down.
Now, the other company let this happen because they decided to stop using this accounting software 8 years ago and they started using another product, which means we still have 7 years ahead of us...
The hardware is a "white label" server for which they say they had a contract but I couldn't find any evidence. Two 72GB SATA 8 years old RAID 0 hdd's ready to die on my hands. Yep, you read it right, RAID 0. Apparently 72GB (RAID 1) was somehow not enough for a Windows 2003 installation with MSSQL and the accounting software. Ridiculous!
They stopped paying the HW contract because they decommissioned the accounting software and thought they could just let the server be there for 15 years rotting and not being responsible for it.
No backups either. This company apparently never had a backup plan because they didn't have an IT admin. Makes me wonder how they got this far...
Just to spice things further, this old accounting software has a valid contract but the contract says that we can't install anything on the server or else we void the contract.
They say they added that clause to the contract because the company "we bought" didn't want to pay contracts for both the new and the old accounting software. So they made up a contract that if the accounting software stops due to a bug they will solve it. But if it's because of a Windows update or some software that we installed or some HW problem, we are responsible and we have to deal with it. I'd rather not pay contract, period...
Bottom line, one thing lead to the other and now I have a time bomb ticking in my hands.
On the board meeting they laughed and said that's why they pay me...
Too bad they don't have a clue.
*** End of explaining ***
I had to do something similar some time ago, and what I did was to use the old ColdClone CD (assuming you still hve it) and convert the Windows 2003 Server into a VMware Workstation format (ColdClone doesn't support ESXi 5 as a target). Once converted I used the latest converter and converted the Workstation VM (V2V) to the vSphere environment.
André
Interesting.
So first you had to convert to VMw Workstation format. I guess I don't need VMw Workstation in order to do that, do I? I hope ColdClone.iso is enough for that.
Then I must install the latest Standalone Converter and convert to ESXi 5.x, right? I'll give it a try.
Thanks a bunch. Will let you know how it went later.
Cheers
The simple reason for this two-step approach was that the ColdClone version doesn't support newer vSphere versions. The conversion to the Workstation format creates the VM's files on the specified location (e.g. a file server). For the second conversion install the Converter on e.g. a PC, select Workstation VM as the source type, and point to the VM's .mx file.
What I usually do as the first step after conversion - i.e. prior to powering on the VM on the target - is to create a snapshot. Then cleanup the VM (remove hardware related drivers, services and tools), install VMware Tools, and finally - if everything works as expected - delete the snapshot.
André
Hello I am wondering am I correct in assuming that this is specifically in regards to the Converter Version 5.0 and not in regards to the ESXi platform Versions
If you could please let me know it would be greatly appreciated
You are correct, it is about Converter versions 5.0 and newer.
Im trying to convert the existing HyperV VM´s to our ESXi Clusternodes.
I have to convert through the vSphere server because my root permissions are missing for converting to the direct node.
Does anyone have an Idea whats the problem?
open Ports on vSphere Server:
TCP 445
TCP 139
TCP 443
TCP 902
open Ports on Clusternode:
TCP 445
TCP 139
TCP 443
Routing should be ok.
Sorry for my bad english - im from germany.
thanks in advance.
greeting ma.
Hello,
VMware KB: Required VMware vCenter Converter ports
From that KB you would need also Port 902 to the Esxi Hosts
could you open that Port and trying again?
thx
Max
Hi Madmax01,
I requested this already. it takes a bit until that is implemented...
I'll let you know then.
thanks, ma
Okay, the Port is not the problem.
The first line looks as if the target server reject the connection. Half a minute later no answer seems to pitch on the firewall.
FW Log:
Aug 17 09:31:09 10.25.15.22 framf02: NetScreen device_id=framf02 [Root]system-notification-00257(traffic): start_time="2015-08-17 09:31:05" duration=5 policy_id=1001 service=tcp/port:902 proto=6 src zone=bt-mgmt dst zone=bt-mgmt action=Permit sent=16576 rcvd=0 src=10.15.3.201 dst=10.15.5.219 src_port=50961 dst_port=902 session_id=171331 reason=Close - TCP RST
Aug 17 09:31:39 10.25.15.22 framf02: NetScreen device_id=framf02 [Root]system-notification-00257(traffic): start_time="2015-08-17 09:31:20" duration=19 policy_id=1001 service=tcp/port:902 proto=6 src zone=bt-mgmt dst zone=bt-mgmt action=Permit sent=279933 rcvd=0 src=10.15.3.201 dst=10.15.5.219 src_port=50980 dst_port=902 port=902 session_id=251722 reason=Close - AGE OUT
Any idea?`