lavadour
asked on
Moving Exchange to new hardwared with the same name, can't reset computer account
I am following Technets procedure to move exchange to new hardware and keeping the same name. http://technet.microsoft.com/en-us/library/aa997176(EXCHG.65).aspx
After taking the old Exchange server offline I can't reset the computer account in Active Directory.
When I right click the name and click reset account I get "Server *** is a domain controller. You cannot reset the password on this object". When I try to join the new server to the domain with the same name it tells me it already exists. Is there a way I can force the resetting of the account?
After taking the old Exchange server offline I can't reset the computer account in Active Directory.
When I right click the name and click reset account I get "Server *** is a domain controller. You cannot reset the password on this object". When I try to join the new server to the domain with the same name it tells me it already exists. Is there a way I can force the resetting of the account?
ASKER
VFCC:
Thanks i will give that a try.
Let me get your opinion. This is small business with 50 employees. We have three servers, File Server, Exchange 2003 / DC, and a DC. Would it be better to just have the one DC and not make the Exchange server a DC as well. I thought it was best to have a backup DC if it's an option. I'm fairly new at this so any suggestions would be great.
Thanks,
Thanks i will give that a try.
Let me get your opinion. This is small business with 50 employees. We have three servers, File Server, Exchange 2003 / DC, and a DC. Would it be better to just have the one DC and not make the Exchange server a DC as well. I thought it was best to have a backup DC if it's an option. I'm fairly new at this so any suggestions would be great.
Thanks,
In your environment you could easily get away with having only 1 DC, however like you said it is better to have the secondary DC because several services depend on authentication with AD. I am not absolutely certain of your full system specs but I would personally put the secondary DC on the fileserver and make it also a GC instead of the exchange box. This will give you redundancy and the two services won't conflict as much because fileservices are heavy disk I/O where AD is more memory and processor intensive.
-Yehoshua24
-Yehoshua24
ASKER
I tried running the netdom command but I get a message back. Network path not found. The command failed to complete successfully
Here is the command I tried.
netdom reset kite /domain:raptor
Here is the command I tried.
netdom reset kite /domain:raptor
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Why do you want to keep the same name? If you have a new server do a swing migration. Much easier, no downtime, no risk.
Simon.
Simon.
ASKER
This is my first time doing a exchange migration and I just thought that would be best but after spending all weekend trying to get it working I am thinking otherwise. Right now this is my situation. I have two new servers. One of these servers is my DC/DHCP/DNS server and I have it authenticating users, issuing IP's etc. Everyone in the office is authenticating to it. The other server I was going to make a DC/Exchange server but after talking to you I think I will just make it Exchange. So I have a Exchange 2003/DC that I want to just move exchange off of to the new server then I will decom the DC and will be setting this server up for other purposes. I've heard of a swing migration but haven't looked into it. I am a newby at Exchange so it's all a little scary to me. If you have any info on the swing migration that would be great. I will start looking around for info as well.
Thanks for all of your help.
Thanks for all of your help.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have another question. I have setup replication for the Public Folders and they have replicated to the new server. It says once the replication is complete that I need to turn off replication. If I am not planning on moving all the mailboxes right now can I just leave replication going for the public folders? I only have just a couple. Or is it once I turn Replication off then users are actually connecting to the new server for Public Folders and not the old server?
You should leave the public folder replication removal until there are NO mailboxes on the server that has the public folders. While in theory Outlook should find public folders that it needs on another server, I find that it does not.
Simon.
Simon.
ASKER
Thanks for all the help.
The quick answer is that you can use netdom to reset the computer account password.
http://support.microsoft.com/?kbid=216393
However I would recommend that when you implement this new hardware that you not put exchange on a DC. It really is against best practice because that DC will also have to be a GC. This means that exchange will only access the GC locally and if the service fails exchange will not look externally for information. THis creates a single point of failure. Also you will notice a significant decrease in system performance with both services because they are both Memory, and processor intensive.
- Yehoshua24