- Sep 29, 2000
- 70,150
- 5
- 0
Here it is: We have a machine that has an administrator account and a secondary user account which has power user rights (whatever that means hehe). I have been working on some somewhere that runs on this machine. The software runs fine under administrator but we didn't want the users wrecking stuff, hence the power user account.
When the power user account was made all went fine at first. However after a few days that account stopped working. It lost access power to change file properties and what not that it originally had. The program I made no longer had the permissions it required to work. If a person logged off the secondary account, logged in the admin, then the program worked. Logging off the admin and back into the secondary, the program now worked and the secondary login was back to normal.
Fast forward a week: Secondary account starts failing again. We had whomever is in charge of user accounts and crap like that fix this secondary power user account. Program started to work once again (since it had the required permissions). A week later it stopped working. Now this power user account doesn't work at all with the required persmissions, but administrator always does. SOMETHING is corrupting this secondary account and killing of its privlages.
The people here who are in charge of user accounts and the hardware have run out of ideas and think my program is to blame. I can't see how a client program could break a windows login and kill off some of its rights.
Any ideas...? In the meantime we've actually got another admin account renamed to look like the old secondary account so that people logging in will think they're only a power user when in fact they are an admin :Q
When the power user account was made all went fine at first. However after a few days that account stopped working. It lost access power to change file properties and what not that it originally had. The program I made no longer had the permissions it required to work. If a person logged off the secondary account, logged in the admin, then the program worked. Logging off the admin and back into the secondary, the program now worked and the secondary login was back to normal.
Fast forward a week: Secondary account starts failing again. We had whomever is in charge of user accounts and crap like that fix this secondary power user account. Program started to work once again (since it had the required permissions). A week later it stopped working. Now this power user account doesn't work at all with the required persmissions, but administrator always does. SOMETHING is corrupting this secondary account and killing of its privlages.
The people here who are in charge of user accounts and the hardware have run out of ideas and think my program is to blame. I can't see how a client program could break a windows login and kill off some of its rights.
Any ideas...? In the meantime we've actually got another admin account renamed to look like the old secondary account so that people logging in will think they're only a power user when in fact they are an admin :Q