Differences

This shows you the differences between two versions of the page.

--- microsoft:server:2016:drvmap_gp [2026/05/12 11:09] – sysadmin
+++ microsoft:server:2016:drvmap_gp [2026/05/12 11:52] (current) – sysadmin
@@ Line 4: / Line 4: @@
 Copied from [[https://activedirectorypro.com/map-network-drives-with-group-policy/|HERE !!!]]
-===Logon Scripts VS Group Policy===
-The ability to map a network drive with Group Policy was introduced in Server 2008.
-Logon scripts are a thing of the past.
-Logon scripts can actually slow computers down. Yes, group policy is faster.
-Unless you have some crazy complex script that does something that Group Policy cannot do then there is no reason not to use it.
-Mapping Drives with Group Policy has the following advantages:
+====Example 1: Map a Department Network Drive Using Group Policy====
-  * It’s much easier than logon scripts. Checkboxes and drop down lists, no need to understand scripting
-  * It’s scalable. GPO mapped drives can handle very large Active Directory environments.
-  * It’s very flexible. With item level targeting you can target groups, users, OUs, operating systems, and so on.
-  * It’s easy
-Now let’s move on to some examples of mapping drives with group policy.
-===Example 1: Map a Department Network Drive Using Group Policy===
 In this example, I’m going to map a network drive for the HR department. I’ll use item level targeting so it only maps this drive for users in the HR organizational unit.
@@ Line 29: / Line 15: @@
 **1. Open the Group Policy Management Console**
-[slija]
+{{ :microsoft:server:2016:GPO-Map-Drives-1.jpg?300 }}
 **2. In the Group Policy Management Console, Right Click and Select “Create a GPO in this domain, and Link it here”**
@@ Line 35: / Line 21: @@
 //TIP: This will be a user based GPO so make sure you link the GPO to a location that will target the users.  I have all of my users separated into an OU called ADPRO Users, I’ll create and link the GPO there.//
-[slija]
+{{ :microsoft:server:2016:GPO-Map-Drives-2.jpg?400 }}
 **3. Name the new GPO**
@@ Line 43: / Line 29: @@
 I can later add additional drive mappings to this GPO.
-[3]
+{{ :microsoft:server:2016:GPO-Map-Drives-3.jpg?400 }}
 The new GPO is now created and linked, now it’s time to configure the settings.
@@ Line 51: / Line 37: @@
 **1. On the GPO right click and select edit**
-[4]
+{{ :microsoft:server:2016:GPO-Map-Drives-4.jpg?400 }}
 **2. Navigate to User Configuration -> Preferences -> Windows Settings -> Drive Mappings**
+{{ :microsoft:server:2016:GPO-Map-Drives-5.jpg?400 }}
-[5]
 **3. Right Click Drive Mappings, Select New – > Mapped Drive**
-[6]
+{{ :microsoft:server:2016:GPO-Map-Drives-6.jpg?400 }}
@@ Line 71: / Line 56: @@
   * Label as: This is optional but may be beneficial for users.
-[7]
+{{ :microsoft:server:2016:GPO-Map-Drives-7.jpg?400 }}
 Common Tab Settings
@@ Line 81: / Line 66: @@
 Click the Targeting Button
-[8]
+{{ :microsoft:server:2016:GPO-Map-Drives-8.jpg?400 }}
 Select New Item
@@ Line 87: / Line 72: @@
 Select Organization Unit then select the OU you want to target
-[9]
+{{ :microsoft:server:2016:GPO-Map-Drives-9.jpg?600 }}
 Click OK, Click OK again to close the new drive properties
@@ Line 98: / Line 83: @@
 I’ve rebooted the computer, now I’ll log in with an account that is in the HR organizational unit.
-[10]
+{{ :microsoft:server:2016:GPO-Map-Drives-10.jpg?400 }}
 Once logged I will go to file explorer and check for the mapped drive.
-[11]
+{{ :microsoft:server:2016:GPO-Map-Drives-11.jpg?600 }}
 It works.
-Now, any user I put in the HR folder will get this mapped drive. If you don’t want to use an OU you can also target a group of users by using a Security group.
+Now, any user I put in the HR folder will get this mapped drive. If you don’t want to use an OU you can also target a group of users by using a Security group.3
+====Example 2: Using Group Policy to Map a Drive for Individual Users====
+This example will map a drive for individual users. This will give the users their own personal folder to save files.
+You can create a new GPO or add to your existing one, I have all my drive mappings in one GPO.
+This example requires a folder to be setup on a network share that matches the user’s logon name. You will want to modify the NTFS permissions so the individual user is the only one that has permissions to it.
+I’ll be using Mark Foster as an example, the logon name is mfoster so I’ll need a folder setup on a network share called mfoster.
+//I’m not going to repeat every step, I’m basically starting at Step 3 from the first example.//
+===Step 1: Create a New Drive Mapped drive===
+Here are the drive map settings for mapping a drive for an individual user
+The %UserName% is a variable that will match the user’s logon name.
+{{ :microsoft:server:2016:GPO-Map-Personal-1.jpg?400 }}
+Just to be clear you must have folders setup on a network share that matches the location and users logon name.
+My file server is file1, the share is users and in the user’s folder is a folder for each user. Screenshot below of users folder on file1 server.
+{{ :microsoft:server:2016:GPO-Map-Personal-2.jpg?400 }}
+That is it.
+Just have the user log off and back on and it should map the M drive
+{{ :microsoft:server:2016:GPO-Map-Personal-3.jpg?600 }}
+Perfect! Now the user is mapping a department drive and a personal drive.