Quick Checklist for a ConfigMgr evaluation on a single box
Although there is a virtual machine ready to use on www.microsoft.com/vhd, many people like to get theirs hands on a product first by installing it.
I don't mean this post to be very detailed in each step, so please consider this more of an unofficial checklist.
So, what do you prepare on a server, before launching the Configuration Manager setup? Here is a list:
- Windows Server 2003 with SP2.SP2 is recommended, although you can use SP1 [If you use SP1, it's recommended to install hotfixes 911897, 912818, 913538, 914389, 925903. And you would also have to install MMC 3.0]
- IIS, ASP.NET, BITS and WebDAV components
- SQL Server 2005, followed by its SP2. Only database services are needed in the SQL Server setup, although having the administration tools might come handy. Reporting Services is not needed at this time (it will be needed for SCCM 2007 R2). Installing SQL Server 2005 will automatically install .NET Framework 2.0.
- Hotfix 932303 is an optional update for the .NET Framework 2.0, although I always install it.
- Ideally, make sure this server has internet access, as setup will need to copy some files. If not, you can get those files on another box, by just running SETUP.EXE /DOWNLOAD <local path>
Before running the setup, you will also need to prepare your Active Directory (this is not mandatory, but the documentation covers why it'd be a shame not to integrate with AD!):
- On a domain controller with schema admins privileges, run EXTADSCH.EXE from the SMSSETUP\BIN\<Platform> folder. A log file is created at the root of the C: drive, so you can check success/failure of the operation. A classic cause of failure is when the domain controller has not been replicating fine lately. You can force this using the Active Directory Sites and Services MMC snap-in and make sure the replication went well.
- You can also create the "System Management" CONTAINER (not Organization Unit, so you need ADSI EDIT here) in the System container for the domain, and grant control for the future SCCM server.
After you have successfully run the SCCM setup, here is what is left to do:
- Add a reporting point in your environment (this is not installed by default during the setup, even in the "express" setup option)
- Configure boundaries
- Enable discovery
- Configure a Client Push Installation account, so you can right-click on any discovered machine and push the client (make sure firewalls are correctly configured on the client side or, in a test environment, disabled)
- Enable Asset Intelligence classes to add to the inventory. This is covered in the documentation: https://technet.microsoft.com/en-us/library/bb694072.aspx (and there will be checkboxes to do this directly in the UI in SP1!)
Then you should be good to go. I'll try to cover the Software Update Management and Operating System Deployments step-by-step prerequisites & configuration in the same way, in future posts.
Happy SCCM'ing!