finkster

Guys, Just a quick pint HKCU is a virtual reg hive - it is a user but not a user..if you see what I mean - programatically its a nightmare as current (logged on ) user can change - if you want to affect all user or default user (profiles) then these are better areas to target... i think I'm talking the same thing here http://www.msfn.org/board/index.php?showtopic=56584&hl=#

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

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

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

Yep I use a UK keyboard and had this issue - UK keyboard characters in login so my ris account password not accepted...its in the welcome and login osc files...you can display the text in the CIW screens after the initial welcome i gather..loading a mulitlingual =osc extension...but I think you may mean the keyboard... I think its a code page setting,? Maybe its a hack in the oscml files/tags -... dunno if this helps at all FinKster

Just a thought - if you have AD just set most of this stuff in GPO - you can configure more or less everthing here - lots of resources from MS... If you dont have this ...then you'll need to run some clean up scripts, which as you say will require reg entries and some wsh/vbs I guess..... I have similar stuff to do but I dont have to worry too much about the "build" after it joins the domain as policies are applied - I'll post my clean up when I write it.. FiNkSter

Apologies guys - got an ISA error and didnt realise that I had infact double posted.. Please delete / clode this second post... FinkSter

1ST Post - have searched but still have Q. Wonder if anyone can help - Background: Setup RIS on 2003 member server in single Domain - all working well. Getting DHCP addresses from sep DHCP server - config options on DHCP to provide routers bootfile/server addr to RIS clients. Able to deploy and can deploy RIS images (flat) to laptops and desktops. Slipstreamed XPsp2 into i386 source, created $OEM$ DIR structures, and placing drivers in $1 folders etc - calling PnP drivers path in sif file, and using excellent cmdlines runonceex unattended install methods gleaned from here and other linked sites. Happy with process, linking fully automated build to infrastructure (client has SMS2003 so software is fully deployable in terms of applications...) Hardware scope all DELL desktops GX240/260/270/280s maybe other models but all DELL. What I would like to do is this: 1. Use RIS f12 option to Boot Desktop PCs - but initially interogate BIOS and if downlevel flash to agreed level then deploy image. 2. use 1 image for all dell desktops? (Im not using riprep so its not platform specific.) 3. Customise OSC files in RIS to accept predefined user ac and password so that on the welcome.osc all the tech/engineer/user has to do is press enter which takes to next osc (which is login.osc) which really is choice options and this would prompt for machine name/build image ie type. I understand that the min number of osc file = 2...has anyone acheived this? Wondered what any thought might be... Thanks in advance... Finkster