I’m living out of a hotel room this week, so I get pretty bored at night. This is good news for everyone other than me! It means I have the time to write ConfigMgr scripts I had been planning for awhile. Tonight’s script is one that allows you to create collections and deployments from applications! Yea yea, I’ll get to the import applications script soon enough…
This script gives you the ability to quickly create install collections for your applications. Features:
- Create one application and deploy all selected applications to it, or one collection per application
- Quickly select the DP or DP groups you want the content in (You only need to select one DP or one DP group, or you can select ones from both columns!)
- Collections are automatically named the name of the application, but you can put a prefix in to help identify the collection
- Move the collections to a folder (Folder will be created if it doesn’t exist)
- Set the limiting collection
- Works on user or device collections
- Gives you all the options anyone cares about for the deployment settings.
- This will only work for NEW collections. This is to protect you!!!
- It will fail on any application that does not have content. There is a bug in Start-CMApplicationDeployment that makes it so you can’t start a deployment on an application with no content.
- There might be a lot of red in your console window from the tool starting content transfers. I made the decision to not check if content is already on a DP before running the cmdlet to add it to the DP. This should not cause any problems, though your console window will be very red.