Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: Windows Server » microsoft.public.windows.server.update_services
Thread: Bandwith Calculation

HTVi
TV Discussion Newsgroups

Bandwith Calculation
bacot 6/20/2007 6:48:00 AM
Hi,

can anyone advise me how to calculate the time needed to deploy a patch to a
group of PCs. For example I want to deploy Windows XP service pack2
(WindowsXP-KB835935-SP2-ENU.exe - 266 MB)to 1000 WinXP workstation.

How can I specify this patch to be deployed between a certain timeframe
(i.e. everyday from 8.00 p.m - 6.00 a.m).

If I specify a group policy to "auto download and schedule install -
everyday at 8.00 p.m, will the workstations start downloading the patch at
8.00 p.m or will the workstation download the patch prior to 8.00 p.m and
start the installation of the patch at 8.00 p.m?



Re: Bandwith Calculation
Jason Ede <j.d.ede.nospam[ at ]nospam.shef.ac.uk> 6/20/2007 7:44:42 AM
bacot wrote:
[Quoted Text]
> Hi,
>
> can anyone advise me how to calculate the time needed to deploy a patch to a
> group of PCs. For example I want to deploy Windows XP service pack2
> (WindowsXP-KB835935-SP2-ENU.exe - 266 MB)to 1000 WinXP workstation.
>
> How can I specify this patch to be deployed between a certain timeframe
> (i.e. everyday from 8.00 p.m - 6.00 a.m).
>
> If I specify a group policy to "auto download and schedule install -
> everyday at 8.00 p.m, will the workstations start downloading the patch at
> 8.00 p.m or will the workstation download the patch prior to 8.00 p.m and
> start the installation of the patch at 8.00 p.m?
>
>
>

I'm pretty certain that the machines will download the patch whenever
they check in to your WSUS server, but will not install till the
specified time. Otherwise the WSUS servers would be hit very hard at
installation time.

Jason
Re: Bandwith Calculation
"Asher_N" <ashernat[ at ]gmail.com> 6/20/2007 12:28:22 PM
=?Utf-8?B?YmFjb3Q=?= <bacot[ at ]discussions.microsoft.com> wrote in
news:1EFE055C-74A0-4320-96EE-F8AD41DF4250[ at ]microsoft.com:

[Quoted Text]
> Hi,
>
> can anyone advise me how to calculate the time needed to deploy a
> patch to a group of PCs. For example I want to deploy Windows XP
> service pack2 (WindowsXP-KB835935-SP2-ENU.exe - 266 MB)to 1000 WinXP
> workstation.
>
> How can I specify this patch to be deployed between a certain
> timeframe (i.e. everyday from 8.00 p.m - 6.00 a.m).
>

You can use different GPO to specify different times. Install time is not
a range.


> If I specify a group policy to "auto download and schedule install -
> everyday at 8.00 p.m, will the workstations start downloading the
> patch at 8.00 p.m or will the workstation download the patch prior to
> 8.00 p.m and start the installation of the patch at 8.00 p.m?
>
>


The GPO containd 2 timing entry. One is the install time. How often
(every day, or wich day of the week) and the time of day.

The other is the frequency at which clients will check in with the WSUS
server. It is an interval expressed in hours. The default is 22 hours. A
random offset is also applied. Clients will also check in with WSUS at
startup.

Once a client checks in, if needed updates are available, the client will
pull them from the WSUS server using BITS. When updates are fully
downloaded and the install time is reached, the updates will be applied.

Bandwidth is managed both by the detection frequency and the bandwidth
throtling capabilities of BITS.

>

Re: Bandwith Calculation
bacot 6/20/2007 11:41:48 PM
Thanks for the replies.

So I guess there is no mechanism in WSUS that I can use to ensure that the
patch will be deployed on a certain timeframe. And also there is no way we
can specify a timeframe to when deploying a patch. I thought the deadline
feature on the WSUS server works to ensure that a patch is deployed by a
specified time that the WSUS administrator specified.

So If I need to deploy a patch like SP2 for WIndows XP (which is fairly big
in size) to 1000 PCs, is it fair to say that it will take days /weeks for
this patch to completely deployed to all of these PCs and there is no way
that IT / WSUS admin could provide an ETA on when the specified patch will be
completely deployed.

The reason why I am interested in finding out how to calculate the bandwith
required to deployed a patch is because I am interested in finding out is how
other people provide a time estimation for deploying a patch or a series of
patches to a number of PCs for a project plan / management report.


"Asher_N" wrote:

[Quoted Text]
> =?Utf-8?B?YmFjb3Q=?= <bacot[ at ]discussions.microsoft.com> wrote in
> news:1EFE055C-74A0-4320-96EE-F8AD41DF4250[ at ]microsoft.com:
>
> > Hi,
> >
> > can anyone advise me how to calculate the time needed to deploy a
> > patch to a group of PCs. For example I want to deploy Windows XP
> > service pack2 (WindowsXP-KB835935-SP2-ENU.exe - 266 MB)to 1000 WinXP
> > workstation.
> >
> > How can I specify this patch to be deployed between a certain
> > timeframe (i.e. everyday from 8.00 p.m - 6.00 a.m).
> >
>
> You can use different GPO to specify different times. Install time is not
> a range.
>
>
> > If I specify a group policy to "auto download and schedule install -
> > everyday at 8.00 p.m, will the workstations start downloading the
> > patch at 8.00 p.m or will the workstation download the patch prior to
> > 8.00 p.m and start the installation of the patch at 8.00 p.m?
> >
> >
>
>
> The GPO containd 2 timing entry. One is the install time. How often
> (every day, or wich day of the week) and the time of day.
>
> The other is the frequency at which clients will check in with the WSUS
> server. It is an interval expressed in hours. The default is 22 hours. A
> random offset is also applied. Clients will also check in with WSUS at
> startup.
>
> Once a client checks in, if needed updates are available, the client will
> pull them from the WSUS server using BITS. When updates are fully
> downloaded and the install time is reached, the updates will be applied.
>
> Bandwidth is managed both by the detection frequency and the bandwidth
> throtling capabilities of BITS.
>
> >
>
>
Re: Bandwith Calculation
"Asher_N" <ashernat[ at ]gmail.com> 6/21/2007 1:31:06 PM
The easy answer is within 48 hours.

If you leave the detection at the default 22 hours, then within about 24
hours, all machines will have initiated a download of the patch.
Completion of that download is a factor is size of the patch and
bandwidth available to BITS. From that you can infer that a percentage of
the machines wil lhave the patch ready by the next install time, and the
remainder by the next one. If your GPO specifies daily updates, then
within 48 hours of approving a patch, all workstations will have it
installed.

All the deadline does is ensure that the patch will be installed by a
certain date. Be careful with deadlines, they are unforgiving to the
user. Deadlined patches WILL reboot the computer after installation, no
other choice is given.



=?Utf-8?B?YmFjb3Q=?= <bacot[ at ]discussions.microsoft.com> wrote in
news:98BE9F3E-88C1-4E6A-81A7-AC423779AAF4[ at ]microsoft.com:

[Quoted Text]
> Thanks for the replies.
>
> So I guess there is no mechanism in WSUS that I can use to ensure that
> the patch will be deployed on a certain timeframe. And also there is
> no way we can specify a timeframe to when deploying a patch. I thought
> the deadline feature on the WSUS server works to ensure that a patch
> is deployed by a specified time that the WSUS administrator specified.
>
> So If I need to deploy a patch like SP2 for WIndows XP (which is
> fairly big in size) to 1000 PCs, is it fair to say that it will take
> days /weeks for this patch to completely deployed to all of these PCs
> and there is no way that IT / WSUS admin could provide an ETA on when
> the specified patch will be completely deployed.
>
> The reason why I am interested in finding out how to calculate the
> bandwith required to deployed a patch is because I am interested in
> finding out is how other people provide a time estimation for
> deploying a patch or a series of patches to a number of PCs for a
> project plan / management report.
>
>
> "Asher_N" wrote:
>
>> =?Utf-8?B?YmFjb3Q=?= <bacot[ at ]discussions.microsoft.com> wrote in
>> news:1EFE055C-74A0-4320-96EE-F8AD41DF4250[ at ]microsoft.com:
>>
>> > Hi,
>> >
>> > can anyone advise me how to calculate the time needed to deploy a
>> > patch to a group of PCs. For example I want to deploy Windows XP
>> > service pack2 (WindowsXP-KB835935-SP2-ENU.exe - 266 MB)to 1000
>> > WinXP workstation.
>> >
>> > How can I specify this patch to be deployed between a certain
>> > timeframe (i.e. everyday from 8.00 p.m - 6.00 a.m).
>> >
>>
>> You can use different GPO to specify different times. Install time is
>> not a range.
>>
>>
>> > If I specify a group policy to "auto download and schedule install
>> > - everyday at 8.00 p.m, will the workstations start downloading the
>> > patch at 8.00 p.m or will the workstation download the patch prior
>> > to 8.00 p.m and start the installation of the patch at 8.00 p.m?
>> >
>> >
>>
>>
>> The GPO containd 2 timing entry. One is the install time. How often
>> (every day, or wich day of the week) and the time of day.
>>
>> The other is the frequency at which clients will check in with the
>> WSUS server. It is an interval expressed in hours. The default is 22
>> hours. A random offset is also applied. Clients will also check in
>> with WSUS at startup.
>>
>> Once a client checks in, if needed updates are available, the client
>> will pull them from the WSUS server using BITS. When updates are
>> fully downloaded and the install time is reached, the updates will be
>> applied.
>>
>> Bandwidth is managed both by the detection frequency and the
>> bandwidth throtling capabilities of BITS.
>>
>> >
>>
>>
>

