When you want to give some users permission to manage you SCCM 2007 environment, you don’t want to give them full admin rights. With the ConfigMgr User Wizard, you can add users and specify the permissions for this users based on classes and instances.

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

when you’re going to deploy a new package with SCCM 2007, there are a few steps you need to follow. The easiest way to deploy a package is to follow the next steps:

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!

When you make any changes to your SCCM 2007 environment, the clients will polling for this changes by a interval. Default this is 60 minutes. If you want to force an Machine Policy Retrieval, you can use to following two options:

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
———————————————————————————————