next »

[mikerick]

Hi there,
i have a problem, which i want to share with you :-) In an Active-Directory Domain Environment we have Machine-Startup-Scripts for executing Stuff at machine level. For example we activate hibernation-mode for our Notebook-OU with 'powercfg -h on'. We also want to manipulate some Registry Keys using 'Active Setup'. This is a mechanism, which enables windows to put reg-keys into HKCU, when a user logs on the first time on a machine. You see all that when you log on a computer in a domain, which never logged on that system, like 'Internet-Explorer Settings etc.'. We are talking about windows xp, btw. :-)
However, all runs fine when we set windows-shell. As soon as Res-shell is set, active setup is not being run.
We only have res-powerfuse, i tried with external commands, but this does not work either
Any help would be great
Regards
Michael

[pkaak]

I always thought that this IS done by powerfuse. Only PF names this 'setting workspace for first run...'. Althought not all settings are done at that moment.

What Windows does is mainly setting registry keys at that point, as the new profile is already created from the default profile. It can also execute some task if RunOnceEx keys are created in HKCU.

I mostly use it mixed (powerfuse and Windows default Profile). I make a new Default User template (running the login for the first time without powerfuse, doing some settings like setting the default explorer view to detailed and after that copying that profile to the default user profile. That profile is captured in the image or copied to every workstation by Wisdom. Everytime a new user is logging in with no roaming (or local if you do not use roaming) profile, Windows makes a new profile by using the information in the Default User profile.

Second task is to set the rest of the registrykeys Windows makes just by using Powerlaunch user registry and set them to Run Once.

If you use RunOnceEx to set some extra tasks, you should use External Taks for them and set them too to Run Once.