Re: Inconsistent Group Policy behavior
From: Eric Voskuil (voskuil_at_online.autoprof.com)
Date: 04/18/04
- Next message: metsalam: "Favorites folder redirection"
- Previous message: metsalam: "Num Lock"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 18 Apr 2004 02:56:17 -0400
Paul,
It's not clear to me what's going on here, but it looks like it should work.
You might want to try simplifying the problem until you can find which part
of it is not working.
The Policy Maker Printers policy extension makes this ridiculously simple
and easy to troubleshoot. You can map all of your printers in one GPO if
you want. You can use one of the many per-item filters to target the
appropriate groups. It's all point and click just like other graphical
policies, and you get per-item event logging, tracing, and RSoP reporting
for each printer. You won't get any of that from scripting, making it more
complicated to set up and difficult to troubleshoot.
Regards,
Eric Voskuil
Policy Maker
http://www.autoprof.com/policy
"Paul Ledbetter" <anonymous@discussions.microsoft.com> wrote in message
news:1d28201c42326$fe0d7240$a401280a@phx.gbl...
> I have a Windows Server 2003 domain controller running in
> native mode. I want to set up Group Policies that assign
> mapped drives through the NET USE command in a DOS batch
> file dependent on which group a user belongs to at logon
> time. For example, everyone will be assigned a "P:"
> drive as an Authenticated User. Users belonging to the
> MIS Group will be assigned an "X:" drive, and users in
> the Accounting Group will be assigned an "R:" drive. In
> addition, there is a subset of accountants who will also
> require an "I:" and an "S:" drive.
>
> To accomplish this, I set up a hierachial OU structure,
> assigning different Group policies at different points in
> the hierachy. For example, the MIS and Accounting OUs
> are both subordinate to the domain. Subordinate to the
> Accounting OU are the AcctgHist and AcctgExecs OUs
> respectively. AcctgExecs is subordinate to AcctgHist.
> Users are assigned to each OU, depending on what drives
> they need mapped.
>
> My expectation is that when a user logs in, since they
> are logged into the domain, they get assigned drive "P:",
> as stated in the login script associated with the logon
> section of that respective Group Policy. If the user is
> actually in <Domain>\Accounting OU\AcctgHist OU, then I
> would expect that when they log in, first, the logon
> script associated with the domain would be run, then that
> of Accounting OU, then that of AcctgHist. Similarly,
> someone in the MIS OU would see the login script run for
> the domain, then that for the MIS OU. Right now, only
> the login scripts for MIS run completely. For the
> accountants, the only logon script that is run is that
> for the Group Policy related to the domain.
>
> For example, when an MIS person logs in, the following
> drives are mapped:
> H: Home drive, in the user's profile
> P: Public Drive, from the logon script associated with
> the domain Group Policy
> X: Downloads drive, from the logon script associated with
> the MIS OU Group policy.
>
> When my accountants log in, they only get the H: and P:
> drives. They should also get:
>
> R: History drive, from the login script associated with
> the AcctgHist OU Group policy
>
> If they are managers, they should also get:
> I: and S: From the login script associated from the
> AcctgExecs OU Group policy.
>
> Can anybody out there help?
- Next message: metsalam: "Favorites folder redirection"
- Previous message: metsalam: "Num Lock"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
