“Content location request for P0100021:1 failed. (Code 0×80040102)”

Package with ID P0100021 are the VMware Tools, and yes this is one step in my task sequense. This error is simple to resolve, just deploy the specific package to a distribution point…

After a succesvol deployment to the distribution point, the task sequence finisched succesfull!

1.) Create a new Collection. (In my example it is All Obsolete Computerobjects)
2.) Create a new query. (In my example it is Query All Obsolete Computerobjects)
3.)  Edit the query statement. Use the following query:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,
SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,
SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Obsolete = 1
4.) Run the “Update Collection Membership”
5.) View the result

4.00.5135.0000 – SCCM 2007 Beta 1
4.00.5125.0000 – SCCM 2007 Beta 1 Escrow
4.00.5221.0000 – SCCM 2007 Beta 1 Refresh Escrow
4.00.5224.0000 – SCCM 2007 Beta 1 Refresh
4.00.5571.0000 – SCCM 2007 Beta 2 Escrow
4.00.5574.0000 – SCCM 2007 Beta 2 Escrow Update
4.00.5578.0000 – SCCM 2007 Beta 2 with a hotfix
4.00.5578.0002 – SCCM 2007 RC0 Preview
4.00.5790.0000 – SCCM 2007 RC0 Preview
4.00.5815.0000 – SCCM 2007 RC0
4.00.5924.0000 – SCCM 2007 escrow
4.00.5931.0001 – SCCM 2007 RTM                             
4.00.6086.1000 – SCCM 2007 SP1 (prerelease)          
4.00.6221.1000 – SCCM 2007 SP1                              
4.00.6425.2000 – SCCM 2007 SP2 beta                       
4.00.6468.2001 – SCCM 2007 SP2 RC
4.00.6487.2000 – SCCM 2007 SP2 RTM
4.00.6487.2157 – SCCM 2007 SP2 R3

1.) Microsoft Windows 2008 R2 x64
2.) .NET Framework 4.0
3.) Microsoft SQL 2008 Server Service Pack 1
 4.) Database Engine Services
 5.) Reporting Services
 6.) Management Tools Complete
7.) Microsoft SQL 2008 Server Service Pack 1 CU8 CU8 (10.0.2775.0)
8.) Install the schema extension (extadsch.exe)
9.) Install BITS and Remote Differential Compression (RDC)
10.) Install Windows Server Update Services (WSUS) optionally
11.) Install Windows Deployment Services
12.) Give the vNext computerobject “full control” rights within your active directory on the organizational unit “System” (this object and all child objects).
13.) Install the PXE Service Point service role within SCCM vNext. This step is optionally when you’re going to use OSD.

Centralized Power Management
Mobile Device Management
Enhanced Scalability and Performance

Configuration Manager R3 lets IT organizations centrally manage the power settings of Windows 7, Vista and XP computers, helping reduce energy consumption and costs. You can plan and apply a power management policy for high and low PC usage periods, monitor user activity to avoid any productivity interruptions and correct non-compliance. Detailed reports of trends and settings help you make smart power management choices, and also validate Green IT projects with summaries of power, money and CO2 savings.

Configuration Manager R3 includes licenses for the popular System Center Mobile Device Manager, so you can run comprehensive asset inventories, deploy software, manage settings and enforce password policies for Widows phones.

Configuration Manager R3 is more scalable than ever, increasing the number of supported clients to 300,000 per site. R3 is also more efficient in the way it communicates with Active Directory, helping you discover user or machine changes more quickly and allowing custom queries to define user, system or group attributes.

1.) Create a new collection and give it a name
2.) Create a new query and give it a name
3.) Configure the following criteria
     – Criterion Type: Simple value
     - Where: System Resource – Operating System Name and Version
     – Operator: is like
     – Value: Microsoft Windows NT Workstation 6.1
4.) Configure the update schedule
5.) Right-click on your collection and select “Update Collection Membership”
6.) Right-click on your collection and select “Refresh”
7.) Your collection is now ready to use

Now you’re sure that the system drive will not be used by SCCM!

To fix this problem, you’ll need to do the following steps:

1.) On the SQL Server, right-click My Computer and select Manage to open the Computer Management console
2.) Expand the Local Users and Groups node and select Groups
3.) Double-click Administrators in the right-hand pane of the Computer Management console
4.) Click the Add… button to open the Select Users, Computers and Groups dialog box
5.) Click the Object Types… button and ensure Computers is selected in the Object Types dialog box. Click OK to return to the Select Users, Computers and Groups dialog box
6.) If the From this location field in the Select Users, Computers and Groups dialog box does not show the domain that the Configuration Manager site server is in, click the Locations… button and select the correct domain
7.) In the field labelled Enter the object names to select, type the computer name of the Configuration Manager site server. Click the Check Names to confirm that the name has been recognised
8.) Click OK

In this example i’ve added a new user with only permissions to read all the Packages.

1.) Open the System Center Management Console
2.) Navigate to the Site Database, Security Rights, Users, Manage ConfigMgr Users
3.) Add a new user, browse and select the new user
4.) Select “Add another right or modify an existing one”
5.) In this example the user has only the permission to read the packages
6.) Select in the Class box “Package”
7.) Select in the Instance box “(All Instances)”
8.) Finish the wizard

For remote connecting to the SCCM Site Server, you’ve to edit the DCOM security, otherwise you’ll receive an error when you try to open the System Center Management Console.

1.) Go to your SCCM Site Server
2.) From the Start menu, click Run and type Dcomcnfg.exe
3.) In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer. On the Action menu, click Properties
4.) In the My Computer Properties dialog box, on the COM Security tab, in the Launch and Activation Permissions section, click Edit Limits
5.) In the Launch Permissions dialog box, click Add
6.) In the Select User, Computers, or Groups dialog box, in the Enter the object names to select, in this example: markswinkels
7.) In the Permissions for markswinkels, select the check box to allow Remote Activation
8.) Click OK twice, and then close Computer Management

1.) Collection
2.) Package
3.) Program
4.) Distribution Point
5.) Advertisement

Before we are going to deploy Office 2007, we’ve to create a MSP file for customize the Office 2007 installation. You can start the Office Customization Tool using the following command: setup.exe /admin. Save the file in the updates folder on your Office 2007 source directory.

Step 1, creating a collection:
1.) Create a new collection, to specify the computers where Office must be installed.
2.) Navigate to System Center Configuration Manager, Site Database, Computer Management, New Collection
3.) Give your new collection a name, for example “Office 2007 Enterprise”
4.) On the Membership Rules dialog box, click the computer icon, which opens the Create Direct Membership Rule Wizard. Click Next
5.) On the Search for Resources dialog box, click the Resource class drop-down menu and select System Resource. Then, click the Attribute name drop-down menu and select Name. In the Value field enter %, and then click Next
6.) On the Collection Limiting dialog box, click the Browse button, select All Windows Workstation or Professional Systems, and then click Next
7.) Select the computer(s) you want to deploy Office 2007 and click Next

Step 2, creating a package:
1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Package, New Package
2.) On the General dialog box of the New Package Wizard, enter the Name, Version, Manufacturer, and Language. For example, Office, 2007, Microsoft, English (US)
3.) On the Data Source dialog box, select This package contains source files. Click the Set button, and then enter the path for the location of the source files in the Source directory field. For example E:\Software\Office 2007\, which contains a copy of the 2007 Office Enterprise installation CD.
4.) Click OK, and then continue to click Next and accept the default settings on all of the following dialog boxes: Data Access, Distribution Settings, Reporting, and Security. On the Wizard Completed dialog box

Step 3, creating a Program:
1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Packages, Office 2007, Programs, New, Program
2.) Give the new program a Name
3.) On the Command-line box, type in setup.exe (Because the customization file, CustomOffice.MSP, was placed in the \Updates folder, a command line option is not needed to reference its location)
4.) On the Environment dialog box, click the Program can run drop-down box and select Whether or not a user is logged on. This will enable Run with administrative rights for the Run mode. Leave the default for Drive mode to Runs with UNC name, and then click Next
5.) On the Advanced dialog box, select the check box for Suppress program notifications, and then click Next

Step 4, Copy to Distibution points:
1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Packages, Office 2007, Distribution points
2.) Manage Distribution Points
3.) Select “Copy the package to new distribution points”
4.) Select the distribution points
5.) Click finish and wait a copple of minutes
6.) Check the status changing from Install Pending to Installed

