Re: Re: Running an OU policy only after a previous OU policy com
- From: CraigD <DoNotEmail@xxxxxxxxxxxxxxxxx>
- Date: 12 May 2005 12:35:43 -0400
"lforbes" wrote:
> Hi,
>
> That may be your problem. I have never had much luck adding
> Printers with .vbs logon scripts because regular users don't
> usually have write access to the Winnt directory where the
> computer needs to copy the printer drivers. You can't add a
> printer with a vbs startup script because the engine doesn't
> load in time and you get the error.
>
> I use VBS for everything but adding printers and mapping
> drives. That I do with the batch files.
>
> Type rundll32 printui.dll,PrintUIEntry /? at the command line
> to get a list of help.
>
> What I meant about the users login as well.
>
> My printers are added per computer. However, this is a
> PERMANENT add so it is there for everyone who logs on until
> you delete it either manually or with the delete printer
> script (note the /dl for delete)
> rundll32 printui.dll,PrintUIEntry /dl /q /n "\serverprinter"
>
>
> I have a Computer OU (with all the computers in it) where I
> Add a Computer Group Policy. In the Computer Configuration
> section I enable the Looback Processing Mode (admin
> temp-system-group policy) with "Merge". What this does is
> anything in the User Configuration of the COMPUTER Group
> Policy gets "merged" with the Users regular group policy. In
> the Computer Configuration (computer GP) I put the Startup
> Script and in the User Configuration I put the Same as a Logon
> Script.
>
> What this means is when a computer in room 111 starts up, it
> adds the Room 111 printer to the computer and copies the
> printer drivers from the server. A User logs into that
> computer and the Room 111 Printer is "readded" as a login
> script. I set the default at the login script as well.
>
> The reason I have to use the login script is for the Windows
> XP machines. For some reason when you add it to the computer
> in Windows XP it shows up in the registry but not in the
> Printers Section.
>
> Cheers,
>
> Lara
Thanks Lara,
That?s a good explanation. Just a few more questions.
I created a Computer OU, and added a test computer. In the startup
script section of the Computer Config. I have the following:
# Map printers
rundll32 printui.dll,PrintUIEntry /in /q /n
"\\DOMAIN1\CanoniR550"
rundll32 printui.dll,PrintUIEntry /in /q /n
"\\DOMAIN1\CanoniR330"
rundll32 printui.dll,PrintUIEntry /in /q /n "\\DOMAIN1\IBM24"
# Map drives
net use G: \\DOMAIN1\COMMON
net use K: \\Domain1\APPLICATIONS
net use H: \\Domain1\Data
Now, you also add the exact same thing to the login script of the User
Config in the Computer OU?
When I did this, things looked good, except for the mapped drives,
they show up as, example: "Disconnected Network Drive (G:), although
they are really connected and I can see the contents. Can this be
fixed to show up as normal like "Common on \\DOMAIN1"?
To recap, by having the exact same script in 2 places, when you make
a change, you have to remember to do it in 2 places I guess?
Thanks!
.
- References:
- Prev by Date: How can I reaply Software-Install distributed via GPO
- Next by Date: log off script and VPN
- Previous by thread: Re: Re: Running an OU policy only after a previous OU policy com
- Next by thread: preventing domain choices from display
- Index(es):
Relevant Pages
|