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

Hi,

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 http://support.microsoft.com/kb/2345451 and install it on the SQL server used for hosting the Site Database and Reporting Services.

Hope this helps.

Regards,

Stefan Hazenbroek

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

Hi,


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.


Workaround
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.

Regards,

Stefan Hazenbroek

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.

http://support.microsoft.com/kb/978754

Remember, this is not applicable on Windows Server 2008 R2 but only for windows Server 2008.

Hope this helps.

Regards,

Stefan Hazenbroek

ConfigMgr: AD Permissions for Domain Join Account

It's a good practise to use a service account for any sort of automated task, and this is no different with SCCM Operating System Deployment.

SCCM OSD has the capability of automatically adding a workstation to the domain during the Task Sequence, so the amount of work that needs to be done by hand is kept to a bare minimum. You use a service account in SCCM that has the permissions to add the computer to the needed OU, but what permissions do you need exactly?
Well, at a minimum you'll need the following permissions:




I hope this helps, I know I'll be back when I need it set again :)

Regards,

Stefan Hazenbroek

ConfigMgr: Software Update Point - The server name or address could not be resolved

The first thing I recommend costumers who are using SCCM is: Install the ConfigMgr Admin Console on a management server and keep your hands off the site server. This way when you accidentally fire up a script that contains a reboot, it'll restart your management server and not your site server. Also, when using it like this it'll keep your site server cleaned up and tidy, which is always something you'd want.

However, when this is the case and you're using a proxy server this also brings along some issues. When trying to download the updates you can run into the following error:

The server name or address could not be resolved

It took me a while to figure this one out, but it's quite easily fixed. Open up internet explorer and go to Internet Options. Now, go to Connections and choose Lan Settings. Fill in the same proxy server, so you can resolve internet addresses without issues. Close and re-open the ConfigMgr Admin Console and try to download the updates again. As you can see, the error is gone.

Hope this helps.

Regards,

Stefan Hazenbroek

ConfigMgr: The process is not in background processing mode.

When trying to provision updates using the ConfigMgr Console of System Center Configuration Manager 2007 (R2 SP2 in my case, but it also applies to earlier versions) you can get the following error in the process screen of the Update List Wizard.

The process is not in background processing mode

Now what? Background processing mode makes you think it's because of BITS being used. Well, you're right. This is the way you can resolve this issue.

1. Login to your WSUS Server.
2. Stop the BITS Service (through Services.msc or net stop bits at a commandline)
3. Stop the Automatic Updates Service (through Services.msc or net stop wuauserv at a commandline)
4. Browse to: Documents and Settings\All Users\Application Data\Microsoft\Network\Downloader

Note: If you're using Windows Server 2008 or Server 2008 R2 the Application Data folder is a junction point which has deny list permissions set to Everyone. If you need to be able to browse this folder you need to remove these NTFS permissions.

5. In the \Downloader folder delete the files qmgr0.dat and qmgr1.dat. These files will be recreated once you start the BITS service.
6. In the C:\Windows\ directory delete the folder SoftwareDistribution This folder will be recreated once you start the Automatic Updates service.
7. Start the Automatic Updates service using services.msc or by using net start wuauserv
8. Start the BITS service using services.msc or by using net start bits
9. Go into the ConfigMgr Console and go to Software Updates and right click on Software Repository. Choose Run Synchronisation.

Now you're able to download the updates again. I hope this helps.

Regards,

Stefan Hazenbroek

ConfigMgr 2007 R2 SP2: Windows Server 2008 R2, WSUS 3.0 SP2 on Site Server

And we have another one!

In my testlab I have WSUS setup on the same server as the SCCM Site Server. However, when trying to setup the Active SUP I got the following error in the WSYNCMGR.log

SMS WSUS Synchronization failed. Message: WSUS server not configured. Source: CWSyncMgr::DoSync. The operating system reported error 2147500037: Unspecified error

From this message it looks as if WSUS could not be contacted, but the WSUSCtrl.log states that all connections to the WSUS server are succesful. After searching around it seemed that this issue was due to the fact of WSUS and the SCCM Site Server being on the same machine. The fix is as follows (also check out http://support.microsoft.com/kb/896861 for more information (choose Method 1)):

1) Fire up regedit.
2) Go to HKLM\System\CurrentControlSet\Control\LSA
3) Create a new DWORD value called DisableLoopbackCheck
4) Edit the value and in the Value Data box type 1
5) Close regedit
6) In the SCCM Console right-click on Update Repository and check the WSYNCMgr.log for any issues.

In my case this fixed my issues.

ConfigMgr 2007 R2 SP2: Windows Server 2008 R2 and Management Point

I've been reinstalling my testenvironment to support Windows Server 2008 R2 instead of Windows Server 2008, but while installing SCCM 2007 R2 SP2 I ran into the following problem:

SMS Site Component Manager failed to install component SMS_MP_CONTROL_MANAGER on server.

The WebDAV server extension is either not installed or not configured properly.
Solution: Make sure WebDAV is installed and enabled. Make sure there is an authoring rule that allow “All users” read access to “All content”. Make sure the WebDAV settings “Allow anonymous property queries” and “Allow property queries with infinite depth” are set to “true” and “Allow Custom Properties” is set to false.

Now what? I am 100% sure I have the correct settings in WebDAV (according to the log also) but it doesn't seem to recognize it. After doing some searching on the internet I found the location of the configuration file of Webdav. This file is located in: C:\Windows\System32\inetsrv\config\schema\WebDAV_schema.xml. After opening this file up I noticed that the settings in this file were different from the settings I changed in the IIS Manager.

The settings were configured as:

<attribute name=”allowAnonymousPropfind” type=”bool” defaultValue=”false” />
<attribute name=”allowInfinitePropfindDepth” type=”bool” defaultValue=”false” />
<attribute name=”allowCustomProperties” type=”bool” defaultValue=”true” />

However they should be:

<attribute name=”allowAnonymousPropfind” type=”bool” defaultValue=”true” />
<attribute name=”allowInfinitePropfindDepth” type=”bool” defaultValue=”true” />
<attribute name=”allowCustomProperties” type=”bool” defaultValue=”false” />

After correcting these settings (remember you have to take ownership of the file to be able to change it) and restarting the World Wide Web Publishing Service and the SMS_SITE_COMPONENT_MANAGER the Management Point gets installed correctly. You can check if the installation is succesful in the logfile MPSetup.log in your SCCM\Logs directory. If succesful the log looks like this:

<01-16-2010 22:08:36> ======== Completed Installation of Pre Reqs for Role SMSMP ========
<01-16-2010 22:08:36> Installing the SMSMP
<01-16-2010 22:08:36> Passed OS version check.
<01-16-2010 22:08:36> IIS Service is installed.
<01-16-2010 22:08:36> checking WebDAV configuraitons
<01-16-2010 22:08:37> WebDAV is configured
<01-16-2010 22:08:37> No versions of SMSMP are installed. Installing new SMSMP.
<01-16-2010 22:08:37> Enabling MSI logging. mp.msi will log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log
<01-16-2010 22:08:37> Installing C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\mp.msi CCMINSTALLDIR="C:\Program Files (x86)\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files (x86)\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<01-16-2010 22:08:57> mp.msi exited with return code: 0
<01-16-2010 22:08:57> Verifying CCM_CLIENT virtual directory.
<01-16-2010 22:08:57> Website path is IIS://LocalHost/W3SVC/1.
<01-16-2010 22:08:57> Connecting to IIS.
<01-16-2010 22:08:57> CCM_CLIENT is currently C:\Program Files (x86)\Microsoft Configuration Manager\Client.
<01-16-2010 22:08:57> Installation was successful.

One last thing. When creating a backup of the WebDav_schema.xml, do not create the backup in the same directory as the original file. All .xml files put in this directory will be read by IIS so your settings will not seem changed afterwards.

Good luck, I hope this helps.

ConfigMgr: SMS Site Component Manager failed to reinstall this component on this site system.

Within a ConfigMgr environment it's possible you run into the following error when running SMS_SITE_SQL_BACKUP and the SQL Server runs on a remote system.

SMS Site Component Manager failed to reinstall this component on this site system.


Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the reinstallation in 60 minutes. To force SMS Site Component Manager to immediately retry the reinstallation, stop and restart SMS Site Component Manager using the SMS Service Manager.

I noticed this error at home (yes, I'm running ConfigMgr 2007 SP1 + R2 at home, call me crazy ;-)) and started looking around if there's a solution available. After finding no KB-article or anything about it I started searching on. The reason for this error seems to be that the SQL Server cannot bootstrap the executable to install the service on the SQL Server.

Luckily, the fix is quite easy. Go to the ConfigMgr installation directory, in my case

C:\Program Files (x86)\Microsoft Configuration Manager\

and open the file install.MAP with notepad. In this file you'll search for the following lines:

BEGIN_COMPONENT_FILELIST
<SMS_SITE_SQL_BACKUP>
<1193>
BEGIN_DIRECTORY
<bin\i386>
<9><X86><>
FILE <smssqlbkup.exe><1><766496>
END_DIRECTORY
BEGIN_DIRECTORY
<bin\x64>
<17\><AMD64><>
FILE <smssqlbkup.exe><1><1547296>
END_DIRECTORY
UNIT <SMS>
END_COMPONENT_FILELIST

Change these lines to the following

BEGIN_COMPONENT_FILELIST
<SMS_SITE_SQL_BACKUP>
<1193>
BEGIN_DIRECTORY
<bin\i386>
<9><X86><>
FILE <smssqlbkup.exe><1><766496>
FILE <srvboot.exe><0><219904>
END_DIRECTORY
BEGIN_DIRECTORY
<bin\x64>
<17><AMD64><>
FILE <smssqlbkup.exe><1><1547296>
END_DIRECTORY
UNIT <SMS>
END_COMPONENT_FILELIST

Afterwards restart the SMS_SITE_COMPONENT_MANAGER at the site server and after a minute or so reopen the Components log. After changing the install.MAP and restarting the SMS_SITE_COMPONENT_MANAGER I got the following happy message:

SMS Site Component Manager successfully reinstalled this component on this site system.

I hope this helps resolve some issues.