Need help with unattended network setup

Can anyone explain the process and why you would choose this method versus RIS or Sysprep?

I am stumped for some reason

I tried running it on a lab but cant seem to get it going. I have the I386 files on a server 2003 share set up as my "distribution server". It says to boot from network floppy and connect to share and run winnt32 or winnt. It also says you have to PRE-format it as FAT (?). Shouldnt this be NTFS? If not, why does it HAVE to be formatted as FAT?

I assume that once I actually do connect to the share point from the target pc that i would initialize the installation from a command prompt so that i could do the switches, correct? What if i just wanted to do an "over the network" install attended? i could just connect to share point and run winnt32 correct?

Sorry for all of the questions (and I am sure they seem STOOPID but this has me stumped for some reason

Find more posts tagged with

Comments

sprkymrk

Breadfan wrote:

Can anyone explain the process and why you would choose this method versus RIS or Sysprep?

Well, an unattended install is just running the setup with an answer file previously created. You can run it on any hardware platform as it runs the setup wizard for drivers and such rather than using driver files from the computer the answer file was created on. I rarely use it, but there are certain limited situations in which it might be useful. It is better than having to stand there and answer all the set up wizard questions, but not as good as RIS or Ghost/Sysprep by a long shot.

Breadfan wrote:

What if i just wanted to do an "over the network" install attended? i could just connect to share point and run winnt32 correct?

Yes. Just don't specify the answer file. You can just execute the winnt32. Otherwise you would execute winnt32 with switches like this:
winnt32.exe /unattend:answer_file

Here was a pretty decent explanation:
http://www.quepublishing.com/articles/article.asp?p=174359&seqNum=5&rl=1

HTH.

Breadfan

That explains a lot. I am still unclear of why the target computer must be preformatted as FAT and not NTFS, and how you would do it if it is an "unattended method"

Sprkymrk thanks for the help. Looks like you and I are both in SC but your scenery is MUCH better than here in the capital city.

I have wanted to move there since forever but the job market is very tight there (not that her in cola is better though

)

Again, thanks for the help

sprkymrk

Your welcome breadfan. I forgot about your question on FAT vs NTFS. I am not sure that is true, and here is why. For one reason, I know I have run an unattended installation on more than one occasion overwriting an existing NTFS partition. Now, just in case my brain is suffering from old fart syndrome and I never did do that (even though I know I did), here is something else.
You can manually edit a line in the unattend.txt file to use the command Repartition=Yes. This tells setup to delete all exisiting partitions on the first hard drive and create a single NTFS partition filling the entire drive. Can you reference your source that claims it must be FAT? I haven't searched technet, but the couple of books I have don't say anything about it.

Yes, I love the Charleston area - it's beautiful (especially compared to Iowa where I used to live). I make it up to Columbia quite often. I'm glad I don't live there, there's not much to say about it other than it has a decent mall and resteraunts, eh?

Breadfan

The FAT partition thing I got it from a couple of different sources, the first being the MS Press 270 book. Here's the excerpt:

2. Create a FAT partition on the target computer. The target computer requires a formatted partition to copy the installation files to. Create a partition containing at least 1.5 GB of disk space or more, and format it with the FAT file system.
3. Install a network client. A network client is software that allows the target computer to connect to the distribution server. On a computer without an operating system, you must boot from a client disk that includes a network client that enables the target computer to connect to the distribution server.

yes SC had to be a culture shock for you from iowa

sprkymrk

Hmmm. It doesn't say you have to use fat... Is that just a lab step-by-step excerpt?

Iowa=flat, you can see the horizon in all directions, you fall asleep driving and still make it to your destination because of straight roads, cold winters with snow, corn.

SC=trees and hilly, beaches, too much scenery to fall asleep driving, mild winters in the 50's, lizards in the house (freaks out the wife), flowers everywhere.

Breadfan

I checked the study guide from MCMCMSE.com and it states to format it as FAT or FAT32. Either way, I will try it all 3 ways.

I first have to get it working on my VMware. I think i have it solved though (i dont have a floppy drive). if i use an iso of a floppy image and conenct to that i think i can make it think its a floppy drive (it works well for cd rom drives and faster too)

i have had the lizards too (the cat and wife were freaked)

wish there were good companies with good opportunities there in charleston. i want to move to either sullivans isle or some place maybe west ashley where we have friends. SC isnt exactly the techno hub of the southeast US

jburn

Breadfan, DOS can not access NTFS partions. You must do the conversion after. That is why you would use FAT or FAT32.

Breadfan

Thanks for the help jburn. It makes since and I wouldve figured it out I guess had i got the vmware lab to boot correctly to try this out.

I shouldve known that anyway. a big DOH to me

Hopefully i can get the vmware lab to work soon so i can actually study 270 stuff instead of figuring out the vmware stuff

Thanks again

jburn

No problem buddy, and don't feel bad about asking questions. The more you work and study with any technology the more comfortable you will get with it. Nobody knows it all and what they do know, they had to learn also. ( Myself included )

sprkymrk

jburn wrote:

Breadfan, DOS can not access NTFS partions. You must do the conversion after. That is why you would use FAT or FAT32.

When does DOS need access to the drive during an unattended install? You boot with a floppy with network drivers to access the i386 distribution share OR you boot with the Install CD using an answer file on the floppy disk (named winnt.sif). Either way, winnt32 can access the drive, dos does not play a role. As I mentioned, I have performed unattended installations using this method more than once.

Maybe I'm crazy? :P
I am going to have to find a spare machine and try it this week.

jburn

When you boot from a network boot disc you are in a DOS environment and therefore are subject to the rules of DOS. Since you are not running setup from your CD drive you must access a partition from a network share that has the I386 folder on it, DOS cannot access a NTFS partition in any shape form or fashion. When you perform an unattended install by using a CD and having your winnt.sif answer file on a floppy you are not actually booting from the floppy, you are booting from the CD, which starts set up without having to access any partition and then looks to the floppy for the answer file.

sprkymrk

jburn wrote:

When you boot from a network boot disc you are in a DOS environment and therefore are subject to the rules of DOS. Since you are not running setup from your CD drive you must access a partition from a network share that has the I386 folder on it, DOS cannot access a NTFS partition in any shape form or fashion.

With all due respect to you jburn my friend - dos can, does, will, and always has been able to access ntfs across the network, because you are no longer dealing with ntfs locally. I am sure dozens of folks on this forum have created dos boot disks that would map a network drive somewhere on a server that used ntfs and pull an image file down from it. I have done it many many (and many more) times. So when you use a dos boot disk with network drivers, as long as the share is not local, then you can access it all day long.

jburn wrote:

When you perform an unattended install by using a CD and having your winnt.sif answer file on a floppy you are not actually booting from the floppy, you are booting from the CD, which starts set up without having to access any partition and then looks to the floppy for the answer file.

That was kind of my point.... wasn't it?

So again I ask the question - At what point during an unattended install does dos ever need to access an ntfs partition? Then back to the original question - Why would you need to format with fat32? My answer is that you don't need to. As I mentioned I have done unattended installs over an NTFS drive just fine. I also have Mark Minasi's Windows 2003 Server book (I can stand on it to reach stuff on top shelves the thing is so big) and the Coriolis Windows 2000 Server On Site book, both have chapters on Unattended Installs, neither mention fat32.

And if I am wrong, I'll buy you capuccino next time you are in Charleston, deal?

TechJunky

I just went ahead and setup a cd with the winnt.sif answer file under the i386 folder. This way makes it much easier. Dont have to deal with a floppy disk. You can have a ntfs or fat file system. I have a burned cd with SP4 and an answer file on hand just incase I need it. I would recommend making a bootable cd with an answer file on the disc just for good practice.

http://www.aselabs.com/articles.php?id=149

Here is a decent tutorial. Just replace SP2 with the latest Service Pack for your OS that you are creating the unattended install for.

If you are really lazy you could always use this tool.

http://www.softpedia.com/progScreenshots/Windows-Unattended-CD-Creator-Screenshot-28180.html

Breadfan

I think I have it. My problem was (is) that I took out my floppy drive when i added a new HD and had trouble with the vm ware floppy since i didnt have one. i found a link and am using a "virtual" floppy" so that i can create a boot disk then save it down as an image then use to my VM. seems to be working.

I have spent WAY too much time on this. in retrospect, I shouldve just broken out my old 400MHz machines and KVM switch and installed the server and client machines that way. They at least still the floppies

but i have learned much about vmware workstation so that is a plus I guess. Next time i will prep the VM's much better.

Again, thanks. As I go thru the MS Press 270 book exercises I am sure I will have more obstacles and questions. Is it time for a beer yet?