Setting Up Share Points

Hi All,
after a huge crash I have reinstalled my system. I am attempting to set up my share points in Server Admin but am having some issues, ie folders do not show up when the server is mounted by users. Here's what I've done.
Set up my users and added them to a group called 'company'. Selected the folder in the Finder and selected Shared Folder. In File Sharing in the SA, added the group to the ACL settings. Changed to Read & Write to this and children etc and then propagated the permissions.
Seems like everything should work. I have three folders that need to be shared like this. But when any of the users log in (all OS X), they just see the default Public and Users folders and the drives.
So what is the best way to set this up?

Hi
+"Selected the folder in the Finder and selected Shared Folder"+
You should not be using the Finder to apply any Sharing. Even applying/fixing Permissions via the Finder is not a good idea either. In Server Admin click on the Server Name in the left hand sidebar, click on the File Sharing Icon, select the Volume the Folder(s) you want to share are located on, click the Browse option, select the Folder, click the Share button. Finally click Save. Apply desired Protocols as well as desired access and permissions afterwards. Make sure you use the "Propagate Permissions" option.
Whilst you're there and if you have no need for them click on Share Points and un-share the default Users, Groups and Public folders. These are always shared by default and always have been since at least 10.2 IIRC. Don't delete these either. The Server will complain if you do and probably disappear up its own backside for good measure.
Tony

Similar Messages

  • Installing office 2010 - should I set up share point for users

    I have just upgraded from office 2003 to office 2010.  We are limited to 2010 because of some legacy programs.
     Anyway this is my first install of office 2010 that eventually I need to install on 40 or 50 computers.  After it is installed there appears a menu item to set up sharepoint. It says "Welcome to Sharepoint Workspace" "Create a new
    account" when I click Next it asks me to "Create an account using your email address" and so on.
    We do not have a sharepoint server, I also know almost nothing about sharepoint. We use Exchange 2003.
    Here are my questions,
    Can I create a sharepoint account without having sharepoint server?
    Is there any advantage if I can install it?
    If having SHAREPOINT without a Sharepoint Server is useless then should I in future installs remove some portion of the install when I install office 2010?
    I know this is a bit of a generic question but I really don't know what sure point does this by watching videos, it seems like it does a lot of the things that's other programs already do like address books ensuring of calendars.  That's really what exchange
    does.
    Thanks.

    Alex has hit all the right notes in his response and the one that I'd agree with would be the planning.  It's not uncommon to hear stories of firms putting SharePoint in, before they get around to thinking what to do with it.  It is a collaborative
    product that can provide answers to defined problems.
    On the SharePoint workspace issue, my personal thought would be give it a miss.  It doesn't have a 2013 version and it'll be pointless giving this to your user base, only to have to remove it depending on what your settled SP plans might be.
    Steven Andrews
    SharePoint Business Analyst: LiveNation Entertainment
    Blog: baron72.wordpress.com
    Twitter: Follow @backpackerd00d
    My Wiki Articles:
    CodePlex Corner Series
    Please remember to mark your question as "answered" if this solves (or helps) your problem.

  • Can't set up share point for external drive on Xserve

    I have an iomega 2TB drive connected to an Xserve. I can not seem to access the ext. drive from a client machine. I've been able to do this in the past, now it doesn't show up as one of the mountable drives when I connect to server.
    I CAN see it if I remote in to the sever. On the server desktop, the ext. drive is mounted. I can access it there, see folders inside and everything. However, if I look in the Server app, from a client machine, the ext. drive shows up in the list of volumes, but the disk space bar is all gray (no green, yellow or red) as if it's not readable. I know this is kinda hard to describe, but the bottom line is that I can't access my ext. drive that is attached to the Xserve.

    Alex has hit all the right notes in his response and the one that I'd agree with would be the planning.  It's not uncommon to hear stories of firms putting SharePoint in, before they get around to thinking what to do with it.  It is a collaborative
    product that can provide answers to defined problems.
    On the SharePoint workspace issue, my personal thought would be give it a miss.  It doesn't have a 2013 version and it'll be pointless giving this to your user base, only to have to remove it depending on what your settled SP plans might be.
    Steven Andrews
    SharePoint Business Analyst: LiveNation Entertainment
    Blog: baron72.wordpress.com
    Twitter: Follow @backpackerd00d
    My Wiki Articles:
    CodePlex Corner Series
    Please remember to mark your question as "answered" if this solves (or helps) your problem.

  • Do I have to set each external drive as a Share Point?

    Hi all,
    I was wondering if I can set a Share Point that would allow acces to all external drives (sometimes they are swapped out) It looks like I have to do them individually. 
    Any advice? Thanks!!!!
    Hugh

    Last time I tried something similar, when I tried to tell the Finder on the server to eject the external drive prior to disconnecting it, it correctly refused as the drive was considered inuse/busy. I had to unshare the drive first before it would let me eject it.
    If you just yank it out there is a chance it will leave things confused and you might end up with it still thinking it is connected and it then writing to a folder in /Volumes on the boot drive thinking it is the external drive. So you should do it properly by unsharing, then ejecting the drive.

  • Migration: Names of Share Points in Server Admin

    We're migrating from OS X Server 10.3.9 to 10.5.6. I've exported and imported the Users and Groups successfully and am setting up the Share Points manually.
    We have several Share Points whose directory names are the same: let's say, "Fred". In Panther Server, Workgroup Manager shows these as "Fred", "Fred (1)", and "Fred (2)". We gave the shares Custom AFP and SMB names as follows: "Fred1", "Fred2", and "Fred3", respectively.
    Now, when setting up Share Points in Leopard Server, Server Admin (why'd they move this from Workgroup Manager, anyway?) renames same-named shares a bit differently from Panther: "Fred", "Fred-1", "Fred-2". Note the hyphen instead of a space and parentheses. I can still give these shares the same Custom AFP and SMB names as on the old server, but my question is:
    Will the different "behind the scenes" names mean my users won't be able to connect to the shares? Or will these new names be irrelevant, since the names the users see (and map to automatically, in many cases) remain the same as before?
    Thanks.
    Jon Eiche

    Just to clarify, these Share Points are NOT users' home folders or any other such thing automatically created by the operating system (i.e., we don't have three users all named Fred, so don't tell me the folders shouldn't have the same names in the first place); they're independent shares we created as locations to place files.
    Jon Eiche

  • Panther server and share points on separate internal drives

    I'm using an old Graphite G4 with OS 10.3 server. I've installed the system on a small drive, and want to set up share points on a raided pair of larger internal drives, but have not been able to find the way to do it, as server admin doesn't see the raid. Surely this can't be that unusual a setup...
    Clues?

    IIRC, in 10.3 you use Workgroup Manager to designate share points
    It's been a while, but from memory you open Workgroup Manager, connect to the server, then click the 'sharing' icon in the top bar. From here you can choose any directory on the system and setup the sharing rules.

  • How to configure SharePoint HNSC with a reverse proxy server so that HNSC Share Point URLs are not exposed to end users.

    Could you please let me know how SharePoint HNSC can be configured with a reverse proxy server so that HNSC Share Point URLs are not exposed to end users.
    In normal path based site collections/web applications, reverse proxy configuration can be done using alternate access mappings with  Public URL = "proxy URL", internal = "HNSC Share Point URL" so that share point sends response back
    to Public URL = "proxy URL".
    In Host Named Site Collections,  alternate access mappings  are not supported. Each HNSC is designed to have only one URL in each zone. Zone is one of the five zones(Default,Intranet,Internet,Custom,Extranet) with each of which only one alternate
    URL is associated.  This is what we are able to get using power shell command "Set-SPSiteUrl", but this will not help us to get the response back to proxy URL after a request sent to share point because we could not find any mechanism in share
    point HNSC to respond  to a different URL(proxy URL). Consequently, Share Point URLs are exposed to  external users.
    Below share point article in MSDN blog is symmetrical to what we are observing with Share Point 2013 and Proxy Server. It mentions that internal HNSC URLs can’t be hidden using any proxy server. If  hiding the internal Share Point URLS is a requirement,
    it suggests to use a web application instead of host named site collections.
    Though I’m also observing the same behavior with Share Point 2013 HNSC, Could you please confirm my understanding is correct.
    http://blogs.msdn.com/b/kaevans/archive/2012/03/27/what-every-sharepoint-admin-needs-to-know-about-host-named-site-collections.aspx
    Excerpt from above article-
    "Host Named Site Collections Only Use One Host Name
    Continuing on the discussion on AAMs and host named site collections, you cannot use multiple host names to address a site collection in SharePoint 2010. Because host-named site collections have a single URL, they do not support alternate access mappings and
    are always considered to be in the Default zone.  This is important if you are using a reverse proxy to provide access to external users. Products like Unified Access Gateway 2010 allow external users to authenticate to your gateway and access a site
    as http://uag.sharepoint.com and forward the call to http://portal.sharepoint.com. Remember that URL rewriting is not permitted. Further, a site collection can only respond to one host name. This means if you are using a reverse proxy, it must forward the
    calls to the same URL.  If your networking team has a policy against exposing internal URLs externally, you must instead use web applications and extend the web application using an alternate access mapping."<u5:p></u5:p>

    Hi Satish,
    You are right that only one URL is allowed for each zone of the host-name site collections in both SharePoint 2010 and SharePoint 2013.
    It is by design that each host-name site collection only support one URL for each zone.
    The article below is about RTM version of SharePoint, and it is the same for SharePoint 2013 with the latest CU.
    https://support.microsoft.com/en-us/kb/2826457
    So to make the URL of HNSC not exposed to external users is not supported, you need to use path-based sites instead.
    Best regards.
    Thanks
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Different passwords for different share points on 1 server?

    On a lion server I have two share points.
    A 'general' is accessible for all users, a 'confidential' is for a select group of users.
    The permissions are set and the select group have their server access password in their key chain.
    The server password is stored in a separate key chain ie. not in the login key chain.
    The select users connect to the server and allways mount the 'general' share point.
    The 'confidential' share point is mounted only when needed and unmounted afterward.
    Problem is when the users walk away from their computer and forget to lock the computer or to completely disconnect from the server, which is generally very inconvenient because of open documents.
    "Unmounting" the confidential share in my setup is not really putting it away securely because at that moment, anyone can sit down at that computer and mount 'confidential' because the login credentials were already given when mounting 'general'.
    Is there any way, lest having Parallels running another Lion server that shares the 'confidential' mount point, to force users to enter a password before 'confidential' can be mounted WHILE 'general'  IS ALREADY MOUNTED?
    In other words, can credential exchange be tied to share point mounting time rather than to server connection time and thus be different for different shares and allow for share-specific unmounting, effectively locking it away?

    Has nobody done this before?

  • Setting up access points for public access

    Okay, here's the situation. I have a PowerMac G4/1.25GHz dual processor running Server X 10.3.9 with four Mac clients (a small law office). Up until recently, everyone had also been running (client) 10.3.9, but I started upgrading some of them to 10.4 (currently 10.4.5). When I did this, they started running into problems with Word sometimes giving a "network or file permission error" when attempting to save documents to the server. After weeks of posting questions to Word support and trying everything in the book that I could think of, I found Apple recently posted what appears to be the answer to this (article 302979, "Microsoft Office applications fail to save to a server volume." The problem? I have all four users logging into the same account on the server, and when one of them logs out, it zaps everything in a Microsoft-created temp folder on the server, including temp files created by open documents created by other clients. Sheesh.
    I had everyone set to use the same account because they have no need of document security -- everyone should be able to get into everyone else's files on the server, period. So, because of this snafu, I've created separate accounts for each of the users. My problem now is that, if user "X" creates a file or folder on the server, user "Y" cannot modify it because it is created as read-only. Strangely, if someone modifies an existing file, it doesn't change the user rights at all -- not sure why.
    I'll admit to being a bit of a novice with Server X but am familiar with parent/child folder permissions -- I think I've got everything set right, but I must obviously be missing something. Here's what I've got setup, and what I've tried. If anyone can point out how I've got this setup improperly, I really need to get this fixed... thanks.
    I have a single sharepoint ("workfiles"). I used the "public" folder as an example, and set the owner to "root" and the group to "staff". Further, I set the owner, group and everyone privileges to "read & write". I've also tried setting the group to "admin". All the individual user accounts I've set are also setup as admin users. I've tried setting each users's primary group as "staff (20)" or "admin (80)". I've copied all these privileges to all enclosed items, which does reset everything to public access, but as soon as someone creates a new folder or file, that folder/file becomes private to that user (it shows up with the creator's username as "owner" (r&w), group as "admin (read-only), and others as "read-only" as well.
    PS: If upgrading the server to Server X 10.4 would help, I'm sure I can arrange that.

    In our law firm, the server (10.4.4), we have set access to read/write access so staff can open client files/folders, edit then and close, etc. That seems to be working okay. Before the tech worked on permissions, if someone created a letter another staff member could open it, but it was read-only.
    The problem we are having is that if a file that is clicked on stationery pad and we want to edit it, it will not allow us to. For example, if we need to edit our letterhead that normally comes up as an untitled document, if I unclick the stationery pad box, it unclicks, but it still comes up as an untitled document. I even tried to unclick a stationery pad on a document that I created before the server upgrade and it wouldn't let me.
    If I create a brand new document and put it on stationery pad, it comes up untitled as it should. If another user on another desktop wants to make changes, they unclick the stationery pad box, but when they open it, it comes up untitled and in checking get info, the stationery pad is selected.
    The tech set it up as follows:
    Share Points and All tabs:
    General tab: box to share this item and its contents is clicked
    Access tab: owner, group and everyone have read/write privileges
    If select dial at bottom to propagate permissions, all boxes are checked, except for access control list, which is shaded.
    I cannot drag/add anything to the control list and the pencil and the minus sign is shaded
    Protocol tab: Both boxes, share item using AFP and Allow AFP guest users are clicked. But for better security in reading the article, this should be unchecked.
    Also under the protocol tab: the inherit permission from parent radio dial is clicked, not the use standard POSIX behavior.
    What are we missing?
    Thanks, Cheryl

  • How do I connect a user account to a server's share points when the user is on the same Mac as the Lion Server?

    I've installed and configured Lion Server on an old iMac that suddenly became available when I upgraded to a new iMac. I've got a share point on there. It was easy. Love it.
    My bookkeeper comes into my office once a week and works on that iMac. He already has a regular user account set up there. He needs to access the sharepoint that is on that iMac he's using, and which is now running Lion Server. But I can't see the server from his account, and I can't manually connect to it - I get an error to connect locally on the Mac instead.
    But I can't navigate to the point in the user account that I'm using as a file serving account to get him access to the directory I'm sharing.
    So, in short, how does a local user on an iMac running Lion Server connect to the server's sharepoints?

    All drives are now listed under volumes both local and remote.
    I would try the fullpath using /Volumes/....
    or post the file paths your trying
    are you trying the goto menu?

  • Share point in server admin not working correctly... I think

    I suspect that the share point in server admin is not working correctly. In workgroup manager when I click on a user and then click on the "home" tab, under the full path field I see a file path of:
    afp://server.mydomain.com/Users
    However if I go to Server Admin -> AFP -> Share Points then click on the Users share and then click on the share point tab below, enable auto mount is disabled. How can this be possible? I thought for a directory to show up in home in workgroup manager it had to be set as an auto mount. Has something possibly corrupted? And what?

    Here's a bit more information about our setup and our experiences with Apple's CUPS implementation:
    On the server, all printer queues are set up with only lpr and ipp sharing enabled with the PPD setting for each printer set to Generic Postscript. We found that setting the PPD to the printer specific one on the server caused problems when clients tried to use printer specific options, like paper tray selection, etc.. The selection would be undone, apparently because the driver on the server would override the previous settings. Using Generic Postscript allows the client PPD settings to go through unmodified. Our printers are general a mix of HP LaserJets and some Sharp Copiers.
    All clients use lpd to the server queues with the printers' actual PPDs configured. Using ipp is superior in that printer feedback (jams, out of toner, etc) makes it back to the clients, but ipp only works when the client, the server, and the printer are on the same network. If the ipp client is not on the same network, the client spooler immediately goes into a paused state and the print job is stuck on the client.
    Using lpd to the server queues works reliably, but there is no feedback to the client. Jobs disappear from the client queue and go to the server, appearing to the user as a successful print. If the printer is down, there's nothing they can see or do about it.

  • How to remove corrupt share point?

    Hi All,
    I have a corrupt sharepoint that is killing my backups, I'm in need of some help getting rid of this "beast".
    OS X Server 10.5.4 Advanced.
    Mac Mini 1.83 GHz 2GB RAM.
    Server runs on internal drive, backs up to external firewire drive.
    Server has been in daily use for about 4 months without incident.
    Here's the what happened and what I've tried so far.
    I Created a new sharepoint in ServerAdmin.
    Shared folder: /Library/WebServer/Documents
    Custom AFP name: /WebDocs
    The sharepoint "/Documents" was created, but I was unable to see or connect to /WebDocs.
    The first workstation connecting to /Documents resulted in a server crash (did not record details). Server seemed to be OK after rebooting.
    A second attempt to connect by the same workstation (Windows 2000) worked as expected and the user was able to read and write data on the server.
    As "/Documents" conflicts with an important local name, I deleted the /Library/WebServer/Documents share point and set up /Library/WebServer with Custom AFP name at default "WebServer".
    The sharepoints "/WebDocs" and "/Documents" do not appear in Server Admin.
    Now the server, and workstations bound to it, have an alias "/WebDocs" which seems to be corrupt and causes Superduper backups to fail with an error:
    Error - SDCopy: Failed to copy extended attributes to directory /Volumes/SrvBack/WebDocs:
    Too many levels of symbolic links
    Running Repair Permissions did not help.
    Get Info on /WebDocs (in Path Finder) shows:
    Kind: Alias
    UTI: com.apple.mount-point
    Locked: Yes
    Owner: root
    Permission 000
    type: 'lcmt'
    Creator 'rhap'
    BUT...
    server:/ root# ls -ld /WebDocs
    dr-xr-xr-x 2 root wheel 1 Aug 3 12:08 /WebDocs
    server:/ root# chmod -h 777 /WebDocs
    chmod: /WebDocs: Too many levels of symbolic links
    server:/ root# rm -d /WebDocs returnes an error:
    rm: /WebDocs: Resource busy
    server:/ root# mv /WebDocs /BrokenWebDocs
    seems to work as expected, but /WebDocs alias is recreated on server boot.
    server:/ root# ls -l /WebDocs returns an error:
    ls: WebDocs: Too many levels of symbolic links
    server:/ root# ls -l /var/db/dslocal/nodes/Default/config/Sharepoints
    shows all expected sharepoints, WebDocs is not present.
    server:/ root# sharing -l
    lists all expected sharepoints, WebDocs is not present.
    LDAP Log does not list WebDocs or Documents
    Server Log contains:
    Aug 4 13:14:35 server servermgrd[88]: servermgr_filebrowser:
    FSPathMakeRef failed with status -35.
    path: /Volumes/Macintosh HD/WebDocs
    I am guessing that the corrupt /WebDocs share point is contained in the LDAP directory, because it's propagated out to the work stations, but I don't know where to begin looking for that.
    Any input would be greatly appreciated!
    -Glen
    Message was edited by: gihrig

    The solution to this problem:
    Workgroup Manager/Preferences/Show "All Records" tab and inspector.
    Select the "All Records" tab (Target icon).
    Use the search tool to find the errant sharepoint and delete it.
    Problem solved.
    Odd that the sharepoint did not sow in the System Admin tool...
    Regards,
    -Glen

  • Custom NFS share point directory showing up on all network machines

    Hi,
    I'm in the process of migrating our 10.4 PowerMac server to a Mac Pro (running 10.5). I've been trying to recreate our 10.4 server setup as much as possible and so far I've only come across one annoying issue.
    We have fink installed on the server and under our 10.4 setup the /sw directory was set up as an NFS automounted share point with a custom mount point of '/sw'. I.e. users logging into client machines saw a /sw directory and could work with that. This made it easier to add fink packages as I only needed to do this on one machine (the server). This setup worked very well under 10.4 and had been working stably for the last couple of years.
    As we now have (for another month or two at least) a mix of intel and Power PC machines, I don't want to share out the (intel) server version of fink to all clients. In Server Admin, I have chosen to set the NFS protocol options to specify the IP address of just one client (an intel machine). I am only using NFS to share this directory. The plan is to add more client IP addresses as we get more intel machines.
    This works for the one intel client machine. Logging in via the GUI or via ssh allows you to run programs located under the /sw directory. The problem is that a phantom /sw directory appears on all client machines, even though their IP addresses are not specified in Server Admin. The /sw directory has root/wheel permissions (for user/group) and attempting to list its contents returns 'Operation not permitted' (even with 'sudo ls /sw').
    If I use Directory Utility to remove the connection to the Directory server on our main server, then the /sw directory becomes owned by root/admin and I can remove it (it appears empty). Reconnecting to the Directory Server changes the permissions back to root/wheel. It is also worth noting that when I first installed fink on the server (in /sw) the act of making this a share point also changed the permissions on /sw to root/wheel meaning that I couldn't access the fink programs that I had only just installed (this forced me to reinstall fink in /Volumes/Data/fink).
    Has anyone else noticed this behavior? It almost seems like Server Admin is not honoring the list of IP addresses that are being listed as targets for client machines. I had planned to install fink locally on the PowerPC clients until we upgrade them to intel machines. However, I would then also have to install fink somewhere other than /sw as I can't write to that directory. I would presume that this behavior should happen on any NFS share point that is trying to automount to a custom mount point on a client. Can anyone else verify this?
    Regards,
    Keith

    As a footnote. I have now removed my shared fink installation. It is no longer listed as an NFS sharepoint in Server Admin and running the 'showmount -e' command does not list it. However, a /sw directory is still being created on the server and on the client machines on our network.
    This is perplexing and frustrating. There is no sharepoint any more. I rebooted the server but it makes no difference. I removed the /sw directory (on the server) by booting the machine in target firewire mode and removing it by using a 2nd machine. But following the restart, it appeared again.
    This suggests that once you make any custom mountpoint (using NFS sharing) then you will forever be stuck with a directory at the root level of all your clients which you can not remove.
    Keith

  • List value retaining in Share point hosted app 2013

    I'm creating a Share point hosted app.
    I have a list inside Share point 2013 app. We are inserting records into the list through some other forms in app.
    But when we deploy the app, it is getting retracted & deployed again. So the list values are getting deleted.
    Is there any way to retain the Share point app list values during deployment?
    I tried the following things as suggested by some experts in internet.
    • Setting up the app catalog for app in Central admin and increment the version for every deployment.
    • I set the “deployment conflict resolution” property of list instance to “none”.
    But both the things not working.
    Please help me on this issue.

    Hi,
    According to your post, my understanding is that you wanted to keep the list data while redeploy the app project.
    As you had known, to keep the data in the app, we should first set up the  app catalog.
    Then we should upload your app with version 1.0.0.0. Install app to the desired web.
    After some code modification increment your version to 1.0.0.1 and upload again your app to catalog.
    Upgrade your installed app. More details about updating            
    http://sharepoint.stackexchange.com/questions/83021/app-deployment-keep-the-existing-data-in-internal-list-of-an-sharepoint-app
    Thanks & Regards,
    Jason
    Jason Guo
    TechNet Community Support

  • ACL on share points doesn't seem to work

    Hi Everyone,
    I have a server set up, with a series of share points on it. One of those folders is "Marketing", and the Marketing team has a boss, who is the only guy who should be able to create folders within that share.
    The people in the Marketing group, should have access to write and delete files, but not create folders.
    Here's the setup:
    Users/Groups:
    John (boss)
    Roger (one of the Marketing employees)
    John and Roger both belong to the Marketing group
    Share point ACL:
    Marketing / Allow / Custom ( full read, write attributes, write extended attributes, create files, delete )  but not create folder, delete subfolders and files
    John / Allow / Full Access
    As last detail, all users are on Apple computers.
    Problem
    John is able to do everything he should, create files, folders, etc.
    Roger on the other hand, can only read. 
    Question
    Does the ability to write files, require the ability to write folders?  If I let Marketing group write folders, Roger's access works.  If so, is there a workaround?
    Thanks!

    I know that order of the permissions in the acl window is relevant, from what ive learned on here based on different issues.  I think if you have a deny permission, and further down you have an allow permission so to speak, the allow overides.
    HTH

Maybe you are looking for