Configuration Manager Blog

Configuration Manager 2016 is now out for evaluation download Configuration Manager 2016 is now out for evaluation download Technet is available at https://technet.microsoft.com/library/dn965439.aspx Technet Preview where you can download it & try out in your lab environment. available at https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-configuration-manager-and-endpoint-protection-technical-preview The following exceptions apply to this release: Each install remains active for 60 days before it becomes inactive. English is the only language supported. Only a stand-alone primary site is supported. There is no support for a central administration site, multiple primary sites, or secondary sites. Only the following versions of SQL Server are supported with this build: SQL Server 2012 with cumulative update 2 or later SQL Server 2014 The site supports up to 10 clients, which must run one of the following: Windows 7 Windows 8 Windows 8.1 Windo

ConfigMgr and Active Directory Integration (Extending the Schema) I got some questions that why Active directory integration is required in Configuration Manager, so thought just put theoretical information which will help to understand the concept. (Ref. Book : System Center 2012 Configuration Manager (SCCM) Unleashed ) Active Directory is the central information store used by Windows Server to maintain entity and relationship data for a wide variety of objects in a networked environment. AD provides a set of core services, including authentication, authorization, and directory services. ConfigMgr takes advantage of the AD environment to support many of its features. ConfigMgr can use AD to publish information about its sites and services, making it easily accessible to Active Directory clients. To take advantage of this capability, you must extend the AD schema to create classes of objects specific to ConfigMgr. Although implementing ConfigMgr does not require extending the

System Center 2012 Configuration Manager - Useful Information with links  All in one :  System Center 2012 Configuration Manager Survival Guide Getting Started :  -  System Center 2012 Configuration Manager - Knowledge Base (KB) Articles - Supported Configurations for Configuration Manager - Understanding the new content library store in 5 minutes - Frequently Asked Questions for Configuration Manager -  Technical Reference for Ports Used in Configuration Manager

The domain user account which had full Security rights in SCCM console, if got disabled & your new domain account is not having equivalent full rights. Then how will you access SCCM objects or delgate access to other user accounts? Security rights provide the capability to define and refine the level of access that users have when working with configuration manager objects. This gives you the ability to delegate specific tasks to specific groups of users. In my environment SCCM 2007 was installed by domain admin account "domain\SCCMAdmin1" on Primary site server. Domain\SCCMAdmin1 account has full access on all instances. As employee left the organization, this user account got disabled. Then we created another domain admin account "domain\SCCMAdmin2", Now if anyone will try to copy permissions of "domain\SCCMAdmin1" to "domain\SCCMAdmin2", definately it will give following error Errors ConfigMgr Error Object: instance of SMS_Extende

If you are reinstalling SCCM on the same hardware with same old site code then refer this link It's not best practice nor is it supported to re-use site codes. It's best if you make site codes totally random. Nobody will ever see the secondary site code except for the SCCM admin. Site codes are a bigger deal on primary sites. In that case you CAN NOT reuse them because the site code is appended to all package, advertisement, etc. This would be a major problem because they could end up being duplicated from the old environment to the new one which would wreak havoc on your clients.   Where you want to replace a primary they only way to reuse that site code is to restore the primary site from the SCCM backup created on the server before it died.

I had uninstalled the SCCM 2007 secondary site & again was trying to install it on the same hardware without formatting the OS. In the setup installation, while installing the SMS provider component it gave the error  'Setup failed to install SMS provider' When I checked it in ConfigMgrSetup.log CompileMOFFile:Failed to compile MOF E:\SMS\bin\i386\NetDisc.mof, error -2147217407 Setup cannot compile MOF file E:\SMS\bin\i386\NetDisc.mof. Do you want to continue? Setup failed to install SMS Provider. For more information about this error, see Microsoft Knowledge Base at http://microsoft.com or contact Microsoft Technical Support for further assistance. This type of error can also occur when the namespace 'NetworkModel' is not removed from WMI, while uninstallation of SCCM, on the same machine and then an SCCM 2007 RTM install is attempted. In my case  I had uninstalled the secondary site from the same hardware machine & was trying to install SCCM