ORION permission checker; TEMP path error

Question

I ran the permission checking program and received these errors. The system seems to be working (I didn't install it), but  our security folks are complaining that the NETWORK SERVICES account has access to the TEMP folder. I suspect there may be multiple issues here.

1. the services is logging in with the  Local System Account (is this level of access required?) Perhaps a dedicated account should be used.

2. was the TEMP path misconfigured during installation

Any ideas?

thanks

FAILED Check write NETWORK SERVICE C:\Windows\TEMP 'write' access right to the

'C:\Windows\TEMP' path for the 'NETWORK SERVICE' principal is not configured. Actual path was C:\Windows\TEMP\hsperfdata_W2LIL01XEM$

FAILED     Check read NETWORK SERVICE C:\Windows\TEMP 'read' access right to the 'C:\Windows\TEMP' path for the 'NETWORK SERVICE' principal is not configured.

Actual path was C:\Windows\TEMP\fwtsqmfile04.sqm.

jrouviere · Answer

Adding to this I can tell you that if you don't have access to the TEMP directory some images may not load correctly.

For example, we had an issue where those permissions were denied to most accounts due to some internal shenanigans and the images and backgrounds for our Orion Maps would no longer load.

Once the permissions were updated it worked fine.

Mind you most of the rest of the console functioned just fine, that was the main macroscopic piece that we noticed, but Orion Maps became fairly unusable without the images.

HerrDoktor · Answer

These Permissions are required for proper performance. You will notice a decrease in the Web-GUI Performance when the permissions are not set. I dont have the technical background WHY the permissions are needed for NPM and web gui but here's an article why it is needed for NCM:

Success Center