Some troubles with unattended installation

Discussion in 'Windows Desktop Systems' started by Punkrulz, Mar 26, 2004.

  1. Punkrulz

    Punkrulz Somewhat eXPerienced

    Messages:
    790
    Location:
    Woodbury, NJ
    Hey guys,

    Hoping you all can help me, you were a big help when I first started this. I'm sure you all know that msfn has changed their design, so it's not the most easy thing to navigate that's out there... oh well. Anyways, I've had some good unattended installs before, but now I'm having some issues. Ever since I decided to add cmdlines.txt to upload a registry group [Black Viper's Gaming Setup for XP Pro], I've gotten some issues. Instead of making a CD, I made a bootable ISO using a program that MSFN specified, so I could test it with VMWare, and I ran into the following issues:

    1) The resolution didn't take from the winnt.sif file.
    2) It made me create a login, instead of forcing me to use Administrator... I don't want to use autologin with Admin, I just want to be able to click it on the user settings and then type in the password.
    3) It didn't import the gaming registry that I had modified it to do.

    Here is the winnt.sif file, located in \I386\.

    Code:
    ;SetupMgrTag
    [Data]
        AutoPartition=0
        MsDosInitiated="0"
        UnattendedInstall="Yes"
    
    [Unattended]
        UnattendMode=FullUnattended
        OemSkipEula=Yes
        OemPreinstall=No
        TargetPath=\WINDOWS
    
    [GuiUnattended]
        AdminPassword=Hidden
        EncryptedAdminPassword=Yes
        OEMSkipRegional=1
        TimeZone=35
        OemSkipWelcome=1
    
    [UserData]
        ProductID=Hidden for purposes
        FullName="Dan Lewis"
        OrgName=""
        ComputerName=desktop
    
    [Display]
        BitsPerPel=32
        Xresolution=1280
        YResolution=1024
        Vrefresh=72
    
    [Identification]
        JoinWorkgroup=WORKGROUP
    
    [Networking]
        InstallDefaultComponents=Yes
    Is it because of OEMPreinstall? That just caught my eye, I'm just curious if that was causing EVERY issue, or just some of them?

    Thanks guys!
     
  2. cpugeniusmv

    cpugeniusmv Computer Genius

    Messages:
    485
    1) that's probably VMWare's fault. try it on a real machine.
    2) I can see from your winnt.sif that you do not have it set to autologin as Administrator...are you creating an account in cmdlines.txt? or do you want to login as administrator?
    3) cmdlines.txt is located in X:\$OEM$\cmdlines.txt right? would you mind posting the contents of that file? (ALSO! set OEMPreinstall to Yes. this may also fix the user problem.