Forum Discussion
Windows Server 2025 DC Won't Install / Uninstall MSI packages, NIC Domain Category issue.
Replying to my own post as I have a resolution to the issue. Actually have to give credit to Ninja support. They provided a reference to a Reddit post that had the solution. Being that Ninja also installs Splashtop, the issue reported in other posts, although related to Syncro & Atera applies to Ninja as well as they all use Splashtop (although Ninja has their own Remote app that is awesome, haven't used Splashtop since starting using their remote app)...but I digress.
Setting the Splashtop Remote Service to either Disabled or Automatic (Delayed) and rebooting the machine resolves the issue. .MSI packages will now install / uninstall normally. Also, while the issue with the machine's NIC network category automatically being set to Public upon reboot still remains, running the script mentioned before now executes correctly in Task Scheduler. So the Splashtop issue also affected the scheduled task.References:
Primary post that helped resolved the issue: https://www.reddit.com/r/syncro/comments/1j26412/splashtop_appears_to_break_windows_server_2025/Others:
https://www.reddit.com/r/WindowsServer/comments/1j261uc/splashtop_win_server_2025_dc/
https://learn.microsoft.com/en-us/answers/questions/2191037/agents-not-communication-after-promoting-a-server?forum=windowserver-all&referrer=answers&page=1#answers
https://www.reddit.com/r/WindowsServer/comments/1iq9b4f/applications_wont_install_2025/
In a similar vein, I also have a server2025 system. i used remotepc as the remote access app; i had Megaraid storage manager (deprecated management interface for dell PERC controllers) and Macrium reflect for backup and disaster recover. When i promoted to a DC; everything went south. The remote control app came up but the service wasn't running normally; I could not access the system remotely (except for remote desktop) i couldn't uninstall, etc, etc. In the end; i had to set all 3 services for all 3 products to delayed start for everything to work. just to experiment; i set remotePC and MSM to delayed start; set Macrium (the last thing i added) to "automatic" and remotePC stopped working. Its only reliable for me if all 3 (of the products i use) are set to delayed start. I'm sure they have some dependency on some microsoft service the wedges the system. Its odd (to me) that when macrium is set to automatic; that remotePC stops functioning.
Yea, though it is a different mix of products, seems that the commonality is the Delayed start setting. Hope MS is monitoring these types of threads and acknowledges that there is a problem.
Eleanor_LittleMicrosoft
Hello! Thank you for reporting these issues. It would be great if you could file these on feedback hub as well, it makes it easier for the owning dev teams to investigate and look into these issues.