Maintenance Windows: Possible to prevent downloading of packages until window opens?
I have several collections with specific maintenance windows during off-hours. I was initially under the impression that the maintenance window would prevent workstations in a specific collection from both downloading the package for an advertisement and running the package until the appropriate window opened up. With further testing, I have realized that the systems will still download the package at will, they just won't execute it until the window opens up.
Is there a way to prevent advertised packages from being downloaded until the window opens (aside from changing when the advertisement becomes available)?
Is there a way to prevent advertised packages from being downloaded until the window opens (aside from changing when the advertisement becomes available)?
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
dunnpy
14 years ago
Glad to be of some help.
Found a link for you 'How to Deploy a Branch Distribution Point'. You have to setup some protected site boundaries so that only machines on that site use the Branch DP there.
Don't forget to rate a post you might have found useful [;)]
Thanks,
Dunnpy
Found a link for you 'How to Deploy a Branch Distribution Point'. You have to setup some protected site boundaries so that only machines on that site use the Branch DP there.
Don't forget to rate a post you might have found useful [;)]
Thanks,
Dunnpy
Posted by:
dunnpy
14 years ago
Blake,
It's not something that I've had to deal with on my SCCM site, as it is well connected without remote offices.
What about installing some Branch DP's on your remote sites? Branch DP's can be installed on any SCCM client machine - including Windows XP Pro machines.
That way you can throttle the BITS to the DP's during core hours to save band-width, but still have a deployment run when you like without hammering your link.
Just thinking aloud - hope it helps,
Dunnpy
It's not something that I've had to deal with on my SCCM site, as it is well connected without remote offices.
What about installing some Branch DP's on your remote sites? Branch DP's can be installed on any SCCM client machine - including Windows XP Pro machines.
That way you can throttle the BITS to the DP's during core hours to save band-width, but still have a deployment run when you like without hammering your link.
Just thinking aloud - hope it helps,
Dunnpy
Posted by:
aslander
14 years ago
Yea, I've already previously modified the BITS setting to throttle it down pretty low. The main problem being that we have many remote locations without a distribution point at that location. I have it throttle down to about 100Kbps, but this can still adversely affect the bandwidth when a hundred or so systems are downloading at this speed in conjunction with normal business activities.
If I could specify different BITS settings based on collection, that would probably solve my problem, because then I could basically throttle it down to practically zero during certain windows, but I don't think this is possible.
Dunnpy, I like your idea of changing the polling interval, and that may somewhat work as well, I was just curious what other people have done in situations where they cannot risk impacting network connectivity adversely. Thanks for your suggestion.
If I could specify different BITS settings based on collection, that would probably solve my problem, because then I could basically throttle it down to practically zero during certain windows, but I don't think this is possible.
Dunnpy, I like your idea of changing the polling interval, and that may somewhat work as well, I was just curious what other people have done in situations where they cannot risk impacting network connectivity adversely. Thanks for your suggestion.
Posted by:
aslander
14 years ago
Hmmm, that sounds like a better idea. I wasn't aware that they can be any XP machine with the client can be set up as a DP.
Aside from our large sites, we have probably 30 remote sites with 15-25 PCs, so it would probably be a good idea to do something like that on a dedicated machine. I will start investigating into that possibility. I appreciate your help!
Aside from our large sites, we have probably 30 remote sites with 15-25 PCs, so it would probably be a good idea to do something like that on a dedicated machine. I will start investigating into that possibility. I appreciate your help!
Posted by:
konman2k4
13 years ago
Posted by:
dunnpy
14 years ago
Blake,
I've got a suggestion - don't know how practical it would actually be...
On the 'BITS' tab of the 'Comptuter Client Agent' you can specify a throttling window for your clients. You may be able to tweak the settings so that it will only download the package to install within your maintenance window.
The only other thing is to specify a different polling schedule for those clients, so the check and download of the package falls inside your window - from the 'Modify Collection Settings' option.
Can't think of anything else...
Dunnpy
.
I've got a suggestion - don't know how practical it would actually be...
On the 'BITS' tab of the 'Comptuter Client Agent' you can specify a throttling window for your clients. You may be able to tweak the settings so that it will only download the package to install within your maintenance window.
The only other thing is to specify a different polling schedule for those clients, so the check and download of the package falls inside your window - from the 'Modify Collection Settings' option.
Can't think of anything else...
Dunnpy
.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.