SCCM 2012 Archives - Page 3 of 5

Security Compliance Manager 3.0

Feb

24

2013

Tweet With the Microsoft Security Compliance Manager (SCM) can help you to create and maintain security baselines using Group Policy Objects or System Center Configuration Manager 2012. With SCM, you can obtain baseline policies based on security best practices , customize them to the particular needs of your organization and export them to a number ...

System Center 2012 Configuration Manager Configuration Pack 5

Feb

23

2013

Tweet Compliance Settings for ConfigMgr 2012. Microsoft has provided us with a Configuration Pack for ConfigMgr 2012. This Configuration Pack contains Configuration Items and a Configuration Baseline for our ConfigMgr 2012 environment. This Configuration Pack monitors following: Management Point(s); Site Server(s); Software Update Point(s). You can download the Configuration Pack HERE. From the Microsoft site: ...

ConfigMgr 2012 Compliance Settings

Feb

23

2013

Tweet Compliance Settings in SCCM 2012 SP1. This was called ‘Desired Configuration Management’ in SCCM 2007. Compliance Settings consist of ‘Configuration Items’ and ‘Configuration Baselines’. There is another node here: ‘User Data and Profiles’. This one is not a Compliance Setting but Folder Redirection from within the ConfigMgr Console…(hmm well that’s what GPO’s are ...

WSUS and ConfigMgr 2012 HTTPS communication 3

Feb

2

2013

Tweet When you have your ConfigMgr 2012 site fully communicating over HTTPS you may also want your Software Updates delivered over a secure channel. Well that´s possible! More info: http://technet.microsoft.com/en-us/library/bb633246.aspx When you have the WSUS component installed on the SCCM 2012 SP1 server, the same certificate that was used to secure the ´Default Web Site´ ...

HTTPS Communication SCCM 2012 SP1 (Part 3) 3

Feb

2

2013

Tweet If you do a default installation of ConfigMgr 2012 the clients will communicate over HTTP with the Management Point. Also all traffic from the Distribution Point will be over HTTP. And if you use the Application Catalog, well that’s HTTP also. In this 3 post series I will explain the steps to go from ...

HTTPS Communication SCCM 2012 SP1 (Part 2) 7

Feb

2

2013

Tweet If you do a default installation of ConfigMgr 2012 the clients will communicate over HTTP with the Management Point. Also all traffic from the Distribution Point will be over HTTP. And if you use the Application Catalog, well that’s HTTP also. In this 3 post series I will explain the steps to go from ...

HTTPS Communication SCCM 2012 SP1 (Part 1) 3

Feb

2

2013

Tweet If you do a default installation of ConfigMgr 2012 the clients will communicate over HTTP with the Management Point. Also all traffic from the Distribution Point will be over HTTP. And if you use the Application Catalog, well that’s HTTP also. In this 3 post series I will explain the steps to go from ...

Create Cloud Distribution Point on Windows Azure with SCCM 2012 SP1 (Part 2) 1

Feb

1

2013

Tweet Cloud, everybody is talking about that. And with the new ConfigMgr 2012 SP1 fully integrating with Windows Azure it’s time to see how this works. You need to have some things in place first, so here we go: A Windows Azure subscription (duh) A working PKI Infrastructure 2 (a .cer and a .pfx) certificates ...

Create Cloud Distribution Point on Windows Azure with SCCM 2012 SP1 (Part 1) 2

Feb

1

2013

Tweet Cloud, everybody is talking about that. And with the new ConfigMgr 2012 SP1 fully integrating with Windows Azure it’s time to see how this works. You need to have some things in place first, so here we go: A Windows Azure subscription (duh) A working PKI Infrastructure 2 (a .cer and a .pfx) certificates ...

Domain-Join Account for SCCM and MDT 8

Jan

30

2013

Tweet When working with deployment tools you need to have an account which can add Computers to a certain Organizational Unit (OU) in Active Directory. As we all know: do NOT use a ‘Domain Admin’ account for this purpose. The account used for adding computers to Active Directory will appear unencrypted in the unattend.xml! So ...