mcarriere893
Posts: 3616
Score: 300 Joined: 4/12/2002 From: Manitoba, Canada Status: offline
|
Might not like this, but deployments, and deployment packages are not actually linked together. Paraphrasing the documentation: Clients install updates in a deployment by using any DP that has the updates available (regardless of deployment package). So, even if you delete a deployment package, if the update is still in another deployment package (and is on a DP that a client can access), that client will install it. When the last deployment package is delete that contains an update in a deployment, then, clients will not be able to (obviously) retrieve the update in the deployment. K, so you really have to (and it takes a little time playing in the lab) think of all these things as different /non linked items. One way to think if it is that you can create a deployment package with tons of updates. So these updates are now all sitting on DP(s), and so when you create a deployment, you select the updates you want (doesn't have to be all the updates in the deployment package), and are good to go. You don't have to do a deploy and a deployment package together. To see what updates you are deploying, you need to look at each deployment. To see what updates are in a deployment pacakge, you need to look at each deployment package. Try to think of creating deployment packages per month, and then name them as such instead of naming the deployment package and deployment the same.
_____________________________
Mark Carriere Microsoft MVP-SMS www.SMSUG.ca
|