Windows 7 : Installing Configuration Manager 2007 (part 2) - Install the Site Server

11/23/2012 2:54:54 AM

2. Install the Site Server

You can install ConfigMgr once the prerequisites are installed and configured. These steps will install Configuration Manager 2007 with Service Pack 2, update the site server to Configuration Manager 2007 R2, and add additional components that assist OSD.

2.1. Install Configuration Manager 2007 with Service Pack 2

Take the following steps to install Configuration Manager 2007 with Service Pack 2:

  1. Insert your Configuration Manager with Service Pack 2 media into the site server. If Autorun is disabled, you can run the Splash file on the root of the media. Click the Configuration Manager 2007 SP2 link under Install to launch the setup wizard.

  2. Choose the default option of Install A Configuration Manager Site Server.

  3. Choose the Custom setting when you get to the Installation Settings screen. The site type will be Primary. You should have a D: drive so you can install ConfigMgr onto it—for example, you can choose D:\ConfigMgr.

  4. Every site in ConfigMgr has a three-letter code and a site name. Think these through without rushing the installation before you deploy a production system. For this exercise, you'll be using DPL as the site code and Deploy as the site name in the Site Settings screen. Enter the code and site name you've chosen.

  5. For a production system, this would be a pure ConfigMgr 2007 system, so you will choose Configuration Manager Native Mode as the site mode. For a site with legacy SMS 2003 clients, you would choose the Mixed mode. Note that a Native mode site requires a PKI infrastructure. That requires a bit of work and a lot of explanation. To speed things along, we're going to take a shortcut for this exercise and choose to have a Mixed mode site. This won't affect OSD exercises.

  6. A ConfigMgr client can have a number of agents enabled. For this exercise, accept the default settings for the SQL Server Computer settings as well as the installation location in the SMS Provider Settings screen.

  7. You should accept the default setting for creating a management point on the Port Settings screen.

  8. At the Update Prerequisite Component Path screen, create a folder for the installer. The wizard will then download updates to the installation packages so that the newest files can be installed on your site server.

  9. After a summary screen, a prerequisite check is run. If you've followed all the steps correctly, you should have a single green check mark giving you the good news. Click Begin Install to install your site server.

2.2. Upgrade to Configuration Manager 2007 R2

If you have the licensing, you can insert the media for ConfigMgr 2007 R2 and perform an upgrade of your site server. The installer is quite simple and will install the new components that are included in the R2 release. Three OSD features were added with the R2 release:

Unknown Computer Support

Prior to R2, you had to either already manage a computer or provision a computer account in advance for a new machine. R2 allows unknown computers to connect to the PXE service point.

Multicast Deployment

ConfigMgr 2007 R2 is capable of taking advantage of the multicast feature of WDS on Windows Server 2008 or later.

Alternative Command-Line Credentials

Command-line tasks that are used in OSD can use credentials other than Local System. This will be useful when accessing secure network resources.

2.3. Install MDT 2010

Configuration Manager is capable of leveraging MDT 2010 to extend its ability to create and manage task sequences for OSD. To take advantage of this ability, you should install MDT 2010 after you have installed Configuration Manager with Service Pack 2.

  1. MDT 2010 requires the free-to-download Word Viewer. You can get that from and install it on your ConfigMgr site server. Then install MDT 2010.

  2. When MDT is installed, launch the MDT Deployment Workbench and create a new deployment share:

    • Deployment share path: D:\DeploymentShare

    • Share name: DeploymentShare$

    • Deployment share name: DeploymentShare

  3. Leave the remaining screens in the New Deployment Share Wizard with the default settings and close the Deployment Workbench.

  4. The last step is to integrate MDT 2010 with your ConfigMgr site server. You can do this using the Configure ConfigMgr Integration utility, which is in the Microsoft Deployment Toolkit program group in the Start menu. The default settings for Site Server Name and Site Code should be okay, so leave them in place, as shown in Figure 6.

Figure 6. Integrate MDT 2010 with Configuration Manager

You've now installed the components that you'll be using to create operating system packages and deploy them. We're not quite done yet. Some other configurations must be done in ConfigMgr to prepare for our OSD exercises. We'll have a look at that next.

Your last step, as always with any new server, should be to run Windows Update to ensure all security updates are installed and to install any other patches that you require.

Most View
Belkin AC1200 DB Wi-Fi ADSL Router
Ditch Your Laptop For Your Phone (Part 1)
Installing and Configuring SharePoint 2013 : Creating the Farm (part 1)
Using Services for UNIX to Integrate UNIX Systems with an Active Directory/Exchange Server 2007 Environment
Apple - Celebrating 7 Years Of Success
ASP.NET 4 : Error Handling, Logging, and Tracing - Handling Exceptions
Security Pros Get Caught Out By QR Codes
Samsung ATIV Tab Review - A Wonderful Windows RT Tablet (Part 2)
How To Extend Life For Mac (Part 1)
Edifier E10 Exclaim - Exclamation Mark
Top 10
Sharepoint 2013 : Developing Applications Using Office Services - What’s New in Access Services
Sharepoint 2013 : Developing Applications Using Office Services - The New Machine Translation Services
Sharepoint 2013 : Developing Applications Using Office Services - Word Automation Services and the New PowerPoint Automation Services
Sharepoint 2013 : Developing Applications Using Office Services - What’s New in Excel Services
Sharepoint 2013 : Developing Applications Using Office Services - WOPI and the New Office Web Apps Server
Sharepoint 2013 : Building a BCS-enabled Business Solution : Building an Integrated BCS Solution with an App for SharePoint Containing an App for Office
Business Connectivity Services in Apps for SharePoint 2013 : Building an App-level BCS Solution for Office 365 SharePoint Online
Business Connectivity Services in SharePoint 2013 : Adding a Business Data Connectivity Model to Office 365 SharePoint Online
Remote Event Receivers in Sharepoint 2013 : Introducing Remote Event Receivers
Windows Server 2008 and Windows Vista : Common GPO Troubleshooting Tools (part 3) - GPResult, GPOTool