Using a customised "default user" within RIS?

[finkster]

This is the issue -

I want to prepopulate the default "default user" key for RIS based images so that its in the "build" so to speak.

Has anyone got any idea of how to prepopulate the system default (NT USER.dat) without messing about with reg keys.

The process is easy enough in windows but I need to automate this so when the "user" logs on first time and creates their local profile (default user) settings are applied and help create the required look and feel....

Ideally I would like to place files in the RIS Image.

Any ideas?

thanks

[InTheWayBoy]

You could try configuring and backing up the NTUSER.DAT file, and then using the $OEM$ folders to copy it over. I don't know if this really works, but I've seen it mentioned here before. Basically you would put NTUSER.DAT here:

X:\$OEM$\$Docs\Default User\

Then, when the $OEM$ files are copied over your custom NTUSER.DAT should be in place, allowing every new user to user your tweaks.

Hope this works...good luck!

[RogueSpear]

Are you using roaming or non-roaming profiles? I used to use roaming profiles (decided they were way more trouble than was worth the effort). It can be done either way. I use scripting to copy down the ntuser.dat file.

[InTheWayBoy]

Hey RougeSpear...does my process sound correct? Assuming it's not attatched to a domain it should work, right? More of me just wanting to know I'm not talking out my *ss than anything...also, what kinda script are you using? Any chance of seeing the source? As a new net admin I'm trying to learn as much as I can, so I'd love to see how you do it...sounds like you know a hell of a lot more than most of us

And don't forget to PM me about the RIS site...if you're still interested.

[finkster]

Guys (and Gals ?)

OK bit more info

Thanks for your replies so far...

Additional info in response to above:

I'm in a domain (can you run RIS out of a domain?) and am attaching to domain at the stage where I am looking to prepoulate the Default User - this is largely created as a result of the NTUSER.DAT and the profiles held in All Users and "Default User" I attach to bring certain apps and other things down such as domain GPO's. I dont want (for various reasons....) to rely on GP to force profiles...

To confuse issues further there are both roaming and local profiles in operation - part of the reason why I'm not forcing via GPO and also why I want to prepoulate a (local) user profile from default user....

Solution i have so far is to copy preconfig settings from a user profile -> network share (keeping attribs on all files...worth checking msdn kb for this) and then using robocopy

will probably shell out to robocopy at the cmdow stage - post ?Mini setup / run once reboot...

this then gives me a customised default user profile for anyone who is loggin onto machine that doent have roaming profile

anyone got any other suggestions

or ideas on how best to use robocopy as some files have time date issues...

thoughts or comments ?

cheers

Finkster

[finkster]

re $oem$ docs$

I think this may not work because it doesnt preserve security and file attribs...

on all files copied across in a "profile" not sure if this works on just a nt user.dat file....

finkster