How to change SCCM Client local policy for SUP? Not updating

Patrick Mor 51 Reputation points
2022-03-08T19:27:03.383+00:00

I changed SUP to a new server (new server, cnew hostname).

But my clients local policy is pointing to old SUP hostname yet.

How can I force the hostname change in Local GPO?

Microsoft Security | Intune | Configuration Manager | Other
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Amandayou-MSFT 11,156 Reputation points
    2022-03-09T06:39:40.74+00:00

    Hi @Patrick Mor ,

    Agree with kalyansundar-6796, we should configure the new boundary group to change the new SUP. If we use the manual option to change SUP, it is required to disable the older SUP to avoid change failure.

    Besides the method, we could try to disable the option Enable software updates on clients and then delete the record of WU & AU policy, and configure the new boundary group including new SUP, and then able the option, and run the policy on the side of client, check the related log to see if the action is successful.

    181190-391.png

    181293-39.png


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    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.

    3 people found this answer helpful.

  2. Amandayou-MSFT 11,156 Reputation points
    2022-03-21T07:45:19.167+00:00

    Hi,

    Just checking in to see if there is any update. May we know the current status of the question? Here's a short summary for the problem.

    Problem/Symptom:
    I changed SUP to a new server (new server, cnew hostname).
    But my clients local policy is pointing to old SUP hostname yet.
    How can I force the hostname change in Local GPO?

    Solution:
    Configure the new boundary group to change the new SUP. If we use the manual option to change SUP, it is required to disable the older SUP to avoid change failure.

    Besides the method, we could try to disable the option Enable software updates on clients and then delete the record of WU & AU policy, and configure the new boundary group including new SUP, and then able the option, and run the policy on the side of client, check the related log to see if the action is successful.

    Please click "Accept Answer" to your answer and upvote it, this will help other users to search for useful information more quickly. Thanks again for your time.


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    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.

    3 people found this answer helpful.
    0 comments No comments

  3. Kalyan Sundar 566 Reputation points
    2022-03-08T21:07:33.17+00:00

    Have you configured the new SUP on required boundary group?

    Check the client locationservice.log for the change or error.

    You can also use the manual option from SCCM console to change SUP , check the below blog

    https://www.anoopcnair.com/change-sccm-client-software-update-point-sup-from-console/

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.