starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 06:55:52 +03:00

[GH-ISSUE #1724] Certain service checks return error "access denied" #3019

New issue

Open

opened 2026-03-14 06:15:55 +03:00 by kerem · 4 comments

kerem commented

2026-03-14 06:15:55 +03:00

Owner

Originally created by @Aidan-abss on GitHub (Jan 2, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1724

Server Info (please complete the following information):

OS: [Ubuntu 22.04.3]
Browser: [Firefox]
RMM Version : 0.17.3

Installation Method:

Standard

Agent Info (please complete the following information):

Agent version: Agent v2.6.1
Agent OS: Windows Server 2019

Describe the bug
Services like: RPCSS, Distributed Transaction Coordinator, and Dcom Server Process Launcher which are running on the agent system can not be checked and return an error "access denied". Those services do not show up when creating a check for a specific agent. The service does not appear in remote background.

To Reproduce
Steps to reproduce the behavior:

Create an automation policy with a service check for one of the affected services
apply the policy to some servers
run your checks on your servers
See error

Expected behavior
We should see that the check reports that services are running when they are running (confirmed by logging into the system and checking the services MMC snap-in). We should see the check tell us the service is stopped when it is stopped

Screenshots

Additional context
Add any other context about the problem here.

Originally created by @Aidan-abss on GitHub (Jan 2, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1724 **Server Info (please complete the following information):** - OS: [Ubuntu 22.04.3] - Browser: [Firefox] - RMM Version : 0.17.3 **Installation Method:** - [x] Standard **Agent Info (please complete the following information):** - Agent version: Agent v2.6.1 - Agent OS: Windows Server 2019 **Describe the bug** Services like: RPCSS, Distributed Transaction Coordinator, and Dcom Server Process Launcher which are running on the agent system can not be checked and return an error "access denied". Those services do not show up when creating a check for a specific agent. The service does not appear in remote background. **To Reproduce** Steps to reproduce the behavior: 1. Create an automation policy with a service check for one of the affected services 2. apply the policy to some servers 3. run your checks on your servers 4. See error **Expected behavior** We should see that the check reports that services are running when they are running (confirmed by logging into the system and checking the services MMC snap-in). We should see the check tell us the service is stopped when it is stopped **Screenshots** ![image](https://github.com/amidaware/tacticalrmm/assets/141785712/27079084-d3a3-4a9b-9a5f-b9325ee42a48) ![image](https://github.com/amidaware/tacticalrmm/assets/141785712/db00dc09-d497-449a-8e8a-11019fd6fea9) **Additional context** Add any other context about the problem here.

kerem added the

help wanted

label

2026-03-14 06:15:55 +03:00

kerem commented

2026-03-14 06:16:08 +03:00

Author

Owner

@silversword411 commented on GitHub (Jan 9, 2024):

This has been discussed before, can't find where ATM.

Pretty sure you are using windows server 2019/2022.

There's some kind of security or special permission where some services are protected in a new/different way for security.

If you find more info and/or a pattern please post info.

@silversword411 commented on GitHub (Jan 9, 2024): This has been discussed before, can't find where ATM. Pretty sure you are using windows server 2019/2022. There's some kind of security or special permission where some services are protected in a new/different way for security. If you find more info and/or a pattern please post info.

kerem commented

2026-03-14 06:16:13 +03:00

Author

Owner

@silversword411 commented on GitHub (Jan 9, 2024):

Found it. Discord discussion

https://discord.com/channels/736478043522072608/1138917739835166843

Are the problem services running as "NETWORK SERVICE"?

@silversword411 commented on GitHub (Jan 9, 2024): Found it. Discord discussion https://discord.com/channels/736478043522072608/1138917739835166843 Are the problem services running as "NETWORK SERVICE"?

kerem commented

2026-03-14 06:16:18 +03:00

Author

Owner

@Aidan-abss commented on GitHub (Jan 11, 2024):

Found it. Discord discussion

https://discord.com/channels/736478043522072608/1138917739835166843

Are the problem services running as "NETWORK SERVICE"?

Yes. They do run as network service.

But not all services that are running as "network Service" experience this issue, such a s RPC locator service.

@Aidan-abss commented on GitHub (Jan 11, 2024): > Found it. Discord discussion > > https://discord.com/channels/736478043522072608/1138917739835166843 > > Are the problem services running as "NETWORK SERVICE"? Yes. They do run as network service. But not all services that are running as "network Service" experience this issue, such a s RPC locator service.

kerem commented

2026-03-14 06:16:23 +03:00

Author

Owner

@silversword411 commented on GitHub (Jan 13, 2024):

So it's something else along with that.

Is there any Microsoft documentation on the topic?

@silversword411 commented on GitHub (Jan 13, 2024): So it's something else along with that. Is there any Microsoft documentation on the topic?