2 questions about deployments and collections

Hello all. OK still new to 2012 but I have questions.
1. Once I create a collection and assign a deployment to it, is there a way to remove the deployment without removing the collection?our help
2. If I deploy an app via a collection but later want to remove the app from the client do I have to create a new collection and assign the deployment and set to uninstall or is there an esier way?
 
thanks for your help
 
-DW

dwilson11


Hello all. OK still new to 2012 but I have questions.
1. Once I create a collection and assign a deployment to it, is there a way to remove the deployment without removing the collection?our help
2. If I deploy an app via a collection but later want to remove the app from the client do I have to create a new collection and assign the deployment and set to uninstall or is there an esier way?

thanks for your help

-DW

hey DW.
1. Absolutely. if you highlight the collection, along the bottom of your screen you'll see different tabs - one being deployments. Click that tab, right-click the deployment you want to remove and delete it. Once you create a collection, you shouldn't ever have to delete it unless the collection is no longer useful to you.
2. Are you talking about true App deployment or did you deploy an application through package deployment? That's 2 different deals in 2012.
If it's a package deployment, make sure you delete the install package, then advertise the uninstall program.
 
Hope this helps...
 

Question 1 Resolved. Thanks
Question 2 so it sounds like for every package i create i should create 2 one for install one for uninstall
I saw that on the properties on the deployment there is a greyd out box to select install vs uninstall. If it was not i could just change the deployment on the fly

Well, when you create a package, it can have multiple "programs" that all use the same source files. that's why there is a "programs" tab at the bottom when you highlight a package. so, yes, create a install and an uninstall "program" in every package - which usually turns out to be a simple change in your CMD line running for the program.
 
Know what I mean?
Read this for further understanding http: //technet.microsoft.com/en-us/library/gg699369
 
And please score my post so I can post links! (stars on the right)