Posted on 09-18-2013 09:26 PM
Happy September...
on the tail of my wireless authentication woes, another problem came up. I have machines that were imaged in 2 weeks ago, that tecahers used. fine. Now it seems each machine will not let one and only one user not login ( different user on each machine) we use AD. the user home folder is there with correct ownership rights. logs show the user as an 'unknown' user. changing the password/deleting, adding the account does not work.the only thing that does seem to work for now is a nuke and pave. I do see the user with an updated USN number in AD. again it is just one particular user, which makes it frustrating.I just get the shaking grey screen. any ideas/
OS: 10.8.4
Bound to AD
Solved! Go to Solution.
Posted on 10-02-2013 09:19 AM
Thanks to all finally got it solved. it was an issue with a defunct DNS server used during a migration process and mobile accounts being created.Our network does not like mobile accounts
cheers
LS
Posted on 09-18-2013 09:54 PM
I had a similar issue with SL, try removing the users home folder in AD and then try logging on and see if that helps and let us know.
Posted on 09-19-2013 04:41 AM
How are you binding? We used Quest for years and if the account sat with inactivity for too long they would freeze out the user.
Posted on 10-02-2013 09:19 AM
Thanks to all finally got it solved. it was an issue with a defunct DNS server used during a migration process and mobile accounts being created.Our network does not like mobile accounts
cheers
LS