sathwet@gmail.com
- Sath Wetthasingha PGD(UK),Dip-BCS(UK),Dip-NCC(UK),MCSE,MCT,MCLC,MACS,MBCS,MCTS,ACIW
- Melbourne, VIC, Australia
- I’m specialized in Microsoft technologies and information security. I always willing to ride an extra mile to help the IT community sharing my past experience and technical knoladge.
Friday, August 26, 2011
SCCM Software update point technet
About Software Update Point:
About Software Update Point
Planning:
Planning for Software Updates Client Settings
Configuration:
Configuring Software Updates
How to Configure the Software Updates Client Agent
How to Create and Configure an Active Internet-Based Software Update Point
Best Practices:
Configuring Configuration Manager Sites for Best Performance
Checklist for Security Best Practices
Best Practices for Central and Primary Site Hardware and Software Configuration
Best Practices for Operating System Deployment
Software Update Point process Flowcharts:
Software Updates Synchronization Process Flowchart
Software Update Deployment Process Flowchart
Deployment Package Process FlowchartSoftware Update Deployment SuperFlow
About Software Update Point:
About Software Update Point
Planning:
Planning for Software Updates Client Settings
Configuration:
Configuring Software Updates
How to Configure the Software Updates Client Agent
How to Create and Configure an Active Internet-Based Software Update Point
Best Practices:
Configuring Configuration Manager Sites for Best Performance
Checklist for Security Best Practices
Best Practices for Central and Primary Site Hardware and Software Configuration
Best Practices for Operating System Deployment
Software Update Point process Flowcharts:
Software Updates Synchronization Process Flowchart
Software Update Deployment Process Flowchart
Deployment Package Process Flowchart
Thursday, August 25, 2011
Wednesday, August 10, 2011
Monday, July 11, 2011
Configuration Manager ADM Templates
Configuration Manager ADM Templates
Obtain the ADM Templates that comes on the Configuration Manager 2007 CD, located: on the CD\TOOLS\ConfigMgrADMTemplates.
ADM template names:
- “ConfigMgr2007Assignment.adm"
- "ConfigMgr2007Installation.adm"
The "ConfigMgr2007Assignment.adm" is used to place the Configuration Manager site assignment settings in the clients registry
The "ConfigMgr2007Assignment.adm" template sets the following settings in the registry under: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client
- GPRequestedSiteAssignmentCode =
- GPSiteAssignmentRetryDuration(Hour) =
- GPSiteAssignmentRetryInterval(Min) =
The image below shows the settings for the ConfigMgr2007Assignment.adm template after it’s imported into the GPO.
Definitions
The "GPRequestedSiteAssignmentCode" is the site code your client should and will be assigned to. When the client is reassigned by any other method to a site code other than the site code specified in the GPO, these GPO policy settings will automatically reassign the client back to the site code you defined in the GPO policy.
The "GPSiteAssignmentRetryDuration(Hour)" is the amount of hours the client will keep attempting to reassign the client until successful or till reassigned to the site code specified in the GPO.
The "GPSiteAssignmentRetryInterval(Min)" is the interval the GPO policy will wake up and check to see if the client is assigned to the site code specified in the GPO.
The "ConfigMgr2007Assignment.adm" template sets the following settings in the registry under:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\ccmsetup in a Value Name: SetupParameters.
The below settings is the CCMSETUP parameters that will to be set in the above location, which are the parameters the client will use when the installation starts.
/MP:msserver SMSSLP=smsslp.domain.com SMSSITECODE=XR2 FSP=smsfsp.domain.com CCMLOGMAXSIZE=100000 CCMENABLELOGGING=TRUE CCMLOGLEVEL=0 DISABLESITEOPT=TRUE DISABLECACHEOPT=TRUE CCMLOGMAXHISTORY=5 SMSCACHESIZE=9000
NOTE: When a client installation starts, ccmsetup.exe will first look to the command-line first for the ccmsetup parameters. If it does not find ccmsetup command-line parameters, the ccmsetup.exe will look to the registry for the ccmsetup.exe parameters, if the parameters are not found in the registry, the ccmsetup.exe will use Active Directory and assign the client based on Configuration Manager site boundaries.
The image below shows the settings for the ConfigMgr2007Installation.adm template after it’s imported into the GPO.
This type of client assignment forces clients to remain assigned to the site of choice.
Import these ADM templates, into a Group Policy Object targeting the OU or SG of clients to be managed.
An additional setting must added to this GPO the will set the Windows Update URL the clients will use to connect and scan for required offered updates.
This setting location can be found with the local GPO Mgr or GPO Management Console. You can find the location for these settings in the path below.
- Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Windows Update
Thursday, July 7, 2011
Tuesday, May 24, 2011
Deploy SCCM packages to a Security group
Active Directory System Group Discovery
Active Directory Security Group Discovery
once done... in Active directory you need to setup a structure for this,
You will need to create some Active Directory Security Groups, and then create an OU in Active Directory and call it Applications Group
now, you need to create your corresponding Collections in SCCM,
so lets create three new collections
Office 2003
Computers in the Office 2003 Security Group
Users in the Office 2003 Security Group
The two sub collections will have separate queries to determine their contents:
The query for Computers in the Office 2003 Security Group shall be
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.SystemGroupName = "SCCM2007\\Office 2003 Users"
so from the above, SCCM2007=your domain and Office 2003 Users is the Active Directory Sercurity Group you added Computer Objects to.
Note: To define collection queries please read this post
The query for Users in the Office 2003 Security Group shall be
select SMS_R_USER.ResourceID,SMS_R_USER.ResourceType,SMS_R_USER.Name,SMS_R_USER.UniqueU
serName,SMS_R_USER.WindowsNTDomain from SMS_R_User where UserGroupName = "sccm2007\\Office 2003 Users"
Now you can target these sub collections with software to install, so in this case you would target the collections above with an advertisement to install Microsoft Office 2003.
once done, you can start adding computer or user objects to the respective Active Directory Group in active directory, and based on your Discovery Methods schedule they will appear within the correct Collection
and based on the collection they are in they will receive the correct advertisement,
as this is a common question, I have renamed the topic, and pinned it.