HerbM

Member
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About HerbM

Profile Information

  • OS
    Windows 7 x64
  1. I just downloaded the portable 7zip version, unzipped it, and ran the GDism xxxx.exe file. I made on change, English instead of Spanish, then tried to use the OSCDImg function. The buttons next to ISO and Source folder were unresponsive. Am I missing something? Is this a good version? Nice idea -- thanks for taking the trouble to share and to answer questions from people like me..... -- HerbM
  2. Quite alright, that confusion is due to my trying to distinguish multiple 'autounattend.xml' files -- I called on the Dell.xml just as (poorly chosen). Yes, I will call setup and specify the file, but first I must 'merge' the settings from the 2 files. My file and the Dell provided autounattend.xml It is the only way to deal fully with 2 WindowsPE sections both having critical information.
  3. So is this how the command prompt in WinPE is done? What pass? I need to replace the booted Command prompt in a WinPE with a scripted command prompt to (like you say) do multiple things. I have assuming I could do this but it sounds like you are pretty much describing what I need to do. After a functional WinPE is running with basic windows command line, I need to run commands to fix up the AutoUnattend on writable disk (merge tow of them actually) and then (re)start the (separate source)DVD installer for the real (non-WinPE) install. The details aren't important, but the idea is to "do some stuff" from WinPE and reboot. So, likely I could just call this out in the Windows PE section of the (WINPE) AutoUnattend.xml file. Cool. Thanks. -- HerbM
  4. I am going to read that article -- I now have at least one bootable (on his machine) WinPE. Proof of concept I can build another with my own features to run a script, rebuild the combined XML files, replace the Dell version, and reboot-to/start the actual install while the drivers are there. Likely the drivers are on a "timer" -- they stay connect for some time not a fixed number of boots, and certainly not just "1 boot" That was good news. Also, I have found the bypass for the "OS check" when provisioning the drivers -- the iDRAC provisions drivers for a particular OS and then CHECKS to see if the OS is present, but there is a bypass if your OS doesn't (actually) match or if you are going to connect that real OS later. Again, Thanks.
  5. Not exactly... There are 3 other places that setup will look first before going to media. This TechNet Article explains the implicit search order for answer files. When it does get down to the media locations, it searches in drive letter order. If you mount the ISO, can you find an 'Install.wim' file (I am unfamiliar with the Dell disc, so pardon me if I'm incorrect)? If so, you might be able to pull the wim file off the DVD, use ImageX to mount it and replace the answer file with your own, then create a new ISO with the modified wim file. I understand there are 'other' locations, that is no the thrust fo the question (exclusivity) -- My question is whether all roots were checked -- my testing say the answer is "yes". Not using a Dell disk --- what disk do you mean? Without mention of Dell, I would have thought you meant MS Windows 2008 disk. I briefly tried to use the WIM from the install DVD -- but I didn't spend enogh time to become fully expert enough to know if I did it correctly. It's good idea, but I will be just "hacking" until I learn more of the details. Thanks for the response.
  6. The answer is: One AutoUnattend.xml file per pass. Only the first which has a particular pass configured gets used. That's what my testing and reading the setupact.log shows. They are both 'read', 'checked', and 'seen' but only first one is used during WindowsPE pass. It's been a tough few days, but boy did I learn a lot. -- HerbM
  7. Thank you so much for responding - this is a very sticky and tricky problem. First, I am pretty sure that it is safe to say: No, two AutoUnattend.xml files will NOT be processed by the install for the SAME pass. The first one (i.e., highest precedence) configured for a particular pass provides ALL of the settings. 1. Can't do that easily - it's coming out of Dell flash and already processed by the time I would see it -- in fact, at the point it is available and processed I am no longer in control of the process and the Unattended instal should be wel on th way. 2. Can't do that -- there is no "iso" when this happens --the ISO is mounted (read-only) as if it is a real DVD (For all practical purposes it is a REAL DVD.) 3. Audit mode is way to late - I need to affect WindowsPE mode and cannot run sysprep because I am doing a "DVD Boot" install. I actually have convinced myself that only one file is processed (per pass) so now I have a new scheme. In rough outline: Mount on iDrac Flash my script created "img" file with Autounattend.MINE (some other name) for the custom install. Build my own WindowsPE ISO (small as possible) mount it on iDrac Flash -- include Perl or some smaller tool to auto edit the multiple XML files Mount the OS Install DVD as a remote file (doesn't get copied in full until needed by installer) Boot to my own PE, run a Perl (or something) to fix up the combination of the DELL and my custom XML. (This part is pretty easy if I get control here) Reboot to the DVD (that's mounted) for the install with the correct (full) XML So in essence, this is a really round-about-way to do your #1 idea. Thanks for the suggestions and you may have given me another idea that COULD be simpler.
  8. Can Multiple AutoUnattend files be processed on the SAME PASS, e.g., WindowsPE? If there are multiple AutoUnattend files found containing WindowsPE pass items, will ONLY the items from the first (highest priority) be applied or will they all apply? [Assume there are no conflicting settings -- if there are conflicts then I would expect the file with the highest priority to "win".] My extensive searching and reading has found no information directly addressing this -- my testing suggests (strongly) that only the first file is used. Reason: I need an AutoUnattend.xml coming from the Dell Integrated LifeCycle controller to supply the disk drivers configuration AND for my own file mounted on removable media to ALSO be applied -- there are no conflicts, just both are configured to do things in the WindowsPE pass: Disk driver config by Dell's file and Drive partitioning etc by my file.-- both during WindowsPE pass. -- HerbM
  9. Additiional Info after more investigation: Using the Shift-F10 Command prompt during the (paused) install, and looking in %WinDir%\Panther there is NO answer file (XML) there -- supposedly the one that is being used should have been copied to the Panther directory by the install. However, using FIND on the setupact.log shows 2 AutoUnattend.xml files are being found -- on on C:\ (a minimalist one likely produced by the Dell driver provisioning) and MINE on E:\ (as intended). Both are valid; both have WinPE sections. The Dell one on the C:\ would take precedence over mine. Is there some way that MY answer file can "supplement" the Dell one? The Dell XML is essential to Driver provisioning & installation -- it is difficult or impossible to replace or do without Edit: Reading Here http://technet.microsoft.com/en-us/library/cc749415(v=ws.10).aspx ...it's not even clear what happens with multiple valid configs for the CURRENT phase -- does the 1st get used or do they get combined in the precedence order and all (combination) changes applied? That would be perfectly fine as the WindowsPE section of the Dell driver provisioning has no conflicts with my WindowsPE section..... -- HerbM
  10. Thanks in advance -- I have tried to search here and google to see if this has been covered but no one seems to be doing quite what I am working to do. Win2008 R2 SP1 integrated DVD source. I believe that my AutoUnattended.xml is not being found during the install (after spending a lot of time proofing,rebuilding, validating in SIM,trying the sample with minimal modifications etc) so my file must be being SKIPPED. Please confirm or correct my understanding of the location of this file. Goal: Install from DVD* source with no admin/user input. My Understanding: an AutoUnattend.xml on the ROOT of available media is be read and processed. Is this correct? I have the AutoUnattend.xml on the E:\ drive root -- I can confirm that by pressing Shift-F10 to get a shell command prompt when the Language UI dialog pops up (which also indicates my file is not be processed correctly.) The file is clearly there in the root. Language settings, OS choice, Disk partitioning etc are throwing dialogs so EITHER the file is not being found OR it has some type of error that make it fail to process. [E: is read-only but I understand that this should only affect the PRECEDENCE of the XML file if there were multiples -- I only have ONE.] I am virtually certain that this method worked at least once and that it is a supported/recommended way to provide the file. * For those interested in "Why" -- technically this is a DELL iDRAC (iLO) Server with the "DVD" mounted from an ISO file on a nearby server, and the E: drive is created on the SDCard in Flash memory to contain the AutoUnattend.xml file. The media is definitely mounted since I can see the OS DVD as F: and the XML file is clearly present (read-only) on E:\. I do not wish to pre-build a bunch of custom images for every change so wish to use the stock (MAK) DVD for this. Once this is working, I intend to write a (simple) script to modify the 10-20 things we would typically change for different installs etc. (Server type, tools loaded, disk partition sizes etc). I wish to take advantage of the fact that I SHOULD be able to get pretty much any type of OS install from ONE "stock DVD" merely by changing ONLY the XML file. Since I am going to need to edit the XML file for each install anyway, i would like to limit the changes to just that. Any thoughts? Ideas? -- HerbM