Jump to content

Raja

Member
  • Posts

    37
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Australia

Posts posted by Raja

  1. 1. Create a .reg file with following and save it as C:\RunOnceEx.reg

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\0001]
    "RunOnceEx"="Notepad.exe"

    2. Create following String Value entry under RunOnce key:

    ValueName = RunOnceEx and its value as Regedit /s C:\RunOnceEx.reg

    OR Alternatively to achieve the same create another .reg file as below and run it by double clicking on it.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce]
    "RunOnceEx"="Regedit /s C:\\RunOnceEx.reg"

    The RunOnce reg entry when executed, after all RunOnceEx entries are executed(if any), will create entry to run Notepad in RunOnceEx and will not be initiated till next logon or reboot. At the next logon/reboot, RunOnceEx entries will be enumerated and as a result Notepad will fire up.

  2. Hi

    U will have to overwrite the existing Default User profile with Domain Admins profile with xcopy.exe. You must be logged on as administrator to do so.

    Option 1:

    1. Enable auto logon to log on domain admin.

    Note: Password is exposed in the registry till auto logon is disabled

    2. Log of and auto logon as local admin.

    3. Use Xcopy.exe from RunOnce to copy the domain admin profile to default user profile.

    4. Disable auto logon and then Log Off.

    Option 2:

    1. have a pre configured domain admin profile folder as part of your build.

    2. At the first logon, use Xcopy.exe from RunOnce to copy the domain admin profile to default user profile

  3. The following will set a variable strCDROM to the CDROM drive letter in a vbscript.

    Modify to suit your need.

    Set objDrives = CreateObject("Scripting.FileSystemObject").Drives
    For Each Drive In objDrives
    If Drive.DriveType = "4" Then strCDROM = Drive.DriveLetter & ":"
    Next

    Also does anyone know in VB if there is away to put a application switch in, so if the user puts /1 it will think that there is only 1 CD to install

    Provide more details on what you are trying to accomplish, may be able to help you.

  4. Dennise

    I will try again to share my thought on the subject. With what I am suggesting you will have one master image only and no sysprep image. The solution involves a bit of scripting.

    1. Have a computer build the way you want it to be.

    2. Add the driver folders as discussed previously.

    3. Enable the auto logon and have a script executed through RunOnce key

    4. Shutdown the computer and take the image of it.

    5. This image become your master image.

    What will your script have?

    1. Ability to auto detect the model and use that information to get the right drivers copied to C:\Drivers. (As discussed in the first reply). If you do not want to put the effort in working on the auto detect code then you can get the script to prompt you for the model name.

    2. Execute Sysprep.exe with reboot option.

    What will you see on ghosting the image on new PC?

    1. On powering ON the PC, auto logon is executed followed by running of the script from RunOnce key.

    2. PC restarts again as a result of sysprep command from the script.

    3. On restart Mini setup wizard starts as per settings in Sysprep.inf.

    Note: The sysprep.inf and cmdlines.txt could be customised for each model on the fly by the above discussed script.

    4. PC reboots ready for user logon.

    The concerns...

    1. You need to have some knowledge on scripting(plenty of help available in forums and newsgroups)

    2. At the first auto logon you will be seeing New Hardware Found wizard popping up, but is not a worry as Sysprep.exe will kick in soon enough and restart the PC.

    I hope this all makes some sense so that you can benefit from this. If still not clear, ask me specific questions so that I can help further.

    Cheers

    Raja

  5. Hi Dennise

    This will work for "one image for all" solution. Could you point out where do you see this failing in your scheme of things so that I can assist you further. If I am guessing it right you are using ghost to dump the image after you have done the Sysprep. If true, then prepare your master image before the sysprep and integrate the above suggestion into your solution. I am hoping that you can take it on from here, otherwise feel free to write to me directly (rkohli@energy.com.au) and will provide you the detailed steps to accomplish what you want. Unless I am missing something, what you want is how I do my images so am confident of it working for your needs.

    Hope to hear soon from you.

    Cheers

    Raja

  6. Hi Dennis

    Try this;

    Create unique driver folders for each hardware model with a common prefix and have all the folders available as part of the image in the root of C: drive. Copy all the driver files for each device (audio, video, network..etc) of each model to the root of each driver folder for that model.

    Example:

    D_e3400 - Copy all device drivers for e3400 to the root of this folder

    D_T22 - Copy all device drivers for T22 to the root of this folder

    D_8183 - Copy all device drivers for 8183 to the root of this folder

    Have oempnpdriverspath set to C:\Drivers

    Edit (create if you do not have one) the batch file which runs the sysprep.exe to add these line before the sysprep is executed.

    Move C:\D_%1 C:\Drivers

    For /F "Tokens=*" %%A IN ('Dir /B /AD /S C:\D_*') DO RD /S /Q %%A

    Call the batch file with the hardware model as the argument so as to replace the value of %1 with that models driver folder.

    Example:

    If your batch file is called ABC.bat then run it as ABC.bat T22 for T22 model.

    The batch file will first rename the C:\D_T22 folder to C:\Drivers folder and then delete all the other folders starting with D_ in the root of the C: drive.

    Also do you realise that having installed all your apps on a FAT32 partition and then converting it to NTFS you have missed the opportunity to benefit from the default security settings these apps would have applied during their installation had the NTFS be available at the time of installation.

    Regards

    Raja

×
×
  • Create New...