maandag 4 juli 2011

ConfigMgr: SMS SRS web service is not running on SRS Reporting point server when using SQL 2008 R2


Since about a year SQL 2008 R2 is a supported platform for System Center Configuration Manager. However, when you use the Reporting Services Server as apposed to the ConfigMgr Reporting you get an error every hour, stating your Reporting Services Point cannot be reached. When you connect to the point, it works without a problem though.

The exact message from the ConfigMgr console is:
SMS SRS web service is not running on SRS Reporting point server

The error has error message 7403.

Some time ago the SQL Server product team released a new Cumulative Update (CU) for SQL Server 2008 R2, which fixes the issue.

If you are encountering above mentioned issue, please download CU4 from and install it on the SQL server used for hosting the Site Database and Reporting Services.

Hope this helps.


Stefan Hazenbroek

zaterdag 25 juni 2011

ConfigMgr: Deploy Internet Explorer 9 as part of a Task Sequence


When installing Internet Explorer 9 during OS Deployment the installation gives a weird issue after the machine is fully deployed. When a non-administrative user logs in to the machine, the Internet Explorer shortcutshows up as a "blank" icon and the target points to a non-existent path like T:\.  When an Administrative user logs on to the computer before a non-administrative user does, everything will be okay.

This error seems to be caused by an issue in the Active Setup part of Internet Explorer 9. Please see this post by Steven Bone explaining what Active Setup is and means.

As long as there is no bugfix available for this issue, you can deploy Internet Explorer 9 correctly via a task sequence following these steps.

- Install Internet Explorer 9 in the task sequence by using the .msu file.
- After a reboot, create the following two task sequence actions:
Task Sequence Step 1:
reg.exe DELETE "HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components" /v "NoIE4StubProcessing" /f 
The task sequence step (Run Command Line) should look like this:

Task Sequence Step 2:
reg.exe DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce" /v "NoIE4StubProcessing" /f

The task sequence step (Run Command Line) should look like this:

In my case I have to tick the box "Disable 64-bit file system redirection" because I am deploying Windows 7 x64 workstations.

I hope this helps in deploying Internet Explorer 9 successfully.


Stefan Hazenbroek

maandag 30 mei 2011

ConfigMgr: OSD Domain Join fails when Computers CN/OU is chosen

Hi all,

When I build up an environment, I always try to keep everything tidy and as close to reallife as possible. This made me find out the fact that ConfigMgr's OSD domain join will fail when you choose for the Computers CN as a container instead of a "real" OU.

So, when you have a task sequence to install Windows (whatever version) within SMS 2003, SCCM 2007 or even SCCM 2012, if the domain join fails without an error in the Advertisement status, this is most likely the problem.

Open up the Apply Network Settings step in the Task Sequence and change the OU to a real OU, or to blank when the computers should be put in the Computers CN.

I hope this helps.


Stefan Hazenbroek

donderdag 24 maart 2011

BitLocker: Microsoft BitLocker Administration and Monitoring beta available for download

Microsoft has just released the Microsoft BitLocker Administration and Monitoring (MBAM) beta to the public. This beta can be downloaded by subscribing to the Connect site of Malta.

For more information about MBAM, check out the following link:

In the following posts I'll cover the installation and configuration of MBAM.


Stefan Hazenbroek

vrijdag 25 februari 2011

W7/2K8 R2 SP1: Remove unneeded Service Pack files

As you might know SP1 for Windows 7 and Windows Server 2008 R2 has been released recently. This SP contains all prior updates released through Windows update and some important updates aside from that.

In this short blogpost I will explain how you can remove the installation files of the SP so you can keep your installation tidy. This is particularly handy when you want to create an image of the installation so you can have your pc's deployed with SP1 included from now on.

Now, off we go.

1. First, open My Computer.
2. Right click on your C-Drive (or the drive on which Windows is installed on, for the sake of argument I'll assume this is C).
3. Choose Properties.

4. Clik Disk Cleanup.
5. Click Clean up System Files.
6. Tick Service Pack Backup Files so the checkbox is selected. As you can see this will cleanup about 540M on my pc.
I hope this helps.


Stefan Hazenbroek

donderdag 13 januari 2011

ConfigMgr: Drivers not applicable.

Consider the following scenario. You're running SCCM 2007 SP2 with R2 (or R3 for that matter) on Windows Server 2008 and want to deploy Windows 7 cliƫnts. When you try to import the drivers for your Windows 7 workstations into SCCM you might run into the issue when some drivers give the error:

The selected driver is not applicable to any supported platforms
You'll only get this error when you're trying to import drivers that are Windows 7 exclusive. This issue is due to the fact that SCCM uses the internal methods of handling inf files and Windows Server 2008 does not 'know' of Windows 7 yet. Install the following hotfix from Microsoft to fix this issue.
Remember, this is not applicable on Windows Server 2008 R2 but only for windows Server 2008.

Hope this helps.


Stefan Hazenbroek

AD CS: Move AD CS Database and Log to a different drive

What if you created a certificate infrastructure, sized it according to the requirements known at the moment and a new project comes along that requires a certifcate services Database and log that is three times the size of the original one, so it doesn't fit onto your sized harddisk. In alot of scenario's it's possible to expand the disks (using vmware, xenserver or hyper-v this is quite easy), but when you're using physical servers it's not so easy.

Or, maybe, when you installed AD CS you forgot to move it from c:\windows\system32\Certsvc. No worries, it's quite easy to change it.

In this short blogpost I'll explain how to move the certificate services database and log location after AD Certificate Services has been installed.

1. Prepare the disk, LUN or whatever you have in mind for your database and log. Ideally both will be placed on separate disks for performance reasons. Create the path for the database and log. In case it'll be placed on one disk I always assume CertDB for the database and CertDB\Logs for the logs, to keep things tidy.

2. Stop the AD Certificate Services service by running net stop certsvc from an elevated command prompt or by right clicking and selecting Stop service in the Services MMC.

3. Copy the database and the logs to their new location.

4. Open the registry editor by starting regedit and browse to HKLM\System\CurrentControlSet\Services\CertSvc\Configuration.

5. Edit the following entries:
DBDirectory (default is C:\Windows\System32\CertLog\..., change it to your new databasedir)
DBLogDirectory (default is C:\Windows\System32\CertLog, change it to your new logdir)
DBSystemDirectory (default is C:\Windows\System32\CertLog, change it to your new databasedir)
DBTempDirectory (default is C:\Windows\System32\CertLog, change it to your new databasedir)

6. Start the certification authority again by running net start certsvc from the commandline or by right clicking the AD Certification Services service and choosing Start. From this moment your DB and log should be running from the new location.

7. Verify it is running from the new location. You can do this by opening up the certification authority MMC. Right click on the name of your CA and choose Properties. Choose the tab Storage. The tab should look like this, with the location of your DB and Logs on a perhaps different drive/letter.

Hope this helps.


Stefan Hazenbroek