I wanted to provide an update on where we’ve been. Back in February of 2014 Jesse and I, along with William Bracken & an additional partner, started a new consulting company. We focus on client and datacenter automation, primarily through System Center. You can find our new blog posts here. Here’s a bit of information on the company.
The Model Way
Henry Ford’s creation of the Ford Model T car in 1908 was undoubtedly brilliant, but it was not what made him a pioneer. Ford’s true vision was brought to life when he fine-tuned the assembly line mode of production and enacted a method of keeping the best workers loyal to his company.
You see, he didn’t invent the product. He perfected the process. And he honored the people who worked hard to make it possible. In that, he revolutionized an industry.
At Model, we are inspired by the advancements we’ve seen in businesses through Microsoft automation technology.
Automation fascinates us, and helping businesses achieve their objectives through automation is our professional reason for being. Our team has invested years of our lives studying and perfecting the art of automation, and we are excited to share our expertise to help you see the breakthroughs for your business.
Just as equally, Model is passionate about cultivating a strong IT community. We know that our brand is a reflection of our people, and therefore we are committed to cultivating an empowered, champion technologist culture. And, beyond the Model team, we are invested in contributing to the growth of Microsoft technologies and the world of innovators who support it.
Recently I had the opportunity to troubleshoot SCOM at a client, here’s my recent experience with APM.
My client had two web servers, not joined to the domain. Both of these servers hosted an application that we wanted to instrument with APM. 01 wasn’t working with APM but was working with other OpsMgr alerts and rules. 02 was working for APM and for other alerts and rules.
- These servers are not domain joined (verified the runas account, cert thumbprint, communication port, etc…)
- The two servers are exact clones of one another ( same serialnumber listed in SCOM, not ideal but unsure if this is causing the issue or not)
- OpsMgr agent installs on both 02 – gets the instrumentation 01 – does not
- Both servers show the same discovery information from the IIS MP
- Once I setup the .NET template, here’s a list of high-level troubleshooting steps
- Created a custom group containing only web01 and scoped a new .NET monitor to the group
- On the .net template, I removed the group and flushed the health services
- Tried putting Web01 in maintenance mode for 10 min
- Verified discovered inventory on the health service
- Viewed the failed / applied rules & monitors (no failures)
- setup a new .NET template from scratch
The entire time, I’m closely watching the event logs on Web01 for any signs. Come to find out there was a bug in 2012 SP1 where, if the discovery of the server name shows up in lowercase and in uppercase throughout the OpsMgr Console it may cause APM some heartburn. So I upgraded to 2012 SP1 UR 4, which contains the fix – Read this here’s the link to UR4
Unfortunately, the issue wasn’t resolved, so I went through the steps once again with no positive result. Next I enabled Verbose tracing and created the issue again, stopped verbose tracing, and went through the logs. Decided to reapply the UR4 server update, ran LODCTR /R on Web01, waited 5 minutes, and all was fixed.
Need to get a better understanding on what the WSUS icons mean in the SCCM console? Here’s the TechNet article:
You’ve probably seen the MP 500 error at some point in your SCCM career.
Call to HTTPSendRequestSync failed for port 80 with status code 500, text: internal server error
Well most of the fixes pertain to prereq’s, permissions, or port conflicts. But what if those items don’t resolve your issue? What if you install the MP and all is well. You’ve looked at MPControl, the application event log, MPlist and MPCert and everything is healthy but some time later (4-10 hrs) the dreaded 500 error returns.
Here are some typical troubleshooting steps for an unhealthy MP:
- Check all MP prereq’s (IIS, etc…)
- Check local group permissions on site servers
- Verify DNS and connectivity (firewall, etc…)
- Check the SQL DB for the MP server login and it’s DB role as SMSDBROLE_MP
- Enable SQL logging for successful and unsuccessful logins to review in the app log
- Check for the MP listening ports for bindings to 80 or 443 (netstat -an)
- Check MPList http://<ServerName>/sms_mp/.sms_aut?mplist (should look like XML)
- Check MPCert http://<ServerName>/sms_mp/.sms_aut?MPCert (should look like XML)
- Check SPN (SETSPN -L serviceaccountname)
- Check the W3 logs in InetPub
- Verified the SCCM 2007 client isn’t installed on the 2012 MP
There’s a pretty good thread out there that has the same issue and finds that it’s group policy related which can be found here .
We recently discovered that in our instance the Group policy conflict was service related. There was a policy in place that forced CCMExec to automatic. Removing that policy fixed the instance of the issue we ran into.
As many of you know distribution points have undergone significant changes in SCCM 2012. One of the newer features is the pull distribution points. I would go through the explanation of the new feature but Yvette Omeally did a great job of explaining them n this blog article , happy reading!
Recently I upgraded Configuration Manager 2012 to 2012 Sp1. We had a bunch of task sequences, but they wouldn’t open. I re-ran the configuration manager extension integration from the MDT 2012 Update 1 install, forcing the extensions down and resolved the error. I was thinking of blogging about this topic, and somone already did, 8 days ago. Nice work Jeroen Erkelens, here’s the Post.
MDOP 2013 has launched. Several enhancements to the suite of apps including MBAM 2.0. This utility now has integration into ConfigMgr and a self-service portal and automated provisioning with Win8 deployments. AGPM, DART, App-V, and UEV have all been improved. Continue reading about the new feature sets at the Windows Blog.