Solved

restablish trust with domain

Posted on 2009-04-07
3
283 Views
Last Modified: 2012-05-06
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
Comment
Question by:jmahlmann
  • 2
3 Comments
 
LVL 77

Expert Comment

by:arnold
ID: 24092387
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
 

Author Comment

by:jmahlmann
ID: 24092404
But i thought you could not do that because the original is 32 bit and my new os is 64?
0
 
LVL 77

Accepted Solution

by:
arnold earned 250 total points
ID: 24092521
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

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Auslogics BoostSpeed 9 software 5 69
Forcibly removing a 2003 server from the Domain 4 46
Unexpected Windows system folders on D drive 16 83
Domain Controller FSMO 7 35
INTRODUCTION The purpose of this document is to demonstrate the Installation and configuration of the Data Protection Manager product. Note that this demonstration was prepared on the basis of Windows OS is 2008 R2 and DPM 2010. DATA PROTECTI…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …

813 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now