Do you really need to know if it’s a network account, or do you just need to know where the home directory is?

Here’s how I detect local accounts in a login hook:

#!/bin/sh
USERNAME=$1
LOCALACCT=`/usr/bin/dscl . read /Users/$USERNAME 2>/dev/null`
if [ “$LOCALACCT” != “” ]; then
# $USERNAME is a local account
else
# $USERNAME is a network account
fi

and here’s how I get the home dir (no matter the account type) in a login hook:

#!/bin/csh
set homedir=~$1

Note that I used /bin/csh in the second example. /bin/sh won’t do the same thing.

There are other ways to do these.

By default all local accounts have a UID of 500 to 999 and all open directory accounts, be portable or network have a UID of 1000 or greater. You can maybe do it by UID I think.

Another method is if you do an authenticated bind you can set computer group policy to apply MCX to local user accounts via WGM and don’t even have to script anything out.

[QUOTE][u]Quote by: tlarkin[/u][p]By default all local accounts have a UID of 500 to 999 and all open directory accounts, be portable or network have a UID of 1000 or greater. You can maybe do it by UID I think[/p][/QUOTE]

While that’s the current behavior of OS X and Open Directory, I wouldn’t rely on it. And if you are using any directory service other than Apple’s Open Directory it’s unlikely to follow Apple’s conventions as far as UIDs.

-Greg