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

Similar Messages

  • Portable Homes / Mobile Homes and Network Shares

    So, i'm now using portable home and its working pretty well.  Gave up on using Profile manager to configure it and using WGM instead. 
    But, I also have a variety of network share points that I'd like to have available on the road, including when I don't have internet.  Right now, I can access them via VPN which works ok, but is there any way to sync share points just like my home folder?
    In my setup, I'd be the only user who has this level of access to the share points---i woudn't set up any other users to be able to sync them. 
    Doable?
    I currently use dropbox, but dropbox really isn't secure enough for my business (healthcare), and I can't really use dropbox to sync network shares
    I've looked at Owncloud, but it looks like the only way that Owncloud will sync network shares is if I give read/write access to those folders to the _www user, and I don't fully appreciate the security implications of that and would like to avoid it.
    Anyone got a better idea for making the contents of several network shares (on an OSX server) synchronize to my laptop (which is bound to the server and has a mobile home) for on and offline use?

    Aren't you going to run into update conflicts when someone back at the office updates files you also update when offline?
    Perhaps a cellular data plan would solve your 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

  • 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!

  • 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 Preferences visible on Menubar for Network Accounts

    On Mobile Accounts (setup with Profile Manager), acting as network account (home folder in server), the mobile account preferences are shown on the menubar. In addion, it says "last home sync" incomplete. Both are wrong according to my understanding.
    However it makes sense - and it if the case - if the account is really working as mobile account with local home folder on a e.g. macbook.
    Does anyone has the same issue?

    I have the same issue. No fix yet.
    One of my machines has joined the network and seems to be ok in almost every way...clearly with the exception of this way.
    I will post if / when I find a solution.
    W

  • 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!

  • 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

  • Mobile account can't login when connected to network

    I have a 10.6.3 mobile account set up on a laptop that's bound to an AD domain. The mobile account creation worked great, as expected, and the user was fine for a few days.
    Then the user reported that he was no longer able to log in to his mobile account. After troubleshooting a bit, I noticed that if he's NOT connected to the company LAN where the AD domain is located, he can login fine. But if I connect him to the company LAN, the machine complains that his password is wrong (and we've reset the password in AD, so we know it's correct). So if I flip him back off the network, his login works again.
    There are many other mobile accounts working on this same LAN that aren't having this problem.
    Anyone seen this or know what I might try?
    Thanks.

    Trying turning on DirectoryServices debugging and see if you can scare up any more data:
    sudo killall -USR1 DirectoryService
    Then monitor
    /Library/Logs/DirectoryService/DirectoryService.debug.log
    Even without debugging, you might want to look at
    /Library/Logs/DirectoryService/DirectoryService.error.log
    and
    /Library/Logs/DirectoryService/DirectoryService.server.log

  • Network accounts instead of Mobile accounts

    All of a sudden with any of our images and fresh build form CD, once joined machines are placed on the domain. When a network account logs in to them they get netowrk accounts instead of mobile accounts. Not sure what caused it but looking for an swer to why. Anyone have any ideals? Running Snow Leopard in an Active Directory environment.
    Thanks,
    Indiana

    you set up rules that control the syncs so you can decide when, how often and what gets synced.
    The time it takes to sync at login/log out is the only real frustration with mobile homes.
    Basically you have two types of sync: login/logout and background
    Login/Logout happens when you log in or log out (obviously!) and is meant to be used to sync the library and other files that can't sync while they are in use.
    Background sync happens on a schedule that you can set, and is meant to sync the rest of your home folder except Library and microsoft user data
    You can adapt the rules however you like though, and exclude individual files, folder or sets of folders from either or both of the syncs
    Its best not to be logged in to the same user at the same time on multiple macs, cos it could get into a real mess, you would log out of Mac A then log into Mac B and because Mac A completed its sync on log out then Mac B will have all the upto date files.
    If you did log into the same account on different macs at the same time it would show you syncing conflicts and you would be given the choice of saying the correct file is on This Mac or the Network Home

  • Mobile accounts reset to normal network accounts ?

    Hello
    I've switched my network users back from mobile accounts to normal network accounts after experimenting for awhile. I have deselected the mobile account preferences for all my machines in WGM and deleted all the local home folders created by synching my network accounts on the local machines in Volume/Users. There's obviously more things I need to do, as:
    Some desktop machines allow users to login normally with their network account and mount the network home at login (shortcut in dock via MCX) as before mobile synching. This seems to be only for machines the user did not use when there were mobile account prefs. set .
    Other machines create a new local home for the user but also leave a question mark in the dock for their "User's Network Home Folder"; which mounts with full access when clicking the question mark.
    Lastly, some machines are not mounting the network home at all, but authorizing the user with their LDAP account and making a new local home instead.
    Is this a cache, preferences or corrupt config. issue or something else?
    thanks
    Xserve G5, G4s, eMacs, iMac G5s, 10.4.5 all

    Deleting the mobile user account records in System Preferences>Accounts solved it.
    http://www.macosxhints.com/article.php?story=20031222232124568

  • An unknown error occurred while performing a sync operation. Please check your account and network settings, then try again.

    hi,
    i cannot perform any syncs / back ups (including mobile me) on my imac other than old ipods.
    i recieve this message
    "An unknown error occurred while performing a sync operation. Please check your account and network settings, then try again".

    hi,
    i cannot perform any syncs / back ups (including mobile me) on my imac other than old ipods.
    i recieve this message
    "An unknown error occurred while performing a sync operation. Please check your account and network settings, then try again".

  • Mobile Account Sync still occurring outside network

    Hello;
    From everything I have read I was under the impression that once I left my network, my mobile account would not sync but was of course still usable as it is a mobile account and the homefolder does reside on the local hard drive.
    My mobile account still syncs from home. What am I missing or did I just misunderstand?
    Thanks.

    If your workstation can't connect to the file server, it won't sync. You probably shouldn't be providing file sharing access over the internet. Use your firewall to restrict external access.

  • 10.4.x and Active Directory Logins - mobile accounts

    Managing 10.4.x workstations and trying to get AD logins to work using OS X AD plugin set to "create mobile home" and "Force local home directory".
    AD user accounts get stuck at the login window. The user name and password field are greyed out and the computer sits like that for a long time. Computer responds when pressing the power button to restart, shutdown, sleep, or cancel.
    Console reads: automount 174: can't mount server name .... invalid argument (22) over and over
    tried setting automount in /etc/hostconfig to NO and that just keeps returning the "unable to login as user .... afp/smb error"
    If the AD plug in is cofigured with out the "create mobile home" and "force local home directory" checked, the AD user can log in with a true network home directory.
    Seems like the login doesn't work when it's set to create a mobile home and mount the users network folder in the dock.
    Clients are Mac 10.4.9 + / WIndows/Active Directory 2003 / OS 10.4 server for management purposes.
    any ideas?

    my apologies.... posted this question in the wrong forum. will repost.

Maybe you are looking for