February, 2008

What NAP is and how it works?

Yesterday was the first Windows 2008 event in Canada. The first event was in Toronto and had almost 3000 attendees. Twenty MVPs participated in Ask-The-Expert and I was one of them :). One of the commonly asked questions was question about “What NAP is and how it works?“

So, I’d like to show what posted on TheLazyAdmin.com about NAP:
With the recent launch of Windows Server 2008 you are no doubt spending all your free time playing around with everything new. One thing you might be playing around with is Network Access Protection. There is a great document on getting a DHCP based NAP lab set up but one thing the document is missing is how to configure the NAP client in XP SP3. In Windows Vista you simply start the service then enable the client through the NAP Client Configuration MMC (napclcfg.msc) but XP SP3 does not include the MMC. So how does one configure the NAP Client without a Nap Client configuration tool? Netsh, that is how!

To enable the NAP Client on XP SP3 you need to do the following:

1. Start –> Run –> Services.msc
2. Change the Network Access Protection Agent service to start automatically
3. Start the Network Access Protection Agent service
4. Start –> Run –> CMD.exe
5. Type netsh nap client set enforcement ID = ##### Admin = “Enable”
6. Start –> Run –> GPEdit.msc
7. Drill down to Computer Configuration | Administrative Templates | Windows Components | Security Center
8. Enable the Security Center
9. Start –> Run –> Services.msc
10. Start the Security Center service

You will need to replace the ##### with the ID based on whichever enforcement method you are using. You can use the following IDs for the various enforcement methods:

• DHCP = 79617
• RAS = 79618
• IPSec = 79619
• TS Gateway = 79621
• EAP = 79623

For more labs and information see:

Step-by-Step Guide: Demonstrate IPsec NAP Enforcement in a Test Lab

Step-by-Step Guide: Demonstrate 802.1X NAP Enforcement in a Test Lab

Step-by-Step Guide: Demonstrate VPN NAP Enforcement in a Test Lab

Windows Server 2008, Microsoft SQL Server 2008 and Microsoft Visual Studio 2008 Launched!

Yesterday was a Largest Enterprise Launch in company history includes Windows Server 2008, Microsoft SQL Server 2008 and Microsoft Visual Studio 2008; focuses on Security, Web, Virtualization and Better Business intelligence.

SoftGrid 4.1 SP1 and 4.2 HFRU2 Now Available

This cumulative update for SoftGrid v4.1 SP1 and v4.2 provides the latest updates to SoftGrid.

New capabilities
This update provides the following new capabilities:

• SoftGrid now supports deployment of Virtual Application .msi files that are generated by the MSI Utility for Microsoft Application Virtualization to SoftGrid clients that are running Microsoft Windows 2000 or Windows 2000 Server/Advanced Server and that have Terminal Services enabled.
• SoftGrid 4.2 HFRU2 now supports Windows Vista Service Pack 1 (SP1).

Please Note:  The 4.1 SP1 KB article incorrectly identifies Windows Vista Service Pack 1 (SP1) as a new capability of 4.1 SP1 HFRU2.  We’re in the process of changing the article now so you should see it updated soon.

SoftGrid 4.1 SP1 HFRU2 Bits: http://support.microsoft.com/kb/938497
SoftGrid 4.2 HFRU2 Bits: http://support.microsoft.com/kb/941408

Changes in Functionality from Windows Server 2003 to Windows Server 2008

The document describes new features and technologies, which were not available in Windows Server 2003, that will help to increase the security of computers running Windows Server 2008, increase productivity, and reduce administrative overhead.

Released on 7th Feb 2008,  containing 341 pages. Download here

Group Policy Settings Reference for Windows Server 2008

Windows Server 2008 delivered with Administrative template files (.admx/.adml) policy settings for computer and user configurations. The policy settings included in this spreadsheet cover Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP Professional and Windows 2000.

