Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > Group Policy > Correct way for applying GPO.
Ask a questionAsk a question
Search Forums:
 

AnswerCorrect way for applying GPO.

  • Friday, October 30, 2009 9:06 AMmypass604 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I am using Login script for Mapping drive at clinet side. In Windows Server 2003  I use GPO and write script in a bat file.


    NET USE x: \\SERVER_NAME\Sahre Folder Name /PERSISTENT:NO

    There are five  OU  and in each OU there are 10 users. For adding the bat file I use the following steps.

    Active Directrory Users and Computers .....>Right Click Domain Name ......>Properties......>Group Policy.....> Default Domain Policy...>Edit...User Configuration.....>Windows Settings......>Script.....>Login

    Please guide me that is it the correct way 

    1-  The above mentioned steps but under Group Policy I shall press "NEW" give it a name "Mapped Drive " and then press edit.

                                                                   or

    2- Right Click on each OU Properties......>Group Policy.....> Default Domain Policy.

    Please guide me the professional way .

    thanks in advance.
    mypass


     

Answers

  • Friday, October 30, 2009 10:08 AMFlorian FrommherzMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Think about 1 and 2. Don't alter the Default Domain Policy directly - either create your own GPO at the domain level or link it to the OUs. Either way is correct. It just depends on whether you really want _ALL_ users of the domain (even those in the Users container and evrey new user you create in any new OU you create) to have that script applied (-> GPO on domain level) or whether you want newly created users to NOT apply the GPOs automatically unless they're in the five specified OUs.

    cheers,
    Florian

    Microsoft MVP - Group Policy (http://www.frickelsoft.net/blog)
     
  • Friday, October 30, 2009 5:45 PMFlorian FrommherzMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Yeah, that is the better approach to tackle it.

    Again, to repeat myself, this approach would result in _all_ users getting the drives mapped: not only those in the OUs but also the users in the "Users" builtin container. That results in all new users created having the mapped drives.

    Florian
    Microsoft MVP - Group Policy (http://www.frickelsoft.net/blog)
     

All Replies

  • Friday, October 30, 2009 10:08 AMFlorian FrommherzMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Think about 1 and 2. Don't alter the Default Domain Policy directly - either create your own GPO at the domain level or link it to the OUs. Either way is correct. It just depends on whether you really want _ALL_ users of the domain (even those in the Users container and evrey new user you create in any new OU you create) to have that script applied (-> GPO on domain level) or whether you want newly created users to NOT apply the GPOs automatically unless they're in the five specified OUs.

    cheers,
    Florian

    Microsoft MVP - Group Policy (http://www.frickelsoft.net/blog)
     
  • Friday, October 30, 2009 3:55 PMmypass604 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    thanks for the reply. Well it seams good practice if we don't change the default GPO. I think assigning Mapp drives to all users in AD under Group Policy I should click button and make my own GPO with named "Mapp Drives Script"

    What u say about it now?

    thanks.
     
  • Friday, October 30, 2009 5:45 PMFlorian FrommherzMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Yeah, that is the better approach to tackle it.

    Again, to repeat myself, this approach would result in _all_ users getting the drives mapped: not only those in the OUs but also the users in the "Users" builtin container. That results in all new users created having the mapped drives.

    Florian
    Microsoft MVP - Group Policy (http://www.frickelsoft.net/blog)
     
  • Saturday, October 31, 2009 2:55 AMmypass604 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    well thanks again for your reply. If for specific OU I want to make make drive then I should right click on that specific OU like "Marketing" and them properties and GPO. In this way it will not affect  the whole AD users.

    2-I want to know that is there any utility on server 2003 R2 that I can see  the mapp drive is  connected  or disconnected of AD users. Or there is any Script? please let me guide about it.

    thanks
    mypass
     
  • Thursday, November 05, 2009 8:58 AMMervyn ZhangMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    On the server, open Computer Management, open Shared Folders, open Sessions, you would find all users who connect to the server.

    Thanks.
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
  • Friday, November 06, 2009 11:12 AMmypass604 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    thanks for the reply.In case of windows server 2008 where I can see the users who are connected to the server?
     
  • Monday, November 09, 2009 5:40 AMMervyn ZhangMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    Try to open:

    Control Panel-> Administrative Tools-> share and Storage Management-> Select one share folder, click Manage Sessions in the right-panel.

    Thanks.
    This posting is provided "AS IS" with no warranties, and confers no rights.