Author: Eswar Koneti

Configuration Manager uses site system roles to support management operations at each site. When you install a Configuration Manager site, some site system roles are automatically installed and assigned to the server on which Configuration Manager Setup has run successfully. One of these site system roles is the site server, which you cannot transfer to another server or remove without uninstalling the site. You can use other servers to run additional site system roles or to transfer some site system roles from the site server by installing and configuring Configuration Manager site system servers. Each site system role supports different…

Listing the frequently asked questions on the features of configuration manager 2012 .This might be beneficial to you to know about its features and difference with its previous version of configuration manager 2007. The Configuration Manager Console : Does the Configuration Manager console support a 64-bit operation system? Yes. The Configuration Manager console is a 32-bit program that can run on a 32-bit version of Windows and on a 64-bit version of Windows. Sites and Hierarchies : Are there new Active Directory schema extensions for System Center 2012 Configuration Manager? No. The Active Directory schema extensions for System Center 2012…

Listing the comparison between Configuration manager 2007 what we know and configuration manager 2012.   Feature Configuration Manager 2007 Configuration Manager 2012 Create/Model Software Package                      Program Application                            deployment deploy Software Advertisement(Install Status) Deployment(state-Based) Via Detection Method Targeting Collection Rules(server-Based) Requirement Rules(Client-Based) User-Targeting None or Limited User Device Affinity Client User Experience Run Advertised Programs Software Center Software Install From Website None Application Catalog Content Management None or Limited content Library

Configuration Manager 2012 RC2 native 64-bit applications no more supported on 32 Bit (OS and Hardware should be 64 Bit). Site server and Site roles : Windows Server 2008 (64-Bit) Windows Server 2008 R2 (64-Bit) Database (Below are listed for SCCM 2012 RC2): Supported versions of SQL Server 2008(64-Bit) for RC2: SQL Server 2008 SP2 Standard and Enterprise with CU7 SQL Server 2008 R2 SP1 and CU4 SQL Server Express 2008 R2 and CU4 If you are running SQL 2008 SP2, install CU7 from http://support.microsoft.com/kb/2617148 If you are running SQL Server 2008 R2 SP1, use CU4 from http://support.microsoft.com/kb/2633146 Distribution Point…

When SCCM client is installed on computers and get assigned to site correctly,you will have schedule ID’s for each agent that runs on the client.  You can use the below codes to kick off different agents on the client. There are several scripts out there that will allow you to to do this. One of the most used is the SendSched.vbs file from the SMS 2003 Toolkit2. The toolkit can be downloaded from this link. Hardware Inventory Collection Task {00000000-0000-0000-0000-000000000001} Software Inventory Collection Task {00000000-0000-0000-0000-000000000002} Heartbeat Discovery Cycle {00000000-0000-0000-0000-000000000003} Software Inventory File Collection Task {00000000-0000-0000-0000-000000000010} Request Machine Policy Assignments {00000000-0000-0000-0000-000000000021}…

I ran into an issue with a customer where they were getting an error that the package could not be downloaded. The that they kept showing up in the client logs was 0x80070057. In going over the logs and researching the issue we found that the issue was in that the file path was too long. The deployment was a user based install which adds a lot of characters to the path. The problem is with writing the files to the cache on the client side. The error number 0x80070057 translates to "The parameter is incorrect." Here is a little…

SCCM collection that returns all windows XP or Windows 7 machines which has 1 GB of RAM(1024*1024 KB) running with MS office products. select *  from  SMS_R_System inner join SMS_G_System_X86_PC_MEMORY on SMS_G_System_X86_PC_MEMORY.ResourceId = SMS_R_System.ResourceId inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceId = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_X86_PC_MEMORY.TotalPhysicalMemory = 1048576 and (SMS_G_System_OPERATING_SYSTEM.Caption = "Microsoft Windows XP%" or SMS_G_System_OPERATING_SYSTEM.Caption = "Microsoft Windows 7%") and SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Microsoft Office 2003%"   Edit the display name correctly from your Add and remove programs and change the RAM as per the needs.

Configuration Manager 2012 is introducing a lot of changes in update deployment procedures. Most of the changes are around the "HOW" part while there are some new concepts too. In this post I'll talk about what some of the changes are around: Configuration of Software Updates components Deployment of software updates to endpoints Monitoring and tracking deployment status