2003 R2 Extensions Space Rquirements

Can someone tell me the space requirements for to upgrade an existing 2003
domain controller to R2?

Thanks

> Can someone tell me the space requirements for to upgrade an existing 2003
> domain controller to R2?


If you have cause to worry about space, you might consider taking care of
that problem now rather than later. After all there WILL be service packs on
down the line that need to be installed.


hth
DDS

"Steve" <> wrote in message
news:188F7E3C-BB85-41A6-81FE-...
> Can someone tell me the space requirements for to upgrade an existing 2003
> domain controller to R2?
>
> Thanks

You're absolutely correct, this domain controller is getting replaced I have
another server that is already R2 and I would like to promote the new server.
Before I do that I need to update the AD with the new R2 extensions, but I
don't have a very big system partition on the old server.
Am I incorrect in my migration plan?

"Danny Sanders" wrote:

> > Can someone tell me the space requirements for to upgrade an existing 2003
> > domain controller to R2?
>
>
> If you have cause to worry about space, you might consider taking care of
> that problem now rather than later. After all there WILL be service packs on
> down the line that need to be installed.
>
>
> hth
> DDS
>
> "Steve" <> wrote in message
> news:188F7E3C-BB85-41A6-81FE-...
> > Can someone tell me the space requirements for to upgrade an existing 2003
> > domain controller to R2?
> >
> > Thanks
>
>
>

Dear Customer,

Thank you for posting in newsgroup. And thanks to Danny for the
contribution.

According to the description, you want to know the space requirements for
to upgrade an existing Windows Server 2003 domain controller to Windows
Server 2003 R2 domain controller. If I have any misunderstanding, please
feel free to let me know.

Based on the research, here is some information which may be helpful for
you.

Analysis and Suggestions:
=====================

According to the test, we need to upgrade the schema version to Windows
Server 2003 R2 level by using "adprep.exe /forestprep" and "adprep.exe
/domainprep" from second Installation CD of Windows 2003 R2. This operation
will extend the forest and domain schema, which won't take lots of disk
space. However, the required Windows Server 2003 Service Pack 1 requires
329.3MB disk space to be installed. If you install extra components
included in Windows Server 2003 R2, you will need additional disk spaces.

I agree with Danny’s opinion. When we plan disk requirement, we should take
future service pack, hot fix, updates and application installation into
consideration and allocate enough buffer.

Hope it helps.

David Shen
Microsoft Online Partner Support

Thanks for the info. I've already installed SP1, I just wanted to make sure
the schema upgrades could be installed so then I'll be able to promote
another domain controller that is already R2. This current DC will
eventually be retired, so space planning isn't a primary concern.

"David Shen [MSFT]" wrote:

> Dear Customer,
>
> Thank you for posting in newsgroup. And thanks to Danny for the
> contribution.
>
> According to the description, you want to know the space requirements for
> to upgrade an existing Windows Server 2003 domain controller to Windows
> Server 2003 R2 domain controller. If I have any misunderstanding, please
> feel free to let me know.
>
> Based on the research, here is some information which may be helpful for
> you.
>
> Analysis and Suggestions:
> =====================
>
> According to the test, we need to upgrade the schema version to Windows
> Server 2003 R2 level by using "adprep.exe /forestprep" and "adprep.exe
> /domainprep" from second Installation CD of Windows 2003 R2. This operation
> will extend the forest and domain schema, which won't take lots of disk
> space. However, the required Windows Server 2003 Service Pack 1 requires
> 329.3MB disk space to be installed. If you install extra components
> included in Windows Server 2003 R2, you will need additional disk spaces.
>
> I agree with Danny’s opinion. When we plan disk requirement, we should take
> future service pack, hot fix, updates and application installation into
> consideration and allocate enough buffer.
>
> Hope it helps.
>
> David Shen
> Microsoft Online Partner Support
>
>

Actually the adprep needs to be ran on the schema master for the domain
which is one of the FSMO roles, which CAN be moved if necessary.

hth
DDS

