Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Lemon Lime

Member
  • Content Count

    7
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Lemon Lime

  1. The WAIK User Guide (found in the help of Windows SIM) has a section called "Methods for Running Windows Setup". It explains the valid locations of autounattend.xml. Here is the part of the section that describes the implict search order. The entire search order is listed in that section of the WAIK user guide.
  2. I have an update: I installed Vista, created a user called "Setup" and configured a profile. Ran sysprep /oobe /generalize logged on the the "Setup" user account. Rebooted into PE and captured the image using imagex. Then I created an autounattend.xml file using Windows SIM and included the copyprofiles component (Microsoft-Windows-Shell-Setup: specialize) and set that to true. When I brought the image down, I was prompted to create a new account, which I named "Setup2". When I logged in as "Setup2", some of the configurations did carry over from the original "Setup" account (I didn't set to many settings, the classic start menu and the modification to the gadget bar carried over). The desktop background however did not. Maybe there was something I missed in my configuration of the profile and unattend file. UPDATE: I just realized that after I was prompted to create a user, I was prompted to edit the computer name, with the option to select my desktop background wallpaper. Guess that's where the profile got it's background from.
  3. I am trying to create a Unattended Vista install with multiple partitions as well. The method I am using is to create the unattend.xml answer file using Image Manager and then apply that xml file (located on a removeable USB drive) during the Windows DVD install. After the install is complete, run sysprep /oobe /generalize, restart the computer into Windows PE and capture image using Image X. I am configuring the partitions in the autounattend.xml file using the Create and Modify Partitons components to create a Vista_Install(C:) and My All Data(D): partitions. When I apply the unattend.xml file during the DVD install, it creates the partitions correctly. However, when I run sysprep and boot into Win PE, the partitions get reversed. The C partition (where the OS should reside) becomes the D partition and vice versa. So now according to Win PE the OS is on the D partition. I tried capturing the D drive, but after deploying the image, Windows would not even start. Here is the disk configuration of my unattend.xml file. Anyone have any suggestions of what I maybe doing wrong? Going to give it another try. - <DiskConfiguration> - <Disk wcm:action="add"> - <CreatePartitions> - <CreatePartition wcm:action="add"> <Order>1</Order> <Size>20000</Size> <Type>Primary</Type> </CreatePartition> - <CreatePartition wcm:action="add"> <Order>2</Order> <Size>25000</Size> <Type>Primary</Type> </CreatePartition> </CreatePartitions> - <ModifyPartitions> - <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>Vista_Install</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> - <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>My All Data</Label> <Letter>D</Letter> <Order>2</Order> <PartitionID>2</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> <WillShowUI>OnError</WillShowUI> </DiskConfiguration> - <ImageInstall> - <OSImage> - <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> <WillShowUI>OnError</WillShowUI>
  4. I experienced those issues with RC1 and the BDD Beta as well. Any information if an updated BDD version is scheduled to release?
  5. Thank you Fizban2 for the suggestion. I checked the autounattend.xml file and it appears that OOBE is enabled. What impact does OOBE have on the default profile? I would like to configure the image so that new users that log into the Vista imaged computer will all receive the same default profile, with all the same desktop configurations (Classic Start Menu, desktop background, same desktop icons, tool bar configurations for example).
  6. Hello, We have been testing out WAIK and deploying an unattended test install of Vista Beta 2. I enabled the copyprofile property in the unattend.xml and ran sysprep with the profile that I wanted to be the default, but when I brought the image down, the profile was not being used as the default. I figured that possibly that feature was not ready in the Beta build. Has anyone been able to set a default profile? Now, with XP, I used to use the Administrator account as the default profile, but since you cannot login (should not) as Administrator in Vista, I will need to create a local user and use that for the default profile. I would prefer this local user not to be in the image when being deployed. Since you cannot login as administrator to copy the profile to the default user, how would I be able keep the users profile as the default while at the same time, removing the local user from the image? Anybody have a working process for image deployment? Thanks!
×
×
  • Create New...