Microsoft Knowledge Base Email Alertz

This article discusses information about deploying a Microsoft .NET Framework enterprise security policy before you install the .NET Framework. This article also describes issues that you may experience when you install the .NET Framework with a...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 816641 - Last Review: January 11, 2007 - Revision: 2.2

INFO: Deploy an Enterprise Security Policy Before You Install the .NET Framework

On This Page

SUMMARY

This article discusses information about deploying a Microsoft .NET Framework enterprise security policy before you install the .NET Framework. This article also describes issues that you may experience when you install the .NET Framework with a restrictive enterprise security policy.

The .NET Framework Configuration tool permits you to create a Microsoft Windows Installer file that can be used to deploy an enterprise security policy installation package. The Windows Installer file runs without the .NET Framework.

MORE INFORMATION

Requirements

  • You must have security administrator permissions to deploy the enterprise security policy.

    Note Security administrator permissions are not required if the computer has a Microsoft Windows 95 operating system, a Microsoft Windows 98 operating system, or a Microsoft Windows XP operating system. Security administrator permissions are also not required if the computer has a disk with a FAT32 file system or with a FAT16 file system, or if the permissions are granted to the user by the security administrator.
  • Your interaction is not required during the deployment of the enterprise security policy installation package.

Install the Enterprise Security Policy

When you start the enterprise security policy installation package that is generated by the .NET Framework Configuration tool, the enterprise security policy configuration file (Enterprisesec.config) is deployed to the following directory:

%WindowsDirirectory%\Microsoft.Net\Framework\<installdir>\config

Note The <installdir> represents a version of the runtime that is used to create a policy file in the form of the following string:
“v” +<major>+<minor>+<build>
The following is an example:

c:\windows\microsoft.net\framework\v1.1.4322\config

The Windows Installer file that you create by using the .NET Framework Configuration tool applies only to a specific version of the .NET Framework. If you want to deploy an enterprise security policy for different versions of the .NET Framework, you must deploy a separate Windows Installer file for each version of the .NET Framework. Each version of the .NET Framework has its own .NET Framework Configuration tool.

REFERENCES

For additional information about enterprise security policy administration and about enterprise security policy deployment with the .NET Framework, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/aa302354.aspx (http://msdn2.microsoft.com/en-us/library/aa302354.aspx)

APPLIES TO
  • Microsoft .NET Framework 1.1
Keywords: 
kbinfo kbpackage kbsecurity kbpolicy kbdeployment kbconfig KB816641
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate