Domain Controller Down (VM)
-
VMware SABU checking in... You need a webex to fix this?
-
will you look at that, gorgeous!
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender What do you think?
That wiring is seriously not bad. I have seen way worse.
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender What do you think?
That wiring is seriously not bad. I have seen way worse.
Me too, lol.
-
@JaredBusch @dafyre That's really sad guys.
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender What do you think?
That wiring is seriously not bad. I have seen way worse.
Agreed, the main thing wrong with that patch panel is the cables are to long.
-
right click on your 2003 VM and start it.
-
-
@John-Nicholson Does VMware offer any services for suicide watch?
-
@JaredBusch said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
right click on your 2003 VM and start it.
NO
no?
-
@Dashrender said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
right click on your 2003 VM and start it.
NO
no?
Looks like he has some VM named something to to with replication.
-
So because of THAT doing some kind of potential replication on the backend we need to look for running VM's elsewhere first.
-
@JaredBusch said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@Dashrender said in Domain Controller Down (VM):
right click on your 2003 VM and start it.
NO
no?
Looks like he has some VM named something to to with replication.
Yeah he has failover setup - well, his predecessor did. He saw log entries or something that showed if failed earlier
-
@wirestyle22 open another instance of the client to each host and verify what is running where.
-
@Dashrender Yes that is correct
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 open another instance of the client to each host and verify what is running where.
Why not just use the vSphere web client?
Sure he might have to do a https://IP address:9443/vsphere-client to get there.
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 open another instance of the client to each host and verify what is running where.
-
and finally the the third host in the other building
-
No over lap in VM names yet.
-
@John-Nicholson said in Domain Controller Down (VM):
VMware SABU checking in... You need a webex to fix this?
@wirestyle22 if you take him up on this, I would love to just listen in on the trouble shooting steps, if you're ok with it.
