Migrating home directories to an Xraid

I have just installed an Xraid to an existing Xserver. I have User Directories on the Xserve and some other folders from a Windows 2003 file server. I have updated my LDAP directory and can't seem to get Workgroup Manager to recognize the home directories I've moved over. The directory on the Xraid is shared and choose-able in the Home section of Workgroup manager. I did go into terminal and do a chown on one of the users, but it still wouldn't see the directory.
Any help would be great!!
Chuck

I'd like some more advice on this as well, as I am about to migrate from user accounts from the G5 Server to an X-RAID. Here are the steps I have in mind. Anything else?
1. You'll need to unshare the current Home folders directory on the server using the WorkGroup Manager.
2. Then create the share-point on the RAID. Make it Network mountable.
3. Change User path to the location in WorkGroup Manager. Shift-select all the users who are going to change path- select the new share under Home and Save it. Check under Home tab to verify.
4. Migrate accounts using ditto copy.

Similar Messages

Migrate home directories from NW6.5/NSS to OES2/NSS

Hi
Is there a way to migrate the user home directory from NW65 to OES2/Linux in the same tree and copy trusties and change the users home directory setting in the user object?
I've looked at the migration tool in OES2 but I can only copy data, and not trusties and change home directory...
/Jonas

I use a utility called HOMES...by HBware...slick!
I have also used a utility called (I think) Mass volume changer...that was slick too. HOMES is the more powerful, though. Both are freeware.
--El
Originally Posted by jonhol
My mistake... Trustees are copied. Just my luck that when I tested I randomly selected a homdir and that one had no trustees as someone deleted the user object without deleting the directory...
Tried wit another homedir and it worked just fine.
Just the problem with changing the home directory in the user object left to solve...
/Jonas

Migrating Local Users to Network/Mobile Home Directories

Hey Everyone!
A Happy Holiday's to you all! I'm in the midst of building a new system for my new clients. They had nothing but static IP numbers and no actual servers in a 50+ Mac environment. MacBook Pros, G5's and PowerBook G4s up the yang.
What I'm looking to do is migrate as seamlessly as possible, all of the existing local users to network users and then some of those network users will become mobile accounts. I have Open Directory authenticating properly so...
Here's my plan:
1) Finish creating new builds for the MacBook Pro's, the G5s, and the PowerBook G4s.
2) Create the users in OD and assign them to groups for permissions.
3) Drag and drop entire home directory from each computer to a shared folder on my OD Server.
From here I want to run chown, I'm guessing, to change the user:group for the home folders I copied over so that they match the ID's created by OD. I figure when I do that, then I can simply replace the OD created home folders in my server's Users folder with the copied and permission modified home directories from each local user.
My guess is that would be the fastest way to migrate the users to the network.
My question is are the terminal commands I need to run on each folder in order to make this as seamless as possible?
chown -R username:newgroupname /~path to copied local home directory
Is that syntax right?

The command is correct!!!
But my quess is if you use ACL's to set the permissions you won't need to run the command on every folder
Best Regards

Migration Assistant does not see Home Directories from AD Users

We use AD as authentication domain but home directories are stored local at the client computer. Hence they are backed up via Time Machine. AD Users can use Time Machine like any local user. But now one machine crashed and we wanted to restore the full computer via Migration Assistent. Unfortunally AD Users home directories are not restored to the computer although the home directories are on the backup set. Is there a way to restore the whole Computer from the Backup Set inclusive all Users directories (including these from the AD Users, which had been stored locally)?

So, finally after fourten hours of unattended "migration," I let it continue overnight and in the morning found that the time remaining had not moved a minute. I canceled MA and found that not one iota of data had transferred.
As far as I'm concerned, Migration Assistant ranks lower on the Apple success list than Open Doc, Newton, Pink and Taligent.
Now I have to manually install software I want to use on the MBA, apply licenses, and all the other stuff I would expect from Windows.
NOT happy.

Migrating Users To Server-based Home Directories

When you install a new server and you want to migrate users to server-based home directories and they currently have local home directories (with iCal, iTunes, iPhone, etc.), what is the process?
Will their local data be auto-moved to the server? Will it be deleted? What?
Message was edited by: Jerry Britton1

I went through this many years ago. Here's what I did...
#1: Create the user in Open Directory.
#2: Log in to the local account on the computer.
#3: Using "Connect to Server..." mount the network home on the client Mac.
#4: Copy all data to the same folders on the network home.
#5: Delete the local account.
Now when the user logs in with network credentials their network home will have all their stuff. Some preference files may need to be recreated but that's about it.

Multiple simutaneously logged in users accessing AFP home directories?

Hi,
Many of our problems are described in this guy's blog:
http://alblue.blogspot.com/2006/08/rantmac-migrating-from-afp-to-nfs.html
The basic capability we want is to have multiple simultaneously logged in users to have access to their AFP mounted home directory, which is configured in a sane, out-of-the box setup using WGM and Server Admin.
Multiple user access could take the form of FUS (fast user switching), or simply allowing a user to SSH into a machine that another user is already logged into and expect to be able to manipulate the contents of her home directory.
From my extensive searches, I have no reason to believe this is currently possible with 10.4 Server and AFP.
(here's the official word from apple: http://docs.info.apple.com/article.html?artnum=25581)
I've read that using NFS home directories will work, though.
I want to believe that Apple has a solution for this by now (it's been almost a year since we first had difficulty), or at least a sanctioned workaround. If Apple doesn't have one, maybe someone else has come up with something clever. I find it hard to believe that more people haven't wanted this capability! (not being able to easily search the discussion boards doesn't help, though...)
Thanks for your help!
Adam

Parallels Issue. Track at http://forum.parallels.com/showthread.php?p=135585

Home Directories can't be deleted in Workgroup Manager

I set up a Home Directory at the ROOT level of my server to test it. I was successful so I "thought" I knew what I was doing.
I needed the Directories to be in my XRaid as that's where the "room" is and I expect to have 15-20 Home Directories.
So I deleted the User folders at the ROOT level and unshared them in Server Admin (prob the WRONG order).
Now the path to the deleted Directories still shows up in Workgroup Manager and the little "negative" sign is grayed out. I see no other way to delete it.
Now I'm stuck as it appears that any time I try to create a new Home Directory, it "saves" quietly but the user folder it creates is only 44k (although it includes all the Home folders). When I attempt a Log-In I get an error:
"You are unable to log in to the user account "jeff" at this time. Logging in to the account failed because an error occurred. The home folder for the user account is located on an AFP or SMB server....."
I tried exporting all my Users, deleting then and importing them... same issue.
Any other ideas??
Thanks

Hi
When you install OSX Server by default it creates and shares Users, Groups and Public. This has been the case ever since 10.2 came out. Leopard Server continues this 'tradition'. If you delete any of these default folders after first unsharing them, the server will complain mightily as well as giving you problems.
If you want require a sharepoint for your users networked home folders to reside elsewhere simply unshare those default folders and create similar folders wherever you want them (an XServe RAID for example), share these and continue doing what you need to do.
Whenever I have had to attend a site where the local admin has deleted these folders more often than not it has required a rebuild - drastic I know. I have had some limited success by stopping all the services and unfortunately this would also mean demotion to Standalone for your OD Master and recreating the default folders (name them the same) at the root level of your server's boot drive. You can do it using the finder or terminal:
sudo mkdir /Users
Then restart the server. If on successful login the icon on the Users folder comes back then you should be OK.
Hope this helps, Tony

Network Home Directories for all users

Hi,
I hope someone can shed some light on a possible issue.
I work for a primary school in the UK.
I have Tiger server 10.4.10 running as an Open Directory Master. I have a 1TB XRAID attached to this server where the Home Directories are hosted. I have been told that they are now slow at logging in (I am currently unwell at home so have not confirmed this yet).
It used to be a magic triangle setup but found there were problems with the managed prefs for the clients not being obtained on startup and network logins not working.
The DNS and DHCP comes from the AD still.
The OD has been set up to have the same kerberos realm as that of the AD (is this wrong) as the users are in both AD and OD with same username and password.
The users Home dirs for the OD are hosted as i say on the XRAID which has a striped array of 1TB so the HDD speed shouldn't be a problem.
The server is now connected to a 1Gb switch as are the clients.
I have added more ram to the Xserve (now running on 5GB RAM). I have read that an afp server needs a lot of ram to work effectively. Is this enough?
I have not set up link aggregation yet.
The total amount of users logging in at one time will be no more than 40 users at once as there are only 40 mac machines in the school.
I hope you can help as i would like to have something to go back to school with to tackle this if it does turn out to be true.
Any more info needed just ask.
TIA

Hi. Let me restate so I understand it right. You are using an XServe to host network home folders and also using Active Directory for authentication? I work at a primary school also and we have an XServe that has the users home folder on it, but we also connect to an AD server for authentication. We had some speed issue with logging in but as soon as we set up a time server to ensure that both the XServe and AD server had the same time the trouble was fixed. Hope this helps.

Portable Home Directories in 10.8 Server?

I have a Mac mini Server running 10.6.8. Now that 10.8 is out, Apple will probably stop supporting 10.6 (as is their policy) and that means either slowly eroding security or moving to 10.8. I have been looking at the documentation and it seems underneath it all is still by an large the same basic unix-stuff like postfix, dovecot, a dns system, etc. Giving the lack of support for GUI-managing the more complex setups, I'll probably be doing it command-line (stuff like multiple virtual mail domains, multiple web domains, etc.). Not fun (and a business opportunity for some enterprising software engineer).
But what I haven't been able to see in the documentation or anywhere else is Portable Home Directories. In my current setup, I have a 10.6.8 Server and 10.7 clients. On these clients is a single local administrator acocunt and the rest are 'managed mobile accounts'. These are local acocunts. They work when away form the network on which the server is, but when in range of the server, the server may push settings and stuff. And on login/logout and when connected to the LAN and during work, the home directory of the user is constantly synchronized with a copy of the user's home directory on the server. This means my users can take any computer and get their own account and a synchronized copy of their home directory. They can also take a laptop off line for a while and when they return to my LAN (either physically or by VPN), any changes will be synced. This is a sweet setup and it works with 10.7 clients and 10.6.8 server.
But what I haven't been able to find if this will still work with 10.8 Server. I have looked at teh 10.8 Server documentation and haven't found anything about it. Will it still work somehow and if not, is there a good alternative?

Gerben Wierda wrote:
Or: you create the users anew in the network directory, you replace their home directories with the content of what is on the MacBook (TDM is your friend) and do the chmod. Easier still.
That way, I suggest the migration in that way; because, you can test everything out before the data gets moved over. There's nothing like something going wrong in the setup/migration, and you have to do it all over again.
Kirk, you can always put the Home directories/folder on an external. But if you do, you'll probably want to run this command in Terminal:
sudo defaults write /Library/Preferences/SystemConfiguration/autodiskmount AutomountDisksWithoutUserLogin -bool YES
That sets the system-wide setting to mount external HDs on startup. The default behavior in OS X, probably around 10.3 onward (but Apple may have flip-flopped on this), is to mount externals on user GUI-login, not on startup like internal HDs. The default behavior is a huge problem with network users, whose home directories reside on the external, since the external on GUI login often mounts "too late" and new "phantom" home directories are created (along with warning messages that the home directory can't be found) and you sometimes get duplicate mount points. In short, the default behavior creates a bit of mess. To spare you some frustration, run that command, which will mount the externals on startup, so the home folders are always available.
It's also handy if you plan on creating other shares on the external; it prevents some flaky behavior.
Gerben's "general description" can be applied to Lion and Mountain Lion, although with Mountain Lion you have fewer tools, and you'll often be working in Server.app rather than some of the older tools like Server Admin.
Again, basically you need to:
(1) Setup file sharing, where you designate a directory/folder as a share to hold the network home directories. On the default install, Apple makes /Users a share, and you could (similar to what Gerben did) use that to hold not only local accounts' but also the network accounts' home directories. In that setup all users' home directories reside in the same place. All you have to do then is check the box "Make available for home directories over" and leave "AFP". See below; note the very last checkbox; that needs to be checked:
I preferred to keep the local and network users separate, so I actually use a different share for the network users, and not /Users. If you go that route, pay attention to the permissions, it's somewhat easy to get them wrong. I think I cheated and used Carbon Copy Cloner to clone the /Users directory to another HD, then just renamed the directory. FYI you're actually not seeing this in these screen shots, since I'm using a "fresh install" virtual machine to make the screen shots.
Also if you don't need it, I'd probably uncheck "Share with Windows clients (SMB).
2. You need to setup Open Directory, so you can manage Network Users. Since you want portable home directories, then you might consider using Profile Manager (introduced in Lion Server), which is Apple's latest tool for that. You can also download separate Workgroup Manager as well. Not sure which is better, or exactly why there are both. I think the documention indicated for older pre-Lion OSes, Workgroup Manager is still around.
2a - If you go straight to Profile Manager, and set it up, it will first make you setup Open Directory, then the rest of the setup for Profile Manager itself.
2b - Or you can always "two-step", first setup Open Directory, then later if you want "Profile Manager".
3. Once you have OD (step 2), and the share setup for network home directories (step), you use Server.app to create the network users, and assign their home directory to the share not local. Note the entry "Home Folder"; use the pull-down menu to select your share. See below.
If you forget to set the Home Folder, you can always "edit" the user and change the Home Folder to the share, and not Local Only.
4. To get portable Home directories, I'm pretty sure you're going to have to setup and activate Profile Manager or use Workgroup Manager. Sorry not much details I can provide there, I've only played with it a bit, and was planning on upgrading my MacBook Pro to Mountain Lion before giving it a go again.

Home directories loosing access rights - Urgent help required

We have just migrated around 2000 user accounts onto a new xserve server and we have just set up these user accounts so that there home directory is stored on the server as opposed to locally on each machine. To get past a serious performance issue we changed the rights for the group so that only the owner could see there own directory and they had full read right access. Now there is one group and around 2000 user folders in that group, with each folder having the specific owner. Now after we made this change to the rights for the group to be none, and the owner as read/write access to the folder. We pushed this out using Workgroup manager and applied the changes to all child folders and files. Now in theory, when a user logged on they would only be able to see there own home directory and no one else’s on the server - and this is what happened, for the first 5 minutes... and then without making any changes to their server or the client machine, the user then lost access to their own home directory. The only way we have been able to get around this is to allow the group read access to the parent folder, so if a user navigates through to the volume on the server where these home directories are stored then they will be able to see all 2000 folders (but not access any data in them) Now this would not be such a big deal for us to fix ASAP, however it does cause the client machines to go very very very slow when browsing to open files through various programs. E.g. when you click file and then open in Photoshop or whatever the pinwheel will come up and start to spin for at least a min or so before it brings up the finder. I am assuming that this is because the machine is trying to look in all 2000 odd folders. Does anyone have any idea or suggestions on how we can get around this issue or what we are doing wrong?
We are about to split the users up into groups of around 200, which should have been done from the start (BTW we did test this on a test server before implementing it, however it is murphies law that new bugs had to come up)
Any help would be greatly appreciated.
:S

Thanks for you suggestions; we only used workstation manager to change the preferences. We were trying to change the rights so that the students would not even see the other student’s folders. We ended up setting up the rights similar to how you suggested, but there was still slow performance issues browsing to folders in the finder, because machine would get to the directory /Volume/server.address/mac_students and then search through 2000 folders (And maybe try to index) before going to the next level being the students home directory. So we split the 2000 users into 10 groups (Which really should have been done from the start) This enabled the finder to load a lot faster, but students could still see the top level folder of the other students in the group, but hey at least we were not faced with a "ohhhh boy, it is Monday morning and no students can log in" situation... We will be tweaking the image that is on all the clients to have the default locations in Photoshop and Quark etc to point locally, but that will be a bit of a longer term thing.
I guess my real initial question was if we made a mistake with the rights on how we set them up, why did it work on the test server the whole time, and even on the live server for a few minutes, I would have thought that if the rights were wrong, then it would not have worked from the start?
Never mind it is working now, which is the main thing.
Another question though, for anyone that is reading, is how to you change the preferences of spotlight and where it saves its data.. Basically when a student logs onto a new computer, spotlight indexes and saves results in each folder and we would like to prevent it from indexing and saving to the home directory (Because this is on the server) We can actually see the CPU of the server go up when a student logs onto a machine that they have never logged into before and spotlight starts indexing the new machine. And preferably we would like to not disable spotlight on all the client machines - as students will no doubt like to search. Also should we disable spotlight on the server end? I guess this would improve performance a bit as well.
Thanks in advance for any suggestions

How to specify one ethernet port for network home directories (other for normal filesharing)?

So I'm trying to get Home Directories up and running on a 10.6.8 Xserve (waiting until I get my NFS sharepoints migrated to a Linux server [for other reasons] before moving up to 10.7 Server). But posting here since that will be happening in the next few weeks, and it might be applicable now (so I can at least get that resolved ahead of time).
I have a different DNS entry for each ethernet port: server.office.domain.com at 192.168.0.11 for the first, and homes.services.internal at 192.168.0.10 for the second. DNS lookups for both resolve correctly (as does the reverse lookup).
If I use the Server Admin to pick a sharepoint as an automount for Home Directories, everything is fine, but it picks the server.office.domain.com hostname. Picking that works just fine, but that is also the connection that feeds the filesharing. I'd prefer to split that home directory traffic out onto the second ethernet port. So I tried just duplicating the initial connection (since it can't be edited directly in Workgroup Manager) and changing the hostname to the internal one, but I get an error when attempting to log in (the client login screen gives a very helpful "Couldn't login because of an error" error message) and don't see anything in the server logs.
The client machine shows the following line:
Code:
10/20/12 5:27:42.688 PM authorizationhost: ERROR | -[HomeDirMounter mountNetworkHomeWithURL:attributes:dirPath:username:] |
PremountHomeDirectoryWithAuthentication( url=afp://homes.services.internal/Users,
homedir=/Network/Servers/homes.services.internal/Volumes/HomeDirectories/Users/ user123, name=user123 ) returned 45
(added line breaks so it didn't extend off the page)
So it looks like this is failing because the automount isn't in place, but I'm not sure how to work that out either (i.e. how do I add that making sure it uses the internal hostname?).
Any suggestions on getting this to work?
I realize one solution is just to LACP the two ports, but that is a different ball of wax (I may do that later if I get a 4 port ethernet card and performance limitations demand it).

A possible solution might be this.
On ADSLBOX and CABLEBOX configure different subnets for the LAN, e.g.
ADSLBOX: 192.168.1.0/24
CABLEBOX: 192.168.2.0/24
The MEDIABOX gets these static IPs:
ADSL-LAN: 192.168.1.2
CABLE-LAN: 192.168.2.2
On the MEDIABOX, configure the two network interfaces using two routing tables.
The ADSL-LAN routing table
ip route add 192.168.1.0/24 dev eth0 src 192.168.1.2 table 1
ip route add default via 192.168.1.1 table 1
The CABLE-LAN routing table
ip route add 192.168.2.0/24 dev eth1 src 192.168.2.2 table 2
ip route add default via 192.168.2.1 table 2
The main routing table
ip route add 192.168.1.0/24 dev eth0 src 192.168.1.2
ip route add 192.168.2.0/24 dev eth1 src 192.168.2.2
# use the CABLE-LAN gateway as default, so general internet traffic from MEDIABOX runs over CABLEBOX
ip route add default via 192.168.2.1
define the lookup rules
ip rule add from 192.168.1.2 table 1
ip rule add from 192.168.2.2 table 2
To test the setup:
ip route show
ip route show table 1
ip route show table 2
I don't know how to persist something like this in ArchLinux using netctl. Might require to write a special systemd unit for it. Above is a working example from a RedHat box at my company.
Last edited by teekay (2013-12-04 07:42:22)

Workgroup Manager doesn't create home directories for OD accounts

I'm having an issue where home directories aren't created for OD accounts. My setup is as follows, the home directories are stored on the OD Master (the only Apple/OD/AD server on the network), and the home directory paths are filled as afp://192.168.1.254/Customers, fakeuser, /Users/Customers/fakeuser
This same pathing scheme works fine for local accounts, however for OD, clicking Create Home Directory and saving the account does nothing (no errors, nor folders created). If I ftp into said account, I wind up being directed to /Users (definitely not the expected behaviour)
I am deploying a web based upload system that I want to authenticate against OD users so as to share home folders and permissions with the ftp server, once I have this figured out I will be migrating a bunch of accounts to OD from local.

In addition to potential DNS issues, it sounds like you may be using the wrong procedure to define the users' home directories. You should never have to specify the paths manually; instead, define the share point ("Customers" in your case) to be automounted, and then it should automatically show up in the list of available home folder locations, with all the necessary paths predefined. Here's the full procedure:
1. Run Server Admin, and select: the server name in the sidebar -> File Sharing in the toolbar -> Volumes & Browse under that -> navigate to the /Customers folder in the column view.
2. Make sure the folder is being shared (with it selected, you should see an "Unshare" button near the top right of the window); if not share it with the Share Button (then Save the change).
3. Select the Share Point tab under the file browser (NOT the one above it), and select the Enable Automount checkbox. A dialog will open asking for the automount details; make sure the Directory is set to /LADPv3/127.0.0.1, Protocol to AFP, and Use for is User home folders and group folders. OK the dialog, and be sure to click Save to make the change take effect.
4. Run Workgroup Manager, and select Accounts in the toolbar -> Users (single person icon) tab under that -> some user account(s) you want to configure under that -> Home tab on the right.
5. Select (None) from the location list and click Save (this wipes out any current setting, so we can rebuild it correctly).
6. The Customers share point should be in the list of available locations (due to being configured for automount); select it, then click Create Home Now, and finally Save.

Moving Portable Home Directories from one server to another

I am in the process of migrating users from an older xserve running 10.3 with open directory to a new xserve running 10.5. So far, everything is looking good with the migration, the only major issue I'm running into in my testing is with Portable Home Directories. Presently, the portable home directory on the computer still points to the old server for existing user accounts after they are moved to the new open directory server. On the 10.3 server, the home directories are all mounted under /Volumes/Home, where on Leopard it appears it wants to create the shares under /Volumes/ServerName/Folder. Granted, at present the original server's Home Folders are on a fiber attached raid and in testing I don't have this available. Any suggestions on a way to test easily without moving the raid? Also, is there an easy way to do a mass change on user machines where if I move my raid over to the new server, I can make sure that users data is being backed up to the proper location?
Sorry for the lengthy post, just trying to make sure I'm covering all my bases, heh.

Antonio, thanks for the response. I do have one more question regarding this. On the client side, the mirrors.plist file references the old server FQDN and share name. Because this will be being moved over to the new server, is there an easy method to update the clients mirror plist without breaking the PHD mirror? My big concern here is that either the users will not be able to synchronize phd's or we will have to re-establish all the phd's from the client machines to the server. My thought here is simply using a cname to direct any traffic still trying to hit the old server name to the new server name.

Portable Home Directories over CIFS

I'm trying to configure PHD over CIFS with samba/linux as file server.
It works. But there is a issue. When it synchronizes directory with server, for every newly created folder it complains about problem with sync.But regardless of complain directory is created. I traced down. Error happens when FileSync trying to chflags on directory created on samba share.
Typical error is
0:: 09/12/16 06:49:55.282 EXCEPTION: Invalid argument <-SStoreFileOperator_FS applyPermissionsFromObject: (StoreFileOperator-FS.m:508): chflags('/Network/Servers/cmsdata.tnw.utwente.nl/cifstest/Library/Assistants', flags=0)--> Error Domain=NSPOSIXErrorDomain Code=22 UserInfo=0x10058c170 "Invalid argument">
0:: 09/12/16 06:50:02.221 EXCEPTION: Invalid argument <-SStoreFileOperator_FS applyPermissionsFromObject: (StoreFileOperator-FS.m:508): chflags('/Network/Servers/cmsdata.tnw.utwente.nl/cifstest/Library/Autosave Information', flags=0)--> Error Domain=NSPOSIXErrorDomain Code=22 UserInfo=0x10057cb50 "Invalid argument">
Also it complains in similar way for chflags for couple of files
<PHD> 0:: 09/12/16 06:48:50.852 EXCEPTION: Operation not permitted <-SStoreFileOperator_FS applyPermissionsFromObject: (StoreFileOperator-FS.m:508): chflags('/Users/cifstest/Library/Preferences/com.apple.CoreGraphics.plist', flags=0x10000)--> Error Domain=NSPOSIXErrorDomain Code=1 UserInfo=0x1005839b0 "Operation not permitted">
But files isn't a big issue it is just couple of files from ~/Library which aren't going to be changed often, but complains about every directory - it is definitely too much. And, in fact, it even doesn't really want to set some flags for directories. Most of time it is "flags=0".
Is it possible to switch off this behavior? And not by "unix extensions = no", cause I need support for symlinks.
In fact, if you have mixed mac os x/other unix environment situation with PHD is terrible.
OSX doesn't support kerberized NFS4 in full way, especially through open directory (obviously, autofs doesn't accept vers=4, but even if it would, mount_nfs needs "4.0alpha", while autofs clearly expects number there). Although it is possible to patch sources for both of them, it isn't really solution.
In mixed unix environment AFP to Netatalk is useless, cause it doesn't handle symlinks in proper way (like native OSX server does, translate "slink" fdType into underlying FS symlink.
And with samba it is problem of chflags now. (ACL's also broken with samba BTW).

antst wrote:
Actually, there is a chance that I will add XServe into our setup. But it isn't $500 solution
I was referring to the price of the software only. If you want to add hardware as well, that is a different story.
But, still, Xserve doesn't support nfs4 for linux hosts.
Is that a requirement?
So far, from what I see, best option for file-server in multi-platform environment is solaris.
I think the best option for a server in a multi-platform environment is "each to his or her own". Get MacOS X Server for Macs, Solaris for NFS, and Windows for Windows. They can all access each other, but for system critical tasks like booting and home directories, let them handle what they know best.
It has full support of NFS4 ACLs on ZFS, which means you will also map correctly SAMBA ACLs and Netatalk also supports ACL when underlying system supports NFS4 ACLs (but probably only on solaris).
And in addition you get all nice features of ZFS and probably the best NFS server implementation.
I think you need to review what your requirements really are. You are still going to have 2 out 3 OSes running from foreign servers. You may find yourself back at square one with NFS4 instead of CIFS.
The last time I used Solaris full time was 2006, I think. I was in an organization big enough to have all our Solaris and NFS work done by Sun people on site. NFS went down on a regular basis. We are starting to go back to Solaris at my current big organization because Linux can't handle Multipath and QFS.
Don't get any ideas about me vis-a-vis all those buzzwords. I'm still just a programmer. It is perfectly normal to have multiple servers with different OSes. You can get things working the way they are supposed to work and then see if you can migrate things over to NFS4. I still think you would have more success running MacOS X as the server and getting rid of Netatalk.

Best practice - moving home directories

Hello all,
I was looking for insight on best practices for moving home directories.
I was thinking that using the migration tool would be best to move the directories and then using dsrazor to remap all of the home directories for our users.
We are running Netware 6.5 SP8. I have added a 2TB RAID 10 set to one of our servers which is where I am planning on moving all of the user directories.
Thoughts/suggestions are welcome.
Steve D.

Originally Posted by sjdimare
Moving data from one volume to another on the same server should not require migration, correct? I just want to make sure all of the trustee assignments stay in place.
I also will need to redo volume space restriction on new user templates and the migrated volumes.
First test went quite smoothly.
Steve D.
When you move data (using Windows explorer ect) across volumes the trustee rights drop off. If moving from NW to NW use Server Consilidation and Migration Tool. If moving from NW to OES Linux use miggui. The SCMT has a few other features like project planning and verification.

Migrating home directories to an Xraid

Similar Messages

Maybe you are looking for