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 currently facing a debate regarding the Internet Explorer's setting 'Initialize and script ActiveX controls not marked as safe for scripting'.

I have been maintaining an in-house application that uses Outlook's and Word's automation to send email and generate letters. As it is an internal application, the url of the application is detected as 'Local Intranet'.

Our Sysadmins have changed the GPO of our workstation and disabled this setting. Unfortunately, this broke the script that was automating Office. Now we have a debate around the questions:

  1. should we change this setting back?
  2. or change the security of the local intranet zone to low (which would allow the script to run - with a prompt)?
  3. or should we re-develop the application in order not to use office automation?

Of course, as a developer, I would recommend the first or the second solution. But, I'd like to make sure that I'm not asking for something that would put our company's security at stake.

Does anyone have any experience? feedback on such a topic?

share|improve this question
up vote 1 down vote accepted

I would change it back. Local Intranet only includes local sites and services (unless others have been added, but this can be controlled through GPO), and as such, should provide a level of trust since they're administered directly. If that's not good enough for your IT then you'll probably have to redesign the code. I would not recommend turning the security level down to low, since this isn't necessary to achieve your stated goal (basically it's overkill).

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.