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

Similar Messages

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.

Server Admin won't let me view Share Points

I had a server crash while editing a user in Workgroup Manager that forced a restart. Since then Workgroup Manager works fine, but I cannot see the Share Points in Server Admin. I select File Sharing then Share Points, and just get a spinning indicator on the lower right. I can browse the volumes, but clicking on a user's folder does nothing. The Share/Unshare button never becomes active and I can't view the permissions. Other functions of the Server Admin seem to be OK, except the Web settings take forever to show up. This happens whether I run Server Admin locally or remotely.
I get this from the Console when I launch Server Admin but it makes no sense:
12/28/07 5:48:48 PM /Applications/Server/Server Admin.app/Contents/MacOS/Server Admin[632] ATS AutoActivation: MDQueryExecute failed! (params: queryString = {comapple_ats_namepostscript == "ArialMS" && kMDItemContentTypeTree != com.adobe.postscript-lwfn-font}, valueListAttrs = {<CFArray 0x10092ba0 [0x12321a0]>{type = immutable, count = 1, values = (
0 : <CFString 0x2ea09d8 [0x12321a0]>{contents = "kMDItemContentType"}
)}}, sortingAttrs = {<CFArray 0x10092bc0 [0x12321a0]>{type = immutable, count = 1, values = (
0 : <CFString 0x2ea0908 [0x12321a0]>{contents = "kMDItemContentModificationDate"}
)}}, scopeList = {<CFArray 0x10092be0 [0x12321a0]>{type = immutable, count = 1, values = (
0 : <CFString 0x2ea1b28 [0x12321a0]>{contents = "kMDQueryScopeComputer"}
because I get the something similar when I launch FileMaker from the same machine:
12/28/07 5:48:42 PM /Applications/FileMaker Pro 9/FileMaker Pro.app/Contents/MacOS/FileMaker Pro[628] ATS AutoActivation: MDQueryExecute failed! (params: queryString = {comapple_ats_namefond=="B773B2D3A9FAC5E9"}, valueListAttrs = {<CFArray 0xb2ba910 [0x51de1a0]>{type = immutable, count = 1, values = (
0 : <CFString 0x67e09d8 [0x51de1a0]>{contents = "kMDItemContentType"}
)}}, sortingAttrs = {<CFArray 0xb2babb0 [0x51de1a0]>{type = immutable, count = 1, values = (
0 : <CFString 0x67e0908 [0x51de1a0]>{contents = "kMDItemContentModificationDate"}
)}}, scopeList = {<CFArray 0xb2bacb0 [0x51de1a0]>{type = immutable, count = 1, values = (
0 : <CFString 0x67e1b28 [0x51de1a0]>{contents = "kMDQueryScopeComputer"}
Any ideas where to look?
10.5.1 on dual-core intel XServe 4GB RAM

Use the inspector in work group manager to delete /config/sharepoints.
You will need to be in the local directory in work group manager and you will have to reshare all shares but no data will be removed. You should probably reboot after deleting the directory. This would replace the old way of doing it in the past with netinfo manager since we don't have netinfo anymore.

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

Share Point folder size limit - File Services

I created a new folder inside a share point using Server Admin. Is there a way to set a folder size limit (quota) for that folder.
P.S. I am NOT talking about user accounts quotas for home folders created using Workgroup Manager! ...Just any new folder created, to be used on any volume, is there a way to set a mamimum size?
For example I have a 1TB volume on my Xserve RAID. I create a new folder but want to set its maximum capacity to 200GB. Is that possible?
Thank you very much in advance for any feedback.

There's no direct way to set a limit on a folder size.
The 'simplest' method I can think of is to create partitions on your disk of the appropriate sizes and share these - they will have inherent size limits based on the size of the partition. It's a little messier but should solve your issue.
:: thinking :: you might be able to use disk images rather than partitions, although I've never tried sharing a mounted disk image, and you'd need to address automounting the disk images when the server starts, so it might not be viable.

System creates group for every share point

Every time I create a new share point on my OS X Server 10.5, a group is created by the system on the fly along with it.
For example, I created a folder nameded Research Office and shared in Server Admin. Then when I assign the permission for the share point in Server Admin, I see a group called Research Office group with a GID of 124. However, this group does not appear in Workgroup Manager so I can not assign members to it.
Anyone see this before?

These groups are 'local' (Not LDAP) I still have difficulty wrapping my head around some of the rules about the 'how' this works but assigning LDAP users to this group does work!
OK _To see this group(s)_.
1: Open Workgroup Manager.app.
2: Select /Local/Default in your Authentication list (this spot is between the Toolbar and the 4 (or 5) icons for User, Groups, Computer Groups etc.) We are looking for the place that should say something like 'Authenticated as XXXXX to local directory /Local/Default')
3: Select the Groups icon (3 Shadows standing together)
4: Select Menu View, Show System Users and Groups
5: Now you will be able to select these groups.
_To add LDAP users and groups to this 'local' group._
1: Highlight the group in question
2: Select the Members tab in the right pane
3:Click the plus
4: After the tray slides out, at the top of the tray, you will see a disclosure arrow and Local Directory /Local/Default. Click on it and select /LDAP/127.0.0.1
Now you can select your LDAP users to assign rights.
Peter

Folders Not Showing in Server Admin AFP Share Point?

Hello all,
My problem is I can make a folder in Server Admin under AFP Share Point, But the Folder wont actually be made on the HD.
Under Server Admin AFP Share Point it will tell me that it doesn't exist?
So I thought I'll go to that point on the HD and make the folder then set the permissions to it... nope I can make the folder I can see it in finder and in terminal, But not in Server Admin AFP Share Point.
I have never seen this before any help is greatly welcomed.

Hi Kristoffer,
I have seen an attribute for folder object which could control SharePoint folder hide or show in webdav explorer view, you can use PowerShell to output the problematic folder property, see if it the case, then use the PowerShell code to set it's property
with blank value to make it show in explorer view,
Use the PowerShell to get the folder object and then check the property value with this code line $folder.Properties["vti_winfileattribs"]
#folder can be site, library level and folder level
$folder = (Get-SPWeb http://sp).Folders["shared documents"].SubFolders["folder1"]
#hide folder
$folder.Properties["vti_winfileattribs"]="00000016"
#show folder
####$folder.Properties["vti_winfileattribs"]=""
$folder.Update()
https://social.technet.microsoft.com/Forums/lync/en-US/9ceafb38-24dc-466c-b497-2cee062b81cf/explorer-view-hidden-folder-attribute?forum=sharepointgeneral
Thanks
Daniel Yang
TechNet Community Support

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]

Can't mount share points over VPN after moving server

I'm tearing my hair out over this one. We have a server that was located in our office. I just moved it downtown to a colo center (no longer in office) and set up VPN access.
However, nobody is able to mount the server share points, even though the connection to the VPN seems to work fine (e.g.: I choose "connect to L2TP..." and it connects, VPN icon shows I am online with the server).
Any attempt to mount a share point fails. I've tried using afp://servername.com and I've tried afp://64.xx.xx.xx (where that's the machine's public IP address). Am I supposed to use a different address (such as an internal 192 address that works over the VPN) or should I be able to mount the afp point using the server public domain name? Should I try NFS?
Any help would be appreciated -- really need to get access to this system's files again! Thank you!

Morris Zwick wrote:
And does anyone know which IP you enter for your sites in the web service? The public static IP or the internal private static IP?
For the external DNS server I am sure you have already deduced that it should be the static IP issued you by Comcast and this will be forwarded by your router to your server.
For your internal DNS server you could use either the internal LAN IP, or the external IP although the later might be affected by your firewall so this you will need to test.
For the Web Server service in Server admin, if your only running a single website you could avoid the issue by just using the wildcard entry which will respond to any IP address, so this would be an empty host name and an IP address of *
In fact you don't have to specify an IP address you could just use the hostname, so it will listen to traffic arriving at your server addressed to any IP address and as long as the URL that was requested includes the hostname you define for the site it will get responded to. So if as an example you have two websites you want to serve
www.example.com
site2.example.com
then as long as both have the IP address for the site as an * (asterisk) then both should work as separate sites for traffic addressed to either the LAN or WAN IP address of the server.
You will still need to use two IP addresses on the server to enable VPN, you could use a USB Ethernet adapter for the second one. Port forwarding for VPN is not as simple as other traffic as VPN requires traffic different to the standard IP and UDP packets. Routers that support 'VPN Passthrough' are specifically designed to accomodate this but I don't know if the AirPort Extreme does this. I have also found PPTP copes better with this sort of setup than L2TP although PPTP is generally regarded as less secure.

WebDAV Share Points Missing in OS X Server 10.8

WebDAV share points are missing in OS X Server 10.8.
To see for yourself:
1) Do a clean-install of OS X Server 10.8 with a single admin account and a .local host name.
2) In Server.app -> File Sharing, enable WebDAV access for the three default share points: /Groups, /Public, /Users.
3) In Finder -> Go -> Connect to Server -> http://server.local/webdav/ and log-in as the admin account.
Note that only the admin account's networked Home directory appears. There is no WebDAV access to the enabled share points.
4) In Finder -> Go -> Connect to Server -> afp://server.local and log-in as the admin account.
Note that the three default share points appear, along with the networked Home directory. AFP allows access to the enabled share points.
Any suggestions for a fix, or work-around?

I agree with Larry Goldman on this 100%. OS X 10.4, 10.5, 10.6 were rock solid when released. Starting with 10.7 it's been Vistaville all the way. Combined with fanboi arrogance, this has been totally frustrating.
There was a file/directory permissions error in 10.7.0 through 10.7.3, This permissions error caused endless random untracable problems and Apple said NOTHING about it. This wasn't fixed until 10.7.4, and a month later Mountain Lion came out.
"Don't reopen windows at startup" didn't work until 10.7.4 either - causing no end of headaches and problems, but Apple shipped 10.7 out the door with this glaring bug. Nobody at Apple saw this? Nobody tested this? It took a year for Apple to finally to fix it?!?!
Lion was a broken piece of **** until 10.7.4, and I cannot imagine all of the user frustration that must have occured as a result of these two problems, but how many other problems wreaked havoc, undetected?!?
I guess all the seasoned Apple devs went over to iOS, and the beginners are working on OS X. It really shows.
When I booted Lion and Mountain Lion for the first time, all kinds of buggy weirdness reared its ugly head. Windows not closing, artifacts remaining on screen, preference setting reverting without reason, fields not accepting input, Safari suddenly unable to connect to the internet (even though Chrome worked perfectly at the same time for the same URL), yada yada yada...
It used to be Microsoft that made their customers find all their OS bugs for them because it was cheaper than writing clean code from the beginning.
Today, quality control and testing have obviously gone out the window at Apple. They need to spend more of that $100 billion on QA and less on marketing.

Mavericks won't log onto Snow Leopard server share points

I have 3 imacs, running mavericks which won't successfully log onto Snow Leopard server share points.
The server appears on the list on the left and i get to a login screen when i select the server.
I enter the username and password and the box just shakes.
However if I tick the "access as administrator" in the user prefs on the server, it can connect, however i don't want certain users to have admin rights.
The strange thing is, is that if i choose to login with a user name and password for one of the older macs (10.6), i can log in. But that defeats the object.
This is obviously an authentication issue between mavericks and SL.
Any one else had this?
Thanks in advance.

Try using sort format of user name

Mavericks won't connect to Snow Leopard server share points

I have 3 imacs, running mavericks which won't successfully log onto Snow Leopard server share points.
The server appears on the list on the left and i get to a login screen when i select the server.
I enter the username and password and the box just shakes.
However if I tick the "access as administrator" in the user prefs on the server, it can connect, however i don't want certain users to have admin rights.
The strange thing is, is that if i choose to login with a user name and password for one of the older macs (10.6), i can log in. But that defeats the object.
This is obviously an authentication issue between mavericks and SL.
Any one else had this?
Thanks in advance.

The "Trust, but verify" follows...
Launch the MS-DOS command box on Microsoft Windows XP.
Verify IP network connectivity with ping. Ping the Samba/CIFS server by IP, then by name. Ensure that the box you're connecting to is the one you think it is; that can be via telnet or web connections or otherwise; make sure your IP network is configured the way you believe it is, and you're getting to the host you think you're reaching.
If the IP address connection works but the domain name (host name) does not, then debug the DNS validity with dig or nslookup, and ensure the client can get DNS translations.
Verify that the [Windows registry settings|http://labs.hoffmanlabs.com/node/1590] allow access to Samba/CIFS shares.
If you're not running Microsoft Windows 7 and the x86 gear here supports it, definitely upgrade. Windows 7 is a vast improvement over earlier releases, including over Windows XP.

Mobile Account - How to Map Share Point Locally on Server?

Hello,
Using mobile accounts on a mac mini server, this is a small home network. Primary reason for server was to use mobile accounts allow the various computers and laptops to be accessed by all family and guests with data linked to login.
All work fine except, when I login into the server as my mobile account it is unable to sync, or find any files because the Share Points do not map locally. Warning message says use locally. This causes problems with itunes, mobile account syncs etc.
Is there a way to map the Share Points using the network path, locally on the server in the mobile accounts?
Thanks
Peter

You need to convert the project to sharepoint 2013, you have to change the target office version 15.0 and target framework versions to 4.0 or 4.5. For more details go throught the below posts
http://www.codeproject.com/Articles/522220/Converting-Multiple-SharePoint-2010-Projects-to-Sh
http://social.msdn.microsoft.com/Forums/en-US/c15f274c-1dfe-47cc-b753-883307fc354f/migrate-sharepoint-2010-visual-webpart-to-sharepoint-2013-using-visual-studio-2012
http://sharepoint.stackexchange.com/questions/58377/upgrade-a-vs-2012-sharepoint-2010-project-to-sharepoint-2013
Raghavendra Shanbhag | Blog: www.SharePointColumn.com
Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
Disclaimer: This posting is provided "AS IS" with no warranties.

Unable to unshare a share point due to forced drive (volume) name change.

I just upgraded a single CPU G4 Xserve from 10.3.9 to 10.5.2. I have run into a bug that I found discussed in another thread here; the bug that two drives on the server cannot have very similar names or it leads to the File Sharing pane in Server admin being unable to access and control the permissions of that drive. I had two drives, Poseidon I (boot drive) and in the second slot, Poseidon II. I have a sharepoint called Prepressfiles inside Poseidon II. After the upgrade I could not access the volumes permissions due to the aforementioned bug (the thread I just responded to should come up right under this posting). Well, once I changed the name (to PPFiles) I could then access the volume as well as being able to rehare the sharepoint, however it automatically renamed it Prepressfiles (1) which means I would have to go and change a lot of things elsewhere, obviously. Well, I can't delete the old sharepoint which is why the new one has the (1) in the name added automatically, because that volume doesn't exist anymore, and if I change the name back, I can't deleted the sharepoint either because of the naming bug!!!
How can I manually delete this sharepoint from the Server Admin, as that seems the only way I can at this point. I need to be able to rename the drive as I did and then reshare the sharepoint as plain old 'Prepressfiles'.
MANY THANKS!!!!

Hi Abiebelcap,
Based on your description, my understanding is that you have configured a new URL for the newly created web application in Configure alternate access mapping in Central Administration.
If that is the case, please make sure that the two things below have been done:
1. Make sure that the host header used in the new URL have been added in the DNS server and it points to the IP address of the server where the web application runs.
For example, I used the host header called test:
2. Make sure that binding for the new URL is added to the web application in Internet Information Services(IIS).
Open IIS, right click the site of the newly created web application and select Edit bindings.
After that, you can access the site collections inside the new web application from the new URL.
More reference:
http://blog.blksthl.com/2012/12/03/a-guide-to-alternate-access-mappings-basics-in-sharepoint-2013/
http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/05/27/alternate-access-mappings-explained.aspx
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Windows XP PC won't connect to Snow Leopard server share points

Cabled network. Two imacs and two pc's. All apart from one PC won't connect.
The Other PC is running the same Windows and connects, see's share points and login using correct user name and password. The Other pc, see's the server under workgroup, but when you go to connect it just whirs away and does nothing. The PC in question connects to internet, prints on network printer fine.
Disabled firewall and checked settings and they are the same as the other pc. Really stumped.
anybody got any clues?

The "Trust, but verify" follows...
Launch the MS-DOS command box on Microsoft Windows XP.
Verify IP network connectivity with ping. Ping the Samba/CIFS server by IP, then by name. Ensure that the box you're connecting to is the one you think it is; that can be via telnet or web connections or otherwise; make sure your IP network is configured the way you believe it is, and you're getting to the host you think you're reaching.
If the IP address connection works but the domain name (host name) does not, then debug the DNS validity with dig or nslookup, and ensure the client can get DNS translations.
Verify that the [Windows registry settings|http://labs.hoffmanlabs.com/node/1590] allow access to Samba/CIFS shares.
If you're not running Microsoft Windows 7 and the x86 gear here supports it, definitely upgrade. Windows 7 is a vast improvement over earlier releases, including over Windows XP.

Migration: Names of Share Points in Server Admin

Similar Messages

Maybe you are looking for