So a new version of SMS is dawning on us…and one that Im very excited about aside from the new name! It integrates very nicely with NAP which Ive blogged about before and Im keen to see the level of integration so Im having a play with it. In fact Phil Duff and I are presenting on the NAP and SCCM 2007 integration at TechEd Australia!
As I started the install a few Microsofties warned me of a few things which Ill share with you.
What you need to download – and I’m making the assumption you already have a Windows Server 2003 box built and joined to your domain.
1. SCCM 2007 RC1
2. SQL 2005
3. SQL 2005 SP1
4. Windows Server 2003 Support Tools (for SetSPN)
Unfortunately all the same stuff that you had to do before in SMS 2003 also applies in SCCM 2007. I blogged about that 3 years ago now albeit with a few changes. SCCM now has a prerequisite tool to run before you do the installer but its still missing stuff in RC1 that I hope will get fixed in the released version.
There’s a couple of things you must do first – and you have to do it first!! Dont install and then try and get it working – as you will get problems…
1. Extend Active Directory’s schema. You do that via the extadsch.exe tool that is in the \smssetup\bin\i386 directory. Of course you need schema admins permissions.
2. Make sure you install BITS and enable WebDAV in IIS 6.0 (which of course needs to be installed first)
3. Get a PKI running if you want to run SCCM in native mode (optional – otherwise you can only run in mixed mode)
4. The Management Point will be a problem if you don’t do this one…and I have to thank Andrew McMurray for this… Go into the .Net Framework directory under the Windows Directory (c:\windows\microsoft.net\framework\v2.0.50727\Temporary ASP.NET files). Right click the temporary asp.net directory and give Network Service “Full Control” to the directory.
5. In Active Directory Users and Computers, enabled the Advanced Options. Find the “System” Container and give the computer object you’ve installed SCCM on, “Full Control” to that container and all child objects. That should allow it to create the System Management container and add its necessary bits.
6. Set the Service Principal Name (SPN) for the SQL Server. See my previous blog post for info on that one.
Now start the install. It has a prerequisite checker that checks some of the above but not all of it. You should be able to get it running from here. Sometimes theres warnings under the Site logs but there should be no glaring errors. It should work as expected now.
Let me know if I’ve missed anything