TVITBRIAN

Okay here's a run down of the situation. Got a Server 2003 domain. Got 3
servers, 2 are domain controllers. One of the domain controllers runs Server
2003 Standard SP2 the other R2. The one running Standard lets call
"labserver" the one running r2 lets call "server2003". labserver shares out
all the printers. Server2003 pushes the printers to the machines via group
policy and print management(feature of R2). This is a school. There are
several labs. All the students use a mandatory profile. All the lab machines
are cloned exactly alike. Here's my problem. Sometimes when the students try
to print it says that the printers aren't installed correctly. Basically that
there isn't a driver installed for the printer. Even though it's being pushed
VIA startup with group policy. But here's the kicker, it doesn't happen to
every student. Just random ones at random times. Everyone will be able to
print just fine for days and then all of a sudden printing problems. Does
anyone have any ideas? Please help.

Dallas

Hi, Sorry I have no solution but I can tell you I am having the same
experience.
Once again roaming mandatory profiles. Our printers though are on the same
R2 server that is used to manage printers.
It can happen at random whether or not the printer gets installed for the
user. If it is not installed sometimes logging off then back on will install
the printer.
I am aware that you can increase logging when you use the
"PushPrinterConnections.exe in the Script Name box.
If you want to enable logging, type –log in the Script Parameters box. Log
files are written to %windir%\temp\ppcMachine.log (for per-computer
connections) and %temp%\ppcUser.log (for per-user connections) on the
computer on which the policy is applied."
As our clients are all vista we are not using the script to push printers
and need some other way of logging.

TVITBRIAN

Do you by any chance have a program called CleanSlate installed?



"Dallas" wrote:

> Hi, Sorry I have no solution but I can tell you I am having the same
> experience.
> Once again roaming mandatory profiles. Our printers though are on the same
> R2 server that is used to manage printers.
> It can happen at random whether or not the printer gets installed for the
> user. If it is not installed sometimes logging off then back on will install
> the printer.
> I am aware that you can increase logging when you use the
> "PushPrinterConnections.exe in the Script Name box.
> If you want to enable logging, type –log in the Script Parameters box. Log
> files are written to %windir%\temp\ppcMachine.log (for per-computer
> connections) and %temp%\ppcUser.log (for per-user connections) on the
> computer on which the policy is applied."
> As our clients are all vista we are not using the script to push printers
> and need some other way of logging.

Dallas

Hi,
No we do not have cleanslate. It is just Windows Vista Enterprise with
office 2007. We do have abtutor installed though.

"TVITBRIAN" wrote:

> Do you by any chance have a program called CleanSlate installed?
>
>
>
> "Dallas" wrote:
>
> > Hi, Sorry I have no solution but I can tell you I am having the same
> > experience.
> > Once again roaming mandatory profiles. Our printers though are on the same
> > R2 server that is used to manage printers.
> > It can happen at random whether or not the printer gets installed for the
> > user. If it is not installed sometimes logging off then back on will install
> > the printer.
> > I am aware that you can increase logging when you use the
> > "PushPrinterConnections.exe in the Script Name box.
> > If you want to enable logging, type –log in the Script Parameters box. Log
> > files are written to %windir%\temp\ppcMachine.log (for per-computer
> > connections) and %temp%\ppcUser.log (for per-user connections) on the
> > computer on which the policy is applied."
> > As our clients are all vista we are not using the script to push printers
> > and need some other way of logging.

Dallas

Oh I should add that symantec 10.2.xxxx is the antivirus of choice.
I have come to a conclusion that it is a bug and hopefully will be fixed in
the next service pack. Our workaround for now is to install the printer
locally then redirecting the local port to the network printer.

"TVITBRIAN" wrote:

> Do you by any chance have a program called CleanSlate installed?
>
>
>
> "Dallas" wrote:
>
> > Hi, Sorry I have no solution but I can tell you I am having the same
> > experience.
> > Once again roaming mandatory profiles. Our printers though are on the same
> > R2 server that is used to manage printers.
> > It can happen at random whether or not the printer gets installed for the
> > user. If it is not installed sometimes logging off then back on will install
> > the printer.
> > I am aware that you can increase logging when you use the
> > "PushPrinterConnections.exe in the Script Name box.
> > If you want to enable logging, type –log in the Script Parameters box. Log
> > files are written to %windir%\temp\ppcMachine.log (for per-computer
> > connections) and %temp%\ppcUser.log (for per-user connections) on the
> > computer on which the policy is applied."
> > As our clients are all vista we are not using the script to push printers
> > and need some other way of logging.