I'm running in HTTPS with PKIs but I think I'm missing something when it comes to PXE as I'm getting the following messages spammed in my SMSPXE.log file whenever a machine tries to PXE boot: 7096 0x1bb8 in ssl but with no client cert. I went to Administration, Security and then Certificates. In there I had 2 out of 3 blocked DP certificates and the issued to fields were showing as GUIDs rather than actual FQDNs. Any ideas?
@clivebuckwheat
5 ай бұрын
Nial, why is it when you pxe boot and looked at the smspxe.log you still see in ssl but no client cert?, I am having this issue right now and resolving policy is taking forever to bring up the advertise task sequence window
@ncbrady
5 ай бұрын
hi Clive, that's a red-herring, ignore it. If policy is taking a long time to flow down from the management point then you need to troubleshoot that, perhaps try deleting then redeploying that task sequence, i think you'll see a difference. If not, reduce the size of the task sequence or improve the network connection (if remote).
@clivebuckwheat
5 ай бұрын
@@ncbrady I did all that. I am on day 5 of this. I deleted all the task sequences advertised to unknown computers, our task sequences aren't complicated. I got excited when i saw your video I thought maybe my battle was over. It takes about 10 minutes for the advertise task sequence page to pop up. This all began after I upgraded to CM 2309. I have updated the boot images on the dp, I have even tried boot media instead of PXE and it takes forever, to resolve the policy. I'll say this sometimes its fast, meaning (normal speed) but most of the time it's slow now. oh well my battle is not over it seems thanks for the reply.
@ncbrady
5 ай бұрын
@@clivebuckwheat you need to tell me more about the environment that you have then, i bet it's 10 minutes on remote distribution points right ?, what about local dp's ? is PXE boot ok there ? any changes recently to the network infrastructure ?
@clivebuckwheat
5 ай бұрын
@@ncbrady one on-premises distribution point one off premises PXE is on the on-premises distribution point and it services our clients across the street It’s really not a PXE problem as I first was certain it was because it happens with boot media as well. Nial here’s a scenario PXE boot a machine or use boot media to connect to our configmgr environment it’s normal speed, find policy for this machine is fast, pick a ts resolving dependencies Is fast and OSD kicks off. PXE boot or boot media the same machine again both looking for policy for this computer is slow and after 10 minutes the advertise task sequence window pops up and resolving dependencies is slow for the task sequence another 10 minutes and OSD kicks off. PXE boot or boot media the machine again it’s slow. Switches were changed in my environment recently Anyways it’s so sporadic I can’t pin it down
Пікірлер: 6