Chrome ADMX Issue via Group Policy - Windows Server 2016

Zubair Zafar 0 Reputation points
2023-08-28T16:57:04.1533333+00:00

After deploying Chrome ADMX through Group Policy on Windows Server 2016, when I initiate Chrome on a client machine, the cursor functions appropriately. However, upon attempting to click, the cursor halts and an audible beep is produced. Do you possess any insights regarding this matter?

Windows
Windows
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
5,065 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Daisy Zhou 21,046 Reputation points Microsoft Vendor
    2023-09-12T05:55:15.2933333+00:00

    Hello Zubair Zafar,

    Thank you for posting in Q&A forum.

    1.Does the issue occur on only one client machine or more client machines?
    2.Did you configure any Chrome GPO to apply to the client machines?

    If you did not configure any Chrome GPO to client machines. And if the problem occurs on only one client machine, it seems it is not related to deploy Chrome ADMX through Group Policy on Windows Server 2016.
    You can try to restart this client machine to see if it helps.

    If you have configured Chrome GPO to client machines, and the problem occurs on multiple client machines.
    You can try to disable or undo the configured Chrome GPO and update GPO by running "gpupdate /force" on one problematic client machine to see if it helps.

    Hope the information above is helpful.

    If you have any question or concern, please feel free to let us know.

    Best Regards,
    Daisy Zhou

    ============================================

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

    0 comments No comments