Mounting of Windows home folders: When someone logs in to a Mac using an Active Directory user account, the Active Directory connector can mount the Windows network home folder specified in the Active Directory user account as the user’s home folder. See Control authentication from all domains in the Active Directory forest. Alternatively, you can permit only specific domains to be authenticated on the client. If a domain controller becomes unavailable, the connector uses another nearby domain controller.ĭiscovery of all domains in an Active Directory forest: You can configure the connector to permit users from any domain in the forest to authenticate on a Mac computer. See Map the group ID, Primary GID, and UID to an Active Directory attribute.Īctive Directory replication and failover: The Active Directory connector discovers multiple domain controllers and determines the closest one. The generated user ID and primary group ID are the same for each user account, even if the account is used to log in to different Mac computers. The packet encryption and packet signing options ensure all data to and from the Active Directory domain for record lookups is protected.ĭynamic generation of unique IDs: The controller generates a unique user ID and a primary group ID based on the user account’s globally unique ID (GUID) in the Active Directory domain. Packet encryption and packet-signing options for all Windows Active Directory domains: This functionality is on by default as “allow.” You can change the default setting to disabled or required by using the dsconfigad command. In addition to supporting authentication policies, the Active Directory connector also supports the following: Therefore, it might be necessary to change the ACL of those attributes to permit computer groups to read these added attributes. It seems to work aside from the sync conflict message, so thats the main thing I guess.Tip: Mac clients assume full read access to attributes that are added to the directory. Just wanted to check that I had followed your advice correctly. Maybe its just a result of the way the iDisk has to be set up to make the syncing work. Is there any reason for getting the iDisk Sync conflicts message? "MobileMe", then the documents weren't synced, (when I downloaded the document from my MobileMe site, it wasnt updated) When I tried it the other way round, i.e. If I select the "This Computer" option then everything is synced. Which file do I want to keep - "This Computer" or "MobileMe". The only thing I have noticed is that after the syncing I get a "Sync Conflict" messages I then open/save/edit from the iDisk>Documents and all is synched! the ones I dragged from the HD in the first place) I then deleted the alias folders from my iDisk>Documents. I dropped those new alias folders into my HD>Documents folder, and deleted the original folders that were in there, so as only to have the alias folders in this location. I dropped the Folders from my HD>Documents folder into my iDisk>Documents folder. I think I carried out your instructions correctly. cat $LOG | mail -s "Output of rsync to iDisk" the more advanced, a simple update to the script that would check for access to the internet could be used to only do the rsync if internet access is currently available. I chose every two hours.įor those who want a little closure, adding the following to the end of the script would email a copy of the log file to yourself, assuming you have a local mail server running. In the "What" section, enter the path to the script (ie: Macintosh HD/Users/MyName/scripts/rsync_idisk.sh), then set a time to run every so often. Download and install Lingon, then open a new item. Lingon allows you to schedule jobs to run at specific/recurring times via launchd (like cron on most other *nix systems). The joy of rsync is that after the first (long) run, future iterations only sync over what's changed. While this works well, it's still a manual process. Item x of x" in the bottom of the Finder window. Additionally, opening up Finder and drilling in on the Documents folder under your iDisk will show "Syncing iDisk. If you like, open another console and do a tail -f log_name and watch the files sync in real time. (iDisk seems to only be giving up about 50Kbps these days, whereas it used to be 250Kbps or better). #!/bin/sh# Sync all data from Documents dir (except Virtual Machines) to MobileMe iDiskexport LOG=/Volumes/"Macintosh HD"/Users/MyName/idisk.logecho `date` > $LOGecho "Starting copy of Documents to iDisk." > $LOGrsync -a -E -4 -u -exclude=.DS_Store -exclude=.TemporaryItems -exclude=.VolumeIcon.icns -exclude=tmp -exclude="Virtual Machines" -exclude="Virtual Machines.localized" -stats -progress /Volumes/"Macintosh HD"/Users/MyName/Documents/ /Volumes/iDisk/Documents/ > $LOGecho "Backup of Documents to iDisk complete." > $LOGecho "" > $LOGecho `date` > $LOGexit 0With the script saved and executable, simply run it with.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |