[GH-ISSUE #1935] Automated Patch Policies for Workstation get applied to Servers too #1208

New issue

Open

opened 2026-03-02 02:21:53 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 02:21:53 +03:00

Owner

Originally created by @PIT-IT on GitHub (Jul 26, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1935

Server Info (please complete the following information):

OS: Debian 12
RMM Version 0.19.2

Installation Method:

Standard

Agent Info (please complete the following information):

Agent version 2.8
Agent OS: Windows Server 2022

Describe the bug
We have created 2 Automation Policies for automated Windows Updates for Servers and Workstation
both are configured the same but the Workstation Policy has the additional Task to execute "shutdown /s" 3 hours after patches
those Policies are applied to the client menu
after running once the Servers got the Shutdown command from the Workstation Policy and were added to the Agents

To Reproduce
i have not been able to reproduce this problem with test VMs

Expected behavior
Servers should not inherit Workstation policy

Screenshots
Server Policy

Workstation Policy

Workstation Task

Client Configuration

Server-Agent Configuration it got after running once

Originally created by @PIT-IT on GitHub (Jul 26, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1935 **Server Info (please complete the following information):** - OS: Debian 12 - RMM Version 0.19.2 **Installation Method:** - [ ] Standard **Agent Info (please complete the following information):** - Agent version 2.8 - Agent OS: Windows Server 2022 **Describe the bug** We have created 2 Automation Policies for automated Windows Updates for Servers and Workstation both are configured the same but the Workstation Policy has the additional Task to execute "shutdown /s" 3 hours after patches those Policies are applied to the client menu after running once the Servers got the Shutdown command from the Workstation Policy and were added to the Agents **To Reproduce** i have not been able to reproduce this problem with test VMs **Expected behavior** Servers should not inherit Workstation policy **Screenshots** Server Policy ![image](https://github.com/user-attachments/assets/275b4681-7157-4fa4-97ee-c3524afc825a) Workstation Policy ![image](https://github.com/user-attachments/assets/627ff8b0-e95a-467f-855b-dc9af68eaf06) Workstation Task ![image](https://github.com/user-attachments/assets/9dfcef64-70de-4b10-bbd4-8321bec54304) ![image](https://github.com/user-attachments/assets/7f40e680-1489-476c-98c3-e261cc2ea876) ![image](https://github.com/user-attachments/assets/8b94ee62-4626-4447-9a29-f6e81416a6c7) Client Configuration ![image](https://github.com/user-attachments/assets/694f65b2-a340-4947-bdf4-ee8df65eb83e) Server-Agent Configuration it got after running once ![image](https://github.com/user-attachments/assets/f728024a-ae29-4bd7-be8c-22cd377e4b8b)