Good point...the mapping is hardly necessary these days, I agree, only the redirection of the system folders is
Sent from my Blackberry, which may be an antique but delivers email RELIABLY -----Original Message----- From: "Kennedy, Jim" <[email protected]> Sender: [email protected]: Thu, 9 May 2013 20:19:34 To: [email protected]<[email protected]> Reply-to: [email protected] Subject: RE: [NTSysADM] Home Directory - Security / Share setup recommendations I redirect My Docs to create the folder...then map that via GPP Drive mappings. But the Drive mapping is really legacy for the long timers that still prefer to work off a mapped drive rather than My Docs from time to time. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, May 09, 2013 4:17 PM To: [email protected] Subject: Re: [NTSysADM] Home Directory - Security / Share setup recommendations Don't people use GPP Drive Maps to assign this now just substituting the environment variable %username%? Admittedly it won't create the folder but a GPP Folder action could do that. Perms might need some slightly more complex jiggery-pokery though. I thought setting stuff like profile paths and home drives through ADUC was considered legacy now? I may be completely wrong though, its not something I do much these days. Cheers, JR Sent from my Blackberry, which may be an antique but delivers email RELIABLY ________________________________ From: "Guyer, Don" <[email protected]<mailto:[email protected]>> Sender: [email protected]<mailto:[email protected]> Date: Thu, 9 May 2013 15:55:07 -0400 To: [email protected]<[email protected]<mailto:[email protected]%[email protected]>> ReplyTo: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Home Directory - Security / Share setup recommendations "X:\Shares\Users\UserName (In this method only 1 share)" Create it through ADUC and it will assign the perms for you. \\shares\Users\%username%<file:///\\shares\Users\%25username%25> Make sure you have security set at the level above it (Users) the way you want right off the bat to prevent future issues. Regards, Don Guyer Catholic Health East - Information Technology Enterprise Directory & Messaging Services 3805 West Chester Pike, Suite 100, Newtown Square, Pa 19073 email: [email protected]<mailto:[email protected]> Office: 610.550.3595 | Cell: 610.955.6528 | Fax: 610.271.9440 For immediate assistance, please open a Service Desk ticket or call the helpdesk @ 610-492-3839. [Description: Description: Description: Description: Description: InfoService-Logo240] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Greg Saunders Sent: Thursday, May 09, 2013 3:51 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] Home Directory - Security / Share setup recommendations I know this will be a newbie question, but I don't setup Windows Server very often. What methodology do you use for the Home Folder setup in AD? For example do you have an administrative share like \\server\users$<file:///\\server\users$> and then each user have a folder like this X:\Shares\Users\UserName (In this method only 1 share) Or do you have a share for every single user going to \\server\username<file:///\\server\username> which sits in a place like X:\Shares\Users\UserName (In this method many shares) What method do you use (list another if you have it) and if you use the first method what security do you place on the X:\Users folder and then the actual User folder to protect it from others. I have seen different variations and just wonder what is the standard methodology for setting this up. Thanks Confidentiality Notice: This e-mail, including any attachments is the property of Catholic Health East and is intended for the sole use of the intended recipient(s). It may contain information that is privileged and confidential. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please delete this message, and reply to the sender regarding the error in a separate email.
<<inline: image001.jpg>>
