G
Guest
Hi All,
Have setup a RIS server on Win 2K3 SP1 and which successfully deploys XP Pro
SP2. Now looking at "nice to have" things to configure but RIS seems to have
a method of selectively undoing my tweaks.
1. Have added certain scripts to the "Default User" RunOnce hive (to
configure Outlook, printers and things). When the image is pulled down from
the server to a client this configuration is missing. The keys configured
aren't in the "HKCU" hive or in the "Default User" ntuser.dat file.
2. Similar to the above, have fiddled with the boot.ini file to change the
"OS Selection" timeout and DEP policy settings but it gives me a default
boot.ini file when the image is pulled down.
3. Finally, place "Favourites" under the "Default Profile". These don't get
pulled into the Default profile at all ... let alone put into any new
profiles.
Have thought about sticking the default profile under Netlogon but I don't
think this this is really an option with the fact that we have so many
different configurations on client machines (applications, hardware, etc).
Image is riprep as opposed to CD-based. When the image is RiPreped upto the
server I can load the registry dat files and look at the boot.ini file and
all looks as I configured. Can someone point me in the right direction to
sort this out ? Or better, has anyone come across this before and found any
work arounds ?
Thanks for any help,
Mark
Have setup a RIS server on Win 2K3 SP1 and which successfully deploys XP Pro
SP2. Now looking at "nice to have" things to configure but RIS seems to have
a method of selectively undoing my tweaks.
1. Have added certain scripts to the "Default User" RunOnce hive (to
configure Outlook, printers and things). When the image is pulled down from
the server to a client this configuration is missing. The keys configured
aren't in the "HKCU" hive or in the "Default User" ntuser.dat file.
2. Similar to the above, have fiddled with the boot.ini file to change the
"OS Selection" timeout and DEP policy settings but it gives me a default
boot.ini file when the image is pulled down.
3. Finally, place "Favourites" under the "Default Profile". These don't get
pulled into the Default profile at all ... let alone put into any new
profiles.
Have thought about sticking the default profile under Netlogon but I don't
think this this is really an option with the fact that we have so many
different configurations on client machines (applications, hardware, etc).
Image is riprep as opposed to CD-based. When the image is RiPreped upto the
server I can load the registry dat files and look at the boot.ini file and
all looks as I configured. Can someone point me in the right direction to
sort this out ? Or better, has anyone come across this before and found any
work arounds ?
Thanks for any help,
Mark