Step 5, creating the advertisement
1.) Navigate to System Center Configuration Manager, Site Database, Computer Management, Software Distribution, Advertisements
2.) New Advertisement
3.) Give the advertisement a Name
4.) Select the package, Program and Collection
5.) Click finish and wait a copple of minutes
6.) On the client wait for the next Machine Policy Retrievel & Evaluation Cycle

After the setup is finished, Office 2007 is deployed to your client(s) and is ready to use!

1.) Open your control panel
2.) Configuration Manager
3.) Action tab
4.) Machine Policy Retrieval & Evaluation Cycle
5.) Initiate Action

The next option is to use the following script.
———————————————————————————————
on error resume next

dim oCPAppletMgr ‘Control Applet manager object.
dim oClientAction ‘Individual client action.
dim oClientActions ‘A collection of client actions.

‘Get the Control Panel manager object.
set  oCPAppletMgr=CreateObject("CPApplet.CPAppletMgr")
if err.number <> 0 then
    Wscript.echo "Couldn’t create control panel application manager"
    WScript.Quit
end if

‘Get a collection of actions.
set oClientActions=oCPAppletMgr.GetClientActions
if err.number<>0 then
    wscript.echo "Couldn’t get the client actions"
    set oCPAppletMgr=nothing
    WScript.Quit
end if

‘Display each client action name and perform it.
For Each oClientAction In oClientActions

    if oClientAction.Name = "Request & Evaluate Machine Policy" then
        wscript.echo "Performing action " + oClientAction.Name
        oClientAction.PerformAction
    end if
next

set oClientActions=nothing
set oCPAppletMgr=nothing
———————————————————————————————

————————————————————————————–
Dim ClientResource
Set ClientResource = CreateObject(“UIResource.UIResourceMgr”)
Set CacheInfo = ClientResource.GetCacheInfo
CacheInfo.TotalSize = 10000
————————————————————————————–

- Microsoft Application Virtualization Sequencer:
The Application Virtualization Sequencer ‘program’ is used to package virtual applications for deployment with Configuration Manager.

- Configuration Manager Site Server:
A part of the Configuration Manager Site hierarchy, the Configuration Manager Site Server manages virtual application distribution through
Configuration Manager Distribution Points to target systems, either as a streaming service, or as a locally delivered package.

- Configuration Manager Distribution Point (Distribution Point):
Configuration Manager Distribution Point site roles provide management services such as hardware and software inventory, operating system deployment, and software updates, as well as software distribution of both physical and virtual applications, to Configuration Manager target systems (often referred to as ‘clients’).

- Configuration Manager / Application Virtualization Clients:
Client devices include desktop/laptop PCs, terminal servers and Windows Vista Enterprise Centralized Desktop (VECD) clients.  Configuration Manager Clients that receive delivery of virtual applications from a Configuration Manager infrastructure require both the Configuration Manager Advanced Client and Application Virtualization Client software to be installed and configured.  The Configuration Manager and Application Virtualization Client software work together to deliver, interpret and launch virtual application packages.  The Configuration Manager Client manages the delivery of virtual application packages to the Application Virtualization Client. The Application Virtualization Client executes the virtual application on the client PC.

Configuration Manager and Application Virtualization Software Requirements:

- A healthy Configuration Manager infrastructure:
It is critical to ensure that the customer’s Configuration Manager infrastructure is healthy before enabling Configuration Manager’s virtual application management features.

Below you’ll find a list of the minimum Configuration Manager infrastructure components required for virtual application management with System Center Configuration Manager R2.

- Primary Site:
A Configuration Manager Primary Site with Configuration Manager 2007 SP1 + Configuration Manager 2007 R2 installed

- Site Server:
A Configuration Manager Site Server configured with the following site server roles:
     – Site System
     - Site Server
     – Component Server
     – Distribution Point
     – Fallback Status Point
     – Management Point
     – Reporting Point

- Distribution Point Servers:
One or more standard Distribution Point servers or Branch Distribution Point servers.  The use of a Branch Distribution Point requires at least one standard Distribution Point

- Clients:
One or more Configuration Manager Client PCs

Below you’ll find a list of the minimum Application Virtualization 4.5 infrastructure components required for virtual application management with System Center Configuration Manager R2.

- Application Virtualization Sequencer
     – Required to sequence applications
     – 4.5.0.1485 or later

- Application Virtualization Client for Windows Desktops
     – Required to run virtual applications on desktop and laptop PCs
     – 4.5.0.1485 or later

