Aperture and mobile account

Hello -
Would it be sensible to create a mobile account for a user who uses Aperture?
Has anyone any experience of this - or even just a straight forward network account?
Thanks,
Andrew

Yes, that is a very simple solution. Just create each user and either give them home folders or give them access to a shared folder. In Aperture, just point the location of the library to the network share.
Aperture > Preferences > General then set in Library Settings.
This comes with a few caveats, of course.
As a professional photographer myself, this is a great idea if you have a fixed workstation in an office setting where you have network access 24/7. If you are editing big pics (like in the 10MB + range) your performance will suffer unless your network is very fast and your machines are quite fast.
Now, how you're connecting is another issue. I can only deduce that you are inferring a direct hard line network connection in an office? Not bad. We do it here in my studio on a gigabit ethernet connection. Wireless? Average. VPN or mobile connection outside the office? Oh wow.. prepare to beat yourself with your camera.
One other thing you must remember with Aperture, there is no syncing, per se. If your library resides on a non-local drive, you must access it to get your photos. They are not stored on your local machine, rather your network share. You can set up Previews in Aperture > Preferences > Previews and then you will be able to "see" what your photo libraries contain, but you cannot edit until you are on the local network.
Hope this helps,
Scott

Similar Messages

Using MobileMe with Network Home and Mobile Account

Hi,
I'm having some issues using MobileMe with a new Network Home, frequently seems that after I setup syncing with the network account, which works fine, after logging off and back on to the network account syncing is disabled. After doing some investigating and speaking to the MobileMe support people I think it's related to a 'lock' folder that seems to hang around in the ~/Library/SyncServices folder for longer than it should do, if I do a successful sync then wait for this lock file to disappear then log off everything seems fine, otherwise the sync is disabled and I get a 'Sync unavailable' dialog saying there is more than one network home syncing, which there isn't.
Also, I'm wondering if the mobile version of the network account should have MobileMe syncing enabled as well or will the Home Sync just sync everything (i.e. Address Book, Contacts, etc.) back when plugged into the network ?
Mark

This definitely sounds like something you might want to take up with Adobe Customer Support. (In case you didn't know, the people here are just other users, like yourself).
If your company bought 300+ licenses, I'm sure they'd be willing to help.
Will they be able to solve the problem? Well, that's a different issue altogether.

Mixing mobile account and network account.

Is it possible to have mobile account on some computers and network account on others and having the same user logging in (only one login at a time) without sync issues ?
I have tested it with account preferences set on computers and it is working nice until I have been logged in on a computer with networked account, then I experience sync issues. Every time I log in mobile account I got a dialog window asking me to select "Sync Later" , "Mobile" or "Networked". It does not matter what I select, the dialog comes back everytime I log off and on with the mobile account. I have only managed get rid of it by deleting mobile account and sync it again.
Message was edited by: kenguru

Again, thanks for taking your time explaining this for me.
After been reading the User Management documentation from apple about Managing Portable Computers (Chapter 8), I got the opposite impression about running Mobile Account on multiple computers. From this text, as I read it, it is a common thing to do, as long as we are aware of sync issues that might occur and know how we shall deal with it.
So I'm a little confused about this topics, as it seem to make sense what you are saying, but the documentation says something different.
I have tried setting sync preferences on the user instead, so that every login is made with a mobile account on every computer. That seems to work ok. Off course sync issues may arise, but here the the file sync can be fixed through the dialogs windows that pops up. Unlike under the mix of network logins and mobile account logins where it doesn't matter which location I set to be the place containing the most recent files. This only occurs after a network account login. If I have been logged on another computer set up with mobile account everything syncs nicely. I think
So for now, I think I will stick with setting up users with mobile account preferences and skip the networked account.
Does this make any sense or am I still mistaking here?
Ok, thanks for all you help.
Bernt

Open Directory and Mobile Home Folders

Hi All,
I am a bit confused about Open Directory and Mobile Accounts! here is our scenario. We have an Open Directory setup and all Accounts are set to mobile, accounts are almost 250+, my main problem is the Synchronization Conflicts, the accounts are automated to sync every 30 mins, the problem is every now and then schronization conflict windows popups, our users are complaining almost everytime, another problem is all of the users home folder has a qouta of 5GB, problem is there are users who excedd on the qouta some goes up to 60GB and 100GB, how do i solve this two problems. i am about to loose my mind. We setup like this in order for us to have a backup of all files of the users in case problem arises in the workstation. i have notice that synching file error comes up if you have temporary files used by any applications. the home folder of each user will exclude library, trash, music and entourage databse. Please Do help me.!!! Anyone who knows..?
Environment
OD Server - MacOS X Server Tiger 10.4.4
Workstations - mix MacOS X Tiger 10.4.4 - 10.4.7
AFP Home Folder - MacOS X Server Tiger 10.4.6 mounted Xsan Volume for home folders
johnaris
PLEASE HELP!

Thanks for the info, by now i will look into that little utility that is very helpful (console!)
Yes, I was thinking of synching our users at login and logout, the problem here is that, users here has bigger home folders.. mostly about 3GB, and it will took time to login a user, about 6-10 mins, depends on the network, we have networks users that that has slow networks and fast network on video editing users. What I did is that i excluded the Library in the synch options on each unit here, since we are not using Apple's Mail and iCal, it did minimize the synching error but the temp files and date discripancies are mostly that will generate an error, I am having really problems with this.
thanks for the info i really appreciate it.

Login.keychain and mobile user accounts

After removing a corrupt login.keychain file in a mobile user account, the user could no longer log in to their account when off site. What account login information is kept in the keychain file of a mobile account?

I don't have problems syncing other files that are also system packages, like iPhoto ones... although I have a terrible suspicion that again the sync agent only sees a single file, not a bundle.
I assume that the OS doesn't have any problem with packages since they are used pretty much elsewhere and they are basically a folder with a specific file inside that "forces" the OS to show us as a single file, instead of letting us see directly the content.
Even the new disk image format that Apple recommends to be used in order to speed up Time Machine backups (.sparcebundle) is based in package (or bundles, whatever you prefer to call them)
The main issue here might be the folder structure inside.
If you do a "show package content" and, for instance, check the thumbnails folder, I can easily see some chars that might create some confusion if not properly escaped during the sync, like on this example:
My Aperture.aplibrary/Thumbnails/%pARYo%fT52I77jmdf8mqQ/AP.Thumbnails
(Those "%" are so prone to errors if not properly handled)
Time Machine doesn't have any problem with both packages and those chars, so I truly hope that they use TM tech and improve the way that the syncing agent work.
Anyways, Aperture seemed a nice app.
I'm really sad that I can't use it because of this... specially when I'm considering getting a new digital camera.
I understand that it was recently released so let's hope that Apple can figure out what's happening and release an update (to either Aperture or Mac OS X Server) in the next few months.
Take care.
Pedro Fardilha

I'm using a Mac. I "upgraded" to LR5 from LR4. I do not want to be a member of the "Creative Cloud". I just want to use the software I purchased, specifically to upload to my SmugMug account. Is there a way to use an add-on to do this? Aperture and L

I'm using a Mac. I "upgraded" to LR5 from LR4. I do not want to be a member of the "Creative Cloud". I just want to use the software I purchased, specifically to upload to my SmugMug account. Is there a way to use an add-on to do this? Aperture and LR4 were easy but I'm finding it impossible without subscribing to CC.

Sorry, maybe I don't understand, but why do you feel compelled to subscribe to CC if you already have a permanent Lightroom 5 licence?
For the SmugMug plugin, a simple Google search ("smugmug lightroom plugin") gives this link to download the plugin: http://help.smugmug.com/customer/portal/articles/121321
Another way is to click the button "Find more services online..." in the the Publish Service section of Lightroom, and to search for SmugMug in the Adobe Add-ons portal; you will find a link to the latest plugin: https://creative.adobe.com/addons/products/1755

Mobile Account Creation and old topic

http://discussions.apple.com/thread.jspa?threadID=1786733&tstart=1 -- This was never successfully answered and has been archived and marked as so?
The problem it turns out, is that Leopard doesn't seemingly like the AD user's home folder location. I've verified this still as an issue today, on 10.5.7. I tried to create a mobile account for a user on a new laptop i got -- it would prompt me for the password three times, saying it's incorrect each time before the account creation is canceled.
If in Server 03 AD tools you first switch that user's "Home Directory" to local (or a mac server), this issue will not persist. On the AD Binding/Directory utility un-check "Require Confirmation" before creating a mobile account.
Then you should be able to log out and login as the user (may have to first delete the user's local directory if one has been created under "Users"), so long as the Home folder is set in AD to a location that is seemingly 'agreeable' with the mac os.
Message was edited by: Oh4Sh0

The usual approach with Open Directory is to either use Workgroup Manager to define a managed login preference for a computer group to define that those member computers should cause the use of mobile accounts on those computers, or to do the same thing via Profile Manager.
Note: If you are using Mavericks you must use Profile Manager as it does not support this via Workgroup Manager managed preferences.
This will not require users to need admin authorisation.

Mobile account doesn't complete initial creation and sync process

I'm trying to setup a mobile account for a network account but it won't complete the sync process on the client MacBook Pro. Both the server and the MacBook Pro are running 10.5.5.
When I login to client it prompts me to create a Mobile account and proceeds with the sync to create the account, but when the sync is complete it just logs in with the default account setup. None of the user files or settings (desktop image, preferences, etc) appear. The sync process says "Checking..." for all the files that supposedly get copied to the client, but it looks like it doesn't complete.
Is there a way of knowing what the problem is? Is there an issue with the user's home directory, some file that prevents the sync and mobile home creation from completing?
Thanks.

I solved this myself. The user ended up have a folder on his desktop that contained a backup home folder from an old powerbook that he was trying to save. It was a complete home folder, Documents, Library, etc and I thought it might be interfering with the sync of the normal home folder. So I created a folder called Bad Stuff in the home folder and copied the old powerbook home folder into it. Then opened up the Sync Settings and excluded the Bad Stuff folder from the sync. And it worked, the sync when fine and is resyncing fine.
Hope that helps with other people with a similar problem.

Mobile account setup stops syncing and acts like a network user

Mobile account setup stops syncing and acts like a network user system under ODM
Setup: Mobile laptop users authenticating against an ODM. Every user has a networked home directory on an Xserve. The whole setup is 10.4 (client and server). All systems run a standard image. Most effected systems have been re-imaged since the onset of the issue.
Issue: Some of the users are not syncing properly every time. It is as if the system forgets it is a mobile system and reverts to using the User's network home (instead of saving to /Users and syncing). If the user is effected, the system will not even accept cached credentials if they are off network. This forgetfulness does not seem to follow any pattern and does not effect all of our mobile users.
In mucking about trying to find a cause to this issue I ran across an oddity in all effected systems Netinfo database. The users are each listed twice. Each entry has the same username, short name and UID. Also, In each case one record looks wrong... this varies somewhat from user to user, but in each case there is marked difference in the record's contents. Deleting the incomplete record in Netinfo manager seems to solve the issue (seems, as we are very early in testing this).
Anyone have a clues as to where this double came from? The only lead so far is that it looks like the users having issues pre-date the use of mobile accounts. At some time they all had local accounts that authenticated against the ODM but never synced or had networked home directories. The pool of users who just got laptops (and thus never had a local account) seem unaffected so far.
Also, what is the best way to browse the ODM master to find these duplicates?

I have a similar issue with computers bound to Active Directory. Users occasionally have a problem logging into their computers even though their account is fine. Logging in as Admin and running netinfo manager always shows duplicate user accounts. Deleting the one that says disabled always clears up the issue. I'd like to find a startup script that would delete the disabled account, thus preventing the issue.

Lion Server Setup (Network Login/Mobile Account and more...)

Hardware:
     Mac mini Intel Core i7, 2 GHz, 8 GB memory (Server)     x 1
     iMac 21.5" 2.8GHz Intel Core i7, 12 GB memory (Workstation)     x 6
Operating System:
    Mac OS X Server Lion 10.7.4 (11E53)
     Mac OS X Lion 10.7.4 (11E53)
Relevant Software:
     Server.app Version 10.7.4 (1.4.3)
     Workgroup Manager Version 10.7 (400.3)
     Server Admin Version 10.7 (355)
So my head's swimming with "I dunno's" and I've been perusing probably all the wrong threads trying not to sound like a noob and find the literature that will finally lead me to a solution. This is my first rodeo so make no assumptions about my experience (maybe).
Short Version
I can't login network users. I get an error "You are unable to log in to the user account "<%short_name%>" at this time. Logging in using >console tells me this No home directory: <path to home directory>    i.e. /Network/Servers/department.domain.com/Department/Accounts/bbunny
If anyone can point me where to read, I will do so.
Perhaps a longer discussion on how to verify that the proper permissions exist on the share/home directory in question and what those would be.
More detail...
I want to setup a Mac Mini server to have network login accounts stored on the 2nd data volume in a directory we shall call Accounts*. Here all the "network users/logins" have their home directories, so that when they login at the workstation the idea is the workstation will sync their account and allow them to login, if the server is not available, the hope is I can configure it to allow them to login if they've logged in before and the files will sync when they are able. That being the ideal, I get the impression that for best practices, Apple is discouraging the use of mobile accounts that use Home Sync perhaps because it's reliability has been iffy, please advise. A windows user might think of this as "roaming profiles" but, if I understand it, its a little more than that.
Note, I do not want to login to the server and actively work on that network share, I want the account to be local and sync'd as needed. But I want the user to be able to sit at any of the 6 other workstations and see the same documents, emails etc. Obviously if the server is down, it won't be possible to authenticate, but I think it should have cached credentials that should allow the user to login if the server is down and still go about their work.
This is the small picture...there is a larger picture that involves, parallel virtual machines of Windows Server 2008 R2 on server and and Windows 7 on the client, ical, ichat and perhaps wiki's.
I apologize for the roughness of this question, in the interest of brevity, I have plenty of problems that led me here that I can expound upon if asked.
Also a silly question someone might know the answer too, Why does the login payload settings that I have pushed to a workstation device, sometimes vanish inconsistently upon logout?

Ok, Some Good news and clearer understanding to disseminate in this post I hope it helps
"the Universe" so I am posting it here in my "ever-the-noob" blog on apple forums.
Problem
What do you do when you get an error when logging into a mobile account setup?
One symptom would be the error message below...
     "You are unable to log in to the user account "<%short_name%>" at this time.
Logging in using >console You get the message…
     "No home directory: <path to home directory>"
     or
     "You are unable to log in to the user account "<%short_name%>" at this time.
     Logging in using >console tells me this No home directory: <path to home directory>
Solution
Do the check list…
Short Version
Sever Admin.app > Access (Key Component)
Check Permissions on directories for your file shares.
(The reason stuff doesn't work especially when you're rebuilding/recovering a server)
File sharing setup (Turned ON, Home sharing Enabled)
Directory Utility > Directory Editor or dscl
( Do not underestimate the importance of this part!!!!
Use white-gloves when you're handling it though!!! )
Workgroup Manager
(You're poopy "main" interface that really is a "window", not a "door", but maybe Apple likes to do things "Dukes of Hazard" style?)
Long Version
Check Sever Admin.app > Access
Make sure that your user has the "Proper" access. For me I created a test user from Server.app and saw what access he had as a way to "check myself for a properly created users" and because I think one is kind of on his/her own using WGM and duplicated the same access. (I was a little neater, though and did it with a group, not individual users, that would have been a mess!)
Server Admin.app > Access
Click the "+" sign, sort by UID and Add the imported users to the following Services…
( You can use a group, but understand when Server.app creates users they get added
individually to each of these groups. )
Address Book
AFP
iCal
iChat
Mail
Profile Manager
SMB
VPN
Check Permissions on directories for your file shares.
          (That's an understatement) I could go in depth about all the crap I had to read about, I still
          know I am missing a chunk of tech brain when it comes to the particulars. Basically, I boil
          it down to this…
          Permissions require thinking about things first with regards to POSIX permissions... good
          ole ls, chmod, chgrp, chown to the rescue with ugo permissions or the old 755, 600 etc
          stuff.
          Apple's file-sharing access uses this as a starting point to see what the user is allowed to
          access.
          I also needed to use chflags once to unhide a file that I mucked around with using xattr.
          I still haven't figured out why folders can lose their triangles, but I didn't find out if you cp or
          move them from terminal, the triangles come back in the moved or copied directory. For a
          minute I thought it was because cp alone doesn't preserve flag attributes, but mv actually
          works by doing a cp that preserves the flags, unless it's a bug. I dunno.
          This helped me get my file visible again...
          chflags hidden path_to_file
          chflags nohidden path_to_file
          Read up on those manuals, if you're not a terminal type go to apples website
          http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/
          or download...
          http://www.bruji.com/bwana/ I thought that was cool.
          or if you prefer to read the manual in pdf try…
man -t sharing | pstopdf -i -o ./Desktop/Sharing\ Manual.pdf
          man -t chown | pstopdf -i -o ./Desktop/CHOWN\ Manual.pdf
          man -t chmod | pstopdf -i -o ./Desktop/CHMOD\ Manual.pdf
          man -t chgrp | pstopdf -i -o ./Desktop/CHGRP\ Manual.pdf
          My basic guideline was avoid using ACLs if at all possible, if you try to use them, things
          can get crazy complicated, take notes and plan, baby. If you read above, opening up
          permissions wide is wrong though. You would restrict permissions tightly to begin with and
          then place ACE (Access Control Entries) to specifically target the rights you want to enable.
          Here's one that's obviously a novice attempt to do this, but since the novice is the only one
          speaking…. here it is, Universe… >:P
          sudo chmod -R +ai "admin allow read,write,delete,file_inherit,directory_inherit,search,list" Department/
          That allowed my admin to do all the things a normal user could do so far… It fixed things for
          my admin, which made me happy. I really hate having to authenticate or sudo just to see
          the contents of a nested directory. I could explain it, and even give a few notes on why its
          probably overkill, but I will attempt to look less stupid till "poked".
          There's another command line utility I STILL haven't read, which may bear mentioning
          because…well I haven't read it. umask (see wikipedia or unix.com)…I worked past my
          problems without going into it so far, but obviously it's there, and it serves a purpose.
          I also found this article helpful…and educational. :O
          http://www.bresink.de/osx/300321023/Docs-en/pgs/ACL.html
          (          Its enlightening to hear the air whistling between a developer/coder's ears, still it's
                    apparent he has a clear idea what's going on.
                    Ever wonder why when you use get info to check or assign permissions it kind of
                    flakes out and doesn't take? Read this article!          )
          Second, if you can't obtain the "specific" permissions you need with POSIX, chmod also
          can set the 2nd category of permissions, which windows users may be familiar with
          Access Control Lists (ACLs) and here you get some really fine granularity...messy stuff.
          All in all, if I felt I could guide you through these murky waters, I would, but I think I'll let
          the professionals weigh in on that one and cut my wall-of-text to ribbons.
          To heuristically check I would connect from a client as one or two of my users and see what
          folders I could mount as a share, armored with an understanding of what ls -le@O * showed
          me in Terminal.
3.)           File sharing setup (Turned ON, Home sharing Enabled)
          Here is an example of using command line sharing utility where each share is properly
          labeled (that took a bit for me to figure out) still this share only enables the AFP share as
          you can see from my flags.
sudo sharing -a /Volumes/Hard\ Drive/Department/Database -A Database-afp -F Database-ftp -S Database-smb -n Database -s 100 -g 000 -i 10
          Then you do a sudo sharing -l and get back what you just did…
                                        List of Share Points
          name:                    Database
          path:                    /Volumes/Hard Drive/Department/Database
                    afp:          {
                    name:          Database-afp
                    shared:          1
                    guest access:          0
                    inherit perms:          1
                    ftp:          {
                    name:          Database-ftp
                    shared:          0
                    guest access:          0
                    smb:          {
                    name:          Database-smb
                    shared:          0
                    guest access:          0
          If you mess up the sharing command, you may not be paying attention (I wasn't) but there
          are a lot of defaults that Apple will just assume you meant to do anyway and it won't read
          any of your flags, you have to get it right or the flags will be defaulted.
          (          Basically I could tell I was bombing it for one, I explicitly only wanted afp working, but
                    the default was afp and smb. So each time I ran sudo sharing -l after I shot my sharing
                    command…back would come smb shared: 1 and I knew that wasn't right. Also my
                    custom names were defaulting to the name of the directory not the name I had
                    specified.           )
          I like to know what protocol my share is over so when it doesn't work, I know which protocol's
          are connecting. It's not full-proof, but it's a bookmark. I wish the network browser would
          identify the protocol that its available listed shares are using, because small visual queues
          like that help when you're trying to see what works. Maybe that's something I should
          investigate via the command line?
          As a note about reading forums, I discovered using command line that "\" is kind of like a
          way of going to next line neatly with long commands…."\ " is a way to insert a space. As you
          can see above where I have a volume with a space in it.
          Removing shares was a little trickier though, sharing -r Share\ With-space didn't work….I
          had to enclose it in quotes and do "Share With-space" instead. So nooby beware!
          (          *nix users are now rolling their eyes at this tip.          )
          I wasn't sure how you enabled a share for home directories from the command line, maybe its
          in the manual, but I was up to my eyeballs in manuals already so I haven't gone back to
          revisit this question since my work around was to go to Server.app and verify that what I set
          up in the sharing in terminal was being reflected in the gui…sort of my own MVC
          (model-view-controller) check.
4.)           Directory Utility > Directory Editor or dscl
Make sure what you see in WGM and Server.app are reflected here….to that question let's
          take a journey where I did some exploring about that.
Ever really wonder "WHY CAN"T I REMOVE AN OLD HOME DIRECTORY SHARE?!!!"
          Ah, then you will  - LOVE -  this tip…
          (          Provided my testing or yours, later, doesn't prove that in my ignorance I've broken
                    Open Directory. Remember, WHITEGLOVES!!!! but here we get a little dirty. I think of
                    OD as Apple's Registry, but that's not what it is at all. However, you as the user do have
                    to "****" around in it from time to time.          )
          I scoured the forums and everyone was saying things like "You have to change your server
          role" etc. which seemed a little bit dumb to me (dumb because you're pushing views around
          not "controlling"), and well, yea, that share that I couldn't modify or delete was REALLY
          bugging me.
          Now hmm… Before you do ANYTHING, how do you try to not hurt yourself…in Windows you
          can make a Registry Backup….(yea bad analogy) In Server Admin.app you can go to your Open
          Directory Service > Archive and Choose a place to Archive your information. (Figure this out by
          yourself, this is getting long…sheesh! It's easy. Restoring is just as easy and painless.)
Before we can remove the entry we "SEE" in WGM we should make sure no
          one has it selected so as not to "corrupt" the OD db, so in WGM first before going to Directory
          Utility set the Home directory to "None". (We need to remember to set this to a correct share
          later….Mental Note!!!)
          Now Open Directory Utility
          Method 1
          System Preferences > Users & Groups > Login Options
          Click the Lock to make changes…
          Authenticate -> click "OK"          (do I REALLY have to step-by-step this?)
          Network Account Sever: • Local Server - click "Edit" button here.
          Open Directory Utility > Directory Editor
          (          Wow, did Apple hire someone from Microsoft? You'ld think with all their research in to
                    Human Interface Design that's WAY too many clicks to get to something you need.          )
          or
          Method 2 (It's good to know about this directory, neat-o speed-o app's hidden here.)
          Use "Go to Folder" Under Finder > Go > Go to Folder...
⇧⌘G /System/Library/CoreServices/
          Click "OK"
          and Double click Directory Utility.app
          or
          Method 3
          Terminal
          open /System/Library/CoreServices/Directory\ Utility.app/
          Now From the Directory Editor Pane you will see a Pop-up menu Labeled "Viewing"
          You should glance through this and get to know it. You should use it to see what
          information is really being stored about your Users, Groups, Mounts…
          We are interested in Mounts, which is where we want to go…and there is the pesky
          mount that you will see reflected in WGM.
          Authenticate, and delete the bugger.
          Quit WGM and restart it. Voila, bad share is GONE!!!!!
          a.)          First select all my users
          b.)           Then I clicked on the "+" and added the correct share
                    (          Remember, I only showed you the first one we created, this is another and
                              for THIS one you HAVE to go into Server.app and verify that it is set to be
                              available for Home Directories in this case for AFP.          )
                    For the home directory entry you do this...
                    afp://computer.domain.com/Accounts-afp
                    %short_name%
                    /Network/Servers/computer.domain.com/Volumes/Hard\ Drive/Department/Accounts/%short_name%
%short_name% is a wild card for the short name there are other wild cards check out Apple's
                    Documentation on them. I lost the link sorry \<shrug\>
          Interesting dscl commands…(check it out in command line form and compare side by side with
          what you see in the GUI Directory Utility)
          dscl . list /users
          dscl . list /groups
          If you want to output information about each user, though, use readall:
          dscl . readall /users
          dscl . readall /groups
          And if you need to programatically parse said information, use -plist to make your life easier:
          dscl -plist . readall /users
          dscl -plist . readall /groups
          This made a little more direct sense to me, language wise…but fyi "." is kind of a wild card I think so the first
          commands I think look in ALL directories local, Search, LDAP whatever you have. The command here
          corresponds to the Entry from the Pop-up menu "…in node > Blah…" see GUI of Directory Utility to confirm.
          dscl /LDAPv3/127.0.0.1 -list /Users
          dscl /Local/Default -list /Users
5.)          Workgroup Manager
          Remember this is a utility that is not long for this world. Apple's Mountain Lion is rumored to fully
          replace it, why? Yea, Apple's making a go at MDM (Mobile Device Management) and somehow
          desktop computers are being pulled/dragged along for the ride. I have plenty of issues with
          Profile Manager, but I'll likely revisit it in a couple of months and see where we stand.
          Anyway, treat this baby like the bottom rung, because, well it is built like you start your
          foundation here, but it's just a viewer with controlling "tweaks". Use the other areas to get a solid
          grasp of what is actually going on. Server.app is where you should create accounts you can
          feel are safe. When you create accounts in WGM, you are responsible for making sure they
          have the appropriate EVERYTHING.
This list is by no means complete, but these are the areas this noob is or was prepared to talk about.
Good night for now. Enjoy climbing my wall of text, and yea sorry about that. :O Run for you lives!!!!
- Signed Shadowwraith

Mobile Accounts - Sync of iCal and Desktop Background Fails

I just set up mobile accounts and mobile home syncing on my computers so network users have a local home rather than just their network home. However it is interesting to me that the desktop picture is independent of the network home. That is to say, each machine has its own desktop picture for any one account.
However iCal does the same thing and thats a problem for me. For example, if I set up iCal to sync with my gmail on on computer, the other computers will not do it. I'm trying to avoid going into every computer and setting up the calendar preferences because that would be a pain in the tail.
Any clues?

Ditto. I am having the same problem. I don't understand why ~/Library/Application Support/ doesn't sync. There are two entries in the exclusion list, but none of them would prevent Mail, iCal, AddressBook, or iChat from syncing their configuration (.plist) files.
The only reason I bought this Mini Server was to manage these portable home directories (or Mobile Accounts) so that my family could login on any Mac and have their account all setup with everything configured and files available as if they were on their primary Mac.
Really a bummer!

Aperture 3 and Mobile Me Gallaries

I'm using the trial version of Aperture 3 and tried to create a Mobile Me Gallery. I created the gallery within Aperture and published it. However it seems to be published to: http://homepage.mac.com/username. As a result it doesn't show up in in the Mobile Me Gallery which has the domain: http://gallery.me.com/username. Is there any way to publish a Web Gallery/Journal directly to Mobile Me? If one selects a single photo, or a group of photos, and clicks the Mobile Me icon in Aperture's toolbar, it publishes correctly to Mobile Me. My settings for Mobile Me is System preferences are correct. Any ideas?
Thanks

Since there have been no replies to my original question, I'm thinking this is just the way Aperture works. It's easy to select a group of images and click on the Mobile Me icon to create a Mobile Me gallery containing the selected images. However if you first create a Web Page or Web Journal, and drag images into it, chose a theme, add text etc, and publish to Mobile Me it publishes as a web page to your iDisk in the Sites folder, I think. The problem as I see it is that if you don't remember the URL, it's hard to display the web page, and as far I know, you can't display the web page using Mobile Me. I mistakenly thought the web page would show up as a link within my Mobile Me galleries or be displayed there along with other galleries. This is obviously not the case. Is there a way to integrate web pages created in Aperture with iWeb? Has anyone done this? Or is it easier to publish web pages to other hosting sites?

What is 'mobile account' and how does it work?

This is a hidden feature in Mac OS Leopard, that I believe require an Leopard Server on the network.
I have not found it in the regular user interface, but it can be revealed by following the below process:
1. Go to System Preferences > Accounts
2. Unlock
3. Search for mobile account, and press Enter
4. Wait for the Mobile account options to show up
What is this feature? How does it work?
I have found no references to it in the normal documentation.

Google is your friend:
"A mobile account is a Mac OS X Server user account that has been copied to a local computer and remains synchronized with the server account so that both locations contain a matching set of data."(Mac OS X Server User Management, p. 46).
And it has been around since 10.3, so it is not something new to Leopard.
see: http://www.afp548.com/articles/Panther/mcx2.html

I'm using aperture 3 and mobile me to set up galleries which I send to friends. My question. Will icloud allow me to do the same or will i lose this function when mobile me closes down in July.

I'm using aperture 3/mobile me to set up photo galleries which I send to friends. My question. Will icloud allow me to do the same or will I lose this function when mobile me closes down in July. If this function isn't part of icloud does anybody have any suggestions how I can do this in future through aperature. Thank you

You will have to find a new hosting service for your galleries, when MM is gone; but you will still be able to create the galleries with Aperture. Export them to your disk and upload them via FTP to your new hosting service.
See these support articles: Migrating from Mobile Me
http://www.wilmut.webspace.virginmedia.com/notes/migrate/frommobileme3.html
and this FAQ about Mobile Me and iCloud Transition http://support.apple.com/kb/HT4597

Mobility and Network account Sync

I'm using Network Account and I sync my MacBooks with Mobility in Workgroup Manager.
In Terminal I see that files dotted (.ssh, .profile, .....) are not synced at all.
I try to modify "Home sync" in Mobility in Network Manager, but nothing happened.
Any suggestion?
Thanks!

SOLVED!!!
I hope this is usefull for others!
I do this:
1) Login in your user
2) Enable sync Rules in Workgroup manager -> Mobility (I use Workgroup manager installed in my client)
Manage: Once - Sync: login, logout, background, manual
In options choose Manage: Once - Sync in background: Every 20 minutes - Show status in menu bar
3) Create a temp fake file in home client to force update the modification date (I use terminal):
touch ~/.fakefile.txt
4) Logout and login in your user from client and wait that the sync finish its job
5) Go to user System Preferences -> Users and Group -> Mobile account and setup your preferences about sync as you want (you have to chek the logout for full sync)
6) Delete the fake file (I use terminal):
rm ~/.fakefile.txt
Now you can try to create a hidden dotted directory/file and try manual sync to see if it is syncing.
mkdir ~/.fakedir
and after you see the sync (remember, this is just for test) you can delete it
rmdir ~/.fakedir
Now, in my clients it was all right.
Ciao!

Aperture and mobile account

Similar Messages

Maybe you are looking for