In XP, Win7 and Vista -- in keeping with windows standards we have a few files that need to be written to and accessed. In the XP days we simply stored these files in the program files folder. However, now it's restricted. We have the following files that are accessed and changed by the program by general users without Admin Rights connectionstring.xml -- common to ALL users and the software makes changes when the user points to a different database. program.config -- program settings universal to all users Sample Database -- this is a sample database for the program, accessable to all users using the software on that PC. Thank you and I look forward to your response

You may try the launchapp.wsf script to run the tasks with high privilege. Please refer: Deploying Group Policy Using Windows Vista This method is alto applied for Windows 7.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The issues seem to be more pronounced when a user has restricted permissions such as General User or when their permissions are restricted further by a domain login setup. Our need is have some configuration files which are common to all users (not user specific) as well as a sample database which can be written and accessed by anyone. Furthermore, there could be a support need which will require us to go to that folder and look at the contents of these files. In addition, there are cases whereas clients may write a new database to that folder, however, not recommended. So, under the new UAC standards where is the best place to put these folders if Program Files will be restricted.Mark Clabaugh