Share This Post

USMT 4.0 and unconditionalExclude

Was recently working on a custom.xml for a client with USMT 4.0 and was struggling with getting my exclusions to work. My syntax appeared to be correct, however it wasn’t excluding the music file extensions I had created like it was supposed to. It was excluding them on the drive, but not on the desktop where I had placed some files to test.

After some searching, I came across this great blog post:

After reading through that post, I realized I had the incorrect syntax in my custom.xml. My context was set to context=”System” instead of context=”UserAndSystem”, doh! After making that change and testing, I finally got the behavior I was expecting. Mind the details!

So be sure to read the above link for the following issues.

Common cause 1: Your XML uses exclude and not unconditionalExclude
Common cause 2: You have set unconditionalExclude in the wrong context
Common cause 3: You have not correctly provided the case for unconditionalExclude

Share This Post

I am a Microsoft MVP for System Center Configuration Manager and owner of Nackers Consulting Services, LLC. I focus primarily on System Center Configuration Manager and the Microsoft Deployment Toolkit. In addition to helping clients leverage the technologies they use, I enjoy spending a lot of time on the forums and email lists helping answer questions and just seeing what people are doing with the deployment technologies available to them. I have spoken at Microsoft Management Summit on ConfigMgr/MDT integration and I have spoken at user groups around the country. If you have any questions, please feel free to contact me, I am always willing to help.

Leave a Reply