Wednesday, March 5, 2014

Dll, config file in SCCM packages cannot be distributed.

A package which I packaged for SCCM do not seem to be distributed to Distributions points after a couple of days despite re-packaging.
The package status remains at install pending for a extended period of time.
In my case my package contained a dll files.

It was found that this is due to configuration in the applicationhost.config file located on c:\windows\system32\inetsrv\config. TheDLL files are filtered by the distribution point.

To determine this issue, the following was done

1) Look at the IIS logs for on the source DP.

2) It was found that the http 500 was encountered for DLL file types

To resolve this issue, the below was removed from the applicationhost.config file
Look for the below <add fileExtension=".dll" allowed="false" /> in the file.
It should be found within the tag of <requestFIltering>

<fileExtensions allowUnlisted="true" applyToWebDAV="true">
<add fileExtension=".asa" allowed="false" />
<add fileExtension=".asax" allowed="false" />
<add fileExtension=".ascx" allowed="false" />
<add fileExtension=".master" allowed="false" />
<add fileExtension=".skin" allowed="false" />
<add fileExtension=".browser" allowed="false" />
<add fileExtension=".sitemap" allowed="false" />
<add fileExtension=".config" allowed="false" />
<add fileExtension=".cs" allowed="false" />
<add fileExtension=".csproj" allowed="false" />
<add fileExtension=".vb" allowed="false" />
<add fileExtension=".vbproj" allowed="false" />
<add fileExtension=".webinfo" allowed="false" />
<add fileExtension=".licx" allowed="false" />
<add fileExtension=".resx" allowed="false" />
<add fileExtension=".resources" allowed="false" />
<add fileExtension=".mdb" allowed="false" />
<add fileExtension=".vjsproj" allowed="false" />
<add fileExtension=".java" allowed="false" />
<add fileExtension=".jsl" allowed="false" />
<add fileExtension=".ldb" allowed="false" />
<add fileExtension=".dsdgm" allowed="false" />
<add fileExtension=".ssdgm" allowed="false" />
<add fileExtension=".lsad" allowed="false" />
<add fileExtension=".ssmap" allowed="false" />
<add fileExtension=".cd" allowed="false" />
<add fileExtension=".dsprototype" allowed="false" />
<add fileExtension=".lsaprototype" allowed="false" />
<add fileExtension=".sdm" allowed="false" />
<add fileExtension=".sdmDocument" allowed="false" />
<add fileExtension=".mdf" allowed="false" />
<add fileExtension=".ldf" allowed="false" />
<add fileExtension=".ad" allowed="false" />
<add fileExtension=".dd" allowed="false" />
<add fileExtension=".ldd" allowed="false" />
<add fileExtension=".sd" allowed="false" />
<add fileExtension=".adprototype" allowed="false" />
<add fileExtension=".lddprototype" allowed="false" />
<add fileExtension=".exclude" allowed="false" />
<add fileExtension=".refresh" allowed="false" />
<add fileExtension=".compiled" allowed="false" />
<add fileExtension=".msgx" allowed="false" />
<add fileExtension=".vsdisco" allowed="false" />
<verbs allowUnlisted="true" applyToWebDAV="true" />
<hiddenSegments applyToWebDAV="true">
<add segment="web.config" />
<add segment="bin" />
<add segment="App_code" />
<add segment="App_GlobalResources" />
<add segment="App_LocalResources" />
<add segment="App_WebReferences" />
<add segment="App_Data" />
<add segment="App_Browsers" />

3) Restart IIS
4) Monitor the DP

Thursday, February 27, 2014

Clipboard not working in Windows 2008 RDP Session

There maybe instances that you find that you are unable to use the clipboard operations in a Remote Desktop Session in Windows 2008.

To resolve the issue, please follow the below

 Ensure that the fDisableClip set to 0 under
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp

If fDisableClip is set to 1 rdpclip.exe will terminate, because clipboard mapping is disabled. Check that rdpclip is still listed under Addins

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Addins\Clip Redirector
Type REG_DWORD 0x00000003

Thursday, February 6, 2014

Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted.

You may encounter the below in Windows 2003 Servers when attempting to perform gpupdate to refresh the group policies

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1054
Computer: SERVER
Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted.
For more information, see Help and Support Center at

To overcome this:
Create the registry keys as below and restart the server
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]