Any of the following could have done this:
1. An administrative policy deployment.
2. Installation or patching of any application.
3. "Manual" policy change or reversion to defaults by a sufficiently
privileged user.
4. Alteration of policy by any application run under the identity of a
sufficiently privileged user.
One possibility under #2 is installation of a .NET Framework service pack.
See
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q317399 for
details.
HTH,
Nicole
[quoted text, click to view] "spg" <spg@discussions.microsoft.com> wrote in message
news:43C63332-616A-44AF-B48E-49C1476FC91F@microsoft.com...
>I have a VB.net app running on the 1.0 framework. The exe resides on a
> network share and all of the client computers have a full trust configured
> to
> the shared folder from which the exe runs. The app was deployed one year
> ago
> and the clients had no trouble using it. This is a seasonal app and it's
> time to use it again. Some clients have reported not being able to access
> the app. Investigation found that the security trust had disappeared.
> Once
> it is re-established the app works as expected. My question: what could
> possibly be deleting the trust? When asked what has changed on the
> computer
> all of those affected had the same answer "Nothing." (...that they are
> aware
> of when the question is asked.)
>
> Any ideas, anybody?