Pxe boot sun x4170-m2 LSI raid 5 disks issues 2.10_u9 rel
Hi Gurus,
I am trying to image sun fire x4170-m2 series servers with Latest solaris 10.u9 patch set using Raid-5 disks setup with one hot-spare. Pxe boot works but i minboot not able to find raid-5 disks which is about 1.2 TB disks size. Where as if i used DVD to boot the servers it works properly. What i am missing. Here is my pxe entry and menu.list<mac-address> entry. I tried to insert driver LSI megraid driver with x86.miniroot, but it's already available into kernel/drv.
-dhcpd.conf entry.
host foobar { hardware ethernet 00:21:28:8E:3D:F2; fixed-address 10.228.150.14; next-server 140.87.100.21; filename "010021288E3DF2"; option host-name "foorbar.us.oracle.com";}
menu.1st.<mac-address>
cat /tftpboot/menu.lst.010021288E3DF2
default=0
timeout=30
min_mem64 1024
title Solaris_10 install_x86_64_2.10_u9
kernel /I86PC.Solaris_10-9/multiboot kernel/unix - install - nowin -B console=i86pc,install_config=140.87.100.21:/export/jumpstart_x86_64_2.10_u9,sysid_config=140.87.100.21:/export/sysid_2.10_u9/10.228.144,install_media=152.68.248.67:/vol/local/x86/solaris/100/base/u9/mar2011,install_boot=140.87.100.21:/export/install_x86_64_2.10_u9_new/boot -v -m verbose
module /I86PC.Solaris_10-9/x86.miniroot
Please let me know if you have any solution for this issue.
Thanks & Regards,
-Sunil.
Hi.
Read thread:
X4x70 (M1) with extremely slow disk I/O
Try workaround the problem by adding the following line to /etc/system and then reboot:
set idle_cpu_no_deep_c = 1
Regards.
Similar Messages
-
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. -
We are having issues with our clients not being able to receive an address from the imaging server, so while our networking team fixes that problem I would like to create a cd/floppy that I can use to point the client computers to the imaging server to continue our testing of imaging. I tried to use zimgboot.exe from the sys directory on the server but it does not work? Any help would be appreciated.
ZfD version 6.5.2
AndyI just tried to pxe boot 4 workstations using the same jack and found 3 of the 4 cannot find the boot file while trying to pxe boot. From what I can tell I see no differences, besides the mac addresses. They are all hp d530 SFF machines with the same pxe client ( pxe2.1 Build 082 v 6.1.2) and broadcom netxtreme Gig network cards. At this point I'm not sure what else I can look at in trying to resolve this issue.
I also check a few other workstations with different pxe clients and network cards and they cannot boot into pxe either.
>>> Marcus Breiden<[email protected]> 12/09/2007 9:15 AM >>>
On Thu, 06 Dec 2007 15:16:53 GMT, Andy_DeWees wrote:
> Although the imaging server and workstations are on different subnets, but the 2 computers that work are on a different subnet, then when I plug another computer into that same jack I get the error message.
hmm.. same network card in those boxes?
If you have already compiled drivers or have linux.2 please put them on
http://forge.novell.com/modules/xfmo...ect/?zfdimgdrv
Live BootCd and USB Disk from Mike Charles
http://forge.novell.com/modules/xfmod/project/?imagingx
eZie http://forge.novell.com/modules/xfmod/project/?ezie
Marcus Breiden
If you are asked to email me information please remove the - in my e-mail
address.
The content of this mail is my private and personal opinion.
http://www.didas.de -
W520 - BIOS update (8buj19uc.iso) hangs after PXE booting
After PXE booting the latest 1.40 BIOS bootable CD,
the system hangs after pressing "2. Update system program"
Here my setup:
LABEL w520bios
MENU LABEL ^w. BIOS V1.40 W520 - 32bit - Normal - ISO - (EN)
TEXT HELP
* Boot the W520 BIOS ISO image over PXE
ENDTEXT
LINUX memdisk
INITRD ../isos/bios/w520/8buj19uc.iso
APPEND iso raw
I need this feature, because we have several thinkpads to update!
Any help regard this topic is greatly appreciatedI had no clue what PXE is, so I looked it up:
The Preboot eXecution Environment (PXE, also known as Pre-Execution Environment; sometimes pronounced "pixie") is an environment to bootcomputers using a network interface independently of data storage devices (like hard disks) or installed operating systems.
http://en.wikipedia.org/wiki/Preboot_Execution_Environment
W520 4270CTO i7-2820QM Quadro2000M 1920x1080 Display 16GB RAM 2x240GB Intel 510 SSDs (RAID 0) - BIOS 1.42 - PCMark7:4,568
Samsung Series 9 15-inch NP900X4C-A03US - PCMark7: 4674 -
Problems PXE booting Gen 2 Virtual Machines after Upgrading to Windows Server 2012 R2
My Current Setup:
I have two virtual machines set up with Hyper V on my Windows Server 2012 Server.
VM1: Configured to boot from an ISO file and runs Clonezilla server.
VM2: Configured to PXE boot using a legacy network adapter, and with a passthrough 250Gb hard disk.
These two VMs are connected to an external Virtual Switch, which allows physical machines to PXE boot to the Clonezilla server.
For the past few months I have been using this setup for two purposes:
1. To clone physical machines to the Clonezilla virtual server (as a backup).
2. To restore those image to the second VM if I find that need to get access to the files on the original image..
This has worked perfectly, except for the fact that the speed of the legacy network adapter on the second VM (which is required to PXE boot) is very slow. But I know this is because of the limitations in how the legacy adapter works...
Now my problem:
I found out that Gen 2 VMs allow you to PXE boot without having use a legacy network adapter, allowing me to image back to the VM faster. So I upgraded the Server to Server 2012 R2 . I then created the same two virtual machines on the R2 server. I can still
PXE boot the Gen 1 VM to the Clonezilla Server but I cannot get the Gen 2 VMs to PXE boot properly. They get an IP address from the Clonezilla Server but then just stop with the following screen. (note: I have disabled the Secure Boot).
Are Gen 2 VMs unable to pull down images from anything other than a WDS Server?Hi J,
>>Unfortunately WDS is not a solution for us as it is dependent on the PC being part of a domain
If you would like to make the client not join to the domain, please check the box before “Do not join the client to a domain after an installation.” In addition, make sure not to set the client to the domain in the unattend file and do not prestage
the computer in AD. "
It is quoted from following thread :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/1026c3a9-0a10-4a58-a48f-5391659a96c8/wds-set-unattend-file-for-workgroup?forum=winserversetup
Best Regards
Elton Ji
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. -
Can't boot G5 even from OS install disk. Help?
I've trolled the message boards 25 pages deep and searched all the "Can't boot my G5" threads and still haven't found anyone describing what my machine is doing so thought I'd start a new thread in the hopes someone can help me out.
Ok I have a G5 dual processor machine. (Power PC chip, not Intel) Things went bad when I tried to do an Archive and Install of Leopard (OS 10.5) The install looked as normal until I got to one minute left on the install. At that point the install never progressed. I thought maybe it was doing some behind the scenes processing and decided to leave it over night. The next day my machine was still hung on that One minute left. So obviously it was a failure. Of course now the problem is I have an install that never completed of the OS and so that partition is, I assume, unbootable. Wiped away the Tiger OS and did a 99% install of Leopard. So I had to shut down by holding the power button.
I think to myself, "No worries I can just boot from my 2nd partition holding down the Option key to select it on the boot up screen". I always keep a partition with an OS on it for times like these. So I reboot, hold option key, select my other partition, things look OK. I get the grey screen with the Apple logo and I get the wheel animation turning. (Not beachball of death but the typical circular, almost sun ray configuration thing) At this point, usually the screen will go black for a moment before the desktop loads. However, in my case once the screen goes black after the load screen, it stays black. Now let me say the monitor does NOT turn off. There is a definite difference when I manually turn the monitor off. When off it's truly black. But this is like a power on black, not true black. (If you need me to explain this better feel free to ask me to clarify)
So the untouched, pristine Tiger partition boot is a No Go. I figured I'd then give up on trying to put Leopard on my desktop machine (I use it on my laptop) and reinstall the original OS and system software from the system disk that came with my G5. I boot machine holding down eject button, place the disk in, close the drive door and shut down again by holding power button. Reboot holding C key and the same routine happens with booting from the disk. Gray Apple logo screen, sun ray circle moving, screen goes black on the attempted transition to desktop .. but stays black. I also tried booting with my Disk Warrior disk to no avail. Same thing happens. (Also tried booting from disks by selecting them manually from booting with Option key down) At first I wondered if it was a monitor issue. That maybe my desktop was up but there was an issue with the signal being passed to the monitor on the resolution jump. Thought perhaps hitting the Eject key on the keyboard when I had attempted to boot from the partition (not from disk on this test) would tell me if it was a monitor issue. If it was a monitor issue, the disk tray should open. But alas, no.
So since I cannot boot normally from any partition or disk I decided to boot into single-user mode.
I did the fsck -fy thing and it told me everything was ok. I had also previously installed applejack and I ran that and short of correcting a few permissions and dumping some unneeded caches it came back with a system OK.
At my wits end I booted into target disk mode and ran Disk Warrior on both the original half installed OS partition and the back up emergency boot up partition from my laptop. Again, everything OK. Hoped against hope that I could actually install an OS onto my G5 from my laptop but I was only given the option of being able to do it from my laptop with the Leopard disk and it would only allow me to do it if I used Disk Utility to completely format that drive first. No, thanks.
Re-attempt to boot G5. Failure. So now I turn to hardware. Disconnected everything beside the keyboard and mouse. Try again. Fail. Pulled a couple sticks of Crucial memory out of the machine and left the stock RAM. No dice. Pressed the small power unit reset button under the RAM slots. No change. Zapped the PRAM. Still nothing. Try to boot in Safe mode holding down shift key. Doesn't work.
It seems to me if I can't even get the machine to boot from the Install disk that there is something going on that is much more major than software issues.
Bad motherboard? Any ideas? Because I'm all out of ideas.Brother, Sound74, I thought I was the only one pulling the hair out of my chest one by one the past two days. Your situation is very similar to mine, and I'm just as clueless as you are. I started getting kernel panic screens, then nothing on boot, until finally I brought it to the local genius bar. They ran all the usual software/hardware tests, updated Tiger to 10.4.11, recommended I buy Leopard and do an erase-install. My computer, of course, was working absolutely fine by this point. I bought Leopard, came home, backed everything up, then tried to install the new OS. Like in your case, it just up and quit half-way through. Screen went black and a "No DVI Signal" message came on my display (it does this when I turn it on without first turning on the computer).
So I thought, well, maybe it takes a really long time to erase-install, and the monitor is just waiting for things to kick back in. I've always upgrade-installed before, so I couldn't tell if this was normal or not. But about half an hour later, my fans kicked in so fast I thought I had a P-51 Mustang taking off in my studio. I waited a bit more and finally force-shut-down my system. Not knowing what to expect, I nervously tried to re-boot.
Nothing. Zip. I can't safe boot, I can't boot from the installer disc, etc. The only thing I can do is the option-key thing whereby you choose the startup disc. And of course, it only gives the Leopard install disc as an option, because now the entire HD has been erased! But when I choose the Leopard disc, of course it doesn't work.
So I have a nice $3000 paperweight sitting in my studio. I guess I'll have to bring it back to the Mac store, where if it costs more than $300 to fix, I'm going to say screw it and put that dough toward a new iMac.
Sorry I couldn't provide any helpful info, but I just wanted you to know you're not alone in suffering the slings and arrows of outrageous technology.
Keep me posted on any solutions you discover, and I'll do the same.
Noochy1
PS My applecare expired a month ago! AAAAARRRRGGGHHHH!!! **** Murphy and his stupid laws. -
I'm trying to boot a toshiba SP6100 from ris but getting
PXE-T01:File not found
PXE-E3B: TFTP error - File not found
PXE-MOF: Exiting Intel PXE ROM.
No problem what so ever when booting other mashies (Other brands).
When trying to boot from a Remote boot disk i get:
Error: Could not found a supported network card.....
PC is running latest bios (1.9)
Any suggestions?Hi
I have found an interesting Microsoft Knowledge Base Article Q304992.
It deals with the PXE Boot and RIS server method, perhaps it could help you!
Pelox -
Hello folks,
I need your help in following situation.
My source-system has 1 RAID5 (600GB) over 5 HDDs. On the RAID-Disk are one primary partition (250GB) and 1 extended partitions (350GB).
Because the hardware is out of support, I will migrate it to new hardware-server. I must minimized the downtime and the administrative effort. So I can't reinstall a new windows-installation, because 4 different software-licences are binding on SID. Additional
a DFS-R is configured, so I need some hours to reconfigure it.
The new destination-system has one RAID1 (300GB) that I will use it for windows-system, and one RAID 6 (1TB) that is planed for data.
I has make a full backup (with all Critical) by using Windows Server Backup to a NAS storage. Than I has boot my destination system from Windows Server 2008 R2 media, and will make a recover. All Hard Disk is detected, after I install the storage-drivers. When
I confirm the last step in windows-server-backup, windows-backup stop with error "Not enough space on harddisk 0"
How can I move the extended partition to harddisk 1 (RAID6) durring BMR??? I cann't exclude the volume in backup-procedure, because the DFS-R is installed with some share on this disk.
Has anyone a idea?
Best regardsHi,
I'm afraid we will not get it resolved. BMR will restore the partition information so you need at least a 600GB disk/RAID to restore both Drive C and D - it will create partitions on disk/RAID but cannot be separated restore to different disks/RAIDs.
How about get another 300GB disk and change your system RAID from RAID1 to RAID5. (Or change RAID1 to RAID0 but of course you will lose fault tolerance ability).
If you have any feedback on our support, please send to [email protected] -
Have an ultra 20 which was fully loaded with o/s, patches and other software. The box I used to jumpstart had to be rebuilt and this Ultra 20 was a good box to test that with. I went into setup and set the box to boot from PXE which worked, except obviously got into a loop of installing the when it rebooted at the end of jumping. So I happened to wait to enter setup and changed the boot setting back to the original setting.
What is the right way to do this? I didn't want it to reinstall but I was stuck on the phone when that happened. What options do I have? IIRC, originally, I used a DVD to run the PXE boot, but can't recall.Hello Monarch,
if we're talking Linux:
on your bootserver, change the bootfile in /tftpboot/pxelinux.cfg to something like
DEFAULT localhost
LABEL localhost
LOCALBOOT 0after machine boots to install. It will boot from disk the next time. There are packages which do this by themselves automatically, like systemimager.
Cheers, Peter.
PS: Can you do me a favour and check if the output of dmidecode run as root tells something about IPMI? -
i already read the hardware requirements for solaris 10.
https://www.sun.com/software/solaris/specs.jsp
but is it possible to PXE boot with only 256 mb ram? since 512 mb is only a "recommended amount"I think so, it depends on how much RAM the installation program want, but i think 256 is enough if you dont run the install GUI..
.7/M. -
Default PXE Boot.wim "stuck" and cannot be changed
We would like our default PXE boot.wim to be the x64 boot.wim. Somehow, it has been changed to x86 and it cannot be changed back. I am aware of the method by which config manager chooses which disk to use (last deployed TS to a collection), but despite creating
multiple deployments utilizing the x64 disk, it is still defaulting to the x86 one. We have 2 main collections that TS's are deployed to, and both of them have a most recent deployment using the x64 disk.
Anyone have any ideas what is going on, or where I can look to get this changed?Hi,
Do you mean the clients are still trying to boot from the x86 iamge?
You referred that you have deployed task sequence via the iamge. Is the task sequence still bind with the image? -
Issues with Boot Images & PXE Booting Since SP1 Install
Good Afternoon All -
I recently updated to SP1, had some issues, but they got resolved. Now, though, I'm having an issue booting to PXE as well as updating any boot images created
before SP1 was installed. Booting to USB Bootable media using a newly created boot image seems to work fine.
Boot Images
When I update my DPs for any of my boot images in SCCM, they fail and i get the below error:
Error: The wizard detected the following problems when updating the boot image.
• Failed to install required components into the boot image
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4566;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"BBS0012F\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;
I've even gone as far as removing all drivers from the boot image, but still get the same message. I was able to create a couple of
new MDT boot images which seem to work fine, though. I am not sure which log file is for boot images, but nothing appeared in distmgr.log.
PXE Booting Issue
After trying many things, I removed PXE config from my site and uninstalled WDS then started all over again. Here's what I did and my results. Please tell me what I'm missing...
After uninstall & server reboot, I enabled PXE + every option in DP tab in SCCM
It automatically installed WDS (same server) and added the two boot images I had checked for PXE use. one x64 and one x86.
I checked my DHCP Scope whose values hadn't changed sine it worked (that I know of). They are:
Option #66: 192.168.20.37 (SCCM Server/DP/PXE)
Option #67 \boot\x86\wdsnbp.com. I've tried \boot\x86\pxeboot.com as well as each of these with x64.
When I PXE boot from a workstation, I receive an IP, a bit of info, then it goes to Contacting Server.... When trying one of the boot files above, I was prompted for F12, but receved a blue screen with error. When trying all other boot files,
they just hang at Contacting Server until they timeout.
I looked at SMSPXE.log and found something interesting...
The IDs for the two boot images I have assigned to PXE are ABC003B3 & ABC00B36. In the smspxe.log, though, it keeps repeating "could not find boot image ABC0012F! 12F does exist and is a boot image,
but not the one I want to use by any means and does not have PXE checked.
I went ahead and checked 12F, updated DPs (which failed - see above); unchecked it; then updated the DPs again. PXEBoot.log showed that it was trying to remove the 12F files from RemoteInstall which was a good sign. I then restarted the WDS service
and tried PXE booting again. Yet again, it failed and was still looking for 12F.
Any suggestions / Ideas??? Thanks!
UPDATE 1
I just changed option #67 to \smsboot\x86\pxeboot.com then restarted the WDS service. I booted to PXE and this time was asked to hit F12. I did so and it looked as if it would work.
Instead, I got a blue screen with the following error:
Recovery
Your PC needs to be repaired
The boot configuration disk contains errors or is missing
file: boot\BCD
Error Code: 0x000000f
I think that it's the same error as before, but is blue instead of black due to new Win8ADK perhaps. Thanks
Ben K.Update 4
Sorry to make this the longest post ever :)
I just read that others with this error checked DISM.log. I did so when running a DP update for the boot image and got the below errors:
2013-01-11 16:27:04, Info DISM DISM Provider Store: PID=1636 TID=5104 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2013-01-11 16:27:07, Info CBS Failed to find a matching version for servicing stack: C:\Windows\TEMP\BootImages\{DADCFE01-3557-4058-99CC-2A15EDF905AF}\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\
[HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2013-01-11 16:27:07, Info CBS Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2013-01-11 16:27:07, Warning DISM DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\MsiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-01-11 16:27:07, Warning DISM DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-01-11 16:27:07, Error DISM DISM Package Manager: PID=4104 The package WinPE-Scripting-Package is not applicable to the image. - CPackageManagerCLIHandler::Private_ProcessPackageChange
2013-01-11 16:27:08, Info DISM DISM Package Manager: PID=4104 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2013-01-11 16:27:08, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{DADCFE01-3557-4058-99CC-2A15EDF905AF}/mount/Windows/System32/config/SOFTWARE,
the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
(The above one appears 8 times - almost in a row)
2013-01-11 16:27:08, Error DISM DISM Package Manager: PID=4104 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081e)
Help! Thanks :)
Ben K. -
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. -
I'm having an issue getting my Imaging server to work. I've have MDT 2012 Update 1 running on Windows Server 2012.
Every thing was working fine until recently. I've tried to find an answer to this but so-far haven't run in to the answer.
Here are the details. I'm trying to image and HP DeskPro 600 and I can get it to PXE boot but when the windows splash screen comes up it does not proceed to the MDT login screen to start the process. If I use a USB stick that has the boot IOS
on it I can get through the complete script and start the imaging process but it hangs when it come to formatting the disk. I'm wondering it the issue might have something to do with UEFI. We do disable that function on our computers before we
image and like I said it has worked in the past. Currently I'm moving WIM file to another server that has MDT 2013 installed and they seem to work fine on that server. So, do you thing an update from 2012 to 2013 would solve the issue I'm
having? Or if someone has had this issue and has a fix for It I would appreciate some help in this area.
Kris
Kris Da San MartinoGut;
It seems like your issue is just the reverse of mine. I'm not booting to the 32 bit LightTouch on the DC600 and I'm not having any issue with other models of the HP computer.
They all seem to image fine. It's just the ProDesk that is giving me stress. But just to cover all the basses I downloaded the latest storage driver and will try that out to see if it works.
Everything else I have tried has failed to fix the issue so-far.
What version of MDT are you running their? I've been thinking that moving to 2013 would fix this issue so that's why I ask.
Kris Da San Martino -
PXE Boot a client to connect to a Remote Desktop Session Host/Terminal Server Farm via SCCM 2007
Hi all,
we've got a bunch of old desktops which are destined for disposal but i was wondering if we couldn't use them as disk-free clients to connect to our Remote Desktop farm. I did some digging and have managed to put together an iso which will boot
the machine into WinPE and then connect to our farm. However, since it's an iso i have to use either a cd or usb for this to work. (This is pretty much what i did: http://www.iammacgyver.com/2011/02/easy-rdp-60-from-winpe-30-simple-boot.html)
What i want to do is to advertise the boot.wim to the client via SCCM so that it boots via PXE and then picks up the WinPE image and connect to the RD farm. I've imported the boot.wim file into SCCM under Boot Images and created an empty Task Sequence
with the boot.wim as its Boot Image. I then advertised this Task Sequence to a collection which contains the old desktop clients. The machine PXE boots ok and loads up WinPE but rather than launch a remote desktop connection, it trundles through the normal
WinPE stages and once it's finished 'Preparing Network Connections' it simply ends and the client reboots.
Is what i'm trying actually possible?
Can anyone tell me why the ISO works yet pushing the boot.wim out as a Boot Image doesn't? I know the boot.wim file (which is the same one present in the ISO) is ok since the client boots into WinPE fine when PXE booted so why doesn't the remote
desktop session conenction launch? How is booting from the ISO different from booting from the PXE boot.wim file?
Slightly long winded problem so many thanks in advance to anyone who can pass some info my way!It doesn't work because importing it into ConfigMgr injects binaries and the task sequence engine along with the process to launch the engine thus suppressing whatever you've got configured.
Perhaps you could use a pre start command (pre-execution hook in 2007 parlance) to launch your RDP process though.
Jason | http://blog.configmgrftw.com | @jasonsandys
Maybe you are looking for
-
I know there is a way to add a user to a paid membership subcription using the web form. There is a video on BCGuru that shows how to do it. Is there also a way to use web form for the user to terminate his paid membership? Or does it always have to
-
MBP Pro Qmaster Start Sharing Greyed Out
I have fcp studio 2 and MBpro and dual g5. On my G5 in the system preferences for qmaster none of it is greyed out and sharing is on. On my MBP It is all greyed out and I can not select any options or click start. ANy ideas ? On the g5 in activity mo
-
Anyobe ever hook their ibook up to a widescreen lcd hdtv/monitor?
i just got a sharp aquos 32" hdtv monitor. i have a s-video output cable for my ibook and i want to hook it up to the tv. i know it won't display 720/1080 but will it look good? will my ibook display a resolution suitable for a 32" widescreen as if i
-
Transferring songs from your phone onto a new computer
i recently bought a macbook pro and connected my iphone 4 to it and it said transferring purchases, after about 20 minutes it had finished transferring but it only transferred the purchased songs. it did not transfer the other 400 songs on my phone,
-
Oracle 9i Application Server+Oracle 8i EE+ Forms on the web Very urgent
Hi, I have correctly install Oracle 9i Application Server and Oracle 8i Entreprise Edition on Windows 2000. What are the following steps to follow in order to run a form on the web. example: test.fmx? Thanks in advance. null