|
1. Where can I obtain my Microsoft® Windows® XP OEM Preinstallation Kit (OPK) tools and the Windows Preinstallation Environment (WinPE) CD-ROM? Are these available for download?
The OPK tools—such as Setup Manager, the System Preparation Tool (SysPrep), and WinPE—are located on a separate CD in the 3-packs and available only through Microsoft Authorized Distributors. The tools are not available for download. Please contact your nearest distributor to order Microsoft products at http://oem.microsoft.com/worldwide/500330.asp.
2. How do I get prepared for preinstallation of Windows XP? Is there a quick guide for preinstalling Windows XP?
Refer to the “Quick Guide to Preinstalling Windows XP Using the OEM Preinstallation Kit (OPK)” on the Microsoft System Builder Web site at http://oem.microsoft.com/worldwide/512505.asp.
3. I keep getting a “Cannot Authenticate to Server” error. What should I look for?
Ensure that the OPK Tools folder is shared with administrator rights. Also verify that the \\computer_name\user_name and password are correct for the technician computer. Make sure that you have connectivity to the technician computer by pinging it from the master computer using the CMD from the OPK CD in a WinPE session.
4. If I want to do a preinstallation using static Internet Protocol (IP) addresses in a workgroup and not DHCP, how do I do this? What is the syntax?
First make sure that all of the computers are in the same workgroup. Then change the technician computer to have a static address in the TCPIP configuration as:
ipconfig=169.172.0.1
subnetmask=255.255.0.0
On the master computer’s WinBOM.ini on the floppy disk, add a static address with the syntax in the [WinPE.net] section of the WinBOM.ini file add:
ipconfig=169.172.0.2
subnetmask=255.255.0.0
5. Do the Deploy.cab file tools on the Windows XP Professional retail product include the same version of Setup Manager and Sysprep as the OPK CD?
No. The Deploy.cab tools are a subset of the OPK tool set. To get the full set of OPK tools, you must purchase OEM product from your local distributor. If you would like to make a SysPrep. INF file or a file for Remote Installation Services (RIS) server, then the Setup Manager that comes with Deploy.cab is your best bet. To have OEM tools for branding and customizations, please use the OPK tools.
6. Where do I get the latest patches and fixes for Windows XP?
You can find support for preinstallation of Windows XP on the Microsoft OEM System Builder Web Site newsgroup found at http://oem.microsoft.com/worldwide/500330.asp.
OEM System Builder Support Team e-mail sbst@microsoft.com
System Builder site: http://www.microsoft.com/oem/
System Builder newsgroups: http://oem.microsoft.com/general/bbs/
Microsoft Product Support Services: http://www.microsoft.com/support/
7. Where do I get the latest patches and fixes for preinstallation of Windows XP?
Go to the Windows Update page at http://v4.windowsupdate.microsoft.com/en/default.asp.
8. I want to install applications using the Guest Account. How can I do this?
Copy and stage the application on a network server or locally, and then share the folders and make sure you add the appropriate user name and password. Because the Guest Account is not enabled by default, you will need to enable this on your technician computer.
However, we do not recommend using Guest. A better solution is to create a limited user that is used only for installations (called OPKUSER, for example) and then give that user access to install.
9. I want to copy my WinBOM.ini file to the root of the CD for preinstallation. Does this work? If so, how?
Create a custom WinPE ISO file using MKIMG (see OPK.chm on the tools CD).
Overwrite the existing WinBOM.ini file that is located in the root of the temporary folder that was created in step 1.
Recreate the image from that temporary folder using OSCDIMG –betfsboot.com –h –n temporary_folder iso_image_file.
Example:
Copy the WINPE folder from the tools CD to your hard disk.
Copy Factory.exe and Netcfg.exe from \tools\x86 to C:\WINPE.
From a command prompt, change to the C:\WINPE folder and execute MKIMG D: C:\Winpe.tmp C:\Winpe.iso.
Replace C:\Winpe.tmp\winbom.ini with the customized version.
Change back to the C:\WINPE folder and execute OSCDIMG –betfsboot.com –h –n c:\Winpe.tmp c:\Winpe.iso.
10. When I’m using Mkimg.cmd, does the drive path or fully qualified paths need to be correct?
When using Mkimg.cmd, you must use fully qualified paths such as C:\Winpe.tmp and C:\Winpe.iso rather than \Winpe.tmp and \Winpe.iso. The drive letter and colon are required as well as the absolute path. Relative paths are not allowed.
11. If I change the permissions to the folder that I’m sharing, do I need to make any changes to my WinBOM.ini file?
No, unless your effective permissions are Read or better.
12. How do I set up a Windows 2000 Server RIS and at the same time as the Windows XP installation?
You must use a Pre-boot Execution Environment (PXE)–enabled network interface card (NIC) on the remote workstation or a PXE-compliant card (which most PCI NICs are). See Microsoft Knowledge Base article ID Q242920 for a list of compliant cards.
13. How do I modify an existing image once I’ve resealed it without activating it?
Start with an original image and add your hardware in audit mode. Configure the image just the way you like it, and then reseal, image, and apply to other computers. Use SysPrep to reseal the image after you have added your custom applications and hardware. You can then use the image on multiple computers of the same configuration.
14. Can I still press CTRL+SHIFT+F3 to enter audit mode during Windows Welcome?
Yes, during the first screen of Windows Welcome where Qmark, the question mark character, appears, you can enter audit mode by pressing CTRL+SHIFT+F3. However, this does not work on any other screen after this. Click Back to return to the first screen.
15. How do I configure Setup Manager to build configuration sets that use a user name and password that is different from the user name and password that I used when I first installed the OPK?
If a different account has been set up on your technician computer to complete preinstallation (different from what was used when you first installed \OPKtools), then proceed to the \OPKtools folder, open Setupmgr.ini, and change the account name and password. This will input the proper account information into any of the new accounts you may create.
16. If DiskPart fails, can I use WipeDisk to clean the drive?
You should use WipeDisk by adding the following entries in the [DiskConfig] section of the WinBOM.ini file, where N is the partition number to be activated:
WipeDisk=Yes
SetActiveN=Yes
The [DiskConfig] section should appear as follows:
[DiskConfig]
Disk1 = First.Config
[First.Config]
WipeDisk=Yes
Size1 = *
FileSystem1 = NTFS
SetActive1 = Yes
PartitionType1 = Primary
Refer to Knowledge Base article Q310820.
17. Where do I find corporate downloads?
http://corporate.windowsupdate.microsoft.com/en/default.asp
18. How do I install the Windows Recovery Console?
http://support.microsoft.com/support/kb/articles/q216/4/17.asp
19. I would like to prepopulate the product Key number off of the Certificate of Authenticity (COA) label and preactivate Windows in my factory. How can I do this?
This has to be done on a per-machine basis. Open the Oobeinfo.ini file on the finished computer, and add the product key in the following section:
[Version]
ProductKey=Place your valid Product Key number
You must activate the product key on the finished computer immediately before you run SysPrep. The end user will not be asked for their product key. You must prepopulate the product key separately on each computer to ensure that the genuine product key and activation has taken place before you reseal and ship the computer. You will not be able to make an image of this if you preactivate.
20. I want to do a preinstallation using a 1394 FireWire/USB hard drive that I can move from computer to computer. Can I do this?
You can install your OPK tools to a FireWire/USB hard drive, create your configuration sets on this hard drive, and then remove the hard drive from the technician’s computer. Then you can connect the drive to your target computer, boot the computer using WinPE, and install your configuration set.
When you first install the OPK tools, the FireWire/USB hard drive must be connected to a computer running Windows 2000 or Windows XP.
All you need to do is modify the following line in your WinBOM.ini file:
SourceRoot=D:\opktools
(You are changing this line from whatever was there before—e.g., \\server\opktools.)
21. Can I put my logo on the splash screen at startup? If so, how do I do this?
No, you cannot brand the BIOS startup page. This is not supported. However, you can have your logo appear during Windows Welcome. This is done using the Oobeinfo.ini file created by Setup Manager.
22. How do I create a custom WinPE CD with my own set of network drivers on it?
Follow the steps outlined above for replacing the WinBOM.ini file. Please see http://oem.microsoft.com/worldwide/512502.asp. However, in step 2 (step 4 in the example), place the INF for the Network Interface Card in the C:\Winpe.tmp\i386\INF directory and the driver file(s) in the C:\Winpe.tmp\i386\System32\Drivers directory.
23. Are there localized versions of the OPK? If so, where do I obtain them?
Localized versions of the Windows XP Professional OPK are available from the OEM Distributor in your region.
24. How do I build a Windows XP–based peer-to-peer network for small businesses?
You can find more information about peer-to-peer networking at http://oem.microsoft.com/worldwide/513212.asp.
25. I had my configuration set working before, but now that I have shared the OPK tools directory it does not work. What might be the issue?
Go to the sharing properties and make sure that “Files can be changed by users” is selected. Also make sure that you do not have “Internet Firewall” enabled if working in a peer-to-peer workgroup, because this will make the two computers unable to connect with each other.
26. Why am I getting “Windows was unable to determine which Network Connection to use for Internet Access” during Windows Welcome?
The Windows XP OOBE Cannot Determine Your Network Configuration screen shows up during Windows Welcome if you have two NICs or a NIC card and a 1394 card in the computer (or onboard components).
For a resolution to this problem, see http://support.microsoft.com/support/kb/articles/q307/9/79.asp.
27. How do I capture error logging using my WinBOM.ini file?
To assist in troubleshooting errors that occur while WinPE is processing your WinBOM.ini file, you can enable error logging in your WinBOM.
Under [Factory] in your WinBOM.ini file, add the following lines:
Logfile = a:\winbom.log
Logging=Yes
LogPerf=Yes
This will create a WinBOM.log file on your floppy disk.
28. If I change my password in WinBOM.ini on the floppy disk, do I need to change the WinBOM.ini file that resides in the \cfgsets folder?
Yes. If you change the password that is used to connect to the server, you definitely should change it on your existing WinBOM.INI files as well. You easily can change it in Setupmgr.ini, and the new password will be propagated to all subsequently created configuration sets.
29. I want to preinstall Microsoft Office XP during my installation. Any samples or ideas on how to do this?
You can use Setup Manager to point to the Universal Naming Convention (UNC) path, such as \\servername\sharename, and then copy the Office XP setup.exe file to this location. Make sure you share it with a user name other than the one you are using for the configuration set, such as office installer. Then copy all of the Office XP files to your network share. In your Setup Manager configuration set in the Application Preinstall wizard page, add the network share pointing to the Office XP Setup.exe file, using /q for quiet installation.
30. The preinstallation process begins but then stops with the command prompt window open and the cursor at the D:\i386\System32> prompt. What’s happening?
Incompatible hardware. The most common cause of this problem is a NIC that is not on the Hardware Compatibility List (HCL) for Windows XP. Test for possible NIC failure by verifying that the Transmission Control Protocol/Internet Protocol (TCP/IP) has been bound to the NIC. At a command prompt, type Ipconfig /all and then press ENTER. This should list all IP configuration information. If no information is listed or an error message is displayed, then the NIC probably is not on the HCL.
http://www.microsoft.com/hcl/
31. The preinstallation process begins but then stops with the command prompt window open and the cursor at the D:\i386\System32> prompt and I have confirmed that TCP/IP is bound to the NIC. What else could be wrong?
There are several possibilities.
You have a network connectivity error.
Ensure that the computer is connected to the network and that the network cable is in working order.
The technician computer was not available.
Verify that the technician computer is working by typing ping IP_address (where IP_address is the IP address of the technician computer) at a command prompt. If you receive four replies, the technician computer is working and the NICs on both computers are configured correctly.
The UNC path in the WinBOM.ini file is not correct.
Correct the UNC path in the WinBOM.ini file.
The user account specified in the WinBOM.ini file is not valid or does not have access to the Distribution folder.
Correct the user account in the WinBOM.ini file and give the user account access to the Distribution folder.
32. I have a device that fails or I have replaced a driver and get a failure. What can I do?
The driver is not signed.
Run Sigverif.exe from a command prompt to verify that all the drivers are signed. If a device fails and its driver is not signed, replace the driver with the original and retest. If you determine that the problem is the result of a recent driver or hardware change to the system, undo that change.
For more information about the File Signature Verification tool, see article Q259283 at http://support.microsoft.com/support/kb/articles/Q259/2/83.asp.
33. How do I preinstall the Step by Step Interactive (SBSI) training program? Do I have to do this manually in audit mode or is this preinstalled automatically?
In the English version of Windows XP, SBSI is installed automatically by default. For other languages, it must be run manually using the localized CD in your OEM 3-pack from the local distributor. The Application Preinstallation page is a good place to run this if you need to install a localized version.
Form : http://www.ltcom.com/page/FAQ/WinXP%20OEM%20Preinstallation%20FAQ/ |
|