All tag results for ‘WDS’
October 17th, 2008 · No Comments · 107 views
In the Active Directory domain network, you try to use Windows Deployment Services (WDS) to deploy a version of the Windows NT operating system. To make the client computer name that is automatically generated unique in the network, you configure a new computer naming policy for WDS. When you configure the new policy, you use the variable %MAC to include the network adapter media access control (MAC) address of the client computer as part of the computer name.
However, when WDS deploys the client computers during the unattended phase, the computer names that are generated for the client computers show zeros instead of the MAC addresses of the client computers. Therefore, the process fails because of duplicate computer names in the network.
May 5th, 2008 · No Comments · 128 views
May 5th, 2008 · No Comments · 200 views
Consider the following scenario:
- You are running a Windows Vista-based computer.
- You use Windows Desktop Search (WDS) or Instant Search to perform a search on some traditional Chinese characters.
In this scenario, documents that are known to contain the traditional Chinese characters are not returned in the search results.
For example, when you perform a search by using a person’s full name in WDS or in Instant Search, documents that contain the name are returned in the search results. However, when you perform a search by using the person’s first name, no documents are returned.
March 18th, 2008 · No Comments · 160 views
January 10th, 2008 · No Comments · 144 views
You upgrade a Remote Installation Service (RIS) server to use Windows Deployment Services (WDS). However, images that are based on an ACPI Uniprocessor (ACPI APIC UP) Hardware Abstraction Layer (HAL) are not available. These images are not available when you start a Pre-Boot execution (PXE) client WDS boot image on an ACPI Multiprocessor (ACPI APIC MP) computer.
This problem occurs when the multiprocessor computer is running Windows Server 2003, Windows XP, or Microsoft Windows 2000.
November 7th, 2007 · No Comments · 267 views
When trying to deploy Windows images using Windows Deployment Service (WDS), you receive an error message:
Windows cannot install required files. Make sure all files required for installation are available, and restart the installation. Error code 0X80070020.
June 19th, 2007 · No Comments · 384 views
Consider the following scenario. You try to deploy Windows Vista by using Windows Deployment Services (WDS) in an Active Domain environment. You have configured the new client naming policy for WDS. To make every client name unique, the automatic naming options apply an increasing number in every new client name. For example, you use %[0][n]# as the expression for the new client naming policy.
In this scenario, WDS cannot generate more than 255 client names. Therefore, you cannot add more than 255 machine account objects (MAO) into the domain. Users can install Windows Vista on more than 255 client computers. However, only the first 255 computers are automatically joined to the domain. Therefore, you cannot centrally manage the Windows Vista deployment for other computers.
March 6th, 2007 · No Comments · 381 views
Consider the following scenario:
- You use a Windows Deployment Services (WDS) client unattended file to try to deploy Windows Vista on a client computer.
- The Windows Vista installation fails.
In this scenario, the WDS client unattended file, WDSClientUnattend.xml, may remain on the hard disk of the client computer.
Note: The WDSClientUnattend.xml file may contain sensitive information such as domain credentials or a product key.