Jump to content

thammerling

Member
  • Posts

    26
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by thammerling

  1. wow... our lenovo rep is a spaz... and i'm not much better. I hate the **** machines. turns out it wasn't a m52 at all, but an m55e, they shipped us the wrong machine :P and because these lenovo's have such screwy model naming conventions i had no clue it wasn't an m52. oh well, we had an older image for the m55e, so i just used that and washed my hands of it (we only have _1_ m52 in our district... i'm not wasting my time on this anymore specially because we switched vendors to dell).

    thanks for your help :)

  2. Alrighty, I have a sysprep image which works on many many many different models of PCs. from a p3 650Mhz machine to a brand spanking new dell amd 64 bit system. It will install and run on 9 different models so far. the problem is with some IBM lenovo computers. When i lay the image down on one of these Lenovo's (they happen to be IBM M52's) the image is put on properly, and upon restart I get the windows "splash screen" that is shown just before mini-setup starts, and then the computer reboots before going into mini-setup. and it will just keep looping like that.

    I'm kind of baffled, because this image has worked very well on so many different machines.

    any help is greatly appreciated.

    Taylor

  3. ok, I have tested these settings out on a machine that had already been imaged, and I got it working. However, once i changed the registry in the image, and pushed the image out to a machine it did not work. I then compared the settings in the registry on the newly imaged machine to what should have been there, and found that the AutoAdminLogon in the winlogon key was missing.

    I think this has something to do with the fact that this image is a sysprep image. I think somewhere in mini-setup the AutoAdminLogon is being removed... not 100% sure on that, but i think. I'll keep this thread updated with my progress.

    T

  4. I'm not 100% sure. I've been a windows guy for the past 6 years, and am just getting into novell, so please bear with me. I would like the computer to autologin as if the "workstation only" box was checked using the local administrator account. I believe that this is the same as "Auto login to NT and disable login to NDS", but I don't want to disable login to NDS permanently, just for the first autologin. another side note, we don't have an active directory domain at all, I would be authenticating against the local box.

    I will read the documentation (although i'm pretty sure it is what I have already tried... I must just be doing something wrong...)

    Taylor

  5. First let me start off by giving you all a little background on what my situation is.

    I am working on making a sysprepped Master Image for my employer. The computers are all XP sp2, and are using the Novell Client for Windows 4.91 SP2. It is working 99.99%, the only problem being I cannot get Autologin to work at all.

    I would like the computer to autologin as the LOCAL administrator. I have tried many many many different things, and have had no success at all :(

    any help would be greatly appreciated.

    Taylor

  6. hrm... I have that deploy cab, and when i look in ref.chm I find this

    To run Cmdlines.txt during Mini-Setup

    In the distribution folder, create:

    %SYSTEMDRIVE%\Sysprep\i386\$OEM$

    Copy Cmdlines.txt to the %SYSTEMDRIVE%\Sysprep\i386\$OEM$ folder.

    In Sysprep.inf, add:

    [unattended]

    InstallFilesPath = C:\Sysprep\i386

    Run Sysprep.

    Either way, I have tried it with the cmdlines.txt in both $oem$'s and at the root of the sysprep folder, and none have worked.

    I'm stumped!

    I found this how-to, and it seems like i'm doing everything right... i'm boggled!

    http://www.geocities.com/kilian0072002/sysprep/sysprep.html

    :(

  7. Hi everyone, i'm having a dickens of a time getting cmdlines.txt to work.

    Let me start by saying that I am working on a master image for the school district I work for. We run novell servers, so we use zenimg to create and push down images. I made a nice clean image, and sysprep -resealed it. I then used zenimg to push the image up to our storage server. I then realized that I would want to use cmdlines.txt to do some stuff. I used the zenworks image explorer to add the cmdlines.txt file and to update the sysprep.inf with the appropriate InstallFilesPath. Everything looks ok to me, but it isn't working at all (it doesnt even appear to be touching the cmdlines.txt!)

    Please see the attached pic for a rundown of the file structure... Notice the two $oem$ folders. I had read conflicting reports of where your $oem$ folder should be, so i made two of them, both containing the same files.

    My cmdlines.txt is as follows

    [COMMANDS]

    "DriverInstall.bat"

    DriverInstall.bat is located at the root of both $oem$ folders and contains the following

    echo "omg! we are in cmdlines.txt - The one located at *the path it's at*!!!"

    c:\windows\system32\cscript.exe c:\sysprep\DriverInstalls.vbs

    pause

    and then the DriverInstalls.vbs is just a vbs file to do some junk, not really important since I never even hit my cmdlines.txt.

    oh, and my sysprep.inf is as follows

    ;SetupMgrTag

    [unattended]

    OemSkipEula=Yes

    InstallFilesPath=C:\sysprep\i386

    UpdateInstalledDrivers=1

    DriverSigningPolicy=Ignore

    TargetPath=\WINDOWS

    OemPnpDriversPath=drivers\audio;drivers\chipse;drivers\modem;drivers\nic;drivers\other;drivers\video;drivers\wlan

    OemPreinstall=Yes

    [GuiUnattended]

    AdminPassword=myencryptedadminpassword

    EncryptedAdminPassword=Yes

    OEMSkipRegional=1

    TimeZone=20

    OemSkipWelcome=1

    [userData]

    ProductKey=myproductkey

    FullName="admin"

    OrgName="MASD"

    ComputerName=*

    [setupMgr]

    DistFolder=C:\sysprep\i386

    DistShare=windist

    [Display]

    BitsPerPel=32

    Xresolution=1024

    YResolution=768

    [identification]

    JoinWorkgroup=MASD

    [Networking]

    InstallDefaultComponents=Yes

    [sysprepMassStorage]

    *a whole TON of storage devices, which i have removed to make the post more readable*

    So my question is, do i need to start from scratch and put in all this stuff and THEN reseal the box? (i know that some values are read from sysprep.inf and written into the registry when a machine is resealed... any help would be greatly appreciated!

    Taylor

    post-95889-1178203844_thumb.jpg

  8. does anyone know if WMI is up and running during the gui portion of an xp install? I have a script that will check the model of a machine and then install certain drivers (which are being troublesome and won't install properly without the setup file being run) based on that machines model. it works fine in a full blown already installed windows xp box, but it doesnt run properly when put into the commandlines.txt. it starts to run but fails. I am thinking this is because WMI isn't up and running yet there... any thoughts?

  9. it's a dell optiplex GX620, which has an ATI radeon x600 SE (128mb) in it.

    I have tried both the dell drivers (downloaded from dells site) and the ati catalyst drivers (most recent versions, downloaded from ati's site) neither one works.

    I am currently exploring some more creative ways of doing this (namely having a script check the model of the computer, and if it is "optiplex gx620" then that script kicks off the actual setup files from ati...) i would MUCH prefer to just be able to put in a few sys and inf files and a cat and have that take care of it (simpler is better)... but as of right now, i'll try anything ;)

  10. I thought a little more detail might be helpful. The drivers DO get installed, but when the computer comes back up it is running at 640X480, when you check in device manager the device is banged out (with a yellow exclamation point) and if you check the details it says "this device could not start (Code 10)". the funny thing is, i can right click on the desktop, and select properties and then change the resolution to whatever i want, and it works...

    I hope this can help someone help me :)

  11. Hi all, i've got my ris image about 99% done, everything works great except the ati drivers. I have all my drivers in the $OEM$\$1 structure. the problem is, i can't seem to find a way to get the ati drivers to work without running the setup program. I know i COULD use guirunonce or commandlines.txt to kick off the setup.exe, but this ris image is used for many computers, not all of which have ati cards. my boss would like to be able to continue to use the "one image for many machines" approach. Anyone have any suggestions?

  12. ok, a co-worker of mine mentioned that i might be "overcomplicating" things a bit... at first i got mad, but it made me look at the problem from another angle. what IS the problem, autologon. why do i need to autologon? to make guirunonce run. could the contents of guirunonce be put somewhere else, like oh, i don't know... commandlines.txt :P so i got rid of all my scripts except commandlines.txt and put all the junk from guirunonce into commandlines.txt, and low and behold! it worked perfectly with no user intervention and no autologon required :)

    yay!

×
×
  • Create New...