Automatic Deployment Rule - One ADR for Two Different Collection for Two Different time Intervals

I have a scenario where two collection of Windows 8.1 is made based on geographical location. One collection is for all the windows 8.1 machines in India and one collection is for all windows 8.1 machines in US. Now I have created one ADR to be deployed
to the Collection for Machines in India with a schedule.
My requirement is that can i use the same ADR for those two collection with different schedule. Say I want ADR to be deployed in India at say 10:PM IST and for US collection at say 10:00 PM PST.
Can I use one ADR with two different schedule and can be deployed to two different collection. Any help will be greatly appreciated.

Couple of "bits" to help you one your patch automation quest:
A ADR is very much a 1:1:1 rule. It creates (or updates) ONE update group, deploys it to ONE collection, and you can provide ONE schedule. While you are more than capable of flipping said deployment time to use local time instead of UTC, in general
it's a very simple set of rules that are dogmatically run.
That said because of the "include" feature of collections it's not that hard to setup a good/robust patching pattern. What I recommend doing is building an ADR for each variance of deployment of patches or enforcement time. for example,
my ADRs look something like this:
Software Updates - Zero day enforced
Software Updates - Critical and Security 1 month enforced
Software Updates - Critical and Security 1 month no reboots
Exact terminology is up to you of course, but I find a good descriptive ADR name saves a lot of confusion. For each ADR I create an identical collection. From there I can use existing collections and a simple "include collection" rule
to bundle things up and make them part of the patching schedule of my choice. Anyone can now go into my "software update" folder, look at my collections, and know exactly what gets patched by what deadline.
Finally, don't be afraid to look into maintenance windows to trim down ADR count. Making a deployment available for a month before it goes enforced, then setting up groups of maintenance windows (one for each Friday of the week for example) can also
accomplish a similar goal by having machines auto-patch during their week but you only using one ADR.
So by having two "types" of collections to manage your patching (one to assign a ADR built by deployment deadlines, the other for exact update windows) you should be able to group most your workstations into a decent patch scheudle without being
too excessive about creating a billion ADRs.

Similar Messages

SCCM 202 R2 - Automatic Deployment Rules

Hi all,
just got a question about the way in which the Automatic Deployment Rules work in SCCM 2012 R2. I've got a number of patching collections configured with different types of machines in (Pilot Group, Desktops, Test Servers, Prod Servers etc...) and was
hoping to set up a corresponding ADR for each of these collections.
Having had a quick test of the ADR, it seems to work well. When the Evaluation Schedule deadline hits, I see the updates are downloaded (watching RuleEngine.log) and then a new Software Update Group is created and is deployed to the machines
in the collection.
My question is, what's the best way to set up the ADRs to patch these collections? Does each patching collection need it's own ADR? If so, does this mean I will end up downloading the same updates multiple times since most of the ADRs will have the
same Products/Classifications selected?
Realise this is probably a fairly simple question but can't quite get my head round it so any help/info would be much appreciated!
Cheers

There really are three possible strategies here:
- Use an ADR for each collection. This will of course cause duplicate update groups but will be fully automated.
- Use a single ADR for each OS type; e.g., one for workstations and one for servers. Then manually add deployments to the appropriate ADR for each collection. This requires a bit of manual intervention but its not much and offers a QA checkpoint.
- Use a single ADR targeting a master collection and then use maintenance windows to control deployment times to "sub-collections". This is fully automated as well but does require some manipulation of the maintenance windows on a month to month
basis.
I often do a combination of the above depending upon the exact needs of the environment.
Jason | http://blog.configmgrftw.com | @jasonsandys

Trying to comprehend the use of Automatic Deployment Rules

I am having a hard time trying to conceptualize ADRs. I would appreciate it if someone can let me know if I am on the right track here.
The way I see it is I can set up an ADR for every 2nd Tuesday of every month (Patch Tuesday) to run to build my initial deployment to a pilot test group. Then I have to build subsequent deployments after that since ADRs can only build one deployment (the
one for my pilot test group).
My question is, should an ADR be used only for a pilot test deployment and not a production deployment?
Thank you very much everyone, I appreciate your help

