Link to home
Start Free TrialLog in
Avatar of bs_ssg
bs_ssgFlag for United States of America

asked on

adprep32, how long to allow replication to finish?

I will soon be running adprep32.exe on a Windows 2000 Server, which is the FSMO DC in the network.  I am adding two Windows 2008 R2 servers to become the DCs. The first run is 'adprep32 /forestprep'.  Then I read this: '...allow the changes to replicate throughout the forest before you prepare any domains', which refers to the next step 'adprep32 /domainprep /gpprep'.

What's the best way to know when the changes are finished replicating throughout the forest?  It's a small, in-house, local network. So, I'm assuming it will be within minutes and not some overnight wait.

Thanks.
Avatar of Mike Kline
Mike Kline
Flag of United States of America image

You can verify your schema is at 47

http://technet.microsoft.com/en-us/library/dd464018(v=ws.10).aspx#BKMK_VerifyForestPrep

I like using adfind with the shortcut to verify   http://adisfun.blogspot.com/2012/09/windows-2012-ad-schema-version.html

how many sites do you have?

Thanks

Mike
How many DC's do you currently have? if just one it would basicly be instant, would still give it 10 - 15 minutes.  

Joining to the DC for the windows 2008 R2 boxes will take the longest and for the most part depends on how many files it has to replicate on your domain.

To check files you can open run and type - \\domain.name\ and check the folder sizes in there.
Avatar of bs_ssg

ASKER

I am aware of the schema version.  It is currently 30, but will go to 47 after I run adprep32 from the 2008 R2 DVD.  I reckon I can assume that once both current DC's show the Schema Version at 47, then any replication initiated by adprep32 will have been completed?
But, when does the Schema Version change?  Is it after /forestprep or after /domainprep?

The current domain controllers are two very old Dell Poweredge tower style Windows 2000 and a Windows 2003 machines.  These are the only two in the system.  I'm replacing them with two Windows 2008 R2 machines that are HP DL120 G7s.  There are currently less than 200 'items' in Active Directory.

The replication here is just for the changes that adprep32 will make after running /forestprep and before running /domainprep.  So, I'm thinking this will be in that 10 - 15 minute range... or less, at which time I can then run the /domainprep /gpprep.

The longer process, as mentioned, will be when joining the new DCs to the system with dcpromo.
so better run adprep and the repadmin /syncall then wait for 10-15 Mins
SOLUTION
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bs_ssg

ASKER

Ok, back from the holidays...

Speaking of making a backup first, I see a lot of call for that.  But, then I never see any examples of what could happen, what errors might pop up, etc., that would require using a backup and then how to actually do the backup.

One of my concerns is exactly that.  The current system I am working with doesn't leave me with a lot of confidence that all will go smoothly.

Since I am adding new DC's to replace the old DC's and not doing an upgrade of the current DC's, how likely is it that I will need to recover using a backup?  How likely is it that running adprep32 will hose up the Windows 2000 Server DC and that prevents the new Windows 2008 DC's from being promotable and if that happens will the schema version have changed to 47 and then the backup recovery changes it back to 30?

This can be some scary stuff in the mind of a novice like me.  :-)

Thanks...
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bs_ssg

ASKER

I was laid off and I'm no longer working this issue.