Wolfcrazy
Fri Jun 09 09:00:03 CDT 2006
Because printers are connected on a per profile basis and a startup script
runs as System I have launched my VB printer script as a logon script and not
a startup script. User Configuration -> Windows Settings -> Scripts -> Logon
This way the scripts runs using the users credentials and adds themselves to
the users profile.
Hopefully this helps.
David
"Springside" wrote:
> Thank you, but this unfortunately did not help.
>
> "Richard Mueller" wrote:
>
> > Springside wrote:
> >
> > > I'm trying to create a startup script for WinXP workstations via Win 2003
> > > server. I have the VB script for adding printers and can run them
> > > successfuly when running directly on the workstation. However, when I
> > > assing
> > > the script via GPO in Active Directory as a startup script, the script
> > > does
> > > not run. Upon starting up, the machine shows "startup scripts," but once
> > > I'm
> > > logged on no printers appear. I have de-activated Windows Firewall in
> > > hopes
> > > that that was the culprit, to no avail. Any help here will be greatly
> > > appreciated.
> > > Thanks in advance,
> > > Vince
> >
> > If the script works when you run it as yourself, but not during startup, it
> > is probably a permission issue. Startup scripts run with System permissions
> > on the local machine, but with the permissions of the computer object in the
> > domain. If you access resources in the domain, the computer needs
> > permissions. I generally grant such permissions to the "Domain Computers"
> > group, rather than each computer object individually.
> >
> > --
> > Richard
> > Microsoft MVP Scripting and ADSI
> > Hilltop Lab -
http://www.rlmueller.net
> >
> >
> >