I thought during the wizard it allows you to specify which type of patches you want to deploy such as Security, etc?
You select the update filter and criteria in the ADR wizard:
http://blogs.technet.com/b/configmgrdogs/archive/2012/05/08/configmgr-2012-automatic-deployment-rules.aspx
An example scenario:
http://technet.microsoft.com/en-us/library/jj134348.aspx#BKMK_Step2
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

SCEP definition update through Automate Deployment Rule

Hi all. Got a question on deploying SCEP 2012 definition updates to client PC through SCCM2012 R2 by using Automate Deployment Rule. It looks like the client PC is not receiving the definition updates immediately. The ADR seems working
fine, it completed the synchronization successfully, no error on "PatchDownloader.log" and "ruleengine.log"; deployment folder got filled up with new definition updates. However, the client is not receiving the new SCEP definition
updates immediately, although I've configured ADR to install the update as soon as possible, yet nothing happens for the past 2 hours. I ended up launch the SCEP console on the client PC and then click the "update" button manually, and this
launch the update process. I just wondering how much time we need to wait for the SCEP definition update to apply onto the client PC. Microsoft seems release 3 - 4 definition update per day, I am afraid we might not using the latest definition
update due to the time waiting issue. Thank you.

I've configured the polling interval to take place every 3 hours. I guess this contribute to the waiting time. I will keep an eye on it to see if the definition in deed installs automatically.
Yes that's one of the delay which is the major Contribution also there would be some delay for the updates when they are downloading and getting updated to the distribution points. You can check the 'Content Status' for that package to verify if it got updated.
Umair Khan
Microsoft Support Escalation Engineer
Blog: http://blogs.technet.com/umairkhan
Facebook:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Automatic Deployment Rule - Error 5

Hello,
I'm experiencing an odd issue with setting up an automatic deployment rules. Everything looks like it's fine, but it's running into a permissions error on the location of the package. I enabled auditing and gave EVERYONE full access to the share and everything
runs fine and verify that my admin account is the one writing. When I remove EVERYONE and designate the admin account with full share and full security permissions it gives back error 5 for permissions. Any ideas?

An ADR runs with SYSTEM credentials and not with your admin credentials.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM Automatic Deployment Rule Schedule

Dear All,
I have SCCM 2012 R2 running on Win2008 R2 Sp1. When I create an automatic rule, and later on I decide to change the Deployment Schedule, it wont save the changes.
I wonder if this is some sort of bug.
Thank yoiu

Hi,
Could you reproduce this situation on the same site?(create a new Automatic deployment rule, then edit it)
How about on the another site with the same infrastructures?
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.

System Center 2012 Error on Automatic Deployment Rule

Good day,
I have created and Automatic Deployment Rule to deploy my EndPoint Protection updates. So far, I have been able to deploy the agents, and the Antivirus to all my network computers. The problem I have is when the update rule runs. I have checked the SMSProv.log
file, and this I what I get:
Execute SQL =select all SMS_AutoDeployment.AutoDeploymentEnabled,SMS_AutoDeployment.AutoDeploymentID,SMS_AutoDeployment.SecurityKey,SMS_AutoDeployment.Description,SMS_AutoDeployment.LastErrorCode,SMS_AutoDeployment.LastErrorTime,SMS_AutoDeployment.LastRunTime,SMS_AutoDeployment.LocaleID,SMS_AutoDeployment.Name,SMS_AutoDeployment.Schedule
from vSMS_AutoDeployments AS SMS_AutoDeployment where SMS_AutoDeployment.AutoDeploymentID = 1
I am running System Center 2012 R2 on Windows Server 2012 R2. With this, I run SQL Server 2012 Sp1.
Thanks
Chris

Hi,
UpdatesHandler.log on the client records about the download and installation of software updates on the client.
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.

Automatic Deployment Rules SCCM 2012 R2

Hello,
i have the following Situation.
I created a ADR for my Key Users. This ADR dowloads the needed updates add them to a a existing Deployment Group and add them to a Deployment Package.
When the ADR is starting, the Deployment package is updated and the Deployment Package is distributing to my DPs.
I have a second ADR, which does the same but a bit later (one week) and for my "Production Clients".
If the second ADR is starting, and MS offers new updates they will be downloaded and pushed on my Production Clients without beeing tested by the key users.
Another effect is that the Deployment Package is redistributed to my DPs and the packe has a size of 15 GB.
Any ideas how i can deal this?

Hello Thorsten,
thanks for replying.
Perhaps you have Suggestion for me:
I have two collections "Test Clients" and "Productiv Clients"
I have two ADRs
"ADR Test Clients":
Target Collection "Test Clients"
SUG: "ADR Test Clients"
Deployment Package: "Monthly Updates"
After 7 days the second ADR should run:
"ADR Productiv Clients":
Target Collection "Productiv Clients"
SUG: "ADR Productiv Clients"
Deployment Package: "Monthly Updates"
If i use the same settings for "Software Updates" in the second ADR, it might be possible, that new updates will be added, without being tested by the "Test Clients"
I think i found a solution:
I will start "ADR Productiv Clients" before the
"ADR Test Clients":
Settings I will do for the ADRs
"ADR Productiv Clients":
Evaluation Shedule: Monthly / every third Tuesday / Starting: 01:00 AM
Deployment Shedule: Software available after 7 days
Installation Deadline: 1 Hour
"ADR Test Clients":
Evaluation Shedule: Monthly / every third Tuesday / Starting: 10:00 AM
Deployment Shedule: Software available after 7 hours
Installation Deadline: 26 Hours
Result:
in any case the Test Clients will have the newer Version as the Productive Clients.

Looking for the right collection for a specific problem

Hi guys,
Just wanted to say great work you guys are doing here. the forum has definitely helped me a lot in the past.
I am currently having a problem selecting a collection for this specific application that i have to do for my final year project. I am looking for a way to store a bunch of strings a collection that uses the actual string as its key and stores the number of times that the string have been added to the collection as its value.
so for e.g
String a = "a";
String b = "b";
String a2 = "a";
String c = "c";
/**Here is where i create my collection */
// Collection mycollection = new collection
// mycollection.add(a);
// mycollection.add(b);
// mycollection.add(a2);
// mycollection.add(c);
/**if you request for the string a or a2 the collection should return the number of times that string appead e.g */
// System.out.println(mycollection.get(a));
//this should print 2
Does such a collection exist? I remember using something similar when i was learning c++ but i havent been able to find what i am looking for in the API documentation. Please help.
Frank

I think what the OP is looking for is probably a Bag. Unfortunately the default collections framework does not provide a Bag interface or implementation. You could look into using the Jakarta Commons Collection, they do provide those (look at the API[url] as well.

Automatic Deployment Rule for SCEP Definitions growing too large.

See the deployment package for SCEP definition is now 256MB and growing. How can we make sure it stays small? The ADR creating the package is leaving 26 Definition in there right now.

The method that Kevin suggests above is what is implemented as part of a default deployment template included with SP1. This limits the number of definitions in the update group to the latest eight (I think).
As a supplemental note here, whenever an ADR runs and is configured to use an existing update group, it first wipes that update group.
Jason | http://blog.configmgrftw.com

Automatic Deployment Rules - Just Not Working/Reboot

Good Morning:
For the better part of 5 days I have been trying to get ADR deployed in my lab to install and automatically reboot machines. I have gotten everything set up and the rule is working and downloading the update, just never making it to the clients to
install the updates and or reboot. For simplicity sake, I created a device collection, "domain controllers" and this finds my two DCs just fine. I then created a ADR
Collection - Domain Controllers, Add to Existing Software Update Group - Software Updates (date released - 2 months, Product - 2008 R2) as both of my DCs are 2008 R2 - Evaluation Schedule (Run on schedule - once a week at 11:30 pm) - Deployment Schedule
(software/specific time 1 hour) (installation/2 hours) - User Experience Software Installation Checked - Then I create a new deployment package and then run it.
It created the deployment packages, and the software update group, I checked the logs and it downloads the files just fine and shows 42 updates needed. However I cannot get those two servers to install updates and reboot for the life of me. I have
google and read everything possible. I checked the permissions of the package source, I created a maintenance window for that time, I attempted to change the work information via powershell in case it was overlapping.
Can anyone please give me a little push in the right direction on what I could possibly be missing?
I did see this in the log,
Could not find element DeploymentId SMS_RULE_ENGINE
1/3/2014 10:03:35 AM 3240 (0x0CA8)
Could not find element UpdateGroupId SMS_RULE_ENGINE
1/3/2014 10:03:35 AM 3240 (0x0CA8)
Could not find element UpdateGroupName SMS_RULE_ENGINE
1/3/2014 10:03:35 AM 3240 (0x0CA8)
SQL is: select cis.CI_ID from vCI_ConfigurationItems cis join vProvisionedCIs pci on cis.CI_ID = pci.CI_ID where cis.CI_ID in (16789853, 16789855, 16789865, 16789867, 16790069, 16790071, 16790077, 16790081, 16790087, 16790089, 16790164, 16790166,
16790193, 16790195, 16790203, 16790205, 16790213, 16790217, 16790221, 16790424, 16790426, 16790430, 16790436, 16790438, 16790444, 16790448, 16790452, 16790509, 16790517, 16790523, 16790527, 16790531, 16790535, 16790537, 16790547, 16790568, 16790574) order
by cis.CI_ID SMS_RULE_ENGINE
1/3/2014 10:03:35 AM 3240 (0x0CA8)
42 of 42 updates are downloaded and will be added to the Deployment.
SMS_RULE_ENGINE 1/3/2014 10:03:35 AM
3240 (0x0CA8)
Any assistance would be greatly appreciated as this is just making me spin in circles.

In the WUAHandler
<![LOG[Failed to Add Update Source for WUAgent of type (2) and id ({425A8C16-C127-4006-B60D-8F04DF0333EB}). Error = 0x87d00692.]LOG]!><time="11:28:02.414+360" date="01-03-2014" component="WUAHandler" context="" type="3" thread="6796" file="cwuahandler.cpp:2325">
<![LOG[Its a WSUS Update Source type ({425A8C16-C127-4006-B60D-8F04DF0333EB}), adding it.]LOG]!><time="12:58:08.788+360" date="01-03-2014" component="WUAHandler" context="" type="1" thread="4344" file="sourcemanager.cpp:1232">
<![LOG[Enabling WUA Managed server policy to use server: http://KSP-SCCM.waw.local:8530]LOG]!><time="12:58:08.788+360" date="01-03-2014" component="WUAHandler" context="" type="1" thread="4344" file="sourcemanager.cpp:948">
<![LOG[Waiting for 2 mins for Group Policy to notify of WUA policy change...]LOG]!><time="12:58:08.803+360" date="01-03-2014" component="WUAHandler" context="" type="1" thread="4344" file="sourcemanager.cpp:954">
<![LOG[Group policy settings were overwritten by a higher authority (Domain Controller) to: Server http://KSP-SCCM:8530 and Policy ENABLED]LOG]!><time="12:58:10.348+360" date="01-03-2014" component="WUAHandler" context="" type="3" thread="4344" file="sourcemanager.cpp:1013">
<![LOG[Failed to Add Update Source for WUAgent of type (2) and id ({425A8C16-C127-4006-B60D-8F04DF0333EB}). Error = 0x87d00692.]LOG]!><time="12:58:10.348+360" date="01-03-2014" component="WUAHandler" context="" type="3" thread="4344" file="cwuahandler.cpp:2325">
So now I think that GPO setting maybe causing my issues.

I just found out my credit score dropped because Verizon One bill put me through collections for my final bill that I never received and after almost two hours on the phone transferred back and forth they still could not confirm if I owe money or not.

After 2 hours transferred back and forth between billing, one bill, home and wireless no one could prove that I owed money. Wireless said I owed nothing and home said I had a credit for cancelling a couple days before the billing cycle but owed for wireless. After a three-way called between Home and Wireless and Wireless insisting I do not owe anything, the Home representative disconnected herself, the wireless rep promised me a call back the next day to get the other department online and to get everything resolved. No one called me back next day and the day after. Knowing this could go in circles and don't want to do anything bad to my credit, I paid the settlement amount to the collection agencies. Now I saw that my credit score got ding for an amount that Verizon couldn't prove that I owed. I should not have paid it at all. If someone from Verizon reads this message, please get back to me and get this resolved. After more than 15 years with this company, this is making me so frustrated. I liked Verizon services but at this point I am going to start looking for someone with better billing.

I called customer service, spoke to Verizon Wireless Representative but they cannot pull anything on my record. So after two transfers I asked to speak to financial services. Spoke to Ronnie Ext 5100. Representative was very rude, not listening, kept on insisting that since I paid the collection agency I cannot dispute. Said should not have paid the collection agency. Rep was over talking, not listing to me explaining my frustration of being on the phone for hours in November between Verizon OneBill, Home and Wireless and got nothing resolved, and that's why I paid. Said there's nothing she can do except to put a note to Credit Bureau that the account is paid in full. I asked to talk to a supervisor or a manager and she said no one can do anything else. I insisted and she asked me to leave a phone number to call back. After all the calls and speaking to many reps, this is the worst. Now I am back to square one waiting for someone to call me back. And my credit score is still one hundred points lower thanks to Verizon!!!

Should I include the "Required" as part of my criteria when creating an Automatic Deployment Rule?

I want to make sure that I do not have unnecessary software updates in my packages and SUGs so should I include the "Required" criteria and configure it as greater than or equal to "1"?
Thanks

I concur with Peter. Using Required as a criterion is being reactive instead of proactive. Security should be proactive.
Additionally, if you do use Required, other systems could come onto the network missing older updates that you've never made available before and thus they, depending upon the exact criteria you use, may never get that update.
Jason | http://blog.configmgrftw.com | @jasonsandys

SCCM 2012 R2: Forefront Endpoint protection via automatic updates only work when manually triggering automatic updat rule

Hi,
I followed this manual to configure forefront endpoint protection on clients: http://www.windows-noob.com/forums/index.php?/topic/6106-using-system-center-2012-configuration-manager-part-6-adding-the-endpoint-protection-role-configure-alerts-and-custom-antimalware-policies/
Now in short: everything works fine ... as long as I trigger the audomatic deployment rules.
Current situation:
1. ADR ran fine (3:30 this night)
2.Software update group is NOT ok
3.I run ADR manually (right click on ADR, run)
4.software update group is ok (green icon)
Then virusupdates are succesfull. This means that clients only update their virus definitions when I manually run the ADR-rule.
I'm missing something here.
Please advise.
J.
Jan Hoedt

Probably this issue: http://social.technet.microsoft.com/Forums/en-US/c6109678-785b-4c6d-9cb4-c9dfc1e34b2e/sccm-2012-automatic-deployment-rule-not-executing-updates-for-scep?forum=configmanagerapps
Iow: wsus updates were scheduled at 3, automatic update rules at 3:15, probably sync wasn't done yet so it doesn't find updates. "The day after" updates are marked as expired.
Jan Hoedt

Automatic Deployed Updates Source Cleanup

I recently set up an automatic deployment rule for the scep definition updates. It works like a charm, new update are being downloaded, and old updates are beeing superseeded and at last expired.
But, the source folder, where my software update deployment package lies is just getting bigger and bigger. SCCM obviously don't distribute the expired updates to the DP anymore but does not cleanup the source folder.
Is there a mechanism which will cleanup my source folder or do i need to write a script for that? I also run the WSUS Cleanup Wizard, but it also won't cleanup my update source folder.
We are using SCCM 2012 SP1 CU3
Thanks in advance..

You should remove the expired updates from your software update Groups. That way the source and the DP will be "cleaned up"
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals

Automatic Deployment Rule - One ADR for Two Different Collection for Two Different time Intervals

Similar Messages

Maybe you are looking for