JumpStart Network Boot problem

Network boot of Ultra 10 test machine from JS environment on a RedHat FC3 box all works perfectly with a Solaris 9 (0404) kernel and network boot directory structure.
When attempting jumpstart with a Solaris 10 FCS kernel and jumpstart environment, after
boot net:dhcp - install
I see usual boot device stuff, then the tftp transfer of
38600
and then
Requesting Ethernet address for IP.AD.DR.ES
boot: failed to allocate 8192 bytes from scratch memory
panic - boot: boot: scratch memory overflow
Program terminated
ok
All the refs I can find to the scratch memory overflow problem suggest a problem back in the days of a Solaris 8 kernel that a later patch solved anyway.
Firstly, has anyone one else seen similar errors to mine with a Sol10 JS ?
Secondly, has anyone any other ideas as to what's going on here (other than the unlikely chance that I have a Solaris 8 kernel inside my Sol10 JS environment !!)

This is an old thread, but I found it along my searches for the same issue - only one Sun box, and no CD/DVDROM.
I had exactly the same setup - FC3 jumpstart server which worked fine for Sol9, but failed with Sol10. The Sol10 NFSv4 client has difficulties during install talking to the Linux NFS server. One can work out the issues, installing NFSv4 - see http://www.citi.umich.edu/projects/nfsv4/linux/ - and fixing a few other problems - see http://www.tzone.org/~vandry/howto/solaris10-install-from-linux.html - or move to a FreeBSD or NetBSD jumpstart server.
I wrote a little how-to on setting up a FreeBSD jumpstart server for Solaris 10 which can be found at http://www.pbandjelly.org/item/38
I hope this can help out those people trying to find a solution in setting up their Sun with jumpstart.
Kind Regards,
Michael

Similar Messages

TFTP Read Access Violation in Snoop while doing network boot

Hi
I have setup my Oracle dhcp server and AI on oracle 11.1.
configure the /etc/ethers and /etc/hosts file as well.
pntadm and dhtam is also setup with macro
I deplou solaris 11.1 AI sparc image as my service
create-client and manifest is also associated as per client machine Mac interface
On client machine
I created the devalias entry for my Nic interface
did now
boot net:dhcp
Requesting Internet Address for 0:e:1E:8:bf:f8
Requesting Internet Address for 0:e:1E:8:bf:f8
Time out waiting for tftp reply
On server machine in snoop its showing
tftp read "01010F19" (octet)
TFTP Error : Access violation
I check tftp service is running on server as below
/usr/sbin/in.tftpd -s /etc/netboot
Please help me i am not able to figure out whats the problem
Thanks

But even on dhcp it doesn't work without setting network-boot-arguments on OBP
If i don't feed any entry in /etc/ethers and /etc/hosts
whenvever I do on client side boot net:dhcp it always give rarp messages in the snoop on server.
What can be the reason.

WDS Windows Server 2008 R2 network boot PXE x86 UEFI support?

Hi,
WDS Windows Server 2008 R2 network boot PXE x86 UEFI support?
-I have an SCCM 2012 SP1 site on Windows server 2008 R2.
-I have an HP ElitePAD 900 with Atom x86 processor, and I have some problem to deploy an OSD image to the ElitePAD.
Do I need WDS on an Server 2012 to get PXE x86 UEFI support with KB2817245?
http://support.microsoft.com/kb/2817245/en-us
/Per Sai
/SaiTech

Is this why I get this error with 2008R2?
Windows failed to start. A recent hardware or software change might be the cause. To fix it... <blahblah>
File:\Windows\System32\boot\winload.efi
Status: 0xc0000359
Thanks,
Jason

IBook boot problems

Hello, My iBook recently won't boot correctly. It goes to the login screen and then goes to a full screen terminal and asks for my password. The only password that works is the root password. Now this happened after I installed the xvid codec for quicktime but as far as I know that couldent have caused something like this. So in trying to fix this I rebooted the computer into single user mode and removed the applesetupdone (/var/db/.applesetupdone) file to hopefuly get the computer to just go through the intl. setup. Well that didnt work. Now it gets stuck in a loop saying it cant load up the intl. setup. I can still get into single user mode though so it should still be fixable. If not I think the mac has smbmount so I could just move my files over to my friends computer and reformat. I know this problem was not caused by my dual boot because its been running fine for about 2 years. Could anyone tell me how I could fix this boot problem or how to startup the network services in single user mode.
Thanks, Spazo

