I've got a little problem with the install of SCCM. I don't know if it's a problem because it keeps warning me of those 2 things.
This is a printscreen of what I get



I did the schema extension with 'extadsch.exe' in \SMSSetup\bin\i386\ on the domain controller. This is the log to prove:

<05-15-2008 14:10:19> Modifying Active Directory Schema - with SMS extensions.
<05-15-2008 14:10:19> DS Root:CN=Schema,CN=Configuration,DC=SCCMDOM,DC=LOCAL
<05-15-2008 14:10:19> Defined attribute cn=MS-SMS-Site-Code.
<05-15-2008 14:10:20> Defined attribute cn=mS-SMS-Assignment-Site-Code.
<05-15-2008 14:10:20> Defined attribute cn=MS-SMS-Site-Boundaries.
<05-15-2008 14:10:20> Defined attribute cn=MS-SMS-Roaming-Boundaries.
<05-15-2008 14:10:20> Defined attribute cn=MS-SMS-Default-MP.
<05-15-2008 14:10:21> Defined attribute cn=mS-SMS-Device-Management-Point.
<05-15-2008 14:10:21> Defined attribute cn=MS-SMS-MP-Name.
<05-15-2008 14:10:21> Defined attribute cn=MS-SMS-MP-Address.
<05-15-2008 14:10:21> Defined attribute cn=mS-SMS-Health-State.
<05-15-2008 14:10:21> Defined attribute cn=mS-SMS-Source-Forest.
<05-15-2008 14:10:22> Defined attribute cn=MS-SMS-Ranged-IP-Low.
<05-15-2008 14:10:22> Defined attribute cn=MS-SMS-Ranged-IP-High.
<05-15-2008 14:10:24> Defined attribute cn=mS-SMS-Version.
<05-15-2008 14:10:24> Defined attribute cn=mS-SMS-Capabilities.
<05-15-2008 14:10:25> Defined class cn=MS-SMS-Management-Point.
<05-15-2008 14:10:25> Defined class cn=MS-SMS-Server-Locator-Point.
<05-15-2008 14:10:25> Defined class cn=MS-SMS-Site.
<05-15-2008 14:10:26> Defined class cn=MS-SMS-Roaming-Boundary-Range.
<05-15-2008 14:10:26> Successfully extended the Active Directory schema.

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

The second warning it tells me that I have to install WSUS or at least the console.

These are my testmachines:

Server 1 - DC + DNS
Server 2 - SCCM site server
Server 3 - SQL 2005 with SP2

Client 1 -WinXP

Server 4 - fresh WSUS 3.0 in pre-production with some test clients on it. I don't know if I'm gonna install a new WSUS 3.0 on my SCCM or just install the console.

What are you thoughts and solutions? 

 Make sure your SCCM server can talk to your Domain controller (same IP subnet) and also ensure that the DNS server entries are correct on the SCCM server. As for the WSUS, you just need to install the console on the SCCM server if you have another server handling that role.

Also, make sure you grant full rights to all child objects in the System folder of AD for your SMS site.  Otherwise, it won't be able to publish it's AD information.

 Hi,

My schema problem is resolved. Now I'm getting a SQL problem that it has not the correct right or something. Both machines can ping each other.

 You should install SQL and SCCM on the same server....Makes it easier.....

 No thank you. Working on a remote SQL is much more secure for me and easier to troubleshoot afterwards. In the future we'll set up a clustered sql.

 All my problems are solved for the post-install of SCCM and even with the install of SP1 for SCCM (like MMC problems and stuff) with a little digging and googl'ing 

When you've got a 50 box infrastructure with 80,000 clients...well, there are definately some situations where you don't want SQL and SCCM on the same box.

 What version of SQL are you using? If it is 2005, ensure that you have the surface configuration set up to allow remote connections via named pipes (remote connections are disabled by default). Also ensure that the sccm service account has permissions to the database instance that you should have created on the remote sql server.

 Thanks but I've already found the problem

 It was the sccm comp name that wasn't admin of the sql instance

Hi Kingkawn,

Well that you had found the remedy for the problem. If possible then please post the solution in brief.Thanks

 Well the solution is simple

 For the schema problem, give the correct rights to the container in AD. 

For the WSUS SDK problem, juste install WSUS 3.0 with SP1 on the site server or just the console if you have a remote WSUS (like me) and give it also an update of the SP1.

That's all ;-)