Schema extensions Warning before install SCCM 2007
I have got an warning "Schema extensions" when I'm running Prerequisite Check on a member server of my single forest,even Iperform schema extension by running "Extadsch.exe" from the Schema Master Domain Controller on the same forest. Do I need to promote my SCCM 2007 Server to a DC also? Thank you!
July 6th, 2009 12:25pm

No, you don't. But you should verify that the extend schema process was successful. Check the extadsch.log file on the server where you ran the extadsch.exe utility. Most likely it didn't succeed.Kent Agerlund | http://agerlund.spaces.live.com/blog/
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2009 12:31pm

Hi Aiya,Can you check the C:\ConfigMgrPrereq.log for more information? Perhaps it is unable to locate a DC.Please mark posts as Answered if appropriate.
July 6th, 2009 1:17pm

Hi Kent & Jannes,Below is my ConfigMgrPrereq.log and ExtADSch.log. From ExtADSch.log, it shows successfully extended the Active Directory schema, and from ConfigMgrPrereq.log, I cannot see more information about the schema extensions warning. Please help !!! Thank you!ExtADSch.log:<07-06-2009 17:15:33> Modifying Active Directory Schema - with SMS extensions.<07-06-2009 17:15:33> DS Root:CN=Schema,CN=Configuration,DC=moon,DC=ad<07-06-2009 17:15:33> Attribute cn=MS-SMS-Site-Code already exists.<07-06-2009 17:15:33> Attribute cn=mS-SMS-Assignment-Site-Code already exists.<07-06-2009 17:15:33> Attribute cn=MS-SMS-Site-Boundaries already exists.<07-06-2009 17:15:33> Attribute cn=MS-SMS-Roaming-Boundaries already exists.<07-06-2009 17:15:33> Attribute cn=MS-SMS-Default-MP already exists.<07-06-2009 17:15:33> Attribute cn=mS-SMS-Device-Management-Point already exists.<07-06-2009 17:15:33> Attribute cn=MS-SMS-MP-Name already exists.<07-06-2009 17:15:33> Attribute cn=MS-SMS-MP-Address already exists.<07-06-2009 17:15:34> Defined attribute cn=mS-SMS-Health-State.<07-06-2009 17:15:34> Defined attribute cn=mS-SMS-Source-Forest.<07-06-2009 17:15:34> Attribute cn=MS-SMS-Ranged-IP-Low already exists.<07-06-2009 17:15:34> Attribute cn=MS-SMS-Ranged-IP-High already exists.<07-06-2009 17:15:34> Defined attribute cn=mS-SMS-Version.<07-06-2009 17:15:35> Defined attribute cn=mS-SMS-Capabilities.<07-06-2009 17:15:35> Class cn=MS-SMS-Management-Point already exists.<07-06-2009 17:15:35> Located LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=moon,DC=ad<07-06-2009 17:15:35> Successfully updated class LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=moon,DC=ad.<07-06-2009 17:15:35> Class cn=MS-SMS-Server-Locator-Point already exists.<07-06-2009 17:15:35> Located LDAP://cn=MS-SMS-Server-Locator-Point,CN=Schema,CN=Configuration,DC=moon,DC=ad<07-06-2009 17:15:35> Successfully updated class CN=Schema,CN=Configuration,DC=moon,DC=ad.<07-06-2009 17:15:35> Class cn=MS-SMS-Site already exists.<07-06-2009 17:15:35> Located LDAP://cn=MS-SMS-Site,CN=Schema,CN=Configuration,DC=moon,DC=ad<07-06-2009 17:15:35> Successfully updated class LDAP://cn=MS-SMS-Site,CN=Schema,CN=Configuration,DC=moon,DC=ad.<07-06-2009 17:15:35> Class cn=MS-SMS-Roaming-Boundary-Range already exists.<07-06-2009 17:15:35> Located LDAP://cn=MS-SMS-Roaming-Boundary-Range,CN=Schema,CN=Configuration,DC=moon,DC=ad<07-06-2009 17:15:36> Successfully updated class LDAP://cn=MS-SMS-Roaming-Boundary-Range,CN=Schema,CN=Configuration,DC=moon,DC=ad.<07-06-2009 17:15:36> Successfully extended the Active Directory schema. <07-06-2009 17:15:36> Please refer to the SMS documentation for instructions on the manual <07-06-2009 17:15:36> configuration of access rights in active directory which may still <07-06-2009 17:15:36> need to be performed. (Although the AD schema has now be extended, <07-06-2009 17:15:36> AD must be configured to allow each SMS Site security rights to <07-06-2009 17:15:36> publish in each of their domains.)ConfigMgrPrereq.log:<07-06-2009 18:25:05> ********************************************<07-06-2009 18:25:05> ******* Start Prerequisite checking. *******<07-06-2009 18:25:05> ********************************************<07-06-2009 18:25:05> CPrereqManager: - Since Registry values empty, this is for fresh installation.<07-06-2009 18:25:25> Executing prereq functions...<07-06-2009 18:25:25> <<<Server Name: XXX_SCCM>>><07-06-2009 18:25:25> <<<RuleCategory: Access Permissions>>><07-06-2009 18:25:25> <<<CategoryDesc: Checking access permissions...>>><07-06-2009 18:25:25> Rule Name: Administrative rights on site system<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> <<<Server Name: XXX_SCCM>>><07-06-2009 18:25:25> <<<RuleCategory: System Requirements>>><07-06-2009 18:25:25> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>><07-06-2009 18:25:25> Rule Name: Unsupported site server operating system version for setup<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: Domain membership<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: Schema extensions<07-06-2009 18:25:25> Result: Warning<07-06-2009 18:25:25> Configuration Manager Active Directory schema extensions are not required, for site server installation, but are recommended to fully support the use of all Configuration Manager features.<07-06-2009 18:25:25> Rule Name: Software updates KB911897<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: Software updates KB912818<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: Software updates KB913538<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: Software updates KB914389<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: Software updates KB925903<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: Software updates KB932303<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: FAT Drive on Site Server<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: Short File Name (8.3) Support (Site system)<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> <<<Server Name: XXX_SCCM>>><07-06-2009 18:25:25> <<<RuleCategory: Dependent Components>>><07-06-2009 18:25:25> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>><07-06-2009 18:25:25> Rule Name: Microsoft Management Console (MMC) version<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: Minimum .NET Framework version<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: Microsoft XML Core Services 6.0 (MSXML60)<07-06-2009 18:25:25> Result: Passed<07-06-2009 18:25:25> Rule Name: WSUS SDK on site server<07-06-2009 18:25:26> Result: Warning<07-06-2009 18:25:26> Configuration Manager software update points require Windows Server Update Services (WSUS) version 3.0 or later. If using a remote software update point, the WSUS administration console must be installed on the site server. For more information on WSUS installation see http://go.microsoft.com/fwlink/?LinkID=79477.<07-06-2009 18:25:26> <<<Server Name: XXX_SCCM>>><07-06-2009 18:25:26> <<<RuleCategory: Access Permissions>>><07-06-2009 18:25:26> <<<CategoryDesc: Checking access permissions...>>><07-06-2009 18:25:26> Rule Name: SQL Server sysadmin rights<07-06-2009 18:25:26> Result: Passed<07-06-2009 18:25:26> Rule Name: Site server computer account administrative rights<07-06-2009 18:25:26> Result: Passed<07-06-2009 18:25:26> Rule Name: SQL Server security mode<07-06-2009 18:25:26> Result: Passed<07-06-2009 18:25:26> Rule Name: Administrative share (Site system)<07-06-2009 18:25:26> Result: Passed<07-06-2009 18:25:26> <<<Server Name: XXX_SCCM>>><07-06-2009 18:25:26> <<<RuleCategory: System Requirements>>><07-06-2009 18:25:26> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>><07-06-2009 18:25:26> Rule Name: Domain membership<07-06-2009 18:25:26> Result: Passed<07-06-2009 18:25:26> Rule Name: Short File Name (8.3) Support (Site system)<07-06-2009 18:25:26> Result: Passed<07-06-2009 18:25:26> <<<Server Name: XXX_SCCM>>><07-06-2009 18:25:26> <<<RuleCategory: Dependent Components>>><07-06-2009 18:25:26> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>><07-06-2009 18:25:26> Rule Name: SQL Server version<07-06-2009 18:25:26> Result: Passed<07-06-2009 18:25:26> ***************************************************<07-06-2009 18:25:26> ******* Prerequisite checking is completed. *******<07-06-2009 18:25:26> ***************************************************<07-06-2009 18:25:26> Updating Prerequisite checking result<07-06-2009 18:25:26> Connecting to XXX_SCCM registry<07-06-2009 18:25:26> Setting registry values
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2009 1:38pm

