should be fine?
From: Jeremy Anderson [jer...@mapiadmin.net]
Sent: Tuesday, April 21, 2009 11:19 PM
To: NT System Admin Issues
Subject: RE: Error authenticating to exchange
Before flattening the box, Reset the Computer account in AD, remover the server
from
There are SO many potential problems here, it isn't even funny.
Try a netdom resetpwd. If that doesn't work - I'd probably approach this
problem differently.
From: Jason Gauthier [jgauth...@lastar.com]
Sent: Tuesday, April 21, 2009 4:15 PM
To: NT System Admin
would you approach it? This process is usually perfect for me to get a lab
instance of my domain and exchange.
m open to alternatives.
From: Michael B. Smith [mailto:mich...@owa.smithcons.com]
Sent: Tuesday, April 21, 2009 4:18 PM
To: NT System Admin Issues
Subject: RE: Error
.
Exchange doesn't care about the server GUID. Only it's name.
From: Jason Gauthier [jgauth...@lastar.com]
Sent: Tuesday, April 21, 2009 4:25 PM
To: NT System Admin Issues
Subject: RE: Error authenticating to exchange
Slap me silly and hand me a Bar
Huh. I thought it was concerned with the GUID. Alright. I will give that a
try. Thanks.
From: Michael B. Smith [mailto:mich...@owa.smithcons.com]
Sent: Tuesday, April 21, 2009 4:32 PM
To: NT System Admin Issues
Subject: RE: Error authenticating to exchange
Database portability works
...@owa.smithcons.com]
Sent: Tuesday, April 21, 2009 1:32 PM
To: NT System Admin Issues
Subject: RE: Error authenticating to exchange
Database portability works fine.
So...you are fine with your DC process (as long as you make it a GC first
before disconnecting it from the domain).
Then delete
