SVG Viewer problem

[news.dls.net]

Hi all,

I've just added a page to our intranet that needs the svg viewer from Adobe.
Our TS users are severly limited in what they can do. I can add the svg
viewer as myself, but when I log in as a restricted user, it prompts me to
download the viewer, but doesn't allow it because of security restrictions.

How can I make the svg viewer available to all users so the new intranet
link will work?

Thanks!

Randy

 

[Vera Noest [MVP]]

Try this:
download the svg viewer package to your local harddisk. Put the
server into "install mode" by typing "change user /install"
(without the quotes) in a command window. Install the viewer.
Change back to execute mode with "change user /execute".

It should now be available to all users.

 

[news.dls.net]

Thanks for the suggestion. I tried that before, but didn't go back to
/execute mode... I logged out instead. I uninstalled and reinstalled going
into /install, then back to /execute, but still doesn't work for other
users. We run a custom shell. This shell has a VB browser that the SVG
viewer works with. I put one of the users in the "IS" OU temporarily and it
popped up a user license to agree to, then it worked. I put that user back
in the "Thin Client" OU and it still works. Other "Thin Client" users do
not get the license agreement. I suppose I could move the clients
one-by-one into "IS", agree to the license, the put them back into "Thin
Clients". We have only about 20 users. Any other suggestions before I do
it manually?

Thanks!

Randy

 

[Vera Noest [MVP]]

I'm not sure what your "IS" OU is, but the main problem seems to
be the license agreement.
I've had similar issues myself, with programs that are technically
speaking not completely installed during the normal installation
procedure. I.e. they perform some final one-time action when you
run the application for the first time (in your case: present the
license agreement).
These kind of problems can often be solved by starting the
application the first time as administrator, WHILE STILL IN
INSTALL MODE. This makes the license agreement part of the
registry entries that are copied to the shadow area in the
registry.
You could still do this, but since you already have run the
application and accepted the license agreement with your normal
administrator account, it involves that you use a fresh
administrator account, which has never run the application. Logon
with that account, go into install mode, start the application,
accept the license, exit the application and return to execute
mode.

Only you can decide if this method is quicker then temporarily
moving your users (and it is not garantueed to work).
If you choose the above method, please let us know if it works!