Vmware converter windows 2008 r2 domain controller




















I read your original post wrong and thought P2V instead of V2V. Can you tell us what you're converting from and converting to? When I stop, am I correct to assume that server is down from AD point of view? I don't see where you need to convert anything. Stop the 5. You can copy it from the datastore it's resident on to a PC and then back up to its new datastore. Start it up, it shouldn't even know it was moved.

Optionally, update VMware Tools once it's up. As I said, I have no access to source vCenter server due to other reasons. You can browse datastores by navigating to the configuration of the host and choosing the Storage option then the datastore in question.

Since you have other DCs, would it be terribly hard just to build a new DC in the new datacenter? Alternatively, what backup software do you use? Would taking a backup, shutting down the DC in the source datacenter, and then restoring the VM to the new datacenter be an option here? I guess it depends on whether you have access to image backups of this DC.

I don't understand why you can't spin up a new DC and migrate services, but if that isn't an option then if you are able to ensure that the only domain controller in the domain is the one you are moving you can get away with it. When it tries to push that information to other DCs is when the problem comes in. If you only have the one DC against MS best practice then you can do the migration without worrying because it doesn't have any other DCs to mess up. If the latter, you can simply move the machines when powered off, if the former, as others have said, build a new one, replicate, decommission the old, simplest, safest and proven to work.

They have already said they have no access to the other vcenter so this is not possible. OP, I have to ask, what are you trying to do here by cloning it, if you have no access to the other vcentre, cannot clone or export it - are you supposed to have access to the DC at all? Just need access to the source host and to a destination host so you can browse the datastores attached to those hosts.

I'm wondering why he can't ask someone to do this for him either. Maybe he's building a non-sanctioned test or lab environment. Who knows. It may also be possible to use vmware converter not sure if still a thing and just convert it from one host to the other. Have not done this for a while, P2V it as you normally would treat the current virtual as a physical, computers don't know the difference converter will just do the same procedure as a physical machine, on the virtual!

The OP also states they cannot migrate roles, which suggests they either done have DA rights, or have no access to the DCs period. It is possible, but you still need access to the ESXi host or the vcentre, and the machine needs to be shutdown. Converter is still and thing and is useful for just copying VMs from vCenter to vCenter when all you have is the network between them "shared nothing" , but the vSphere 6 Web client not the VPX client can do this as well, I believe.

It tends to change them if you don't notice and choose the type manually. I am still wary of changing any of the hardware including virtual hardware on a domain controller, and for that reason, I would shy away from using the Converter. Usually I'm the first to recommend the thing as a great tool, and I do use it occasionally, but for DC No it tends to work better with the machine running strangely enough LOL never yet been able to get a computer to work with it turned off.

For V2V the machine has to be off, if your going to install the converter IN the guest, that's different, but that is not an ideal way to do it for virtual machines, even more so for busy active ones.

I am failing to understand what the op wants to do this for, when they have already stated they have no access to the machine or the vcentre. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks.

Do you see any issues? Appreciate your thoughts on this. Popular Topics in VMware. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need.

Learn More ». Thai Pepper. JeffNew This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. There are many, many articles online on doing what you want. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 10 years, 6 months ago.

Active 7 years, 3 months ago. Viewed times. Improve this question. So you did something that goes against all wisdom, admit that you know it was a bad plan, and are surprised when things get mucked up?

You're going to need to provide more details of what exactly is happening. What are the errors you're seeing? What does "screwing with my DNS" mean? I'm not at all surprised - but am pondering possible solutions to a problem. I edited the post in any case — atomicharri. If you really need a linux server so badly, just run it on some old desktop machine you have around. As much as I hate running server OSes on non-server class hardware, this would be a better situation than what you're currently doing.

Add a comment. Active Oldest Votes. Improve this answer. Mark Henderson Mark Henderson That won't fix the problem. You're thinking of what workstations do. What domain controllers do is register themselves so that workstations can find them and find group policies. It's not even done by the same service as on workstations, let alone is configured in the same way.

Adam Adam 1. Sign up or log in Sign up using Google. Sign up using Facebook.



0コメント

  • 1000 / 1000