Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Set up a schedule for package deployment SCCM 2007

Posted on 2010-08-18
4
1,190 Views
Last Modified: 2013-11-21
We have a project where we're setting up 16 new distribution points.  The points are in different branches outside of headquarters.  We don't want to sap all the bandwidth by pushing the packages out so we want to only push them out on Sunday.  Is this possible?  Can I separate the distribution points into groups of 4 so that say on the first Sunday of the month, group 1 gets all the packages.  On the second Sunday, group 2 gets the packages ... etc.?  If so, how do I set this up?

Any suggestions?
0
Comment
Question by:sedberg1
  • 2
4 Comments
 
LVL 6

Expert Comment

by:Exemplar
ID: 33468801
Hello sedberg1!

Absolutely you can deploy packages at specified times.  This is done by utilizing ConfigMgr's "Maintenance Window" functionality.  You can identify the systems involved by Collection and then create a Maintenance Window on that Collection to only allow advertisements/software updates to start at the date/time you designate.

If you're unfamiliar with ConfigMgr Maintenance Windows, you can create one by doing the following:

Right-click on the Collection, chose Modify Collection Settings, chose Maintenance Windows tab.  Now you are in the Maintenance Windows tab, press the yellow asterisk to create a new Maintenance Window.  You will now be prompted to create a custom Maintenance Window.  Keep a few things in mind:  1. If it is a one-time window choose 'None' for the Recurrence pattern.  2.  Remember to go back and remove any on-time Maintenance Windows or they could affect future deployments.
IMPORTANT:  Make sure that the Advertisement is NOT set to Ignore Maintenance Windows (found on individual Advertisement - Schedule tab).  If it is set to Ignore Maintenance Windows... the Maintenance Window you created will be useless for this advertisement and will install outside the date/time you intended.

/cheers
0
 

Author Comment

by:sedberg1
ID: 33469010
So, I could make four collections, each one with 4 new distribution points.  Then make the Maintenance Window for each one to 1st Sunday, 2nd Sunday, etc.  Ok, I see how to do that now.  But with the Advertisements, those are for deploying packages.  What I mean to do is update the distribution point so that the package is available to clients from the new distribution point.  I don't want the new distribution point to install these packages, just have them available to clients.

What I mean, is when there's a package to create and clients should have them installed, that package needs to be copied to a distribution point.  Normally, if the distribution point does not have the package, I go to the package> right-click > Manage DP > Copy the package to new distribution points > then choose the DP.  Rather than have to go to each package and run this process to update the new DPs, is there a better way?
0
 
LVL 6

Accepted Solution

by:
Exemplar earned 500 total points
ID: 33469269
sedberg1,

Yeah, that's a tough consideration when adding 16 new DPs I suppose.  As far as I know you have to add the package (in the method you identified) for each of the new DPs as required by the ConfigMgr clients.

Thanks,
Ex
0
 

Expert Comment

by:jparekh
ID: 33487540
Wait, do you want to separate the package push to the clients or just getting the packages to the DPs?
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip is around source server preparation. No migration is an easy migration, there is a…
Know what services you can and cannot, should and should not combine on your server.
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Although Jacob Bernoulli (1654-1705) has been credited as the creator of "Binomial Distribution Table", Gottfried Leibniz (1646-1716) did his dissertation on the subject in 1666; Leibniz you may recall is the co-inventor of "Calculus" and beat Isaac…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question