|
|
We use WSUS to update our servers on the weekend. Is it possible to set a
window so that upgrades do not start until a specified time and are complete
by a specified time.
I can set a deadline so that updates are started by a certain time, however,
if I approve the updates early they may start before I want them to.
We have a window of time that we need to complete the upgrades within and I
am having trouble kekping within the window.
Thanks,
Joe
|
|
In the GPO for server, select option 3 - download only, then update
manually
=?Utf-8?B?Sm9lcmFiYmk=?= <Joerabbi[ at ]discussions.microsoft.com> wrote in
news:27DB6820-4C7D-4784-9DB1-3D07A13F7853[ at ]microsoft.com:
[Quoted Text] > We use WSUS to update our servers on the weekend. Is it possible to
> set a window so that upgrades do not start until a specified time and
> are complete by a specified time.
> I can set a deadline so that updates are started by a certain time,
> however, if I approve the updates early they may start before I want
> them to.
>
> We have a window of time that we need to complete the upgrades within
> and I am having trouble kekping within the window.
>
> Thanks,
> Joe
>
|
|
|
|
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > Yes, see this article for a discussion on one way to accomplish this > objective: > > How can I update my server when I have a fixed maintenance window? > http://wsusinfo.onsitechsolutions.com/articles/011.htm> > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007)
Lawrence, that is what I thought too. My actual experience did not play out
as expected. I had the GPO set up to download and apply on Saturday every
week with a detection frequency of one hour. I did not approve any updates
for a couple of weeks. On the week that I was going to install updates, I
approved the updates on Thursday morning with a deadline of Friday evening.
I should have made the deadline for saturday but the results would be the
same. On Thursday afternoon one of my servers started installing updates and
rebooting. This was a day before the deadline and two days before the
install time.
As near as I can figure, the server saw the update as being detected from
the previous Saturday (because of the continuing one hour detection refresh)
and therefore applied it.
Since I have over 100 servers to update in one day, I would prefer not to
have to download and wait. I would prefer to have the method you describe
and that I used, work.
Have any others had similar experiences?
Thanks,
Joe
|
|
"Joerabbi" <Joerabbi[ at ]discussions.microsoft.com> wrote in message
news:F456C0A7-434A-4623-93FE-395FA303F2F1[ at ]microsoft.com...
[Quoted Text]
> Lawrence, that is what I thought too. My actual experience did not play
> out
> as expected. I had the GPO set up to download and apply on Saturday every
> week with a detection frequency of one hour. I did not approve any
> updates
> for a couple of weeks. On the week that I was going to install updates, I
> approved the updates on Thursday morning with a deadline of Friday
> evening.
> I should have made the deadline for saturday but the results would be the
> same.
As discussed in the article, the critical component of this process is that
the deadline *must* be exactly the same time as the scheduled installation
event.
Otherwise you will cause the installation of the updates to occur at the
deadline time, not at the scheduled maintenance window.
> On Thursday afternoon one of my servers started installing updates and
> rebooting. This was a day before the deadline and two days before the
> install time.
Then this was caused neither by the deadline, nor by the scheduled
installation. This was caused by a =human=. The WindowsUpdate.log can be
used to determine the exact methodology of the installation of the update,
but there are only three ways an update initiate an installation:
[1] The scheduled installation time is reached and an update has been
downloaded and scheduled for installation.
[2] A configured deadline has expired and the update has been
downloaded.
[3] A human being initiates installation of an update that has been
downloaded.
> As near as I can figure, the server saw the update as being detected from
> the previous Saturday (because of the continuing one hour detection
> refresh)
> and therefore applied it.
Not at a "random" time on Thursday afternoon it did not. To present the
corollary of the above statements:
[1] Either the server had a scheduled installation event configured for
Thursday afternoon.
[2] The deadline for the updates was set for Thursday afternoon.
[3] The machine powered up on Thursday afternoon after being
continuously powered off since the last scheduled installation event, with
updates scheduled for installation.
[4] A human being initiated the installation from a console session.
> Since I have over 100 servers to update in one day, I would prefer not to
> have to download and wait. I would prefer to have the method you describe
> and that I used, work.
I promise you. If you follow the description as presented in the article,
exactly, and ensure that you don't get any "help" from other admins, it
*will* work exactly as described in the article.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
|