- Application Virtualization Client for Terminal Services
     – Required to run virtual applications on Windows Terminal Servers
     – 4.5.0.1485 or later

In this example we are going to enable the Hardware Inventory Client Agent, so we know what hardware is available in our environment.

1.) Go to the Site Management, Your site name, Site Settings, Client Agents, Hardware Inventory Client Agent
2.) Open the properties
3.) Enable the “Enable hardware inventory on clients”
4.) Select a schedule interval
5.) On the client wait for the next “Machine Policy Retrieval & Evaluation Cycle” (to run this action directly, select “Initiate Action”)
6.) You’ll now see an extra action on your client “Hardware Inventory Cycle”
7.) On the client wait for the next “Hardware Inventory Cycle” (to run this action directly, select “Initiate Action”)
8.) Wait a few minutes so that all the collected items are commited into the Site Database
9.) Go to the Computer Management, Collections, All Systems
10.) Select the computer you want to view, right click, Start, Resource Explorer
11.) Now you see all the hardware of this computer

1.) Open your SCCM Management Console
2.) Go to Site Management, your site name, Site Settings, Site Maintenance, Tasks
3.) Here you see “Backup ConfigMgr Site Server”
4.) Open the properties of “Backup ConfigMgr Site Server”
5.) Enable this task, set the backup paths and select the schedule interval
     – Note: when your SCCM Database is on a different server, there’s a folder created on the E:\ drive of that server!
     – For exameple: one folder on server SRV-SCCM01 and one folder on server SRV-SCCM02.
6.) When you want to start the backup manual, you can start the following service on your SCCM Site Server
     – SMS_SITE_BACKUP
7.) Your SCCM environment is now succesfully backuped with exactly the same time stamps.

- Client push
- Software Update point
- Group Policy
- Manual
- Loginscript
- Software Distribution
- Imaging

In this example we are going to push the client to our servers and workstations.

1.) First you need to configure your boundaries. I’ve added a IP range of my workstation DHCP scope. This can also be:
     – IP subnet
     – Active Directory site
     – IPv6 prefix
     – IP address range
2.) Now we can enable the client push installation. Go to Site Management, your site name, Site Settings, Client Installation Methods, Client Push Installation.
     – Enable: “Enable Client Push Installation to assigned resources”
     – System types: Choose the system types where you want to install the SCCM clients
     – Accounts: Type in a account with administrator rights
     – Client: Type in the installation properties. In this example I’m using only the option SMSSITECODE=S01. For an overview of all the options, check the following link: http://technet.microsoft.com/en-us/library/bb680980.aspx
3.) Make sure you’ve run an discovery, so the system where you want to install the client is succesfully discovered
4.) In order to successfully use client push to install the Configuration Manager 2007 client, you must add the following as exceptions to the Windows Firewall:
     – File and Printer Sharing
     – Windows Management Instrumentation (WMI)
5.) Right click on the system where you want to install the SCCM client and select Install Client
6.) After starting the installation, you’ll see the following proccess on your client
     – CCMSETUP.EXE, this is a sign that the installation is running
7.) When the installation is finished, there’s a new proccess CCMEXEC.EXE
8.) Verify that the agent is succesfully installed. Go to your control panel on your client and check the following new icons:
     – Configuration Manager
     – Remote Control
     – Run Advertised Programs

1.) Install the following Role: Webserver IIS
2.) Install the following Role Services of Webserver IIS
     – Web Server
          – Common HTTP Features
          – Static Content
          – Default Document
          – Directory Browsing
          - HTTP Errors
          – HTTP Redirection
     – Application Development
          – ASP.NET
          – .NET Extensibility
          – ASP
          – ISAPI Extensions
          – ISAPI Filters
     – Health and Diagnostics
          – HTTP logging
          – Logging tools
          – Request Monitor
          – Tracing
     – Security
          – Basic Authentication
          – Windows Authentication
          – URL Authorization
          – Request Filtering
          – IP and Domain Restrictions
     – Performance
          – Static Content Compression
     – Management Tools
          – IIS Management Console
          – IIS Management Scripts and Tools
          – Management Service
          – IIS 6 Management Compatibilty
          – IIS 6 Metabase Compatibility
          – IIS 6 WMI Compatibility
          – IIS 6 Scripting Tools
          – IIS 6 Management Console
3.) Enable the following feature, BITS Server Extensions
4.) Enable the following feature, Remote Differential Compression
5.) Open the IIS Manager
6.) Open the WebDAV Authoring Rules
7.) Make a new Authoring Rule with:
     – Allow access to: All content
     - Allow access to this content to: All users
     - Permissions: Read
8.) Open the WebDAV Settings and edit the following options:
     – Allow Anonymous Property Queries: True
     – Allow Custom Properties: False
     – Allow Property Queries with Infinite Depth: True
     – Allow Hidden Files to be Listed: True
9.) Apply theses settings
10.) If you need to extend the Active Directory Schema, you’ve to use the LDIFDE tool. You need to install the Remote Server Administration Tools (RSAT):
     – ServerManagerCmd -i RSAT-ADDS
11.) After the prerequisites check you can report the following logfile:
     – C:\ConfigMgrPrereq.log
     – C:\ConfigMgrSetup.log

In this example i’m going to enable the Active Directory System Discovery. In the following articles I’ll show you also the other discovery methods.

1.) Go to Site Settings and choose Discovery Methods
2.) Open the properties of Active Directory System Discovery
3.) Click on Enable Active Directory System Discovery
4.) Specify the location in your Active Directory you want to discover (root domain, OU level ect…)
5.) Specify the Polling schedule (when should the discovery proccess run)
6.) Enable Run discovery as soon as possible if the proccess must started directly!
7.) Specify the Active Directory attributes you want to discover
8.) After a copple of minutes go to you Computer Management, Collections, All Systems
9.) You’ll see your computer object from the Active Directory environment

1.) Internet Information Services (IIS)
2.) Enable network COM+ access
3.) Background Intelligent Transfer Services (BITS) Server Extensions
4.) Allow WebDAV Web Service Extensions

Now the environment is ready to start the installation. You can run the prerequisite checker to see if you’ve installed all the nessesary prequisites.

1.) The first site server is always the Primary SCCM server (Central Server)
2.) Choose the Custom settings, to specify your installation path, SQL server etc…
3.) The first server is always a Primary site
4.) Give the site a unique site code. This must be a unique 3 character code with a combination of letters, numbers or a combination of this two. For example S01, S02.
5.) Choose the mode for your SCCM environment. Note: for native mode requires a Public Key Infrastructure (PKI)
6.) Choose the agents you want to enable
7.) Specify the computername, instance and database name to store the SCCM database Note: Express Editions of SQL are not supported!!
8.) Enter the SMS Provider, used by the Configuration Manager Console to communicate with the site database
9.) Enter the FQDN of you Management Point. SCCM agents communite with the Management Point
10.) Specify the HTTP settings, default port 80 HTTP
11.) Download the latest updates to ensure the highest level of functionality and compatibility
12.) Check the settings summary
13.) Start the installation
14.) After the installation, check the following logfiles on your C:\ drive
     – ComponentSetup.log
     – ConfigMgrPrereq.log
     – ConfigMgrSetup.log

There are two ways to prepare your Active Directory environment.

1.) Running the EXTADSCH.exe from the installation media. This is a next, next, finish action.
2.) Import the schema extensions with LDIFDE. More actions, but a great logging option.

In my example I’ll use the LDIFDE tool, so the error reporting is much better.

1.) Copy the file CONFIGMGR_AD_SCHEMA.LDF to the local hard drive of your server. (you need to add the server name in this file!!)
2.) Open the file CONFIGMGR_AD_SCHEMA.LDF in Notepad
3.) Edit DC= in DC=DomainName. For example DC=SCCM,DC=LOCAL
4.) Open the command prompt
5.) Enter the following command ldifde -i -f .\CONFIGMGR_AD_SCHEMA.LDF -v -j .\log.txt
     * -i = Turn on Import Mode (The default is Export)
     * -f filename = Input or Output filename
     * -v = Turn on Verbose Mode
     * -j path = Log File Location
6.) Check the logfiles for any errors
7.) Give the SCCM Server full control permissions for performing the installation
8.) Open Active Directory Users & Computers
9.) Open the properties of the organizational unit System
10.) Go to the Security tab
11.) Add the new SCCM Server and give it Full Control to This object and all child objects
12.) Your Active Directory environment is now prepared for deploying SCCM 2007