"Steve" <> wrote in message
news:4834C1EC-DB83-4093-BA88-...
> Thanks for the info. I've already installed SP1, I just wanted to make
> sure
> the schema upgrades could be installed so then I'll be able to promote
> another domain controller that is already R2. This current DC will
> eventually be retired, so space planning isn't a primary concern.
>
> "David Shen [MSFT]" wrote:
>
>> Dear Customer,
>>
>> Thank you for posting in newsgroup. And thanks to Danny for the
>> contribution.
>>
>> According to the description, you want to know the space requirements for
>> to upgrade an existing Windows Server 2003 domain controller to Windows
>> Server 2003 R2 domain controller. If I have any misunderstanding, please
>> feel free to let me know.
>>
>> Based on the research, here is some information which may be helpful for
>> you.
>>
>> Analysis and Suggestions:
>> =====================
>>
>> According to the test, we need to upgrade the schema version to Windows
>> Server 2003 R2 level by using "adprep.exe /forestprep" and "adprep.exe
>> /domainprep" from second Installation CD of Windows 2003 R2. This
>> operation
>> will extend the forest and domain schema, which won't take lots of disk
>> space. However, the required Windows Server 2003 Service Pack 1 requires
>> 329.3MB disk space to be installed. If you install extra components
>> included in Windows Server 2003 R2, you will need additional disk spaces.
>>
>> I agree with Danny's opinion. When we plan disk requirement, we should
>> take
>> future service pack, hot fix, updates and application installation into
>> consideration and allocate enough buffer.
>>
>> Hope it helps.
>>
>> David Shen
>> Microsoft Online Partner Support
>>
>>

Hello Steve,

Thanks for the reply. I understand your mainly concern.

Yes. You can upgrade the forest and domain schema on the old DC and then
introduce the new Windows Server 2003 R2 to be an additional DC in the
domain. Afterwards, you may demote the old DC.

For the Schema upgrade on the old DC, it won't take much space, the system
only extend the schema by importing several .ldf files to the current
domain.

You may verify the Active Directory verify the level of the schema by using
the Adsiedit.exe or the "AD Explorer" to view the "objectVersion" attribute
in the properties of the "CN=Schema, CN=Configuration, DC= <domain>
partition".

The Schema Version ObjectVersion values and corresponding operating system
support level:

13=Microsoft Windows 2000
30=Original release version of Microsoft Windows Server 2003 and Microsoft
Windows Server 2003 Service Pack 1 (SP1)
31=Microsoft Windows Server 2003 R2

For your convenience, I have list some general steps for your reference.

Since the following operation have potential damage to Active Directory
database, it is highly suggested that you'd better perform a full backup of
Active Directory (System State) firstly. Also it is better to test the
following procedure in a similar lab environment first.

General Steps:
=============

1. Verify the new server's TCP/IP configuration has been pointed to the
current DNS server.

2. Make the new server become a member server of the current Windows Server
2003 domain first.

3. Upgrade the Windows Server 2003 forest schema to Windows Server 2003 R2
schema with the "adprep /forestprep" command on old server.

Please run the "adprep.exe /forestprep" command from the Windows Server
2003 R2 installation disk 2 on the schema master. To do this, insert the
Windows Server 2003 R2 installation disk 2, and then type the following
command:

Drive:\CMPNENTS\R2\ADPREP\adprep.exe /forestprep

4. Upgrade the Windows 2003 domain schema with the "adprep /domainprep"
command on old server.

Please run the "adprep.exe /domainprep" command from the Windows Server
2003 R2 installation disk 2 on the infrastructure master. To do this,
insert the Windows Server 2003 R2 installation disk 2, and then type the
following command:

Drive:\CMPNENTS\R2\ADPREP\adprep.exe /domainprep

5. Run "dcpromo" on new server to promote it as an additional domain
controller in existing Windows 2003 domain, afterwards you may verify the
installation of Active Directory.

Please refer to:
How to Verify an Active Directory Installation in Windows Server 2003
http://support.microsoft.com/kb/816106

6. Verify the new server's TCP/IP configuration has been pointed to current
DNS server.

7. If you have DHCP server to migrate, we suggested that you perform the
DHCP database migration before promoting it to a domain controller.

8. Export the DHCP database from the current DHCP server using the DHCP
Export Import utility (Dhcpexim.exe). You may migrate the DHCP database to
a Windows 2003 domain controller.

9. Install the DHCP server service on the new server that is running
Windows Server 2003 if necessary. Import the DHCP database to the new DHCP
server

Please refer to:

How to move a DHCP database from a computer that is running Windows NT
Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is
running Windows Server 2003
http://support.microsoft.com/kb/325473

10. Adjust DHCP scope settings to make them use the new DNS server.

11. Unauthorize the old DHCP server and Authorize the new DHCP server and
so that the new one can work normally within Active Directory.

12. Insert Windows Server 2003 R2 Installation Disc in the new server.

13. Run "dcpromo" on new server to promote it as an additional domain
controller in existing Windows 2003 domain, afterwards you may verify the
installation of Active Directory.

14. Enable Global Catalog on new server and manually Check Replication
Topology and afterwards manually trigger replication (Replicate Now) to
synchronize Active Directory database between 2 replicas.

Please note: It will some time to replicate GC between DC, please wait some
time with patience.

15. Disable Global Catalog on the old DC.

16. Transfer all the FSMO role from the old DC to the new DC.

Please refer to:
How to view and transfer FSMO roles in Windows Server 2003
http://support.microsoft.com/kb/324801

17. Verify that the old DNS Server Zone type is Active
Directory-Integrated. If not, please refer to:

How To: Convert DNS Primary Server to Active Directory Integrated
http://support.microsoft.com/kb/816101

Note: Active Directory Integrated-Zone is available only if DNS server is a
domain controller.

18. Install DNS component on new server and configure it as a new DNS
Server (Active Directory Integrated-Zone is preferred). All the DNS
configuration should be replicated to the new DNS server with Active
Directory Replication.

19. Make all the clients change TCP/IP configuration to point to new server
as DNS.

20. You may configure TCP/IP on all the clients, or adjust DHCP scope
settings to make them use the new DNS server.

Please note: It is a good practice to make the old DC offline for several
days and check whether everything works normally with the new server
online. If so, you may let the old DC online and run DCPROMO to demote it.

Hope the information can help.

David Shen
Microsoft Online Partner Support

Dear Customer,

I am just writing to see how everything is going. If you have any updates
or need any further assistance on this issue, please feel free to let me
know. I am glad to be of assistance.

David Shen
Microsoft Online Partner Support

Thanks David, that was more than I expected.

"David Shen [MSFT]" wrote:

> Hello Steve,
>
> Thanks for the reply. I understand your mainly concern.
>
> Yes. You can upgrade the forest and domain schema on the old DC and then
> introduce the new Windows Server 2003 R2 to be an additional DC in the
> domain. Afterwards, you may demote the old DC.
>
> For the Schema upgrade on the old DC, it won't take much space, the system
> only extend the schema by importing several .ldf files to the current
> domain.
>
> You may verify the Active Directory verify the level of the schema by using
> the Adsiedit.exe or the "AD Explorer" to view the "objectVersion" attribute
> in the properties of the "CN=Schema, CN=Configuration, DC= <domain>
> partition".
>
> The Schema Version ObjectVersion values and corresponding operating system
> support level:
>
> 13=Microsoft Windows 2000
> 30=Original release version of Microsoft Windows Server 2003 and Microsoft
> Windows Server 2003 Service Pack 1 (SP1)
> 31=Microsoft Windows Server 2003 R2
>
> For your convenience, I have list some general steps for your reference.
>
> Since the following operation have potential damage to Active Directory
> database, it is highly suggested that you'd better perform a full backup of
> Active Directory (System State) firstly. Also it is better to test the
> following procedure in a similar lab environment first.
>
> General Steps:
> =============
>
> 1. Verify the new server's TCP/IP configuration has been pointed to the
> current DNS server.
>
> 2. Make the new server become a member server of the current Windows Server
> 2003 domain first.
>
> 3. Upgrade the Windows Server 2003 forest schema to Windows Server 2003 R2
> schema with the "adprep /forestprep" command on old server.
>
> Please run the "adprep.exe /forestprep" command from the Windows Server
> 2003 R2 installation disk 2 on the schema master. To do this, insert the
> Windows Server 2003 R2 installation disk 2, and then type the following
> command:
>
> Drive:\CMPNENTS\R2\ADPREP\adprep.exe /forestprep
>
> 4. Upgrade the Windows 2003 domain schema with the "adprep /domainprep"
> command on old server.
>
> Please run the "adprep.exe /domainprep" command from the Windows Server
> 2003 R2 installation disk 2 on the infrastructure master. To do this,
> insert the Windows Server 2003 R2 installation disk 2, and then type the
> following command:
>
> Drive:\CMPNENTS\R2\ADPREP\adprep.exe /domainprep
>
> 5. Run "dcpromo" on new server to promote it as an additional domain
> controller in existing Windows 2003 domain, afterwards you may verify the
> installation of Active Directory.
>
> Please refer to:
> How to Verify an Active Directory Installation in Windows Server 2003
> http://support.microsoft.com/kb/816106
>
> 6. Verify the new server's TCP/IP configuration has been pointed to current
> DNS server.
>
> 7. If you have DHCP server to migrate, we suggested that you perform the
> DHCP database migration before promoting it to a domain controller.
>
> 8. Export the DHCP database from the current DHCP server using the DHCP
> Export Import utility (Dhcpexim.exe). You may migrate the DHCP database to
> a Windows 2003 domain controller.
>
> 9. Install the DHCP server service on the new server that is running
> Windows Server 2003 if necessary. Import the DHCP database to the new DHCP
> server
>
> Please refer to:
>
> How to move a DHCP database from a computer that is running Windows NT
> Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is
> running Windows Server 2003
> http://support.microsoft.com/kb/325473
>
> 10. Adjust DHCP scope settings to make them use the new DNS server.
>
> 11. Unauthorize the old DHCP server and Authorize the new DHCP server and
> so that the new one can work normally within Active Directory.
>
> 12. Insert Windows Server 2003 R2 Installation Disc in the new server.
>
> 13. Run "dcpromo" on new server to promote it as an additional domain
> controller in existing Windows 2003 domain, afterwards you may verify the
> installation of Active Directory.
>
> 14. Enable Global Catalog on new server and manually Check Replication
> Topology and afterwards manually trigger replication (Replicate Now) to
> synchronize Active Directory database between 2 replicas.
>
> Please note: It will some time to replicate GC between DC, please wait some
> time with patience.
>
> 15. Disable Global Catalog on the old DC.
>
> 16. Transfer all the FSMO role from the old DC to the new DC.
>
> Please refer to:
> How to view and transfer FSMO roles in Windows Server 2003
> http://support.microsoft.com/kb/324801
>
> 17. Verify that the old DNS Server Zone type is Active
> Directory-Integrated. If not, please refer to:
>
> How To: Convert DNS Primary Server to Active Directory Integrated
> http://support.microsoft.com/kb/816101
>
> Note: Active Directory Integrated-Zone is available only if DNS server is a
> domain controller.
>
> 18. Install DNS component on new server and configure it as a new DNS
> Server (Active Directory Integrated-Zone is preferred). All the DNS
> configuration should be replicated to the new DNS server with Active
> Directory Replication.
>
> 19. Make all the clients change TCP/IP configuration to point to new server
> as DNS.
>
> 20. You may configure TCP/IP on all the clients, or adjust DHCP scope
> settings to make them use the new DNS server.
>
> Please note: It is a good practice to make the old DC offline for several
> days and check whether everything works normally with the new server
> online. If so, you may let the old DC online and run DCPROMO to demote it.
>
> Hope the information can help.
>
> David Shen
> Microsoft Online Partner Support
>
>

Hello Steve,

I am glad that the information is helpful for you. If you have other
question, welcome to the newsgroup again.

Thanks.

David Shen
Microsoft Online Partner Support