Troubleshooting – sccm.haas.se

Quick-fix for Scheduled Updates and Windows 10

In System Center Configuration Manager 2012 Release 2, Service Pack 1, Cumulative Update 1. There is a bug. If you try to do offline servicing to a Windows 10 Operating System Image (also known as a Scheduled Update) there will be exactly zero visible software updates in the console to apply to the image. It’s annoying but it takes only 30 seconds to fix. But why does this happen? I’ll show you!

This is from SMSProv.log at the same time I tried to Schedule an update and as

Read More…Read More…

Report Builder can’t connect to SQL Server

You try to connect to the SCCM 2012 Data Source but Report Builder throws this error:

“A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 – The certificate chain was issued by an authority that is not trusted.)”

This is because the connection needs to be authenticated by the means of a certificate that is on the SQL-server which your client doesn’t have. You need to export the “ConfigMgr SQL Server Identification Certificate” from your SQL Server Personal store to your clients Trusted Root store. Here’s a How-To:

Read More…Read More…

Build and Capture + Software Updates in Native mode

The goal of this article is to describe how to insert Software Updates into the Base Image, the Windows-image you want to base your Operating System deployment on, in SCCM Native Mode.

In order to shorten the installation time of the operating system for your end-users you want to include as many patches and updates as possible in the image you’re deploying. But you want to include as few programs as possible so that you don’t end up updating your Golden base image every two weeks…

Obviously you will want to update your image with new Software Updates every once in a while – but that will not be manual labour but automated in the task-sequence that builds the Base Image.

I could have written a book about all the things I tried to get this to work… Let’s just establish the fact that Software Updates and in particular WSUS must have been written the morning after some very big Microsoft launch party… ;-)

That said. I finally managed to get this to work. It took a a week of Googling, trial and error, troubleshooting, late nights and lots of coffee. And the silly thing is that’s it pretty easy to get it to work – if you know exactly what to do. As always.

I’ll summarize what this article does:

Use only one Hotfix (KB2509007).
Use SLP as a parameter for your CM-client.
Check “Allow HTTP for roaming…” and rebuild the boot-image.
Run a script to trigger software updates scan and run it a couple of times!

Read More…Read More…

No program in the Task Sequence

You’re trying to add a program in your Task Sequence but the program in your package doesn’t appear?

This can be one of two things.

Either you’re allowing your users to interact with the program or the program can only run with a user logged on. This is not possible since the task sequence is supposed to be unattended.

Choose “Whether or not a user is logged in” and uncheck “Allow users to interact with the program”.

/Mathias

Error poetry

An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset ‘DataSet2’.
The EXECUTE permission was denied on the object
‘PowerManagementGetPowerCapabilities’, database ‘SMS_CEN’, schema ‘dbo’.

Right, so you’re trying to view a report in Reporting Sevices that you copied from ConfigMgr and now you’re getting this. What is wrong? The SQL-account you’re using to access the Reporting Services database simply has insufficent rights. That’s what the message above is trying to tell us.

After some trial and error I gave my Reporting Services SQL-account rights as db_datareader and smsschm_users in the ConfigMgr database (SMS_<sitecode>). See screenshot below:

After that, reports work great.

/Mathias

Subscribe to reports with SQL Reporting Services

Subscribing to reports is really great to show to upper managment. How do you make that work? It’s not too hard actually. You just need to give ConfigMgr a username that has access to the database so that Reporting Services can save the information in the database. I use the same account for that as the account I specified during the installation of SQL Reporting Services. If you run into access problems, check my post above this one.

Accountsettings — Right click on your Server below Reporting Services in ConfigMgr.

/Mathias

Reporting Services configuration can be tricky…

…very tricky indeed. I had no idea how complicated it can be until today.

In this installation of SCCM 2007 R2 (in my case R3) with SP2 – Configuration options where greyed out in the “Copy Reports Wizard” as well as when you right click the Reporting Services Server icon below Reports in the SCCM-console.

According to Microsoft this can happen if you run more than two instances of SQL Reporting Services on the same machine and that’ll make ConfigMgr confused since it automatically selects the default instance of Reporting Server through WMI. I’m pretty sure this issue happens if you choose “Install but do not configure the report server” during the SQL 2008 installation instead of “Install the native mode configuration”. I have to test this in the lab but I’m guessing the SQL RPS instance never gets created if you don’t configure RPS and therefore SCCM can’t find it.

If you want to fix this, all you need to do is to open Reporting Services Configuration Manager and configure RPS manually.

Read More…Read More…