Deleting a deployment without a Software Update Group

I deleted a Software Update group prior to removing the deployment attached. I am not unable to remove the deployment nor recreate the deployment with the same name through the Config Manager.
Is there a was to remove the deployment package?
Thanks.

I deleted a Software Update group prior to removing the deployment attached. I am not unable to remove the deployment nor recreate the deployment with the same name through the Config Manager.
That should also have removed the deployment of the software update group then.
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

Deployment Package vs Right-Click, Deploy directly from Software Update Groups?

I'm not sure I understand the difference between collecting updates into a group and then just using right-click to create a deployment from within Software Update Groups?
One thing I did notice this morning, is that if I want to distribute that content to other DPS, I have to create deployment package first? Are there other reasons for not simply deploying from within Software Update Groups?
Thank-you

Update Groups *group* updates together. That's it, they have no additional functionality.
Updates can be deployed individually or as groups (in the form of Update Groups) -- it would be pretty painful to manually deploy every update individually so that's why there are update groups.
Update Packages (I don't like calling them deployment packages even though that's what they're labeled as in the console because they have nothing to do with deployments) make update binaries available to the clients.
Update Groups have nothing to do with Update Packages. Update Groups contain references to updates, update packages contain binaries. Deploying an update or update group assigns those updates to the client within the collection specified. Clients that have
an update assigned that is also applicable will download the binary for the update from any available update package and install it.
You create an update package by right-clicking on an update or update group and choosing download. The wizard offers you a choice between using an existing package or creating a new one. You cannot directly create on.
Secondary sites have nothing to do with this process whatsoever. Clients are clients are clients regardless of where they are located. As long as they are within t he collection targeted by the deployment and they have access to the assigned update binaries
in an update package, they will download and install the updates properly.
Jason | http://blog.configmgrftw.com | @jasonsandys

Change deployment package for software updates

Hi there
Currently we have different deployment packages and software update groups based on year, product, etc.
In the near future i'd like to rearange our software deployment process in configuration manager 2012:
1x Deployment Package for all updates
1x "Full" Software Update Groups with all updates in it. Additional to that we'll create a "Diff" Software Update Group at the Patchday and merge the updates later via edit membership in the "Full" Software Update Group.
Are the following steps which i would perform correct?
1. Select all updates which are deployed and not expired and not superseeded
2. Create a new Software Update Group "Full"
3. Select the new Software Update Group --> Download --> Create my new deployment package
4. Deploy the new software update group to my collections
5. Delete the obsolete software update groups / deployment package
6. Delete the old updates source folders on our filer.
I current don't know if the redownload process let the updates "forget" the old deployment package. With the above described steps i should get rid of all expired and superseeded updates.
Thanks for any advice :-)
Regards,
Simon

That is correct they only receive and install the updates they require, but don't confuse the metadata and deployments with the updates themselves. They will still receive the metadata and the policies for every update you deploy to them and that's where
the problem lies. Each and every update assigned to a client (using a deployment) has it's own policy which of course must be downloaded by the client and stored in WMI causing the bloat. Note that I haven't experienced this first-hand but am relying on the
accounts of others here in the forums but to me, if there is any chance of this being an issue, I would avoid it.
For Update Groups, just a few categories is sufficient to break things up and I typically do three: workstations, server, office. These are often on different patching schedules anyway so it makes sense to have three separate ADRs for them anyway.
For packages, I typically organize based on the calendar creating a new package every 3-6 months with the package containing all updates. There's really no need to divide the package up by product unless you have DPs dedicated to a specific product. Note
that pre-R2, to change the package an ADR referenced you had to use PowerShell -- it's been added into the GUI in R2 though.
Jason | http://blog.configmgrftw.com

Software update group question

I did my June updates in June seems to pushing updates fine but now I look at the JUNE update group and the icon looks like this and I know it is not finished updating all workstations. Is there a setting to keep it active longer?
MSB

Also, the icon simply indicates that the group itself contains at least one expired update. This does not in any way affect the deployment of the software update group as a whole or the other updates within the group -- they will still be deployed normally.
Only the actual update(s) that are expired will not be deployed.
Jason | http://blog.configmgrftw.com

