New WSM install

update....
It appears to be related to the HP switch (new 5412zl) and spanning tree.. I found that if I removed power from the device I could boot thin clients (Z00d) but if I rebooted it would not boot. I hard coded the port at 100-full duplex and the clients boot and reboot (albeit slowly)... Working with WYSE support to define a switch config that will support 1000 full without the lengthy STP transitions...

1) If the DHCP Proxy Server is not configured for "Enable Device Discovery" than you will have to add the clients from the WSM UI. What you see is the expected behavior, because the WSM DHCP Proxy is answering ony requests for clients present in its database for the sake of security.
2) What error message do you get when you reboot the client after it has booted one time successfully?
3) The OS Image has to be in a shared mode (persistant or versatile) to be streamed to multiple clients at the same time.

 Originally Posted by mhaase 

1) If the DHCP Proxy Server is not configured for "Enable Device Discovery" than you will have to add the clients from the WSM UI. What you see is the expected behavior, because the WSM DHCP Proxy is answering ony requests for clients present in its database for the sake of security.
2) What error message do you get when you reboot the client after it has booted one time successfully?
3) The OS Image has to be in a shared mode (persistant or versatile) to be streamed to multiple clients at the same time.

The DHCP server is located in another subnet and is a windows box. I do have the proxy service enabled as well have a helper address in the router. The error I get is that E01 or no offers received. The client were in the database at the time. It may be that it was not in streaming mode (at the time) but it is now for sure. Ill report back what I find later today thank for the response

If WSM Admin Serive (which controls WSM DHCP Proxy service) and WSM OS Authentication are running I reckon something is wrong with either your DHCP forwarders or NIC Team. Please keep in mind that WSM only listens on one logocal/physical NIC for inincoming PXE requests.
You can do a trace on the WSM serve to see whether it is receiving the DHCP broadcast from the clients.
Also, looking at the WSM server side logfiles and search for the clients mac-address could give a hint whats the problem.

Thanks MHaase...

its weird that new clients boot right up and I can configure them but once you reboot them they do not.. Its like they go missing in the database (since you said for security WSM will ignore requests from devices not in the DB) but they are in the database.. I can configure hem in the DB add them to device groups and what not. It is really strange... Is it normal to have to independent MSSQL services running? In my services I have MSSQLSERVER and also WSMSQLSERVER (also in reporting services) though only one is ever running (the MSSSQL..) so I guess its not a problem since I can add things and tweak things in the Database.. hohum.... I contacted support.. 24 hours and no response...

Ok. Double checked this morning. Image is in volatile cache and assigned to the default site group that is part of the default site that is part if a new server group I created (only I e server currently). Image shows enabled and assigned to a device group that I created. Client sits at pxe dhcp sequence. I manually created the client in the WSM server and booted a new one but nothing. Server nic is a team from a 4 port intel server adapter.

Ok. Dhcp is working but only new clients will boot. I configure them in the preboot phase and then they boot the shared image. Once I reboot them they do not boot anymore. Dhcp just spins.