![remote desktop server 2016 not mapping local drives remote desktop server 2016 not mapping local drives](https://patrick6649.files.wordpress.com/2017/08/2.jpg)
Configuring item-level targeting for drive mapping. Under the Common tab of the mapped drive properties, check the Item-level targeting option, and then click Targeting…. Refer to Figure 4 below.įigure 4.In our example of configuring drive mapping, only users in the Product Managers group would receive the mapping. ILT options for Group Policy preferences. The criteria available for targeting settings to users and computers can be seen below in Figure 3.įigure 3. Item-level targeting (ILT) is a feature of Group Policy preferences that allows preference settings to be applied to individual users and/or computers dynamically. ILT allows an administrator to specify a list of conditions that must be met in order for a preference setting to be applied or removed to a user or computer object. Once the Group Policy settings have taken effect on the desired users/computers, the mapped drives should automatically appear under Network Location(s) as seen in Figure 2.ĭeploying item-level targeting with Group Policy preferences Configuring general properties for drive mapping.įor the settings to take effect, open a Command Prompt in the computer receiving the drive mapping, type GPUPDATE, and hit Enter.
![remote desktop server 2016 not mapping local drives remote desktop server 2016 not mapping local drives](https://i.stack.imgur.com/SFib5.png)
Hide/Show all drives: Select whether, by default, all the shared drives/folders are hidden or visible.įigure 1. Hide/Show this drive: Select whether you want to hide the folder or make it visible on the network.
![remote desktop server 2016 not mapping local drives remote desktop server 2016 not mapping local drives](https://www.terminalworks.com/blog-images/blobs/post_161/blobid237.png)
Remote desktop server 2016 not mapping local drives windows#
Label as: Pick a suitable name for the shared drive, e.g. SharedDrive.ĭrive Letter: Select a suitable letter for the drive, e.g. K.Ĭonnect as: Enter a username and password if you want users to connect with certain credentials other than their own Windows login credentials.
![remote desktop server 2016 not mapping local drives remote desktop server 2016 not mapping local drives](https://martinsblog.dk/wp-content/uploads/2019/07/img_5d30587d504ea.png)
Reconnect: Enable this to auto connect the drive. Location: Specify the full file path, e.g. \\Anjali-dc1\c. Under the General tab (see Figure 1 below), do the following: Right-click and select New > Mapped Drive. Go to User Configuration > Preferences > Windows Settings > Drive Maps. Right-click and select Edit to open the Group Policy Management Editor. Right-click the domain or the required subfolder to create a new GPO, or select an already existing one. The Drive Maps policy in Group Policy preferences allows an administrator to manage drive letter mappings to network shares. Administrators can use them to deploy and manage applications on client computers with configurations targeted to specific users. Group Policy preferences are a set of extensions that increase the functionality of Group Policy Objects (GPOs). Setting up drive mappings with Group Policy preferences However, more recently, administrators have found an effective alternative in Group Policy preferences and are increasingly making the switch. Mapping network drives using Group Policy preferences is flexible, provides easy control over who receives the drive mappings, and has easy-to-use user interfaces, all of which are in stark contrast with the complexities associated with scripts. For years, IT administrators have been relying on logon scripts for mapping users’ network drives in a Windows domain environment.