saying ADPREP doesn't change much over time is actually not quite right - it
has evolved quite a bit to include better error-handling logic and user
guidance to fix potential issues, as well as additional commandline options
to control the exact update behaviour for ACLs on SYSVOL (/DomainPrep
/GPprep).
Also the version of ADPREP you're using will determine which LDIF files will
be used to extend the schema - the SP1 ADPREP version will only update the
schema to version 30 (same version as Win2003 RTM, except for a change in the
tombstonelifetime set in the SCHEMA.INI file, which only matters for new
forests). As such it won't change anything in an existing Win2003 schema.
However, the ADPREP from the R2 disk will add another file to the list of
schema LDIF files, which will update the schema to version 31 and include all
the R2 specific schema changes.
It's a different question if you need the R2 schema extensions or not:
=> you will need them if you plan to use any new R2 features that relies on
these extensions, such as DFSR or the PrintMgmt console with the capabilities
to distribute printer queues to clients via GPO
=> some R2 features do not require the R2 schema extensions, such as ADFS
(ADFS merely needs to run on an R2 box)
=> naturally, as soon as you wish to promote an existing Win2003 R2 server
(either 32 or 64-bit), you'll also need to extend the schema to R2
Mixing the ADPREP version with different Schema LDIF files and a different
schema.ini file can lead to an undesired state and as such I'd not recommend
using this approach.
As such, if you care to update your existing Win2003 AD schema to the "real"
R2 schema on an exsiting 32-bit DC, you'll have to use the 32-bit version of
the R2-CD2 (although
http://support.microsoft.com/?kbid=917385 suggests the
64-bit R2-CD2 should have both x86 and x64 bits of ADPREP, I couldn't find it
on the 64-bit CD).
/Guido
"Charlie Russel - MVP" wrote:
> adprep doesn't change much over time. All the smarts are in the .LDF files.
>
> Charlie.
>
> "akeiii" <> wrote in message
> news:1FAC8437-C2B0-4CB3-8CA5-...
> > Thanks for the reply, I did not know I could use the ADPREP from Windows
> > Server 2003 with the LDF files from Windows Server 2003x64 R2. I did
> > locate
> > CD2 from the 32 bit version of R2 so now I have two solutions.
> >
> >
> > "Charlie Russel - MVP" wrote:
> >
> >> You can actually use the version of adprep from your SP1 installation,
> >> it's
> >> the LDF files that are in the same directory on the R2 CD that you need.
> >> The
> >> alternative is, of course, a 32-bit version of the R2 CD which will have
> >> the
> >> 32-bit version of adprep.
> >>
> >> --
> >> Charlie.
> >> http://msmvps.com/xperts64
> >>
> >>
> >> "akeiii" <> wrote in message
> >> news:4C6B315B-E55B-41E7-9CB7-...
> >> >I have a domain with Windows Server 2003 SP1 domain controller. I have
> >> > installed a new server with Windows Server 2003x64 R2. I want to
> >> > promote
> >> > the
> >> > new server to a domain controller. My CATCH22 is:
> >> >
> >> > 1.) ADPREP.EXE from CD2 of Windows Server 2003x64 R2 must be run to
> >> > prep
> >> > the forest.
> >> > 2.) ADPREP.EXE must be run on the operations master.
> >> > 3.) The operations master is Windows Server 2003 SP1 (32 bit).
> >> > 4.) The ADPREP.EXE from the Windows Server 2003x64 R2 will not run on
> >> > the
> >> > current operations master!
> >> >
> >> > I can not find a download for the version of ADPREP I need.
> >>
> >>
>