RE: Migrating from Win2k DC's to Win2k3 DC's; ADPrep question

Thank you Amanda for the helpfull article, and the thorough response.

Once again, I hope to clarify the situation, as the answer you give leaves
me with the impression that you think we have a different configuration than
we actually do. We do not have any exchange 2000 servers whatsoever. We had
at one time, but ran the upgrade as instructed, which I believe included
working with adprep, which was the reason for my original question.

Current environtment:

Win2k server (DC, WINS, DNS, etc.)
Win2k server (DC, WINS, DNS, etc.)
Win2k server (member server, SQL 2000)
Win2k server (member server, Exchange 2003, not 2000)

The two new Win2k3 machines will replace the first two machines listed, then
those will be retired.

The article addresses problems with mangled attributes for forests with
Exchange 2000 servers. What I will have to investigate is if the this is
still in effect on a member server that was adprepped and upgraded to
Exchange 2003 running on Win2k. If you have any insight on this, let me know.

Yes, I agree with you that ideally, it would be wonderfull to build
everything in a pristine condition. Unfortunately I didn't have the choice
at that time. This is actually why I'm choosing to go with a non-in-place
upgrade for my domain controllers. Granted, the AD schema will be moved over
to the new boxes, but hopefully, the fact that there will be two new DC's
with clean builds will hopefully make my life a little easier.

Regardless, do you suggest that I run the adprep /forestprep and /domainprep
from the Windows Server 2003 CD? I'd hate to run it only to find out I used
an old version.

--
Sketchy


"Amanda Wang [MSFT]" wrote:

> Hello,
>
> Thanks for your update and the information is helpful.
>
> I have read the Q321648 article carefully and verify you are right if it is
> an in place upgrade.
>
> However, we strongly recommend you use not in place upgrade for security
> purpose. When you try to upgrade Windows 2000 DC to Windows 2003 while
> Exchange 2000 is installed. Under this circumstance, actually we suggest
> you first upgrade Exchange and run Exchange 2003 setup /forestprep to
> extend Windows 2000 AD and then we don't need to run Windows 2003 adprep
> any more.
>
> Why we suggest to do so? The reason is that Windows Server 2003 adprep
> /forestprep Command will Cause Mangled Attributes in Windows 2000 Forests
> That Contain Exchange 2000 Servers. Fore the current situation, you have
> upgraded Exchange 2k to 2k3 on Windows 2k server. Therefore, please read
> the following article carefully and verify the scenarios in it:
>
> 314649 Windows Server 2003 adprep /forestprep Command Causes Mangled
> Attributes
> http://support.microsoft.com/?id=314649
>
> For further questions related Exchange, please contact
> Microsoft.public.exchange2000 newsgroup to get the most qualified support
> on it.
>
> Meanwhile, you want to know if you have extended the schema for the Win2k3
> AD in general.
>
> If there is no ADPREP.LOG file in the
> %systemroot%\system32\debug\adprep\logs\<latest log> directory that means
> you haven't run it before.
>
> HTH!
>
> Thanks & Regards
>
> Amanda Wang [MSFT]
>
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> ====================================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================================
>
> --------------------
> >Thread-Topic: Migrating from Win2k DC's to Win2k3 DC's; ADPrep question
> >thread-index: AcVcm746WnMhm7sKRQyHhMIgGFpi4g==
> >X-WBNR-Posting-Host: 216.190.22.29
> >From: "=?Utf-8?B?c2tldGNoeQ==?=" <sketchy@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <31CB5B91-B194-437B-A1FB-91106FC2D93C@xxxxxxxxxxxxx>
> <JkRK0kEXFHA.3052@xxxxxxxxxxxxxxxxxxxxx>
> >Subject: RE: Migrating from Win2k DC's to Win2k3 DC's; ADPrep question
> >Date: Thu, 19 May 2005 10:54:03 -0700
> >Lines: 135
> >Message-ID: <03556CAA-7A88-4D90-A4FA-AF155539BA20@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.migration
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10262
> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >
> >Let my try to clarify my position.
> >
> >First, with regards to exchange (but getting off the subject of my
> original
> >question). Running Exchange 2003 on and Windows 2000 server is the ONLY
> way
> >to do an in-place upgrade of an exchange server. E2k will not run on an
> >Windows 2003 server. More info on this subject can be found at:
> >http://support.microsoft.com/?kbid=321648
> >
> >The ONLY reason I mentioned anything about my exchange box (a seperate
> Win2k
> >member server running E2k3 that is and has been running perfectly) is the
> >process of running ADPREP. So in other words, let us forget about the
> >ellement of the Exchange server. ...I simply wanted to know if what I ran
> >already extended the schema for the Win2k3 AD in general. (I am still
> >looking for the specific documentation that guided me on this).
> >
> >Based off of your response though, it sounds like I should plan on running
> >the ADPREP commands anyway. ...I looked for the log file that you
> suggested
> >on the domain controllers, and could not find them, so it's probably
> safest
> >to go ahead and run it.
> >
> >Thank you for your assistance on this. Much appreciated.
> >
> >--
> >Sketchy
> >
> >
> >"Amanda Wang [MSFT]" wrote:
> >
> >> Hello,
> >>
> >> Thanks for your post.
> >>
> >> I understand you want to know how to check if you have run the ADPREP
> >> command. If I have misunderstood, please feel free to let me know.
> >>
> >> Based on my experience, Exchange 2k3 cannot be installed on win2k
> server.
> >> If it is an in-place upgrade, you need to upgrade win2k to win2k3 first
> and
> >> then upgrade Exchange.
> >>
> >> If it is not a in-place upgrade, you need to install win2k3 member
> server
> >> in a new machine, on old win2k server, run adprep/forestprep to extend
> >> win2k schema to win2k3, then promote win2k3 member to be a DC.
> >>
> >> Run exchange forestprep, then install Exchange 2k3 on the new win2k3
> server.
> >>
> >> Also You mentioned that you may have run ADPREP command when you
> upgraded
> >> Exchange 2000 serer to Exchange 2003. When upgrading Exchange, the
> >> commands you have run from Exchange 2003 media only for Exchange and it
> is
> >> only extend the Exchange schema. Therefore, when upgrading Win2k3, you
> >> must run adprep command from \I386 folder of the Windows Server 2003
> media
> >> and this prepares for a Windows 2000 forest and its domains for the
> >> addition of Windows Server 2003 domain controllers and extends the
> Win2k3
> >> schema.
> >>
> >> The schema and infrastructure operations masters are used to introduce
> >> forest and domain-wide schema changes to the forest and its domains that
> >> are made by the Windows Server 2003 adprep utility.
> >>
> >> Please refer to the following KB article and pay more attention to the
> >> content related to adprep in this article:
> >>
> >> How to upgrade Windows 2000 domain controllers to Windows Server 2003
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;325379
> >>
> >> Also, if you want to check if the adprep command has been run before,
> you
> >> can check ADprep.log file in the
> >> C:\WINNT\system32\debug\adprep\logs\20040617142836 directory for more
> >> information.
> >>
> >> HTH!
> >>
> >> Thanks & Regards
> >>
> >> Amanda Wang [MSFT]
> >>
> >> Microsoft Online Partner Support
> >>
> >> Get Secure! - www.microsoft.com/security
> >>
> >> ====================================================================
> >>
> >> When responding to posts, please "Reply to Group" via your newsreader so
> >> that others may learn and benefit from your issue.
> >>
> >> =====================================================================
> >>
> >> --------------------
> >> >Thread-Topic: Migrating from Win2k DC's to Win2k3 DC's; ADPrep question
> >> >thread-index: AcVbycuoT2KYtFCHQoCmY+XOV5tc3w==
> >> >X-WBNR-Posting-Host: 216.190.22.29
> >> >From: "=?Utf-8?B?c2tldGNoeQ==?=" <sketchy@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >> >Subject: Migrating from Win2k DC's to Win2k3 DC's; ADPrep question
> >> >Date: Wed, 18 May 2005 09:51:11 -0700
> >> >Lines: 18
> >> >Message-ID: <31CB5B91-B194-437B-A1FB-91106FC2D93C@xxxxxxxxxxxxx>
> >> >MIME-Version: 1.0
> >> >Content-Type: text/plain;
> >> > charset="Utf-8"
> >> >Content-Transfer-Encoding: 7bit
> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >Content-Class: urn:content-classes:message
> >> >Importance: normal
> >> >Priority: normal
> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >Newsgroups: microsoft.public.windows.server.migration
> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >> >Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.windows.server.migration:10230
> >> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >> >
> >> >Hello everyone,
> >> >
> >> >I'm planning to move my domain controller responsibilities from two
> >> >antiquated Win2k DC's to some new servers that will be running Win2k3,
> >> then
> >> >retiring the two old boxes. I've been reading up as much as I can on
> >> this,
> >> >but do have a question inre to the ADPREP commands that I need to run.
> >> >
> >> >The documentation states that one needs to run ADPREP /FORESTPREP then
> >> >ADPREP /DOMAINPREP before proceeding further. It states that you
> should
> >> only
> >> >run this once however, implying that bad things happen if you do this
> more
> >> >than once. The problem is that I believe I ran these same commands
> when I
> >> >upgraded my Exchange 2000 serer to Exchange 2003 (It's still running
> >> Windows
> >> >2000), but can't remember for sure. Is there a command or a switch to
> the
> >> >ADPREP command that will allow me to check to see if my schema has
> already
> >> >been updated?
> >> >
> >> >--
> >> >Sketchy
> >> >
> >>
> >>
> >
>
>
.

