AD Schema not extended properly
- Hi
My company has a windows Small Business Server 2003 R2 in Melbourne and we are trying to install a backup domain controller in Sydney with Windows Server 2003 R2. we want to use DFSR to replicate data between the two servers. When I try to set up a replication group it tells me that the
"active directory schema cannot be read. it might be caused by a schema that has not been extended or was extended improperly. a class schema object cannot be found"
I have checked and double checked and the schema has been extended using the adprep tool on the second disk of win server 2003 r2.
I would like to know how to find out if I have extended the schema improperly and whether there is something I can do about it.
Thanks in advance
Odpovědi
Hello khuscen,
From your description, it seems that you ran the ADPrep /ForestPrep, however it did not finish successfully. When you attempt to run ADPrep /ForestPrep again, its states that ForestPrep has already Extend the Schema.
Please try the following steps to re-extend the AD schema to see if it helps.
1. Pleases copy the I386 directory and from the 2nd Windows Server 2003 R2 installation disk to a location that could be accessed by the domain controller that is the Schema Master.2. Please Add or Change the following registry keys on that SBS 2003 R2 computer:
HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
DWORD "Correct Missing Objects"=1 (Missing)
DWORD "Schema Delete Allowed"=0 (Missing)
DWORD "Schema Update Allowed"=0 (Changed from 1 to 0).
3. Please move the data from the following paths to c:\Previous Attempts
%SystemRoot%\system32\debug\adprep
4. It is highly recommended you take a system state backup of the SBS 2003 R2 before making any changes to the environment.
then please delete:
CN=Windows2003Update,CN=ForestUpdates,CN=Configuration,DC=ForestRootDomain,DC=com
5. then change the ObjectVersion Attribute on the
cn=Schema,cn=configuration,dc=ForestRootDomain,dc=com to 30 (which is the version for Windows Server 2003 Schema.)
Version numbers:
13 = Windows 2000 Schema
30 = Windows Server 2003 Schema
31 = Windows Server 2003 R2 Schema
6. Please copy a schema.ini from a SBS 2003 environment that does not have the schema extended for SBS 2003 R2.
The schema.ini is under C:\Windows\system32 on a SBS 2003 R2.
7. Reboot the server.
8. Verify the ObjectVersion in ADSIEdit for the schema head.
9. Verify that in Regedit:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Schema Version = 30
10. Then please attempt to perform extend AD schema again:
ADPrep /ForestPrepFor more detailed about backup system state, please refer to:
Back up System State data
http://technet.microsoft.com/en-us/library/cc781353(WS.10).aspx
Hope it helps.
This posting is provided "AS IS" with no warranties, and confers no rights.- Označen jako odpověďDavid Shen - MSFTMSFT, Moderátor6. července 2009 3:33
Hi khuscen,
From the reply, the issue seems to be more related to SBS 2003. It is recommend you to initial a new thread in SBS community to get further support. The community members and support professionals there are more familiar with SBS and can help you in a more efficient way.For your convenience, I have list the link to SBS community as followed.
Discussions in microsoft.public.windows.server.sbs
Hope the issue will be resolved soon.
This posting is provided "AS IS" with no warranties, and confers no rights.- Označen jako odpověďDavid Shen - MSFTMSFT, Moderátor2. července 2009 14:20
Všechny reakce
Hello khuscen,
As far as I know, DFS-Replication component is not included in SBS 2003 R2. Since DFS-Replication will retrieve replication group information from AD, if there is no DFS-Replication component on SBS 2003 R2, the relevant AD schema objects doesn't exist on SBS 2003 R2.
Therefore, if you want to use DFSR to replicate data between Melbourne and Sydney, it is recommended that you use Windows Server 2003 R2 as the server platform in Melbourne. If you do not have Windows Server 2003 R2 server available, you will need to use FRS to replicate data.
Hope this can be helpful.
This posting is provided "AS IS" with no warranties, and confers no rights.- Zrušeno označení jako odpověďkhuscen 28. června 2009 23:11
- Označen jako odpověďDavid Shen - MSFTMSFT, Moderátor28. června 2009 4:26
- Zrušeno navržení jako odpověďDavid Shen - MSFTMSFT, Moderátor29. června 2009 8:26
- Navržen jako odpověďDavid Shen - MSFTMSFT, Moderátor26. června 2009 10:27
- Thanks david for your reply... if i had three dcs, two with win server 2003 but the pdc is still sbs 2003 should i be able to use dfsr to replicate between those two machines with win server 2003? because when i try to it still tells me that the schem was extended improperly.
Hi Khuscen,
According to the following SBS blog, we should be able to upgrade the schema on SBS 2003 R2 to Windows Server 2003 R2 (31) if we want use DFSR to replicate folders among the two machines with Windows Server 2003 R2.http://blogs.technet.com/sbs/archive/2006/02/28/420825.aspx
To upgrade the schema, we need to use the 2nd disk of Windows Server 2003 R2.
1. 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
Note: You can verify the operating system support level of the schema by looking at the value of the Schema Version registry subkey on a domain controller. You can find this subkey in the following location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters
Please check the schema version on the SBS 2003 R2.
You can also verify the operating system support level of the schema by using the Adsiedit.exe utility or the Ldp.exe utility to view the objectVersion attribute in the properties of the
cn=schema,cn=configuration,dc= <domain> partition.
The value of the Schema Version registry subkey and the objectVersion attribute are in decimal.
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
Please check the ObjectVersion value and give us the result.
I appreciate your time and effort.
This posting is provided "AS IS" with no warranties, and confers no rights.- Hi David thanks again for all your help.
I have checked the registry key on SBS 2003 and it tells me the schema version is 31.
The objectversion value on sbs 2003 using adsiedit is 30!! but I have run the adprep tool from win server 2003 r2 on sbs 2003 and it tell me that I have extended the schema. but this tells me I havent! What can I do now???
Hello khuscen,
From your description, it seems that you ran the ADPrep /ForestPrep, however it did not finish successfully. When you attempt to run ADPrep /ForestPrep again, its states that ForestPrep has already Extend the Schema.
Please try the following steps to re-extend the AD schema to see if it helps.
1. Pleases copy the I386 directory and from the 2nd Windows Server 2003 R2 installation disk to a location that could be accessed by the domain controller that is the Schema Master.2. Please Add or Change the following registry keys on that SBS 2003 R2 computer:
HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
DWORD "Correct Missing Objects"=1 (Missing)
DWORD "Schema Delete Allowed"=0 (Missing)
DWORD "Schema Update Allowed"=0 (Changed from 1 to 0).
3. Please move the data from the following paths to c:\Previous Attempts
%SystemRoot%\system32\debug\adprep
4. It is highly recommended you take a system state backup of the SBS 2003 R2 before making any changes to the environment.
then please delete:
CN=Windows2003Update,CN=ForestUpdates,CN=Configuration,DC=ForestRootDomain,DC=com
5. then change the ObjectVersion Attribute on the
cn=Schema,cn=configuration,dc=ForestRootDomain,dc=com to 30 (which is the version for Windows Server 2003 Schema.)
Version numbers:
13 = Windows 2000 Schema
30 = Windows Server 2003 Schema
31 = Windows Server 2003 R2 Schema
6. Please copy a schema.ini from a SBS 2003 environment that does not have the schema extended for SBS 2003 R2.
The schema.ini is under C:\Windows\system32 on a SBS 2003 R2.
7. Reboot the server.
8. Verify the ObjectVersion in ADSIEdit for the schema head.
9. Verify that in Regedit:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Schema Version = 30
10. Then please attempt to perform extend AD schema again:
ADPrep /ForestPrepFor more detailed about backup system state, please refer to:
Back up System State data
http://technet.microsoft.com/en-us/library/cc781353(WS.10).aspx
Hope it helps.
This posting is provided "AS IS" with no warranties, and confers no rights.- Označen jako odpověďDavid Shen - MSFTMSFT, Moderátor6. července 2009 3:33
- Hi David
See underlined below.
2. Please Add or Change the following registry keys on that SBS 2003 R2 computer:
HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
DWORD "Correct Missing Objects"=1 (Missing)
DWORD "Schema Delete Allowed"=0 (Missing) already have this
DWORD "Schema Update Allowed"=0 (Changed from 1 to 0). already 0
does this change anything?
4. It is highly recommended you take a system state backup of the SBS 2003 R2 before making any changes to the environment.
then please delete:
CN=Windows2003Update,CN=ForestUpdates,CN=Configuration,DC=ForestRootDomain,DC=com
5. then change the ObjectVersion Attribute on the
cn=Schema,cn=configuration,dc=ForestRootDomain,dc=com to 30 (which is the version for Windows Server 2003 Schema.) this is already 30!
Version numbers:
13 = Windows 2000 Schema
30 = Windows Server 2003 Schema
31 = Windows Server 2003 R2 Schema
6. Please copy a schema.ini from a SBS 2003 environment that does not have the schema extended for SBS 2003 R2.
The schema.ini is under C:\Windows\system32 on a SBS 2003 R2.
I found two schema.ini one in c:\windows last modified in july 2007 in and one in system32 modeified in 2006. Is either of these all right for use or where can I get one that has not been extended? and how do you tell anyway?
Hi khuscen,
From the reply, the issue seems to be more related to SBS 2003. It is recommend you to initial a new thread in SBS community to get further support. The community members and support professionals there are more familiar with SBS and can help you in a more efficient way.For your convenience, I have list the link to SBS community as followed.
Discussions in microsoft.public.windows.server.sbs
Hope the issue will be resolved soon.
This posting is provided "AS IS" with no warranties, and confers no rights.- Označen jako odpověďDavid Shen - MSFTMSFT, Moderátor2. července 2009 14:20