Re: Bandwith Calculation
bacot 6/21/2007 10:46:00 PM
Thanks for the reply again Asher_N.

I have set the detection time at default 22 hours, so you say within 48
hours, the patch (if the size is not too large) will normally get deployed to
all workstations. Is there any report on the WSUS 3 that could indicates how
many PC has a patch been deployed to?

"Asher_N" wrote:

[Quoted Text]
> The easy answer is within 48 hours.
>
> If you leave the detection at the default 22 hours, then within about 24
> hours, all machines will have initiated a download of the patch.
> Completion of that download is a factor is size of the patch and
> bandwidth available to BITS. From that you can infer that a percentage of
> the machines wil lhave the patch ready by the next install time, and the
> remainder by the next one. If your GPO specifies daily updates, then
> within 48 hours of approving a patch, all workstations will have it
> installed.
>
> All the deadline does is ensure that the patch will be installed by a
> certain date. Be careful with deadlines, they are unforgiving to the
> user. Deadlined patches WILL reboot the computer after installation, no
> other choice is given.
>
>
>
> =?Utf-8?B?YmFjb3Q=?= <bacot[ at ]discussions.microsoft.com> wrote in
> news:98BE9F3E-88C1-4E6A-81A7-AC423779AAF4[ at ]microsoft.com:
>
> > Thanks for the replies.
> >
> > So I guess there is no mechanism in WSUS that I can use to ensure that
> > the patch will be deployed on a certain timeframe. And also there is
> > no way we can specify a timeframe to when deploying a patch. I thought
> > the deadline feature on the WSUS server works to ensure that a patch
> > is deployed by a specified time that the WSUS administrator specified.
> >
> > So If I need to deploy a patch like SP2 for WIndows XP (which is
> > fairly big in size) to 1000 PCs, is it fair to say that it will take
> > days /weeks for this patch to completely deployed to all of these PCs
> > and there is no way that IT / WSUS admin could provide an ETA on when
> > the specified patch will be completely deployed.
> >
> > The reason why I am interested in finding out how to calculate the
> > bandwith required to deployed a patch is because I am interested in
> > finding out is how other people provide a time estimation for
> > deploying a patch or a series of patches to a number of PCs for a
> > project plan / management report.
> >
> >
> > "Asher_N" wrote:
> >
> >> =?Utf-8?B?YmFjb3Q=?= <bacot[ at ]discussions.microsoft.com> wrote in
> >> news:1EFE055C-74A0-4320-96EE-F8AD41DF4250[ at ]microsoft.com:
> >>
> >> > Hi,
> >> >
> >> > can anyone advise me how to calculate the time needed to deploy a
> >> > patch to a group of PCs. For example I want to deploy Windows XP
> >> > service pack2 (WindowsXP-KB835935-SP2-ENU.exe - 266 MB)to 1000
> >> > WinXP workstation.
> >> >
> >> > How can I specify this patch to be deployed between a certain
> >> > timeframe (i.e. everyday from 8.00 p.m - 6.00 a.m).
> >> >
> >>
> >> You can use different GPO to specify different times. Install time is
> >> not a range.
> >>
> >>
> >> > If I specify a group policy to "auto download and schedule install
> >> > - everyday at 8.00 p.m, will the workstations start downloading the
> >> > patch at 8.00 p.m or will the workstation download the patch prior
> >> > to 8.00 p.m and start the installation of the patch at 8.00 p.m?
> >> >
> >> >
> >>
> >>
> >> The GPO containd 2 timing entry. One is the install time. How often
> >> (every day, or wich day of the week) and the time of day.
> >>
> >> The other is the frequency at which clients will check in with the
> >> WSUS server. It is an interval expressed in hours. The default is 22
> >> hours. A random offset is also applied. Clients will also check in
> >> with WSUS at startup.
> >>
> >> Once a client checks in, if needed updates are available, the client
> >> will pull them from the WSUS server using BITS. When updates are
> >> fully downloaded and the install time is reached, the updates will be
> >> applied.
> >>
> >> Bandwidth is managed both by the detection frequency and the
> >> bandwidth throtling capabilities of BITS.
> >>
> >> >
> >>
> >>
> >
>
>
Re: Bandwith Calculation
"Asher_N" <ashernat[ at ]gmail.com> 6/22/2007 2:19:11 PM

