ConfigMgr Dashboards

As a ConfigMgr administrator, how often have you wished you had a fantastic dashboards, that in a quick glance could show you the health of your environment and different status in beautiful colours (of course - green is the preferred colour ).



A group of Microsoft PFEs has created a bunch of such dashboards.

You can read more about these here:
https://techcommunity.microsoft.com/t5/premier-field-engineering/premier-offerings-system-center-configuration-manager-and-intune/ba-p/1044351

and here:
https://secureinfra.blog/2019/01/10/configuration-manager-advanced-dashboards-rich-view-of-your-configuration-manager-environment/

On both sites are stated:
If you are a Microsoft Premier customer you can reach out to your TAMs for delivery questions!!

So - go ask your TAM for these.....

end of support for ConfigMgr 2007

Today, July 9th, marks the end of support for ConfigMgr 2007

Unknown SQL Error! in SMSProv.log

I was at a customer who could not start ConfigMgr console on the site server after an CB update.
In SMSProv.log following messages was thrown:
*** *** Unknown SQL Error!
*~*~*** Unknown SQL Error!    ThreadID xxxx, DbError: 50000, Sev: 16~*~*
Results returned: 0 of -1

It turned out that the customer has performed a CB update. During the "Prerequisite Check" they had a warning on SQL server level.
After the update - that went well - they looked at the SQL server.
At some point someone has tried to install a service pack, which has only updated some (?) SQL components, leaving others in current state.
They tried to install the service pack again, but they could not, because the sql was already updated...
They detached the databases, uninstalled and installed the sql server, updated it and attached the databases again.

The ConfigMgr console could not start up...

I did the ConfigMgr Reset, checked the right on the SQL server and databases - all fine, but still the ConfigMgr console didn't start.

Luckily I found a post that stated that ConfigMgr requires SA to be owner of the database.
When you do an attach, the user doing this will become the owner.

I ran EXEC sp_helpdb and found the userid for the person who attached the databases as Owner.
To change the owner, I ran:
USE
GO
EXEC sp_changedbowner 'sa'

After this, I could start up the ConfigMgr console again.

News from MMS 2019

MBAM is being integrated into ConfigMgr.

Fix iPhone battery problem

A couple of days ago my iPhone 6s suddenly started loosing power. Rapidly it went from 80% to 1% (but 1% could last very long time).
It was fast to charge up, but again it rapidly lost power and went to 1%.
Since I could use the phone for a long time when it stated 1% I didn't think it was the battery that was the problem.
I did some (a lot) search and found this advice that could help, and it was much easier than resetting the phone and much cheaper than a new battery.
The article I found, was on a Danish part of "ON X" and it was started in 2012 but has comments right up till now from greatfull readers that has been saved by the tip:


Shutdown the iPhone
Remove SIM card
Power On iPhone and accept that there are no sim card inserted
Shutdown the iPhone
Insert SIM card
Power On iPhone


And - voila - problem is gone (ok, some had do to do it twice)

CCMexec stops right after it has been started

I my environment, I suddenly had a lot of inactive clients. I thought that it was strange, so I dived into the issue.
Looking at a client, I found that the ccmexec service wasn't running.
I started the ccmexec service, but it stopped immediately (later I found that, on other client the service stopped after 5 minutes - they would start a repair, and then fail and stop).
Then I looked into the ccmexec.log and found this:
Service settings instance is missing from WMI.

Error loading service settings. Code 0x87d00218 Phase 0 initialization failed (0x87d00218). Service initialization failed (0x87d00218). Shutting down CCMEXEC
x

I tried a repair, but that didn't solve the problem.
Taking a deeper look into the log told me that the client had a problem with the ccm part of wmi.
I then tried to do a client push with the uninstall option checked - and now... Happy client again.

Looking at all my inactive clients - suddenly 10-15% og my environment - it seemed like this issue happened during the upgrade to 1602.

WSUS server broken after a windows update

Came to office this morning to see this in my ConfigMgr console:

Oh... what a MONDAY morning...











A check in the eventlog shows that some updates were installed during the weekend.
So - what now ? remove updates or.... ask google.
Ahh - I was not alone with this problem.

First, I ended up here: https://blogs.technet.microsoft.com/wsus/2016/04/22/what-you-need-to-know-about-kb3148812-part-two/

Well, I didn't install KB3148812, so this could not be my problem, but an update on the page pointed me to this site: https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/
And from here, I was pointed to the page for KB3159706, which I found was installed on my WSUS server:   https://support.microsoft.com/en-us/kb/3159706
As it stated... you needed a manual process to finish this update.

The command: "wsusutil.exe postinstall /servicing" fixed my problem.
After running the command I could start the wsus service again.