Super User is a question and answer site for computer enthusiasts and power users. 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

I recently installed an application that would not run until I made an exception for it in Windows 2008 Server. I've seen the same on a Windows 7 system. Assuming these are commercial applications without trojans, what is the risk in doing this?

share|improve this question
up vote 1 down vote accepted

Well that is the idea behind 2008s DEP. Previously it was set for services and essential programs only. On Server 2008 though it takes the other approach and lets you open up access accordingly. This is actually a more secure way of doing this, denying all and granting access as needed. As long as they are as you said, "commercial" applications, there shouldn't be a problem in making an exception for it, in fact that is one of its features and that is why it is there.

A short post to help you understand why on a Server 2008 machine, it shouldn't be much of a problem.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .