+31Do you have OD as well as AD? If you, you can create a share point in OD and map it that way. I also believe you can map the home folders with the AD plug in on the AD side as well, but I don't have AD to test this with.
As for the scripts, just modify them to the new location of the home folder, or have a log in hook that when a user firsts logs in, it creates a symbolic link form /Users/Username to where ever the new home folder lives.
+21I don’t think the issue has anything to do with mapping the home folders, it just works if they have a Home Folder specified on the profile tab of an AD account. We’ve been using it forever. I find it interesting that Snow Leopard is helping make this transition.
Perhaps some clarification on what you want these scripts to interact with.
Do you want these maintenance self service items to just be performed on the person who is logged in?
OR
Do you want these maintenance items, when run, to parse through all local profiles and do these tasks to all of them?
Craig E
+8For example, we currently have a Self Service policy that removes the Adobe
InDesign CS3 cache folder (~/Library/Caches/Adobe InDesign/). An end user
would sign into Self Service and click on a policy named 'Flush InDesign
Cache' which would trigger a simple remove script (rm -R
/Users/personal/Library/Caches/Adobe InDesign).
Post AD bind, I'd want the Self Service script to only run on the logged in
user. I don't know if it helps, but our JSS server is already bound into AD
and end users use their AD credentials to sign into Self Service (I've been
wondering if that's something that can be supported with single sign-on).
Robb
+21All you need is a script that pulls out the currently logged in username and places it in your command. If someone hasn’t gotten that to you before I get back to my desk (I’m sure Tom will) I’ll have something tonight. If it were a login item it would be even easier. =)
Craig E
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.