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. 


stevemaser

Member
  • Content Count

    14
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About stevemaser

  1. I was just looking for some verification before having our people here contact "Premiere" support to enter this bug. Thanks! - Steve
  2. I've been able to reproduce this with some others working in other locations with differing "unattend.xml" files, but we haven't figure out if there's a workaround. Anybody have any thoughts on this: Go to Windows Update. Click the box that says "get updates for more products" and install the "Microsoft Update" add-on Reboot (if you want) a couple of times -- you'll see that Windows Update now says: You receive updates: For Windows and other products from Microsoft Update. Now run Sysprep. After rebooting and having the machine run through it's sysprep options.... Microsoft Update is no longer installed. Windows Update again has the box that says "get updates for more products". Which you can reinstall again. But you shouldn't have to. Any ideas how to workaround this? Some "reg add" setting for unattend.xml or something? We're stumped on this one so far. Thanks!
  3. think I found it: http://support.microsoft.com/kb/929828/en-us What a PITA...
  4. So, we got a copy of Vista Enterprise here (finally.) First thing I did was start playing with my "unattend.xml" file on my laptop and running sysprep against it to see how it runs. However, after running sysprep with no problems 3 times, when I tried to run it the *4th* time, I got a "fatal error" message. I thought sysprep could be run an unlimited amount of times in "Enterprise"? Am I missing something?
  5. I don't have access to the "connect" forums (I think?). I've posted it to the technet forums, though... http://forums.microsoft.com/TechNet/ShowPo...6&SiteID=17 (not sure if that is the same place or not...)
  6. RC2 doesn't help. Same thing: Have to set the network location *again* and Windows Updates are not configured properly (argh!)
  7. Are you actually getting *this part* to work: <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Work</NetworkLocation> <ProtectYourPC>3</ProtectYourPC> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> Everytime I run sysprep /oobe /generalize /reboot with an unattend file, every time I log back into my account after it's gone through startup, it's asking me to set the Network Location again -- *and* telling me that Windows Update is not configured.
  8. I submitted it as a bug yesterday. Don't know if it'll get into the "RC2" build that's supposed to be released later this week... I'd hope so...
  9. Now that I read up a bit more (and experimented with WAIK a bit further) my "unattend.xml" file now contains: <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <HideEULAPage>true</HideEULAPage> <ProtectYourPC>1</ProtectYourPC> (***WAS "3" but is now "1"***) <SkipMachineOOBE>true</SkipMachineOOBE> <NetworkLocation>Work</NetworkLocation> (***ADDED THIS***) <SkipUserOOBE>true</SkipUserOOBE> </OOBE> </component> Upon reboot after sysprepping with this, it's still coming up after I log in that I have to set the network location and that automatic updates is still not configured. But all the other Welcome dialog boxes are being bypassed as expected... Am I missing something here?
  10. OK, reading the documentation... I figured out that I had the wrong "ProtectMyPC" flag -- it should be "1". But I can't figure out why it's asking me to "set network location" again. I'm still looking for clues on that behavior. Nothing in the documentation is jumping out about this one... - Steve
  11. This site explained my "3 times" issue: http://www.microsoft.com/technet/desktopde...s/013106ds.mspx We have a VL version of XP -- you'd think that the Vista product keys would be VL versions so you could *fully* test stuff, but apparently not... Anyway... If anybody has any thoughts about why sysprepped machines are popping up with that "set network location" and "automatic updates aren't on" notices -- I'm all ears! - Steve
  12. This is my "unattend.xml" file, btw. This is basically exactly what this KB article said to do: http://www.microsoft.com/technet/windowsvi...3dd53bc3fa.mspx with the exception that I just renamed it "unattend.xml" as I was trying to see what sysprep would do *first* rather than continue on to use PE/ImageX, etc... <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>OS_Install</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</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> </OSImage> </ImageInstall> <UserData> <ProductKey> <Key>ABCDE-FGHIJ-KLMNO-PQRST-UVWXY</Key> <WillShowUI>OnError</WillShowUI> </ProductKey> <AcceptEula>true</AcceptEula> </UserData> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <HideEULAPage>true</HideEULAPage> <ProtectYourPC>3</ProtectYourPC> <SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/documents%20and%20settings/admin/desktop/install.wim#Windows Vista ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
  13. Hi all... (Just joined the forum after reading through replies, but I've got a couple of questions I've not seen addressed and nobody around here seems to be trying any of this yet, so...) With build 5728, I've started looking at imaging/sysprep so I can make a Vista load to install on other machines (hopefully). However, I've run across a couple major issues that I'm hoping somebody can comment on: 1) I have an "unattend.xml" file. I can manually modify a shortcut to sysprep to use it with the /unattend flag, but is there a location on the drive that I can put this file that sysprep *automatically* finds if I use the GUI version? 2) "sysprep" seems to only allow me to run it 3 times (!). After that, I get a dialog box about "A fatal error occurred while trying to sysprep the machine". Anybody know if this is intentional behavior? Or something limited to the betas (for some reason?) If so -- why? How is anybody supposed to debug their .xml files if they can only run sysprep 3 times? 3) In my 3 successfull syspreps, when I log back into the account on the machine, I'm asked to -- again -- set my "Network Location". I'm also informed that Automatic Updates isn't set on. Which is odd in that using WAIK, to make the "unattend.xml" file puts this part in it: <OOBE> <HideEULAPage>true</HideEULAPage> <ProtectYourPC>3</ProtectYourPC> <SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> The "ProtectYourPC" flag -- should that be "3" to have Automatic updates turned on? Thanks to all! Glad to see there's a forum somewhere where people are actually trying all this and commenting on what does/doesn't work! - Steve
×
×
  • Create New...