From ac525a3fd71a2c9d1a60e09dfcf66b70039fb150 Mon Sep 17 00:00:00 2001
From: dereklangMSFT <85270473+dereklangMSFT@users.noreply.github.com>
Date: Mon, 7 Apr 2025 14:07:08 -0500
Subject: [PATCH] Update deploy-clients-cmg-token.md

Added a requirement that the user must be a Full Administrator in Configuration Manager as well as a local administrator on the server
---
 .../configmgr/core/clients/deploy/deploy-clients-cmg-token.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/intune/configmgr/core/clients/deploy/deploy-clients-cmg-token.md b/intune/configmgr/core/clients/deploy/deploy-clients-cmg-token.md
index e29c9b0b676..b60fa2011f5 100644
--- a/intune/configmgr/core/clients/deploy/deploy-clients-cmg-token.md
+++ b/intune/configmgr/core/clients/deploy/deploy-clients-cmg-token.md
@@ -57,7 +57,7 @@ If you can't install and register clients on the internal network, create a bulk
 
 To create a bulk registration token for use during client installation on internet-based devices, complete the following actions:
 
-1. Sign in to the top-level site server in the hierarchy with local administrator privileges.
+1. Sign in to the top-level site server in the hierarchy with an account that is a 'Full Administrator' in Configuration Manager and is part of the local Administrators group on the server.
 
 1. Open a command prompt as an administrator.