Tag Info

New answers tagged

0

I found the issue. In reviewing the log file I found that the error was 0x89a. Some googling led to this TechNet Article which solved the problem. I was specifying the DomainAdmin as DOMAIN\User and the DomainAdminDomain as FQDN so it was trying to parse the two as FQDN\DOMAIN\User. I modified the rules to use DomainAdmin=User and DomainAdminDomain=Domain


0

the unattended file will be run in the sysprep mechanics/windows installation, so no. see technet.microsoft.com/en-us/library/ee523221(v=ws.10).aspx Create an Unattend.xml file. Optionally, create an Unattend.xml file for Windows 7 by using Windows SIM or a non-Microsoft Web site. If you used a non-Microsoft Web site to create an ...


0

Look in C:\RemoteInstall\Images there will be a temp image that is not a .wim-file. Delete it and uploading images should work as usual.


0

We have resolved the problem in rather a hacky way by adding the following to the specialize section of the unattend.xml used with the WDS image: <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" ...


0

If the phones aren't performing PXE boot, you should be able to use the vendor class id DHCP option to tell them apart in the DHCP server. PXE requires the vendor class to be "PXEClient".



Top 50 recent answers are included