Guest tnt Posted October 9, 2008 Posted October 9, 2008 Hello, Just making sure I am not confused. I have created shortcuts to a few departments share and placed it on a common share called --> \\fs1\depts$. The departments shares have been locked down (shares/security) and only allowed users of that department access. On the shortcuts created, I also locked down to allow only people that have access to the shares. shortcut security set ------------------- * Read & execute * Read share security ----------------- * Read & execute * List Folder Contents * Read Question: the shortcut securites set are independent of actual securities set on the shares? Just making sure. I have tested. Just want a confirmation. Tnt
Guest Jon Wallace Posted October 10, 2008 Posted October 10, 2008 Re: Setting security on shortcut Yes, a shortcut is actually a file - a.lnk file. Whatever permissions to apply to the shortcut apply to the file, not the share. Permissions on the share are independent to those you apply to the actualy shortcut files... "tnt" <tnt@discussions.microsoft.com> wrote in message news:0F4A0AE5-F877-4B9D-BAE6-48AD8ACF9B06@microsoft.com... > Hello, > > Just making sure I am not confused. > > I have created shortcuts to a few departments share and placed it on a > common share called --> \\fs1\depts$. The departments shares have been > locked down (shares/security) and only allowed users of that department > access. > > On the shortcuts created, I also locked down to allow only people that > have > access to the shares. > > shortcut security set > ------------------- > * Read & execute > * Read > > share security > ----------------- > * Read & execute > * List Folder Contents > * Read > > > Question: the shortcut securites set are independent of actual securities > set on the shares? Just making sure. I have tested. Just want a > confirmation. > > Tnt > > > > >
Guest tnt Posted October 10, 2008 Posted October 10, 2008 Re: Setting security on shortcut Thanks for your reply. I noticed if users logged in without the security rights to the shortcut, the icon is white (thats what we want). Tnt "Jon Wallace" wrote: > > Yes, a shortcut is actually a file - a.lnk file. Whatever permissions to > apply to the shortcut apply to the file, not the share. Permissions on the > share are independent to those you apply to the actualy shortcut files... > > > "tnt" <tnt@discussions.microsoft.com> wrote in message > news:0F4A0AE5-F877-4B9D-BAE6-48AD8ACF9B06@microsoft.com... > > Hello, > > > > Just making sure I am not confused. > > > > I have created shortcuts to a few departments share and placed it on a > > common share called --> \\fs1\depts$. The departments shares have been > > locked down (shares/security) and only allowed users of that department > > access. > > > > On the shortcuts created, I also locked down to allow only people that > > have > > access to the shares. > > > > shortcut security set > > ------------------- > > * Read & execute > > * Read > > > > share security > > ----------------- > > * Read & execute > > * List Folder Contents > > * Read > > > > > > Question: the shortcut securites set are independent of actual securities > > set on the shares? Just making sure. I have tested. Just want a > > confirmation. > > > > Tnt > > > > > > > > > > > >
Recommended Posts