An update. . .
Booted in TDM and wouldn't show up on my MBP, however could view it in disk utility. It wouldn't let me mount it though. I've tried repairing however after an hour still nothing. Here's the info notes. I'm getting the impression the hard drive is damaged beyond repair.
Name : AAPL FireWire Target Media
Type : Disk
Disk Identifier : disk1
Media Name : AAPL FireWire Target Media
Media Type : Generic
Connection Bus : FireWire
Connection Type : External
Connection ID : 2979676490117816
Partition Type : Applepartitionscheme
Device Tree : /PCI0@0/PCIB@1E/FRWR@3/node@a95fffebd32b8/sbp-2@4020/@0:0
Writable : Yes
Ejectable : Yes
Mac OS 9 Drivers Installed : Yes
Location : External
Total Capacity : 27.9 GB (30,005,821,440 Bytes)
S.M.A.R.T. Status : Not Supported
Disk Number : 1
Partition Number : 0

Disable network boot screen in KT4V-L

well this is more of an annoyance than a problem . . .
i was booting up a few days ago and on the screen where u can press (BIOS 1.5 and previous) or (BIOS 1.6) to boot from a network . . .
now i decided to venture into this menu and played around with the options and now a new option comes up after the / screen comes on . . .
it now says something like "press to boot from hard disk" . . . now is there a way to disable this message of booting from the hard disk? or the whole network booting option at all?
my pc boots up fine and i haven't experienced any problems but it just takes up a lot more time to boot into windows . . . i've tried every bios setting possible from disabling everything in the boot menu order, to disabling the network adapter . . . now the only thing that works is by disabling the onboard adapter which i use . . . i've also tried flashing to other bioses in hopes to reset it but it hasn't done anything . . .
does anyone have any suggestions on how to disable this?

oh this is before windows even loads up . . . it's a message from the bios/lan rom itself asking to press to boot from the hard disk or pressing to boot from a network . . . in fact, i get no slowdowns going into windows at all . . .
when u do a cold boot, u get the following screens:
1. the main post screen where u're ide devices get detected
2. the screen that i described above comes up where u press and for network booting
3. the computer configuration info (pci devices, cpu, cache info, etc)
4. boot record search from the floppy/hd/cdrom
5. windows boot screen
it's screen #2 that i'm trying to disable . . .

OS/X 10.4 boot problem

I am having boot problems where I end up at the command prompt (see messages below). I need to get a file from my hard drive to a USB flash. How can I mount the USB drive and copy a file from /user/Documents? Or, is it easier to mount a network share?
CSRHIDTransitionDriver : : probe: 0x0 -v
CSRHIDTransitionDriver : :start before command
CSRHIDTransitionDriver : :stop
IOBluetoothHCIController : :start Idle Timer Stopped

booting into Target mode was easier

Is PXE network booting supported on 875p Neo FIS2R?

Hi all,
I have spent a full day trying to get my computer to boot via PXE from a remote server. My computer is equipped with an MSI 875p Neo FIS2R motherboard.
relevant stats are as follows:
Motherboard: MSI 875p Neo FIS2R
Ethernet Card: Integrated on Motherboard (Intel 82547EI (CSA Interface Gigabit LAN))
The PXE server to which I am trying to connect is running Windows 2000 Server and is configured with Windows Remote Installation Service. The server has been tested with another pxe client (my laptop) and I am able to boot over the network succesfully. It looks like everything is configured properly on the server side.
I am using the msi motherboard's Intel 82547EI integrated ethernet controller when attempting to connect to the server. I do not have another PCI ethernet controller that I can try as an alternative.
I could not find any mention of network booting in the boot sequence section of the BIOS configuration, nor anywhere else in the BIOS settings. I have made sure the integrated ethernet controller is enabled in the BIOS.
I also upgraded the BIOS to the most recent version (2.4) but there is still no sign of any 'network boot' settings in the boot sequence nor anywhere else in the BIOS settings.
See the following webpage for the BIOS versions:
http://www.msicomputer.com/support/bios_result.asp?platform=Intel&model=875P%20Neo-LSR/FIS2R%20(MS-6758%20PCBv1)&newsearch=1
Note that BIOS version 2.2 specifically mentions:
"This BIOS fixes the following problems of the previous version:
- System cannot login to PXE server without floppy drive installed."
This seems to suggest that the motherboard supports PXE. While I do not have a floppy drive installed on my machine, this BIOS update indicates that a lack of a floppy drive should not pose a problem.
When booting the computer I am presented with a few keystroke options, one of which is to press F12 for a 'Network Boot'. After pressing F12 I receive no indication that the computer is attempting to contact a PXE server and the computer boots into Windows XP as usual.
I have searched the MSI forums and have yet to come across a solution. Signs point to there being PXE support but I must be missing something. Can anyone give me any definitive answers here? Thanks in advance.

I've since been in contact with MSI technical support. Oddly they cannot seem give me a definitive answer on the support of PXE in MSI motherboards so again I'm turning to you guys. I'm really hoping someone out there has some experience with PXE and any sort of MSI motherboard. Surely someone must have run into this issue before. Anyone? Anyone at all?

648 Max Booting problems.

Ok first off hello to all the people here. I am hoping somone can help me with what is going on here.
Everytime I power on I get the nice first little beep. This is a blessing since my previous 2 boards would not even post. After my first little beep it goes on into boot and then beeps one more time followed by a pause and then 2 more beeps. Then it brings up if I want to go into setup,boot,or network boot. And then at the bottom it will let you go press F2 to continue into boot mode. Well after I press F2 it will go into pre windows and give me the option of safe mode or normal. When I choose safe mode it loads and my usb mouse will not work. When I choose normal sometimes Windows will boot and sometimes it will not. Most of the time it doesn't. It just goes into a black screen with a dos like cursor at the top and then the monitor acts like it goes into sleep mode. Everytime it does this I have to go in and short the jumper pin to bring it out of whatever is happening and it then looses all my bios settings. I am running the 648 board, 2.66 P4, 120 gig wd hd, 1024 mb of Geil memory, Ati 9700, Sound Blaster Gamer, Plextor burner, and a Dvd drive. It has confused the hell out of me. It seems like I have tried everything to fix this and nothing is working. Any ideas? Thanks ahead of time. ?(
Bowlsie

That combination of motherboard and graphics card, (definitely) needs a good power supply. What's yours rated at?
Also, go back through some of the earlier posts. Should be able to find some things relating to the Radeon9700.
Run memtest86 to check RAM for errors.
Sounds like a power supply problem to me though.
Also, that 1G of RAM, is that 1 stick?

K7N2 Delta-L: Strange cold boot problem & solution

My K7N2 Delta-L has a problem cold booting when the vcore is set in the bios at 1.65v of higher. After a cold boot, you get a blank black screen. I noticed that even if you run at default speeds but set the vcore to 1.65v of higher the problem still occurs. There is no problem rebooting however.
I found the following solutions:
1. After you power up and get a blank, hit the reset button.
2. Don't unplug your PC. My PC is connected to a AVR and after I power down the PC I usually turn the AVR off. If i do this, than the computer will have a booting problem if I try to boot it up 30 minutes later or so. Now if I don't unplug it/power off the AVR than everything is fine.
I don't understand why it acts the way it does though.
Does anyone know of any other solutions?

Have you cleared the cmos. If you do be sure you have the power turned off don't move the cmos jumper with the power on.
I found that turning off power at power supply and unpluging, than turning on the computer the fans will spin just a little this drains all the power. Clear cmos 2-3 than return to
1-2 position.
Than plug the power back in and turn it back on, than try the computer again.

Mid 2006 iMac Boot Problem (Since latest firmware update)

