Operating System Deployment Feature Pack Frequently Asked Questions


Q. My advertisement for Operating System Deployment started on the wrong client, and the user has postponed it. How can I keep it from completing?(Added January 31, 2005)

A.

Follow these steps:

  1. Delete the advertisement to prevent the program from running again (applies to mandatory and recurring advertisements).
  2. On the distribution point, rename the OSDInstallWinPE.exe file in the image package folder. After the client fails to complete the installation, you can restore the original file name.

Q. Do I need a txtsetup.oem file in both the network drivers and storage drivers folders when I create a bootable CD that contains the Image Capture Wizard?

A. No. You need a valid txtsetup.oem file only in the storage drivers path that you specify on the Windows PE section of the Image Capture CD Wizard that you run when you create the bootable CD.

Q. Why did the User State Migration Tool scanstate.exe crash on some of my computers?

A.

If you do not use the /all or /user command option, the User State Migration Tool scanstate.exe crashes on computers running a fully patched Windows 2000 Professional Service Pack 4 operating system when run under the local system security context.

Because you don’t ordinarily run scanstate.exe as a separate command line, you can add the /all parameter on the Specify additional command line options text box on the Capture User State action dialog box (found by clicking the Advanced tab of the Image Package Program Properties dialog box).

In the following example, the command fails:

scanstate.exe /l "C:\MININT\scanstate.log" "C:\minint\state"

If you append the /all or /user command option, the command completes successfully. For example, the following version of the command completes successfully:

scanstate.exe /all /l "C:\MININT\scanstate.log" "C:\minint\state"

Q. The primary partition on my reference computer is drive D. When I run the OS Image Capture Wizard, why do I receive an error message that only the C drive is supported?

A. The Operating System Deployment Feature Pack does not support the primary partition on any logical drives other than drive C. There is no workaround.

Q. The primary partition on my destination computer is drive D. When I run the Image Installation CD wizard in the full operating system and start the Windows PE phase, why do I receive an error message?

A. The Operating System Deployment Feature Pack does not support the primary partition on any logical drives other than drive C. If the destination computer uses drive D as the primary partition, you can restart the computer and boot from the Image Installation CD. When you boot from the Image Installation CD, DISKPART runs to ensure that drive C is the primary partition and that the image is installed on drive C.

Q. Can I target an OS Image package to a collection that contains user accounts?

A. No. The Operating System Deployment Feature Pack supports only collections of computers as a target for an OS Image package.

Q. If I make a change to an OS Deployment Package program, do I have to update the distribution points?

A. Yes. If you modify or delete a program, you must also update the package source and distribution points by right-clicking the package entry in the SMS Administrator console and choosing All Tasks/Update Operating System Package Files and then choosing All Tasks/ Update Distribution Points.

Q. Can I use the OS Deployment Feature Pack to upgrade a computer running Windows 98 to the Windows XP operating system?

A. The Windows 98 operating system platform is supported by the OS Deployment Feature Pack for CD-based installations only. The Windows 98 operating system platform is not supported by the OS Deployment Feature Pack for OS Deployment Image Packages deployed by using an SMS advertisement.

Q. Why do I get an error (or error 1231) when I am capturing an image on the reference computer?

A. When the system is booting Windows PE, press the F8 key to run a command prompt. When the error occurs, type ipconfig /all and review the IP address information. If you do not see any IP address information, check that you have added the correct NIC drivers to your OS Image Capture CD.

Q. I accidentally ran OSDInstallWinPE.exe on my site server—what do I do?

A.

OSDInstallWinPE.exe will install Windows PE on your machine and modify the boot loader, causing your machine to start up in WinPE the next time it reboots. If you accidentally run it and it finishes successfully—that is, if the directory C:\minint\backup exists—enter the following commands at a command prompt to restore your boot record:

attrib -r -a -s -h c:\ntldr

attrib -r -a -s -h c:\ntdetect.com

del c:\ntldr

del c:\ntdetect.com

xcopy /y /h c:\minint\backup\*.* c:\

Q. Where can I find documentation about User State Migration Tool 2.6?

A. You can find documentation about User State Migration Tool 2.6 at
http://www.microsoft.com/technet/desktopdeployment/userstate/userstateusmt.mspx.

Q. Where can I find information about the Windows Pre-Installation Environment (PE)?

A. You can find detailed information about Windows PE at http://www.microsoft.com/whdc/system/winpreinst/. A version of Windows PE is included with the OS Deployment Feature Pack. If you participate in Microsoft’s Service Agreement program, you can obtain separate versions of Windows PE.

Q. Where can I find documentation about Microsoft desktop deployment solutions?

A. You can find detailed documentation about Microsoft desktop deployment solutions at
http://www.microsoft.com/technet/desktopdeployment/default.mspx.

Q. Where can I find more FAQs about SMS 2003 Operating System Deployment Feature Pack? (Updated January 31, 2005)

A. Microsoft MVP Larry A. Duncan has created a FAQ about the OS Deployment Feature Pack on his blog site at
http://msmvps.com/lduncan/articles/19685.aspx.


For More Information

Did you find this information useful? Send your suggestions and comments about the FAQ to smsdocs@microsoft.com.

 

 Top of page