Deploying one software update group to multiple collections.

Good Afternoon,
We are in the process of rolling out Windows updates to our server environment. This will be the first rollout on a mass scale. Previously, we have rolled out to about 4 collections to test.
In a prior life, I managed deploying Windows updates using SCCM 2007. You were able to target to a deployment to a parent collection and select the option to deploy to sub-collections.
With CM2012, we have a parent folder and our collections live inside of this folder. My question is this, how can deploy my software update group without having to create a deployment targeted to each individual collections. Our structure looks
like this
Parent Folder (Production)
Subfolder (Monthly)
Monthly Collections
We have 43 monthly collections for production. I would prefer to not have to create 43 different deployments. Can you target the parent folder and include the collections? I read another article where CM2012 did away with the use SubCollections,
but I have not been able to verify that.
Any assistance would be appreciated.
Thank You
Brian Dougherty

You can still do something similar as with a top collection in CM07. In CM12 you can use the include collection. So that would mean that one collection can include multiple collections, which allows you to target only one collections. Those separate collections
can then be used for different maintenance windows (or whatever you want to do with it).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

How can I tell what Software Update Groups are members of Deployment Packages?

I have a single SCCM 2012 SP1 CU4 server running on Windows Server 2012.
I am trying to clean things up a little bit and I am curious:
How can I tell which Software Update Groups use
which Deployment Packages? I don't see it on the Properties of either one.
Thanks!

Funny thing is that you can't see from the software update (in the software update group) in which deployment package(s) it exists. Your only options are manually comparing every single update (not really an option), or use PowerShell and do something
like this:
http://myitforum.com/myitforumwp/2014/05/12/matching-configmgr-software-updates-to-a-deployment-package-with-powershell/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2012 SP1 - PowerShell command to create a software update group deployment DISABLED by default

Hello,
I create deployment jobs using new Powershell cmdlet "Start-CMSoftwareUpdateDeployment". However it looks there is no way with this cmdlet to create a job which is disabled by default.
Is it possible ? As an alternative, which cmdlet could I use to manage enable/disable job state ? I have not found anything so far.
Regards.
Sylvain

hi, i tried the solution to create a deployment using http://cm12sdk.net/?p=2014 link.
it creates deployment but it is not downloaded so a red cross sign is shown in front of software update group. can you guide me on which command to use to download software update after which we can try the script mentioned in the link.
thanks.

Added additional update to software update group, do I need to deploy it?

Hi,
I am fairly new to SCCM and I am not sure about this. Couple days ago I downloaded some windows updates and placed them into a software update group 2015Clients and created the required deployments. So today I found an additional update that needed
to be added to this update group 2015clients. So I downloaded the additional update and it was placed into the 2015Clients deployment package. My first question is why is it in the deployment package 2015Clients and not in the software update group 2015Clients
as well? Second question, the new update that is now in the deployment package group says that it is not deployed like the other updates do. Do I need to deploy this new update? I was confused because when I tried to deploy it using the same deployment name
as the other updates it wants me to use a different name. TIA

Downloading an additional update doesn't directly add an update to an update group. Those are two separate things and by that two separate actions. There is no direct link between an update group and a deployment package.
The deployed update group tells the client which updates it should install and the deployment package is the method to make the content of the update available.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Modifying a Software Update Group Deployment via PowerShell

Good Morning Guys -
Recently, I created numerous Software Update Group (SUG) advertisements to a variety of collections using a PowerSHell script I wrote. It used the cmdlet "Set-CMSoftwareUpdateDeployment" which is described by Microsoft as "Modifies a
software update deployment in Configuration Manager." Below is the command I used for the advertisement I'm using as an example here:
Start-CMSoftwareUpdateDeployment -SoftwareUpdateGroupName "Workstation Related - Mar 2014 Deployment" -CollectionName "Workstation Patch Management - Window #5 - 3rd Monday - Auto Restart" -DeploymentName "Workstation Patch Management - Window #5 - 3rd Monday - Auto Restart" -DeploymentType Required -VerbosityLevel OnlySuccessAndErrorMessages -TimeBasedOn UTC -DeploymentAvailableDay 2014/3/17 -DeploymentAvailableTime 5:00 -DeploymentExpireDay 2014/3/17 -DeploymentExpireTime 5:00 -UserNotification DisplaySoftwareCenterOnly -SoftwareInstallation $False -AllowRestart $False -RestartServer $False -RestartWorkstation $False -ProtectedType NoInstall -UnprotectedType NoInstall
What I'm needing to do, though, is change many of these advertisements from "Required" to "Available" using PowerSHell again. Since it's described as "modifies," I assumed that I could run the exact same line used to create
the advertisement, except only change the "Required" string to "Available." The advertisement name is the same, so I thought it would work.
When I ran it, it simply created another advertisement with the same name:
Am I doing something incorrectly when trying to modify the advertisement or is what I've trying to do even possible with this cmdlet? If not possible, any suggestions you have as to how I could do what I'm trying to do on a large scale would be appreciated!
Thanks!
Ben K.

I just tried on a required deployment:
set-cmsoftwareupdatedeployment -softwareupdategroupname "My Group Name" -deploymentname "My deploymentname" -collectionname "my collection name" -deploymenttype "available"
And it changed to Available. Not sure why that isn't working for you.

Software update group - Superseded updates

Hi all,
I need to understand something. I have Software Update Group and it has a deployment configured . When a given update becomes superseded and I remove it from the software update group, how does this affect the configured deployment? I don't
want to delete/recreate the deployment. Will the deployment automatically update itself and remove the update that I removed from the Update Group, will it still try to deploy the upddate...wil it give an error...etc.
Thanks in advance,
Jesmat.

The deployment is for the updates in the software update group. For currently targeted devices it will need a machine policy update before they know about the change.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

I can not update a Windows Server 2008 R2 with Software Update Group in SCCM2012

Hi all,
I got some problems with update deployments these days.
I try to configure SCCM2012 to update 1 Windows Server 2008 R2 (with Hyper-V / This server is in a cluster)
Actually i've 4 other Hyper-V servers and i would like to add one more in the cluster called Hyper-V5. To do that i need that all Hyper-V servers use the same Windows Updates.
I created a collection for my Hyper-V servers and then a Software Update Group with all needed updates (checked the list of another HV-Server).
I did a deployment on this collection using this new Software Update Group.
I checked the Sofwtare Center's logs on the Hyper-V5 server and i saw that synchronization has a successfull state.
But there is no updates installed or displayed in Sofwtare Center.
Here is some screenshots : Oh no i can't post image because ... "Body text cannot contain images or links until we are able to verify your account." waiting to be verified since months.
Thanks for your help.

Hi,
Have you try to run Software Updates Scan Cycle and Software Updates Deployment Evaluation Cycle Actions on the client? Please check ScanAgent.log and PolicyAgent.log to see whether the client received the updates deployment policy.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Collections based on Software Update Group compliance

Hi!
Is it possible to create a collection based on software update group compliance? This is for software update groups which are
not deployed, they are just monitor groups (for example, groups for yearly or quarterly software update compliance).
I would like to create a collection that lists all devices which are non-compliant in software update groups with names like "%Client Updates" - is this possible?
The reason for this is so I can impose some stricter Compliance Settings (among some other stuff) on devices that are not compliant.
I looked around a bit, but I could not find anything that I can use. Even Google couldn't solve my question :/

you can try something like this:
This collection is basically sub selected query get list of computers that do not have specific assignment enabled.
select * from SMS_R_System where SMS_R_System.ResourceId not in (SELECT distinct SMS_UpdateComplianceStatus.MachineID FROM SMS_UpdateComplianceStatus JOIN SMS_UpdateDeploymentSummary ON SMS_UpdateComplianceStatus.CI_ID = SMS_UpdateDeploymentSummary.CI_ID
WHERE SMS_UpdateDeploymentSummary.AssignmentName like "%Client Updates%")
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr

What Changes to Software Update Group Causes Clients to Re-check Compliance

Hello,
I have a number of software update groups that have been deployed over the past couple of years. When Microsoft release new updates etc. some of the updates already deployed change their status e.g. an update might get marked as expired. As a result of this
I can go from having clients reporting as being compliant to a situation where they are in an unknown state until they report back again.
Does anyone know what changes to an update already deployed would cause clients to have to check their compliance status for that software update group?
Thank you.
Stephen

If you are referring to the enforcement state, this is indeed specific to the deployment, not the group itself.
With regards to your question - Upon a change to your deployment, your clients will receive updated policy. On a successful evaluation of the deployment, it will re-send a state message if necessary. Unfortunately I do not know if there are certain
things that do not trigger a policy update (i.e. change in the name or description vs. update membership or deadline change)

SCCM 2012 Software Update Group Statistcs showing wrong Asset Count

Under Software Update Groups in the summary tab the statics section shows total asset count: 5. I only have this group deployed to only one collection with 1 machine.
I have a second Software Update Group in the summary tab the statics section shows total asset count: 5. I only have this group deployed to only one collection with 3 machines.
The two collection have only one machine in common.
I tried to run a summarization but these numbers are not updating.
where does the asset count come from and how do I get it to display correctly?
Thanks,

The asset counts shown in the console for software groups are not specific to any collection or deployment. If you want numbers specific to a collection, you need to use reporting or a console query.
Jason | http://blog.configmgrftw.com

All Software update groups expired

Hi,
Please see http://social.technet.microsoft.com/Forums/en-US/39b60e34-f30a-4963-a08b-6a8e13e44b91/software-update-groups-grey-icon-with-x-?forum=configmanagersecurity
for reference.
We created update lists for Windows 7 with Office, automatic updates for SCEP, they all are expired (Expired icon of “http://technet.microsoft.com/en-us/library/hh848254.aspx). I don’t want them to expire. I want to make sure every new
OS will get the latest updates + antivirus updates.
Not sure if this is by design, an error on SCCM (http://social.technet.microsoft.com/Forums/en-US/0c13c27d-55a9-4f56-8ac0-f9053301ab0c/all-updates-in-sccm-software-updates-are-set-to-expire?forum=configmgrsum=>
my SCUP is there) or there is some misconfiguration.
Please advise. J.
Jan Hoedt

Jan,
> *Can you help me with this mechanism, I'm not familiar with it?
While viewing the updates that are a member of the software updates group, either sort by the "Expired" column or filter by Expired = Yex. Select all expired updates, right click, and select 'Edit Membership". Uncheck the checkbox for the software
update groups you are trying to remove them from.
> *I seem to remember there was somewhere an option that mentioned expired
This option has to do with how long 'superseded' updates will remain available for deployment. You can set under Administration > Site Configuration > Sites. Right click on your site and select Configure Site Components > Software Update
Point. The setting is on the "Supersedence Rules" tab.
However, Microsoft will also directly expire updates from time to time as well. In general, this is normal and something you shouldn't worry about managing. When the update has been expired by Microsoft, it is something you couldn't install even
by going to Windows Update, so you shouldn't worry trying to deploy them. Instead, deploy the current updates instead of superseded ones.
>How can I automate this (not automatically apply but using manually which updates to use and deploy at times I choose)?
For organizations with very simple Software Update processes, you could use an Automatic Deployment Rule to select updates based on a criteria, download the content to a deployment package, add the updates to a software update group, and create a deployment
to a collection. That deployment can be 'available' and not required if you plan to hand install them later.
This documentation gives you an overview of how all the Software Update Management features work:
http://technet.microsoft.com/en-us/library/gg682168.aspx#BKMK_DeploymentWorkflows
And this blog post gives an example of using an ADR:
http://blogs.technet.com/b/configmgrdogs/archive/2012/05/08/configmgr-2012-automatic-deployment-rules.aspx
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you've found a bug or want the product worked differently,
share your feedback.
<-- If this post was helpful, please click "Vote as Helpful".

Deleting a deployment without a Software Update Group

Similar Messages

Maybe you are looking for