kasperskyfan

To give Read permissions to NT AUTHORITY\SYSTEM it looks like huge security risk.

Can anyone else confirm this results with Device Control policy?

I have latest KSC 14.2, and device policy for USB. Problem is when I allow user to use USB, I receive notification "Event "Operation with the device prohibited" has occurred on device", but for "User: NT AUTHORITY\SYSTEM (Initiator)". I have a lot of these notification. Is this normal behavior and what is the best practice?

I my new KSC Administration server I have clients from two domains and different networks. On one network I cant manage clients in the way that cant stop/start KES or agent, and cant stop/start any task (gray). don't see info on Session to. Everything else seams to work. I can install KES app, can see app installed on client, updates are working. It seams to me that is some kind of network problem, as maybe some ports are blocked. But I'm confused. Can you help me?

I'm accessing KSC 13.2 administration server through my computer - KSC administration console with AD account that is KLAdmin. When I put that account in Protected Users group in AD, I can't access ksc server - "Failed to connect to the Administration Server because access is denied." Is there any way that my account be member of protected users group and can access KSC server?

I found out what is problem. I deploy Windows images from WDS/MDT server, but Windows 10 2004 version makes all junction links in c:\ProgramData to show to D partition, which is not correct. Deleting application data junction link solve my problem, and I can update agent without problem. Related: https://www.reddit.com/r/MDT/comments/hopnbb/anyone_else_having_issues_with_win10_2004_deploys/

I have installed latest KES 11.4.0.233, but still have this error (BAD JUNCTION) when installing Network agent. Is it possible that I’m only one with this problem on Windows 10 2004 version? I have latest KSC 12, with patch a installed.

No, it’s not only virtual. I have two physical machine with this problem.

Probably is important, both my problematic systems are virtual (hyper-v host).

I get this message in event logs on new Windows 10 2004 system after sucesffuly installed both KES 11.3.0.773 and Network agent 12.0.0.7734: Installation of updates 'Patch..exe' for software modules of '1103' has returned an error: Bad junction. . Windows TEMP folder is full of folders and files of (nagent_autopatches_...) failed installation content, and eventualy run out of disk space. I have the same problem (only) on one Windows server 2016. Please help.