R. Saeks July ’06 - 13 -
The setup currently in place is based on offering a more efficient and streamlined system, as well as a setup that is
consistent, to the users. We have 3 types of users in place right now. Those are student, staff, and administrators.
These general groups control what on the machine can be accessed, such as System Preferences and Applications.
On each machine there is a local account called studentuser. This was done as it was found to be more efficient
running the student account locally rather than from their Network-based home directory. This is accomplished by
creating a local account as normal on the machine called studentuser. The account was then setup with the proper
desktop icons, safari settings, and other miscellaneous preferences that don’t need to be set dynamically based on
machine location. It was also tested with students to make sure nothing was overlooked. Once ready, the apple-
user-homeurl attribute was removed from the user record, as well as the homeDirectory path, shown on page 6,
changed to /Users/studentuser.
Once the account was setup as it needed, the studentuser folder was copied to /Library/Management/profiles/. In
doing this, a pristine copy of the profile is retained. The copy was done with the root user account so file
permissions were not an issue. When using this, remember that any changes needing to be made will need to be
made with the studentuser account logged in, making the necessary changes, then copying the profile back into the
profiles directory mentioned above.
Once all the static tasks were done with the user account, dynamic tasks were set with various AppleScripts. The
AppleScripts used at login are structured in such a way that specific actions are performed which change depending
on who is logged in. One builds desktop icons for faculty, and a similar one does the same for students.
The scripts that are utilized for Faculty and Staff generate desktop shortcuts for an applications folder, Network user
folder, Network Drop Box, and the common files on the network for all faculty. Similarly to this, the student script
generates a user folder shortcut and the Network Drop Box to teacher folders. The application folder for students
resides in the profile Desktop folder, and that is re-generated at login for them. This is accomplished based on the
login hook shown page fifteen.
In addition to desktop icons, there is also an AppleScript application that checks for expired Novell passwords. There
was a need for this as a 3rd Party directory service was utilized and a built in method to notify users their password
expired was absent. Using the functionality from the Novell Client on the Windows machines as an example, we
wanted to use the number of days to notify the user rather than the number of grace logins remaining. A custom
display message box was created for them, which included an option to change their password. If the user clicks on
yes to change their password, they are redirected to the password self-service portion of iManager. This was used
since there is no built in way for OS X to change their Novell user password. Furthermore, once the password had
Commentaires sur ces manuels