Hi,

We are a software development team for a retail company, all of the programs
we develop are for use internally on our network. Recently, we have moved
towards thin-client technology with everyone running remote desktops using
Citrix.

This proves to be troublesome when deploying - only domain administrators
can actually install anything onto the Citrix Server itself. Since we have a
farm of about 30 servers, we have to schedule in a deployment date & ensure
the Citrix team carry out the install correctly and replicate it across all
servers!

We've got around this in the past by deploying onto a network share that has
user specific data in. Eg;

\\SharePath\data\UserName\Program Files\MyExecutable.exe

This ensures we are in control of our programs, we have an auto-update
program that rolls out any fixes or amendments we have made to programs -
there is no major delay in rolling out a new version.

In the .Net framework, there are security issues when running from a shared
network drive. What is the best approach to allow us to continue to run an
executable from a share path, using resources located locally on the Citrix
Server?

We have a Strong Name key file for our department that we sign all of our
programs with. If the Citrix team amend the security configuration for the
.Net framework on each of the servers, can we trust all assemblies signed
with our Strong Name Key so that they can run from network shares (as in .7
of .NET Framework Enterprise Security Policy Administration and Deployment
FAQ?)

Is this the best approach to allow us to continue share deployment? It should mean that the Citrix team only have to do one bit of configuration, then we can roll out updates as and when...?


Thanks