Creating And Configuring The AD System Management Container For SMS
This document will walk you through the process of creating and
configuring the Active Directory System Management container for SMS.
This applies to SMS 2003 (either Service pack) on a Windows 2003
Server operating system.
Note: You must be a member of the Schema Administrator group to
successfully extend the schema.
Use the following steps to create the from the System Management container
Download the Windows Server 2003 Support Tools to get the AdsiEdit utility.
From a Windows 2003 Server DC logon as an account that is a member of
the Schema Administrator group.
From the "Start" - "Run" line type in Adsiedit.Msc then and click "OK".
Click the + sign next to your "Domain (ServerName.DomainName.Com\Net)"
Click the + sign to expand the "DC=DomainName,Dc= Com\Net"
Click the + sign to expand the "CN=System" container.
Right mouse click the "CN=System" container and from the context menu
select "New" and then select "Object" to begin the Create Object
wizard.
From the "Create Object" "Select A Class" dialog box select
"Container" then select "Next" to continue.
In the "Value:" line type in "System Management" and click "Next" to continue.
Select "Finish" to complete the System Management container creation process.
Verify that the "CN= System Management" object has been created successfully.
From the "Administrative Tools" program group select "Active
Directory Users And Computers"
From the "View" menu select "Advanced features" to allow the "System"
leaf to be displayed.
Click the + sign to expand the "Systems" leaf then select Right mouse
click on the "System Management" container and from the context menu
select "Properties".
From the "System Management Properties" dialog box select the "Security" leaf.
Select "Add" then select "Object Types" and make sure that both the
"Users" and "Computers" object types are checked then click "OK" to
close the window.
Select "Advanced" and the "Users, Computers, or Groups" dialog box
will be displayed.
Select "Find Now" and select your SMS Service account if you are
running in Standard Security Mode or your SMS server name if you are
running in Advanced Security Mode then click "OK" to continue.
Highlight the account that you are using (from the step above) and
grant the account the following rights:
Read
Write
Create All Child Objects
Delete All Child Objects
Click "OK" to complete the task.
Insert your SMS Installation CD-ROM media in the CD drive and from the
"Start" - "Run" line browse to the "SmsSetup\Bin\I386" directory
folder and select "Extadsch.Exe" and click "OK"
Click "OK" once again and the command prompt window opens and the
application begins.
When the process has completed open the ExtADSch.Log file located in
the root dive (C:\) of the server from which it was executed from and
verify that the last line states: "SMS Setup completed successfully!"
-------------------
Thanks,
http://paddymaddy.blogspot.com/
SMS_Def.Mof : Mcafee ePO Dat Version Hardware Inventory Mof File modify
Mof File modify:-
// //
// Mcafee ePO Plugins Enumeration //
// //
/////////////////////////////////////
#pragma namespace ("\\\\.\\root\\cimv2\\sms")
#pragma deleteclass("Win32Reg_Mcafee_ePO_Plugins", NOFAIL)
[ SMS_Report (TRUE),
SMS_Group_Name ("Mcafee ePO Plugins"),
SMS_Class_ID ("McAfee|ePO_Plugins|1.0") ]
class Win32Reg_Mcafee_ePO_Plugins : SMS_Class_Template
{
[SMS_Report (TRUE), key ] string SoftwareID;
[SMS_Report (TRUE) ] string Version;
[SMS_Report (TRUE) ] string ProductName;
[SMS_Report (FALSE) ] string PluginPath;
[SMS_Report (FALSE) ] string UninstallCommand;
[SMS_Report (FALSE) ] string InstallPath;
[SMS_Report (FALSE) ] string InstalledPath;
[SMS_Report (TRUE) ] string HotFixVersions;
[SMS_Report (TRUE) ] string HotFixInstallDate;
[SMS_Report (TRUE) ] string DatInstallDate;
[SMS_Report (TRUE) ] string DatVersion;
};
//Configuration.MOF
/////////////////////////////////////
// //
// Mcafee ePO Plugins Enumeration //
// //
/////////////////////////////////////
#pragma namespace ("\\\\.\\root\\cimv2")
#pragma deleteclass("Win32Reg_Mcafee_ePO_Plugins", NOFAIL)
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Network
Associates\\ePolicy Orchestrator\\Application Plugins")
]
class Win32Reg_Mcafee_ePO_Plugins
{
[PropertyContext("Software ID"), key] string SoftwareID;
[PropertyContext("Version")] string Version;
[PropertyContext("Product Name")] string ProductName;
[PropertyContext("Plugin Path")] string PluginPath;
[PropertyContext("Uninstall Command")] string
UninstallCommand;
[PropertyContext("Install Path")] string InstallPath;
[PropertyContext("Installed Path")] string InstalledPath;
[PropertyContext("HotFixVersions")] string HotFixVersions;
[PropertyContext("HotFixInstallDate")] string
HotFixInstallDate;
[PropertyContext("DatInstallDate")] string DatInstallDate;
[PropertyContext("DatVersion") ] string DatVersion;
};
-------------------
Thanks,
http://paddymaddy.blogspot.com/
Sccm 2007 DCM Web resources from Microsoft
Desired Configuraion Manager Web resources from Microsoft.com
Configuration Manager Configuration Pack Catalog
https://www.microsoft.com/technet/prodtechnol/scp/configmgr07.aspx
Technical Reference for Desired Configuration Management
http://technet.microsoft.com/en-us/library/bb680894.aspx
Configuration Pack Authoring Guide
http://technet.microsoft.com/en-us/library/bb680894.aspx
Configuration Manager Documentation Library
http://technet.microsoft.com/en-au/library/bb680651.aspx
Configuring Desired Configuration Management
http://technet.microsoft.com/en-au/library/bb680669.aspx
Desired Configuration Management on TechNet Forums
http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=1817&SiteID=17
DCM with SCCM 2007
The configuration Manager 2007 toolkit contains the following tools for DCM
DCM Model Verification - A tool used by desired configurationmanagement content administrators for the validation and testing of
configuration items and baselines authored externally from the
Configuration Manager console.
DCM Digest Conversion - A tool used by desired configurationmanagement content administrators to convert existing SMS 2003
Desired Configuration Management Solution templates to Desired
Configuration Management 2007 configuration items.
DCM Substitution Variables - A tool used by desired configurationmanagement content administrators for authoring desired
configuration management configuration items that use chained
setting and object discovery.
SCCM 2007 R2 Application Virtualization
http://weblog.bassq.nl/?p=157#more-157
Enjoy,
Paddy
SCCM 2007 Virtual Application all Packages Tools Pdf files and Scripts how to use them
Using the Virtual Application Package Tools
The following list of procedures describes how to use the tools that are available to help manage virtual application packages in your Configuration Manager 2007 environment. By default, the files are located in the following directory: <ConfigMgrInstallationPath> \ SMS \ Tools \ VirtualApp.
AppVirtMgmtClient.sms
Use the AppVirtMgmtClient.sms file to create a Configuration Manager 2007 package to distribute the Microsoft Application Virtualization (App-V) Client. For more information about installing the App-V client, see How to Install the Microsoft Application Virtualization Client.
Note
By default, the program created by AppVirtMgmtClient.sms file will restart the target computer because the App-V client setup needs to update files used by the operating system. When you upgrade from previous versions of the App-V client, you must use the setting ConfigMgr restarts computer. For new App-V client deployments, you can change this program setting to No action required. However, you should install the App-V client setup manually in a test environment to ensure the computer does not need to be restarted as part of the installation.
After the App-V client has been installed, software metering for virtual application packages will not be available until after you have restarted the target computer. You should choose the setting ConfigMgr restarts computer if you plan to run software metering for virtual application packages.
AppVirtMgmtSequencer.sms
Use the AppVirtMgmtSequencer.sms file to install the App-V sequencer into your Configuration Manager 2007 environment. For more information about installing an application using a program definition file, see How to Create a Package from a Package Definition File.
Using the ManageVAppPackage.vbs Script
You can use the ManageVAppPackage.vbs file to import new virtual applications and update existing virtual application packages in Configuration Manager 2007.
Use the following procedure to manage virtual application packages
To manage virtual application packages
Open a command prompt. Navigate to the directory containing the ManageVAppPackage.vbs. The default location is <ConfigMgrInstallationPath> \ SMS \ Tools \ VirtualApp \ ManageVAppPackage.vbs.
To update an existing virtual application package, or to import a new virtual application, type the applicable command.
To import a new virtual application, type the following command using your values:
cscript ManageVAppPackage.vbs /Action ADD /SGVAppSource VirtualApplicationSourceDirectory /SMSVAppSource \\Server\VappsourceDirectory\VirtualApplicationName [/DPList \\Server\Share] [/PackageName YourPackageName] [/PackageComment YourPackageComment] [/Manufacturer YourManufacturer] [/Language YourLanguage]
To update an existing virtual application package, type the following command using your values:
cscript ManageVAppPackage.vbs /Action UPDATE /PackageID YourPackageID /SGVAppSource VirtualApplicationSourceDirectory /PackageName YourPackageName [/PackageComment YourPackageComment] [/Manufacturer YourManufacturer] [/Language YourLanguage]
Use the value descriptions in the following table to help you determine the actual text you will use with the preceding commands.
Value Description
/Action
Specifies if a new virtual application will be imported or an existing package will be upgraded. To import a new virtual application, use the ADD parameter. To update an existing virtual application package, use the UPDATE parameter. If you are importing a new virtual application, do not specify an associated PackageID. If you are updating an existing virtual application package, do not use the /DPList parameter.
/SGVAppSource
Specifies the source location for the App-V virtual application. Configuration Manager 2007 will copy the contents from the specified directory. The directory specified can be a local folder or a folder specified by using UNC format.
/SMSVAppSource
Specifies the Configuration Manager 2007 source folder. You must specify this location using UNC format.
/Packagename
Specifies the package name for the virtual application package. If no name is specified, Configuration Manager 2007 will assign the name specified in the associated manifest file.
/DPList
Specifies the distribution points that the virtual application package will be added to. If you want to add the package to all distribution points, use an asterisk (*).
/PackageComment
Specifies the comment that will be associated with the virtual application package.
/PackageID
Specifies the Configuration Manager 2007 package associated with the virtual application.
/Manufacturer
Specifies the manufacturer that will be associated with the virtual application package.
/Language
Specifies the language that will be associated with the virtual application package.
Using the SetRetensionRules.vbs Script
You can configure retention rules for virtual application packages by using the SetRetentionRules.vbs file. This script can be used only on a primary Configuration Manager 2007 site.
Use the following procedure to set the retention rules for virtual application packages located on Configuration Manager 2007 distribution points.
To set virtual application package retention rules
Open a command prompt. Navigate to the directory containing SetRetentionRules.vbs. The default location is <ConfigMgrInstallationPath> \ SMS \ Tools \ VirtualApp \ SetRetentionRules.vbs.
To set the retention rules, type the following command, replacing the text in brackets with your values:
cscript SetRetentionRules.vbs [TransitionDays] [Max Versions]
Use the value descriptions in the following table to help you determine the actual text you will use in the preceding command.
Value Description
TransitionDays
Specifies the number of days virtual application packages will be saved.
Max Versions
Specifies the maximum number of versions that will be saved.