Hello,
We have a customer requirement to run a kiosk using a standard user profile that cannot access files that it creates. We are able to structure this until we try to enable the Inteset software. When we do, we get a message that says the Inteset software needs to run with Administrative authority.
I know this sounds kind of odd, but the kiosk creates confidential files that our customer does not want anyone other than the Windows administrator to be able to open, copy, see, read, delete, move, etc. the confidential files.
So far, we have created a standard user that auto logs on and only has authority to write files to the D: drive. Naturally, the Administrator has the right to do anything to the D: drive.
The customer wants to be the only one that knows the Admin password. We want our application to run under the standard user profile.
Do you have any suggestions for how to configure this customer requirement ?
We have a customer requirement to run a kiosk using a standard user profile that cannot access files that it creates. We are able to structure this until we try to enable the Inteset software. When we do, we get a message that says the Inteset software needs to run with Administrative authority.
I know this sounds kind of odd, but the kiosk creates confidential files that our customer does not want anyone other than the Windows administrator to be able to open, copy, see, read, delete, move, etc. the confidential files.
So far, we have created a standard user that auto logs on and only has authority to write files to the D: drive. Naturally, the Administrator has the right to do anything to the D: drive.
The customer wants to be the only one that knows the Admin password. We want our application to run under the standard user profile.
Do you have any suggestions for how to configure this customer requirement ?
0
chris.talbot
