> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Doherty, Chris - Elmira, ON
> Sent: Friday, September 16, 2005 4:22 PM
> To: unattended-info@lists.sourceforge.net
> Subject: RE: [Unattended] Never mind; continue about your
> daily business ( was biosinfo.txt not found when using
> unattended with XPSP2 integrated MV LS)
>
> > 2 unattended.sourceforge.net Overview
> >
> > It took me about two weeks of working with the system to
> really wrap
> > my head around how things worked. Hopefully I can explain
> it a little
> > better than the documentation did.
>
> What I find I need to know most is exactly how to control all
> the various scripts so they do exactly what I want to, not
> what the developer thinks is the Right Way To Install
> Windows. This is why I abandoned ANI - there are too many
> non-standard assumptions hard-coded into the config files.
> Same thing here - AFAICT, the only way to pass a drive share
> and credentials to Unattended for mapping the Z: drive
> automatically without hacking the DHCP server is by either
> rebuilding the boot CD or using PXE netboot, both of which
> require significantly more investment of time than I've got.
You can easily modify the linux iso-image. Under Linux i.e.:
mount isoimage to dir
copy dir to new path
modify isolinux.cfg
make new iso with mkisofs
Under Windows you can use WinIso or similar...
it works!
regards, Moritz
>
> I'm in a fairly typical situation: we have Windows XP on the
> desktops, we need to standardize our installs, but for legacy
> reasons we haven't moved to Active Directory yet, otherwise
> I'd be using RIS and not bothering with any of this.
>
> At this point I'm planning to abandon both Unattended and ANI
> and just write my own simple solution. There are too many
> deal-breakers in the setup assumptions of Unattended:
>
> 1.1) You have to create a DNS alias of ntinstall for your
> install server - sorry, this is a branch office. We don't
> have access to the DNS server.
> We're not allowed to rename servers, either.
> 1.2) You have to enable guest access to your deployment
> server (actually, the docs imply *on your domain*). Forget
> it. Not gonna happen at any Windows shop that isn't
> completely insane.
> 1.3) To change either 1.1 or 1.2, you have to either netboot
> (so you can change the pxelinux cfg) which involves changing
> the DHCP server (branch office, not gonna happen) or rebuild
> the boot CD from scratch, which requires massive source
> downloads, gcc, and time. I've tried burning the boot CD to
> a CD-RW and then overwriting the isolinux.cfg file, but
> that's not working.
>
> In my opinion, fixing these problems is a great deal more
> important than allowing for custom partitioning schemes.
> I've never seen a Windows shop that does anything but one
> large NTFS primary for their workstations.
>
> Not to mention the scripts themselves:
>
> 2.1) use strict; ? Okay, while we're at it, how about use
> english; use warnings ; use
> variable_names_that_make_some_kind_of_sense ; use
> an_architecture_diagram_and_stick_to_it ; use
> comments_that_adequately_document_your_code ; ...
> 2.2) sub{}s go at the end of the file, not embedded in your
> primary script logic.
> 2.3) Variables go at the top of the file, not embedded in
> your primary script logic.
> 2.4) Too many scripts in too many locations, none of which
> are documented.
> Jumping back and forth between the boot medium, c:\netinst,
> z:\dosbin, and z:\scripts without any indication of how and
> when script execution is handed off (or why) makes the system
> nigh-unmodifiable.
>
> I would guess that the majority of people who need an
> unattended system like this are working in a largish office
> environment with some pretty straightforward and standardized
> needs that are _not_ going to match the assumptions in
> unattended. But in its current state, 4.6 is basically
> unmodifiable without, as you mentioned, spending two weeks
> wrapping one's head around it. I've spent a week working on
> this, and right now I'm going to spend an afternoon building
> a Bart's Network Boot Disk, and an unattend.txt on a network
> share, and that will work just fine. Software package
> installs I can do from within unattend.txt.
>
> Chris Doherty
> Helpdesk Analyst
> Crompton Co./Cie a Chemtura Company
> Elmira: (519) 669-1671 x319
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App
> Server. Download it for free - -and be entered to win a 42"
> plasma tv or your very own Sony(tm)PSP. Click here to play:
> http://sourceforge.net/geronimo.php
> _______________________________________________
> unattended-info mailing list
> unattended-info@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/unattended-info
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info
