ClickOnce on Terminal Services farm

[YYZ]

Hello,

We have a ClickOnce application that one of our clients would like to
install in a Terminal Services server farm. The application is
installed from a URL and added to the Start menu and uses the .NET 2.0
framework.


The ClickOnce application files are stored in the directory


C:\Documents and Settings\<username>\Local Settings\Application Data.


The issue is that the Local Settings folder is not part of Profile
Synchonization (or folder redirection). Their policy is that files in
the Local Settings folder are removed when the user logs off. The
result is that the application is re-installed each time the user runs
the application from the start menu. This is of course unacceptable.


I am afraid that the only solution is to have them use an MSI file,
but I am looking for other ideas?


I have read conflicting reports that there is a way to modify the
ClickOnce store on each server? Anyone?


Thanks in advance.


Glenn Smith

 

[Udo Nesshoever]

Hi Glenn,

We have a ClickOnce application that one of our clients would like to
install in a Terminal Services server farm. The application is
installed from a URL and added to the Start menu and uses the .NET 2.0
framework.

The ClickOnce application files are stored in the directory

C:\Documents and Settings\<username>\Local Settings\Application Data.

The issue is that the Local Settings folder is not part of Profile
Synchonization (or folder redirection). Their policy is that files in
the Local Settings folder are removed when the user logs off. The
result is that the application is re-installed each time the user runs
the application from the start menu. This is of course unacceptable.

I am afraid that the only solution is to have them use an MSI file,
but I am looking for other ideas?

I have read conflicting reports that there is a way to modify the
ClickOnce store on each server? Anyone?

It's more a practical workaround rather than a solution for your problem.

Is the application that big? What if you set the ClickOnce deployment to
[X] The application is available online only.
[ ] The app... (launchable from the Start menu)

That way the application will not be stored in the Local Settings at
all. (But of course it is reloaded from the server every time you start
the application).

Cheers,
Udo

 

[YYZ]

Hi Glenn,

We have a ClickOnce application that one of our clients would like to
install in a Terminal Services server farm. The application is
installed from a URL and added to the Start menu and uses the .NET 2.0
framework.

The ClickOnce application files are stored in the directory

C:\Documents and Settings\<username>\Local Settings\Application Data.

The issue is that the Local Settings folder is not part of Profile
Synchonization (or folder redirection). Their policy is that files in
the Local Settings folder are removed when the user logs off. The
result is that the application is re-installed each time the user runs
the application from the start menu. This is of course unacceptable.

I am afraid that the only solution is to have them use an MSI file,
but I am looking for other ideas?

I have read conflicting reports that there is a way to modify the
ClickOnce store on each server? Anyone?

It's more a practical workaround rather than a solution for your problem.

Is the application that big? What if you set the ClickOnce deployment to
[X] The application is available online only.
[ ] The app... (launchable from the Start menu)

That way the application will not be stored in the Local Settings at
all. (But of course it is reloaded from the server every time you start
the application).

Cheers,
Udo

Thanks for your suggestion. I have thought of this as well, but another
issue we have is with the network setup at this site. It seems that anytime
a file is downloaded, it is scanned for viruses which is resulting in a 10MB
file to take 13 minutes to download, scan and install. So, it would take 13
minutes to start the program each time..this is another story...