Printer deploying causing slow down

[Guest OneWaySWB]

Hello,

 

I am not sure if this is the right newsgroup for my issue but here it goes:

 

We are deploying 10 printers via login script (vbs script) to users. After

logging in the workstation will be extremely slow for about 20-30 minutes. I

check with task manager and it showed csrss.exe was consuming much of the cpu

cycles. So, I ran process explorer to check what was causing the issue. I

found many regsvr32.exe threads popping in and out taking up the CPU time;

sometimes there would be up to ten at a time. I was finally able to catch

one as to what was being registered and it was a printer driver. The

workstations are GX260 P4 2.0GHz 256Mb ram running Windows XP sp2 and joined

to a AD domain.

 

Should the registering of the printer dlls slow down the workstations to

where it takes 3-4 minutes for Microsoft word, firefox or IE to open? If

not, does anyone know what I can check?

 

We are not ready for Windows 2003 R2 yet but is there another way to deploy

the printers that would avoid this high CPU use?

 

Thanks,

Steve

[Guest R. Paulson]

RE: Printer deploying causing slow down

 

Did you deploy with IP addresses? Jet direct? how? Are they registered in

DNS? Is the script bieng sent via GPOs? Or AD link? btw, I'd go batch file if

you are on W2k servers... More details are needed.... If not... and your DNS

servers are working correctly... and your machines are not releying on

NetBIOS, then....Congratulations you have a virus...

 

"OneWaySWB" wrote:

> Hello,

>

> I am not sure if this is the right newsgroup for my issue but here it goes:

>

> We are deploying 10 printers via login script (vbs script) to users. After

> logging in the workstation will be extremely slow for about 20-30 minutes. I

> check with task manager and it showed csrss.exe was consuming much of the cpu

> cycles. So, I ran process explorer to check what was causing the issue. I

> found many regsvr32.exe threads popping in and out taking up the CPU time;

> sometimes there would be up to ten at a time. I was finally able to catch

> one as to what was being registered and it was a printer driver. The

> workstations are GX260 P4 2.0GHz 256Mb ram running Windows XP sp2 and joined

> to a AD domain.

>

> Should the registering of the printer dlls slow down the workstations to

> where it takes 3-4 minutes for Microsoft word, firefox or IE to open? If

> not, does anyone know what I can check?

>

> We are not ready for Windows 2003 R2 yet but is there another way to deploy

> the printers that would avoid this high CPU use?

>

> Thanks,

> Steve

>

[Guest OneWaySWB]

RE: Printer deploying causing slow down

 

 

 

"R. Paulson" wrote:

> Did you deploy with IP addresses? Jet direct? how? Are they registered in

> DNS? Is the script bieng sent via GPOs? Or AD link? btw, I'd go batch file if

> you are on W2k servers... More details are needed.... If not... and your DNS

> servers are working correctly... and your machines are not releying on

> NetBIOS, then....Congratulations you have a virus...

>

> "OneWaySWB" wrote:

>

> > Hello,

> >

> > I am not sure if this is the right newsgroup for my issue but here it goes:

> >

> > We are deploying 10 printers via login script (vbs script) to users. After

> > logging in the workstation will be extremely slow for about 20-30 minutes. I

> > check with task manager and it showed csrss.exe was consuming much of the cpu

> > cycles. So, I ran process explorer to check what was causing the issue. I

> > found many regsvr32.exe threads popping in and out taking up the CPU time;

> > sometimes there would be up to ten at a time. I was finally able to catch

> > one as to what was being registered and it was a printer driver. The

> > workstations are GX260 P4 2.0GHz 256Mb ram running Windows XP sp2 and joined

> > to a AD domain.

> >

> > Should the registering of the printer dlls slow down the workstations to

> > where it takes 3-4 minutes for Microsoft word, firefox or IE to open? If

> > not, does anyone know what I can check?

> >

> > We are not ready for Windows 2003 R2 yet but is there another way to deploy

> > the printers that would avoid this high CPU use?

> >

> > Thanks,

> > Steve

> >