Skip to main content

How to create a drive map with GPO Preferences

Once you have your shared folders correctly configured, you can use Group Policy Preferences to configure the drive mappings on your clients.  This is a nice improvement from the days of using VBScript to map drives on your clients and it also saves us a lot of time in customizing the drive mappings.
In your Group Policy Management Console, either use an existing GPO, or create a new one.  In this case, I created a GPO called DriveMappings.

Expand User Configuration \ Preferences \ Drive Maps

Right click Drive Maps and select New \ Mapped Drive














In the New Drive Properties window, fill in the information below

In the Action: field, select Create

In the Location field, select the UNC path to your share.

In the Label as: field, provide a name.

In the Drive Letter: area, choose what is appropriate

Click OK.

image

If you want to designate a mapped drive for different users, you can use security groups to determine which users get which location mapped to them.  That way Drive G will point to one location for one set of users and drive G will point to another location for other users.

In the New Drive Properties window, click the Common tab.

Check the Item-level targeting check box and click the Targeting… button.

image

Click New Item.

From the drop down box, select Security Group.

image


To the right of the Group field, click the image Button.

Add in the security group that you want this drive mapping to apply to and click OK.

If you are concern about conflicts with other security groups that a user may be a member of, you can check the Primary Group check box.

image

That will set this preference to only process if the specified group is the users primary group.  To set a group as a primary group for a user, open that users object in Active Directory Users and Computers.

Click the Member Of tab.

Click the group that you want to make as the primary group for that user.

Click the Set Primary Group Button.

image

Comments

thanks said…
thank you ..
Hello said…
could you help me..

I have tried to do the same steps with Organization Unit instead of group, but the user can’t see the drive in the computer.

Is it because of the Organization Unit?
Thank you.

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...