G
Guest
I have w2k terminal servers and a web based connection to an oracle database
which is accessed by users on each server, Jinitiater V 1.3.1.13 has been
installed on all the servers. When a connection is made to the oracle
database, Jinitiator starts and creates an "oracle jar cache" folder under
each of the user profile and stores up to 50mb of cache files. This is a
problem for the RDP users as the profle gets very large. When I change the
default settings of Jinitiater on each of the servers to point to the Oracle
Jar Cache folder to a different location, this appeared to work, but as I
have discovered it only changes the folder settings for users logged on to
the server console. Users logged on using RDP connections continue to have
the cache folder created in each of the users profiles?
which is accessed by users on each server, Jinitiater V 1.3.1.13 has been
installed on all the servers. When a connection is made to the oracle
database, Jinitiator starts and creates an "oracle jar cache" folder under
each of the user profile and stores up to 50mb of cache files. This is a
problem for the RDP users as the profle gets very large. When I change the
default settings of Jinitiater on each of the servers to point to the Oracle
Jar Cache folder to a different location, this appeared to work, but as I
have discovered it only changes the folder settings for users logged on to
the server console. Users logged on using RDP connections continue to have
the cache folder created in each of the users profiles?