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.
Thanks
Thanks 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
Similar Messages
-
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. -
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. -
PXE boot fails and reboots after loading PE
I have run into what I think is a unique issue and need some help determining the cause.
We are in the process of replacing and aging DP/PXE point (2003 R2 SP2) with a new server (2008 STD R2 SP1). What makes my pxe issue unique is that pxe works without issue on the existing 2003 DP/PXE server. But on the new 2008 server I run into
the following issue.
Environment: Config Manager 2007 R2, a single primary, multiple DP's and PXE points.
Issue: When I attempt to PXE boot a system, I am able to load PE, but shortly after the custom background screen is loaded, the system reboots. I've searched the internet quite a bit and found lots of potential causes including, bad/missing drivers,
certificate issues, rights issues, etc. None of these seem to be the cause.
My troubleshooting has determined that the client computers are unable to download the variables.dat file. I just don't know why.
We're using the same boot images on both servers.
I've tried using multiple computer models and VM's.
I've opened a command prompt as soon as our background image loads and have verified that the system is pulling a valid IP address. I am able to map a drive to the PXE server's REMINST share using our sccm net access account and manually copy the .var
file using xcopy to the appropriate directory on the local virtual drive. I've also attempted to manually run smstftp.exe by mimicking the command line from the smsts log file. I'll admit that I'm not sure I have the correct syntax for smstftp.
I've tried several variations and all but one result in a short pause and no file copied/created in the X:\sms\data folder. The one that does produce a result says that the file cannot be found. I checked for typos and made sure I used the name
of the newly created .var file.
I've also tried disabling anti-virus on the server, shutting off the windows firewall on the server, granting everyone read rights to the REMINST share.
Below is the smstslog file I've been using as a reference. Per corporate security policy, I have X'd out the IP address of the PXE server. The log file for the successful pxe boot from the 2003 server shows an exit code of 0 for smstftp.exe, a note
about successful download of the pxe var file and then it continues through the rest of the boot process.
-----SMSTS log file from a failed PXE boot on the new 2008 server -----
<![LOG[LOGGING: Finalize process ID set to 832]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="tslogging.cpp:1489">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836"
file="bootshell.cpp:963">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="util.cpp:869">
<![LOG[Debug shell is enabled]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:974">
<![LOG[Waiting for PNP initialization...]LOG]!><time="16:13:54.471+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:59">
<![LOG[Booted from network (PXE)]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="configpath.cpp:198">
<![LOG[Found config path X:\sms\data\]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:553">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:564">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:767">
<![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:850">
<![LOG[Successfully launched command shell.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:430">
<![LOG[The command completed successfully.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
<![LOG[Starting DNS client service.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:597">
<![LOG[Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880"
file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932"
file="tsmbootstrap.cpp:1039">
<![LOG[Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932"
file="tsmbootstrap.cpp:1040">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="util.cpp:869">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="resourceutils.cpp:152">
<![LOG[Processor Is IA64: 0]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1005">
<![LOG[PXE Boot with Root = X:\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:921">
<![LOG[Executing from PXE in WinPE]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstrap.cpp:936">
<![LOG[Loading TsPxe.dll from X:\sms\bin\i386\TsPxe.dll]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1319">
<![LOG[TsPxe.dll loaded]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1329">
<![LOG[Device has PXE booted]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:122">
<![LOG[Variable Path: \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
file="tspxe.cpp:134">
<![LOG[Variable Key Len: 61]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:141">
<![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:123">
<![LOG[Executing: X:\sms\bin\i386\smstftp.exe -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.004+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:177">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="16:14:42.067+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:229">
<![LOG[Set command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:707">
<![LOG[Executing command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:805">
<![LOG[Process completed with exit code 1]LOG]!><time="16:15:29.179+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:1102">
<![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:146">
<![LOG[uExitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\server\pxe\tspxe\tspxe.cpp,185)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
file="tspxe.cpp:185">
<![LOG[Failed to download pxe variable file. Code(0x00000001)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tspxe.cpp:185">
<![LOG[PxeGetPxeData failed with 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tsmbootstraputil.cpp:1419">
<![LOG[HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1420)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context=""
type="0" thread="1932" file="tsmbootstraputil.cpp:1420">
<![LOG[TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2236)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="tsmediawizardcontrol.cpp:2236">
<![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,937)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe"
context="" type="0" thread="1932" file="tsmbootstrap.cpp:937">
<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1106)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="tsmbootstrap.cpp:1106">
<![LOG[Exiting with return code 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1118">
<![LOG[Execution complete.]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:624">
<![LOG[Finalizing logging from process 832]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1736">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1578">
<![LOG[LOGGING: Setting log directory to "D:\SMSTSLog".]LOG]!><time="16:15:29.491+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1803">
This has been an extremely frustrating issue and any assistance would be greatly appreciated!Thanks for your quick response Jason! I didn't expect someone to reply so quickly or I would have checked back sooner.
I had found the two 'older' posts already, but had not seen the 'newer' one. Unfortunately that did not give me any new ideas. But your comment on checking for TFTP availability did. Here are things I have tried since my original
post...
I re-ran most of my tests in case I missed something. I only found one change. Even though I double-checked, I must have made a typo when I manually ran the smstftp.exe command, because when I ran it again I received a timeout message instead
of file not found.
I had a minor 'thinking outside of the box moment' and decided to PXE boot the new 2008 R2 server itself. This was successful and I interpreted the success as meaning that the hardware is ok. Thinking there may be a compatibility issue with
the hardware and the OS, I tried a few different NIC drivers, settings, registry keys, and even a completely different NIC. No luck on any of these.
I decided to build another Server on a VM tovalidate my build process and configuration. And of course clients in multiple locations were able to PXE boot off this VM. Too bad I can't use this in production.
After reading your response Jason, I began to focus on network. I moved the server to a few different locations so it was utilizing different switches. No luck. I noticed in the event viewer for WDS that the server was logging the
beginning of the boot.var file via TFTP. This of course was not very surprising. What was surprising is that the very next entry (informational) noted that the client 'COMPLETED' the download of the boot.var file via TFTP. I know that completed
does not mean successful, but it usually implies or is interpreted as successful. It should have logged a warning or error, or nothing at all because although the process completed, it was not successful. I re-verified that the file was not downloaded
to the client and the client log file still shows the same error noted in the logfile from my original post.
Finally, I installed sniffing software on the server and ran some captures while attempting to PXE boot. Even though I am not much of a network guy, I quickly discovered two things. First, I found the section where the client attempts to download
the boot.var file. Unfortunately I don't think the local security team will allow me to post the capture, so I'll do my best to describe what I found. It starts with a single entry where the client calls for the file via TFTP protocol. This
is followed by a series of alternating entries (all TFTP) where it looks like the server attempts to send a portion of the file, and the client sends an acknowledgement. The sending entries all have checksum errors. The checksum received on
all packets is 0x0000 and of course should be something else. There is also a shorter section below this with alternating entries where the server attempts to send ICMP packets and the client responds with TFTP acknowledgements.
The ICMP entries are all marked as Destination unreachable (Port Unreachable).
The second thing I noticed from the network capture is the a few 'Spanning Tree Protocol' entries. I my search for a solution, I remember reading several posts saying that Spanning Tree can cause this issue. When I asked, I was assured that
Spanning Tree was disabled in this environment. It made sense too, because the 2003 PXE server was functioning properly, and Spanning Tree should affect both 2003 and 2008 servers, right?
Either way I will bring my findings to the network team and see what they have to say.
Any additional thoughts or ideas??? -
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? -
Won't boot from install discs after deleting some system files
I've been looking through the forum and haven't found an answer to my problem - maybe someone can help me out.
I have an aluminum Powerbook G4, 1.67, 1.5 RAM, 10.4.11. I was experiencing the problem with FCE capturing video for about 5 minutes and then freezing, and I read some threads here about how this can be fixed by returning to Quicktime 7.2 and installing it with Pacifist. I did this, but first tried to delete my previous Quicktime version files, and obviously I deleted some system files in the process. That's how my new problem started.
Programs now that do not open - Preview, iTunes, iMovie, FCE, Yahoo, Mail, and Microsoft Messenger. I no longer have my date/time/battery level/airport/bluetooth indicators in my toolbar. The Spotlight icon flashes, but will not open. Also, when opening the System Preferences pane, it opens just for a second or two and then crashes and closes. Safari, airport, and Word all work, though, and I still can access internet.
I tried to re-install OS 10.4 from my black install disc. The computer reads the disc, but after I click the installer icon and then "restart," the computer fails to completely reboot. The disc spins in the drive, I get the Apple, the indicator, and then the screen goes to blue and the disc soon stops spinning. Nothing happens after that. I've tried rebooting by holding down the C key but the same happens. When I hold down the option key, I get to the point where I can choose to boot from the install disc, and then the same thing happens - the blue screen and nothing more. Booting with the shift key held down doesn't work either.
I did just have a repair by Apple - my adaptor plug sparked when inserting it into the outlet, and I had to have the logic board replaced. But the computer seemed to be working fine when I got it back, except for the FCE issue first mentioned. Looks like my good intentions have done me in.
The install disc is about three years old, and is in good condition. It's been in the garage, so could heat or cold affect the readability of the disc?
Does anyone have any suggestions on how I can boot from my install disc and get a fresh install of my OS?Hi bboross,
Tough without a Tiger Disk, but try fsck...
To use fsck, you must run it from the command line. Unlike using your mouse to open an application to do something, you'll need to type a text command at the prompt (#) to tell fsck what to do. The Terminal application (/Applications/Utilities) and single-user mode are two examples of command-line interfaces in which you can type such commands. To use fsck:
1. Start up your computer in single-user mode to reach the command line. Hold CMD+s keys down at bootup. Note: If necessary, perform a forced restart as described in the Emergency Troubleshooting Handbook that came with your computer. On desktop computers, you can do this by pressing the reset/interrupt button (if there is one) or holding down the power button for several seconds. On portable computers, simultaneously press the Command-Control-power keys. If your portable computer doesn't restart with this method, you may need to reset the Power Manager.
2. At the command-line prompt, type /sbin/fsck -fy
(space between fsck and -fy important)
3. Press Return. fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found: ** The volume (nameofvolume) appears to be OK If fsck found issues and has altered, repaired, or fixed anything, it will display this message: *** FILE SYSTEM WAS MODIFIED *** Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
4. When fsck reports that your volume is OK, type reboot at the prompt and then press Return.
http://docs.info.apple.com/article.html?artnum=106214
Then Safe Boot , (holding Shift key down at bootup), & use Disk Utility from there to Repair Permissions, reboot once more. -
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 -
System file tampered with - Mac won't boot up. HELP!
Hi i have somehow managed to delete part of my system file and now when i try to start the computer it is fixed on the start up screen but the login box does not appear just a blue screen.
Is there anything i can do to overcome this problem? For example some way to reset my mac?
Any replies would be greatly appreciatedIf you've deleted system files then you will need to reinstall OS X. If you are using Snow Leopard then the reinstall will not erase the drive. If you are using Leopard then you will need to do an Archive and Install to avoid erasing the drive:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger, Leopard or Snow Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update. -
I installed the system update to 10.7.3. After re-booting, my mail file was missing from the dock. Looked in applications and the mail application is missing. Any thoughts?
Thanks Paul; but, taking your suggestion didn't solve the problem. As mail is part of the OS, the updates don't have the capacity to reinstall applications; so, I had to reinstall the OS. I now have my mail back (although it didn't appear on the dock--I had to go to applications and activate it and then put it back in the dock. Thanks again for trying.
-
How to relocate OS X system files to boot off another internal drive?
Hello, Apple forums!
Currently I have a 120 GB SSD installed where the optical drive was in my MacBook, and Mavericks resides on that. I have a second, larger, internal disc I use to house projects, and audio samples (for music production). Recently, I learned that running the OS off an SSD may actually reduce its lifetime, with so much activity on it. I'm wondering about moving the OS to reside on the HDD (there's plenty of room) and using the SSD just for loading frequently-used samples (which would actually be a big time-saver.)
My question is, is it as simple as a copy-paste of all files on the SSD to the HDD, then rebooting holding Option and selecting the HDD? Please inform if there's any problems there. Thanks all.I don't know who told you running OS X on an SSD would reduce its life. Of course with an SSD a lot of file erasures and frequent read/writes will in time wear out the SSD, but by the time that happened you will no longer be using SSDs.
Furthermore, you cannot simply make drag and drop copies of system files. If you wish to install a system on another drive either you clone and existing drive or you make a completely new OS installation. -
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 -
I took the system file out of the system folder on os 9.2 can't boot to put file back in machine also has osx 10.2 but won't let me boot to either need os 9 compatible boot disk I think?
If the OS X 10.2 on the hard drive is/was bootable, try this -
Restart or boot, then immediately press the X key, keep it held down until you know the machine has started to boot using OS X. This is a hardware instruction to the Mac to boot using the first usable instance of OS X it finds.
Once booted to OS X, you should be able to move OS 9's System file into OS 9's System Folder.
Note - in general, unless you know for sure what you are doing and that the results are desired, do not relocate or rename files in OS 9's System Folder or in OS X's System or Library folders. -
System file deletion to boot in Lion?
What I would like to know is what system file can I delete from the system when booted from another partition so I can boot up in Lion.
Lion locked up when I had ten applications open with a multiple windows and I had to do a HARD SHUT DOWN.
Now every time i try to boot into Lion it tries to reopen all the apps and windows and locks up again.
There must be an "com.apple." file that has this information in it.
I'm now booting from my Snow Leopard partition and need to fix Lion from here.
< Title Edited By Host >Startup Disk prefPane or hold down OPTION on start and select it.
-
I accidentally deleted a system file and my macbook pro will not boot
i accidentally deleted some files and i am guessing now that they were system files. now my macbook pro will not boot. i need help please
What OS version are you on? You're not running iOS 6.1.2 on it.
If you're on 10.7 or 10.8, try the recovery option:
http://support.apple.com/kb/HT4718 -
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.
Maybe you are looking for
-
In older versions of firefox a had the ability to instantly add all my open tabs to a folder of bookmarks. I really liked this feature, it was very convenient when I was doing something and was interrupted and wanted to be able to get back to where I
-
How can I set the default home page for all new users in Firefox 4
I'm trying to deploy FF 4.0rc1 in a corporate environment but I can't find a way to set the default home page or any other settings for that matter. Is there a way to set the default home page for all new users and lock it so that the users can't cha
-
Hi, We have a scenario where data is sent from MDM - PI - ECC. To send the data from MDM repository, we are using sender JCA adapter. While testing scenario, file is getting picked up by sender adapter with the status 'Message processing completed'
-
How to play .cdr files in Front Row without Toast
I just created an image of a few personal home DVD's using the Disk Utility and created as a CD/DVD Master images having extension .cdr . They load fine and I am able to play them via DVD Player, but I wish to see it in Front Row. I found from the in
-
Only Apple products will connect to Airport Extreme
Until a couple of weeks ago all was fine with my Airport Extreme. Now, only our Ipad2 and Iphone5 will connect, my laptop and blackberry cannot (they were ok before). The AX is setup in bridge mode and is working fine for the ipad and iphone but my