"The home folder...isn't located in the usual place or can't be accessed" after 10.9 AD bind.

Question

Okay a little backstory here because I'm trying to eliminate or identify what I feel might be a bug in OS X Mountain Lion and Mavericks.  Just FYI, I'm not our institution's AD admin, I just have rights to bind and query for this and that, but I can't make changes or really investigate our AD domain server/s:
So we're an educational institution with lots of adjuncts that come and go each year.  Recently in August, I had about 5 cases where these adjuncts couldn't log in because of a cryptic "login failed" error.  I have my macs setup to create mobile accounts without confirmation.  I don't want ANY syncing going on just local user accounts created, but something in the profile creation process demands access to their network home folder.  Well these 5 users were brand spanking new and somehow didn't have permissions to their own network home folders that everyone else hasn't had a problem with before.  I had our admins fix the permissions, and they were able to login thereafter.  Our admins are still looking for what might have caused this, but still don't know....
Recently I've been testing the same AD bind script I've always used on Mavericks.  It's a simple bash "dsconfigad" customized for our institution.  It seems to work successfully but on the login screen I get no usual "arrow" that allows me to back out and click "Other" and login to AD.  I reseated the Ethernet cord and checked the AD configuration in Directory Utility - it was all set correctly as per the script parameters.  When I clicked OK and exited out to the login screen, the Other option was working correctly.  I was able to login with my own credentials just fine.
I needed to tweak my image a little so I wiped and reloaded the machine with the new image (nothing relevant to binding and users was changed).  Got the same "no arrow" issue and tried the same steps, which again worked after some monkeying around.  I tried to login with my credentials - failed.  Now I get "The home folder for user 'my username' isn't located in the usual place or can't be located."  I went into a local user admin account and tried to add my home folder manually, nogo.  I logged onto a windows machine and tried to mount the same home folder in Windows - access denied - this is the SAME type of thing that ended up happening to my adjuncts.  I don't know if they are related but it's certainly a strange coincidence.
How could testing AD binds change my home folder permissions, or possibly even corrupt the folder altogether?  The network share/home folder that our macs smb communicate with as per the bind settings are on a windows server (to the best of my knowledge).  My guess previously with the adjuncts error is that despite the fact that I don't need or want the profiles created to sync, the default options turns this on for mobile accounts even though it doesn't select any actual folders for syncing, but because it still tries some sort of "handshake" or something initially, first logins fail without network home folder permissions.  Now it seems like something in the initial profile creation process might actually be corrupting the network home folder or changing its permissions.
I would post the bind script but I'm not sure it's relevant, as another mac admin in a different area ran into the same error with one of his new users and he bound manually, not with a script.
I'm kind of new to this sysadmin stuff, so does anyone have any ideas or suggestions to track down the cause of this and possibly fix it?  The network share admin can fix my permissions, but if I could break it when it was working once, I foresee this happening again.

Answer 1

Here's the script I used previously that is not connecting to AD "completely" that causes the errors mentioned (I'm replacing institution info with "xxx"):
echo -n "This computer needs to be renamed and bound to Active Directory.  Please enter the XXX Inventory Number from the affixed XXX label on the machine: "
    read userinput
    echo -n "Enter the XXXAdmin password (you will still be asked to enter this for system configuration changes): "
    read -s xxxpassword
    scutil --set ComputerName $userinput
    scutil --set LocalHostName $userinput
# Active Directory Bind Script For OS X Client
    # Modified by Wade Wei according to previous popular bind script
    # Adapted for xxx by xxx
    echo "Binding to Active Directory…"
    echo -n "Enter AD admin username: "
    read adusername
    echo -n "Enter AD admin password (please wait after password submitted, do not press any keys): "
    read -s adpassword
    #Basic parameters
    computerid=$userinput
    fqdn="ad.xxx.edu"
    username=$adusername
    password=$adpassword
    #Advanced parameters
    alldomains="enable"
    localhome="enable"
    protocol="smb"
    mobile="enable"
    mobileconfirm="disable"
    useuncpath="enable"
    user_shell="/bin/bash"
    admingroups="domain admins,enterprise admins,xxx,xxx"
    namespace="domain"
    packetsign="require"
    packetencrypt="require"
    localuser="XXXAdmin"
    localpassword=$xxxpassword
    # Bind to AD
    echo "Binding to AD - do not interrupt…"
    dsconfigad -add $fqdn -username $username -password "$password" -computer $computerid -force -packetencrypt $packetencrypt -localuser $localuser -localpassword $localpassword
    sleep 5
    #Configure advanced options
    echo "Configuring AD for Mac OS X…"
    dsconfigad -localuser $localuser -localpassword $localpassword -alldomains $alldomains -localhome $localhome -groups "$admingroups" -mobile $mobile -mobileconfirm $mobileconfirm -namespace $namespace -packetsign $packetsign -useuncpath $useuncpath -protocol $protocol -shell $user_shell -nopreferred
Can anyone tell me if I need to update the script for Mavericks, and how?  Or should this be working and the bug is in Mavericks itself?