Jump to content

brettule

Member
  • Posts

    5
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Australia

Everything posted by brettule

  1. I took a look at the examples and noticed my specialize has a lot of x86 entries in it when really it's only used on 64bit machines now. I copied the 64bit example you linked into my xml and then transposed my various 64bit settings only and added a few others. Although I don't know which line exactly was causing me the issue doing this has solved the error. Cheers.
  2. Nope, that didn't fix it. The exact error is: Windows could not parse or process unattend answer file [C:\windows\panther\unattend.xml] for pass [specialize]. A component or setting specified in the answer file does not exist. I guess that means something is broken in the <settings pass="specialize"> ????
  3. After I sysprep with my unattend.xml the system reboots then fails to build properly claiming "a component or setting specified in the answer file does not exist." Can anyone tell me what is causing this? My unattend.xml is attached. unattend.xml
  4. Hi, I want to achieve a single build, what's the best approach in your wisdom? I have a ghosted XP image with all various applications and OS tweaks already installed. It's been syspreped ready for deployment. - The image needs to identify and load drivers for many different hardware platforms, mainly Dell's. Q. Is the best way to do this with the answer file? - The image although English will be deployed in many timezones and require many different regional settings/keyboards/etc. Q. Should I use a script at some point to prompt for a location to set up the regional settings, where would I do this?
  5. We have a different local admin password for each of our offices, in our unattended build we do not specify a password instead we allow the install to prompt the tech and set the office standard password. Problem is that although this looks like it works, it in fact does not change the password at all! It leaves the original admin password in tact from when the machine was first built and sysprepped. Anyone know how to fix this?
×
×
  • Create New...