System configuration manager 2007 pdf

Troubleshooting Configuration Manger. Optimizing Service Manager. Optimizing Service Manager Book Description — This book provides you with a framework for planning and delivering a successful Service Manager project. Network Virtualization and Cloud Computing. Network Virtualization and Cloud Computing Book Description — This book provides you with a framework for planning and delivering a successful Service Manager project. Designing Orchestrator Runbooks. Designing Orchestrator Runbooks Book Description — The objective of this book is to provide a framework for runbook design and IT process automation to help you get the most out of System Center Orchestrator With more than 10 years of content writing experience behind him, it's one of his favorite activities.

His goal is to write comprehensive posts and guides, always aiming to help people with essential information. Thank you very much for these books, they really help! Hi , Do we have update a new book?

Thank you. I will update the post once i find the new books. Thanks really because you are concerning about others future. Thanks in advance. Thank you so much. I mistake? An Active Directory message box appears listing steps that may be required to complete the creation of the new site. The list of sites appears in the details pane. Notice the new site is listed. The New Object — Subnet dialog box appears. In the Address box, type your range Microsoft System Center 40 9. In the Mask box, type your subnet The list of subnets appears in the details pane.

Notice the new subnet and its associated site. The list of servers for this site appears in the details pane. Notice that there are no servers in this new site. This is your domain controller. You will move this to your new site as its server. On the Action menu, click Move. The Move Server dialog box appears displaying all sites available.

The list of servers for the default site appears in the details pane. Notice that there are no servers in the default site. The list of servers for the new site appears in the details pane. Notice that your PDC has been moved to the new site.

Close Active Directory Sites and Services. The installation will implement a mixed mode security environment. Note Complete this exercise on the virtual computer running as a Windows Server SP2 member only. Click Install a Configuration Manager site server, and then click Next. Verify that Custom settings is selected, and then click Next.

The Microsoft System Center Configuration Manager Site Type dialog box appears displaying options for the type of site to install. Verify that Primary site is selected, and then click Next. Notice that involvement in the program is configured to no participation. As we are in a virtual environment, click Next to decline participation at this time. Microsoft System Center 42 9. In the Key box, if not using the evaluation version of Configuration Manager, type your product key, and then click Next.

Click Next to enable and configure the selected agents ensuring that Network Access Protection is not enabled. The Microsoft System Center Configuration Manager Management point dialog box appears prompting for the computer to use to install the management point on.

Since SCCM requires a management point, setup will install one by default. The Microsoft System Center Configuration Manager Updated Prerequisite Components dialog box appears prompting for the location of the required client components.

Microsoft System Center 43 The Configuration Manager Installation Prerequisite Check runs to validate that the computers targeted for SCCM installation meet the requirements for installation. There is a warning that no WSUS installation was found. This is required to be able to deploy software updates, but it is not required for the deployment lab, so you can continue. Microsoft System Center 44 In the following procedure, you will use Configuration Manager status messages generated by the site server installation to verify that the site server installation was successful.

You can use this same procedure to view status messages generated by any Configuration Manager processes. The list of Configuration Manager site system roles appears in the results pane with the current status of each site system. Verify that each site system has a status of OK.

In the tree pane, click Component Status. The list of SCCM components and their status appears in the results pane. Click All. Notice the message with the ID of It mentions that the site server was configured to receive Configuration Manager server components. Click the message, and then on the View menu, click Detail. The Status Message Details dialog box appears. Notice the header information for the message, as well as the text under Description.

On the File menu, click Exit. The list of SCCM components appear in the results pane. You may notice the message with a message ID of This message indicates that SCCM retains the most recent copies of the site control file. At this point, SCCM has just been installed, however there will have already been some site control file modifications processed. Notice the message with an ID of From here, you might notice many sets of site control file images being modified.

You might see messages with IDs of , , , , and in each set of site control file modification requests. You will view these messages in later sections of this review. Microsoft System Center 45 You might notice the messages with message IDs of These messages indicate that Hierarchy Manager has successfully processed a site control file modification and updated the site database.

You might notice the message with a message ID of This message indicates one server was discovered and discovery data was written for it. This occurred as a result of installing SCCM site components on the site server computer. In the following procedure, you will add the Active Directory site to the Configuration Manager Boundaries. The list of boundaries for the local site appears in the results pane.