To configure these policy settings we need use Group Policy objects (GPOs). In addition, this spreadsheet includes the following categories of security policy settings:

• Account Policies (Password Policy, Account Lockout Policy, and Kerberos Policy)
• Local Policies (Audit Policy, User Rights Assignment, and Security Options)
• Event Log
• Restricted Groups
• System Services
• Registry
• File System policy settings

Download here

Extending the Windows Server 2008 evaluation period

Evaluating Windows Server 2008 software does not require product activation. Any edition of Windows Server 2008 may be installed without activation, and it may be evaluated for 60 days. Additionally, the 60-day evaluation period may be reset (re-armed) three times.

When the initial 60-day evaluation period nears its end, you can run the Slmgr.vbs script to reset the evaluation period. To do this, follow these steps:

1. Click Start, and then click Command Prompt.
2. Type slmgr.vbs -dli, and then press ENTER to check the current status of your evaluation period.
3. To reset the evaluation period, type slmgr.vbs –rearm, and then press ENTER.
4. Restart the computer.

This resets the evaluation period to 60 days.

WAIK 1.1 for Windows Vista SP1 & Windows Server 2008

As many of you know, Microsoft released Windows Vista Service Pack 1 and Windows Server 2008 to Manufacturing RTM ! So, it’s a time to take a last Windows Automated Installation Kit (Windows AIK). The Windows Automated Installation Kit (Windows AIK) is designed to assist corporate IT professionals customize and deploy the Windows Vista and Windows Server 2008 families of operation systems. The Windows Automated Installation Kit (Windows AIK) is a set of tools and documentation that support the configuration and the deployment of Windows operating systems. By using Windows AIK, you can perform unattended Windows installations, capture Windows images with ImageX, create Windows PE images and much more.

Download WAIK1.1 here

Change Default Prompt in Windows Server 2008 - Server Core

If you are planning to deploy Windows Server 2008 - Server Core installations, I think you should use the following tip, that I’ve found few days ago on very good blog, blogs.technet.com/aralves.

Think about you have more than one Windows Server 2008 - Server Core box and you are connecting to them by using the Terminal Services Remote Programs. What you get? Just a simple prompt. By using following tip you can change the default prompt and add at least the servername. To do this, simple open the registry editor and navigate to the following key:

HKLM\System\CurrentControlSet\Control\Session Manager\Environment

Find a key called Prompt, if it’s not there create one using the following settings.

Value Name: Prompt
Data Type: REG_EXPAND_SZ
Value Data: $_Server:[%servername%]$_Username:[%username%]$_$T$_$p$g

With this value you get the prompt as shown in the picture.

Here are some of the special codes you can use:

* $A - & (Ampersand)
* $B - | (pipe)
* $C - ( (Left parenthesis)
* $D - Current date
* $E - Escape code (ASCII code 27)
* $F - ) (Right parenthesis)
* $G - > (greater-than sign)
* $L - < (less-than sign)
* $N - Current drive
* $P - Current drive and path
* $Q - = (equal sign)
* $S - (space)
* $T - Current time
* $_ - Carriage return and linefeed
* $$ - $ (dollar sign)

Now you will always know on which server you are working

Microsoft Releases Windows Vista Service Pack 1 and Windows Server 2008 to Manufacturing RTM

Windows Vista Service Pack 1 (SP1) was released to manufacturing today and will start being available to customers in March, starting with Microsoft Volume Licensing customers. Windows Server 2008 was also released to manufacturing today and will be available for purchase to new customers on March 1.

Microsoft doesn’t recommend creating Vista ‘Lite’

As many of you know, it’s possible to create a “Lite” version of operating system by using well know program vLite. But, recently Microsoft said in an e-mail to CNET News.com:

“Microsoft does not recommend using any tool to strip out applications from Windows Vista prior to installing it on your system, as it may affect your ability to download future Windows updates and service packs, and may cause your system to become unstable,” 

So, think twice before you creating Vista ‘Lite’