Wednesday, January 11, 2012
"The trust relationship between this computer and the primary domain failed" messing about with SCVMM 2012 RC
I love all things Microsoft, but SCVMM turns out to be a real pain... even in its latest version. Looks like 2012 will stay in my lab environment for more than I initially thought before I start rolling it out to clients.
What I tried to do was to move a highly available VM from an SCVMM 2012 managed Hyper-V cluster to a standalone Hyper-V server. The job failed. I repaired the VM in SCVMM but when I started it Windows came up with this message:
"The trust relationship between this computer and the primary domain failed"
Now, labs are for simulating leal-life senarios and in this instance the VM hosted an Exchange 2010 server so taking it off the domain and joining it back again was out of the question.
There's a whole bunch of fixes on the Net, like changing NIC provider order, deleting corrupt GPOs, resetting the computer account in AD, using NETDOM to reset the secure channels and many more.
I found that the simplest way was to go to System Properties, Computer Name tab, click on 'Change' and under 'Domain' just type in the NETBIOS domain name (i.e. instead of domain.local, type DOMAIN).
OK all windows, restart and voila: domain trust reinstated.
Now all that's left is to figure out why SCVMM botched up the VM move and if the issue can be replicated.
What I tried to do was to move a highly available VM from an SCVMM 2012 managed Hyper-V cluster to a standalone Hyper-V server. The job failed. I repaired the VM in SCVMM but when I started it Windows came up with this message:
"The trust relationship between this computer and the primary domain failed"
Now, labs are for simulating leal-life senarios and in this instance the VM hosted an Exchange 2010 server so taking it off the domain and joining it back again was out of the question.
There's a whole bunch of fixes on the Net, like changing NIC provider order, deleting corrupt GPOs, resetting the computer account in AD, using NETDOM to reset the secure channels and many more.
I found that the simplest way was to go to System Properties, Computer Name tab, click on 'Change' and under 'Domain' just type in the NETBIOS domain name (i.e. instead of domain.local, type DOMAIN).
OK all windows, restart and voila: domain trust reinstated.
Now all that's left is to figure out why SCVMM botched up the VM move and if the issue can be replicated.
Labels:
2012,
Active Directory,
SCVMM
Subscribe to:
Post Comments (Atom)
About Me
Blog Archive
Categories
Musings
(3)
Virtualization
(3)
2012
(2)
SCVMM
(2)
SQL
(2)
2010
(1)
Active Directory
(1)
Cloud
(1)
DMZ
(1)
Errors
(1)
Hyper-V
(1)
Scripts
(1)
TMG
(1)
Threat Management Gateway
(1)
Powered by Blogger.
Popular Posts
- Office 365 with Exchange on-premises Hybrid Deployment and Migration - A COMPLETE HOW-TO GUIDE
- Workaround for Citrix EdgeSight Process Usage report showing average times instead of time sums and a quick insight into using MS SQL Report Builder with queries to generate custom SQL reports
- Using TMG 2010 with Hyper-V to support multiple Virtual DMZ hosts
- Annoying "You cannot access VMM management server scvmm.domain.local" 1604 error: "Contact the Virtual Machine Manager administrator to verify that your account is a member of a valid user role and then try the operation again."
- SCVMM 2012 locale issues and Error 24374 when adding new Library Share with default resources
- How to use msg.exe to send popup messages to multiple PCs / Workstations
- "The trust relationship between this computer and the primary domain failed" messing about with SCVMM 2012 RC
- With a mind on the cloud, eyes on virtualization and feet planted firmly on the (datacenter) ground...
- I'm an IT Manager... nobody loves me!
- Musings of an IT guy
0 comments:
Post a Comment