Any chance that you were logged on using a local (IOW non-domain) account when running the prereq checker?
July 6th, 2009 2:14pm

<07-06-2009 18:25:25> Rule Name: Schema extensions<07-06-2009 18:25:25> Result: Warning<07-06-2009 18:25:25> Configuration Manager Active Directory schema extensions are not required, for site server installation, but are recommended to fully support the use of all Configuration Manager features. Hi,This warning is more an information message. You should be able to run the setup is that correct or is the install button grayed out? Please mark posts as Answered if appropriate.
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2009 2:16pm

Yes. I'm able to run the setup even the warning is there. But I would like to run the setupafter everything is ready (no warning). What I concern is if I cannot fix the problem right now, I wondered that I couldn't be solved after the installation as well. So is that warning exists even I was successed to extendthe schema from the DC? Thank you!
July 7th, 2009 4:23am

Hi all, I found that the SCCM 2007 server is looking for the schema of one of the DC (not the schema master DC) which is not replicated. May I know how to replicate manually or change the point of the DC which the SCCM 2007 server is looking for? Thank you!
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2009 5:49am

I am not aware that you can change that from a ConfigMgr point of view. So I would make sure that AD replication is working without issues.
July 7th, 2009 9:45am

Maybe use replmon to see if AD replication is happy?http://technet.microsoft.com/en-us/library/cc772954(WS.10).aspx
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2009 1:24am

Maybe use replmon to see if AD replication is happy?http://technet.microsoft.com/en-us/library/cc772954(WS.10).aspx
July 11th, 2009 1:24am

Maybe use replmon to see if AD replication is happy?http://technet.microsoft.com/en-us/library/cc772954(WS.10).aspx
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2009 1:24am

I faced the same problem even after running the SMSSETUP\BIN\I386\extadch.exe to update the schema for SCCM though I was running it on a test environment with only single DC having all FSMO roles. This utility should point to your schema master automatically even if its been pointing to a non schema master. I resolved the issue by running the utility again. Don't forget to create a "Systems Mangement" container using ADSIEDIT.
February 18th, 2011 7:52pm

I ran SMSSETUP\BIN\I386\extadch.exe as well and the my schema was extended and this warning went away.
Free Windows Admin Tool Kit Click here and download it now
April 15th, 2011 2:02pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics