Refresh,

I've now a Next Device Boot on my test server...

I try to restart PXE Services...

On my PXE Server (NS too), each time I launch a client Update, it launches Bootwiz.exe...

Greg

After recreate Winpe Configs :

PXE-E77 Bad or Missing discovery list

Try TECH140957, 127591 and 138155

It seems (with the TEHC127591) that the 3 files when I start pxe services, are not created. But all ini files are OK.

GREG

If there is no solution,

Is there a procedure to uninstall / reinstall properly the PXE on my SMP server ?

Thanks

Did you happen to check the service startup order indicated by (referenced by TECH140957), it seems to be a common cause of problems in this arena:

www.symantec.com/docs/TECH127275

Yes,

I did this check.

There is no order for PXE Services.

GREG, I've seen the issue when a single configuration addresses both x86 and x64 architectures and Unknown computers was turned on. To address my issue I created two configurations WinPEx86 and WinPEx64.

Now, PXE-E77 Bad or Missing discovery list  could happen in a couple of scenarios.

1. If you start the PXE services and boot a client before PXE server is ready you would get that.  A way to tell PXE is ready is check \\localhost\deployment\task handler\sbs\sbsstore there should be 3 files that get created everytime the services start. Settings, PXE Images and client data once you see all 3 files give PXE 30 seconds and you are ready to go.  I know this sounds like a pain but once you know what is going on it works.

2. this one is more complicated. Browse to \\localhost\deployment\task handler\sbs\images\config_name\x86pc see if there is a dummy.0 file then thePXE image is not ready. Do the same for x64.  The problem here is that PXE image was not processed by PXE (PXE Service does this) and for sure you will get PXE-E77 because the dummy.0 is zero bits in size and not a valid .0 file.

Hope this helps.

Nelo

Thanks Nelo !

If there is no order for PXE Services, I can put these on Automatic Startup ?

Your solutions doesn't resolve my problem. The 3 files were not created when PXE started...

I've to fully uninstall and reinstall my DS Suite.

I create a first PXE Winpe preboot. It works.

Today, I try to create a second Preboot. My Console freezes when I try to access the Preboot config page.

I've to reboot the server and wait (Bug ?) (My menu was correctly created in my SBS folder)

When preboot config is created,BootWiz.exe process is running in background which consumes CPU usage and so your console might freeze.Its a known issue.

However,do inform if you were successfully able to create 64bit preboot image and boot to that PXE image.

Then the PXE Server service will NOT bind on the ports and respond to PXE requests.  This is documented in the Architecture and Dataflow document.

What you need to do is troubleshoot the 3 files not being created.  Period.  Until that is resolved, nothing else matters.

At this point, it would appear you're chasing 2 issues, so you would probably be best to either 1) open a case with support or 2) branch off into two threads.

What are the issues?  1) a menu not showing up and 2) PXE E-77 when trying to PXE boot.  You're going to get confused quickly if you're not careful.

Relative to the PXE E-77 or any other of those "kinds" of errors, again, first look for those 3 files.  Wipe SBS Store folder and be sure that it's created and 3 files created.  Again, in the Architecture and Dataflow document, we tell you how all this happens.

Relative to Start Order, Nelo is mostly correct.  But in answer to your question, yes, you can and should set all the services to auto-start to ensure they're running after reboots.  There actually IS a start order, but it's relative only in situations where the starting of services is WIDELY separate.  As long as they all start in approximately the same time frame (i.e. within about 5 minutes of each other or so), then it'll be fine to have them start in any order.  Also documented in the Architecture and Dataflow document.

Relative to the x64 option not being listed - not sure now that the waters have been muddied from the other issue.  I'll make sure my x64 option is listed.

However, I will mention that if you have a single configuration that marks both X86 and X64, that will be listed only once - not twice - in the client's menu.  This is also not recommended to use.  X86 is just fine for MOST DS automation tasks.  The only scenarios I know of that require x64 are:

• Scripted OS installs (SOI) of x64 OS's
• Situations where ONLY 64 bit drivers have been created for the hardware for WinPE / LinPE.

Thus, generally speaking, you're just fine with x86 WinPE.  Because of this, we recommend that you build x86 and x64 options separately, not combined.  It will assist you in forcing the x86 build to be used most of the time, and decrease the run-time for BootWiz (generally 20 minutes for each version of the build it creates - so 40 minutes if you select both x86 and x64).

I saw a comment about BootWiz running every time you restart the agent - let it finish, or it'll do this.  Open Task Manager and watch until it's done prior to attempting anything.  Then check the BootWiz folder for a temp folder under it to see if a PXE menu is there instead of where it belongs under SBS\Images.

It's a start.