WARNING: Skipping removing S-1-5-21-* : S on MID ServerIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } MID Server was showing unresolved issue: WARNING: Skipping removing S-1-5-21-* : S NOTE: "S-1-5-21-* : S" is used instead of the user's actual SID. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This is not release specific. Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The message "WARNING: Skipping removing S-1-5-21-* : S" was raised by "MIDFilePermEnforcer". This is a message that is produced by a process called File Permissions Enforcer (EnforceFilePermissions.psm1), which the MID Server runs on the startup of the Service. It is usually raised when: The Service User has lost access to the MID Server Service or agent foldersIf there are unfamiliar accesses/permissions allowed to the MID Server Service, agent foldersIf there are mismatched permissions between the Service User does not have "Log On As Service" Policy. Typically customer host environments will use Local Service Accounts and set up for the MID Server Logged In User. Occasionally you may have customers with an Active Directory User/Group setup to manage their service accounts and permissions allowed to them. In a case, the customer's AD Group which had the "Log On As Service" Policy did not have the Logged In User included, thus the Logged In User did not have the permissions inherited. This caused the warning to continue to show. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Resolution For Standard Environments (No User Management Integrations) Ensure these steps were followed and mentioned users are validated or follow below steps: Check Windows Service Account Settings: Open Computer Management > Local Users and Groups2. Open the Service account > Properties Check Service Account is used to start the MID Server Service Open ServicesRight Click MID Server > PropertiesOpen "Log on" tab and take note of account shown. Check Service Account has "Log on as a Service" policy Open Local Security Policy > Local Policies > User Rights AssignmentRight click "Log on as a service" policy > PropertiesConfirm Service account is in list. Check SID of Service Account and/or Group Open Command Prompt (Win+R > cmd)Run command: " wmic useraccount where name='<insert_service_account_name>' get name,sid "Run command: " wmic group where name='<insert_group_name>' get name,sid,domain "Confirm if SID from warning matches the SID from above commands. Resolution For Environments with Active Directory (AD) Integrations Follow the above steps to gather and validate Service account information. If at any point the customer has an AD Group instead of an AD User, ensure that the Logged In User matches the AD User, and the AD User is a member of the AD Group. In the case of customer X, after confirming the AD User (which was the Logged In User) was NOT in the AD Group with permissions: Add the AD Service Account into the Active Directory Group with "Log on as a service" Policy permissions.Run "gpupdate /force" to help update/sync the AD settings.Restart the MID Server Service. (Several times if need be, to allow for AD to sync permissions correctly)Monitor if the Warning messages appear in MID Server Issues again. Note: The above steps are based on the resolution proposed by the technical support team. The issue was resolved during a zoom meeting with the customer. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } With reference to CS7511378, an attempt to add the parameter to the MID Server's config.xml file was made. <parameter name="mid.windows_host.file_permissions.allow_list" value="S-1-5-21-* : S"> However this did not resolve the issue, but rather added another MID Server Issue, similar to the below: "WARNING: Skipping adding S-1-5-21-* : S : I" So, the parameter was removed from the MID Server's config.xml file. It is recommended to set the Logging Level to DEBUG (mid.log.level = DEBUG) then reviewing the agent0.log files.