Same here deployed or in the process of being deployed and so far only one
machine with any kind of issue but it has a lot of stuff on it I would have
baned a long time ago if I could have.

Jon

On Thu, Apr 16, 2009 at 12:34 PM, Bill Lambert <[email protected]>wrote:

> Did several test machines yesterday and all are good...XP clients and
> W2K3 servers.
>
> Bill Lambert
> Concuity
> 847-941-9206
>
>
> -----Original Message-----
> From: Andy Ognenoff [mailto:[email protected]]
> Sent: Thursday, April 16, 2009 11:27 AM
> To: NT System Admin Issues
>  Subject: RE: Anybody else having patch deployment issues?
>
> I had 5 WinXP clients not allow logins after rebooting this morning -
> login
> screen was frozen.  Had to reboot several times to be able to log in.  I
> also rolled out NOD32 v4 last night though so I don't know which update
> caused it.
>
>  - Andy O.
>
> >-----Original Message-----
> >From: Bill Monicher [mailto:[email protected]]
> >Sent: Wednesday, April 15, 2009 5:31 PM
> >To: NT System Admin Issues
> >Subject: Anybody else having patch deployment issues?
> >
> >I'm deploying today's crop of MS patches to my first wave test set,
> >and I've had 3 of 'em hang during installation so for.
> >
> >Might be caused by (or the cause of?) my update server having network
> >problems.
> >
> >Lots of other things happening on machines being patched, such as
> >20-30 second periods of apps "not responding"
> >
> >Don't notice it on machines not being patched.
> >
> >--V
> >
> >~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> >~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to