September 15 2011

SCCM clients not downloading content from DPs

I’d been looking at an issue where SCCM clients were constantly waiting for content from a local DP even though I had confirmed the content was present and accounted for on the local DP disk (my DP are running Windows Server 2008 R2 which is IIS 7.5). I checked the IIS logs on the local DP and found an interesting line, something like:

HEAD /SMS_DP_SMSPKGD$/APH000CC//filename.config - 80 - Microsoft+BITS/7.0 404 7 0 15

The ‘404 7’ section was interesting because this is a HTTP status code for ‘404.7 – File extension denied’ – according to http://support.microsoft.com/kb/943891.

I found a few articles via Google mentioning this problem and that I should edit the %windir%System32inetsrvconfigapplicationHost.config file to allow the .config file type. This didn’t seem to fix the problem for me. After adjusting this and restarting IIS, when I looked in the IIS management GUI in the Request Filtering section, the .config extension was still blocked. I needed to change the HTTP request filters because by default in IIS 7.5 there are a list of file extensions that IIS will not provide to clients via WebDav. This included the ‘.config’ file type which I needed to deploy as part of an application package.

I didn’t want to manually do this via the GUI on all of my DPs so I used the appcmd.exe command and then restarted IIS:

%WinDir%System32InetSrvappcmd.exe set config "Default Web Site" -section:system.webServer/security/requestFiltering /-"fileExtensions.[fileExtension='.config']"

This did the trick – my clients then downloaded the content from their local DP including the previously problematic .config files.

For more info see some of these links:

 
 



----------------------------------------------------------------------------
I use a maximum of one Google Ad per post to help offset some of my blog hosting costs.

----------------------------------------------------------------------------

September 6 2011

Remote control in WinPE

Fresh from my recent trip to TechEd, I learnt about a way to remotely connect to a WinPE session using a new Microsoft tool called Dart. For more info on this tool, see here – http://www.deploymentresearch.com/Blog/tabid/62/EntryId/36/Software-Assurance-Pays-Off-Remote-Connection-to-WinPE-during-MDT-SCCM-deployments.aspx .

This prompted me to think what organisations without Microsoft software assurance (MDOP) can use for remote connection to WinPE. I successfully configured and used TightVNC version 2.0.2 with WinPE 3.0 (x86) in my environment. Take a look here and here for more hints on how to do this. I used the same method to get BGInfo to run at WinPE startup.

 
 

September 5 2011

Tool for pinging multiple hosts

I came across a great tool called Ping Them, great for pinging multiple hosts. See http://blogs.microsoft.co.il/blogs/doli/archive/2011/08/17/free-tool-ping-them.aspx for more details.

This is similar to a Powershell script of mine over here – http://blog.danovich.com.au/2009/06/10/nifty-powershell-script-to-ping-multiple-servers/ – but this new tool adds a great GUI and some additional functionality.