SCCM Schema Extensions warning

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

SCCM Schema Extensions warning

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> SCCM Schema Extensions warning

Page: [1]

Message

<< Older Topic Newer Topic >>

SCCM Schema Extensions warning - 7/24/2008 9:45:12 AM

glyn808

Posts: 5
Score: 0
Joined: 11/8/2007
Status: offline

Hi I’m currently in the process of installing SCCM 2007 sp1 as a clean build into a dev domain where it will co-exist with our SMS 2003 environment (both sites will have separate boundaries) one of our Schema admins extended the domain on my behalf with the media I supplied. However when I go to install the server, I get an installation warning stating:

“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.”

This would state that the schema hasn’t been expanded but I know that it has been.

Has anybody else come across this error and resolved it?

Post #: 1

RE: SCCM Schema Extensions warning - 7/24/2008 10:09:31 AM

xneilpetersonx

Posts: 157
Score: 1
Joined: 7/18/2006
Status: offline

There would have been a log file (ExtADSch.log) placed at the root of whatever computer the schema extension tool was run on. Have you checked this to verify the extension success?

neilp

(in reply to glyn808)

Post #: 2

RE: SCCM Schema Extensions warning - 7/24/2008 10:48:09 AM

glyn808

Posts: 5
Score: 0
Joined: 11/8/2007
Status: offline

Yes it shows up as a success Please see log :(i have taken out the DS root however i can confirm it was the correct domain)

<05-02-2008 08:58:30> Modifying Active Directory Schema - with SMS extensions.
<05-02-2008 08:58:30> DS Root:
<05-02-2008 08:58:31> Defined attribute cn=MS-SMS-Site-Code.
<05-02-2008 08:58:32> Defined attribute cn=mS-SMS-Assignment-Site-Code.
<05-02-2008 08:58:32> Defined attribute cn=MS-SMS-Site-Boundaries.
<05-02-2008 08:58:33> Defined attribute cn=MS-SMS-Roaming-Boundaries.
<05-02-2008 08:58:33> Defined attribute cn=MS-SMS-Default-MP.
<05-02-2008 08:58:33> Defined attribute cn=mS-SMS-Device-Management-Point.
<05-02-2008 08:58:34> Defined attribute cn=MS-SMS-MP-Name.
<05-02-2008 08:58:35> Defined attribute cn=MS-SMS-MP-Address.
<05-02-2008 08:58:35> Defined attribute cn=mS-SMS-Health-State.
<05-02-2008 08:58:36> Defined attribute cn=mS-SMS-Source-Forest.
<05-02-2008 08:58:36> Defined attribute cn=MS-SMS-Ranged-IP-Low.
<05-02-2008 08:58:36> Defined attribute cn=MS-SMS-Ranged-IP-High.
<05-02-2008 08:58:37> Defined attribute cn=mS-SMS-Version.
<05-02-2008 08:58:37> Defined attribute cn=mS-SMS-Capabilities.
<05-02-2008 08:58:39> Defined class cn=MS-SMS-Management-Point.
<05-02-2008 08:58:39> Defined class cn=MS-SMS-Server-Locator-Point.
<05-02-2008 08:58:40> Defined class cn=MS-SMS-Site.
<05-02-2008 08:58:40> Defined class cn=MS-SMS-Roaming-Boundary-Range.
<05-02-2008 08:58:41> Successfully extended the Active Directory schema.

<05-02-2008 08:58:41> Please refer to the SMS documentation for instructions on the manual
<05-02-2008 08:58:41> configuration of access rights in active directory which may still
<05-02-2008 08:58:41> need to be performed. (Although the AD schema has now be extended,
<05-02-2008 08:58:41> AD must be configured to allow each SMS Site security rights to
<05-02-2008 08:58:41> publish in each of their domains.)

(in reply to xneilpetersonx)

Post #: 3

RE: SCCM Schema Extensions warning - 7/29/2008 6:57:10 AM

glyn808

Posts: 5
Score: 0
Joined: 11/8/2007
Status: offline

Thanks for you input Neil, the issue was that the SCCM server needed to be added and given permission on systems management container within AD this hadn't been done once enabled and given full permissions, everything works fine.

Thanks

Glyn

(in reply to glyn808)

Post #: 4