Notice that there no default boundaries added to the site. In the Actions pane, click New Boundary. The New Site Boundary dialog box appears allowing the creation of a new boundary. In the Type box, click Active Directory site, and then click Browse. The Browse Active Directory sites dialog box appears displaying the available Active Directory sites. The New Site Boundary dialog box appears displaying the information specified for the new boundary.

The list of discovery methods for the local site appears in the results pane. Notice that there are four discovery methods related to Active Directory. The New Active Directory Container dialog box appears allowing you to specify the use of a local domain, local forest, or custom query for the discovery. Verify that Local domain is selected, and then click OK. The Select New Container dialog box appears allowing you to specify the container to use for discovery.

Notice the distinguished name for the container to search. Also notice that a recursive search will be performed on that container and that groups are excluded. Click the Polling Schedule tab. Notice that by default, this polling will occur daily. Click Run discovery as soon as possible and then click OK.

Note You will need to wait for a moment for the discovery process to complete. The list of collections appears in the results pane. In the tree pane, expand Collections, and then click All Systems. Notice that there is one member in the All Systems collection currently, that being the Configuration Manager site server.

In the Actions pane, click Update Collection Membership. An All Systems message box appears prompting to update subcollection membership.

The collection is updated. It takes a moment before the database is updated with the new collection membership information. In the Actions pane, click Refresh. Are there any new members in the All Systems collection?

Are each of the systems assigned to the site? Yes, all are listed as being assigned to the site. Note If the assigned status still remains listed as No, then verify that you have correctly listed SCCMSite as a boundary for the site. Microsoft System Center 48 9. What is the discovered AD site name? In the following procedure, you will create the account necessary to remotely install the Configuration Manager client on your Windows XP Professional client computer.

The Active Directory Users and Computers window appears. Create a new user with the name of ClientInstall, assign it a password of password, ensure that the account is not disabled, and that the password does not require changing at first logon. Add this user as a member of the Domain Admins group. This is the account that will be used to push the Configuration Manager client installation to your Windows XP Professional client.

It must be a local admin on the client computer. Being a member of Domain Admins is not a requirement, but simplifies the configuration in the lab environment. In the following procedure, you will configure the account in the Configuration Manager Console to allow installation of the Configuration Manager client.

The list of client installation methods appears in the results pane. The Client Push Installation Properties dialog box appears. Notice that the installation method is not enabled. It does not need to be enabled for our admin controlled push installation. Click the Accounts tab. The Client Push Installation Properties dialog box displays accounts to be used to push out the Configuration Manager client software.

Notice that there are no accounts listed. Microsoft System Center 49 4. Click New the icon resembles a starburst. The Windows User Account dialog box appears. In the Password and Confirm password boxes, type password and then click OK. Notice that the new account is listed.

In the following procedure, you will use the Configuration Manager Console to install a fallback status point. This is a new site system to Configuration Manager , and is recommended to get client deployment status reporting.

The list of configurable site settings appears in the results pane. The list of site system roles for the site server appears in the results pane.

Notice that there are six site system roles assigned to the computer. In the Actions pane, click New Roles. The New Site Role Wizard System Role Selection dialog box appears displaying the list of site system roles that can be assigned to this computer. Under Available roles, select Fallback status point, and then click Next. The New Site Role Wizard Fallback Status Point dialog box appears allowing you to configure the fallback status point message processing.

Microsoft System Center 50 7. In the Throttle interval in seconds box, type , and then click Next. Note You should not use a value of in a production environment as it could cause performance issues when deploying large numbers of clients in a very short period of time.

We are doing so in the lab to get our state messages processed more quickly to allow for client deployment reports to be generated in a timely manner. The New Site Role Wizard Summary dialog box appears indicating that you have successfully completed the wizard.

Notice that the fallback status point role has been added to the list. In the following procedure, you will configure clients to use the fallback status point during installation of the Configuration Manager client. Note Complete this procedure on the virtual computer running as a Configuration Manager site server only.

Click the Client tab. The Client Push Installation Properties dialog box displays the properties to use when performing a client push. Notice that there are no members of the collection. The collection membership is updated, and the current membership of the All Windows XP Systems collection is displayed. Click Next to accept the default configuration to install the client to assigned resources.

It will take a few minutes before the installation completes. Microsoft System Center 52 In the following procedure, you will verify that the Configuration Manager client has been installed on the Windows XP Professional client. It will take a few moments for the installation of the SCCM client to complete. You can use Task Manager to verify the installation. While ccmsetup. When ccmsetup. The Services window appears.

Close Services. In the following procedure, you will verify that the Windows XP Professional client has reported to the Configuration Manager site that it is installed as a Configuration Manager client. Notice that the Windows XP Professional computer appears. Also notice that the computer is not listed as being an SMS client. Notice that the Windows XP Professional client computer now is listed as being installed as a Configuration Manager client.

Microsoft System Center 53 Exercise 4 Reporting Configuration Manager Client Deployment Status In this exercise, you will install a reporting point for your Configuration Manager site and then run reports to verify the client deployment success in the site.

Note Complete this exercise on the site server computer only. Notice that there are seven site system roles assigned to the computer. Under Available roles, select Reporting point, and then click Next. The New Site Role Wizard Reporting Point dialog box appears allowing you to configure the reporting folder and port to use for the reporting point.

Click Next to use the default values. Notice that the reporting point role has been added to the list. From Administrative Tools, start Services. In the following procedure, you will run a few built in reports to validate that the reporting point is running successfully and that the client was deployed successfully.

Note Microsoft System Center 54 Complete this procedure on the virtual computer running as a Configuration Manager site server only. In the results pane, click Computers assigned but not installed for a particular site, and then in the Actions pane, under Computers assigned but not installed for a particular site, click Run.

The Computers assigned but not installed for a particular site Report Information report appears in the results pane. As this is a prompted report, you must supply the site code of the site you wish to view computer information for. An Internet Explorer window starts and displays the Computers assigned but not installed for a particular site report.

In your evaluation these may be on the same computer. Close the ConfigMgr Report window. The Configuration Manager Console window appears displaying the current report parameters. In the tree pane, click Reports. The Client Deployment Status Details report appears in the results pane. The Client Deployment Success Report appears in the results pane.

Notice that this report displays that status of each client that was installed. You have now successfully deployed Configuration Manager in your AD environment, including site systems required for client deployment and successfully installed a client computer. Estimated time to complete this section: 75 minutes Microsoft System Center 56 Note Complete this procedure from the primary site server computer only.

On the Start menu, click ConfigMgr Console. In the tree pane, click All Systems. Click OK, and then in the Actions pane, click Refresh. Delete any other Obsolete records from the All Systems collection. You have now prepared your images for the lab and may proceed to Exercise 1. Microsoft System Center 57 Exercise 1 Configuring a Branch Distribution Point In this exercise, you will configure a branch distribution point for the site. You will begin by configuring the distribution point on the site server to support BITS downloads, which is required to support a branch distribution point.

If not already running, on the Start menu, click ConfigMgr Console. The list of site system roles configured for the site server computer are displayed in the results pane. Notice that one of the site system roles configured for the site server is as a distribution point. In the results pane, select ConfigMgr distribution point, and then in the Actions pane, click Properties. The ConfigMgr distribution point Properties dialog box appears displaying the current configuration of the distribution point role on the Configuration Manager site server.

Notice that the role is not configured to support BITS. This configures the distribution point to support BITS downloads to Configuration Manager clients, which includes branch distribution points. In the following procedure, you will create a new site system as a branch distribution point. You will configure the Windows XP client to be the branch distribution point.

Note Complete this procedure from the primary site server computer only in the Configuration Manager Console. The list of site systems configured for the site displayed in the results pane. Notice that there is currently only one site system in the site, that being the site server computer. In the Actions pane, click New, and then click Server. Microsoft System Center 58 3. Click Enable this site system as a protected site system, and then click Select Boundaries.

The Boundaries dialog box appears displaying the current configuration of protected boundaries for this site system. Notice that there are currently no protected boundaries configured for this site system.

Notice also that the boundaries are only applicable to the distribution point and state migration point site system roles. The New Boundaries dialog box appears displaying the boundaries available for protecting the site system. Notice that the Active Directory site boundary is listed as an available boundary. Notice that the site system is now configured to be protected for only the one Active Directory site that is added as a boundary in the site. The New Site System Server Wizard System Role Selection dialog box appears displaying the list of site system roles that can be assigned to this computer.

Under Available roles, select Distribution point, and then click Next. Notice that by default, the site system would be a standard distribution point, which is not supported on a Windows XP system. Click Enable as a branch distribution point, and then click Next.

The New Site System Server Wizard Summary dialog box appears indicating that you have successfully completed the wizard. The New Site System Server Wizard Wizard Completed dialog box appears indicating that you have now configured the branch distribution point. The Configuration Manager Console window appears displaying the site systems in the site.

Microsoft System Center 59 The list of site system roles configured for the site system are displayed in the results pane. In the following procedure, you will configure the branch distribution point to not perform BITS throttling. BITS throttling is configured by default and could affect the download of content to the branch distribution point. The list of available client agents appears in the results pane.

The Computer Client Agent Properties dialog box appears displaying general properties. Click the BITS tab. Notice that the default configuration is to perform BITS download throttling from 9 am to 5 pm daily. This could cause delays in the download of the content to the branch distribution point.

Click Not configured, and then click OK. Exercise 2 Distributing Software to the Configuration Manager Client In this exercise, you will distribute software to the Configuration Manager client. Initially this will fail as the branch distribution point will not be configured for the package.

The list of members of the All Systems collection appears in the results pane. Notice that both computers are installed as clients in the site. In the Actions pane, click Distribute, and then click Software.

The Distribute Software to Collection Wizard dialog box appears. The Distribute Software to Collection Wizard Package dialog box appears providing Microsoft System Center 60 options for package creation or distribution. Select Create a new package from a definition, and then click Next. The Distribute Software to Collection Wizard Package Definition dialog box appears allowing you to select the package definition file to use.

Notice the default package definitions built into Configuration Manager. If you do not already have the SMS Toolkit, this can be obtained from here. Download and expand this. The Open dialog box appears.

Notice that SMS Toolkit 2 is displayed. The Distribute Software to Collection Wizard Source Files dialog box appears prompting for source file handling instructions. The Distribute Software to Collection Wizard Source Directory dialog box appears allowing the designation of the source file directory.

Microsoft System Center 61 The Distribute Software to Collection Wizard Distribution Points dialog box appears allowing the designation of distribution points to store the package files. The Distribute Software to Collection Wizard Select Program dialog box appears allowing the selection of the program to advertise.

Under Programs, click Per-system unattended, and then click Next. The Distribute Software to Collection Wizard Advertisement Name dialog box appears prompting for a name and comment for the advertisement.

Click Next to accept the default name. The Distribute Software to Collection Wizard Advertisement Subcollection dialog box appears prompting for advertising to subcollections. Click Next to accept the default option of advertising to subcollections as well even though we do not have any subcollections. The Distribute Software to Collection Wizard Advertisement Schedule dialog box appears prompting for a start and expiration time for the advertisement.

After Advertise the program after, verify that the current date and time is displayed. Verify No, this advertisement never expires is selected, and then click Next. Verify that No, do not assign the program is selected, and then click Next.

The Distribute Software to Collection Wizard Summary dialog box appears prompting to complete the wizard. The Distribute Software to Collection Wizard Wizard Completed dialog box appears indicating the process was successful. The list of members of the All Systems collection in the results pane. Microsoft System Center 62 In the following procedure, you will verify the configuration of the package, program, and advertisement that were created by the Distribute Software to Collection Wizard.

You will also configure the advertisement to only allow content access from the protected distribution point. In the tree pane, expand Computer Management, expand Software Distribution, and then expand Packages. The new package appears in the tree pane. Note You may need to refresh the display to see the new package.

In the tree pane, click Programs. The configured programs for the package appear in the results pane. Notice the Persystem unattended program which you advertised to the client using the Distribute Software wizard. In the tree pane, click Distribution Points. The distribution points for the package appear in the results pane. Notice only the local site server is listed. In the tree pane, click Advertisements. Note You may need to refresh the display to see the new advertisement.

The advertisement for the SMS Toolkit 2 program appears in the results pane. Notice the Available After time is the date and time the advertisement was created. The SMS Toolkit 2 Properties dialog box appears displaying general properties for the advertisement.

Click the Distribution Points tab. The SMS Toolkit 2 Properties dialog box appears displaying properties for distribution point access. Notice that the default values are to download from fast network boundaries, and not run from slow network boundaries. Also notice that the default configuration is to not require download from a protected distribution point. Click to clear Allow clients to fallback to unprotected distribution points when the content is not available on the protected distribution point, and then click OK.

Microsoft System Center 63 In the following procedure, you will initiate the searching for advertised programs on your Configuration Manager client computer. For this procedure, you will use the client running on the site server computer.

In Control Panel, start Configuration Manager. The Configuration Manager Properties dialog box displays the available actions for the Configuration Manager client.

The Configuration Manager client will request new policies, which will include the policy related to the advertised program. It will take a couple of minutes, and then the New Program Available icon appears on the system tray. Double-click the New Program Available icon. The Run Advertised Programs window appears displaying new programs that are available to be installed.

Notice that the SMS Toolkit 2 program is available. In the Run Advertised Programs window, refresh the display use F5. The Run Advertised Programs window appears. Microsoft System Center 64 Notepad appears displaying the contents of the Content Access Service log file. Search for matching. Notice that the current line indicates that there was no matching distribution point found for the content location request.

We know that the content was distributed to the standard distribution point on the site server. However, as the branch distribution point was protected for the Active Directory site that the client is a member of, the client can only access the content from the branch distribution point.

And the branch distribution point does not contain the requested content, and so there is no matching distribution point available for this client. In the following procedure, you will view the advertisement status of the advertised program using the Software Distribution home page to verify the program installation or failure on the clients.

Note Complete this procedure from the primary site server computer only in the Configuration Management Console. The Software Distribution home page appears in the results pane. Notice that there are no results to display. Status has to be summarized before it appears in the home page. It will take a moment for the summarization process to complete. The Software Distribution home page appears in the results pane displaying the current advertisements.

Notice that the SMS Toolkit 2 advertisement is displayed. Notice also that both the statistics and graph indicate that one client has not started the advertisement and another client failed. Microsoft System Center 65 In the following procedure, you will verify the current distribution points for the package do not include the branch distribution point, and then add the branch distribution point. Since the advertisement is configured to only use protected distribution points, and the client is within the boundaries of the protected distribution point, the client is unable to run the program as the protected distribution point branch distribution point does not contain the content requested.

The New Distribution Points Wizard window appears. The New Distribution Points Wizard Copy Package dialog box appears displaying the distribution points available for this package. The New Distribution Points Wizard Wizard Completed dialog box appears indicating that the wizard was completed successfully.

Notice that now both distribution points are listed for this package. In the following procedure, you will force the distribution of the content the branch distribution point. You do not need to complete this procedure in a production environment, as the content will be distributed to the branch distribution point automatically.

You are going to complete this procedure simply to speed up the process for the lab. Microsoft System Center 66 2. The Configuration Manager client will request new policies, which will include the policy related to the branch distribution point package location. It will take a couple of minutes, and then the content will begin being downloaded to the branch distribution point. In the following procedure, you will verify that the content the branch distribution point has requested has been distributed locally.

Start Windows Explorer and then view the contents of drive C. The contents of the C drive appears. This is the folder that the branch distribution point uses to store locally distributed package content. The contents of the package folder appear in the details pane. Notice that the distributed source files are now available on the branch distribution point. Microsoft System Center 67 In the following procedure, you will run the advertised program now that the content is available on the branch distribution point.

A Program Download Required message box appears. By default, in Configuration Manager, advertised programs will be downloaded from the distribution point prior to installation. The program is installed. Note It will take a moment to install the program. Wait a moment before proceeding. Click Close, and then on the Start menu, point to All Programs. The list of program is displayed. Notice that a new program group item for the SMS Toolkit 2 appears.

Point to SMS Toolkit 2. The list of programs in the SMS Toolkit 2 program group appears. These were installed through the SMS Toolkit 2 advertisement. Microsoft System Center 68 8. Search for download location found. Notice that the current line indicates that there was one matching distribution point found for the content location request. To see what type of distribution point was used, you need to look in the LocationServices.

Close CAS. It also provides step-by-step guidance showing how to install and configure the required components, and how to use the most common features. Indeed great guides! Thank you very much! You can post now and register later.

If you have an account, sign in now to post with your account. Paste as plain text instead. Only 75 emoji are allowed. Display as a link instead. Clear editor. Upload or insert images from URL. How do I?