One of the default pie charts shows how many patches are still needed.

I think that if you double click on a particular patch, you will get a
status report of all computers

=?Utf-8?B?YmFjb3Q=?= <bacot[ at ]discussions.microsoft.com> wrote in
news:FBDB129A-A5EE-415B-89CE-406881539B87[ at ]microsoft.com:

[Quoted Text]
> Thanks for the reply again Asher_N.
>
> I have set the detection time at default 22 hours, so you say within
> 48 hours, the patch (if the size is not too large) will normally get
> deployed to all workstations. Is there any report on the WSUS 3 that
> could indicates how many PC has a patch been deployed to?
>
> "Asher_N" wrote:
>
>> The easy answer is within 48 hours.
>>
>> If you leave the detection at the default 22 hours, then within about
>> 24 hours, all machines will have initiated a download of the patch.
>> Completion of that download is a factor is size of the patch and
>> bandwidth available to BITS. From that you can infer that a
>> percentage of the machines wil lhave the patch ready by the next
>> install time, and the remainder by the next one. If your GPO
>> specifies daily updates, then within 48 hours of approving a patch,
>> all workstations will have it installed.
>>
>> All the deadline does is ensure that the patch will be installed by a
>> certain date. Be careful with deadlines, they are unforgiving to the
>> user. Deadlined patches WILL reboot the computer after installation,
>> no other choice is given.
>>
>>
>>
>> =?Utf-8?B?YmFjb3Q=?= <bacot[ at ]discussions.microsoft.com> wrote in
>> news:98BE9F3E-88C1-4E6A-81A7-AC423779AAF4[ at ]microsoft.com:
>>
>> > Thanks for the replies.
>> >
>> > So I guess there is no mechanism in WSUS that I can use to ensure
>> > that the patch will be deployed on a certain timeframe. And also
>> > there is no way we can specify a timeframe to when deploying a
>> > patch. I thought the deadline feature on the WSUS server works to
>> > ensure that a patch is deployed by a specified time that the WSUS
>> > administrator specified.
>> >
>> > So If I need to deploy a patch like SP2 for WIndows XP (which is
>> > fairly big in size) to 1000 PCs, is it fair to say that it will
>> > take days /weeks for this patch to completely deployed to all of
>> > these PCs and there is no way that IT / WSUS admin could provide an
>> > ETA on when the specified patch will be completely deployed.
>> >
>> > The reason why I am interested in finding out how to calculate the
>> > bandwith required to deployed a patch is because I am interested in
>> > finding out is how other people provide a time estimation for
>> > deploying a patch or a series of patches to a number of PCs for a
>> > project plan / management report.
>> >
>> >
>> > "Asher_N" wrote:
>> >
>> >> =?Utf-8?B?YmFjb3Q=?= <bacot[ at ]discussions.microsoft.com> wrote in
>> >> news:1EFE055C-74A0-4320-96EE-F8AD41DF4250[ at ]microsoft.com:
>> >>
>> >> > Hi,
>> >> >
>> >> > can anyone advise me how to calculate the time needed to deploy
>> >> > a patch to a group of PCs. For example I want to deploy Windows
>> >> > XP service pack2 (WindowsXP-KB835935-SP2-ENU.exe - 266 MB)to
>> >> > 1000 WinXP workstation.
>> >> >
>> >> > How can I specify this patch to be deployed between a certain
>> >> > timeframe (i.e. everyday from 8.00 p.m - 6.00 a.m).
>> >> >
>> >>
>> >> You can use different GPO to specify different times. Install time
>> >> is not a range.
>> >>
>> >>
>> >> > If I specify a group policy to "auto download and schedule
>> >> > install - everyday at 8.00 p.m, will the workstations start
>> >> > downloading the patch at 8.00 p.m or will the workstation
>> >> > download the patch prior to 8.00 p.m and start the installation
>> >> > of the patch at 8.00 p.m?
>> >> >
>> >> >
>> >>
>> >>
>> >> The GPO containd 2 timing entry. One is the install time. How
>> >> often (every day, or wich day of the week) and the time of day.
>> >>
>> >> The other is the frequency at which clients will check in with the
>> >> WSUS server. It is an interval expressed in hours. The default is
>> >> 22 hours. A random offset is also applied. Clients will also check
>> >> in with WSUS at startup.
>> >>
>> >> Once a client checks in, if needed updates are available, the
>> >> client will pull them from the WSUS server using BITS. When
>> >> updates are fully downloaded and the install time is reached, the
>> >> updates will be applied.
>> >>
>> >> Bandwidth is managed both by the detection frequency and the
>> >> bandwidth throtling capabilities of BITS.
>> >>
>> >> >
>> >>
>> >>
>> >
>>
>>
>

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen