Archive

Archive for February, 2009

Just Released: the Security Compliance Management Toolkit Series

February 27th, 2009 Comments off

Launch the Download Now
We have just released the Security Compliance Management Toolkit series to help you secure and monitor Windows ® operating systems and 2007 Microsoft ® Office.
This series marks the next generation of Microsoft security guides…(read more)

Categories: Solution Accelerator Tags:

Example of using the new NPS templates feature in Windows Server 2008 R2

February 26th, 2009 No comments

In a previous NAP blog entry, we described the new NPS templates feature in Windows Server 2008 R2. In this blog entry, we show an example of using a template for a RADIUS shared secret.


Templates for RADIUS shared secrets allow users to specify a shared secret that can be reused when configuring RADIUS clients and remote RADIUS servers in the Network Policy Server snap-in. To create and use a RADIUS shared secret template, do the following:


1. From the Network Policy Server snap-in, open the Templates Management node.


2. In the console tree, right-click Shared Secrets, and then click New.


3. In Template Name, type a name for the shared secret template, and then either manually specify the shared secret or have NPS automatically generate one.


4. Click OK to save changes.


To use the RADIUS shared secret template, configure a RADIUS client, a remote RADIUS server, or a remote RADIUS server template and specify the template name for the shared secret, rather than manually configuring a shared secret or having NPS generate one. The following figure shows an example.


NPS template example


To view which RADIUS clients, remote RADIUS servers, and remote RADIUS server templates use a specific RADIUS shared secret template, right click the name of the RADIUS shared secret template, and then click View Usage.


 



NAP Product Team

Example of using the new NPS templates feature in Windows Server 2008 R2

February 26th, 2009 No comments

In a previous NAP blog entry, we described the new NPS templates feature in Windows Server 2008 R2. In this blog entry, we show an example of using a template for a RADIUS shared secret.


Templates for RADIUS shared secrets allow users to specify a shared secret that can be reused when configuring RADIUS clients and remote RADIUS servers in the Network Policy Server snap-in. To create and use a RADIUS shared secret template, do the following:


1. From the Network Policy Server snap-in, open the Templates Management node.


2. In the console tree, right-click Shared Secrets, and then click New.


3. In Template Name, type a name for the shared secret template, and then either manually specify the shared secret or have NPS automatically generate one.


4. Click OK to save changes.


To use the RADIUS shared secret template, configure a RADIUS client, a remote RADIUS server, or a remote RADIUS server template and specify the template name for the shared secret, rather than manually configuring a shared secret or having NPS generate one. The following figure shows an example.


NPS template example


To view which RADIUS clients, remote RADIUS servers, and remote RADIUS server templates use a specific RADIUS shared secret template, right click the name of the RADIUS shared secret template, and then click View Usage.


 



NAP Product Team

Example of using the new NPS templates feature in Windows Server 2008 R2

February 26th, 2009 No comments

In a previous NAP blog entry, we described the new NPS templates feature in Windows Server 2008 R2. In this blog entry, we show an example of using a template for a RADIUS shared secret.


Templates for RADIUS shared secrets allow users to specify a shared secret that can be reused when configuring RADIUS clients and remote RADIUS servers in the Network Policy Server snap-in. To create and use a RADIUS shared secret template, do the following:


1. From the Network Policy Server snap-in, open the Templates Management node.


2. In the console tree, right-click Shared Secrets, and then click New.


3. In Template Name, type a name for the shared secret template, and then either manually specify the shared secret or have NPS automatically generate one.


4. Click OK to save changes.


To use the RADIUS shared secret template, configure a RADIUS client, a remote RADIUS server, or a remote RADIUS server template and specify the template name for the shared secret, rather than manually configuring a shared secret or having NPS generate one. The following figure shows an example.


NPS template example


To view which RADIUS clients, remote RADIUS servers, and remote RADIUS server templates use a specific RADIUS shared secret template, right click the name of the RADIUS shared secret template, and then click View Usage.


 



NAP Product Team

Example of using the new NPS templates feature in Windows Server 2008 R2

February 26th, 2009 No comments

In a previous NAP blog entry, we described the new NPS templates feature in Windows Server 2008 R2. In this blog entry, we show an example of using a template for a RADIUS shared secret.


Templates for RADIUS shared secrets allow users to specify a shared secret that can be reused when configuring RADIUS clients and remote RADIUS servers in the Network Policy Server snap-in. To create and use a RADIUS shared secret template, do the following:


1. From the Network Policy Server snap-in, open the Templates Management node.


2. In the console tree, right-click Shared Secrets, and then click New.


3. In Template Name, type a name for the shared secret template, and then either manually specify the shared secret or have NPS automatically generate one.


4. Click OK to save changes.


To use the RADIUS shared secret template, configure a RADIUS client, a remote RADIUS server, or a remote RADIUS server template and specify the template name for the shared secret, rather than manually configuring a shared secret or having NPS generate one. The following figure shows an example.


NPS template example


To view which RADIUS clients, remote RADIUS servers, and remote RADIUS server templates use a specific RADIUS shared secret template, right click the name of the RADIUS shared secret template, and then click View Usage.


 



NAP Product Team

Example of using the new NPS templates feature in Windows Server 2008 R2

February 26th, 2009 Comments off

In a previous NAP blog entry, we described the new NPS templates feature in Windows Server 2008 R2. In this blog entry, we show an example of using a template for a RADIUS shared secret.


Templates for RADIUS shared secrets allow users to specify a shared secret that can be reused when configuring RADIUS clients and remote RADIUS servers in the Network Policy Server snap-in. To create and use a RADIUS shared secret template, do the following:


1. From the Network Policy Server snap-in, open the Templates Management node.


2. In the console tree, right-click Shared Secrets, and then click New.


3. In Template Name, type a name for the shared secret template, and then either manually specify the shared secret or have NPS automatically generate one.


4. Click OK to save changes.


To use the RADIUS shared secret template, configure a RADIUS client, a remote RADIUS server, or a remote RADIUS server template and specify the template name for the shared secret, rather than manually configuring a shared secret or having NPS generate one. The following figure shows an example.


NPS template example


To view which RADIUS clients, remote RADIUS servers, and remote RADIUS server templates use a specific RADIUS shared secret template, right click the name of the RADIUS shared secret template, and then click View Usage.


 



NAP Product Team

Example of using the new NPS templates feature in Windows Server 2008 R2

February 26th, 2009 No comments

In a previous NAP blog entry, we described the new NPS templates feature in Windows Server 2008 R2. In this blog entry, we show an example of using a template for a RADIUS shared secret.

Templates for RADIUS shared secrets allow users to specify a shared secret that can be reused when configuring RADIUS clients and remote RADIUS servers in the Network Policy Server snap-in. To create and use a RADIUS shared secret template, do the following:

1. From the Network Policy Server snap-in, open the Templates Management node.

2. In the console tree, right-click Shared Secrets, and then click New.

3. In Template Name, type a name for the shared secret template, and then either manually specify the shared secret or have NPS automatically generate one.

4. Click OK to save changes.

To use the RADIUS shared secret template, configure a RADIUS client, a remote RADIUS server, or a remote RADIUS server template and specify the template name for the shared secret, rather than manually configuring a shared secret or having NPS generate one. The following figure shows an example.

NPS template example

To view which RADIUS clients, remote RADIUS servers, and remote RADIUS server templates use a specific RADIUS shared secret template, right click the name of the RADIUS shared secret template, and then click View Usage.

 

NAP Product Team

NPS templates in Windows Server 2008 R2

February 17th, 2009 No comments

NPS templates, the flagship feature of NPS in Windows Server 2008 R2, provides a huge reduction in cost of ownership and deployment for all NPS environments. NPS templates separate common RADIUS configuration elements such as RADIUS shared secrets and RADIUS clients from the configuration running on the server. When referenced, the NPS setting inherits the values configured in the specified template. A change in the template changes the corresponding value in all of the places in which the template is referenced. For example, a single RADIUS shared secret template can be referenced for multiple RADIUS clients and remote RADIUS servers. When you change the RADIUS shared secret template, the change is inherited by all of the RADIUS clients and remote RADIUS servers in which that RADIUS shared secret template is referenced.


You can also use NPS templates to assist in configuration with referencing them. For example, you can create a RADIUS client template that contains common settings (such as the vendor type or shared secret) for a specific group of RADIUS clients (such as all wireless APs from a specific vendor). When you create a new RADIUS client, you can select the RADIUS client template to obtain the common settings. When you unselect the template, the inherited settings remain and you can configure individual settings, such as the RADIUS client’s IP address.


Note  Template settings are not supported by commands in the netsh nps context. Using netsh nps commands will remove the reference to the template and change the configuration element specified in the command.


NPS template settings can also be easily migrated and synchronized across multiple NPS servers.


The following types of configuration elements use templates:


·         RADIUS shared secret


·         RADIUS clients


·         Remote RADIUS servers


·         IP filters


·         Health policies


·         Remediation server groups


You can configure templates for these configuration elements from the Templates Management node of the Network Policy Server snap-in. The following figure shows an example.


Templates in the new NPS snap-in


For a larger version of this figure, click here.


Individual templates can be added, edited, duplicated, or deleted. After they are configured, they can be referenced and de-referenced in the appropriate dialog boxes in the Network Policy Server snap-in.


The following table lists the different types of templates and where they are used in the Network Policy Server snap-in.


























Template


Where it is used


RADIUS shared secret


When creating or configuring RADIUS clients, remote RADIUS server group members, RADIUS client templates, or remote RADIUS server templates


RADIUS clients


When creating or configuring RADIUS clients


Remote RADIUS servers


When creating or configuring remote RADIUS server group members


IP filters


When configuring IP Filters settings for a network policy


Health policies


When creating or configuring health policies


Remediation server groups


When creating or configuring remediation server groups



NAP Product Team

NPS templates in Windows Server 2008 R2

February 17th, 2009 No comments

NPS templates, the flagship feature of NPS in Windows Server 2008 R2, provides a huge reduction in cost of ownership and deployment for all NPS environments. NPS templates separate common RADIUS configuration elements such as RADIUS shared secrets and RADIUS clients from the configuration running on the server. When referenced, the NPS setting inherits the values configured in the specified template. A change in the template changes the corresponding value in all of the places in which the template is referenced. For example, a single RADIUS shared secret template can be referenced for multiple RADIUS clients and remote RADIUS servers. When you change the RADIUS shared secret template, the change is inherited by all of the RADIUS clients and remote RADIUS servers in which that RADIUS shared secret template is referenced.


You can also use NPS templates to assist in configuration with referencing them. For example, you can create a RADIUS client template that contains common settings (such as the vendor type or shared secret) for a specific group of RADIUS clients (such as all wireless APs from a specific vendor). When you create a new RADIUS client, you can select the RADIUS client template to obtain the common settings. When you unselect the template, the inherited settings remain and you can configure individual settings, such as the RADIUS client’s IP address.


Note  Template settings are not supported by commands in the netsh nps context. Using netsh nps commands will remove the reference to the template and change the configuration element specified in the command.


NPS template settings can also be easily migrated and synchronized across multiple NPS servers.


The following types of configuration elements use templates:


·         RADIUS shared secret


·         RADIUS clients


·         Remote RADIUS servers


·         IP filters


·         Health policies


·         Remediation server groups


You can configure templates for these configuration elements from the Templates Management node of the Network Policy Server snap-in. The following figure shows an example.


Templates in the new NPS snap-in


For a larger version of this figure, click here.


Individual templates can be added, edited, duplicated, or deleted. After they are configured, they can be referenced and de-referenced in the appropriate dialog boxes in the Network Policy Server snap-in.


The following table lists the different types of templates and where they are used in the Network Policy Server snap-in.


























Template


Where it is used


RADIUS shared secret


When creating or configuring RADIUS clients, remote RADIUS server group members, RADIUS client templates, or remote RADIUS server templates


RADIUS clients


When creating or configuring RADIUS clients


Remote RADIUS servers


When creating or configuring remote RADIUS server group members


IP filters


When configuring IP Filters settings for a network policy


Health policies


When creating or configuring health policies


Remediation server groups


When creating or configuring remediation server groups



NAP Product Team

NPS templates in Windows Server 2008 R2

February 17th, 2009 No comments

NPS templates, the flagship feature of NPS in Windows Server 2008 R2, provides a huge reduction in cost of ownership and deployment for all NPS environments. NPS templates separate common RADIUS configuration elements such as RADIUS shared secrets and RADIUS clients from the configuration running on the server. When referenced, the NPS setting inherits the values configured in the specified template. A change in the template changes the corresponding value in all of the places in which the template is referenced. For example, a single RADIUS shared secret template can be referenced for multiple RADIUS clients and remote RADIUS servers. When you change the RADIUS shared secret template, the change is inherited by all of the RADIUS clients and remote RADIUS servers in which that RADIUS shared secret template is referenced.


You can also use NPS templates to assist in configuration with referencing them. For example, you can create a RADIUS client template that contains common settings (such as the vendor type or shared secret) for a specific group of RADIUS clients (such as all wireless APs from a specific vendor). When you create a new RADIUS client, you can select the RADIUS client template to obtain the common settings. When you unselect the template, the inherited settings remain and you can configure individual settings, such as the RADIUS client’s IP address.


Note  Template settings are not supported by commands in the netsh nps context. Using netsh nps commands will remove the reference to the template and change the configuration element specified in the command.


NPS template settings can also be easily migrated and synchronized across multiple NPS servers.


The following types of configuration elements use templates:


·         RADIUS shared secret


·         RADIUS clients


·         Remote RADIUS servers


·         IP filters


·         Health policies


·         Remediation server groups


You can configure templates for these configuration elements from the Templates Management node of the Network Policy Server snap-in. The following figure shows an example.


Templates in the new NPS snap-in


For a larger version of this figure, click here.


Individual templates can be added, edited, duplicated, or deleted. After they are configured, they can be referenced and de-referenced in the appropriate dialog boxes in the Network Policy Server snap-in.


The following table lists the different types of templates and where they are used in the Network Policy Server snap-in.


























Template


Where it is used


RADIUS shared secret


When creating or configuring RADIUS clients, remote RADIUS server group members, RADIUS client templates, or remote RADIUS server templates


RADIUS clients


When creating or configuring RADIUS clients


Remote RADIUS servers


When creating or configuring remote RADIUS server group members


IP filters


When configuring IP Filters settings for a network policy


Health policies


When creating or configuring health policies


Remediation server groups


When creating or configuring remediation server groups



NAP Product Team

NPS templates in Windows Server 2008 R2

February 17th, 2009 No comments

NPS templates, the flagship feature of NPS in Windows Server 2008 R2, provides a huge reduction in cost of ownership and deployment for all NPS environments. NPS templates separate common RADIUS configuration elements such as RADIUS shared secrets and RADIUS clients from the configuration running on the server. When referenced, the NPS setting inherits the values configured in the specified template. A change in the template changes the corresponding value in all of the places in which the template is referenced. For example, a single RADIUS shared secret template can be referenced for multiple RADIUS clients and remote RADIUS servers. When you change the RADIUS shared secret template, the change is inherited by all of the RADIUS clients and remote RADIUS servers in which that RADIUS shared secret template is referenced.


You can also use NPS templates to assist in configuration with referencing them. For example, you can create a RADIUS client template that contains common settings (such as the vendor type or shared secret) for a specific group of RADIUS clients (such as all wireless APs from a specific vendor). When you create a new RADIUS client, you can select the RADIUS client template to obtain the common settings. When you unselect the template, the inherited settings remain and you can configure individual settings, such as the RADIUS client’s IP address.


Note  Template settings are not supported by commands in the netsh nps context. Using netsh nps commands will remove the reference to the template and change the configuration element specified in the command.


NPS template settings can also be easily migrated and synchronized across multiple NPS servers.


The following types of configuration elements use templates:


·         RADIUS shared secret


·         RADIUS clients


·         Remote RADIUS servers


·         IP filters


·         Health policies


·         Remediation server groups


You can configure templates for these configuration elements from the Templates Management node of the Network Policy Server snap-in. The following figure shows an example.


Templates in the new NPS snap-in


For a larger version of this figure, click here.


Individual templates can be added, edited, duplicated, or deleted. After they are configured, they can be referenced and de-referenced in the appropriate dialog boxes in the Network Policy Server snap-in.


The following table lists the different types of templates and where they are used in the Network Policy Server snap-in.


























Template


Where it is used


RADIUS shared secret


When creating or configuring RADIUS clients, remote RADIUS server group members, RADIUS client templates, or remote RADIUS server templates


RADIUS clients


When creating or configuring RADIUS clients


Remote RADIUS servers


When creating or configuring remote RADIUS server group members


IP filters


When configuring IP Filters settings for a network policy


Health policies


When creating or configuring health policies


Remediation server groups


When creating or configuring remediation server groups



NAP Product Team

NPS templates in Windows Server 2008 R2

February 17th, 2009 Comments off

NPS templates, the flagship feature of NPS in Windows Server 2008 R2, provides a huge reduction in cost of ownership and deployment for all NPS environments. NPS templates separate common RADIUS configuration elements such as RADIUS shared secrets and RADIUS clients from the configuration running on the server. When referenced, the NPS setting inherits the values configured in the specified template. A change in the template changes the corresponding value in all of the places in which the template is referenced. For example, a single RADIUS shared secret template can be referenced for multiple RADIUS clients and remote RADIUS servers. When you change the RADIUS shared secret template, the change is inherited by all of the RADIUS clients and remote RADIUS servers in which that RADIUS shared secret template is referenced.


You can also use NPS templates to assist in configuration with referencing them. For example, you can create a RADIUS client template that contains common settings (such as the vendor type or shared secret) for a specific group of RADIUS clients (such as all wireless APs from a specific vendor). When you create a new RADIUS client, you can select the RADIUS client template to obtain the common settings. When you unselect the template, the inherited settings remain and you can configure individual settings, such as the RADIUS client’s IP address.


Note  Template settings are not supported by commands in the netsh nps context. Using netsh nps commands will remove the reference to the template and change the configuration element specified in the command.


NPS template settings can also be easily migrated and synchronized across multiple NPS servers.


The following types of configuration elements use templates:


·         RADIUS shared secret


·         RADIUS clients


·         Remote RADIUS servers


·         IP filters


·         Health policies


·         Remediation server groups


You can configure templates for these configuration elements from the Templates Management node of the Network Policy Server snap-in. The following figure shows an example.


Templates in the new NPS snap-in


For a larger version of this figure, click here.


Individual templates can be added, edited, duplicated, or deleted. After they are configured, they can be referenced and de-referenced in the appropriate dialog boxes in the Network Policy Server snap-in.


The following table lists the different types of templates and where they are used in the Network Policy Server snap-in.


























Template


Where it is used


RADIUS shared secret


When creating or configuring RADIUS clients, remote RADIUS server group members, RADIUS client templates, or remote RADIUS server templates


RADIUS clients


When creating or configuring RADIUS clients


Remote RADIUS servers


When creating or configuring remote RADIUS server group members


IP filters


When configuring IP Filters settings for a network policy


Health policies


When creating or configuring health policies


Remediation server groups


When creating or configuring remediation server groups



NAP Product Team

NPS templates in Windows Server 2008 R2

February 17th, 2009 No comments

NPS templates, the flagship feature of NPS in Windows Server 2008 R2, provides a huge reduction in cost of ownership and deployment for all NPS environments. NPS templates separate common RADIUS configuration elements such as RADIUS shared secrets and RADIUS clients from the configuration running on the server. When referenced, the NPS setting inherits the values configured in the specified template. A change in the template changes the corresponding value in all of the places in which the template is referenced. For example, a single RADIUS shared secret template can be referenced for multiple RADIUS clients and remote RADIUS servers. When you change the RADIUS shared secret template, the change is inherited by all of the RADIUS clients and remote RADIUS servers in which that RADIUS shared secret template is referenced.

You can also use NPS templates to assist in configuration with referencing them. For example, you can create a RADIUS client template that contains common settings (such as the vendor type or shared secret) for a specific group of RADIUS clients (such as all wireless APs from a specific vendor). When you create a new RADIUS client, you can select the RADIUS client template to obtain the common settings. When you unselect the template, the inherited settings remain and you can configure individual settings, such as the RADIUS client’s IP address.

Note  Template settings are not supported by commands in the netsh nps context. Using netsh nps commands will remove the reference to the template and change the configuration element specified in the command.

NPS template settings can also be easily migrated and synchronized across multiple NPS servers.

The following types of configuration elements use templates:

·         RADIUS shared secret

·         RADIUS clients

·         Remote RADIUS servers

·         IP filters

·         Health policies

·         Remediation server groups

You can configure templates for these configuration elements from the Templates Management node of the Network Policy Server snap-in. The following figure shows an example.

Templates in the new NPS snap-in

For a larger version of this figure, click here.

Individual templates can be added, edited, duplicated, or deleted. After they are configured, they can be referenced and de-referenced in the appropriate dialog boxes in the Network Policy Server snap-in.

The following table lists the different types of templates and where they are used in the Network Policy Server snap-in.

Template

Where it is used

RADIUS shared secret

When creating or configuring RADIUS clients, remote RADIUS server group members, RADIUS client templates, or remote RADIUS server templates

RADIUS clients

When creating or configuring RADIUS clients

Remote RADIUS servers

When creating or configuring remote RADIUS server group members

IP filters

When configuring IP Filters settings for a network policy

Health policies

When creating or configuring health policies

Remediation server groups

When creating or configuring remediation server groups

NAP Product Team

The Hyper-V Security Guide

