Forum Discussion
nmorgowicz
Nov 26, 2018Copper Contributor
Server Manager on Server 2019/1809 and Windows 10 1803/1809 not working on domain joined computers
Hello, this problem is a bit complicated to describe, but i joined in on a thread here to post my experiences: https://social.technet.microsoft.com/Forums/en-US/ca8b8e3d-b6df-426f-b58f-c9e4adbd1612/w...
Bradley_Hetherington
Nov 29, 2018Copper Contributor
Hi,
I have only spent 5 minutes on this so far, but I saw the same issue with Symantec Endpoint Protection version 14.2 MP1 with patch 1031 (the latest I know of.
If I learn more, I'll post.
Cheers,
Brad
nmorgowicz
Dec 13, 2018Copper Contributor
Hi Brad, But as i mentioned in my analysis, when any machine with SEP installed is not on the domain, there is no problem opening Server Manager. It is only when the machine becomes domain joined that the issue occurs. I don't believe SEP is the problem.
- chris905Jan 24, 2019Copper Contributor
It is the SEPM causing the issue. You can either remove the device and application control or can create an exception in sepm: Windows exception - File, file is servermanager.exe and select application control.
- nmorgowiczFeb 03, 2019Copper Contributor
Hi chris905, I created exceptions for both security/file as well as a custom application and pointed to C:\Windows\System32\ServerManager.exe However, it's still an issue like nothing is changed. I haven't tried a case where i would remove SEP from a domain joined machine to see if it is still a problem, but as i stated a few times above, it's highly unlikely that it's SEP.
I'm just surprised not more people are affected by this.
- DiegoSouzaFeb 14, 2019Copper Contributor
Hello
Same issue here, did you ever find a solution?
Regards,
Diego.