WDS为什么无法调用无人值守文件？

p549989914 · 发表于 2022-5-13 11:35:50

本帖最后由 p549989914 于 2022-5-13 11:38 编辑

按照教程https://www.itsk.com/thread-386144-1-1.html进行部署后其他都正常，就是弄了无人值守文件不调用出来。

以下为图片，和无人值守文件，大神们可以帮忙看看出啥问题了吗？感谢！

这里不会自动下一步，想实现这里的步骤都自动完成。

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="generalize">
<component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" 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>
<Size>300</Size>
<Type>EFI</Type>
</CreatePartition>
<CreatePartition wcm:action="add">
<Order>2</Order>
<Size>200</Size>
<Type>MSR</Type>
</CreatePartition>
<CreatePartition wcm:action="add">
<Order>3</Order>
<Type>Primary</Type>
<Extend>true</Extend>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition wcm:action="add">
<Active>true</Active>
<Extend>false</Extend>
<Format>NTFS</Format>
<Label>win10</Label>
<Letter>C</Letter>
<Order>3</Order>
<PartitionID>1</PartitionID>
</ModifyPartition>
</ModifyPartitions>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
</Disk>
<WillShowUI>OnError</WillShowUI>
</DiskConfiguration>
<WindowsDeploymentServices>
<Login>
<Credentials>
<Password>qwe123456!</Password>
<Username>domain\administrator</Username>
</Credentials>
</Login>
<ImageSelection>
<InstallImage>
<Filename>TXY.wim</Filename>
<ImageGroup>ImageGroup1</ImageGroup>
<ImageName>txy22.5.10</ImageName>
</InstallImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>3</PartitionID>
</InstallTo>
</ImageSelection>
</WindowsDeploymentServices>
<EnableFirewall>true</EnableFirewall>
<EnableNetwork>false</EnableNetwork>
<LogPath>C:\LOG</LogPath>
<Restart>Restart</Restart>
<UseConfigurationSet>true</UseConfigurationSet>>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<SystemLocale>zh-CN</SystemLocale>
<UILanguage>zh-CN</UILanguage>
<UserLocale>zh-CN</UserLocale>
</SetupUILanguage>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>%SystemDrive%\Sysprep\ES5\EsDeploy.exe /InDeploy</Path>
<Description>InDeploy</Description>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<CopyProfile>true</CopyProfile>
<RegisteredOwner>Owner</RegisteredOwner>
<RegisteredOrganization>Organization</RegisteredOrganization>
<TimeZone>China Standard Time</TimeZone>
<ComputerName>*</ComputerName>
</component>
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Identification>
<JoinWorkgroup>WorkGroup</JoinWorkgroup>
</Identification>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<CommandLine>%SystemDrive%\Sysprep\ES5\EsDeploy.exe /Logon</CommandLine>
<Description>FirstLogon</Description>
</SynchronousCommand>
</FirstLogonCommands>
<LogonCommands>
<AsynchronousCommand wcm:action="add">
<Order>1</Order>
<CommandLine>%SystemDrive%\Sysprep\ES5\EsDeploy.exe /Desktop</CommandLine>
<Description>Desktop</Description>
</AsynchronousCommand>
</LogonCommands>
<OOBE>
<NetworkLocation>Other</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<SkipMachineOOBE>false</SkipMachineOOBE>
<SkipUserOOBE>false</SkipUserOOBE>
</OOBE>
<RegisteredOwner>Owner</RegisteredOwner>
<RegisteredOrganization>Organization</RegisteredOrganization>
<TimeZone>China Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SystemLocale>zh-CN</SystemLocale>
<UILanguage>zh-CN</UILanguage>
<UserLocale>zh-CN</UserLocale>
<InputLocale>0804:00000804</InputLocale>
</component>
</settings>
</unattend>

复制代码

y283146775 · 发表于 2022-5-13 12:23:03

本帖最后由 y283146775 于 2022-5-13 13:41 编辑

你的域就叫“Domain.com”吗？

<Password>qwe123456!</Password>
<Username>domain\administrator</Username>

复制代码

domain\administrator要改成你域名SamAccountName（比如：你域名是：qq.com 那这个登录名就应该是：qq\administrator）
如果没有域环境，那就直接用【服务器名\administrator】的形式登录，比如：你WDS服务器的名称是WDS-W19，那登录名应该为：WDS-W19\administrator

p549989914 · 发表于 2022-5-13 14:45:56

y283146775 发表于 2022-5-13 12:23
你的域就叫“Domain.com”吗？

domain\administrator要改成你域名SamAccountName（比如：你域名是：qq.c ...

我没有域环境，这个账号密码我测试了手动输入可以下一步的，但是我现在是到了第一张图片的那个界面，他没有任何提示，也没有使用无人值守文件，没法自动下一步，我还是得手动点击下一步一步一步的设置

发表于 2022-5-13 16:16:16

我也是，卡在跟楼主同样的地方，进了pe后就是这界面不动了，只能一步步的手动往下走，对自应答文件彻底放弃了，网上也看了很多的教程，测试了一周，最后无奈放弃了

y283146775 · 发表于 2022-5-13 17:03:55

p549989914 发表于 2022-5-13 14:45
我没有域环境，这个账号密码我测试了手动输入可以下一步的，但是我现在是到了第一张图片的那个界面，他没 ...

只有这几种可能：
1.就是上面说的账号设置不规范
2.无人值守文件放置的位置不对，最开始配置WDS阶段默认C:\Remotelnstall这个路径，如果你将这个路径变更到其它路径了，那需要放置相对应的变更后的路径
3.体系架构不对应，你可以把所有结构的无人值守文件都配置上。

		自动登录	找回密码
密码			加入我们

[讨论] WDS为什么无法调用无人值守文件？

点评

点评

社区QQ达人