If you are applying Software Updates through a Task Sequence check this out…
There are file types that IIS will by default reject download attempts, typically this isn’t an issue as the rejected file types are Resource Type files such as .config, .vb, .vbproj, .mdf.
In all my years as a System Center admin, I have only run into two (2) file types that I normally have to Allow, that is .config and .mdf.
This is due to .Net applications or Access Applications not being packaged into CAB Files and having a <ExecutableName>.exe.config or Access Database contained within the Source Media.
It is easy enough to resolve this problem if you know where to look. In IIS 7.5 (Windows Server 2008 R2) you can manage the Request Filtering right from within the UI.
On each of your Distribution Points, launch Internet Information Services (IIS) Manager and navigate to Sites | Default Web Site Under IIS category double click on Request Filtering. From here you will find the extension that is being blocked. Right click on the extension and select Remove.
I normally add it back with an Allowed = True so that it is obvious that I made this change.
I recently ran into a problem where an application could not be downloaded to a client.
Upon investigation I discovered that the Source Media contained files that had a Plus (+) sign in the file name, by default IIS won’t \ can’t deal with this and you end up with a “404 File not found” error.
If you enable Double Escaping on the Distribution Points then IIS can deal with the plus sign and the file can be downloaded.
appcmd set config /section:requestfiltering /allowdoubleescaping:true
Be aware that this does reduce the security of your IIS Server, and your distribution point may be vulnerable to malicious URL’s. Since this is only a Distribution Point, this should be a minor issue.
This post started as a local copy of http://powersheller.wordpress.com/2012/08/29/sccmmdt-2012-task-sequence-to-restore-user-migration-from-smp-using-computer-association-recovery-information/ however I have since modified it to suit my style of deployment. So I am giving credit to the post that I got me to where I am today.
Problem: You need to restore user migration data from the State Migration Point (SMP) to a computer other than the destination computer specified in the Computer Association in the System Center 2012 Configuration Manager (SCCM) database.
Solution: The most effective solution is to build an SCCM/MDT task sequence that uses the UDI Wizard to prompt for the recovery information (state store location and state recovery key), connect to the SMP share with a dedicated service account and execute the loadstate command to restore the data on to the machine.
Advantages to this solution:
- A service account is used to access the SMP share, so you don’t have to grant permissions to technicians/users.
- The task sequence is run in the system context, so local administrator rights are not needed on the client.
- You can specify a consistent loadstate command with logging.
- The process is overall more secure, robust, traceable and easy to use.
This solution uses the Build Your Own Page feature in the UDI Wizard included in MDT 2012 Update 1.
ThinkVantage Technologies Administrator Tools
Free ebook: Microsoft System Center: Configuration Manager Field Experience
Free ebook: System Center: Designing Orchestrator Runbooks
Free ebook: Microsoft System Center: Troubleshooting Configuration Manager
Here is a neat article on how to wash Drivers before importing them into ConfigMgr.