Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are looking to publish a ClickOnce application to a large Active Directory network which has to abide by the FDCC (Federal Desktop Core Configuration) which is an OMB-mandated security configuration.

Does anyone have experience with this security configuration and ClickOnce applications? The application requires the ability to read a file the logged in user has access to.

We are also concerned with extra security setting being placed in the future that may stop the ClickOnce application from working.

How robust is the ClickOnce method for deployment when you start to lock down the computer?
What settings must be in place for a ClickOnce to function?

Thank you,

edit: I am also asking this on stackoverflow since it kind of rides both sides.

share|improve this question
up vote 1 down vote accepted

This presentation looks to say that VS2005 ClickOnce is not FIPS compliant. It's a little hard to discern, but also maybe hints that VS2008 ClickOnce is. See pages 3 and 4.

One thing in favor is that ClickOnce doesn't require local admin which is a no-no per FDCC. This is an interesting question (+1) as I'm a .NET developer and deploy via ClickOnce quite often. I'll keep looking and thinking on this.

share|improve this answer
Thanks for the link. It looks like click once will work. I'll post what I find out during testing. – Keith Sirmons May 12 '09 at 2:49

This FDCC blog post says explicitly that you can retire ActiveX controls and replace them with ClickOnce applications. Sorry, no help for any of your other questions.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.