PXE boot stuck at "downloading config file cmds\z_maint.cmd
Hi.
Since I applied NW6.5sp8 to our ZDM7SP1_HP2 server (January Driver Updates were in
place before), the PXE boot gets stuck at
downloading config file cmds\z_maint.cmd
I had this very same issue before, there I missed to drop the correct version of
sys:\tftp\boot\settings.txt, after doing so, PXE boot was working fine again.
I doublechecked, that the right copies of the files initrd, linux and root are to be
found in sys:tftp and ./boot.
I *CAN* sucessfully download the z_maint.cmd file through
tftp -i 10.27.1.8 get cmds/z_maint.cmd
There is a very similar thread:
news://forums.novell.com/dlee.3shxji...ums.novell.com
The server in that thread is running on W2k3, not NW, as we use. So I suspect, that
it might be a simple "wrong files issue", even though I really checked initrd, ...
several times.
What's my mistake?
Regards, Rudi.
Hi.
I just want to add this information:
*ALL* the different client PCs we run get stuck at the very same point of th PXE
boot process.
downloading config file cmds\z_maint.cmd
the cursor is blinking next line and doesn't take any keystrokes.
Regards, Rudi.
Similar Messages
-
Cisco 7920 and Aironet 1100 (Downloading config file)
For some reason the 7920 is trying to Downlaod the config file and can't pass that screen.
It authenticates just fine and the i get the screen "downloading config file" and that's it.
It's been doing the same thig all morning.
Not sure what's going on.
please help.
Call Manager 4.1.3 Aironet 1100
Thanks
Zeekok, so i guess after a while, the phone said "upgrading firmware" and after resseting, i got to the screen with the line up.
I still have a problem though.
i can dial a phone, it will call but once someone answer on the other side, the 7920 resets itself.
PLease help. -
PXE Boot Stuck Contacting Server
OSD using PXE has been working for weeks. Suddenly today it stopped. The client receives the initial response from DHCP and then gets stuck on Pending Request, looking for policy, contacting server. The SMSPXE.log looks normal until the client is stuck contacting
the server. Then "Looking for bootImage PO1xxxxx" just repeats over and over. Here's what I've checked.
Deploy this boot image from the PXE-enabled distribution point is checked.
Boot image (x64) and x(86) are both updated and distributed to the DPs.
Use Boot image (x64) is checked in the Task Sequence.
Task sequence is deployed to both Unknown Computers and Deploy collection.
Deployment settings make available to media and PXE.
Switch the task sequence to x86 boot image.
I have not tried to disable and re-enable PXE on the distribution point or remove WDS yet. Any suggestions from someone that's resolved the issue?The distmgr.log file looks great. But, the SMSPXE.log file might show the root cause. There's an entry now that says BootImage P0100097 needs to be updated (new packageID=P0100097) VersionUpdate=true. Then there are messages about boot.bcd being deleted.
But the Looking for bootImage P0100097 keeps getting logged.
<![LOG[Error opening file: E:\RemoteInstall\SMSImages\P0100097\boot.P0100097.wim. Win32=32]LOG]!><time="09:02:24.995+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40"
file="bootimagemgr.cpp:1085">
<![LOG[Retrying E:\RemoteInstall\SMSImages\P0100097\boot.P0100097.wim]LOG]!><time="09:02:24.995+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="bootimagemgr.cpp:1086">
<![LOG[Boot image P0100097 has changed since added]LOG]!><time="09:02:28.011+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="bootimagemgr.cpp:1112">
<![LOG[ADK installation root registry value not found.]LOG]!><time="09:02:28.011+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="wimfile.cpp:197">
<![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="09:02:28.011+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="wimfile.cpp:334">
<![LOG[Opening image file E:\RemoteInstall\SMSImages\P0100097\boot.P0100097.wim]LOG]!><time="09:02:28.011+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="wimfile.cpp:412">
<![LOG[Found Image file: E:\RemoteInstall\SMSImages\P0100097\boot.P0100097.wim
PackageID: P0100097
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="09:02:28.011+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="bootimagemgr.cpp:925">
<![LOG[Closing image file E:\RemoteInstall\SMSImages\P0100097\boot.P0100097.wim]LOG]!><time="09:02:28.011+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="wimfile.cpp:448">
<![LOG[Boot image P0100097 has changed since added]LOG]!><time="09:02:30.980+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="bootimagemgr.cpp:1112">
<![LOG[ADK installation root registry value not found.]LOG]!><time="09:02:30.980+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="wimfile.cpp:197">
<![LOG[Loaded C:\Windows\system32\wimgapi.dll]LOG]!><time="09:02:30.980+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="wimfile.cpp:334">
<![LOG[Opening image file E:\RemoteInstall\SMSImages\P0100097\boot.P0100097.wim]LOG]!><time="09:02:30.980+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="wimfile.cpp:412">
<![LOG[Found Image file: E:\RemoteInstall\SMSImages\P0100097\boot.P0100097.wim
PackageID: P0100097
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="09:02:30.980+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="bootimagemgr.cpp:925">
<![LOG[Closing image file E:\RemoteInstall\SMSImages\P0100097\boot.P0100097.wim]LOG]!><time="09:02:30.980+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="wimfile.cpp:448">
<![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16781103" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
]LOG]!><time="09:02:37.402+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="libsmsmessaging.cpp:6346">
<![LOG[F0:1F:AF:01:3B:DA, 4C4C4544-0034-3410-8034-B4C04F5A5731: device is in the database.]LOG]!><time="09:02:37.402+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156"
file="database.cpp:483">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:02:37.402+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[BootImage P0100097 needs to be updated (new packageID=P0100097) VersionUpdate=true]LOG]!><time="09:02:37.402+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156"
file="bootimagemgr.cpp:1786">
<![LOG[PXE::CBootImageInfo::CBootImageInfo: key=P0100097]LOG]!><time="09:02:37.402+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagecache.cpp:60">
<![LOG[Saving Media Variables to "E:\RemoteInstall\SMSTemp\2015.01.21.09.02.39.0003.{D7FB3128-3134-466C-AF92-DD5580B12200}.boot.var"]LOG]!><time="09:02:39.105+360" date="01-21-2015" component="SMSPXE" context=""
type="1" thread="3156" file="tsremovablemedia.cpp:186">
<![LOG[Cannot read the registry value of MACIgnoreListFile (00000000)]LOG]!><time="09:02:44.292+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="provsettings.cpp:353">
<![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="09:02:44.292+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="40" file="provsettings.cpp:468">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:02:57.027+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[BootImage P0100097 needs to be updated (new packageID=P0100097) VersionUpdate=true]LOG]!><time="09:02:57.027+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156"
file="bootimagemgr.cpp:1786">
<![LOG[PXE::CBootImageInfo::CBootImageInfo: key=P0100097]LOG]!><time="09:02:57.027+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagecache.cpp:60">
<![LOG[Saving Media Variables to "E:\RemoteInstall\SMSTemp\2015.01.21.09.02.58.0004.{F6BC7C78-658E-4961-AF34-E898C637310C}.boot.var"]LOG]!><time="09:02:58.746+360" date="01-21-2015" component="SMSPXE" context=""
type="1" thread="3156" file="tsremovablemedia.cpp:186">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:03:16.792+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:03:36.574+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:03:56.339+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:04:16.121+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:04:35.887+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16781103" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
]LOG]!><time="09:04:55.809+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="libsmsmessaging.cpp:6346">
<![LOG[F0:1F:AF:01:3B:DA, 4C4C4544-0034-3410-8034-B4C04F5A5731: device is in the database.]LOG]!><time="09:04:55.809+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156"
file="database.cpp:483">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:04:55.809+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:05:15.434+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[File E:\RemoteInstall\SMSTemp\2015.01.21.09.02.28.05.{AD7F5491-DFC7-42A3-B3B0-0C6D34EAB931}.boot.bcd deleted.]LOG]!><time="09:05:17.184+360" date="01-21-2015" component="SMSPXE" context="" type="1"
thread="40" file="bootimagecache.cpp:267">
<![LOG[File E:\RemoteInstall\SMSTemp\2015.01.21.09.02.28.05.{AD7F5491-DFC7-42A3-B3B0-0C6D34EAB931}.boot.bcd.log deleted.]LOG]!><time="09:05:17.184+360" date="01-21-2015" component="SMSPXE" context="" type="1"
thread="40" file="bootimagecache.cpp:282">
<![LOG[File E:\RemoteInstall\SMSTemp\2015.01.21.09.02.30.06.{A3CFA92C-5B28-4D0B-B9A0-079CF96AB214}.boot.bcd deleted.]LOG]!><time="09:05:17.184+360" date="01-21-2015" component="SMSPXE" context="" type="1"
thread="40" file="bootimagecache.cpp:267">
<![LOG[File E:\RemoteInstall\SMSTemp\2015.01.21.09.02.30.06.{A3CFA92C-5B28-4D0B-B9A0-079CF96AB214}.boot.bcd.log deleted.]LOG]!><time="09:05:17.184+360" date="01-21-2015" component="SMSPXE" context="" type="1"
thread="40" file="bootimagecache.cpp:282">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:05:35.215+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:05:54.981+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:06:14.762+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:06:34.528+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774">
<![LOG[Looking for bootImage P0100097]LOG]!><time="09:06:54.294+360" date="01-21-2015" component="SMSPXE" context="" type="1" thread="3156" file="bootimagemgr.cpp:1774"> -
Cant boot windows-Mi​ssing config file
My sister has a Satellite A105-S4384 laptop and she got a virus on it. I restarted the pc on safemode and did a scan. When the scan finished, it prompted me to restart to finish removing the infected files, so I did. after that, I wanted to restart in safemode again so I could do another scan, but i forgot to press f8, so when the system was still loading, i pressed the power button and the pc rebooted. Once the pc restarted, I pressed f8, then i got the error message that windows could not start b/c it was missing the file or it was corrupted (windows/system32/config/system).
I dont remember having the the XP media center edition installation disk, nor can I find it. Please helpSatellite A105-S4384
I dont remember having the the XP media center edition installation disk, nor can I find it.
Best to restore the hard drive to its original factory-new contents. Replacement media can be ordered by calling Toshiba Customer Service at 1-800-457-7777.
They will want the computer's serial number and a credit card number.
-Jerry -
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. -
SkyDrive in Windows 8.1 RTM stuck on downloading files
Hi,
when I make SkyDrive's files offline on Windows 8.1 RTM, the SkyDrive never finishes (it stuck in "Downloading xxx files"). They are kept in this state forever, even after restarts and/or additional uploads.
I have tried this on several computers several times but it always (or almost always) stuck. Number of files differs on each attempt.
I've tried to search for a solution on the net, but have not found anything useful/working (including the App Troubleshooter, or deleting all the files and uploading again), just few notes that for some people a fix on the server side was required.
This issue were present also in the 8.1 Preview era. Applying the RTM Rollup patches did not help.
Would you check the server side for me or suggest how to fix it?Hi,
Let’s try to redirect the skydrive folder and sync again to see what’s going on:
1. Open regedit and find following key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\SkyDrive
2. Change “UserFolder” to another location.
3. Open the SkyDrive Metro app to confirm your files and new directory.
Then check the issue again.
If the issue persists, please try to reset your Windows 8.1.
Note:Backup your personal data.
How to restore, refresh, or reset your PC
http://windows.microsoft.com/en-in/windows-8/restore-refresh-reset-pc
Best regards,
Karen Hu
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. -
[SOLVED]Warning booting: All config files need .conf
Recently i get this boot message:
WARNING: All config files need .conf: /etc/modprobe.d/modprobe.conf.pacnew,
I have another file called modprobe.conf.
Do I just need to rename/delete the file??
Thanks in advance.
Last edited by Hyugga (2011-11-14 00:05:15)Yes... you should ALWAYS vimdiff (or whatever) your pacnew files against their existing counter parts to capture changes from the devs first!
http://amjith.blogspot.com/2008/08/quic … orial.html -
Hi there
I'm trying to deploy a windows 7 image through Windows deployment services via PXE boot from a 2012 R2 server.
Issue: PXE boot is extremely slow, it takes up to more than 60 minutes for the device to download download the PXE boot
Things I already tried to get this up and running:
I've tried to change the TFTP block size via command prompt and via regedit
I've changed the settings on the tab of the WDS role (go to WDS role -> properties on server -> Tab "tftp")
Both actions resulted in PXE boot being even slower than it already was.
To make sure this is not because of our environment I’ve set up the same configuration on a windows server 2008 R2, here PXE boot image is downloaded to the machine within 3 minutes.
Both servers are set up through Hyper-V this is the configuration:
2008 R2:
Memory: 4096 MB
1 Virtual processor
IDE controller 2 hard drives
Network adapter
2012 R2:
Memory: 4096 MB
32 virtual processors
SCSI controller 2 hard drives
Network adapter
I can’t imagine that PXE boot is not working because of the differences of the Hard drives controllers or because of the amount of the virtual processors.
Windows server 2012 R2 seems to handle PXE boot TFTP differently in comparison to 2008 R2.
Do you guys know what I can do/try to get this working?Hi Jacques Rodrigues,
You can run Windows Deployment Services on Hyper-V virtual machines,
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.
If you are using multicast, Check if IGMP Snooping is enabled i.e. Routers that support multicasting. In particular, Internet Group Membership Protocol (IGMP) snooping should
be enabled on all devices. This will cause your network hardware to forward multicast packets only to those devices that are requesting data. If IGMP snooping is turned off, multicast packets are treated as broadcast packets, and will be sent to every device
in the subnet.
The related KB:
Windows Deployment Services Overview
http://technet.microsoft.com/en-us/library/hh831764.aspx
I’m glad to be of help to you!
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. -
PXE boot UEFI Thinkpad 10 not working
struggling with this problem for some time now..
saw some related threads but not really providing an answer
have one customer who bought a bunch of Thinkpad 10 machines from lenovo and the purpose is to install them with a 8.1 SOE, untill now the only thing that works is to use a standalone usb medium
our setup is SCCM 2012 R2 on top of Server 2008R2 using infoblox instead...
the thinkpad 10 has the latest ATOM cpu and is definitely a 64 bit UEFI machine
we also noticed that some switches have problems to (try and ) boot the UEFI machines, dont know why yet
the issue is that the only thing we see during a UEFI only PXE boot is that the NBP file gets succesfully downloaded (even twice) and then just switches back to the next bootoption.
i've checked:
-PXE boot another UEFI device: same symptom
-PXE boot legacy devices: ok
-changed the bootfile in option 67 to the efi file: same symptom
-all files are in the smsboot\x64 folder
lenovo support now wants me to do this: include a winPE x64 image that supports UEFI and then run the following command on the server:
"WDSUTIL /New-MulticastTransmission /FriendlyName:"WDS Boot Transmission" /Image:"Microsoft Windows PE (x64) Win8" /ImageType:Boot /Architecture:x64
/TransmissionType:AutoCast"
but I don't see what UEFI/pxe has to do with multicasting and why should I change something on wds if UEFI boot under similar circumstances works in other implementations?
any more useful ideas folks?if you are using dhcp options, remove them, instead configure iphelpers to point to the server hosting your pxe enabled DP (should be running server 2008r2 or later).
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady
Niall,
this was the solution in our case.
the problem was to convince the network guys to try this for us...
since we are using IP helpers it works to do the PXE boot for UEFI -
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. -
Hi, My MDT server no longer works as expected via PXE boot. After the target machine loads the .wim file an empty command windows is shown. I have returned the custom settings.ini and bootstrap files to default and ensured nothing is being skipped within
the task sequence within both files in hope of viewing the wizard.
However from the same target machine if I map drive to my Deploymentshare/Scripts directory and run LiteTouch file I am asked for domain credentials and the Deployment wizard is displayed asking for task sequence to be selected.
I believe this error is a result of two things:
1) I applied some windows updates to my mdt server (running on 2008 r2).
2) I was implementing changes to
ZTIWindowsUpdate.wsf which i have now returned to default settings.
I have also regenerated boot images and re added to WDS.
Any help much appreciated?
Regards,
PaulHi Paul,
This sounds familiar; I only encounter this behaviour with certain kinds of laptops (Latitude E65x0) but I usually just provide the "wpeutil reboot" command in the empty command window to keep things going. All other hardware is deployed with the
same task sequence and this behaviour does not occur anywhere else...
A bit obvious maybe, but did you check if there is still a "Next Phase" step present and enabled following directly after the "Install Operating System" step? -
I have a validation lab that uses Windows 7, 8 and 8.1 on several completely different systems. I am looking for an easy way for the techs to PXE boot from a 2012 Server, select the OS to install and have the OS installed with drivers so when they come back
to the system it has the OS installed with no Bangs in Device Manager.
I have done this in the past (7-8 years ago) and it was fairly easy. Now from what I read it appears I have to create "Image" files for each system type? I hope I am misreading this because that method is counter-productive to create 10 different
images for 10 different systems.
I thought I used WDS and AIK on a 2K3 Server but I don't remember.
Is there a method/tool to install the operating systems as I described above using original OS ISOs, unattended answer files and driver files? WDS or SCCM? AM I misreading how it works?Consider using newer Windows ADK
http://www.microsoft.com/en-us/download/details.aspx?id=39982 -
PXE Boot - Installation system files...
Hi there,
I need some clarity on the following please.
I am applying the October 2012 ZENworks Imaging Driver Update.
Before the update all works fine and it goes through the pxe boot process as follows.
Pxe boots fine and I get the pxe menu.
Once I select a menu option it goes through a few checks, usb devices etc.
then Sends the DHCP request and lastly
Loading installation system.....(55392 Kb)
I get the #prompt and can image fine.
After the update which I do by backing up and replacing the following pxe files.
srv/tftp/nvlnbp.sys
srv/tftp/boot/settings.txt
srv/tftp/boot/initrd
srv/tftp/boot/root
srv/tftp/boot/linux
I get the following.
Pxe boots fine and I get the pxe menu.
Once I select a menu option it goes through a few checks, usb devices etc.
then Sends the DHCP request and lastly
Loading installation system.....(15000 Kb) --> This file is a lot smaller.
Where do the above files come from..?
Then I get the #prompt and attempts to start the imaging process crash.
Maybe there is something I am missing in the update.
I did the pxe file updates. Is there anything else that should be updated for the pxe boot to work ?
As soon as I revert back to the old files, I get a complete download of the Installation system.
ThanksThanks I tried that, but sadly it did not work
The drivers work for the new hardware model, but the installation system that is downloaded is only 15000, then imaging crashes.
These are the only files that change between the working and not working system. Keeping the old root also did not work.
any ideas anyone ??
srv/tftp/nvlnbp.sys
srv/tftp/boot/settings.txt
srv/tftp/boot/initrd
srv/tftp/boot/root
srv/tftp/boot/linux -
I need help. My ipad 2 was stuck in recovery mode. i tried to connect it to itunes and restore but after downloading the file and extracting the software there is a pop up message that says "the device is full. Deleting files and emptying your recycle been will help you restore." how am i going to erase files if i can't open my ipad. i dont know what to do. Its been 2 days now. please help. thanks.
yes i am sure. This are the exact words... "The iPad "iPad" could not be restored. The disk you are attempting to use is full. (Removing files and emptying the recycle bin will free up additional space". i tried some options, hard reset, redsnow, tinyumbrella but still it's stuck.
-
Hello,
1) I realized that when MBAM bitlocker encryption start both Recovery key and TPM owner password file are send to MBAM server. If we change the computername of the notebook, we can find out Recovery key from MBAM server with the KeyID as we can read it from
computer screen, but we can not find out TPM owner password file with the existing new computername information from MBAM server, so we have to know old names of all computers but it is impossible. So we have to do decryption and clearing TPM than we
can again encrypted it with its new name. is it right?
2) We will going to deploy mbam encryption to our notebooks. But sometimes when a person quit the job his notebook can given to another person or new employee and based to our procedure when a notebook will given to another user it should installed
OS again with PXE boot. I would to know will it be enough to installing with this method again with a diffrent computer name or should I firstly clear its TPM than install OS with PXE to keep TPM owner password file missing as item 1?
I hope i can explain what i mean :)
Regards,
SibelMI would suggest you to first decrypt the laptop and then follow the process:-
- Clear the TPM
- Encrypt the type.
- Check for the encryption behavior.
Cause I have found on some model that if the OS drive is encrypted, PXE boot fail on that machine even though I also did a direct PXE on an encrypted machine with clearing the TPM.
TPM ownership password is a hash file that gets generated with a set of algorithm. SO each time when you PXE boot, by clearing the TPM, the TPM hash password for the TPM will change. This has been done for security measures.
Gaurav Ranjan
Maybe you are looking for
-
Moving from 10.2.8 to 10.4.6
I have a copy of the full install DVD for 10.4.6 (retail not for a specific model) I know 10.5 will be shipping out early fall of this year. But I need 10.4 now to run Adobe CS3 I'm currently running 10.2.8 (9.2.2 installed for classic) on a 2001 Qui
-
A relative gave me her Iphone. Is there a way to associate it to my own apple I'd. Thanks
-
What first - rollnames, comments, keywords, or albums?
I'd like an idea how to get started with organizing approx. 20,800 pics (they are on the drive and ready to go!). The current roll names arent the greatest and really arent organized - but if I am making albums, etc. I dont think that matters,right?
-
Bug report: Option boot fails to show FAT32 partition in SR MacBooks
Holding down the Option key only shows the Macintosh HD partition, even though Win XP Home SK2 is properly installed in Boot Camp into a FAT32 partition. The Windows HD partition shows up in the Startup Disk System Preferences, and can be booted into
-
How to retain format in excel?
Is there any way to retain formatting in excel once a retrival is done i.e. Total bold and underlined?Thanks,Calvin