Relevant Pages

  • Re: upgrade a Windows 2003 DC to R2
    ... MS-KBQ293783_Cannot Upgrade Windows 2000 Server to Windows Server 2003 with ... > when doing adprep forestprep. ... > "attributeId" attribute value for objects defined in Windows 2000 schema ...
    (microsoft.public.windows.server.active_directory)
  • RE: DST update for Exchange 2003 and Outlook 2003
    ... The Ldp GUI tool is included when you install Windows Server 2003 Support ... Microsoft CSS Online Newsgroup Support ... DST update for Exchange 2003 and Outlook 2003 ...
    (microsoft.public.exchange.admin)
  • RE: DST update for Exchange 2003 and Outlook 2003
    ... Majority of my users connect to Terminal Server and ... I also have users running on stand-alone PC's (Windows XP) ... run the Outlook Time Zone Data Update Tool or the Exchange calendar tool? ... 926666 Update for daylight saving time changes in 2007 for Exchange 2003 ...
    (microsoft.public.exchange.admin)
  • RE: Migrating from Win2k DCs to Win2k3 DCs; ADPrep question
    ... When you try to upgrade Windows 2000 DC to Windows 2003 while ... Exchange 2000 is installed. ... The reason is that Windows Server 2003 adprep ... 314649 Windows Server 2003 adprep /forestprep Command Causes Mangled ...
    (microsoft.public.windows.server.migration)
  • Re: upgrade from Win2k to win 2003 + exchange
    ... 842427 How to upgrade Exchange 2000 Server to Exchange Server 2003 in an ... 314649 Windows Server 2003 adprep /forestprep Command Causes Mangled ... > This is almost what I am looking for in order to upgrade our exchange 2000 ...
    (microsoft.public.exchange.setup)
Loading