![]() In my case, I have created an Accounting folder on the file server FileServer1 and shared it with the Accounting Dept security group read/write access to it. Enter the location of the shared folder you are wanting to push to your users.In the box that opens, choose Update for the Action (since we want to push a new drive rather than replace an existing drive).Right click on Drive Mappings and then click on New -> Mapped Drive.Expand User Configuration -> Preferences-> Windows Settings -> Drive Mappings.Right click the OU that you want to link the new GPO to and click on “Create a GPO in this domain, and Link it here….” This will be a user GPO so you’ll want to link it to the OU that contains your user accounts.Open Group Policy Management with a privileged account.You could just as easily use item level targeting to push out drives by OU or a number of other things, which we’ll get into during the tutorial. Here we are going to a create a group policy using item level targeting to push out a mapped network drive for Accounting based on a user’s membership to the Accounting security group. How to Map a Drive for Departmental Use with Group Policy Let’s take a look at the most common use for mapping network drives with group policy, departmental network shares. Since group policy is tightly integrated with your Active Directory, it’s very scalable. This lets you control exactly who and what gets your policy to push out your drive. The ability to use item level targeting is also huge for the group policy method. It can decrease logon times since scripts have to run every time the user logs in. Using group policy over scripting is also more efficient. Mapping Drives with Group Policy vs Logon ScriptsĪs mentioned earlier, group policy tends to be much easier for most admins to understand than scripting. This guide will walk you through each step of pushing out a mapped drive as well as taking advantage of item level targeting to make sure that drive only goes to who and what you want it to. Not only is it easier to understand for people who aren’t into scripting, it’s also easier to keep track of and audit. Unfortunately, the error message generated doesn't really tell you where to start looking.Using group policy is the ideal method of mapping network drives. With all that said, the issue seems to be associated with the 'more secure environment' created with DSM 7. I have reversed the regedit change & it is now back to where it was prior to the change. To say I'm a little disappointed with DSM 7 would be an understatement. I intentionally delayed upgrading to DSM 7 to allow time for the upgrade to settle down. Unfortunately, these are production PC's/NAS devices with established processes & users that are accustomed to accomplishing tasks in certain ways. What was once an easy task, has now become an exercise in WTF is going on? Both the NAS & the PC were rebooted, but, still did not work.Ĭoincidentally, we use WebDrive as a tool in mapping drives on the NAS devices & they too have ceased to function with DSM 7. The fix they provided involved changing some of the SMB settings in File Services within the Control Panel. I did talk to Synology support yesterday & mapping the drives via Synology Assistant has been an issue. Gerard, I have no problem mapping the drives via Windows as you described from any of the PC's. ![]() Thanks for all your suggestions and comments. In any event, I can now map a drive on my laptop to either of my Synology systems running DMS 7. My son then edited the registry on my laptop, basically (as I understand it) enabling Windows 10 to accept NTLMv2. Anyway, when DMS 7 rejected my NTLMv1 request, my laptop running Windows 10 just gave up trying to connect. It seems that my laptop wanted to use NTLMv1 and DMS 7 will not accept it. " As I understand it, NTLMv1 is a security protocol used when two computers are connecting to each other. He logged onto my laptop, did some fiddling, and discovered the following log error: "User xxx from yyy failed to log in via do to. Last night I explained the problem to him. My son is a network security guru for a very large hospital system. Finally found the solution to the problem (actually my son found the solution.) Turns out it was an issue with my Lenovo P52, Windows 10, and Synology DMS 7. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |