Re: adprep/ forestprep

One more item to add here. We have some business processing at night. With
outbound replication disabled for awhile at 6pm and then replication
happening after forestprep, will this affect Users? I figured I would run
the domainprep saturday Noon and then run winnt32 on the 2000DC on Sunday
afternoon after backing up AD again.

"Ace Fekay [MVP]" wrote:

In news:5321CC20-AECC-4F65-AD32-831C5B9C38AA@xxxxxxxxxxxxx,
BA <BA@xxxxxxxxxxxxxxxxxxxxxxxxx> stated, which I commented on below:
Upgrading 2000 to 2003 domain. To ensure replication completes after
each step, is it OK to run forest prep, domain prep and winnt32 to
the DC over a span of 3 days or should it all be done on one off
business hours day? We have 11 sites. One DC at each site. Thanks
for any input you have.

What is your site replication schedule? I would run both on the Schema
master on Friday eve. If you have a hub and spoke replication model from the
central office to the branches, and it;'s set to default (3 hours), then
after 3 hours it will be done.

If you have Exchange on the system, that may complicate things a bit and
need to run a script to clean up mangled attributes prior to the forestprep
to even be able to run. See the link below for more info. I would just run
the forestprep. If the error pops up, then fix it.

314649 - Windows Server 2003 adprep -forestprep Command Causes Mangled
Attributes in Windows 2000 Forests That Contain Exchange:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314649


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.

It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only thing in life is change. Anything more is a blackhole consuming
unnecessary energy. - [Me]



.

Relevant Pages

  • RE: Upgrading from Win2000 domains to Win2003 domains: ROLL BACK !
    ... Yes you can disable outbound replication on the Schema master prior to ... running forestprep to prevent those changes from replicating out. ... change is to bring down all DCs that have it and restore from backup / demote. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Upgrading from Windows 2000 to Windows 2003
    ... replication to take place so that the other domain controller has the ... containers at the same level as the ... our other domain controller is not receiving the ForestPrep updates. ...
    (microsoft.public.windows.server.migration)
  • Re: Upgrading from Windows 2000 to Windows 2003
    ... I tried to force replication to the other domain controller in the ... that didn't get replicated was the ForestPrep containers. ...
    (microsoft.public.windows.server.migration)
  • Re: Upgrading from Windows 2000 to Windows 2003
    ... that its working fine while the ForestPrep contains still not replicated? ... >recreate the replication ring because the domain controllers could not ... >controller before replicating it to all the domain controllers. ... the Operations Container is supposed to be there. ...
    (microsoft.public.windows.server.migration)
  • Installing Exchange 2003, problems with /ForestPrep Switch Commands
    ... I have run ForestPrep and DomainPrep per the Microsoft deployment ... guide and everything appears to have been successful. ... ready to run the Exchange 2003 install and run the E:\setup\i386\setup ...
    (microsoft.public.exchange.setup)
Loading