Technical Reference for Accounts Used in Configuration Manager
Updated: May 14, 2015
Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1, System Center 2012 Configuration Manager SP2, System Center 2012 R2 Configuration Manager, System Center 2012 R2 Configuration Manager SP1
Use the following information to identify the Windows groups and the accounts that are used in System Center 2012 Configuration Manager, how they are used, and any requirements.
Windows Groups That Configuration Manager Creates and Uses
Configuration Manager automatically creates and in many cases, automatically maintains the following Windows groups:
Note
When Configuration Manager creates a group on a computer that is a domain member, the group is a local security group. If the computer is a domain controller, the group is a domain local group that is shared among all domain controllers in the domain.
ConfigMgr_CollectedFilesAccess
This group is used by Configuration Manager to grant access to view files collected by software inventory.
The following table lists additional details for this group:
Detail |
More information |
|---|---|
Type and location |
This group is a local security group created on the primary site server. Note When you uninstall a site, this group is not automatically removed and must be manually deleted. |
Membership |
Configuration Manager automatically manages the group membership. Membership includes administrative users that are granted the View Collected Files permission to the Collection securable object from an assigned security role. |
Permissions |
By default, this group has Read permission to the following folder on the site server: %path%\Microsoft Configuration Manager\sinv.box\FileCol. |
ConfigMgr_DViewAccess
This group is a local security group created on the site database server or database replica server by System Center 2012 Configuration Manager and is not currently used. This group is reserved for future use by Configuration Manager.
ConfigMgr Remote Control Users
This group is used by Configuration Manager remote tools to store the accounts and groups that you configure in the permitted viewers list that are assigned to each client.
The following table lists additional details for this group:
Detail |
More information |
|---|---|
Type and location |
This group is a local security group created on the Configuration Manager client when the client receives policy that enables remote tools. Important After you disable remote tools for a client, this group is not automatically removed and must be manually deleted this from each client computer. |
Membership |
By default, there are no members in this group. When you add users to the Permitted Viewers list, they are automatically added to this group. Tip Use the Permitted Viewers list to manage the membership of this group instead of adding users or groups directly to this group. In addition to being a Permitted Viewer, an administrative user must have the Remote Control permission to the Collection object. You can assign this permission by using the Remote Tools Operator security role. |
Permissions |
By default, this group does not have permissions to any locations on the computer, and is used only to hold the list of Permitted Viewers. |
SMS Admins
This group is used by Configuration Manager to grant access to the SMS Provider, through WMI. Access to the SMS Provider is required to view and modify objects in the Configuration Manager console.
Note
The role-based administration configuration of an administrative user determines which objects they can view and manage when using the Configuration Manager console.
The following table lists additional details for this group:
Detail |
More information |
|---|---|
Type and location |
This group is a local security group created on each computer that has a SMS Provider. Note When you uninstall a site, this group is not automatically removed and must be manually deleted. |
Membership |
Configuration Manager automatically manages the group membership. By default, each administrative user in a hierarchy and the site server computer account are members of the SMS Admins group on each SMS Provider computer in a site. |
Permissions |
SMS Admins rights and permissions are set in the WMI Control MMC snap-in. By default, the SMS Admins group is granted Enable Account and Remote Enable on the Root\SMS namespace. Authenticated Users has Execute Methods, Provider Write, and Enable Account Note Administrative users who will use a remote Configuration Manager console require Remote Activation DCOM permissions on both the site server computer and the SMS Provider computer. It is a best practice to grant these rights to the SMS Admins to simplify administration instead of granting these rights directly to users or groups. For more information, see the Configure DCOM Permissions for Remote Configuration Manager Console Connections section in the Manage Site and Hierarchy Configurations topic. |
SMS_SiteSystemToSiteServerConnection_MP_<sitecode>
This group is used by Configuration Manager management points that are remote from the site server to connect to the site database. This group provides a management point access to the inbox folders on the site server and the site database.
The following table lists additional details for this group:
Detail |
More information |
|---|---|
Type and location |
This group is a local security group created on each computer that has a SMS Provider. Note When you uninstall a site, this group is not automatically removed and must be manually deleted. |
Membership |
Configuration Manager automatically manages the group membership. By default, membership includes the computer accounts of remote computers that have a management point for the site. |
Permissions |
By default, this group has Read, Read & execute, and List folder contents permission to the %path%\Microsoft Configuration Manager\inboxes folder on the site server. Additionally, this group has the additional permission of Write to various subfolders below the inboxes to which the management point writes client data. |
SMS_SiteSystemToSiteServerConnection_SMSProv_<sitecode>
This group is used by Configuration Manager SMS Provider computers that are remote from the site server to connect to the site server.
The following table lists additional details for this group:
Detail |
More information |
|---|---|
Type and location |
This group is a local security group created on the site server. Note When you uninstall a site, this group is not automatically removed and must be manually deleted. |
Membership |
Configuration Manager automatically manages the group membership. By default, membership includes the computer account or the domain user account that is used to connect to the site server from each remote computer that has installed a SMS Provider for the site. |
Permissions |
By default, this group has Read, Read & execute, and List folder contents permission to the %path%\Microsoft Configuration Manager\inboxes folder on the site server. Additionally, this group has the additional permission of Write or the permissions of Write and Modify to various subfolders below the inboxes to which the SMS Provider requires access. This group also has Read, Read & execute, List folder contents, Write, and Modify permissions to the folders below %path%\Microsoft Configuration Manager\OSD\boot and Read permission to the folders below %path%\Microsoft Configuration Manager\OSD\Bin on the site server. |
SMS_SiteSystemToSiteServerConnection_Stat_<sitecode>
This group is used by the File Dispatch Manager on Configuration Manager remote site system computers to connect to the site server.
The following table lists additional details for this group:
Detail |
More information |
|---|---|
Type and location |
This group is a local security group created on the site server. Note When you uninstall a site, this group is not automatically removed and must be manually deleted. |
Membership |
Configuration Manager automatically manages the group membership. By default, membership includes the computer account or the domain user account that is used to connect to the site server from each remote site system computer that runs the File Dispatch Manager. |
Permissions |
By default, this group has Read, Read & execute, and List folder contents permission to the %path%\Microsoft Configuration Manager\inboxes folder and various subfolders below that location on the site server. Additionally, this group has the additional permissions of Write and Modify to the %path%\Microsoft Configuration Manager\inboxes\statmgr.box folder on the site server. |
SMS_SiteToSiteConnection_<sitecode>
This group is used by Configuration Manager to enable file-based replication between sites in a hierarchy. For each remote site that directly transfers files to this site, this group contains the following accounts:
Accounts configured as a Site Address Account, from Configuration Manager sites with no service pack
Accounts configured as a File Replication Account, from sites that run Configuration Manager SP1 and later
Note
Beginning with Configuration Manager SP1 only, the File Replication Account replaces the Site Address Account.
The following table lists additional details for this group:
Detail |
More information |
|---|---|
Type and location |
This group is a local security group created on the site server. |
Membership |
When you install a new site as a child of another site, Configuration Manager automatically adds the computer account of the new site to the group on the parent site server, and the parent sites computer account to the group on the new site server. If you specify another account for file-based transfers, add that account to this group on the destination site server. Note When you uninstall a site, this group is not automatically removed and must be manually deleted. |
Permissions |
By default, this group has full control to the %path%\Microsoft Configuration Manager\inboxes\despoolr.box\receive folder. |
Accounts That Configuration Manager Uses
You can configure the following accounts for Configuration Manager:
Active Directory Group Discovery Account
The Active Directory Group Discovery Account is used to discover local, global, and universal security groups, the membership within these groups, and the membership within distribution groups from the specified locations in Active directory Domain Services. Distribution groups are not discovered as group resources.
This account can be a computer account of the site server that runs discovery, or a Windows user account. It must have Read access permission to the Active Directory locations that are specified for discovery.
Active Directory System Discovery Account
The Active Directory System Discovery Account is used to discover computers from the specified locations in Active Directory Domain Services.
This account can be a computer account of the site server that runs discovery, or a Windows user account. It must have Read access permission to the Active Directory locations that are specified for discovery.
Active Directory User Discovery Account
The Active Directory User Discovery Account is used to discover user accounts from the specified locations in Active Directory Domain Services.
This account can be a computer account of the site server that runs discovery, or a Windows user account. It must have Read access permission to the Active Directory locations that are specified for discovery.
Active Directory Forest Account
The Active Directory Forest Account is used to discover network infrastructure from Active Directory forests, and is also used by central administration sites and primary sites to publish site data to the Active Directory Domain Services of a forest.
Note
Secondary sites always use the secondary site server computer account to publish to Active Directory.
Note
Active Directory Forest Account must be a global account to discover and publish to untrusted forests. If you do not use the computer account of the site server, you can only select a global account.
This account must have Read permissions to each Active Directory forest where you want to discover network infrastructure.
This account must have Full Control permissions to the System Management container and all its child objects in each Active Directory forest where you want to publish site data.
AMT Provisioning and Discovery Account
The AMT Provisioning and Discovery Account is functionally equivalent to the AMT Remote Admin Account and resides in the Management Engine BIOS extension (MEBx) of Intel AMT-based computers. This account is used by the server that runs the out of band service point role to manage some network interface features of AMT, by using the out of band management feature.
If you specify an AMT Provisioning and Discovery Account in Configuration Manager, it must match the AMT Remote Admin Account name and password that is specified in the BIOS extensions in the AMT-based computers.
Note
For more information about whether to specify an AMT Provisioning and Discovery Account, see Step 5: Configuring the Out of Band Management Component in the How to Provision and Configure AMT-Based Computers in Configuration Manager topic in the Assets and Compliance in System Center 2012 Configuration Manager guide.
The account is stored in the Management Engine BIOS extensions of the AMT-based computer and does not correspond to any account in Windows.
AMT Provisioning Removal Account
The AMT Provisioning Removal Account can remove AMT provisioning information if you have to recover the site. You might also be able to use it when a Configuration Manager client was reassigned and the AMT provisioning information was not removed from the computer in the old site.
To successfully remove the AMT provisioning information by using the AMT Provisioning Removal Account, all the following must be true:
The AMT Provisioning Removal Account is configured in the out of band management component properties.
The account that is configured for the AMT Provisioning Removal Account was configured as an AMT User Account in the out of band management component properties when the AMT-based computer was provisioned or updated.
The account that is configured for the AMT Provisioning Removal Account must be a member of the local Administrators group on the out of band service point computer.
The AMT auditing log is not enabled.
Because this is a Windows user account, specify an account with a strong password that does not expire.
AMT Remote Admin Account
The AMT Remote Admin Account is the account in the Management Engine BIOS extension (MEBx) of Intel AMT-based computers that is used by the server running the out of band service point role to manage some network interface features of AMT in Configuration Manager, by using the out of band management feature.
Configuration Manager automatically sets the remote admin account password for computers that it provisions for AMT, and this is then used for subsequent authenticated access to the AMT firmware. This account is functionally equivalent to the Configuration Manager AMT Provisioning and Discovery Account.
The account is stored in the Management Engine BIOS extensions of the AMT-based computer and does not correspond to any account in Windows.
AMT User Accounts
AMT User Accounts control which Windows users or groups can run management functions in the Out of Band Management console.
The configuration of the AMT User Accounts creates the equivalent of an access control list (ACL) in the AMT firmware. When the logged on user attempts to run the Out of Band Management console, AMT uses Kerberos to authenticate the account and then authorizes or denies access to run the AMT management functions.
Configure the AMT User Accounts before you provision the AMT-based computers. If you configure AMT User Accounts after computers are provisioned for AMT, you must manually update the AMT memory for these computers so that they are reconfigured with the new settings.
Because the AMT User Accounts use Kerberos authentication, the user accounts and security groups must exist in an Active Directory domain.
Asset Intelligence Synchronization Point Proxy Server Account
The Asset Intelligence Synchronization Point Proxy Server Account is used by the Asset Intelligence synchronization point to access the Internet via a proxy server or firewall that requires authenticated access.
.jpeg "System_CAPS_security") Security Note |
|---|
Specify an account that has the least possible permissions for the required proxy server or firewall. |
Certificate Registration Point Account
The Certificate Registration Point Account connects the certificate registration point to the Configuration Manager database. By default, the computer account of the certificate registration point server is used, but you can configure a user account instead. You must specify a user account whenever the certificate registration point is in an untrusted domain from the site server. This account requires only Read access to the site database, because write operations are handled by the state message system.
Capture Operating System Image Account
The Capture Operating System Image Account is used by Configuration Manager to access the folder where captured images are stored when you deploy operating systems. This account is required if you add the step Capture Operating System Image to a task sequence.
The account must have Read and Write permissions on the network share where the captured image is stored.
If the password the account is changed in Windows, you must update the task sequence with the new password. The Configuration Manager client will receive the new password when it next downloads client policy.
If you use this account, you can create one domain user account with minimal permissions to access the required network resources and use it for all task sequence accounts.
| Security Note |
|---|
Do not assign this account interactive logon permissions. Do not use the Network Access account for this account. |
Client Push Installation Account
The Client Push Installation Account is used to connect to computers and install the Configuration Manager client software if you deploy clients by using client push installation. If this account is not specified, the site server account is used to try to install the client software.
This account must be a member of the local Administrators group on the computers where the Configuration Manager client software is to be installed. This account does not require Domain Admin rights.
You can specify one or more Client Push Installation Accounts, which Configuration Manager tries in turn until one succeeds.
Tip
To more effectively coordinate account updates in large Active Directory deployments, create a new account with a different name, and then add the new account to the list of Client Push Installation Accounts in Configuration Manager. Allow sufficient time for Active Directory Domain Services to replicate the new account, and then remove the old account from Configuration Manager and Active Directory Domain Services.
| Security Note |
|---|
Do not grant this account the right to log on locally. |
Enrollment Point Connection Account
The Enrollment Point Connection Account connects the enrollment point to the Configuration Manager site database. By default, the computer account of the enrollment point is used, but you can configure a user account instead. You must specify a user account whenever the enrollment point is in an untrusted domain from the site server. This account requires Read and Write access to the site database.
Exchange Server Connection Account
The Exchange Server Connection Account connects the site server to the specified Exchange Server computer to find and manage mobile devices that connect to Exchange Server. This account requires Exchange PowerShell cmdlets that provide the required permissions to the Exchange Server computer. For more information about the cmdlets, see How to Manage Mobile Devices by Using Configuration Manager and Exchange.
Exchange Server Connector Proxy Server Account
The Exchange Server Connector Proxy Server Account is used by the Exchange Server connector to access the Internet via a proxy server or firewall that requires authenticated access.
| Security Note |
|---|
Specify an account that has the least possible permissions for the required proxy server or firewall. |
Endpoint Protection SMTP Server Connection Account
For Configuration Manager with no service pack: The Endpoint Protection SMTP Server Connection Account is used by the site server to send email alerts for Endpoint Protection when the SMTP server requires authenticated access.
| Security Note |
|---|
Specify an account that has the least possible permissions to send emails. |
Health State Reference Publishing Account
The Health State Reference Publishing Account is used to publish the Network Access Protection (NAP) health state reference for Configuration Manager to Active Directory Domain Services.
If you do not configure an account, Configuration Manager attempts to use the site server computer account to publish the health state references.
This account requires Read, Write and Create permissions to the Active Directory forest that stores the health state reference.
Create the account in the forest that is designated to store the health state references. Assign the least possible permissions to this account and do not use the same account that is specified for the Health State Reference Querying Account, which requires only Read permissions.
Health State Reference Querying Account
The Health State Reference Querying Account is used to retrieve the Network Access Protection (NAP) health state reference for Configuration Manager from Active Directory Domain Services.
If you do not configure an account, Configuration Manager attempts to use the site server computer account to retrieve the health state references.
This account requires Read permissions to the Configuration Manager Systems Management container in the Global Catalog.
Create the account in the forest that is designated to store the health state references. Do not use the same account for the Health State Reference Publishing Account, which requires more privileges.
| Security Note |
|---|
Do not grant this account interactive logon rights. |
Management Point Connection Account
The Management Point Connection Account is used to connect the management point to the Configuration Manager site database so that it can send and retrieve information for clients. By default, the computer account of the management point is used, but you can configure a user account instead. You must specify a user account whenever the management point is in an untrusted domain from the site server.
Create the account as a low-rights, local account on the computer that runs Microsoft SQL Server.
| Security Note |
|---|
Do not grant this account interactive logon rights. |
MEBx Account
The MEBx Account is the account in the Management Engine BIOS extension (MEBx) on Intel AMT-based computers and it is used for initial authenticated access to the AMT firmware on AMT-based computers.
The MEBx Account is named admin, and by default, the password is admin. Your manufacturer might provide a customized password, or you might have specified your choice of password in AMT. If the MEBx password is set to a value that is not admin, you must configure an AMT Provisioning and Discovery Account. For more information, see Step 5: Configuring the Out of Band Management Component in the How to Provision and Configure AMT-Based Computers in Configuration Manager topic.
The account is stored in the Management Engine BIOS extensions of the AMT-based computer. This account does not correspond to any account in Windows.
If the default MEBx password has not been changed before Configuration Manager provisions the computer for AMT, during the AMT provisioning process, Configuration Manager sets the password that you configure.
Multicast Connection Account
The Multicast Connection Account is used by distribution points that are configured for multicast to read information from the site database. By default, the computer account of the distribution point is used, but you can configure a user account instead. You must specify a user account whenever the site database is in an untrusted forest. For example, if your data center has a perimeter network in a forest other than the site server and site database, you can use this account to read the multicast information from the site database.
If you create this account, create it as a low-rights, local account on the computer that runs Microsoft SQL Server.
| Security Note |
|---|
Do not grant this account interactive logon rights. |
Network Access Account
The Network Access Account is used by client computers when they cannot use their local computer account to access content on distribution points. For example, this applies to workgroup clients and computers from untrusted domains. This account might also be used during operating system deployment when the computer installing the operating system does not yet have a computer account on the domain.
Note
The Network Access Account is never used as the security context to run programs, install software updates, or run task sequences; only for accessing resources on the network.
Grant this account the minimum appropriate permissions on the content that the client requires to access the software. The account must have the Access this computer from the network right on the distribution point or other server that holds the package content. Prior to System Center 2012 R2 Configuration Manager, you can create only one Network Access Account per site and this account must function for all packages and task sequences for which it is required. Beginning with System Center 2012 R2 Configuration Manager, you can configure multiple Network Access Accounts per site.
Warning
When Configuration Manager tries to use the computername$ account to download the content and it fails, it automatically tries the Network Access Account again, even if it has previously tried and failed.
Create the account in any domain that will provide the necessary access to resources. The Network Access Account must always include a domain name. Pass-through security is not supported for this account. If you have distribution points in multiple domains, create the account in a trusted domain.
Tip
To avoid account lockouts, do not change the password on an existing Network Access Account. Instead, create a new account and configure the new account in Configuration Manager. When sufficient time has passed for all clients to have received the new account details, remove the old account from the network shared folders and delete the account.
| Security Note |
|---|
Do not grant this account interactive logon rights Do not grant this account the right to join computers to the domain. If you must join computers to the domain during a task sequence, use the Task Sequence Editor Domain Joining Account. |
For System Center 2012 R2 Configuration Manager and later: You can now specify multiple network access accounts for a site. When clients try to access content and cannot use their local computer account, they will first use the last network access account that successfully connected. Configuration Manager supports adding up to ten network access accounts.
Package Access Account
Package Access Accounts enable you to set NTFS permissions to specify the users and user groups that can access a package folder on distribution points. By default, Configuration Manager grants access only to the generic access accounts Users and Administrators, but you can control access for client computers by using additional Windows accounts or groups. Mobile devices always retrieve package content anonymously, so the Package Access Accounts are not used by mobile device.
By default, when Configuration Manager creates the package share on a distribution point, it grants Read access to the local Users group and Full Control to the local Administrators group. The actual permissions required will depend on the package. If you have clients in workgroups or in untrusted forests, those clients use the Network Access Account to access the package content. Make sure that the Network Access Account has permissions to the package by using the defined Package Access Accounts.
Use accounts in a domain that can access the distribution points. If you create or modify the account after the package is created, you must redistribute the package. Updating the package does not change the NTFS permissions on the package.
You do not have to add the Network Access Account as a Package Access Account, because membership of the Users group adds it automatically. Restricting the Package Access Account to only the Network Access Account does not prevent clients from accessing the package.
Reporting Services Point Account
The Reporting Services Point Account is used by SQL Server Reporting Services to retrieve the data for Configuration Manager reports from the site database. The Windows user account and password that you specify are encrypted and stored in the SQL Server Reporting Services database.
Remote Tools Permitted Viewer Accounts
The accounts that you specify as Permitted Viewers for remote control are a list of users who are allowed to use remote tools functionality on clients.
Site System Installation Account
The Site System Installation Account is used by the site server to install, reinstall, uninstall, and configure site systems. If you configure the site system to require the site server to initiate connections to this site system, Configuration Manager also uses this account to pull data from the site system computer after the site system and any site system roles are installed. Each site system can have a different Site System Installation Account, but you can configure only one Site System Installation Account to manage all site system roles on that site system.
This account requires local administrative permissions on the site systems that they will install and configure. Additionally, this account must have Access this computer from the network in the security policy on the site systems that they will install and configure.
Tip
If you have many domain controllers and these accounts will be used across domains, verify that the accounts have replicated before you configure the site system.
When you specify a local account on each site system to be managed, this configuration is more secure than using domain accounts, because it limits the damage that attackers can do if the account is compromised. However, domain accounts are easier to manage, so consider the trade-off between security and effective administration.
SMTP Server Connection Account
For System Center 2012 Configuration Manager SP1 and later: The SMTP Server Connection Account is used by the site server to send email alerts when the SMTP server requires authenticated access.
| Security Note |
|---|
Specify an account that has the least possible permissions to send emails. |
Software Update Point Connection Account
The Software Update Point Connection Account is used by the site server for the following two software updates services:
WSUS Configuration Manager, which configures settings such as product definitions, classifications, and upstream settings.
WSUS Synchronization Manager, which requests synchronization to an upstream WSUS server or Microsoft Update.
The Site System Installation Account can install components for software updates, but cannot perform software updates-specific functions on the software update point. If you cannot use the site server computer account for this functionality because the software update point is in an untrusted forest, you must specify this account in addition to the Site System Installation Account.
This account must be a local administrator on the computer where WSUS is installed, and be part of the local WSUS Administrators group.
Software Update Point Proxy Server Account
The Software Update Point Proxy Server Account is used by the software update point to access the Internet via a proxy server or firewall that requires authenticated access.
| Security Note |
|---|
Specify an account that has the least possible permissions for the required proxy server or firewall. |
Source Site Account
The Source Site Account is used by the migration process to access the SMS Provider of the source site. This account requires Read permissions to site objects in the source site to gather data for migration jobs.
If you upgrade Configuration Manager 2007 distribution points or secondary sites that have co-located distribution points to System Center 2012 Configuration Manager distribution points, this account must also have Delete permissions to the Site class to successfully remove the distribution point from the Configuration Manager 2007 site during the upgrade.
Note
Both the Source Site Account and Source Site Database Account are identified as Migration Manager in the Accounts node of the Administration workspace in the Configuration Manager console.
Source Site Database Account
The Source Site Database Account is used by the migration process to access the SQL Server database for the source site. To gather data from the SQL Server database of the source site, the Source Site Database Account must have the Read and Execute permissions to the source site SQL Server database.
Note
If you use the System Center 2012 Configuration Manager computer account, ensure that all the following are true for this account:
-
It is a member of the security group Distributed COM Users in the domain where the Configuration Manager 2007 site resides.
-
It is a member of the SMS Admins security group.
-
It has the Read permission to all Configuration Manager 2007 objects.
Note
Both the Source Site Account and Source Site Database Account are identified as Migration Manager in the Accounts node of the Administration workspace in the Configuration Manager console.
Task Sequence Editor Domain Joining Account
The Task Sequence Editor Domain Joining Account is used in a task sequence to join a newly imaged computer to a domain. This account is required if you add the step Join Domain or Workgroup to a task sequence, and then select Join a domain. This account can also be configured if you add the step Apply Network Settings to a task sequence, but it is not required.
This account requires the Domain Join right in the domain that the computer will be joining.
Tip
If you require this account for your task sequences, you can create one domain user account with minimal permissions to access the required network resources and use it for all task sequence accounts.
| Security Note |
|---|
Do not assign this account interactive logon permissions. Do not use the Network Access Account for this account. |
Task Sequence Editor Network Folder Connection Account
The Task Sequence Editor Network Folder Connection Account is used by a task sequence to connect to a shared folder on the network. This account is required if you add the step Connect to Network Folder to a task sequence.
This account requires permissions to access the specified shared folder and must be a user domain account.
Tip
If you require this account for your task sequences, you can create one domain user account with minimal permissions to access the required network resources and use it for all task sequence accounts.
| Security Note |
|---|
Do not assign this account interactive logon permissions. Do not use the Network Access Account for this account. |
Task Sequence Run As Account
The Task Sequence Run As Account is used to run command lines in task sequences and use credentials other than the local system account. This account is required if you add the step Run Command Line to a task sequence but do not want the task sequence to run with Local System account permissions on the managed computer.
Configure the account to have the minimum permissions required to run the command line that specified in the task sequence. The account requires interactive login rights, and it usually requires the ability to install software and access network resources.
| Security Note |
|---|
Do not use the Network Access account for this account. Never make the account a domain administrator. Never configure roaming profiles for this account. When the task sequence runs, it will download the roaming profile for the account, which leaves the profile vulnerable to access on the local computer. Limit the scope of the account. For example, create different Task Sequence Run As Accounts for each task sequence so that if one account is compromised, only the client computers to which that account has access are compromised. If the command line requires administrative access on the computer, consider creating a local administrator account solely for the Task Sequence Run As Account on all computers that will run the task sequence, and delete the account as soon as it is no longer needed. |