• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 289
  • Last Modified:

restablish trust with domain

I had to change our 32 bit Windows Server 2003 to 64 bit so basically I reinvented the wheel. I kept the same domain name, but now my clients pc has lost trust with the domain. How do I reestablish it with out having to remove and add them back to the domain one workstation at a time??
0
jmahlmann
Asked:
jmahlmann
  • 2
1 Solution
 
arnoldCommented:
You did not reinvent the wheel, you broke the wheel into pieces and reassembled the wheel from those pieces with the splinters and cracks. Now that it rides unevenly and screeching from the stress, you are looking for duct tape to reinforce the "new" wheel.

domain.com on old server is not the same as domain.com on new server.

If you have a backup of the state (AD and sysvol) you could try and restore the AD from Backup.

Do you have a DR backup of your old server?  An option could be to restore the server to its former state.
Use a temporary system and set it up as another DC in the environment.  Transfer all the roles from the original DC to the temporary one.  Rebuild the server with win2k3 x64 and add it back as another DC.  Transfer the roles back from the temporary to the newly minted, rejuvenated X64 DC.

Everybody would be happy and you would not need to readd each workstation and user to the domain.
The shares if any would need to be recreated.



0
 
jmahlmannAuthor Commented:
But i thought you could not do that because the original is 32 bit and my new os is 64?
0
 
arnoldCommented:
Have a look at virtualbox (http://www.virtualbox.org/). Setup a small win2k3 32bit VM.
As I said it would be a risk to try to restore the 32bit system state onto the x64.

rename your new server.
The alternative is setup a VM server (install the virtualbox from http://www.virtualbox.org/) On any workstation where you have available disk resources.  This is a temporary situation.

Install win2k3 32bit as the VM with the same name as the original server.
restore the system state backup in the VM.

Make sure to bind the network interface of the VM to the hosts interface such that the VM will have an IP on the LAN rather than a NATed IP from the host system. Not NAT.

Then you join your Host system as another DC to the VM's Domain.
Once that is done, transfer the AD roles from the VM DC to the new server (FSMO, Schema, GC, etc.)
http://www.petri.co.il/transferring_fsmo_roles.htm
http://support.microsoft.com/kb/324801
http://windowsitpro.com/article/articleid/13390/how-do-i-change-the-schema-master-fsmo.html

One the new server has the old AD, scripts, and is now the master of all the roles, you can decommission the old server (VM) and you're done and everybody is happy.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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