[unattended] Unattending Network setup boot

[Gigre]

Hey guyz, i am new at this forum, so Hi!!

have been using the unattended site for a while now, but i want edit more then i can find on google =)

So....this is what i want to make =):

I have a unattended winXP cd (or any...MCE or something....) and i want the DVD/CD to read a awnser file from an external location (like c:/ bla?) that containes info like:

CD-Key

Computername

Computer discription

IP Adres (static/DHCP)

and some other information

This so that i have 1 cd/dvd with all the updates/unattending 'standard' stuff and a awnser file that contains more info that can change when i reinstall a machine.

I think i can do it like this....

I format the machine

Get the anwser file on the C:/anwser on some way (floppy/cd/usb stick whatever using some sort of bootcd/flop) mayby network?

then put in the unattended DVD/CD that installs everything and reads the external file for the non standard info.

Done =)

But when i was writing this i was thinking mayby the stuff i want to do can be done AFTER windows is installed........

So i use the unattended DVD/CD to install/format/standard all settings and when the pc first boots it runs some sort of script that changes these settings....my question would be is this possable, can i change a serial when windows is already installed using another serial.......

I'd like some more information/ideas for this from you guys, i seached some on this forum and website and google, but did't find anything, hope you guyz can help me out

Edited June 3, 2006 by Gigre

[Mordac85]

Sorta similar to what most people do is to use an install base (from a CD or network share) and they run winnt32 w/the switches to point to the correct files like so:

winnt32 /unattend:<answer file> /s:<install source>

You can find more info on that technique in the MS Deployment Guide

I started off by placing mine on an IDE drive (formatted FAT32), slaved it into the new system and adjusted my boot floppy as needed. I preferred the clean installs but corporate decreed we shall use images. So....

IMHO, it's much easier to leave certain fields in the answer file blank, like computername, and have that be the only prompt on my build. Anything not covered by the answer file is scripted and executed using GUIRunOnce or RunOnceEx. Not a totally automated solution, but you could put the effort into making it automated.

Edited May 11, 2006 by Mordac85

[Gigre]

Ok, thanx

Will be working on this soon, i now have a fully automatic winxp SP2 w hotfixes and the 'standard' awnsers in it, can i still use another awnser file that 'overrules' the one i have in it?

And yea, most use images, but its way better to use unattended DVD's with the standard software installed + custom awnser files for the computernames/ip etc etc etc....

but images have good functions to, but its hardware based =) (most of the time)

[Mordac85]

I've never seen where you can use multiple answer files, or tried it for that matter. I guess you could script the creation of an answer file then kick off the install. One way or antoher you'll have to add the system specific info somewhere.

[Gigre]

But how the *** am i going to 'call' a netwerkdrive in DOS where i can call the unattended awnser file.

winnt32 /unattend:\\servername\unattend\computername.txt /s:d:/i386

something like that, for as i know winXP pro can't do that in his pre install console?

(can't use boot flop for it, because some pc's don't have a floppy, so i need to make a network DOS boot cd and then put in this unattended DVD with this command.......)

is that possible? just thinking and writing atm, not sure if i make sense atm

[Mordac85]

Since you want to maintain the flexibility of changing the files per build I would create a boot disk that can either ask the user for the variable data and create the finished answer file on the fly before kicking off the install. This way the batch file doesn't need to change everytime and it will be fine as the boot source for a CD/DVD. You could use a ram drive as a staging area for all of the file manipulation, but if that's the case why not just leave the fields in the answer file blank and input the data as part of the build process?

On the other hand, you can map to a network drive as part of your autoexec.bat and pull in, or reference, the already edited answer file from your network share as needed. This is a quick C&P from my old boot floppy where I logged into our domain and mapped the drive (I know there are easier ways to do this but it's a good example of what I mean).

net initialize
netbind.com
tcptsr.exe
tinyrfc.exe
net logon USERNAME PASSWORD /domain:DOMAIN /yes /savepw:no < password.txt
net use Z: \\SERVER\SHARE /persistent:no
winnt32 /unattend:Z:\computername.txt /s:d:\i386

If you really want to get creative you could script a method to derive the fields from existing data on the PC or connect to a database that either already has the info defined and create the file on the fly. Like the Perl guys say, "There's more than one way to do it" and it really depends on how you want to implement it.

How many systems per month are you building and how automated do you want the process to be? If you have to manually edit the answer file for each system you're going to run into a bottleneck at some point. Right now there are only 2 fields we manually enter, computername and the end user's name. Everything else is automated and the tech only has to complete those. Not a big deal for us, but what fits for you?

[Gigre]

Well, its a pretty big deal here =)

i think the network solution is the best here, the files you are calling,

netbind.com

tcptsr.exe

tinyrfc.exe

are they 'standard' on a winxpSP2?

will be trying some things the upcoming days, thanx for ur info so far, if you have any ideas let me know =)

just want to change many custom information (DHCP/IP/computername/user account/admin pass etc etc etc)

best way to do it in a custom awnser file that we create using a web based interface, and after that put it on a USB stick or something like that and put it on a server.

[Gigre]

Ok, i got alot of work done now and finaly i am getting somewhere

I have this:

I'll boot with barts network disk (with some extra .cab files for network cards) and boot the pc.

I'll partition the disk with gdisk (will try to find a better one with NTFS support....any1? )

reboot

I'll boot with barts network disk (with some extra .cab files for network cards) and boot the pc.

then i'll make a network connection to the server (works now)

i'll run winnt /u:<path> /s:<path> and then it will start.

the problem is that it keeps saying 'copying files' but it does't do anything! it just keeps that way for hours

I don't know why, did't had much time anymore to try some other commands or formats....but it did't work :/

Does any1 know how to fix this? and/or how to make a NTFS disk in DOS (command line based?) (its faster and i can make it unattended with a batch script.)

The reason i need to make a disk is because when i try to run winnt /u etc it says it does't recognise any HDD"s in it that can be used to store the temp. install files........

mayby there is another way? (ram disk? temp. fat format and then in setup ntfs?) i don't know.....but if any1 would help me

Hope everything is clear, if there are any questions, please let me know, and no, RIS is not an awnser for my problem

edit: reading this topic again.....could it be i did winnt instead of winnt32? winnt32 is windows only right? so....that can't be it?

Edited May 24, 2006 by Gigre

[Mordac85]

You need to use FAT32 for the temp partition, NTFS won't work. Don't worry about the NTFS before your install as long as you've setup the answer file correctly it'll do the job for you.

As a test, you might want to place your install files on a second HDD and slave it into your test system. Adjust your routine and test from there. The speed difference will be amazing and make working out the bugs a whole lot faster too. Once everything is worked out on the slaved drive it's a simple matter to transfer that to a network share. That way you know the install routine and file source is working and any other issues will be in your network connection.

Sorry I didn't get back earlier but as you probably found out netbind.com, tcptsr.exe, and tinyrfc.exe are part of the DOS MSClient for setting up networking and TCP/IP.

[Gigre]

You need to use FAT32 for the temp partition, NTFS won't work. Don't worry about the NTFS before your install as long as you've setup the answer file correctly it'll do the job for you.

As a test, you might want to place your install files on a second HDD and slave it into your test system. Adjust your routine and test from there. The speed difference will be amazing and make working out the bugs a whole lot faster too. Once everything is worked out on the slaved drive it's a simple matter to transfer that to a network share. That way you know the install routine and file source is working and any other issues will be in your network connection.

Sorry I didn't get back earlier but as you probably found out netbind.com, tcptsr.exe, and tinyrfc.exe are part of the DOS MSClient for setting up networking and TCP/IP.

np

Well, its still strange that it keeps saying coping files, and that it just does't do anything ....

Will try again next week, the pc's i am working on are not @ home atm.

[Gigre]

Well, i did some things yesterday to test it.......I have now a windows (not unattended yet) with all hotfixes/SP's and i can install via the network.

Only when he is done with copiing the files that are needed to boot the windows setup it gives a funny blue hardware failure blue screen

I will try to change some hardware/try it on another pc......mayby its wrong =), because even a clean winXP home via the network does't even work!

When this works i'll add the unattended awnser file to it, and hoping he will keep copiing the files.

When this i done i can make a bootable cd/dvd/flop that boots, gives a boot menu with windows DISTR and a list of awnser files that i can take or let me enter a filename for the awnser file.......

Hoping it will work, will make reinstalling pc's alot easier whehe

[Gigre]

Okay, after some debugging (again....) i am this far:

I have made a DOS bootmenu so i can choose what windows i want to load/what i want to do

First i format 20% of the HDD in fat32 (quick format)

format

then i'll make a network connection and will run winnt /s:d:/bla/i386

It copies some s*** to its RAM

it now wants to copy the files to the HDD

----------ERROR----------

In a P-ATA sitiation this will happen:

It copies the files, reboots and then it will run the unattended GUI setup perfect.

in a S-ATA situation i get this:

It will say 'copying files' (i checked untill a hour, then i quit it) and it stays that way, no progress bar, no nothing........i think its because it needs SATA drivers, but i can't 'add' the files live from a disk because the setup is not there yet (u know...when i can press F6 to add drivers and F2 to system restore)

I can make disks and use F6 when needed, but it does't get that far, so i want to intagrade the drivers in NLITE (np right... ? (i hope :s )) but now...finaly my question....

Where can i find an universual S-ATA driver or some custom S-ATA drivers that i can add very fast and that will cover alot of S-ATA/RAID chips....

And then will this work? thats the question....or is there another way? a workaround or something.... ?

After this everything works perfectly (can check here with VMWare and @ a P-ATA disk) custom made winntbuu.dll, winnt.sif txtsetup.sif etc etc etc.

I am almost there to complete it all, all i need is to fix this S-ATA problem because that stupid M$ did't add some standard drivers to SP2....(if they are even out there?)

its alot of tekst, but need help, thanx..

[Mordac85]

So I gather everything works fine for you using a std IDE/ATA drive? If you're having problems w/just the SATA drives you probably need to modify your install sources to include the necessary SATA drivers.

Sounds like you need to check out the Unattended Guide's info on RAID/SATA drivers and add them in. Sorry, but I don't know of any generic drivers for SATA.

[Gigre]

So I gather everything works fine for you using a std IDE/ATA drive? If you're having problems w/just the SATA drives you probably need to modify your install sources to include the necessary SATA drivers.

Sounds like you need to check out the Unattended Guide's info on RAID/SATA drivers and add them in. Sorry, but I don't know of any generic drivers for SATA.

Ok, to bad...will be looking for some things now and try some things, thanx anyway =), will post again if i run in more problems....

thanx for your help.

[Gigre]

For IDE i have it like this:

Boot from CD/DVD

(quick)format my disk 100% with gdisk (fat32)

reboot

make network connection

run winnt and say that it must update the fat32 to ntfs (temp. files allready installed now....)

done.

It works good (atleast, tryd it once and it worked )

Now just need to try it for S-ATA, and hope it works.......