Software Distribution policy disabled?

[Curmudge0n]

We deploy a fair amount of software via group policy. Normally we configure the policy to install from a network location that everyone has access to and things work very well. I've noticed that now, sometimes, when I check for the software on a user's machine I'll find that it's not there. I'll go look the policy and the software installation has gone into a disabled status without any human intervention that we're aware of. I'm wondering if anyone else has seen this or has any thoughts? The best thing that I can come up with is that the network location of the MSI is unavailable temporarily and the policy sets itself to disabled due to a lack of resources. I don't really have any way to confirm that though.

[jeremym]

Your hypothesis is interesting, but I have never heard this before.

In other words, the GPO can't "gray out" because the MSI location isn't there.

[Curmudge0n]

Thanks for the response. I should have used better language- the policy is still active and as far as i can tell applies, but the software installation status changes from "Assigned" to "disabled". Assuming that your comment is still applicable, what are the mechanisms by which the MSI installation can go to a "disabled" state? Obviously, one can right click and set to disabled, but are there any other avenues that lead to a disabled state that anyone is aware of?