I have a Mid 2006 17" iMac. Ever since the latest firmware update in early December, about every other startup I've been having boot problems. After the white screen with the Apple Logo and the spinning wheel it goes to a blue screen like normal, but instead of the 'Loading Mac OS X' white window popping up it stays blue and the spinning loading wheel starts. I've left it loading for quite a while before and nothing changes. I have to do a force shut off by holding the power button. and then I start it up and it will boot normally.
Any help would be appreciated.
Thanks!

Actually, I think it'san early 2006.

1st series iMac G5: Booting problems, kernel panics, waking from sleep...

Specifications of the iMac described: 1.8 Ghz, 1GB, 80GB, 64 Mb Nvidia VRAM, Airport, 10.5.5
Back in August 2004 my dad bought us kids an iMac G5 for ‘family use’. It had a fresh install of 10.3.5 on it and compared to the (1999) iMac G3 it replaced it was amazingly fast.
The iMac never showed any signs of probable issues, until we decided to upgrade to Leopard in January 2008. Initially, this upgrade was only meant to be able to sync with the latest iPod nano (who demanded a newer version of iTunes).
After the installation the first thing I noticed was a high CPU usage, the machine seemed slower than ever and that with 1 Gb of RAM (the minimum sys. req. for Leopard are 512 Mb of RAM). Anyway, then the real thing started, it wouldn’t turn on anymore. We brought it to an Authorized Apple Reseller, the Tech department said the Logic board had failed. The costs of the fix weren’t the worth the computer anymore, so...end of story. The iMac was indeed one of the bad series, although it hadn’t any swollen capacitors.
My dad already made up his mind and bought himself a Macbook. He then told me that if I was able to get the broken iMac fixed, I could keep it. And so, I bought an ‘as-is’ logic board on Ebay. Last weekend I installed it, and it actually seemed to work! Yet, the problems are during the startup: the first thing I see is a screen full with horizontal lines flickering all the time, like an old TV with bad signal. Mostly it won’t boot and I get the message to restart the computer (kernel panic, I got dozens of logs already!). Sometimes it got stuck during booting (grey apple screen with gear in the middle) making the fans go crazy (after a while) and sounding what others describe as a ‘jetliner taking off’ sound. Sometimes the screen remains black. Generally it takes me 5 to 10 minutes to start up properly. Maybe it’s just me but it seems like when the computer has warmed up a little (by turning on and off on and on) starting up gets smoother. I mean the startup screen suffers from less horizontal flickering lines.
During the use of Leopard, I again get high CPU usage, especially when I use multiple programs at the same time, or when starting multiple programs. My iStat Pro said once that the fans were running at 4700 rpm and the heat of the CPU was about 70 Celsius. If I really want to **** my iMac off I should play a racing game. That just totally freaks him out! These problems could probably be solved by adding more RAM. Right?
The iMac also has a sleep problem. Sometimes after lets say an hour or so, you can’t get it out of sleep mode (by manipulating keyboard and/or mouse, the sleep light stops, but the screen stays off --> only solution is to restart). What happened to me once was that it slept so long that it just got into a deep sleep by turning itself off completely!
Here’s a list of what I tried so far:
- Disk Utility: Resetting the permissions, no problems were found.
- Resetting the SMU, both on the logic board itself as by pressing the power button 5 - 8 seconds, no improvements.
- Resetting the PRAM, no improvements.
- Did the Hardware test of the original install CD, nothing was found, all good.
- Did Archive and Instal, this actually messed my system entirely, cause it wouldn't boot at all and when starting up from the Leopard installation DVD it wouldn't recognize the Macintosh HD.
- Did Archive and Instal with the original disks, this disk did recognize Macintosh HD and so I installed the original system, 10.3. Booting problems and those flickering lines are still there though.
Next phase will be erase and install, but first I want to know what you guys think about all this.
Oh eh, One more thing; The guys at Applecare (phone support) told me that the replaced logic board was also out of warranty and so they couldn’t help me. But as the man on the phone was kind, he told me to go look for a special ‘driver’ on the net. He said that the driver should be able to resolve some of the issues described. He said that I had to give in the name of the LB on google and look for results. Is this bogus? Because I haven’t found anything useful on google so far. What’s the name (rather than a number) of the LB in the first place?
I hope you guys can give me some answers. I'm kinda desperate. But I still feel there's hope...

The symptoms of a flakey power supply are sleep problems and you have done all the right things as far as resetting the SMU and PRAM. Your CPU usage can be tracked by going to Utilities>Activity Monitor - look and see what is hogging the memory. The flickering lines could also be an optical system going south.
The other thing you can do is run DiskWarrior or TechToolPro to see if you have corrupted directories. Preferential Treatment will let you check for corrupted preferences.

MSI P45 Neo-f with intermittent boot problems

Current system:
*CPU: Intel core2duo 4300 1,80GHz
Mobo: MSI P45 Neo-F LGA775
*Memory: 1 Kingston 1GB PC2-5300 667MHz DDR2 and 1 Dane-Elec 1GB PC2-5300 667MHz DDR2
Videocard: Club3D Nvidia 8800GT 512MB GDDR3
*Hard drive: 120GB IBM deskstar 7200rpm Ultra-ATA/100 (yes I realize it is known as the deathstar, but it hasn't failed so far, I do back-up because I'm paranoid
PSU: Real Silent Nexus NX-5000 500 watt
*Soundcard: Soundblaster Audigy
OS: Windows XP home, service pack 2
*Lite-on IT dvd-rom drive
*floppy disk drive
I also have 3 case fans spinning away in a marginally large Chieftec Dragon tower.
The parts I marked with an asterisk (*) are parts that I removed from my old rig and re-used.
I'll try to give a clear rundown of my problem and the steps I've taken so far.
3 days ago I acquired the P45 Neo and installed it into my system, together with the 8800GT videocard. I was still using my old PSU, a Chieftec 360watt. This PSU served me well for 7 years, but it was starting to build up noise while trying to keep up games on my old rig.
I had some trouble getting the system to boot, I tried changing some of the 4 pins wires going to the hard drive and the dvd drive. I don't know if it was luck or if I managed to divide the load properly for the system to boot. But I succeeded into booting up, got into the bios and eventually installed WinXP.
As soon as it was time to install the videocard drivers, it stopped responding. I assumed it was a power issue, since I could only install the 20pin and 4pin cpu, but my Chieftec PSU didn't have a 24pin plug to the mobo - and it needed replacing anyway! So I bought a new 500watt PSU that had all the required plugs and more wattage.
I installed the new PSU, checked every connection and pressed the power button. 'Lo and behold, the computer starts up. I install the videocard drivers and it proceeds with no problems. I try to install the soundcard, but the cd says I don't have one installed. I fix that by going to the System list and install the drivers from there. I install a firewall. By then I have successfully rebooted the computer 3 or 4 times. I decide all is well and turn off the computer. But I realize I wanted to check up something on the internet.
I press the powerbutton. The PC power light go up for just a fraction of a second. I can see the blue LED of one of the case fans switching on just as briefly - then it goes out. The computer keeps trying to turn itself on. It looks like it's hickupping to try and boot!
I turn off the PSU power on the back-side because the computer keeps trying and wait for a bit. After 10 minutes, it still doesn't work. I leave the computer for a bit and return an hour later. The computer then starts up with no problems. I turn it off after a few hours, do a reset, start it up, no problems. But then the next day it happens again.
It's pretty tough figuring out what the problem is because it looks..almost random. I considered it could be a heat issue, but sometimes it *does* start up just after it's been turned down. Checking the bios shows no strange temperature shifts.
Hope anyone can help me, because I do not want to go back to my old Asrock mobo

While powered down I cleared the cmos data, removed the Dane Elec DDR2 module and set the bios to optimized defaults. Computer restarted to WinXP with no problems (it has been off the whole night). I shut down WinXP, wait a few moments and then turn the computer back on. Alas, it won't start and starts hick-upping. I turn power off at the PSU again, so it stops.
Now I try switching out the Kingston module instead. By now the computer has been off for 10 min (while I write this entry on laptop). I press the power button on the PSU and then the power button on the front. There is a short pause, lasting a second. The computer turns on, longer now, but it only lasts 2 whole seconds before it turns off again and goes on again (I believe now you can call it powercycling). It repeats this process until I shut off the PSU.
I check to see if I have installed it properly and try again but it starts powercycling again.
15 min pass, I put the Kingston module back in, press the power button and voila, this time it does start. WinXP shows up, no problems. I leave it on for a bit and then shut down. And when I press the power button again - the feeling of dread returns, when it starts hickupping again.
I'm going to see if I can install one of the memory modules from my housemate. Then hopefully tommorrow, I'm going to try if I can test a different PSU, since I see someone else on the forum - who recently posted, has the exact same power supply and also has boot problems, coincidence... or not ^^;.

My daughter has just bought me an iPad 2 from Dubai and set it all up for me but unfortunately the iMessage function doesn't seem to work. We keep getting messages,when trying to activate it, that there is a network connection problem - help!

My daughter has just bought me an iPad 2 from Dubai and set it all up for me but unfortunately the iMessage function doesn't seem to work. We keep getting messages,when trying to activate it, that there is a network connection problem - help!

Thank you both for your responses but my daughter was reassured by the salesman in the iStyle store (official Apple store in the UAE) that iMessages would work but conceded that FaceTime wouldn't. My iTunes account is registered in the uk and my daughter's iPhone has iMessages even though she bought it (and uses it) in Dubai. Can anyone else throw any light on this?

I have an early 2008 Mac Pro, which has re-booting problems. Also what does the spinning beach-ball indicate?

Hi, I have an early 2008 Mac Pro which has re-booting problems.
Processor speed is: 2.8
Memory: 2GB 800 MHz DDR2 FB-DIMM
2 x 28GHz Quad Core Intel Xeon
I am running OSX Yosemite Version 10.10
My Mac Pro keeps re-booting. Last year I had to replace my graphics card. My original card was the ATI Radeon HD 2600 XT 255MB, and that is what I have now. At this precise moment my Mac Pro is running perfectly, except that it is slow and the spinning beach-ball keeps appearing. I have managed to do some work with the disk utilities, verifying, cleaning and partitioning. Some errors were found and when it was cleaned this seemed to help my Mac Pro to function properly. Although I am able to use my Mac Pro now, from day to day I still experience re-boot problems. Also quite unexpectedly my mac dictionary has an error, it closed itself down and will not open at all, I had the message to say that a report will be sent to Apple.
I have tried starting my computer with an external hard drive fitted via a USB cable, I use for back-ups. This worked and I was able to wipe my hard drive clear and replace all info from the back up I had done only a few days ago.
This worked for a few days and then the same problem started again.
I am beginning to wonder if I need to buy a new hard drive.
If there is anyone who has some answers to help me solve my problem, I would be most grateful.
Robert

When you have the beachball activity, note the exact time: hour, minute, second.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

Windows 8.1 pro boot problems

I upgraded my OS on a hp pavilion g6-1d73us from windows 7 home premium to windows 8.1 pro and ever since I have had boot problems. I took all the software off since I thought that might be the problem but the boot problems persist. The computer's self diagnosis helps but I still have problems. Is my laptop incompatible with windows 8.1? Windows 8.1 was a download and I still have recovery disks for windows 7. I originally thought the problem was incompatible software but now I am not sure.

Hi @hifive11 ,
Thank you for visiting the HP Support Forums and Welcome. I am glad you have recovery disks for windows 7, smart thinking. I have looked into your issue about your HP Pavilion g6-1d73us Notebook and having issues with the Windows upgrade to 8.1. Here is a link to the drivers page for your product. I do notice there are drivers for Windows 8.The Updates you need for the system are the Chipset. These are located on the driver page link above.
One of the things that can cause an issue is things connected USB. The computer can not load the drivers so it causes an issue. Once the machine is up to date then return the USB devices.
Then I recommended to restore the BIOS to factory defaults.Here is a link to restore the BIOS.
You can do a system restore. System restore will help if something automatically updated and did not go well on the Notebook.
Please note remove any and all USB devices. Disconnect all non-essential devices.
Hope this helps.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

JumpStart Network Boot problem

Similar Messages

Maybe you are looking for