February 12th, 2009 Comments off

The benefits of virtualization are more evident than ever. Microsoft Hyper-V™ technology allows consolidation of workloads that are currently spread across multiple underutilized servers onto a smaller number of servers. This capability provides you with…(read more)

Categories: Hyper-V, SA, security Tags:

Microsoft Security Advisory (961040): Vulnerability in SQL Server Could Allow Remote Code Execution – Version: 2.0

Revision Note: V2.0 (February 10, 2009): Advisory updated to reflect publication of security bulletin.
Summary: Microsoft has completed the investigation into a public report of this vulnerability. We have issued MS09-004 to address this issue. For more information about this issue, including download links for an available security update, please review MS09-004. The vulnerability addressed is the Microsoft XML Core Services Vulnerability – CVE-2008-5416.

Categories: Uncategorized Tags:

Microsoft Security Advisory (961040): Vulnerability in SQL Server Could Allow Remote Code Execution – 2/10/2009

February 10th, 2009 Comments off

Revision Note: V2.0 (February 10, 2009): Advisory updated to reflect publication of security bulletin. Advisory Summary:Microsoft has completed the investigation into a public report of this vulnerability. We have issued MS09-004 to address this issue. For more information about this issue, including download links for an available security update, please review MS09-004. The vulnerability addressed is the Microsoft XML Core Services Vulnerability – CVE-2008-5416.

Categories: Uncategorized Tags:

Changes to the NAP user experience in Windows 7

February 9th, 2009 No comments

Windows 7 and Windows Server 2008 R2 are now available as public betas. In Windows 7, the NAP client user interface (UI) has been integrated into the Windows Action Center (previously known as the Windows Security Center). For example, Network Access Protection notifications appear in the list of messages when you click the Action Center message in the notification area of the Windows 7 desktop.


The following figure shows an example of how a noncompliant NAP client running Windows 7 displays its status in the Windows Action Center.


NAP notification in the new Windows 7 Action Center 


For a larger version of this figure, click here


When you click View Solution, Windows 7 displays the Network Access Protection status dialog box (also known as the Napstat UI).


 


NAP Product Team

Categories: configuration, Windows 7 Tags:

Changes to the NAP user experience in Windows 7

February 9th, 2009 No comments

Windows 7 and Windows Server 2008 R2 are now available as public betas. In Windows 7, the NAP client user interface (UI) has been integrated into the Windows Action Center (previously known as the Windows Security Center). For example, Network Access Protection notifications appear in the list of messages when you click the Action Center message in the notification area of the Windows 7 desktop.


The following figure shows an example of how a noncompliant NAP client running Windows 7 displays its status in the Windows Action Center.


NAP notification in the new Windows 7 Action Center 


For a larger version of this figure, click here


When you click View Solution, Windows 7 displays the Network Access Protection status dialog box (also known as the Napstat UI).


 


NAP Product Team

Categories: configuration, Windows 7 Tags:

Changes to the NAP user experience in Windows 7

February 9th, 2009 No comments

Windows 7 and Windows Server 2008 R2 are now available as public betas. In Windows 7, the NAP client user interface (UI) has been integrated into the Windows Action Center (previously known as the Windows Security Center). For example, Network Access Protection notifications appear in the list of messages when you click the Action Center message in the notification area of the Windows 7 desktop.


The following figure shows an example of how a noncompliant NAP client running Windows 7 displays its status in the Windows Action Center.


NAP notification in the new Windows 7 Action Center 


For a larger version of this figure, click here


When you click View Solution, Windows 7 displays the Network Access Protection status dialog box (also known as the Napstat UI).


 


NAP Product Team

Categories: configuration, Windows 7 Tags:

Changes to the NAP user experience in Windows 7

February 9th, 2009 No comments

Windows 7 and Windows Server 2008 R2 are now available as public betas. In Windows 7, the NAP client user interface (UI) has been integrated into the Windows Action Center (previously known as the Windows Security Center). For example, Network Access Protection notifications appear in the list of messages when you click the Action Center message in the notification area of the Windows 7 desktop.


The following figure shows an example of how a noncompliant NAP client running Windows 7 displays its status in the Windows Action Center.


NAP notification in the new Windows 7 Action Center 


For a larger version of this figure, click here


When you click View Solution, Windows 7 displays the Network Access Protection status dialog box (also known as the Napstat UI).


 


NAP Product Team

Categories: configuration, Windows 7 Tags: