Often, when writing a report to a network folder, the issue of permissions will come into play. To better understand what's going on, it helps to know a little background about how Windows security works.

All programs run under a certain user account, and that user has certain permissions. When you run Microsoft word and try to write to a shared folder, Windows checks who the Word program is running under (e.g., the logged in user) and then determines if that user has the appropriate permissions to write there.

Because the AirVision Server runs as a background Windows service, it isn't connected as a logged in user. So how does Windows deal with permissions?

Most services run under a "Local System Account", which generally has access to anything on the PC (this is good), but in most IT environments has *no* permissions outside of that PC, which causes problems when we want to use network resources such as a file share or a printer. The best option available to us is to change the "Log On" properties of the AirVision service to use an account that has administrator access on the local PC *and* appropriate network access.

To change this setting, right-click on My Computer, select "Manage" and navigate to "Services." Find the AirVision service in the list and right click->Properties.

Click the "Log On" tab, and change "Local System Account" to "This Account" and put in the appropriate credentials. Restart the service.

It is also important to note that when designating the path for the report, you must use the full UNC name (e.g., \\servername\folder). You cannot use mapped drive letters.