Re: 2003 R2 version question

Thanks for the tip Paul, as soon I am in i will check what you said. I will
keep you all informed.



You know what just to be clear use adsi edit and verify both domains via the
details below:
http://technet2.microsoft.com/windowsserver/en/library/ed42abd5-24c7-4b5a-8165-dbd96727ec841033.mspx?mfr=true
Verify the schema extension
After you run Adprep, you can use the Windows Support tool ADSI Edit to
verify the schema extension.

To verify the schema extension

1. Log on to an administrative workstation that has ADSI Edit
installed.

2. Click Start, click Run, type adsiedit.msc, and then click
OK.

3. Double-click Configuration Container, and then double-click
CN=Configuration,DC=forest_root_domain

where forest_root_domain is the fully qualified domain name
(FQDN) of your forest root domain.

4. Double-click CN=ForestUpdates.

5. Right-click CN=Windows2003Update, and then click Properties.

6. Verify that the Revision attribute value is 9.

7. Double-click Schema.

8. Right-click CN=Schema,CN=Configuration,DC=forest_root_domain

where forest_root_domain is the FQDN of your forest root domain.

9. Click Properties.

10. On the Attributes tab, for Select a property to view,
select objectVersion.

11. Verify that Value(s) equals 31.




--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Paul Bergson [MVP-DS]" <pbergson@xxxxxxxxxxxxxxxxx> wrote in message
news:...
Hummmhhhhhh

I know 31 in the forest root is the correct version, a bit odd that the
child is at 30. Let me ping a couple folks and see what I can find out.
It sounds like there is a problem with your schema replication though.

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.

"eric b" <ericb@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2A24FEE0-D201-4496-8FA2-F8F12E520EAD@xxxxxxxxxxxxxxxx
so this is a correct configuration?
Parent domain:
on one of the dc I opened the registry and these settings are there:
HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\System Schema
Version, REG_DWORD, 0x0000001f (31)

Child domain:
on one of the dc I opened the registry and these settings are there:
HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\System Schema
Version, REG_DWORD, 0x0000001e (30)

rgds, eric

"Paul Bergson [MVP-DS]" wrote:

Since schema extensions are forest wide you only need to do this once
per
forest.

http://technet2.microsoft.com/windowsserver/en/library/84445c1b-a418-4a09-a50c-5f3258cfc5b51033.mspx?mfr=true

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.

"eric b" <ericb@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D9431AEC-3F5D-40E9-A6B9-9CDAB19D5BE0@xxxxxxxxxxxxxxxx
Hello all,

I have a question about schema version.

In the company where I work now they have a variety of windows DC
controllers.

I want to standardize them to windows 2003 SP2 R2.

We have 1 root domain and three child domains

In the root domains there are NO R2 DC and the schema version is 31

In the child domains there are some R2 DC but the schema version is 30


So here is my question: is it necessarily to do a domain prep on the
child
domain from the second R2 cd or is the forrest prep they did before
enough
to
complete the migration to a full 2003 domain functional level.

rgds

Eric B.






.

Relevant Pages

  • Re: 2003 R2 version question
    ... You know what just to be clear use adsi edit and verify both domains via the ... Verify the schema extension ... where forest_root_domain is the FQDN of your forest root domain. ... In the child domains there are some R2 DC but the schema version is 30 ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 R2 version question
    ... When you change the schema on the schema operations master, ... root domain is version 31and that the DC in the child domains are ... You know what just to be clear use adsi edit and verify both domains via ... We have 1 root domain and three child domains ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 R2 version question
    ... not a AD domain prep. ... After the forest prep they where able to install and ... sounds like there is a problem with your schema replication though. ... In the child domains there are some R2 DC but the schema version is 30 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Clone AD Schema to Lab
    ... child domains and 450+ DC's.... ... Is their any other was to clone the schema into the lab? ... Would doing an ldifde export/import work? ...
    (microsoft.public.windows.server.active_directory)
  • Re: DCPROMO 2003 Advanced Server, forest version incorrect
    ... I agree with Barundi that you need to run adprep in the second CD. ... You can verify the operating system support level of the schema by looking ...
    (microsoft.public.windows.server.migration)