---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# File permission enforcement for Windows MID Servers

# File permission enforcement for Windows MID Servers {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

To improve security, Windows MID Servers enforce Windows file permission restrictions.
The enforcement limits access to the MID Server files to a restricted allow list of users and
groups.

|-|
|   |
[ ]

{#mid-non-admin-permission__table_p53_ms4_nhb}

File permission enforcement for Windows MID Servers goes into effect on the MID Server on start
up in Orlando. By default the agent folder is locked to four user accounts and groups: the local
admin group, the system account, creator owner, and the user account the Windows MID Server is
using. The list of permitted user accounts is managed by a allow list, which is controlled by the
MID Server parameter mid.windows_host.file_permissions.allow_list. This
parameter takes a string of comma separated group names, user names, and security identifiers
(SID). Group and user names must follow SAM account naming requirements. Domain accounts must be
specified by using the SID.

## Roll back file permission changes {#mid-non-admin-permission__section_xk3_kmb_sjb}

Changes to the file permissions are recorded, and the last used settings are saved in the
/etc folder as a backup. The file is
fileperm.aclsave. Open a command prompt and run the command
icacls \<agent_folder\> /restore \<agent_folder\>/etc/fileperm.aclsave
where \<agent_folder\> is name of your agent folder.

## Run a MID Server as a non-admin {#mid-non-admin-permission__section_yk3_kmb_sjb}

To run a MID Server as a non-admin user, it must first be installed using an admin
account. Then add the non-admin user to allow list and restart the MID Server. Once the
new enforcement rules run, the MID Server can be switched to the non-admin service
account. See [Manually install a MID Server on Windows](https://servicenow-prod.fluidtopics.net/1n4BMA3dcXnEVbu~5ko~HA#mid-windows-manual-install "Install MID Servers with the ZIP file installation package and verify it is active.") for more information on setting
up non-admin Windows MID Servers, or [Run Linux MID Servers as non-root users](https://servicenow-prod.fluidtopics.net/Kov3JIC3GQu3Crrk3BnUNg#non-admin-linux-mid-install "Run MID Servers as non-root user on a Linux machine to improve security. Multiple MID Server can be installed as services so they can start by themselves after system reboots.") for
Linux MID Servers.