Is everyone here experiencing the problem on a domain? I am having this
problem with our Lenovo T6x line of laptops when they are joined to the
domain. Myself and some other engineers have traced this issue to being
with the Scripts that go off at startup (or at least that's our best
guess at this point). I am curious if everyone else is experiencing the
problem on the domain because I've done some severe testing and found
that before the machine is profiled to the domain, the issue NEVER
happens. I did over 300 reboots of my T61 with a fresh image, with all
updates, hotfixes, and drivers, and never once had the "explorer.exe
not loading" issue happen. As soon as I joined it to the domain, the
issue happened within 5 reboots, and then every ten or so reboots after
that. The fact that it doesn't happen until it was joined to the domain
was why I never saw the issue when I was building the image and didn't
realize it was a problem.
As part of my testing, I turned off all startup items and all drivers.
However the problem still happened. I tried joining the default Lenovo
image to the domain, and the problem also happened.
Then I checked the startup procedures using Autoruns from
systinternals. Explorer.exe (the shell) loads with the rest of the
startup procedures. The only item that happens before this is execution
of .vbs scripts passed down from Group Policy on the domain. I had the
engineers take me out of my usual group on the domain and put me into a
special group that does not have any scripts that run. I re-profiled
with those group policies and BAM - the problem DISAPPEARED.
I asked to be put back into a group with scripts and once agian, within
ten reboots, the problem appeared.
Thus I feel that this has something to do with a script problem on our
domain, I wonder if everyone else's experience is similar. This issue
is a major headache for our users and I've been trying to solve it for
weeks. However I can't find any logged errors of scripts not running or
anything else so I am stumped as to where the problem is occurring. I
know that it doesn't happen when scripts aren't run, but I don't know
what's wrong with our scripts. Our scripts do the same thing as listed
in the first couple posts, they map network drives.
I don't know if this information helps or complicates anything...
ppohio's Profile: http://forums.techarena.in/member.php?userid=35202
View this thread: http://forums.techarena.in/showthread.php?t=694888