Sign in with
Sign up | Sign in
Your question

wireless slowdown after xp pro updates

Tags:
  • Wireless
  • Windows XP
  • Wireless Networking
Last response: in Wireless Networking
Share
Anonymous
a b F Wireless
September 2, 2004 5:13:10 PM

Archived from groups: microsoft.public.windows.networking.wireless (More info?)

8/27/2004 2:27 PM PST
xp pro problem performance after updates

In: microsoft.public.windowsxp.perform_maintain




Senerio:

On Friday August 13th around noon, I applied updates to a
Windows XP Pro Server at Allsouth, They run an appraisal
package WinTotal by Alamode software. I received calls
that afternoon reporting severe degredation in performance
especially noticable on wireless workstations (They have 4
all within 20 feet of the wireless router and generally
connect at 54mps). After several iterations of backing
out and reinstalling Wintotal software and updating the
firmware on the router we decided to hard wire the
stations to allow the business to function. The following
weekend I rolled back the XPPro server to July 31 removing
several updates. This alleviated the problem. All
wireless and wired workstations functioned correctly.
Wintotal transfers large amounts of data across the
network to the mapped drive. The following is a list of
Windows updates that I appeared to remove with the
rollback:

KB840315
KB839645
KB823353
KB867801
KB841873
KB842773
KB870669

The update I suspect is KB870669 which deals with reading
and writing data to the hard drive. Any sugestions
thoughts or comments would be greatly appreciated as I am
reluctant to apply any more fixes to their server until
this is resolved.

Thanks,

Paul Chapman

More about : wireless slowdown pro updates

Anonymous
a b F Wireless
September 2, 2004 7:19:01 PM

Archived from groups: microsoft.public.windows.networking.wireless (More info?)

Same thing here, I'm just running one desktop XP Pro. After running updates I
lost connection drivers and configuration data after each reboot. I
un-installed SP2 and a bunch of other updates and things are back to normal.
Anonymous
a b F Wireless
September 16, 2004 3:22:13 PM

Archived from groups: microsoft.public.windows.networking.wireless (More info?)

Paul,

This is very confusing! How do you mean that various pieces appear to be
still on the system? I am not quite sure what you mean by that. In
add/remove programs you should be able to see the pieces that have been
added to the system (QFE's/KB's, SP's). I only understood that the SP2
upgradecould be applied at once. Are you refering to the fact that later
these pieces were subsumed into SP2 and that now you still have some of
those KB's installed?

If things are working fine, the only thing you can do is either go to SP2 or
leave it alone. The last KB you mentioned was a client-side fix anyways.
It seems that if things are working now, and you are not considering going
to SP2, that the machine is in an OK state and is performing acceptably.
Without a way to test the actual problems there isn't much I can do to help
you, because the problem is too broad, and I don't have your app here to
look at. If you did install that fix and found that the server was then
slow when copying files, I could get on that problem right away.

In these situations it is great (!!) to have a Microsoft cluster solution
installed. With MSCS you can have a pair of computers, with one machine in
active stand-by that act as complete backup solution. When you upgrade, you
do it to only one machine. Then, if that causes problems, you roll the
file-shares over to the back-up node. Then you can analyze the problem,
test the fix, roll the resources (file shares, WWW roots, database
instances) back, etc. It is really fantastic for solving these kinds of
problems.

An equivalent is to just have two machines that are mirrors of each other.
That way you can roll-up one machine, and if it works, put it into
production. If it doesn't, you can fall back on the backup machine. If
the data lives on a separate, external disk, this is a good solution, and
gives you time to figure out what the problem might be while the customer is
happily using the other server.


--
Brian Wehrle
bwehrle@online.microsoft.com
Software Test Engineer/Wireless Networking
Microsoft Corp.

"paulchap" <paulchap@discussions.microsoft.com> wrote in message
news:C1A0A859-0260-4ED2-950C-71ACB07E9132@microsoft.com...
> Brian the software does use files on the server & yes some SP2 pieces were
> installed however the appear to still be in place after the server
> rollback
> and everything is still running normally since I haven't reinstalled the
> particular KBs mentioned in the original posting.... ??? I don't think it
> was
> an SP2 fix.... I believe it was the 669 kb......
>
> "Brian Wehrle [MSFT]" wrote:
>
>> Paul,
>>
>> It is hard to know exactly what is degrading performance on a system. It
>> seems that you have resolved the problem by removing these updates, but
>> that
>> does not exactly show what is causing the problem. Obviously you would
>> just
>> like to get the problem fixed. Since this system is now restored, there
>> is
>> not much we can do to analyzed the situation right now.
>>
>> The software you mention is not known to me; this is not surprising, but
>> without understanding exactly what the software does, it will be hard to
>> identify the problems. Since you said there were problems on wired and
>> wireless connections, it would be wise to test just raw file copies (i.e.
>> a
>> simple performance test)across the network:
>>
>> * Set up a file share on the XP Server
>> * Run: xcopy /s BIGDIR \\srv\fileshare\tmp && rmdir /s /q
>> \\srv\fileshare\tmp
>> * Time this with a wired connection (100 Mbps)
>> * Time this with your wireless connection (54 Mbps)
>> * Re-Apply these KB's
>> * Run these same tests
>>
>> I would be happy to try to reproduce the problem here, in fact, but I
>> don't
>> think it is the source of the problem. Rather, it sounds like there
>> might
>> be some other problem, perhaps related to a DB. Does this software
>> package
>> access a database on this same XP Pro server? Since the only KB here
>> that
>> you mentioned that has to do with a possible server-side component is the
>> last one, KB870669, you can try just installing that one and see if the
>> same
>> problem happens again.
>>
>> If you can narrow it down to one KB it would be much easier to diagnose.
>> I'll see what happens to my machine's performance when I install the same
>> patches, but I feel that it probably has to do with this particular
>> software
>> package that you are using.
>>
>> There have been reports of similar-sounding SP2 problems, please read
>> this
>> link:
>> http://news.zdnet.co.uk/software/windows/0,39020396,391...
>> This apparently is an SP2 issue and applies to Dell notebooks. I cannot
>> endorse this solution nor do I know that it has been analyzed by
>> Microsoft;
>> that is probably something that is already being worked on. Thus I
>> provide
>> this in case maybe you accidentally applied SP2 and did not realized it;
>> SP2
>> is now distributed through Windows Update, automatically. SP2 is called
>> KB811113.
>>
>> Brian Wehrle
>> bwehrle@online.microsoft.com
>> Software Test Engineer/Wireless Networking
>> Microsoft Corp.
>>
>> "paulchap" <paulchap@discussions.microsoft.com> wrote in message
>> news:64FD406C-9B6F-4D4A-BC34-F302AD8D7242@microsoft.com...
>> > 8/27/2004 2:27 PM PST
>> > xp pro problem performance after updates
>> >
>> > In: microsoft.public.windowsxp.perform_maintain
>> >
>> >
>> >
>> >
>> > Senerio:
>> >
>> > On Friday August 13th around noon, I applied updates to a
>> > Windows XP Pro Server at Allsouth, They run an appraisal
>> > package WinTotal by Alamode software. I received calls
>> > that afternoon reporting severe degredation in performance
>> > especially noticable on wireless workstations (They have 4
>> > all within 20 feet of the wireless router and generally
>> > connect at 54mps). After several iterations of backing
>> > out and reinstalling Wintotal software and updating the
>> > firmware on the router we decided to hard wire the
>> > stations to allow the business to function. The following
>> > weekend I rolled back the XPPro server to July 31 removing
>> > several updates. This alleviated the problem. All
>> > wireless and wired workstations functioned correctly.
>> > Wintotal transfers large amounts of data across the
>> > network to the mapped drive. The following is a list of
>> > Windows updates that I appeared to remove with the
>> > rollback:
>> >
>> > KB840315
>> > KB839645
>> > KB823353
>> > KB867801
>> > KB841873
>> > KB842773
>> > KB870669
>> >
>> > The update I suspect is KB870669 which deals with reading
>> > and writing data to the hard drive. Any sugestions
>> > thoughts or comments would be greatly appreciated as I am
>> > reluctant to apply any more fixes to their server until
>> > this is resolved.
>> >
>> > Thanks,
>> >
>> > Paul Chapman
>> >
>> >
>> >
>>
>>
>>
Related resources
Anonymous
a b F Wireless
September 17, 2004 5:51:20 PM

Archived from groups: microsoft.public.windows.networking.wireless (More info?)

Brian, as of right now there are pieces of sp2 on the server even though I
rolled it back to July 31 to remove the fixes in question..... The XP Server
was restored to that date but some sp2 fixes appear to be still applied ??????

thanks

"Brian Wehrle [MSFT]" wrote:

> Paul,
>
> This is very confusing! How do you mean that various pieces appear to be
> still on the system? I am not quite sure what you mean by that. In
> add/remove programs you should be able to see the pieces that have been
> added to the system (QFE's/KB's, SP's). I only understood that the SP2
> upgradecould be applied at once. Are you refering to the fact that later
> these pieces were subsumed into SP2 and that now you still have some of
> those KB's installed?
>
> If things are working fine, the only thing you can do is either go to SP2 or
> leave it alone. The last KB you mentioned was a client-side fix anyways.
> It seems that if things are working now, and you are not considering going
> to SP2, that the machine is in an OK state and is performing acceptably.
> Without a way to test the actual problems there isn't much I can do to help
> you, because the problem is too broad, and I don't have your app here to
> look at. If you did install that fix and found that the server was then
> slow when copying files, I could get on that problem right away.
>
> In these situations it is great (!!) to have a Microsoft cluster solution
> installed. With MSCS you can have a pair of computers, with one machine in
> active stand-by that act as complete backup solution. When you upgrade, you
> do it to only one machine. Then, if that causes problems, you roll the
> file-shares over to the back-up node. Then you can analyze the problem,
> test the fix, roll the resources (file shares, WWW roots, database
> instances) back, etc. It is really fantastic for solving these kinds of
> problems.
>
> An equivalent is to just have two machines that are mirrors of each other.
> That way you can roll-up one machine, and if it works, put it into
> production. If it doesn't, you can fall back on the backup machine. If
> the data lives on a separate, external disk, this is a good solution, and
> gives you time to figure out what the problem might be while the customer is
> happily using the other server.
>
>
> --
> Brian Wehrle
> bwehrle@online.microsoft.com
> Software Test Engineer/Wireless Networking
> Microsoft Corp.
>
> "paulchap" <paulchap@discussions.microsoft.com> wrote in message
> news:C1A0A859-0260-4ED2-950C-71ACB07E9132@microsoft.com...
> > Brian the software does use files on the server & yes some SP2 pieces were
> > installed however the appear to still be in place after the server
> > rollback
> > and everything is still running normally since I haven't reinstalled the
> > particular KBs mentioned in the original posting.... ??? I don't think it
> > was
> > an SP2 fix.... I believe it was the 669 kb......
> >
> > "Brian Wehrle [MSFT]" wrote:
> >
> >> Paul,
> >>
> >> It is hard to know exactly what is degrading performance on a system. It
> >> seems that you have resolved the problem by removing these updates, but
> >> that
> >> does not exactly show what is causing the problem. Obviously you would
> >> just
> >> like to get the problem fixed. Since this system is now restored, there
> >> is
> >> not much we can do to analyzed the situation right now.
> >>
> >> The software you mention is not known to me; this is not surprising, but
> >> without understanding exactly what the software does, it will be hard to
> >> identify the problems. Since you said there were problems on wired and
> >> wireless connections, it would be wise to test just raw file copies (i.e.
> >> a
> >> simple performance test)across the network:
> >>
> >> * Set up a file share on the XP Server
> >> * Run: xcopy /s BIGDIR \\srv\fileshare\tmp && rmdir /s /q
> >> \\srv\fileshare\tmp
> >> * Time this with a wired connection (100 Mbps)
> >> * Time this with your wireless connection (54 Mbps)
> >> * Re-Apply these KB's
> >> * Run these same tests
> >>
> >> I would be happy to try to reproduce the problem here, in fact, but I
> >> don't
> >> think it is the source of the problem. Rather, it sounds like there
> >> might
> >> be some other problem, perhaps related to a DB. Does this software
> >> package
> >> access a database on this same XP Pro server? Since the only KB here
> >> that
> >> you mentioned that has to do with a possible server-side component is the
> >> last one, KB870669, you can try just installing that one and see if the
> >> same
> >> problem happens again.
> >>
> >> If you can narrow it down to one KB it would be much easier to diagnose.
> >> I'll see what happens to my machine's performance when I install the same
> >> patches, but I feel that it probably has to do with this particular
> >> software
> >> package that you are using.
> >>
> >> There have been reports of similar-sounding SP2 problems, please read
> >> this
> >> link:
> >> http://news.zdnet.co.uk/software/windows/0,39020396,391...
> >> This apparently is an SP2 issue and applies to Dell notebooks. I cannot
> >> endorse this solution nor do I know that it has been analyzed by
> >> Microsoft;
> >> that is probably something that is already being worked on. Thus I
> >> provide
> >> this in case maybe you accidentally applied SP2 and did not realized it;
> >> SP2
> >> is now distributed through Windows Update, automatically. SP2 is called
> >> KB811113.
> >>
> >> Brian Wehrle
> >> bwehrle@online.microsoft.com
> >> Software Test Engineer/Wireless Networking
> >> Microsoft Corp.
> >>
> >> "paulchap" <paulchap@discussions.microsoft.com> wrote in message
> >> news:64FD406C-9B6F-4D4A-BC34-F302AD8D7242@microsoft.com...
> >> > 8/27/2004 2:27 PM PST
> >> > xp pro problem performance after updates
> >> >
> >> > In: microsoft.public.windowsxp.perform_maintain
> >> >
> >> >
> >> >
> >> >
> >> > Senerio:
> >> >
> >> > On Friday August 13th around noon, I applied updates to a
> >> > Windows XP Pro Server at Allsouth, They run an appraisal
> >> > package WinTotal by Alamode software. I received calls
> >> > that afternoon reporting severe degredation in performance
> >> > especially noticable on wireless workstations (They have 4
> >> > all within 20 feet of the wireless router and generally
> >> > connect at 54mps). After several iterations of backing
> >> > out and reinstalling Wintotal software and updating the
> >> > firmware on the router we decided to hard wire the
> >> > stations to allow the business to function. The following
> >> > weekend I rolled back the XPPro server to July 31 removing
> >> > several updates. This alleviated the problem. All
> >> > wireless and wired workstations functioned correctly.
> >> > Wintotal transfers large amounts of data across the
> >> > network to the mapped drive. The following is a list of
> >> > Windows updates that I appeared to remove with the
> >> > rollback:
> >> >
> >> > KB840315
> >> > KB839645
> >> > KB823353
> >> > KB867801
> >> > KB841873
> >> > KB842773
> >> > KB870669
> >> >
> >> > The update I suspect is KB870669 which deals with reading
> >> > and writing data to the hard drive. Any sugestions
> >> > thoughts or comments would be greatly appreciated as I am
> >> > reluctant to apply any more fixes to their server until
> >> > this is resolved.
> >> >
> >> > Thanks,
> >> >
> >> > Paul Chapman
> >> >
> >> >
> >> >
> >>
> >>
> >>
>
>
>
Anonymous
a b F Wireless
September 17, 2004 7:31:06 PM

Archived from groups: microsoft.public.windows.networking.wireless (More info?)

Paul,

That sounds very strange. Could you please tell me where you are getting
this information from? I can tell you that in the registry you can look at
the fixes installed in the current location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates
(Please do not modify any registry keys, this is just for looking). So,
could you tell me what you see in this key and its sub-keys?
I am not sure what to do about your problem. Since you rolled back, could
you need to roll-back once more?
Since the systems are stable and working once again, perhaps it is a good
idea just leave them be until you need to install SP2.

Eventually you will want to, for stability and security reasons. At that
point in time, you could test install the software (XP + SP2 +
Applications), copy the application data over (via file shares) and then
test this new system to make sure the problem is no longer happening (during
non-business hours). Then you could bring this test system online and
retire the other system.

Brian

--
Brian Wehrle
bwehrle@online.microsoft.com
Software Test Engineer/Wireless Networking
Microsoft Corp.



"paulchap" <paulchap@discussions.microsoft.com> wrote in message
news:D 389AE49-633F-48A9-8371-92B066E1A1FC@microsoft.com...
> Brian, as of right now there are pieces of sp2 on the server even though I
> rolled it back to July 31 to remove the fixes in question..... The XP
> Server
> was restored to that date but some sp2 fixes appear to be still applied
> ??????
>
> thanks
>
> "Brian Wehrle [MSFT]" wrote:
>
>> Paul,
>>
>> This is very confusing! How do you mean that various pieces appear to be
>> still on the system? I am not quite sure what you mean by that. In
>> add/remove programs you should be able to see the pieces that have been
>> added to the system (QFE's/KB's, SP's). I only understood that the SP2
>> upgradecould be applied at once. Are you refering to the fact that later
>> these pieces were subsumed into SP2 and that now you still have some of
>> those KB's installed?
>>
>> If things are working fine, the only thing you can do is either go to SP2
>> or
>> leave it alone. The last KB you mentioned was a client-side fix anyways.
>> It seems that if things are working now, and you are not considering
>> going
>> to SP2, that the machine is in an OK state and is performing acceptably.
>> Without a way to test the actual problems there isn't much I can do to
>> help
>> you, because the problem is too broad, and I don't have your app here to
>> look at. If you did install that fix and found that the server was then
>> slow when copying files, I could get on that problem right away.
>>
>> In these situations it is great (!!) to have a Microsoft cluster solution
>> installed. With MSCS you can have a pair of computers, with one machine
>> in
>> active stand-by that act as complete backup solution. When you upgrade,
>> you
>> do it to only one machine. Then, if that causes problems, you roll the
>> file-shares over to the back-up node. Then you can analyze the problem,
>> test the fix, roll the resources (file shares, WWW roots, database
>> instances) back, etc. It is really fantastic for solving these kinds of
>> problems.
>>
>> An equivalent is to just have two machines that are mirrors of each
>> other.
>> That way you can roll-up one machine, and if it works, put it into
>> production. If it doesn't, you can fall back on the backup machine. If
>> the data lives on a separate, external disk, this is a good solution, and
>> gives you time to figure out what the problem might be while the customer
>> is
>> happily using the other server.
>>
>>
>> --
>> Brian Wehrle
>> bwehrle@online.microsoft.com
>> Software Test Engineer/Wireless Networking
>> Microsoft Corp.
>>
>> "paulchap" <paulchap@discussions.microsoft.com> wrote in message
>> news:C1A0A859-0260-4ED2-950C-71ACB07E9132@microsoft.com...
>> > Brian the software does use files on the server & yes some SP2 pieces
>> > were
>> > installed however the appear to still be in place after the server
>> > rollback
>> > and everything is still running normally since I haven't reinstalled
>> > the
>> > particular KBs mentioned in the original posting.... ??? I don't think
>> > it
>> > was
>> > an SP2 fix.... I believe it was the 669 kb......
>> >
>> > "Brian Wehrle [MSFT]" wrote:
>> >
>> >> Paul,
>> >>
>> >> It is hard to know exactly what is degrading performance on a system.
>> >> It
>> >> seems that you have resolved the problem by removing these updates,
>> >> but
>> >> that
>> >> does not exactly show what is causing the problem. Obviously you
>> >> would
>> >> just
>> >> like to get the problem fixed. Since this system is now restored,
>> >> there
>> >> is
>> >> not much we can do to analyzed the situation right now.
>> >>
>> >> The software you mention is not known to me; this is not surprising,
>> >> but
>> >> without understanding exactly what the software does, it will be hard
>> >> to
>> >> identify the problems. Since you said there were problems on wired
>> >> and
>> >> wireless connections, it would be wise to test just raw file copies
>> >> (i.e.
>> >> a
>> >> simple performance test)across the network:
>> >>
>> >> * Set up a file share on the XP Server
>> >> * Run: xcopy /s BIGDIR \\srv\fileshare\tmp && rmdir /s /q
>> >> \\srv\fileshare\tmp
>> >> * Time this with a wired connection (100 Mbps)
>> >> * Time this with your wireless connection (54 Mbps)
>> >> * Re-Apply these KB's
>> >> * Run these same tests
>> >>
>> >> I would be happy to try to reproduce the problem here, in fact, but I
>> >> don't
>> >> think it is the source of the problem. Rather, it sounds like there
>> >> might
>> >> be some other problem, perhaps related to a DB. Does this software
>> >> package
>> >> access a database on this same XP Pro server? Since the only KB here
>> >> that
>> >> you mentioned that has to do with a possible server-side component is
>> >> the
>> >> last one, KB870669, you can try just installing that one and see if
>> >> the
>> >> same
>> >> problem happens again.
>> >>
>> >> If you can narrow it down to one KB it would be much easier to
>> >> diagnose.
>> >> I'll see what happens to my machine's performance when I install the
>> >> same
>> >> patches, but I feel that it probably has to do with this particular
>> >> software
>> >> package that you are using.
>> >>
>> >> There have been reports of similar-sounding SP2 problems, please read
>> >> this
>> >> link:
>> >> http://news.zdnet.co.uk/software/windows/0,39020396,391...
>> >> This apparently is an SP2 issue and applies to Dell notebooks. I
>> >> cannot
>> >> endorse this solution nor do I know that it has been analyzed by
>> >> Microsoft;
>> >> that is probably something that is already being worked on. Thus I
>> >> provide
>> >> this in case maybe you accidentally applied SP2 and did not realized
>> >> it;
>> >> SP2
>> >> is now distributed through Windows Update, automatically. SP2 is
>> >> called
>> >> KB811113.
>> >>
>> >> Brian Wehrle
>> >> bwehrle@online.microsoft.com
>> >> Software Test Engineer/Wireless Networking
>> >> Microsoft Corp.
>> >>
>> >> "paulchap" <paulchap@discussions.microsoft.com> wrote in message
>> >> news:64FD406C-9B6F-4D4A-BC34-F302AD8D7242@microsoft.com...
>> >> > 8/27/2004 2:27 PM PST
>> >> > xp pro problem performance after updates
>> >> >
>> >> > In: microsoft.public.windowsxp.perform_maintain
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > Senerio:
>> >> >
>> >> > On Friday August 13th around noon, I applied updates to a
>> >> > Windows XP Pro Server at Allsouth, They run an appraisal
>> >> > package WinTotal by Alamode software. I received calls
>> >> > that afternoon reporting severe degredation in performance
>> >> > especially noticable on wireless workstations (They have 4
>> >> > all within 20 feet of the wireless router and generally
>> >> > connect at 54mps). After several iterations of backing
>> >> > out and reinstalling Wintotal software and updating the
>> >> > firmware on the router we decided to hard wire the
>> >> > stations to allow the business to function. The following
>> >> > weekend I rolled back the XPPro server to July 31 removing
>> >> > several updates. This alleviated the problem. All
>> >> > wireless and wired workstations functioned correctly.
>> >> > Wintotal transfers large amounts of data across the
>> >> > network to the mapped drive. The following is a list of
>> >> > Windows updates that I appeared to remove with the
>> >> > rollback:
>> >> >
>> >> > KB840315
>> >> > KB839645
>> >> > KB823353
>> >> > KB867801
>> >> > KB841873
>> >> > KB842773
>> >> > KB870669
>> >> >
>> >> > The update I suspect is KB870669 which deals with reading
>> >> > and writing data to the hard drive. Any sugestions
>> >> > thoughts or comments would be greatly appreciated as I am
>> >> > reluctant to apply any more fixes to their server until
>> >> > this is resolved.
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Paul Chapman
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>
Anonymous
a b F Wireless
September 23, 2004 11:23:02 AM

Archived from groups: microsoft.public.windows.networking.wireless (More info?)

Brian,
Under this key, under windows xp is an sp0 with 1 kb fix and an sp2 with
many kb fixes and Q fixes also... Do you want a list of all the kb's.....

thanks

Paul

"Brian Wehrle [MSFT]" wrote:

> Paul,
>
> That sounds very strange. Could you please tell me where you are getting
> this information from? I can tell you that in the registry you can look at
> the fixes installed in the current location:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates
> (Please do not modify any registry keys, this is just for looking). So,
> could you tell me what you see in this key and its sub-keys?
> I am not sure what to do about your problem. Since you rolled back, could
> you need to roll-back once more?
> Since the systems are stable and working once again, perhaps it is a good
> idea just leave them be until you need to install SP2.
>
> Eventually you will want to, for stability and security reasons. At that
> point in time, you could test install the software (XP + SP2 +
> Applications), copy the application data over (via file shares) and then
> test this new system to make sure the problem is no longer happening (during
> non-business hours). Then you could bring this test system online and
> retire the other system.
>
> Brian
>
> --
> Brian Wehrle
> bwehrle@online.microsoft.com
> Software Test Engineer/Wireless Networking
> Microsoft Corp.
>
>
>
> "paulchap" <paulchap@discussions.microsoft.com> wrote in message
> news:D 389AE49-633F-48A9-8371-92B066E1A1FC@microsoft.com...
> > Brian, as of right now there are pieces of sp2 on the server even though I
> > rolled it back to July 31 to remove the fixes in question..... The XP
> > Server
> > was restored to that date but some sp2 fixes appear to be still applied
> > ??????
> >
> > thanks
> >
> > "Brian Wehrle [MSFT]" wrote:
> >
> >> Paul,
> >>
> >> This is very confusing! How do you mean that various pieces appear to be
> >> still on the system? I am not quite sure what you mean by that. In
> >> add/remove programs you should be able to see the pieces that have been
> >> added to the system (QFE's/KB's, SP's). I only understood that the SP2
> >> upgradecould be applied at once. Are you refering to the fact that later
> >> these pieces were subsumed into SP2 and that now you still have some of
> >> those KB's installed?
> >>
> >> If things are working fine, the only thing you can do is either go to SP2
> >> or
> >> leave it alone. The last KB you mentioned was a client-side fix anyways.
> >> It seems that if things are working now, and you are not considering
> >> going
> >> to SP2, that the machine is in an OK state and is performing acceptably.
> >> Without a way to test the actual problems there isn't much I can do to
> >> help
> >> you, because the problem is too broad, and I don't have your app here to
> >> look at. If you did install that fix and found that the server was then
> >> slow when copying files, I could get on that problem right away.
> >>
> >> In these situations it is great (!!) to have a Microsoft cluster solution
> >> installed. With MSCS you can have a pair of computers, with one machine
> >> in
> >> active stand-by that act as complete backup solution. When you upgrade,
> >> you
> >> do it to only one machine. Then, if that causes problems, you roll the
> >> file-shares over to the back-up node. Then you can analyze the problem,
> >> test the fix, roll the resources (file shares, WWW roots, database
> >> instances) back, etc. It is really fantastic for solving these kinds of
> >> problems.
> >>
> >> An equivalent is to just have two machines that are mirrors of each
> >> other.
> >> That way you can roll-up one machine, and if it works, put it into
> >> production. If it doesn't, you can fall back on the backup machine. If
> >> the data lives on a separate, external disk, this is a good solution, and
> >> gives you time to figure out what the problem might be while the customer
> >> is
> >> happily using the other server.
> >>
> >>
> >> --
> >> Brian Wehrle
> >> bwehrle@online.microsoft.com
> >> Software Test Engineer/Wireless Networking
> >> Microsoft Corp.
> >>
> >> "paulchap" <paulchap@discussions.microsoft.com> wrote in message
> >> news:C1A0A859-0260-4ED2-950C-71ACB07E9132@microsoft.com...
> >> > Brian the software does use files on the server & yes some SP2 pieces
> >> > were
> >> > installed however the appear to still be in place after the server
> >> > rollback
> >> > and everything is still running normally since I haven't reinstalled
> >> > the
> >> > particular KBs mentioned in the original posting.... ??? I don't think
> >> > it
> >> > was
> >> > an SP2 fix.... I believe it was the 669 kb......
> >> >
> >> > "Brian Wehrle [MSFT]" wrote:
> >> >
> >> >> Paul,
> >> >>
> >> >> It is hard to know exactly what is degrading performance on a system.
> >> >> It
> >> >> seems that you have resolved the problem by removing these updates,
> >> >> but
> >> >> that
> >> >> does not exactly show what is causing the problem. Obviously you
> >> >> would
> >> >> just
> >> >> like to get the problem fixed. Since this system is now restored,
> >> >> there
> >> >> is
> >> >> not much we can do to analyzed the situation right now.
> >> >>
> >> >> The software you mention is not known to me; this is not surprising,
> >> >> but
> >> >> without understanding exactly what the software does, it will be hard
> >> >> to
> >> >> identify the problems. Since you said there were problems on wired
> >> >> and
> >> >> wireless connections, it would be wise to test just raw file copies
> >> >> (i.e.
> >> >> a
> >> >> simple performance test)across the network:
> >> >>
> >> >> * Set up a file share on the XP Server
> >> >> * Run: xcopy /s BIGDIR \\srv\fileshare\tmp && rmdir /s /q
> >> >> \\srv\fileshare\tmp
> >> >> * Time this with a wired connection (100 Mbps)
> >> >> * Time this with your wireless connection (54 Mbps)
> >> >> * Re-Apply these KB's
> >> >> * Run these same tests
> >> >>
> >> >> I would be happy to try to reproduce the problem here, in fact, but I
> >> >> don't
> >> >> think it is the source of the problem. Rather, it sounds like there
> >> >> might
> >> >> be some other problem, perhaps related to a DB. Does this software
> >> >> package
> >> >> access a database on this same XP Pro server? Since the only KB here
> >> >> that
> >> >> you mentioned that has to do with a possible server-side component is
> >> >> the
> >> >> last one, KB870669, you can try just installing that one and see if
> >> >> the
> >> >> same
> >> >> problem happens again.
> >> >>
> >> >> If you can narrow it down to one KB it would be much easier to
> >> >> diagnose.
> >> >> I'll see what happens to my machine's performance when I install the
> >> >> same
> >> >> patches, but I feel that it probably has to do with this particular
> >> >> software
> >> >> package that you are using.
> >> >>
> >> >> There have been reports of similar-sounding SP2 problems, please read
> >> >> this
> >> >> link:
> >> >> http://news.zdnet.co.uk/software/windows/0,39020396,391...
> >> >> This apparently is an SP2 issue and applies to Dell notebooks. I
> >> >> cannot
> >> >> endorse this solution nor do I know that it has been analyzed by
> >> >> Microsoft;
> >> >> that is probably something that is already being worked on. Thus I
> >> >> provide
> >> >> this in case maybe you accidentally applied SP2 and did not realized
> >> >> it;
> >> >> SP2
> >> >> is now distributed through Windows Update, automatically. SP2 is
> >> >> called
> >> >> KB811113.
> >> >>
> >> >> Brian Wehrle
> >> >> bwehrle@online.microsoft.com
> >> >> Software Test Engineer/Wireless Networking
> >> >> Microsoft Corp.
> >> >>
> >> >> "paulchap" <paulchap@discussions.microsoft.com> wrote in message
> >> >> news:64FD406C-9B6F-4D4A-BC34-F302AD8D7242@microsoft.com...
> >> >> > 8/27/2004 2:27 PM PST
> >> >> > xp pro problem performance after updates
> >> >> >
> >> >> > In: microsoft.public.windowsxp.perform_maintain
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > Senerio:
> >> >> >
> >> >> > On Friday August 13th around noon, I applied updates to a
> >> >> > Windows XP Pro Server at Allsouth, They run an appraisal
> >> >> > package WinTotal by Alamode software. I received calls
> >> >> > that afternoon reporting severe degredation in performance
> >> >> > especially noticable on wireless workstations (They have 4
> >> >> > all within 20 feet of the wireless router and generally
> >> >> > connect at 54mps). After several iterations of backing
> >> >> > out and reinstalling Wintotal software and updating the
> >> >> > firmware on the router we decided to hard wire the
> >> >> > stations to allow the business to function. The following
> >> >> > weekend I rolled back the XPPro server to July 31 removing
> >> >> > several updates. This alleviated the problem. All
> >> >> > wireless and wired workstations functioned correctly.
> >> >> > Wintotal transfers large amounts of data across the
> >> >> > network to the mapped drive. The following is a list of
> >> >> > Windows updates that I appeared to remove with the
> >> >> > rollback:
> >> >> >
> >> >> > KB840315
> >> >> > KB839645
> >> >> > KB823353
> >> >> > KB867801
> >> >> > KB841873
> >> >> > KB842773
> >> >> > KB870669
> >> >> >
> >> >> > The update I suspect is KB870669 which deals with reading
> >> >> > and writing data to the hard drive. Any sugestions
> >> >> > thoughts or comments would be greatly appreciated as I am
> >> >> > reluctant to apply any more fixes to their server until
> >> >> > this is resolved.
> >> >> >
> >> >> > Thanks,
> >> >> >
> >> >> > Paul Chapman
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
!