Completely stumped with a 2003 profiles problem
Here's a noodlescratcher for you all.
I've recently inherited a system that, at best,, is in need of a little TLC. It seems the previous NM had a hatred of not only his job, but also children and teachers, so inflicted his hatred by letting the place fall dow around his head. Luckily, he's now gone, but my technician and I have been left to pick up the pieces.
Anyway, woe is me story over, I just can't get my head around this problem we're having when creating new user accounts manually in AD. As the year progresses, we get new students popping up from other sixth forms whom require accounts set up. So far so good, however, recently new accounts have been set up, yet the correct local profile fails to load on login. We copy the accounts over from existing sixth form accounts, set them to prompt to change password on first login, and bam, no profile is loaded. There is usually nothing in the event logs, and i've checked various permissions of local and network profile folders which seem OK.
The next weird thing is, if we set up the accounts NOT to prompt to change password on first login, they load up fine - profile and all. I just can't see the link between creating the profile on first login, and prompting to change password on first login, and why the latter seems to be interfering.
We're still Server 2003, and I'd be the first to admit our setup is far from ideal. It's not a problem in GP as all new accounts should be sharing the same policy settings as existing ones.
Maybe someone has had this issue before, or can offer any wisdom?