Re: Startup Script To Map Printer depending on OU
- From: "Pete Appleyard" <PeteAppleyard@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 26 Apr 2005 05:21:03 -0700
Hi Mike.
We've got it sorted now. What we've done is create a batch file for each
printer that maps it to the local machine when a user logs on. Then, using
MSI's, we send out the batch files to the startup folders on each machine.
A bit of a crude way to do it but it works ok!
Thanks for your help,
Pete
"Miha Pihler [MVP]" wrote:
> Pete,
>
> Can you post the script that you are using...
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Pete Appleyard" <PeteAppleyard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:5359CA4D-88D7-4384-9514-ADE437227C56@xxxxxxxxxxxxxxxx
> > Hi Mike,
> >
> > Thanks for your quick reply.
> >
> > I have checked the logs and RSoP and can't see anything out of the
> > ordinary.
> > The RSoP shows that the policy is filtering down properly.
> >
> > We are running Server 2003 with XP on all clients.
> >
> > Our script works if you run it while logged on to the computer, it's just
> > trying to run it as a startup script that fails.
> >
> > Regards,
> >
> > Pete
> >
> > "Miha Pihler [MVP]" wrote:
> >
> >> Hi Pete,
> >>
> >> If you are running a startup script are computer accounts in this OU
> >> where
> >> you applied the policy?
> >>
> >> On which operating system are you running these scripts? Windows XP? Can
> >> you
> >> check RSoP to see if the policy gets applied?
> >> Also check event logs (System and Application) for any errors.
> >>
> >> --
> >> Mike
> >> Microsoft MVP - Windows Security
> >>
> >> "Pete Appleyard" <PeteAppleyard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> >> message
> >> news:1AB34CAC-DC46-4261-8A6F-C59132B4B474@xxxxxxxxxxxxxxxx
> >> > Hi.
> >> >
> >> > Me and my colleague have been trying for a while now to create a script
> >> > to
> >> > add a printer to a computer depending on the OU the computer's in.
> >> >
> >> > We have suceffully created a bath file that adds a printer to the
> >> > machine.
> >> > This works fine. We can also add it to the logon scripts so that it
> >> > runs
> >> > per
> >> > user.
> >> >
> >> > However, when we create a startup script in a Group Policy for an OU,
> >> > the
> >> > script doesn't work.
> >> >
> >> > I was just wondering if there was another way to do this that anyone
> >> > knows
> >> > of. I can't seem to find anything at all on the net about it.
> >> >
> >> > Thanks in advance for any help.
> >> >
> >> > Cheers,
> >> >
> >> > Pete Appleyard
> >>
> >>
> >>
>
>
>
.
- References:
- Startup Script To Map Printer depending on OU
- From: Pete Appleyard
- Re: Startup Script To Map Printer depending on OU
- From: Miha Pihler [MVP]
- Re: Startup Script To Map Printer depending on OU
- From: Pete Appleyard
- Re: Startup Script To Map Printer depending on OU
- From: Miha Pihler [MVP]
- Startup Script To Map Printer depending on OU
- Prev by Date: Installed 2003 SP1 now Win 98 clients won’t log in
- Next by Date: Re: Load Balancing Windows 2003 Enterprise...
- Previous by thread: Re: Startup Script To Map Printer depending on OU
- Next by thread: Question preparing forest for W2k3 DC install
- Index(es):
Relevant Pages
|