G
Guest
I've got a repeatable issue with XP (SP1) Unattend.txt install. Here's what
happens:
1. WinPE PXE boots, formats the drives, kick off unattend.txt.
2. Unattend.txt puts XP SP1 onto the box, then runs the guirunonce bit to
install 70MB or so of hotfixes, SMS SP1, and Novell client.
3. After bootup, SMS then starts installing applications.
Somewhere in this process, HKU\(currently-logged-in-SID)_CLASSES\ key
develops a problem - users have no rights to that key. The net effect is
that normal users cannot change file associations. If I go to permissions on
that key, administrators, restricted, and system have normal rights, and
there's a long SID in there (S-1-5-21-299502267-84292546-725345534-1007) that
doesn't resolve to a name.
If I remotely connect to the machine as an admin with regedt32, *ensure the
problematic user is logged in* and change permissions for that key (say, add
machinename\USERS full rights) then everything is fine, and that *one user*
can then change file associations at will - including now and after a reboot.
However, any other users that log into the box will have the same problem -
they can't change file assocations until I perform the above fix.
This is repeatable on 100% of the various computer types around.
So, two desired solutions here:
1. How can I find out where in my imaging process this is happening? If I
remove the GUIRUNONCE bit so no (hotfix|sms|novell) files install, the
problem doesn't happen, but if I then (immediately after that first reboot)
manually kick off the guirunonce script, the problem *still* doesn't happen,
so it seems like it's either a contention issue or something else.
2. If I can't stop it from happening during the build, how do I fix it
(allow all users to change file associations)? My current fix only fixes
that ONE currently logged in user on that ONE box he's logged into. I'm
content with a per-machine solution, but I'm hoping for a fix for all users
on a given machine, rather than just one as my current fix allows.
Any ideas on this one?
happens:
1. WinPE PXE boots, formats the drives, kick off unattend.txt.
2. Unattend.txt puts XP SP1 onto the box, then runs the guirunonce bit to
install 70MB or so of hotfixes, SMS SP1, and Novell client.
3. After bootup, SMS then starts installing applications.
Somewhere in this process, HKU\(currently-logged-in-SID)_CLASSES\ key
develops a problem - users have no rights to that key. The net effect is
that normal users cannot change file associations. If I go to permissions on
that key, administrators, restricted, and system have normal rights, and
there's a long SID in there (S-1-5-21-299502267-84292546-725345534-1007) that
doesn't resolve to a name.
If I remotely connect to the machine as an admin with regedt32, *ensure the
problematic user is logged in* and change permissions for that key (say, add
machinename\USERS full rights) then everything is fine, and that *one user*
can then change file associations at will - including now and after a reboot.
However, any other users that log into the box will have the same problem -
they can't change file assocations until I perform the above fix.
This is repeatable on 100% of the various computer types around.
So, two desired solutions here:
1. How can I find out where in my imaging process this is happening? If I
remove the GUIRUNONCE bit so no (hotfix|sms|novell) files install, the
problem doesn't happen, but if I then (immediately after that first reboot)
manually kick off the guirunonce script, the problem *still* doesn't happen,
so it seems like it's either a contention issue or something else.
2. If I can't stop it from happening during the build, how do I fix it
(allow all users to change file associations)? My current fix only fixes
that ONE currently logged in user on that ONE box he's logged into. I'm
content with a per-machine solution, but I'm hoping for a fix for all users
on a given machine, rather than just one as my current fix allows.
Any ideas on this one?