[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 522
  • Last Modified:

WSUS and Print server not working after 2012 Hyper-V unplanned failover

I have a Server 2012 Hyper-V server that crashed with a hardware problem so I did a failover to the replica server. The replica server came up fine but the WSUS and print services do not seem to be working. I cannot connect to the WSUS server remotely or locally and all my printers show they are offline at the users desk but not in the printer console on the server.

I removed replication which was pointing back to the dead server. Is there some other step necessary to bring all this back?
0
LarryDAH
Asked:
LarryDAH
  • 3
  • 2
1 Solution
 
LarryDAHAuthor Commented:
Ok, it seems the my VM replica that I enabled after the server crashed has some permission problems. I cannot UNC to a folder without a challenge, cannot add printers, etc. I can log on to it but cannot seem to do much more than that. This is also a AD server. Can I remove it from the domain and rejoin it or do I have to run dcpromo and demote it first?
0
 
gmbaxterCommented:
So a single server does AD, WSUS and Print? I wouldn't be doing hyper-v replica on a DC. You could have just run a DC over in the replication site - AD natively replicates.

Do you have a DC remaining?
0
 
LarryDAHAuthor Commented:
Yes, I have a standalone DC box. I am not sure why the replica is having such problems. It was replicating fine up till the host server crashed so it can't be out date or sync with the original. It seems to be some kind of permission issue, that is why I wanted to disjoin and rejoin but not sure what effect that would have on AD/DC services.
0
 
gmbaxterCommented:
can you do a "netdom query fsmo" from your workstation and post the results? Could also do with the name of the replica and the name of the standalone.
0
 
LarryDAHAuthor Commented:
Turned out to be a NIC issue, the replica came up on my subnet but without a subnet entry for the NIC, so other subnets could not see it.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now