• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About negatiiv

  • Birthday

Profile Information

  • OS
    none specified
  1. Great, thanks, I'll read those posts about the kansas shuffle and the fake signature method.
  2. Hi All, I have some old systems which have no cdrom, just USB 1.1 and Firewire 400. Installing Win 7 from PE3 would take a long time from USB 1.1, so what I have been doing is booting to PE on a USB key, then running setup off the Firewire HDD. However booting to PE from the USB key still takes quite a long time. Can I set up my firewire HDD as bootable to PE, and then when the computer boots from USB it transfers the boot process to the firewire drive? I've heard of creating a kicker cd for use in systems which don't support usb booting, but I guess in my case I would like to create a kicker usb key for use in my system which doesn't support firewire booting. Thanks!
  3. I combined my autounattend and unattend (no duplicate entries), went back to a previous version of my image, deleted the file C:\Windows\Panther\Unattend.xml, then ran sysprep /generalize /shutdown /oobe /unattend:d:\autounattend.xml. Didn't make a difference though. However I just realized that maybe sysprep is copying the Administrator profile, rather than my standard local admin account, even though the administrator account is disabled. I'll try making all my customizations to the administrator account and then capture the image again and test.
  4. This is from my 64bit winpe pass which will wipe the drive, create two partitions (one 100mb partition, one partition will fills the rest of the drive), and install windows to the second partition: <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi=""> <SetupUILanguage> <UILanguage>en-US</UILanguage> </SetupUILanguage> <InputLocale>0409:00000409</InputLocale> <SystemLocale>en-CA</SystemLocale> <UILanguage>en-CA</UILanguage> <UserLocale>en-CA</UserLocale> <UILanguageFallback>en-US</UILanguageFallback> </component> <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi=""> <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Size>200</Size> <Type>Primary</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Type>Primary</Type> <Extend>true</Extend> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Format>NTFS</Format> <Label>System</Label> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Format>NTFS</Format> <Label>Windows</Label> <Order>2</Order> <PartitionID>2</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> </DiskConfiguration> <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>2</PartitionID> </InstallTo> <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> </component>
  5. Thanks for that! So would it work if I combined my autounattend and my unattend files?
  6. I have a custom wim file which I created after I ran sysprep /generalize /oobe /shutdown /unattend:e:\unattend.xml. In the unattend file, I have the copyprofile set to true. When I apply the wim file using imagex or wim2vhd, the default user profile behaves as I would expect it to. I can create a new local user and it uses the default user settings. However when I use the deploy the wim file using windows setup and my autounattend.xml, the default user is no longer what I created. The theme is gone for one example. Maybe other items are gone, if not all. So my question is: Do I need to have the copyprofile set to true in the specialize phase in both my unattend.xml file and my autounattend.xml file? I thought only in my unattend.xml file. Thanks!