In-place Win to SBS upgrade

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I have a first-time in-place upgrade from Windows 2003 R2 to SBS 2003 R2. Windows is completely patched. The SBS 2003 is a retail (not OEM) set. I have read and acknowledged all the warnings and followed the procedure outlined in

http://www.microsoft.com/technet/prodtechnol/sbs/2003/plan/gsg/chptr3c.mspx

As directed I ran adprep /forestprep first. After entering the product key, the install runs about 5 seconds and completes with a block message that simply says "Set was interrupted because of either user intervention or an unexpected error."

Help...

Joe
.



Relevant Pages

  • Re: XP Copy
    ... >> Microsoft sells retail and a OEM version for use by people ... The OEM operating system can ... >> Microsoft also sells and licenses the larger computer makers ... >> to install customized versions of Windows on computers they ...
    (microsoft.public.windowsxp.general)
  • Re: CD Key Errors
    ... CD-Keys with different media are always interesting, ... A retail key is different from an OEM key, ... MS-MVP - Windows Setup and Deployment ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: OEM and Standard windows - What are the differences?
    ... > difference between OEM and Retail editions. ... > SP1a for each of them, I can't install windows on any of the PCs, The ...
    (microsoft.public.windowsxp.general)
  • Re: Format Drive
    ... new complete version of Windows instead of the OEM Windows I have. ... What makes you think that a retail version is ... You're probably right about retail being essentially OEM, but remember, many companies, like the Dell MCE machine I'm working on that them moment, can pretty severely bastardize the windows envronment under the guise of "customization". ...
    (microsoft.public.windowsxp.basics)
  • Re: Format Drive
    ... new complete version of Windows instead of the OEM Windows I have. ... What makes you think that a retail version is ... No disk calls for the next disk to use and most filenames are simply ...
    (microsoft.public.windowsxp.basics)