Applications working in one profile are nut working in others

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi

After i installed few applications (in house) on machine with admin account
i found that after logging with different username the same applications were
not working. but i they are still working in admin account. one thing is
common in all applications they are using tnsnames.ora file to connect to
database. one solution for this i found that i copied the admin's profile to
default user profile and deleted all other existing profiles. After that if
any user logs in he is able to work on application. but in this case if any
new application is installed on machine then again same activity required to
be done. Do somebody have any solution to this query ?

Ramanjit
 
Ramanjit said:
Hi

After i installed few applications (in house) on machine with admin
account i found that after logging with different username the same
applications were not working. but i they are still working in admin
account. one thing is common in all applications they are using
tnsnames.ora file to connect to database. one solution for this i found
that i copied the admin's profile to default user profile and deleted all
other existing profiles. After that if any user logs in he is able to work
on application. but in this case if any new application is installed on
machine then again same activity required to be done. Do somebody have any
solution to this query ?

Ramanjit
Should I assume you are on a network? please give some details.
 
Ramanjit said:
Scenario is like we are on Domain with 1450 machines
This mostly a software issue. If your program requires running or calling
protected dll files and system files, it is no good. You either need to to
make the local users local admins (bad idea) or go to your policy manager
and tell it what are users allowed to run. Under all circumstances, you
will need to trace what files are called by your software. Another option
is for your developer to use the runas option when launching the
problematic software. You could also allow permissions to the registry keys
this software is using. as you can see, there are a score of issues to
check, and the same number of solutions.
 
Back
Top