Just an update - after working with Brad for a few days and providing him with a customized version of ULS with enhanced debugging data, we found that these two computers indeed had an invalid environment.
When logging in, the NET USE command always returned "Error 10 - The environment is invalid". Adding a "SET > UserEnv.txt" command to the login script showed that there were no variables defined in the environment (the file was empty!) - neither System or User environment variables were present. It was almost as if the registry was unavailable to initialize the environment. It didn't matter if the workstation was recently rebooted or had been on for a while - it happened consistently at login.
After the login completed and a command prompt was opened, the SET command displayed the environment and NET USE commands ran successfully.
The problem presented with any user as well as a new user profile. We checked network settings, (LM)Host file entries, verified that the system was not in a strange return from hibernate state, and a few other things such as verifying that the related login script files were saved in ANSI format and removing the cached copy of the config file. Google searches turned up nothing useful beyond dozens of sites with tables of error messages.
Since this issue was confined to just two of 100+ workstations, they were replaced and the problematic systems are scheduled for reimaging.
With this additional insight, I'm just wondering if anyone has any ideas as to why the environment would be blank during logon, yet operational moments later?
Glenn
_________________________
Actually I
am a Rocket Scientist!
