HTTP Error 500.19 - Internal Server Error - SCCM 2012 SP1 - Windows Server 2012 - WSUS x64

Hello,

I noticed that I was getting a lot of red crossed under my site components and that my default website was chucking out the following error after a WSUS install on the local SCCM server.

HTTP Error 500.19 – Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.

This was also the case when trying to access http://localhost/ccm_client and application portals.

I had a look at the ApplicationHost.config file and noticed that suscomp.dll was installed by WSUS.

Resolution
1. Go to C:\windows\system32\inetsrv\config and locate the ApplicationHost.config file
2. Open it with notepad and look for the following lines below

scheme name=”xpress” doStaticCompression=”false” doDynamicCompression=”true”
dll=”C:\Windows\system32\inetsrv\suscomp.dll” staticCompressionLevel=”10″
dynamicCompressionLevel=”0″ />

3. The following command needs to be run to disable the suscomp.dll that was installed when the WSUS server role was installed, Im not 100% sure but from what I could see compression schemes are in every application pool and when WSUS x64 was installed the suscomp.dll chucks out the 500.19 error when its trying to load the x86 application pool. So from an elevated command prompt running the following.

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

4. If you need to re-enable this just change it slightly and run this command.

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /+[name='xpress',doStaticCompression='false',dll='%windir%\system32\inetsrv\suscomp.dll']

SCCM 2012 Server Sizing Guide

Please see below the latest server sizing guides for SCCM 2012 as provided by RFLSYSTEMS

Link Below

http://www.rflsystems.co.uk/resources/

How I passed my Configuring and Deploying a Private Cloud with System Center 2012 70-247 exam.

I recently sat this exam and I wanted to talk a little about how I passed the exam. Basically what you are tested on can be found here: http://www.microsoft.com/learning/en/us/exam.aspx?id=70-247 

Its an exam on almost everything System Center and a little bit of Hyper-V, oh and lets not forget storage. The subject matter is a mile wide and an inch deep (Gregg Shields gave me that quote). Its not an easy exam as you are basically answering a bunch of high level questions "what if" scenarios.

I have put together a little help section below that helped me pass the exam. I used a lab with VMware and some very kind Server 2008 R2 images that my gracious employer gave me. So get a hypervisor and complete the following in your lab the hard way. This isn't easy so therefore is totally and utterly worth doing.

1. Understand the Microsoft Private Cloud Architecture and Components. There are 8 of these that make up the system center suite. You will use 7, SCCM isn't really utilized here.
TIP: Private Cloud is NOT Hyper-V.

2. Install Hyper-V on Windows 2008 R2. System Center products Pre-SP1 aren't supported on Server 2012. So don't waste time installing it.

3. Install VMM2012. Learn VMM, Love VMM, Keep VMM close.

4. Configure Your Logical Networks in VMM and Storage Arrays.

5. From VMM, Create a Hyper-V Cluster (if you have more than 1 host) and Create a Private Cloud. There is a button that says "Create Cloud" so don't stress.

6. Working with the VMM 2012 Library: Profiles and VM Templates. Making a Private Cloud is basically the beginning. Play around with templates and profiles to lay the foundations of automation.

7. Configure VMM User Roles and the Self-Service Portal. The VMMSSP is obsolete come SP1, but its on the exam.

8. Create Virtual Application Packages with the Server App-V Sequencer. This is relatively simple and fun actually.

9. Work with VMM 2012 Services and Service Templates. Play around with these, they offer the capability of automatic VM provisioning

10. Create a 3 Tier Service. This is not easy and it took me 4 days to figure it out properly.

11. WSUS on VMM 2012. Easy to up and important to learn.

12. From VMM figure out how to automate the deployment of Hyper-V Hosts - Again, not simple but a massively valuable skill once you have learned it.

13. Install and play with App Controller.

14. Install SCOM and figure out how to integrate Cloud Monitoring from SCOM via VMM 2012.

15. Service Manager integration with all things system center.  Fairly simple and worth spending the time doing.

16. Install DPM and SCORCH. Play with runbooks, and set up some simple backups via DPM.

17. Azure. Understand what it is, and how to use it via App Controller, that's it.

There is a lot to learn but ensuring that only the minimum requirements are met and they are deployed in their simplest form is the key here. You do not need to have in dept knowledge of all the components.

All the help and support is out there, TechNet, MSDN and blogs, all this achievable in a about 5-10 days.

Good Luck.

Top Tips for ConfigMgr/SCCM 2012 From 1E

I was digging around on myitforum.com for a post regarding SCSM, but I found this, its a really great post that was from TechNet originally.

I have I feel cant quite get enough good advice from deploying SCCM. 

Enjoy.

1E Consultants took a deep dive into System Center 2012 Configuration Manager and here are their top tips for success.

1. Application model – ConfigMgr 2012 introduces a completely new alternative approach to software distribution – the Application Model. With the Application Model, an Application has a number of Deployment Types, each defining the required source files, install and uninstall command lines and user experience (e.g. does a user need to be logged in?), similar to the properties of the legacy Package and Program.
2. Site hierarchy – data can be now coordinated and replicated throughout the Central Administration Site (CAS), while boundaries can be set for all ‘sites’, providing a simpler, minimalist way to manage the IT infrastructure. A Single Site ConfigMgr 2012 hierarchy will be a reality for most organizations with less than 100,000 clients to manage.
3. Site-to-site replication – Site-to-Site communication has received a major overhaul in ConfigMgr 2012 with the introduction of SQL replication replacing most of the legacy file transfer in and out of inboxes. Changes in any Primary Site database will be replicated globally to all Sites in the hierarchy, not just the immediate parent or child.
4. Administration – The Admin Console in ConfigMgr 2012 has been completely redesigned and written from the ground up. It does not use MMC, displays only the features the admin has rights to and has a separate MSI for installation. The revamped admin security model offers a combination of security roles, collections and security scopes to define what objects an administrative user can see and the types of actions they can perform.
5. Managing clients over the internet – New to ConfigMgr 2012 is the possibility for internet-based clients to evaluate user-based policies (such as Application Deployments).
6. Scalability – support for up to 400,000 clients in a Single Site hierarchy when the database for the CAS is running SQL Server Enterprise. Each Primary Site can support up to 100,000 clients if the database and Primary Site roles are hosted on separate servers.
7. Distribution points – There are some notable changes in the role of the Distribution Point (DP) in ConfigMgr 2012. Essentially a single Distribution Point replaces the previous Branch Distribution Point.
8. User in control – ConfigMgr 2012 has been built with the user in mind. The Software Center provides an accessible interface for the user to view and manage all software installed, as well as a new level of control over the actions that will impact users the most.
9. Client health and efficiency – new agents such as Health Evaluation and Endpoint Protection, as well as the Automatic Deployment Rules feature, work to ensure clients remain healthy, operational and efficient.
10. Client configuration – the introduction of ‘profiles’ replace the previous blanket global approach to configuration, allowing more specific settings dependent on your needs. What is really cool with this interface is that new classes can be added by connecting to WMI on any computer and browsing to the class you want to report on.

If you would like a detailed version of these tips please mail: su.kent@1e.com.