Configuring CIFS to open at a target folder

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2010 10:48 PM
Hi Everyone,
Is it possible when configuring CIFS to set it up so that the CIFS project starts at a certain folder location in the repository. For example /Company Home/Legal/documents. If so how do you do it.
Regards
Brian
Is it possible when configuring CIFS to set it up so that the CIFS project starts at a certain folder location in the repository. For example /Company Home/Legal/documents. If so how do you do it.
Regards
Brian
Labels:
- Labels:
-
Archive
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2010 03:04 AM
Are you asking about CFIS as in when mapping the drive/folder in Windows explorer? If thats the case then yes, just add the correct path in the mapping path, eg;
\\MYSERVERA\Legal\documents\
When mapping that the mapped "drive" wil open the 'documents' folder. Be sure that whatever user you're using to map the drive has permissions to 'legal' and 'documents'. I've had some problems that say, when 'user1' has permissions to 'documents' but not 'legal' the drive wont map. Hope this helps
\\MYSERVERA\Legal\documents\
When mapping that the mapped "drive" wil open the 'documents' folder. Be sure that whatever user you're using to map the drive has permissions to 'legal' and 'documents'. I've had some problems that say, when 'user1' has permissions to 'documents' but not 'legal' the drive wont map. Hope this helps

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2010 07:28 PM
Thanks. I suppose that makes perfect sense. Just map to where you want to start from.
The reason I asked this was really because I wanted to restrict access to the data dictionary and all folders at that level other than Legal. Do you know if there is any implications in changing the security on these top level folders so that everyone does not have read access on them.
regards
The reason I asked this was really because I wanted to restrict access to the data dictionary and all folders at that level other than Legal. Do you know if there is any implications in changing the security on these top level folders so that everyone does not have read access on them.
regards

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2010 04:06 AM
Thanks. I suppose that makes perfect sense. Just map to where you want to start from.
The reason I asked this was really because I wanted to restrict access to the data dictionary and all folders at that level other than Legal. Do you know if there is any implications in changing the security on these top level folders so that everyone does not have read access on them.
regards
Ah, if I understand this correctly, your 'legal' space lies in the 'Data Dictionary' space, and what you would like to achieve is that say; user1 logs on he can see the 'Data Dictionary' space, but when he enters that space only the 'legal' folder is visible to him? If thats the case, all you need to do is use the 'Manage Space Users' tool under 'More actions' and remove EVERYONE and unclick the 'Inherit Parent Space Permissions' tickbox. Note that you have to do this for every space/folder UNDER the 'Data Dictionary' space and not for 'Data Dictionary' itself. The permissions get inherrited into CFIS as well. Hope it helps
