Category Archives: Uncategorized

When using explorer view or try to map a drive to SharePoint you are prompted for credentials when you don’t use a proxy

We have recently changed from using a proxy to not needing one. Once we unchecked use a proxy server from IE our drive mappings to SharePoint sites mapped via GPO stopped appearing. Also users who had mapped drives them selves were prompted to authenticate.

I had already assigned the SharePoint URLs to the Intranet Zone using a GPO. In order to get the WebClient service (this is the services that allows you to access WebDAV folders using explorer) passing the authenticated credentials on transparently(SSO) you need to create a registry entry to allow it.

1.Open Regedit
2. Brows to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
3.Create a new Multi-String Value
4.Name it AuthForwardServerList
5.Modify it, type the URL of the server that hosts the Web share including the protocol e.g. http:// or https://

You will need to apply this to all computers you want SSO to the share point document libraries using explorer. This can be achieved using GPO preferences under; Computer Configuration – Preferences – Windows Settings – Registry


If you are using a shortcut and the path looks like \\\DavWWWRoot\… and your SharePoint site is using SSL you need to update the shortcut to use @SSL after the server name – e.g. \\\DavWWWRoot\…


DFSR does not replicating files because they have been marked as temporary files

If you get the following error when running a DFS Replication validation report

DFS Replication does not replicate certain files in the replicated folders listed above because they have temporary attribute set, or they are symbolic links . This problem is affecting at least 3 files in 1 replicated folders (up to 100 occurences per replicated folder are reported). Event ID: 11004



You might need to change the flag on the files if in fact they are NOT temporary using the command below

Get-childitem “<PATH TO THE DATA>” -recurse | ForEach-Object -process {if (($_.attributes -band 0x100) -eq 0x100) {$_.attributes = ($_.attributes -band 0xFEFF)}}

More information can be found at

Some Useful SCCM OSD log file locations

  • Windows PE before HDD format: x:\windows\temp\smstslog\smsts.log
  • Windows PE after HDD format: x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
  • Full version Windows before SCCM agent installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
  • Full version Windows after SCCM agent installed: c:\windows\ccm\logs\Smstslog\smsts.log
  • Full version Windows (x64) after SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
  • After Task Sequence has finished running: c:\windows\ccm\logs\smsts.log
  • After Task Sequence has finished running (x64): c:\windows\sysWOW64\ccm\logs\smsts.log

Post SCCM 1511 upgrade problems

After our SCCM upgrade from 2012 R2 SP1 to SCCM 1511 applications, OSs etc would not deploy.  The client would sit at 0% downloading.

If you clicked “update content” on the installer within the SCCM console it would then install on the client. Investigating further I found the following error in the DataTransferService.log on the client

 <![LOG[[CCMHTTP] ERROR: URL=http://<DP SERVER NAME>:80/SMS_DP_SMSPKG$/Content_53b51003-972a-41a7-bc75-0a22b18ceaef.1, Port=80, Options=480, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE]LOG]!><time=”09:13:45.837+00″ date=”02-10-2016″ component=”DataTransferService” context=”” type=”1″ thread=”5284″ file=”ccmhttperror.cpp:291″>

This highlighted that the file could not be found on the web server. I checked the file location in IIS on the DP, it was pointing to E:\SMSPKGSIG – as expected the file it was trying to download did not exist. 

To find the application that went with this Content ID I sued the following PowerShell script on the DP/Site server (I cannot remember what website I found this script on so apologies to the author)

$SiteCode = ‘Site Code’

$ContentID = ‘Content_53b51003-972a-41a7-bc75-0a22b18ceaef.1’

#Get-WmiObject -Namespace root\sms\site_$SiteCode -ComputerName $Server -Class SMS_Deploymenttype

Get-WmiObject -Namespace root\sms\site_$SiteCode -Class SMS_Deploymenttype -Filter “ContentID = ‘$($ContentID.Split(“.”)[0])'” | Select LocalizedDisplayName -Unique

I validated the application on this DP and it failed and suggested redistributing. This did not resolve the problem but in the distmgr.log file on the site server hosting the DP role I found this error

 RDC:Failed to copy package content signature file \\?\C:\SMSPKGSIG\Content_53b51003-972a-41a7-bc75-0a22b18ceaef.1.tar to \\<SERVER NAME>\SMSSIG$\Content_53b51003-972a-41a7-bc75-0a22b18ceaef.1.tar. Error 2

The strange thing was, the SMSPKGSIG directory should be on the E drive for our server(as set in IIS). When I check the c:\SMSPKGSIG directory I found the Content_53b51003-972a-41a7-bc75-0a22b18ceaef.1.tar file.

 It would appear after upgrading the DP has changed its location for the SMSPKGSIG & SCCMContentLib directories and is now looking for them on the C drive & E Drive.

I used the ContentLibraryTransfer.exe tool from the ConfigMgr 2012 Toolkit R2 with the following command to transfer the library back to the E drive.

ContentLibraryTransfer.exe -SourceDrive C -TargetDrive E

I then revalidated the content of the failing package on the DP and it passed.

I scheduled a validation on all content – this should have already been on as it is on our other DPs

All Applications and OSs are now deploying again.

Hope this helps someone else as this caused massive head scratching!

Active sync issue when published via MS Web Application Proxy

Exchange 2013 CU7

If you are getting this error on the CAS servers

[Eas] The number of outstanding requests for guard TargetBackend(“servername”) has exceeded the max limit 150. Current request will be rejected.

And this error on the Microsoft Web Application Proxy

The HTTP response from the back end server was not received within the expected interval. Expected interval: 300 seconds.


Reference here 

  • On all CAS servers:

    In \Exchange Server\V15\FrontEnd\HttpProxy\sync\web.config, add this key in the <appSettings> node.

    <add key=”HttpProxy.ConcurrencyGuards.TargetBackendLimit” value=”5000″ />

    In \Exchange Server\V15\FrontEnd\HttpProxy\rpc\web.config, add this key in the <appSettings> node.

    <add key=”HttpProxy.ConcurrencyGuards.TargetBackendLimit” value=”5000″ />

    After this change recycle the MSExchangeSyncAppPool and MSExchangeRPCProxyAppPool in IIS manager.

    After this, we stopped getting Event ID 2002, and all Connection_Dropped_Event_List_Full stopped appearing in Httperror logs.