Expand Article

Last Updated: 11/9/12


Amp applications use Microsoft’s ClickOnce technology for deployment. ClickOnce applications run in an isolated environment which contains its own copy of the application files and libraries.

Microsoft’s Terminal Server also creates an isolated session for each logged on user. This means that when a new user logs into the terminal server for the first time, they must download and install the Amp applications they wish to use. The same is true for updates.

The advanced security settings introduced in Microsoft Vista and now in Windows 2008 Server make it impossible to write to the C:\Program Files folder and to the Registry without elevated privileges. These privileges are not available to ClickOnce applications. These newer operating systems use a workaround called Virtualization. The bottom line is that settings and files shared between applications are now stored in different locations. In our case, we are concerned about the C:\ProgramData folder.

In these newer operating systems, Amp applications read and write local computer settings using the C:\ProgramData\PDS* folders. If this is the first installation of a Amp application, these folders and the files within them are created by the currently logged on user. This presents another problem since these operating systems use file-level security based on the Owner/Creator of the files.

The next time a different user logs onto the Terminal Server and starts a Amp Live application an attempt will be made to read/write from the same settings files in the C:\ProgramData\PDS*. Since this new user is not Owner/Creator of these files, an Access Denied error will be raised by the operating system and the Amp Live applications will generate an error.


The solution to this issue is to right click and each of C:\ProgramData\PDS* folders and change the permissions so that everyone can have full control of the folders and sub folders.


Updated 6/2011

Back to Top