WDS TFTP ErrorCode: 1460
Hello there!
Can anyone explain me what this error means?
Log Name: Microsoft-Windows-Deployment-Services-Diagnostics/Admin
Source: Microsoft-Windows-Deployment-Services-Diagnostics
Date: 26.01.2010 18:49:35
Event ID: 4101
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: pc.domain.local
Description:
The Following Client failed TFTP Download:
IP: 10.1.1.51
Filename: smsboot\x86\wdsnbp.com
ErrorCode: 1460
I'm trying deploy OS using sccm, but this error is on PRE-SCCM stage...
I have test clients in the same VLAN as servers VLAN and they boot perfectly...
P.S.
Environment configuration:
Test environment:
Srv#1 Windows Server 2008 SP2 [AD DS, DHCP, DNS]
Srv#2 Windows Server 2008 SP2 [SCCM R2(MP, DP, PXE, SUP), IIS, WDS, MDT]
Client empty
All this stuff are in different LAN:
Srv#1-2: 10.1.0.0
Client : 10.1.1.0
Yes this is really error about time-out.
I use Virtual workstation and Microsoft Network monitor to see what happening insied box wile booting over network;
And here it is:
As u can see proble is on Clietn side.
Server send DHCP information, then send boot file information, then client started downloading and... oopss ErrorCode: 1460
After consulting Microsoft support service we solve problem.
Operating system deployment over a network by using WDS fails in Windows Server 2008
http://support.microsoft.com/kb/975710
In few words: our network hardware do not transmitt packets large than 1400 buytes, and after applying patch I changed size to 1024 bytes and this solve my errors.
Similar Messages
-
WDS PXE Problems on 1 model of PC only - The following Client failed TFTP Download - Error Code 1460
Hey all,
I am experiencing a problem with my WDS PXE Environment, with 1 specific model of PC's only. This is a Dell XPS machine with an Intel e1000 nic in it.
The problem is that when you PXE Boot, it starts off fine, and I reach a menu that has all of my boot images listed, but as soon as you pick one it hangs on a black screen.
From the event viewer on the server I can see the following entry:
The Following Client failed TFTP Download:
IP: 10.130.148.211
Filename: \Boot\Boot.SDI
ErrorCode: 1460
I've done some google searching and found some topics that could be related, but none of the fixes mentioned helped me. This is the one I tried:
http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/a1246f62-6a8a-482b-9323-7e02dfeab196/#52aaf6fb-9494-4327-bbc3-8afe3e78905c
The problem I had was that the link they gave to the Hotfix, doesnt actually have anyway to download the hotfix!!
http://support.microsoft.com/kb/975710
Although
I am not convinced that packet size is the problem here, more likely some network or disk controller driver issues??
No
idea at all where to go from here. It is only this one model of PC that fails, and all others work fine. If someone can point me in the right direction it would be very greatly appreciated.
I
would be happy to provide you with any additional details you may require.
Thanks,
-BenYou need to contact CSS to get this fix.
Hotfix Information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore,
if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2008 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers
and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
John | Program Manager | System Center Configuration Manager -
TFTP Timeout Error on PXE Boot
Ok this is what happened. I tried to patch a image with windows updates - It filled up my hard drive. So I canceled the process and attempted to remove the folder it created on my hard drive. I went to try pxe boot a machine and I got the
blue screen:
After this I removed the check next to pxe to uninstall WDS and I waited for it to uninstall and reboot. After that I clicked the check box next pxe so it would install everything again. I redistributed the x86 and x64 boot images but now when
I try to pxe boot a machine I get the following in event viewer:
The Following Client failed TFTP Download:
IP *.*.*.*
Filename: SMSBoot\x64\wdsnbp.com
ErrorCode: 1460
I even made added the entry in the registry to change the TFTP block size. I have no idea what to do at this point. I am running Windows Server 2008 R2 and SCCM 2012 SP1. On the client machine I am getting TFTP timeout.1460 (0x5B4) =ERROR_TIMEOUT
This operation returned because the timeout period expired.
Have you seen this KB?
Operating system deployment over a network by using WDS fails in Windows Server 2008 and in Windows Server 2008 R2
http://support.microsoft.com/kb/975710
For more information, see the following TechNet articles:
WDS TFTP Server:
http://technet.microsoft.com/en-us/library/cc753134(WS.10).aspx
(http://technet.microsoft.com/en-us/library/cc726631(WS.10).aspx)
Network Boot Programs (NBP):
http://technet.microsoft.com/en-us/library/cc753134(WS.10).aspx
(http://technet.microsoft.com/en-us/library/cc753134(WS.10).aspx)
How to Modify the BCD Store Using Bcdedit: http://technet.microsoft.com/en-us/library/cc731245(WS.10).aspx#BKMK_41
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
How to Setup Windows TFTP Server in Windows 2008 R2
Hi,
Can anyone please let me know, how to install TFTP Server in Windows 2008 R2.
I installed Windows Deployment Service to get TFTP (got this info in some forum), but I did not see TFTP Service in the Service Manager.
I am a newbie so plz let me know the steps in details.
Thanks in advance.James, WDS ships with a TFTP server as part of the suite of services that are required to boot from the network. The information you've posted above is not correct.
Hi Aaron,
Thanks for your clarification. Towards the WDS TFTP Server, we could find the following statement below:
You use the Windows Deployment Services Trivial File Transfer Protocol (TFTP) server to download the files that are needed to do a network boot using the Pre-Boot Execution Environment (PXE).
From:
WDS TFTP Server
I understand that the we could select Deployment Server and Transport Server during the WDS setup processing. However, neoraghav would like to install TFTP server from the Server Manger towards the Windows Server 2008 R2. I noticed the statement as followed:
The TFTP client is optional software, and marked as deprecated on Windows Vista® and later versions of the Windows operating system. A TFTP server is no longer provided by Microsoft for similar security issues.
From:
Trivial File Transfer Protocol (TFTP) Overview
I should make my reply as clear as possible. Sorry for confusion. :-(
Regards,
James
James Xiong
TechNet Community Support -
WDS PXE Boot "Downloading NBP File..."
Have been able to boot and install from WDS VM. Had this happen once before as well but no idea how it resolved, just started working again.
I haven't touched the server since I last used it successfully.
Today when I attempted to boot a new VM from PXE I have been stuck at "Downloading NBP file..." during the PXE boot process. After about 5 minutes it comes to a "Contacting Server (192.168.4.108)" screen where again has sat so far for
around 5 minutes.
Normal behaviour is it just boots, downloads this file in seconds and is at the Windows Setup within a few more seconds.
I've restarted the WDS services on it's server and rebooted the client multiple times, no change. Checked Logs on the WDS (Application, System) and nothing, no clue where to check specific to WDS...
What am I missing here? This is completely vanilla WDS, installed, added files from 2012 R2 disk and that's it. As said worked fine in the past, now magically not working and not the first time it's done this.Enabled all logging available.
Again, fuck MS not making copy and paste work within Hyper V console.
Have this listed followed by errors:
[WDSServer/WDSTFTP] TftpSession[0x00000026BA967730:192.168.4.101:1301] - Error: Received error from client. Code=8.
I can't find what Code=8 is meant to mean. Where is the Technet article or whatever listing the WDS TFTP error codes and their meaning? Why provide error codes if no such reference exists?
This is followed by:
[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tfptsession.cpp:1636] Expression: , Win32 Error=0x4d3
[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tfptsession.cpp:1636] Expression: , Win32 Error=0x4d3
[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tfptserver.cpp:1211] Expression: , Win32 Error=0x4d3
and eventually after some more informational entries another informational "Max retries done, killing session".
I've enabled Verbose logging but really doubt that will help and really can't be assed typing out what is entered in text on another screen on the same PC but MS can't give a way to copy and paste from.
The whole idea with WDS was just a simple way to spin up new VMs when required, without using a ISO which can cause issues if not removed with Clustered Hyper V we've found. Can't believe something that should be so simple is leaving me scratching my head
for hours. Time to look at other products that don't do this to people I think. -
Server 2012 std not able to see Domain, DC and DNS on Win SBS 2008 std Domain
Hi There
I have a HP ML 110 G5 SBS 2008 std server as my DC on my network. I recently added a HP Microserver running Server 2012 std (with no roles or features installed) to act solely as a file server for a 3rd party program as the program was not running efficiently
on the main server.
The problem I am having now is that the 2012 server keeps falling off the domain and cannot contact DNS server. I have also had to re-enable remote desktop several times. It also shows the 2012 Server as being on a private firewall profile and not on the
domain firewall profile but I suspect that this is part of the same problem.
the resulting problem that this is causing is that the local machines that need to contact an SQL database on the 2012 fileserver intermittently either time out or are very slow to connect.
So far I have tried:
Switching from Static IP to DHCP.
Re-adding the server to the domain.
Stopping and restarting DNS services on the DC.
Checking physical Network connections and routing.
Putting the 2012 server into the same Organizational Unit as the 2008 DC.
Has anyone else encountered this problem when adding a 2012 server to a 2008 domain? I have a feeling that the solution is probably something simple that I've overlooked, but I can't think what. Any help would be greatly appreciated.
Regards
Russ
Also, as some additional info -
Event viewer gives the following errors:
Group Policy Error:
Log Name: System
Source: Microsoft-Windows-GroupPolicy
Date: 2015-04-27 01:17:51 PM
Event ID: 1129
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: [SERVERNAME].[DOMAIN].local
Description:
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has
successfully processed. If you do not see a success message for several hours, then contact your administrator.
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" />
<EventID>1129</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-04-27T11:17:51.111942100Z" />
<EventRecordID>19056</EventRecordID>
<Correlation ActivityID="{C0CBAF2B-1E93-49C0-B910-069AE43F74B2}" />
<Execution ProcessID="732" ThreadID="1336" />
<Channel>System</Channel>
<Computer>[SERVERNAME].[DOMAIN].local</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SupportInfo1">1</Data>
<Data Name="SupportInfo2">1548</Data>
<Data Name="ProcessingMode">0</Data>
<Data Name="ProcessingTimeInMilliseconds">0</Data>
<Data Name="ErrorCode">1222</Data>
<Data Name="ErrorDescription">The network is not present or not started. </Data>
</EventData>
</Event>
DNS Error:
Log Name: System
Source: Microsoft-Windows-DNS-Client
Date: 2015-04-27 04:54:58 PM
Event ID: 8015
Task Category: (1028)
Level: Warning
Keywords:
User: NETWORK SERVICE
Computer: [SERVERNAME].[DOMAIN].local
Description:
The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings:
Adapter Name : {3DDD0E46-D879-48C0-9DF6-5FAC0F1A56C4}
Host Name : [SERVERNAME]
Primary Domain Suffix : [DOMAIN].local
DNS server list :
192.168.2.10
Sent update to server : <?>
IP Address(es) :
192.168.2.15
The reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running
at this time. You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" />
<EventID>8015</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>1028</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2015-04-27T14:54:58.599130300Z" />
<EventRecordID>19105</EventRecordID>
<Correlation />
<Execution ProcessID="856" ThreadID="952" />
<Channel>System</Channel>
<Computer>[SERVERNAME].[DOMAIN].local</Computer>
<Security UserID="S-1-5-20" />
</System>
<EventData>
<Data Name="AdapterName">{3DDD0E46-D879-48C0-9DF6-5FAC0F1A56C4}</Data>
<Data Name="HostName">[SERVERNAME]</Data>
<Data Name="AdapterSuffixName">[DOMAIN].local</Data>
<Data Name="DnsServerList"> 192.168.2.10</Data>
<Data Name="Sent UpdateServer"><?></Data>
<Data Name="Ipaddress">192.168.2.15</Data>
<Data Name="ErrorCode">1460</Data>
</EventData>
</Event>Can you post an ipconfig /all from the server and the DC?
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+ -
WDS PXE Uefi not working in AD integrated mode, TFTP to slow
Dear all
1 Physical host: W2k12R2, 1 Hyper-V virtual switch.
1 Hyper-V VM with W2k12R2 DC with DNS, DHCP, WDS.
1 Empty Hyper-V VM Generation 2 UEFI booting from network.
Problem: Error "PXE-E16: No offer received" on the empty Hyper-V VM when trying to Uefi boot from WDS in AD integrated mode.
I verified that it works when WDS is set-up to standalone mode. See also:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/ceca6149-bedd-4860-8a7f-a1c83bf99aa4/wds-efi-bios-wont-pxe-boot-into-efi-mode
PS: Switch to standalone mode: On the WDS server: wdsutil /verbose /uninitialize-server /server:<servername>; wdsutil /verbose /progress /initialize-server /server:<servername>
/reminst:C:\RmInst
Cause (found by Netmon IP traffic monitoring):
The Client asks for the TFTP Server on UDP port 4011.
The TFTP Server takes more than 8 seconds to reply on port 4011.
This seems to be due to NbtNs (Netbios name search) broadcast queries searching for 1C Domain Controllers.
Solution: ???????
Any help is much appreciated.
Dominique, Zürich, Switzerland.Hi Dominique, Zürich, Switzerland.,
You can also create a virtual machine to act as a client machine when building and testing your deployment images. This is especially useful for building your custom images.
Note, however, that the performance will often be degraded, particularly during the Trivial File Transfer Protocol (TFTP) download phase. This phase is very resource-intensive and may fail if insufficient resources are available on your server running Hyper-V,
could you use the physical computer then configure the same settings then monitor this issue again.
The related KB:
Windows Deployment Services Overview
https://technet.microsoft.com/en-us/library/hh831764.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Wds pxe boot - tftp download loop - 4 times F12
Hi
I just set up a new wds server 2012
When trying to pxe boot a client, it loops like this:
Downloaded WDSNBP from...
WDSNBP started using DHCP referral.
Contacting server...
Architecture...
Contacting server...
TFTP download: boot\x86\wdsnbp.com
Downloaded WDSNBP from ...
Architecture...
Contacting Server...
TFTP download: boot\x86\wdsnbp.com
Then it goes on 4 times in a row:
"TFTP Download: Boot\x86\wdsnbp.com"
With Option "Require the user to press the F12 key..." enabled,
I have to press F12 4 times, which is 3 times too many.After the x-th download of wdsnbp.com the client continues the boot process
normally and the rest works fine.
Any help is greatly appreciated.
MichaelWe are experiencing the same thing.
This started after enabling scope option 67 to solve this error: PXE-E53: No Boot filename received.
This only occurs on selected machines. We do employ IP Helpers and are thinking this could be an issue. -
Hello All,
Please I need help! I have not seen the above error without relationship to two of the known causes for sometime during a Windows 7 osd in an SCCM 2012 R2 environment with a remote DP/PXE server. I understand this error: to occur when the boot images
does not have "Network drivers in the past Winpe version ( i.e. 3.0, 4.0), not Winpe 5.0 which has all the Network and storage drivers for Windows 7" or when Port fast is not enabled on the switch port the pxe device is plugged into. These two causes
stated here have been verified and confirmed not to be the cause in this case within the environment. The PXE boot device has ip-address (verified using ip-config, diskpart as well reveals the disk is online) and can ping the wds/pxe server and the sccm server.
Port fast is enabled on the switch port the device is plugged into. I am stuck on this one; as I could not ascertain the cause on this occasion.
Please see details below and I welcome any help any body can offer, thanks in advance guys!
Client – Winpe x64
Server - Windows Server 2008 R2 configured as a PXE / WDS / SCCM DP
Network - both devices on the same subnet
Problem: Client performs PXE boot, downloads Winpe without problems. Client then tries to download .var file. This is not successful and TFTP timeout is received. Error code in
smsts.log states:
<![LOG[Executing: X:\sms\bin\x64\smstftp.exe -i PXE-Server get \SMSTemp\2014.07.01.14.09.09.0001.{46173825-3EDA-4352-8947-3549830D77A7}.boot.var X:\sms\data\variables.dat]LOG]!><time="14:13:57.285+480"
date="07-01-2014" component="TSPxe" context="" type="0" thread="376" file="tspxe.cpp:177">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="14:13:57.332+480" date="07-01-2014" component="TSPxe" context="" type="0"
thread="376" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\smstftp.exe" -i PXE-Server get \SMSTemp\2014.07.01.14.09.09.0001.{46173825-3EDA-4352-8947-3549830D77A7}.boot.var X:\sms\data\variables.dat]LOG]!><time="14:13:57.332+480"
date="07-01-2014" component="TSPxe" context="" type="0" thread="376" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\smstftp.exe" -i PXE-Server get \SMSTemp\2014.07.01.14.09.09.0001.{46173825-3EDA-4352-8947-3549830D77A7}.boot.var X:\sms\data\variables.dat]LOG]!><time="14:13:57.332+480"
date="07-01-2014" component="TSPxe" context="" type="1" thread="376" file="commandline.cpp:827">
<![LOG[Process completed with exit code 1]LOG]!><time="14:14:45.379+480" date="07-01-2014" component="TSPxe" context="" type="1" thread="376"
file="commandline.cpp:1123">
Network trace is detailed below:
324994 11:47:35 04/07/2014 166.7634594
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:320, UDP:319, IPv4:72}
325069 11:47:36 04/07/2014 167.7554047 svchost.exe Client Server
TFTP TFTP: Read Request - File: \SMSTemp\2014.07.03.15.45.31.0001.{549002A3-C9C9-4189-8AFE-9F8B272BECC1}.boot.var, Transfer Mode: octet
{UDP:321, IPv4:72}
325070 11:47:36 04/07/2014 167.7556504
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:320, UDP:319, IPv4:72}
325071 11:47:36 04/07/2014 167.7598345
Server Client TFTP TFTP: Data - Block Number: 1 {UDP:322, IPv4:72}
325072 11:47:36 04/07/2014 167.7607151
Client Server TFTP TFTP: Acknowledgement - Block Number: 1 {UDP:322, IPv4:72}
325073 11:47:36 04/07/2014 167.7608240
Server Client TFTP TFTP: Data - Block Number: 2 {UDP:322, IPv4:72}
325074 11:47:36 04/07/2014 167.7615948
Client Server TFTP TFTP: Acknowledgement - Block Number: 2 {UDP:322, IPv4:72}
325075 11:47:36 04/07/2014 167.7616991
Server Client TFTP TFTP: Data - Block Number: 3 {UDP:322, IPv4:72}
325076 11:47:36 04/07/2014 167.7624602
Client Server TFTP TFTP: Acknowledgement - Block Number: 3 {UDP:322, IPv4:72}
325077 11:47:36 04/07/2014 167.7625635
Server Client TFTP TFTP: Data - Block Number: 4 {UDP:322, IPv4:72}
325078 11:47:36 04/07/2014 167.7629426
Client Server TFTP TFTP: Acknowledgement - Block Number: 4 {UDP:322, IPv4:72}
325079 11:47:36 04/07/2014 167.7630452
Server Client TFTP TFTP: Data - Block Number: 5 {UDP:322, IPv4:72}
325080 11:47:36 04/07/2014 167.7637927
Client Server TFTP TFTP: Acknowledgement - Block Number: 5 {UDP:322, IPv4:72}
325081 11:47:36 04/07/2014 167.7638947
Server Client TFTP TFTP: Data - Block Number: 6 {UDP:322, IPv4:72}
325082 11:47:36 04/07/2014 167.7643324
Client Server TFTP TFTP: Acknowledgement - Block Number: 6 {UDP:322, IPv4:72}
325083 11:47:36 04/07/2014 167.7644367
Server Client TFTP TFTP: Data - Block Number: 7 {UDP:322, IPv4:72}
325084 11:47:36 04/07/2014 167.7652140
Client Server TFTP TFTP: Acknowledgement - Block Number: 7 {UDP:322, IPv4:72}
325085 11:47:36 04/07/2014 167.7653183
Server Client TFTP TFTP: Data - Block Number: 8 {UDP:322, IPv4:72}
325086 11:47:36 04/07/2014 167.7660907
Client Server TFTP TFTP: Acknowledgement - Block Number: 8 {UDP:322, IPv4:72}
325087 11:47:36 04/07/2014 167.7661940
Server Client TFTP TFTP: Data - Block Number: 9 {UDP:322, IPv4:72}
325088 11:47:36 04/07/2014 167.7669372
Client Server TFTP TFTP: Acknowledgement - Block Number: 9 {UDP:322, IPv4:72}
325089 11:47:36 04/07/2014 167.7670323
Server Client TFTP TFTP: Data - Block Number: 10 {UDP:322, IPv4:72}
325090 11:47:36 04/07/2014 167.7674067
Client Server TFTP TFTP: Acknowledgement - Block Number: 10 {UDP:322, IPv4:72}
325091 11:47:36 04/07/2014 167.7674809
Server Client TFTP TFTP: Data - Block Number: 11 {UDP:322, IPv4:72}
325092 11:47:36 04/07/2014 167.7681308
Client Server TFTP TFTP: Acknowledgement - Block Number: 11 {UDP:322, IPv4:72}
325093 11:47:36 04/07/2014 167.7682056
Server Client TFTP TFTP: Data - Block Number: 12 {UDP:322, IPv4:72}
325094 11:47:36 04/07/2014 167.7685383
Client Server TFTP TFTP: Acknowledgement - Block Number: 12 {UDP:322, IPv4:72}
325095 11:47:36 04/07/2014 167.7686108
Server Client TFTP TFTP: Data - Block Number: 13 {UDP:322, IPv4:72}
325096 11:47:36 04/07/2014 167.7692475
Client Server TFTP TFTP: Acknowledgement - Block Number: 13 {UDP:322, IPv4:72}
325097 11:47:36 04/07/2014 167.7693216
Server Client TFTP TFTP: Data - Block Number: 14 {UDP:322, IPv4:72}
325098 11:47:36 04/07/2014 167.7696477
Client Server TFTP TFTP: Acknowledgement - Block Number: 14 {UDP:322, IPv4:72}
325099 11:47:36 04/07/2014 167.7697202
Server Client TFTP TFTP: Data - Block Number: 15 {UDP:322, IPv4:72}
325100 11:47:36 04/07/2014 167.7703651
Client Server TFTP TFTP: Acknowledgement - Block Number: 15 {UDP:322, IPv4:72}
325101 11:47:36 04/07/2014 167.7704386
Server Client TFTP TFTP: Data - Block Number: 16 {UDP:322, IPv4:72}
325102 11:47:36 04/07/2014 167.7707479
Client Server TFTP TFTP: Acknowledgement - Block Number: 16 {UDP:322, IPv4:72}
325103 11:47:36 04/07/2014 167.7708214
Server Client TFTP TFTP: Data - Block Number: 17 {UDP:322, IPv4:72}
325104 11:47:36 04/07/2014 167.7714862
Client Server TFTP TFTP: Acknowledgement - Block Number: 17 {UDP:322, IPv4:72}
325105 11:47:36 04/07/2014 167.7715603
Server Client TFTP TFTP: Data - Block Number: 18 {UDP:322, IPv4:72}
325106 11:47:36 04/07/2014 167.7718715
Client Server TFTP TFTP: Acknowledgement - Block Number: 18 {UDP:322, IPv4:72}
325107 11:47:36 04/07/2014 167.7719450
Server Client TFTP TFTP: Data - Block Number: 19 {UDP:322, IPv4:72}
325108 11:47:36 04/07/2014 167.7726029
Client Server TFTP TFTP: Acknowledgement - Block Number: 19 {UDP:322, IPv4:72}
325109 11:47:36 04/07/2014 167.7726800
Server Client TFTP TFTP: Data - Block Number: 20 {UDP:322, IPv4:72}
325110 11:47:36 04/07/2014 167.7733471
Client Server TFTP TFTP: Acknowledgement - Block Number: 20 {UDP:322, IPv4:72}
325111 11:47:36 04/07/2014 167.7734203
Server Client TFTP TFTP: Data - Block Number: 21 {UDP:322, IPv4:72}
325112 11:47:36 04/07/2014 167.7737411
Client Server TFTP TFTP: Acknowledgement - Block Number: 21 {UDP:322, IPv4:72}
325113 11:47:36 04/07/2014 167.7738142
Server Client TFTP TFTP: Data - Block Number: 22 {UDP:322, IPv4:72}
325114 11:47:36 04/07/2014 167.7744648
Client Server TFTP TFTP: Acknowledgement - Block Number: 22 {UDP:322, IPv4:72}
325115 11:47:36 04/07/2014 167.7745386
Server Client TFTP TFTP: Data - Block Number: 23 {UDP:322, IPv4:72}
325116 11:47:36 04/07/2014 167.7748657
Client Server TFTP TFTP: Acknowledgement - Block Number: 23 {UDP:322, IPv4:72}
325117 11:47:36 04/07/2014 167.7749395
Server Client TFTP TFTP: Data - Block Number: 24 {UDP:322, IPv4:72}
325118 11:47:36 04/07/2014 167.7755914
Client Server TFTP TFTP: Acknowledgement - Block Number: 24 {UDP:322, IPv4:72}
325119 11:47:36 04/07/2014 167.7756649
Server Client TFTP TFTP: Data - Block Number: 25 {UDP:322, IPv4:72}
325120 11:47:36 04/07/2014 167.7760109
Client Server TFTP TFTP: Acknowledgement - Block Number: 25 {UDP:322, IPv4:72}
325277 11:47:37 04/07/2014 168.7554246
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:320, UDP:319, IPv4:72}
325278 11:47:37 04/07/2014 168.7709396
Client Server TFTP TFTP: Acknowledgement - Block Number: 25 {UDP:322, IPv4:72}
325397 11:47:39 04/07/2014 170.7708892
Client Server TFTP TFTP: Acknowledgement - Block Number: 25 {UDP:322, IPv4:72}
326185 11:47:40 04/07/2014 171.7552905
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:320, UDP:319, IPv4:72}
327030 11:47:43 04/07/2014 174.7588879
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
327031 11:47:43 04/07/2014 174.7707730
Client Server TFTP TFTP: Acknowledgement - Block Number: 25 {UDP:322, IPv4:72}
327178 11:47:44 04/07/2014 175.7552028
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
327510 11:47:45 04/07/2014 176.7551962
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
328598 11:47:48 04/07/2014 179.7552497
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
328630 11:47:51 04/07/2014 182.7551309
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
328631 11:47:51 04/07/2014 182.7707620
Client Server TFTP TFTP: Acknowledgement - Block Number: 25 {UDP:322, IPv4:72}
328658 11:47:54 04/07/2014 185.7550375
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
328669 11:47:57 04/07/2014 188.7709719
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
328677 11:47:59 04/07/2014 190.7862445
Client Server TFTP TFTP: Acknowledgement - Block Number: 25 {UDP:322, IPv4:72}
328690 11:48:00 04/07/2014 191.7708666
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
328717 11:48:03 04/07/2014 194.7706918
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
328730 11:48:06 04/07/2014 197.7704623
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
328736 11:48:07 04/07/2014 198.7861669
Client Server TFTP TFTP: Acknowledgement - Block Number: 25 {UDP:322, IPv4:72}
329217 11:48:09 04/07/2014 200.7705229
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
329420 11:48:12 04/07/2014 203.7704633
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
329795 11:48:15 04/07/2014 206.7704298
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
329796 11:48:15 04/07/2014 206.7858646
Client Server TFTP TFTP: Acknowledgement - Block Number: 25 {UDP:322, IPv4:72}
329990 11:48:18 04/07/2014 209.7704360
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
330005 11:48:21 04/07/2014 212.7703291
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440 {AuthIP:419, UDP:319, IPv4:72}
330014 11:48:23 04/07/2014 214.7862410
Client Server TFTP TFTP: Error - ErrorCode: 0, ErrorMessage: timeout on receive {UDP:322, IPv4:72}Hi,
According to the logs, this issue still should be related to network driver. It failed after network driver initialized. Please try to use another network driver.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
WDS 2012 R2 - Cannot PXE multiple clients at the same time
Hello All,
This is my first post on here so I apologize if this is the wrong place. I work for a school district and we are implementing WDS 2012 R2. We've been extremely satisfied with the speeds and ease of use through unattend files. However, for
the past month I've been looking for a possible answer to a problem that has plagued us from day one of implementation.
So here's the problem:
I have a stand alone WDS server which is not a domain controller and is not our DHCP server. I have IP helpers and broadcast forwarders setup on the network. As well as option 66 and 67 in DHCP. So far so good right!
Well that's partially right. When we boot one client at a time to the WDS server. Everything works as intended. We can TFTP the necessary files from the WDS server. Everything boots up and we're off and running.
However, if we boot up two or more clients at the same time. The WDS server never responds to the traffic. The clients get their DHCP information. They start the referral and download from the WDS server, but get no response. I'm
really hoping that someone on here would have some insight of something I can try. I've about exhausted my list of peers and contacts. They're all stumped as well and were smart enough to stay with 2008 WDS.
I would prefer to stick with 2012 R2 since it's setup and working for the most part. With only this one hiccup.
Thanks in advance for any guidance!Hello Daniel,
I appreciate the reply and apologize for taking so long to get back to this. Things have been a little hectic over here.
I have tried everything on this forum and I am still unsuccessful in PXE booting multiple clients at the same time.
Multicast is enabled on the server, and it works for the clients. However, as stated in the original post. I cannot boot multiple machines at the same time. I can start them from the image selection screen around the same time though. So,
that appears to be working fine. -
SCCM 2012 R2 - No Response from WDS server
We upgraded our SCCM 2012 sp1 servers to R2 and have we are now receiving the following error on our remote PXE enabled DP;
Have performed the usual processes;
Removed the PXE enabled DP
Uninstalled the WDS service
Rebooted server
Deployed the PXE-DP from the site server (letting the site server also install WDS)
Checked the WDS service start OK
Distributed the Boot images to the PXE-DP
Checked the content status has succeeded
Checked that the PXE booting clients are looking at the correct server IP
Checked the smsdpprov.log:
[AC8][Wed 03/19/2014 15:04:50]:Registry key creation successfull
[AC8][Wed 03/19/2014 15:04:51]:CSMSDPInstProv::RegisterDPHealthMonTask: Schedule is '00011700001F2000'
[AC8][Wed 03/19/2014 15:04:51]:1998-01-01T00:00:00Z
[AC8][Wed 03/19/2014 15:04:54]:A DP health monitoring task has been registered successfully
[AC8][Wed 03/19/2014 15:04:54]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[AC8][Wed 03/19/2014 15:04:59]:Failed to enable IIS logging for DP usage task. Error code: 0x80041013
[AC8][Wed 03/19/2014 15:05:00]:CcmInstallPXE
[AC8][Wed 03/19/2014 15:05:00]:RegQueryValueExW failed for Software\Microsoft\SMS\DP, PxeInstalled
[AC8][Wed 03/19/2014 15:05:00]:RegReadDWord failed; 0x80070002
[AC8][Wed 03/19/2014 15:05:00]:Running: C:\SMS_DP$\sms\bin\vcredist_x64.exe /q /log "C:\SMS_DP$\sms\bin\vcredist.log"
[AC8][Wed 03/19/2014 15:05:00]:Waiting for the completion of: C:\SMS_DP$\sms\bin\vcredist_x64.exe /q /log "C:\SMS_DP$\sms\bin\vcredist.log"
[AC8][Wed 03/19/2014 15:05:10]:Run completed for: C:\SMS_DP$\sms\bin\vcredist_x64.exe /q /log "C:\SMS_DP$\sms\bin\vcredist.log"
[AC8][Wed 03/19/2014 15:05:10]:Created the DP mutex key for WDS.
[AC8][Wed 03/19/2014 15:05:10]:Finding Wimgapi.Dll
[AC8][Wed 03/19/2014 15:05:10]:MsiEnumRelatedProducts failed
[AC8][Wed 03/19/2014 15:05:10]:FindProduct failed; 0x80070103
[AC8][Wed 03/19/2014 15:05:10]:MsiEnumRelatedProducts failed
[AC8][Wed 03/19/2014 15:05:10]:FindProduct failed; 0x80070103
[AC8][Wed 03/19/2014 15:05:10]:Found C:\Windows\system32\wimgapi.dll
[AC8][Wed 03/19/2014 15:05:10]:Wimgapi.dll is already installed.
[AC8][Wed 03/19/2014 15:05:10]:Path to smsdp.dll is 'C:\SMS_DP$\sms\bin\smsdp.dll'
[AC8][Wed 03/19/2014 15:05:10]:PXE performance counters have been initialized
[AC8][Wed 03/19/2014 15:05:10]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
[AC8][Wed 03/19/2014 15:05:10]:WDS is INSTALLED
[AC8][Wed 03/19/2014 15:05:10]:WDS service is already installed.
[AC8][Wed 03/19/2014 15:05:10]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
[AC8][Wed 03/19/2014 15:05:10]:WDS is INSTALLED
[AC8][Wed 03/19/2014 15:05:10]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
[AC8][Wed 03/19/2014 15:05:10]:Setting TFTP config key as: System\CurrentControlSet\Services\WDSSERVER\Providers\WDSTFTP
[AC8][Wed 03/19/2014 15:05:10]:Configuring TFTP read filters
[AC8][Wed 03/19/2014 15:05:10]:SetupComplete is set to 0
[AC8][Wed 03/19/2014 15:05:10]:RegQueryValueExW failed for Software\Microsoft\Windows\CurrentVersion\Setup, REMINST
[AC8][Wed 03/19/2014 15:05:10]:RegReadDWord failed; 0x80070002
[AC8][Wed 03/19/2014 15:05:10]:REMINST not set in WDS
[AC8][Wed 03/19/2014 15:05:10]:WDS is NOT Configured
[AC8][Wed 03/19/2014 15:05:10]:Share (REMINST) does not exist. (NetNameNotFound) (0x00000906)
[AC8][Wed 03/19/2014 15:05:10]:GetFileSharePath failed; 0x80070906
[AC8][Wed 03/19/2014 15:05:10]:REMINST share does not exist. Need to create it.
[AC8][Wed 03/19/2014 15:05:10]:Enumerating drives A through Z for the NTFS drive with the most free space.
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: A:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: B:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: C:\
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: D:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: E:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: F:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: G:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: H:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: I:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: J:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: K:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: L:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: M:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: N:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: O:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: P:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: Q:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: R:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: S:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: T:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: U:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: V:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: W:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: X:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: Y:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: Z:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Drive 'C:\' is the best drive for the SMS installation directory.
[AC8][Wed 03/19/2014 15:05:10]:Creating REMINST share to point to: C:\RemoteInstall
[AC8][Wed 03/19/2014 15:05:10]:Succesfully created share REMINST
[AC8][Wed 03/19/2014 15:05:10]:Removing existing PXE related directories
[AC8][Wed 03/19/2014 15:05:10]:Registering WDS provider: SourceDir: C:\SMS_DP$\sms\bin
[AC8][Wed 03/19/2014 15:05:10]:Registering WDS provider: ProviderPath: C:\SMS_DP$\sms\bin\smspxe.dll
[AC8][Wed 03/19/2014 15:05:10]:DoPxeProviderRegister
[AC8][Wed 03/19/2014 15:05:10]:PxeLoadWdsPxe
[AC8][Wed 03/19/2014 15:05:10]:Loading wdspxe.dll from C:\Windows\system32\wdspxe.dll
[AC8][Wed 03/19/2014 15:05:10]:wdspxe.dll is loaded
[AC8][Wed 03/19/2014 15:05:10]:PxeProviderRegister has suceeded (0x00000000)
[AC8][Wed 03/19/2014 15:05:10]:Disabling WDS/RIS functionality
[AC8][Wed 03/19/2014 15:05:10]:PxeProviderUnRegister
[AC8][Wed 03/19/2014 15:05:10]:
[AC8][Wed 03/19/2014 15:05:10]:Found privilege otifyPrivilege on service WDSServer
[AC8][Wed 03/19/2014 15:05:10]:Found privilege SeRestorePrivilege on service WDSServer
[AC8][Wed 03/19/2014 15:05:10]:Found privilege SeBackupPrivilege on service WDSServer
[AC8][Wed 03/19/2014 15:05:10]:Found privilege SeSecurityPrivilege on service WDSServer
[AC8][Wed 03/19/2014 15:05:10]:Privilege SeTakeOwnershipPrivilege NOT found service WDSServer
[AC8][Wed 03/19/2014 15:05:11]:ChangeServiceConfig2 succeeded for WDSServer. Added privilege SeTakeOwnershipPrivilege
[AC8][Wed 03/19/2014 15:05:11]:ChangeServiceConfig succeeded for WDSServer. StartType: 0x2
[AC8][Wed 03/19/2014 15:05:24]:WDSServer status is 4
[AC8][Wed 03/19/2014 15:05:24]:WDSServer is STARTED
[AC8][Wed 03/19/2014 15:05:24]:Running: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall"
[AC8][Wed 03/19/2014 15:05:25]:Waiting for the completion of: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall"
[AC8][Wed 03/19/2014 15:05:27]:Run completed for: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall"
[AC8][Wed 03/19/2014 15:05:27]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
[AC8][Wed 03/19/2014 15:05:27]:No need to configure the firewall
[AC8][Wed 03/19/2014 15:05:27]:CContentDefinition::GetAllPackagesFromLib failed; 0x80070003
[AC8][Wed 03/19/2014 15:05:27]:ProcessBootImages failed; 0x80070003
[AC8][Wed 03/19/2014 15:05:27]:CcmInstallPXE: Deleting the DP mutex key for WDS.
[AC8][Wed 03/19/2014 15:05:27]:Installed PXE
[AC8][Wed 03/19/2014 15:05:27]:Registry key creation successfull
[D48][Wed 03/19/2014 15:08:12]:Registry key creation successfull
[D48][Wed 03/19/2014 15:08:13]:Registry key creation successfull
[D48][Wed 03/19/2014 15:08:13]:Registry key creation successfull
[D48][Wed 03/19/2014 15:08:14]:Registry key creation successfull
[F20][Wed 03/19/2014 15:08:26]:CcmInstallPXE
[F20][Wed 03/19/2014 15:08:26]:PXE provider is already installed.
[F20][Wed 03/19/2014 15:08:26]:Installed PXE
[F20][Wed 03/19/2014 15:08:26]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[F20][Wed 03/19/2014 15:08:26]:1998-01-01T00:00:00
[F20][Wed 03/19/2014 15:08:27]:A DP usage gathering task has been registered successfully
[BB8][Wed 03/19/2014 15:10:59]:Content 'ASC0000E.8' for package 'ASC0000E' has been added to content library successfully
[BB8][Wed 03/19/2014 15:10:59]:Expanding C:\SCCMContentLib\FileLib\24E7\24E71E7B8DBA522A60756D1C2329EE616A364DAB121FFB7A7117D30D4F77A0EC from package ASC0000E
[BB8][Wed 03/19/2014 15:10:59]:Finding Wimgapi.Dll
[BB8][Wed 03/19/2014 15:10:59]:MsiEnumRelatedProducts failed
[BB8][Wed 03/19/2014 15:10:59]:FindProduct failed; 0x80070103
[BB8][Wed 03/19/2014 15:10:59]:MsiEnumRelatedProducts failed
[BB8][Wed 03/19/2014 15:10:59]:FindProduct failed; 0x80070103
[BB8][Wed 03/19/2014 15:10:59]:Found C:\Windows\system32\wimgapi.dll
[F20][Wed 03/19/2014 15:10:59]:Content 'ASC0000A.7' for package 'ASC0000A' has been added to content library successfully
[BB8][Wed 03/19/2014 15:10:59]:SetNamedSecurityInfo() failed.
[BB8][Wed 03/19/2014 15:10:59]:SetObjectOwner() failed. 0x80070003.
[BB8][Wed 03/19/2014 15:10:59]:SetFileSecurity() failed.
[BB8][Wed 03/19/2014 15:10:59]:Expanding ASC0000E to C:\RemoteInstall\SMSImages
[F20][Wed 03/19/2014 15:11:00]:Successfully expanded package ASC0000A to
\\ASC-DP1.LTCHARITY.ORG.UK\SMSPKGC$\ASC0000A
[F20][Wed 03/19/2014 15:11:00]:Waiting for another PXE operation thread to finish.
[F20][Wed 03/19/2014 15:11:05]:Finished waiting.
[F20][Wed 03/19/2014 15:11:11]:Expanding C:\SCCMContentLib\FileLib\DD54\DD5448253B423537C13072C96F3659FF0D1D51FDA5102BC7A68E4949269A0CA5 from package ASC0000A
[F20][Wed 03/19/2014 15:11:13]:Finding Wimgapi.Dll
[F20][Wed 03/19/2014 15:11:13]:MsiEnumRelatedProducts failed
[F20][Wed 03/19/2014 15:11:13]:FindProduct failed; 0x80070103
[F20][Wed 03/19/2014 15:11:13]:MsiEnumRelatedProducts failed
[F20][Wed 03/19/2014 15:11:13]:FindProduct failed; 0x80070103
[F20][Wed 03/19/2014 15:11:13]:Found C:\Windows\system32\wimgapi.dll
[F20][Wed 03/19/2014 15:11:19]:SetNamedSecurityInfo() failed.
[F20][Wed 03/19/2014 15:11:21]:SetObjectOwner() failed. 0x80070002.
[F20][Wed 03/19/2014 15:11:21]:SetFileSecurity() failed.
[BB8][Wed 03/19/2014 15:11:44]:Waiting for another PXE operation thread to finish.
[F20][Wed 03/19/2014 15:11:44]:Expanding ASC0000A to C:\RemoteInstall\SMSImages
[BB8][Wed 03/19/2014 15:11:49]:Finished waiting.
[BB8][Wed 03/19/2014 15:11:49]:CcmInstallPXE
[BB8][Wed 03/19/2014 15:11:49]:PXE provider is already installed.
[BB8][Wed 03/19/2014 15:11:49]:Installed PXE
[BB8][Wed 03/19/2014 15:11:49]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[BB8][Wed 03/19/2014 15:11:54]:1998-01-01T00:00:00
[BB8][Wed 03/19/2014 15:11:57]:A DP usage gathering task has been registered successfully
[BB8][Wed 03/19/2014 15:12:22]:Content 'ASC00003.4' for package 'ASC00003' has been added to content library successfully
[F20][Wed 03/19/2014 15:13:08]:CcmInstallPXE
[F20][Wed 03/19/2014 15:13:08]:PXE provider is already installed.
[F20][Wed 03/19/2014 15:13:08]:Installed PXE
[E7C][Wed 03/19/2014 15:13:08]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[E7C][Wed 03/19/2014 15:13:10]:1998-01-01T00:00:00
[E7C][Wed 03/19/2014 15:13:10]:A DP usage gathering task has been registered successfully
[F20][Wed 03/19/2014 15:13:33]:Content 'ASC00027.7' for package 'ASC00027' has been added to content library successfully
[F20][Wed 03/19/2014 15:13:33]:Expanding C:\SCCMContentLib\FileLib\4681\4681E1F7B35C465F8ADF176C71B2B4CCDA890F2857796DC81EA83B6FC05DBDC3 from package ASC00027
[F20][Wed 03/19/2014 15:13:33]:Finding Wimgapi.Dll
[F20][Wed 03/19/2014 15:13:33]:MsiEnumRelatedProducts failed
[F20][Wed 03/19/2014 15:13:33]:FindProduct failed; 0x80070103
[F20][Wed 03/19/2014 15:13:33]:MsiEnumRelatedProducts failed
[F20][Wed 03/19/2014 15:13:33]:FindProduct failed; 0x80070103
[F20][Wed 03/19/2014 15:13:33]:Found C:\Windows\system32\wimgapi.dll
[F20][Wed 03/19/2014 15:13:33]:SetNamedSecurityInfo() failed.
[F20][Wed 03/19/2014 15:13:33]:SetObjectOwner() failed. 0x80070002.
[F20][Wed 03/19/2014 15:13:33]:SetFileSecurity() failed.
[F20][Wed 03/19/2014 15:13:33]:Expanding ASC00027 to C:\RemoteInstall\SMSImages
[AF4][Wed 03/19/2014 15:14:03]:Waiting for another PXE operation thread to finish.
[AF4][Wed 03/19/2014 15:14:08]:Finished waiting.
[AF4][Wed 03/19/2014 15:14:08]:CcmInstallPXE
[AF4][Wed 03/19/2014 15:14:10]:PXE provider is already installed.
[AF4][Wed 03/19/2014 15:14:10]:Installed PXE
[AF4][Wed 03/19/2014 15:14:10]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[AF4][Wed 03/19/2014 15:14:19]:1998-01-01T00:00:00
[AF4][Wed 03/19/2014 15:14:22]:A DP usage gathering task has been registered successfully
[F20][Wed 03/19/2014 15:15:13]:Content 'ASC00002.4' for package 'ASC00002' has been added to content library successfully
[A9C][Wed 03/19/2014 15:15:56]:CcmInstallPXE
[A9C][Wed 03/19/2014 15:15:56]:PXE provider is already installed.
[A9C][Wed 03/19/2014 15:15:56]:Installed PXE
[A9C][Wed 03/19/2014 15:15:57]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[A9C][Wed 03/19/2014 15:15:57]:1998-01-01T00:00:00
[A9C][Wed 03/19/2014 15:15:58]:A DP usage gathering task has been registered successfully
================================================================================
Checked the SMSPXE.log:
<![LOG[================= PXE Provider loaded. =====================]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:137">
<![LOG[Machine is running Windows Longhorn. (NTVersion=0X601, ServicePack=1)]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="provsettings.cpp:1112">
<![LOG[Cannot read the registry value of MACIgnoreListFile (00000000)]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="provsettings.cpp:353">
<![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="provsettings.cpp:468">
<![LOG[Begin validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context=""
type="1" thread="2720" file="ccmcert.cpp:1662">
<![LOG[Completed validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context=""
type="1" thread="2720" file="ccmcert.cpp:1803">
<![LOG[Initializing PXEPerfObject.]LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:399">
<![LOG[Could not load logging configuration for component ccmperf. Using default values.]LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context="" type="2" thread="2720"
file="stdlogging.cpp:480">
<![LOG[Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown.]LOG]!><time="15:05:24.414+00" date="03-19-2014" component="SMSPXE" context="" type="1"
thread="2720" file="ccmutillib.cpp:373">
<![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
]LOG]!><time="15:05:24.742+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="libsmsmessaging.cpp:6346">
<![LOG[PXE::CBootImageInfo::CBootImageInfo: key=]LOG]!><time="15:05:24.742+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="bootimagecache.cpp:60">
<![LOG[PXE::CBootImageInfo::CBootImageInfo: key=]LOG]!><time="15:05:24.742+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="bootimagecache.cpp:60">
<![LOG[CContentDefinition::GetAllPackagesFromLib failed; 0x80070003]LOG]!><time="15:05:24.836+00" date="03-19-2014" component="SMSPXE" context="" type="3" thread="2720" file="contentlibrary.cpp:925">
<![LOG[Begin validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:24.851+00" date="03-19-2014" component="SMSPXE" context=""
type="1" thread="2720" file="ccmcert.cpp:1662">
<![LOG[Completed validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:24.851+00" date="03-19-2014" component="SMSPXE" context=""
type="1" thread="2720" file="ccmcert.cpp:1803">
<![LOG[PXE Provider finished loading.]LOG]!><time="15:05:24.851+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:184">
<![LOG[Cannot read the registry value of MACIgnoreListFile (800703e5)]LOG]!><time="15:05:29.048+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2700" file="provsettings.cpp:353">
<![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="15:05:29.048+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2700" file="provsettings.cpp:468">
<![LOG[Cannot read the registry value of MACIgnoreListFile (800703e5)]LOG]!><time="15:06:04.490+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="1408" file="provsettings.cpp:353">
<![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="15:06:04.490+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="1408" file="provsettings.cpp:468">
<![LOG[================= PXE Provider shutdown. =====================]LOG]!><time="15:06:39.371+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:223">
==============================================================================
Have we missed something in these logs?
Can anyone help with this issue please?Have you distributed both boot images (x86 and x64) to the PXE-enabled DP?
Torsten Meringer | http://www.mssccmfaq.de -
PXE T01 file not found PXE E3B TFTP Error file not found error
Hi,
I was trying to deploy OS through SCCM . i have made DHCP server and SCCM PC one PCst when i am trying to boot from client to DHCP by f12 i am getting following error. so that i have been completed following steps
TFTP
PXE-T01: File not found
PXE:E3B: TFTP Error- File not found
1)Removed WDS service and reconfigured
2)PXE role removed and re assigned
3)renamed temp folder
4)DP updated
suppose if i am trying to access the port throgh telnet
i am getting
C:\Documents and Settings\Administrator>telnet 192.168.1.65 60
Connecting To 192.168.1.65...Could not open connection to the host, on port 60:
Connect failed
C:\Documents and Settings\Administrator>telnet 192.168.1.65 67
Connecting To 192.168.1.65...Could not open connection to the host, on port 67:
Connect failed
C:\Documents and Settings\Administrator>telnet 192.168.1.65 66
Connecting To 192.168.1.65...Could not open connection to the host, on port 66:
Connect failed
C:\Documents and Settings\Administrator>telnet 192.168.1.65 65
Connecting To 192.168.1.65...Could not open connection to the host, on port 65:
Connect failed
SCCM PXEsetup.log
====================================================================
<05-17-2011 22:02:14> SMSPXE Setup Started....
<05-17-2011 22:02:14> Parameters: C:\PROGRA~1\MICROS~4\bin\i386\ROLESE~1.EXE /install /siteserver:DRDO-QQLUVGDI0P SMSPXE
<05-17-2011 22:02:14> Installing Pre Reqs for SMSPXE
<05-17-2011 22:02:14> ======== Installing Pre Reqs for Role SMSPXE ========
<05-17-2011 22:02:14> Found 2 Pre Reqs for Role SMSPXE
<05-17-2011 22:02:14> Pre Req MSXML60 found.
<05-17-2011 22:02:14> MSXML60 already installed (Product Code: {A43BF6A5-D5F0-4AAA-BF41-65995063EC44}). Would not install again.
<05-17-2011 22:02:14> Pre Req MSXML60 is already installed. Skipping it.
<05-17-2011 22:02:14> Pre Req Wimgapi found.
<05-17-2011 22:02:14> Wimgapi already installed (Product Code: {721ABC3B-5F12-4332-9C0C-C11424EF666C}). Would not install again.
<05-17-2011 22:02:14> Pre Req Wimgapi is already installed. Skipping it.
<05-17-2011 22:02:14> ======== Completed Installion of Pre Reqs for Role SMSPXE ========
<05-17-2011 22:02:14> Installing the SMSPXE
<05-17-2011 22:02:14> Machine is running Windows 2003 SP1 or later. (NTVersion=0X502, ServicePack=2)
<05-17-2011 22:02:14> Error - WDS is not installed. Installation cannot continue
<05-17-2011 23:02:35> ====================================================================
<05-17-2011 23:02:35> SMSPXE Setup Started....
<05-17-2011 23:02:35> Parameters: C:\PROGRA~1\MICROS~4\bin\i386\ROLESE~1.EXE /install /siteserver:DRDO-QQLUVGDI0P SMSPXE
<05-17-2011 23:02:35> Installing Pre Reqs for SMSPXE
<05-17-2011 23:02:35> ======== Installing Pre Reqs for Role SMSPXE ========
<05-17-2011 23:02:35> Found 2 Pre Reqs for Role SMSPXE
<05-17-2011 23:02:35> Pre Req MSXML60 found.
<05-17-2011 23:02:35> MSXML60 already installed (Product Code: {A43BF6A5-D5F0-4AAA-BF41-65995063EC44}). Would not install again.
<05-17-2011 23:02:35> Pre Req MSXML60 is already installed. Skipping it.
<05-17-2011 23:02:35> Pre Req Wimgapi found.
<05-17-2011 23:02:35> Wimgapi already installed (Product Code: {721ABC3B-5F12-4332-9C0C-C11424EF666C}). Would not install again.
<05-17-2011 23:02:35> Pre Req Wimgapi is already installed. Skipping it.
<05-17-2011 23:02:35> ======== Completed Installion of Pre Reqs for Role SMSPXE ========
<05-17-2011 23:02:35> Installing the SMSPXE
<05-17-2011 23:02:35> Machine is running Windows 2003 SP1 or later. (NTVersion=0X502, ServicePack=2)
<05-17-2011 23:02:35> Error - WDS is not installed. Installation cannot continue
<05-17-2011 23:38:26> ====================================================================
<05-17-2011 23:38:26> SMSPXE Setup Started....
<05-17-2011 23:38:26> Parameters: C:\PROGRA~1\MICROS~4\bin\i386\ROLESE~1.EXE /install /siteserver:DRDO-QQLUVGDI0P SMSPXE
<05-17-2011 23:38:26> Installing Pre Reqs for SMSPXE
<05-17-2011 23:38:26> ======== Installing Pre Reqs for Role SMSPXE ========
<05-17-2011 23:38:26> Found 2 Pre Reqs for Role SMSPXE
<05-17-2011 23:38:26> Pre Req MSXML60 found.
<05-17-2011 23:38:26> MSXML60 already installed (Product Code: {A43BF6A5-D5F0-4AAA-BF41-65995063EC44}). Would not install again.
<05-17-2011 23:38:26> Pre Req MSXML60 is already installed. Skipping it.
<05-17-2011 23:38:26> Pre Req Wimgapi found.
<05-17-2011 23:38:26> Wimgapi already installed (Product Code: {721ABC3B-5F12-4332-9C0C-C11424EF666C}). Would not install again.
<05-17-2011 23:38:26> Pre Req Wimgapi is already installed. Skipping it.
<05-17-2011 23:38:26> ======== Completed Installion of Pre Reqs for Role SMSPXE ========
<05-17-2011 23:38:26> Installing the SMSPXE
<05-17-2011 23:38:26> Machine is running Windows 2003 SP1 or later. (NTVersion=0X502, ServicePack=2)
<05-17-2011 23:38:26> WDS Service is installed.
<05-17-2011 23:38:26> No versions of SMSPXE are installed. Installing new SMSPXE.
<05-17-2011 23:38:26> Enabling MSI logging. pxe.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\pxeMSI.log
<05-17-2011 23:38:26> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\pxe.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" PXEENABLELOGGING=TRUE PXELOGLEVEL=1 PXELOGMAXSIZE=1000000 PXELOGMAXHISTORY=1
<05-17-2011 23:39:47> pxe.msi exited with return code: 0
<05-17-2011 23:39:47> Installation was successful.
<05-18-2011 22:20:04> ====================================================================
<05-18-2011 22:20:04> SMSPXE Setup Started....
<05-18-2011 22:20:04> Parameters: C:\PROGRA~1\MICROS~4\bin\i386\ROLESE~1.EXE /deinstall /siteserver:DRDO-QQLUVGDI0P SMSPXE
<05-18-2011 22:20:04> Deinstalling the SMSPXE
<05-18-2011 22:20:04> Enabling MSI logging. pxe.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\pxeMSI.log
<05-18-2011 22:20:04> Deinstalling SMSPXE, with product code {C63C1FBD-C9C8-469D-8ADE-12387FB5EA75}
<05-18-2011 22:20:15> SMSPXE deinstall exited with return code: 0
<05-18-2011 22:20:15> Deinstallation was successful.
<05-18-2011 22:20:15> Removing PXE Registry.
<05-18-2011 22:23:18> ====================================================================
<05-18-2011 22:23:18> SMSPXE Setup Started....
<05-18-2011 22:23:18> Parameters: C:\PROGRA~1\MICROS~4\bin\i386\ROLESE~1.EXE /install /siteserver:DRDO-QQLUVGDI0P SMSPXE
<05-18-2011 22:23:18> Installing Pre Reqs for SMSPXE
<05-18-2011 22:23:18> ======== Installing Pre Reqs for Role SMSPXE ========
<05-18-2011 22:23:18> Found 2 Pre Reqs for Role SMSPXE
<05-18-2011 22:23:18> Pre Req MSXML60 found.
<05-18-2011 22:23:18> MSXML60 already installed (Product Code: {A43BF6A5-D5F0-4AAA-BF41-65995063EC44}). Would not install again.
<05-18-2011 22:23:18> Pre Req MSXML60 is already installed. Skipping it.
<05-18-2011 22:23:18> Pre Req Wimgapi found.
<05-18-2011 22:23:18> Wimgapi already installed (Product Code: {721ABC3B-5F12-4332-9C0C-C11424EF666C}). Would not install again.
<05-18-2011 22:23:18> Pre Req Wimgapi is already installed. Skipping it.
<05-18-2011 22:23:18> ======== Completed Installion of Pre Reqs for Role SMSPXE ========
<05-18-2011 22:23:18> Installing the SMSPXE
<05-18-2011 22:23:18> Machine is running Windows 2003 SP1 or later. (NTVersion=0X502, ServicePack=2)
<05-18-2011 22:23:18> WDS Service is installed.
<05-18-2011 22:23:18> No versions of SMSPXE are installed. Installing new SMSPXE.
<05-18-2011 22:23:18> Enabling MSI logging. pxe.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\pxeMSI.log
<05-18-2011 22:23:18> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\pxe.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" PXEENABLELOGGING=TRUE PXELOGLEVEL=1 PXELOGMAXSIZE=1000000 PXELOGMAXHISTORY=1
<05-18-2011 22:24:11> pxe.msi exited with return code: 0
<05-18-2011 22:24:11> Installation was successful.
<05-18-2011 22:31:06> ====================================================================
<05-18-2011 22:31:06> SMSPXE Setup Started....
<05-18-2011 22:31:06> Parameters: C:\PROGRA~1\MICROS~4\bin\i386\ROLESE~1.EXE /install /siteserver:DRDO-QQLUVGDI0P SMSPXE
<05-18-2011 22:31:06> Installing Pre Reqs for SMSPXE
<05-18-2011 22:31:06> ======== Installing Pre Reqs for Role SMSPXE ========
<05-18-2011 22:31:06> Found 2 Pre Reqs for Role SMSPXE
<05-18-2011 22:31:06> Pre Req MSXML60 found.
<05-18-2011 22:31:06> MSXML60 already installed (Product Code: {A43BF6A5-D5F0-4AAA-BF41-65995063EC44}). Would not install again.
<05-18-2011 22:31:06> Pre Req MSXML60 is already installed. Skipping it.
<05-18-2011 22:31:06> Pre Req Wimgapi found.
<05-18-2011 22:31:06> Wimgapi already installed (Product Code: {721ABC3B-5F12-4332-9C0C-C11424EF666C}). Would not install again.
<05-18-2011 22:31:06> Pre Req Wimgapi is already installed. Skipping it.
<05-18-2011 22:31:06> ======== Completed Installion of Pre Reqs for Role SMSPXE ========
<05-18-2011 22:31:06> Installing the SMSPXE
<05-18-2011 22:31:06> Machine is running Windows 2003 SP1 or later. (NTVersion=0X502, ServicePack=2)
<05-18-2011 22:31:06> WDS Service is installed.
<05-18-2011 22:31:06> SMSPXE already installed (Product Code: {C63C1FBD-C9C8-469D-8ADE-12387FB5EA75}). Upgrading/Reinstalling SMSPXE
<05-18-2011 22:31:06> New SMSPXE is the same product code. This is a minor upgrade.
<05-18-2011 22:31:06> Enabling MSI logging. pxe.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\pxeMSI.log
<05-18-2011 22:31:06> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\pxe.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="C:\Program Files\SMS_CCM" PXEENABLELOGGING=TRUE PXELOGLEVEL=1 PXELOGMAXSIZE=1000000 PXELOGMAXHISTORY=1
<05-18-2011 22:35:43> pxe.msi exited with return code: 0
<05-18-2011 22:35:43> Installation was successful.
<05-18-2011 23:41:19> ====================================================================
<05-18-2011 23:41:19> SMSPXE Setup Started....
<05-18-2011 23:41:19> Parameters: C:\PROGRA~1\MICROS~4\bin\i386\ROLESE~1.EXE /deinstall /siteserver:DRDO-QQLUVGDI0P SMSPXE
<05-18-2011 23:41:19> Deinstalling the SMSPXE
<05-18-2011 23:41:19> Enabling MSI logging. pxe.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\pxeMSI.log
<05-18-2011 23:41:19> Deinstalling SMSPXE, with product code {C63C1FBD-C9C8-469D-8ADE-12387FB5EA75}
<05-18-2011 23:41:33> SMSPXE deinstall exited with return code: 0
<05-18-2011 23:41:33> Deinstallation was successful.
<05-18-2011 23:41:33> Removing PXE Registry.
<05-19-2011 00:38:50> ====================================================================
<05-19-2011 00:38:50> SMSPXE Setup Started....
<05-19-2011 00:38:50> Parameters: C:\PROGRA~1\MICROS~4\bin\i386\ROLESE~1.EXE /install /siteserver:DRDO-QQLUVGDI0P SMSPXE
<05-19-2011 00:38:50> Installing Pre Reqs for SMSPXE
<05-19-2011 00:38:50> ======== Installing Pre Reqs for Role SMSPXE ========
<05-19-2011 00:38:50> Found 2 Pre Reqs for Role SMSPXE
<05-19-2011 00:38:50> Pre Req MSXML60 found.
<05-19-2011 00:38:50> MSXML60 already installed (Product Code: {A43BF6A5-D5F0-4AAA-BF41-65995063EC44}). Would not install again.
<05-19-2011 00:38:50> Pre Req MSXML60 is already installed. Skipping it.
<05-19-2011 00:38:50> Pre Req Wimgapi found.
<05-19-2011 00:38:50> Wimgapi already installed (Product Code: {721ABC3B-5F12-4332-9C0C-C11424EF666C}). Would not install again.
<05-19-2011 00:38:50> Pre Req Wimgapi is already installed. Skipping it.
<05-19-2011 00:38:50> ======== Completed Installion of Pre Reqs for Role SMSPXE ========
<05-19-2011 00:38:50> Installing the SMSPXE
<05-19-2011 00:38:50> Machine is running Windows 2003 SP1 or later. (NTVersion=0X502, ServicePack=2)
<05-19-2011 00:38:50> WDS Service is installed.
<05-19-2011 00:38:50> No versions of SMSPXE are installed. Installing new SMSPXE.
<05-19-2011 00:38:50> Enabling MSI logging. pxe.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\pxeMSI.log
<05-19-2011 00:38:50> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\pxe.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" PXEENABLELOGGING=TRUE PXELOGLEVEL=1 PXELOGMAXSIZE=1000000 PXELOGMAXHISTORY=1
<05-19-2011 00:39:15> pxe.msi exited with return code: 0
<05-19-2011 00:39:15> Installation was successful.I have similar issue same above error but this error i am getting intermittent keeping trying 2 or 3 times i get F12 option to boot the network services
TFTP
PXE-T01 The specified file not found
PXE-E3B TFTP Error : File not found
Our environment have DHCP configured In Inflobox and the Primary site server and PXE DP server located in Same Subnet and configured 2008 R2 sp1 and configured SCCM2012 in VM environment
I tried all the Options uninstall and re-install no luck and i have tried to increase Tramsmiit and recive Buffer size in lan card but the issue is not resolved.
Capture smspxe log when it found boot image the pxe working ,when it not found getting TFTP error.
SMSPxe log says no errors but getting client Pxe TFTP error file not found (Since its not looking Image throw out TFTP error)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777230" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:49D9F374-7606-4277-8AE9-FEE608FFB01E</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="SGP20001" OfferIDTime="6/25/2012 11:09:00 AM" PkgID="SGP00009" PackageVersion="" PackagePath="http://XXX.company.com/SMS_DP_SMSPKG$/SGP00004" BootImageID="SGP00004" Mandatory="0"/></ClientIDReply>
Client Identity: 9c7f0d6a-58dd-4cda-a4f0-3f66316067fb
PXE::CBootImageManager::FindMatchingArchitectureBootImage
Set media certificate in transport
Set authenticator in transport
SMSPxe log says no errors t i can able to do pxe Log found Boot image
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777230" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:49D9F374-7606-4277-8AE9-FEE608FFB01E</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="SGP20001" OfferIDTime="6/25/2012 11:09:00 AM" PkgID="SGP00009" PackageVersion="" PackagePath="http://xxx.company.com/SMS_DP_SMSPKG$/SGP00004" BootImageID="SGP00004" Mandatory="0"/></ClientIDReply>
Client Identity: 9c7f0d6a-58dd-4cda-a4f0-3f66316067fb
PXE::CBootImageManager::FindMatchingArchitectureBootImage
PXE::CBootImageManager::FindBootImage: SGP00004
Looking for bootImage SGP00004
PXE::CBootImageCache::FindImage
PXE::CBootImageInfo::UpdateAccessTime
Appreciate if you could provide some solution
Ksrini -
Maximum number of PXE servers for WDS/MDT
We have an imaging environment based on Windows Server 2012 R2 using WDS with MDT.
For optimal speeds, each imaging station has a server dedicated to it, with its own Multicast address space.
Due to the success and speed accomplished with 10 stations being served by 10 servers, we wanted to scale to 18 stations (so let's call it an even 20, as that was I was building for).
We utilize the registry change to
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSPXE\Providers\BINLSVC]
"AllowServerSelection"=dword:00000001
as to allow us to choose which PXE server to boot to (as detailed here: http://www.stephan-schwarz.net/?p=58 )
However, we have run into a problem- the menu to select a server caps out at 17 servers for older environments (Legacy BIOS) and 16 for UEFI. This was confirmed both within a BIOS and UEFI VMWare environment, as well as our primary deployment device (17
for Legacy, 16 for UEFI). The devices are to be UEFI Secure Boot, so the cap for us is 16.
Is there anywhere I can turn to increase this limit? I'm not going to be surprised if the answer is no.
However, has anyone made a PXE loading page allowing a user to choose a particular server? I had built in the past such a menu using TFTP and Ghost, and I see this article on doing something similar for WDS, but I don't know if it can just point at any other
PXE servers.
Thanks for your time.Actually, with each WDS server with it's own Multicast IP range, we have seen great speeds from each server to each grouping of 30-ish machines, though of course "it could always be better!"
As such, with 16 servers we can move 500+ machines an hour/hour-and-a-half. In fact, it's the drop to Unicast SMB that MDT does after the WIM transfer that slows down the process (as noted here as well as our own testing http://social.technet.microsoft.com/forums/windowsserver/en-US/73e398b5-75ab-4787-b230-6254de107084/wds-multicast-falls-back-to-unicast-after-copying-files-stage)
We'll continue tweaking the technology and attempting to implement some segmentation via subnets/VLANs so we can have more capacity. Someday, I'll have to put it all together in a blog post. -
Hi All,
Hopefully this is in the right place and someone can offer some assistance for me. I will try to lay this out correctly (newbie on this forum).
Have installed WDS on Server 2012 R2. Settings altered...
Setup my server as standard, nothing special. Created boot.wim from a copy of a Dell Win 7 disk, copied locally and imported. Created capture image. Imported numerous drivers (which were installed manually and worked on the client (testing client)). Settings
changed on the WDS server (it is called ntserver29 for reference).
- PXE Response - Respond to all clients...(require administrator approval not ticked)
- AD DS - Computer Account Location - Same Domain as WDS server
- Boot - as default, require user to press f12.
- Client - Joining a Domain - Do not join...ticked.
- DHCP - Neither 'do not listen' and 'configure dhcp options' ticked. (DHCP not installed on that server)
- TFTP - block size (as default) set to 1298 (have changed the registry file from 0 to 512 as previously instructed on an online guide). Enable the TFTP server to negotiate variable window size requests is ticked.
- Network - UDP port policy is set to 'obtain dynamic ports'
- Advanced - Domain Controller - Allow WDS to dynamically discover domain servers (ticked). DHCP Authorisation - Authorize this WDS server in DHCP
- Multicast - Multicast IP set to obtain IP from DHCP. Transfer Settings set to Keey all multicase clients in a session at the same speed.
From the top. Have had issues which seem resolved, will explain further down.
* With the above set. Have built Dell desktop machine with Dell windows 7 disc flat. Installed relevant drivers, some updates and google chrome.
* Using sysprep and the capture image got as far as saving the wim. Was unable to authenticate to the server as it did not even bring up the account login box, just failed to connect (ISSUE 1).
* Chose to test WDS seperate. Copied the image to an external drive. Copied to the RemoteInstall\Images path on the WDS server. This populate the image to the server without involvement from myself. Restarted the server.
* When rebooting the desktop, device only shows Windows 7 Setup and Windows 7 Setup Capture (my 2 original boot images) and nothing else (ISSUE 2).
Bit stuck from there. WDS didnt work prior to uninstalling a specific update and re-installing a fresh WDS.
Any advice would be GREATLY appreciated. I dont lay claim to being knowledgeable about the system, just looking to learn and get this working for the business. Happy to answer questions and will keep checking in.
Many Thanks, hopefully the above makes sense to someone.
MarkIf this will help any. Obtained the details from CMD.
Unattend file present: No
Status: Enabled
Boot Images for ia64
Image count: 0
Image Information:
There are no images that match the specified criteria.
Boot Images for arm
Image count: 0
Image Information:
There are no images that match the specified criteria.
===============================================================================
Summary:
Total number of boot image stores: 4
Total number of boot images: 3
INSTALL IMAGES
===============================================================================
Image Group DistributionGroup
Name: DistributionGroup
Security: O:BAG:DUD:(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;;FA;;;BA)(A;OICIIO;GA;;;C
O)(A;OICI;0x1200a9;;;BU)(A;CI;LC;;;BU)(A;CI;DC;;;BU)
Image format: WIM
Image count: 6
Image Information:
Dell Optiplex 3020 Test
File name: Dell Optiplex 3020.wim
Image name: Dell Optiplex 3020 Test
Description: Dell Optiplex 3020 Test Capture
ID: <Not Assigned>
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 12172102562 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 15 October 2014 19:58:39
Last modified: 15 October 2014 19:58:46
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\Dell Optiplex 30
20.wim
OS version: Microsoft® Windows® Operating System, 6.1.7601
Service pack level: 1
User filter: O:S-1-5-21-1738485378-1525038498-1803697834-16854G:DUD:(A;;FA;;;BA)
(A;;FA;;;SY)(A;;FA;;;S-1-5-21-1738485378-1525038498-1803697834-16854)(A;;0x1200a
9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
<Error>
Windows 7 HOMEBASIC
File name: install-(2).wim
Image name: Windows 7 HOMEBASIC
Description: Windows 7 HOMEBASIC
ID: {587B12B6-D6D9-4F13-8B81-E962AC7078D7}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8306998658 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:18
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(2).wim
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 HOMEPREMIUM
File name: install-(3).wim
Image name: Windows 7 HOMEPREMIUM
Description: Windows 7 HOMEPREMIUM
ID: {150666C9-B2D9-4BA0-873C-3A4B7BF986C3}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8747698450 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:21
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(3).wim
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 PROFESSIONAL
File name: install-(4).wim
Image name: Windows 7 PROFESSIONAL
Description: Windows 7 PROFESSIONAL
ID: {1849C3AE-E2F6-4EC5-9DBD-AD0FD2223185}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8627895833 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:22
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(4).wim
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 ULTIMATE
File name: install-(5).wim
Image name: Windows 7 ULTIMATE
Description: Windows 7 ULTIMATE
ID: {280A4685-155E-4565-B413-D60BB8F105E7}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8785899727 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:24
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(5).wim
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 STARTER
File name: install.wim
Image name: Windows 7 STARTER
Description: Windows 7 STARTER
ID: {1C935F5A-1835-49A3-AE1A-B64910FFF925}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8250904871 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:16
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install.wim
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
NON-NATIVE IMAGES
===============================================================================
===============================================================================
Summary:
Total number of non-wim image groups: 0
Total number of non-wim images: 0
An error occurred while trying to execute the command.
Error Code: 0xC10408B3
Error Description: One or more errors occurred while processing the command. Rev
iew the error logs for more information.
C:\Users\administrator> -
I'm trying to set up WDS on server2008r2. the dhcp server is runnning server 2003. I have option 66 enable pointing to 172.18.4.23 and option 67 boot\x64\boot.wim
when i try to boot up a client to install the first instance to build my company image i get a TFTP open timeout.
i have tried everything that i can find and nothing is getting me any closer to success.
Not sure if this will help or not but I also had a linuxpxe sent up on this network that was working until i switch the options 66 and 67 to coincide with the windows instead of the linux box. but in attempt to put it back the way it was so linux can boot
on our zero clients i get the same TFTP timeout error.
Oh did i mention that this is the first time wds is being used in this enviroment so no one really know how to set it up to get it to work. there are vlans on the network but one thing at a time.Hi TCUTech,
You can try the following simlar thread solution first.
WDS server and DHCP server on two different servers
https://social.technet.microsoft.com/Forums/pt-BR/e84c8a4c-a6da-4c4a-8ca6-2a1007b205ae/wds-server-and-dhcp-server-on-two-different-servers?forum=winserversetup
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Maybe you are looking for
-
I have a gen 3 ipod and can't get it into disk mode. In itunes it does not have the option and I cant figure out how to do it on the ipod touch itself. Any ideas?
-
Why does this script not work when run with osascript cli?
I wrote the following to interface with geektool to display a list of todo's on my desktop (i'm sure it's been done elsewhere, but I wanted to try it myself). I had it working fine until I tried ordering the output to place the highest priority items
-
Report on the urgent correction with actions
Hello, My SolMan version is 7 and sp12. I search a report on SolMan with the N° correction, this differents actions with the created date and the created hours to produce indicators of performance. Can you help me ?
-
Time Machine Backup Crash - HELP!!!! Everything wiped out.
After reinstalling my time machine back-up, at restart I receive the following error: panic(cpu 0 caller 0x5591cb: "Unable to find driver for this platform: \"ACPI\".\n"@/SourceCache/xnu/xnu-1504.7.4/iokit/Kernal/IOPlatformExpert.cpp:13 89 Dbugger ca
-
Windows Live Mail Error ID: 0x80004004 and Windows Live Mail Error ID: 0x8004882E
Hello I am having trouble getting into Windows live. Here are the messages I get. Can you help me? Thank You, Mary