Upgraded to ConfigMGR 2309 now retrieval of policy is taking forever when pxe booting. The SMSTS.log says in SSL but no client cert

Question

This week I upgraded my site server to Configuration Manager 2309. Now whenever I PXE boot a machine it is extremely slow in retrieval of the computer policy step, it might take upwards between 5 to 20 minutes before the select task sequence windows pops up.

We are using unknown computers collection and yes unknown computer support is checked on on the distribution point in the PXE tab.

Under the communications tab I have a valid pfx certificate set to expire in 2025 imported with the password.

Before the upgrade to 2309 PXE boot/retrieval of computer policy was a normal speed 5-10 seconds before the select task sequence window would pop up allowing us to choose a task sequence for OSD

Any insight on how to resolve this would greatly be appreciated.

Answer 1

Hi,

Thank you for posting in Microsoft Q&A forum.

1,Do you install the latest hotfix for Configuration Manager version 2309?

Update rollup for Microsoft Configuration Manager version 2309

2,Does this issue appear for all the PXE task sequences? How about building a Windows 10 client or a Windows 11 client?

Thanks for your time. Have a nice day!

Best regards,

Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Simon,

We are using Unknown Computer support for pxe and advertise deployments against it, yes unknown computer support is check under the PXE tab.

Even before we have a chance to pick a task sequence, the problem exists, We pxe boot a pc and put in the password for pxe, and it gets stuck on "Looking for computer policy" for about 5 minutes until the select a task sequence window pops up, we then select a task, and have to wait another 5-10 minutes for "resolving dependencies" to happen

So it has nothing to do with a task sequence per se because the problem exists long before we even have a chance to select a task sequence.

if I check the smsts.log when the client is "Looking for computer policy" I see "in SSL but no client cert"

Lastly the hotfix has been installed, please advise a course of action.

Answer 3

Hi,

Thanks for your reply. It's really a strange issue. Can you find any clue in the smspxe.log on the server side?

Best regards,

Simon

Answer 4

Simon,

I thought it was related to PXE, but it's not. I have made boot media that connects to our ConfigMgr infrastructure and the retrieval of policy is still slow, so I am thinking it's SQL issue. Please advise.