Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > NCM requires Read/Write permissions to C:\Windows\Temp for .bat files

NCM requires Read/Write permissions to C:\Windows\Temp for .bat files

Table of contents

Updated June 28th, 2016

Overview

This article covers why NCM needs Read/Write permissions to C:\Windows\Temp.

Environment

All NCM versions

Detail

SolarWinds Orion modules require Network Services Read/Write permissions to the C:\Windows\Temp.

 

The job engine uses this directory: C:\Windows\Temp\Solarwinds\JobEngine\ShadowCopyCache-(number) and each job engine worker has a copy of all used libraries so they do not block original files. Directory is created for each worker process (ShadowCopyCache-ProcessID).

 

In NCM, .bat files are written and deleted with an unpredictable unique file name and format. This is by design. These .bat files are required by NCM to do comparisons between newly downloaded configs and previous configs. NCM will delete them automatically once it finishes the comparison task.

 

Name of file is always unique and cannot be controlled.

NCM actively use temp folder for many kinds of operations.

Access to temp folder must be allowed for NCM with no restrictions to make it work correctly.

 

 

 

Last modified

Tags

Classifications

Public