Here are some Proof of Concept guidelines I put together that I thought you might find helpful. While this document provides an overview of installing Configuration Manager in a Proof of Concept (POC) environment, it should under no circumstances be considered a replacement for reviewing SCCM product documentation in detail prior to production deployment.
Note: SCCM can be downloaded from the Microsoft Volume Licensing Site MVLS website on or shortly after 11/1/07 (SQL 2005, which SCCM requires, can also be downloaded from the MVLS website). Customers can download the 120-day evaluation version (which is RTM code, link is below) to begin their testing and once they get their MVLS product key, they will be able to apply the product key using a simple upgrade process (no re-installation will be required). It should be noted that the 120-day evaluation version does NOT support an in-place upgrade from SMS 2003 SP2/SP3. SCCM is also available for download for MSDN subscribers, but this version cannot be used in production (which is the case for all products downloaded from MSDN).
Note: Unless the environment has PKI fully deployed, plan on deploying SCCM in Mixed Mode (PKI can be implemented later then SCCM can be upgraded to Native Mode when ready). This will greatly simplify the initial deployment of SCCM if PKI is not already deployed and in use.
Note: Some steps include hyperlinks which you can click on to get additional online instructions for that step
1. Review SCCM Supported Configurations
2. Review SCCM Release Notes (located in the root SCCM installation media folder, some additional hotfixes may be required as noted in the release notes)
3. Review SCCM Capacity Planning Details
4. Install Windows Server 2003
5. Install Windows Server 2003 SP2
6. Install Windows Deployment Services (PXE support included in Windows Server 2003 SP2) from Add/Remove Programs - Windows Setup
7. Review SQL Server Preparation for Setup
8. Install SQL 2005 Standard or Enterprise Edition
9. Install SQL 2005 SP1
10. Install WSUS 3.0 (default installation, select custom website, and do not configure after installation)
11. Install SQL 2005 SP2 (SP2 causes issues with WSUS 3.0 installation in some cases, so install SP2 after WSUS 3.0)
12. Extend Active Directory and Configure ‘System Management’ container permissions
13. Review SCCM Installation Flow Chart
14. Run SCCM Prerequisite Checker from the SCCM installation media (run spalsh.hta, select the checker, and install/configure any identified issues or hotfixes)
15. Install SCCM (run spalsh.hta, custom installation recommended)
16. SCCM Post Installations Tasks
17. Configure SCCM Software Updates
18. Configure WDS/PXE Support
Note: Click [HERE] for SMS 2003 upgrade information
Note: Click [HERE] for the TechNet Virtual Lab that provides additional SMS 2003 upgrade assistance
Note: Click [HERE] for help with deciding to upgrade or perform a new installation of SCCM
Note: Click [HERE] for a flow chart for a new SCCM installation side-by-side with an existing SMS 2003 installation
Here are some Proof of Concept guidelines I put together that I thought you might find helpful. While
Could you please explain your statement - SP2 causes issues with WSUS 3.0 installation in some cases, so install SP2 after WSUS 3.0 - what issues may you see and is this co]vered in a KB article ?
Hello, my name is Ross and I'm one of the technical writers for the Office Resource Kit. I'm posting
Thank-you everyone for your feedback. I'm now posting the most recent draft copy of this article. The