Microsoft Application Compatibility Toolkit 5.6

The Microsoft Application Compatibility Toolkit (ACT) version 5.6 contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Windows 7®, Windows Vista®, a Windows Update, or a new version of Windows Internet Explorer® in your environment.

What caught my eye. If you enable compatibility logging for Internet Explorer if ACT is not installed then some event ids in Event Viewer lack descriptions. I installed it to add functionality to Event Viewer

Microsoft Application Compatibility Toolkit 5.6

Check firewall not blocking shared printing

Couple of quick ways to check if the firewall is blocking a shared printer.

From a remote machine open an command prompt and use

Net View \\print-server-name

This should return a list that includes the name of the shared printer generally you can now eliminate the network or firewall as an issue.

or download PortQry from Microsoft and check the required ports are open on the computer sharing the printer.

Use PortQry or PortQueryUI to check TCP ports 445 & 139

If computers are not on the same LAN segment don’t just check the print server firewall ensure their is not another firewall between the computers.

Remote Desktop printing add additional drivers

I run Hyper-V with a mix of 32bit/64bit operating systems and would like to print from any of the remote session to my local printer.

My ancient HP LaserJet 1200 has the default Windows 7 32bit driver installed but I cannot get the additional 64bit driver to install.

I seem to remember a similar situations in the past with a network printer where the resolution was the printer had a different name in the 32 bit inf than the 64 bit. I hacked the 64 bit inf file and ensured the names matched exactly … with success.

Did not want to go through that again and thought that I would try the HP Universal Printing PCL 5 drivers installed from the command line with PNPUTIL.EXE … why … never used it and wanted to try it.

• Downloaded both versions of the driver from HP
• Installed the 32 bit driver from an elevated command prompt
• pnputil –a c:\<path>\*.inf
• and did the same with the 64 bit
• opened the printer properties, advanced tab and switched the driver to the HP Universal Printer PCL5

As I did not intend blogging this I forget whether I had to go to the share tab and add the additional drivers or whether it was smart enough to find it for itself.

Painless and I can now print from 64bit VMs

Print spooler must be running on server and client

Read something like this … “In order to print to a server based printer the print spooler must also be running on the client” … time to experiment … It is the same with a Remote Desktop session and a locally attached printer?

Did an experiment, I used Remote Desktop from a Window 7 machine to a Windows 7 VM. Remote Desktop is setup allow the remote session to use the local printer.

Succeeded in printing from notepad on the remote machine to the redirected LaserJet on my local machine.

Shut down the spooler on the remote session with

net stop spooler

and tried to print from notepad got this error and

everything disappeared the from Select Printer except Add Printer

restarted using net start spooler

all the printer came back.

Remote/Shared printing … the spooler must be running on both machines not just the box the printer is plugged into.

Search Active Directory from the Desktop

To quickly get the AD search box up on a domain joined PC create a shortcut on the desktop with item location set to.

%SystemRoot%\SYSTEM32\rundll32.exe dsquery,OpenQueryWindow

Domain joined PC only, try to do it from a workgroup you will get:

Server 2008 R2 core remotely edit group policy.

Windows Server 2008 R2 Core remotely edit group policy.

I have a Windows 7 computer that I use to manage Hyper-V on Windows 2008 R2 core. Both machine are in the same workgroup.

On Windows 7

Start, In Search Programs and Files enter MMC

When the Microsoft Management Console starts open File, Add/Remove Snap-in…

Select “Group Policy Object Editor” click Add > button.

Click Browse  button

Select Another computer and type the name or IP of remote machine

Click OK then Finish and you should now be able to View\Edit the Local Group Policy on the remote server

Remote Server Manager on Server 2008 R2 Core

I have a long standing Hyper-V test environment running on Server 2008 R2 core. Recently decided to try Server Manager remotely from a Windows 7 machine to manage the 2008 Core.

Both machines are in the same workgroup and successfully configured for Remote Desktop. The Remote Server Administration Tool for Windows 7 are installed.

Run Server Manager on Windows 7 then try connecting to Hyper-V server and I get this error:

TechNet: Remote Management with Server Manager

On Hyper-V Server

Ensured that I had done the following

• From sconfig.cmd
• selected 4) Configures Remote Management the server 
• then 3) Allow Server Manager Remote Management

this had no effect on the error there was no need to reboot the server as I had already installed PowerShell but did so anyway but still could not connect with Server Manager

On Windows 7 Client

net start winrm

winrm set winrm/config/client @{TrustedHosts="RemoteComputerName"}

Replace RemoteComputerName with server name

This failed on initial attempt

I should have run the following command first because machines where in workgroup not domain.

reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f

Running the winrm command again and Server Manger could connect to my Hyper-V server.

Still got errors on Server Manager components but a step forward.

Device Manager Error

Resolution Enable Remote Access to Device Manager

See this very useful blog post

Enabling Remote Access to Device Manager on Server Core

Virtual Disk Management Error

Resolution Windows 7 Firewall

Inbound rules on Windows 7 needed to be set

Remote Volume Management - Virtual Disk Service (RPC)

Remote Volume Management - Virtual Disk Service Loader (RPC)

Migrating Hyper-V 2008 R2 Core to 2012 Core

I may be wrong … but on first evaluation it appears you cannot transfer Virtual Machines with Snapshots.

It would also appear that an in-place upgrade from Hyper-V 2008 running on core to Hyper-V 2012 running on 2012 core is not on.

Looks like my upgrade to Hyper-V 2012 will have to be put on hold.

Here is a Microsoft TechNet Blog explaining how to migrate from Hyper-V 2008 to Hyper-V 2012 on the core.

Step-by-Step: Migrating to FREE Microsoft Hyper-V 2012 Servers AND Clusters from 2008 R2 and VMware

Hyper-V 2008 Core Memory Requirements

Windows 2008 core apparently needs only 3GB of disk space and less than 256MB of RAM. Add Hyper-V and my task manager says 727MB.

Small Business Server 2011 with only 4GB RAM

If you follow minimum requirements you would allocate 8GB ram for a virtual machine just to evaluate Small Business Server 2011.

Although the motherboard on my Hyper-V system should take this in it stride the jump from its current 8GB to its 16GB max is expensive.

So do I need 8GB to evaluate SBS 2011? I couldn’t if I wanted to as Hyper-V needs some RAM so I gave it 6GB and it fired up. What about 4GB SBS 2008 worked on this and the only reason 2011 wants 8GB is Exchange 2010.

Here is a shot of my task manager running with 4GB of memory and the Exchange Console running. Onwards with the evaluation.

I have also stopped WSUS from downloading but not disabled it.

Disable WSUS on Small Business Server

I have various versions of Small Business Server running in an evaluation environment and don’t want WSUS constantly downloading updates here is a useful guide from the SBS Diva Blog. Should work for SBS 2008 and 2011.

The guide demonstrates how to prevent WSUS downloading updates without mangling the system. You in effect just put WSUS into a monitoring state.

SBS Diva Blog: Disable WSUS on Small Business Server 2008

Rearm Windows 2011 SBS Evaluation

Something always comes up when you are trying to evaluate a product and X weeks/months later you fire up the virtual machine and the Grace Period has expired.

slmgr.vbs –dli          will tell you how long the grace period is.

slmgr.vbs –rearm     will reset it.

I have tried this on a couple of product the latest being an evaluation version of Small Business Server 2011 and the grace period was reset to 30 days.

If memory serves me then it should work for Windows 2008 evaluations.

Don’t know if it works with products like Windows 8 or Server 2012.

Performance Tuning for Windows Server 2008

Came across this guide while looking for something else may be of use if I ever get time to read it.

This guide describes important tuning parameters and settings that can result in improved performance for the Windows Server 2008 operating system. Each setting and its potential effect are described to help you make an informed judgment about its relevance to your system, workload, and performance goals.

Performance Tuning Guidelines for Windows Server 2008

Windows 7 RTM … No more support

As of April 9th 2013 you cannot get mainstream support from Microsoft for Windows 7 without a service pack.

Mainstream Support stops for Windows 7 13th January 2015

Windows 7 in it virgin form is no longer supported you have to add at least service pack 1.

When does Windows SP1 support end?

Looks like SP1 support will end 13th January 2015

SP1 support stops 24 months after the release of SP2 or when mainstream support stops on 13th January 2015 which ever comes first.

See the following Springboard Series Blog

Windows 7 RTM End Of Support Is Right Around The Corner

Windows Firewall Learning Roadmap

If you are new to Windows Firewall with Advanced Security, this topic can help you identify what you need to learn to fully understand and use all of the features available in Windows Firewall with Advanced Security.

It includes prerequisite topics that cover a variety of networking fundamentals.

TechNet: Windows Firewall with Advanced Security Learning Roadmap

Lost Your Microsoft Licence Key

Where is the product key … in what file … in what filing cabinet. If you’ve worked in technical support for any length of time you know product keys are more likely to be found down the back of a filing cabinet than in it … or were thrown out with the packaging.

Here is a tool from the CNET web site that gives you the keys of the Microsoft products installed on your machine … could not be bothered getting out of my seat to hunt for my Office licence key!!!

http://download.cnet.com/ProduKey/3000-2094_4-10457063.html

Windows 7 Firewall Documentation

Windows 7 Firewall Documentation

Here are some useful TechNet links covering the subject:

TechNet: Windows Firewall with Advanced Security and IPsec

TechNet: Networking and Access Technologies - Windows Firewall

Windows Firewall with Advanced Security Getting Started Guide

Netsh Commands for Windows Firewall with Advanced Security

From TechNet Networking Blog

Deployment: Windows Firewall and Group Policy

User State Migration Tool 4.0 User's Guide

Windows® User State Migration Tool (USMT) 4.0 is a scriptable command-line tool that provides a highly-customizable user-profile migration experience for IT professionals.

USMT includes two components, ScanState and LoadState, and a set of modifiable .xml files: MigApp.xml, MigUser.xml, and MigDocs.xml. In addition, you can create custom .xml files to support your migration needs. You can also create a Config.xml file to specify files or settings to exclude from the migration.

TechNet User State Migration Tool 4.0 User's Guide

USMT used in the migration to Windows 7 note the following:

You can migrate a 32-bit operating system to a 64-bit operating system. However, you cannot migrate a 64-bit operating system to a 32-bit operating system.

USMT 4.0 does not support any of the Windows Server® operating systems, Windows 2000, or any of the starter editions for Windows XP, Windows Vista, or Windows 7. In addition, USMT 4.0 only supports migration from Windows XP with Service Pack 2 or Service Pack 3.

BranchCache Early Adopter’s Guide

Looking for some study materials on BrancheCache as it relates Windows 7 and Windows Server 2008 R2.

TechNet BranchCache Early Adopter’s Guide

Windows 7 DiskPart & Virtual Hard Disks (VHD)

DiskPart.exe and managing Virtual Hard Disks (VHDs) in Windows 7

A useful MSDN blog posting about creating and attaching VHDs in Windows 7

Used DISKPART to create a VHD on my Windows 7 laptop dumped some files in it then moved it to my Hyper-V server and attached it to a Windows 7 Ultimate VM. Just a thing to know.

DiskPart.exe and managing Virtual Hard Disks (VHDs) in Windows 7

Microsoft Baseline Security Analyzer 2.2

The Microsoft Baseline Security Analyzer provides a streamlined method to identify missing security updates and common security misconfigurations. MBSA 2.2 is a minor upgrade to correct minor issues and add optional catalog support.

MBSA 2.2 runs on Windows Server 2008 R2, Windows 7, Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP and Windows 2000 systems and will scan for missing security updates, rollups and service packs using Microsoft Update technologies. MBSA will also scan for common security misconfigurations (also called Vulnerability Assessment checks) using a known list of less secure settings and configurations for all versions of Windows, Internet Information Server (IIS) 5.0, 6.0 and 6.1, SQL Server 2000 and 2005, Internet Explorer (IE) 5.01 and later, and Office 2000, 2002 and 2003 only.

You can scan the local machine or a group of machines

Download the 32bit or 64bit version from the link below:

Microsoft Baseline Security Analyzer 2.2 (for IT Professionals)

Windows 2008 R2 rearm activation grace period

You know how it is new version of a Microsoft product appears and the old evaluation versions disappear. Windows 2008 Evaluation version get it before it’s gone.

How to manually rearm the 10 day activation grace period
When the initial 10-day activation period nears its end, you can run the Slmgr.vbs script to reset it back to 10 days. 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 activation period.

3. To reset the activation period, type slmgr.vbs –rearm, and then press ENTER.

4. Restart the computer.
This resets the activation period to 10 days, and can be used up to four times. After this you will need to either activate or reinstall the evaluation.

Get the Windows 2008 R2 evaluation download from here:

Windows 2008 R2 Evaluation Virtual Machine

Network Access Protection (NAP)

Network Access Protection

Network Access Protection (NAP) is a feature in Windows Server 2008 that controls access to network resources based on a client computer’s identity and compliance with corporate governance policy. NAP allows network administrators to define granular levels of network access based on who a client is, the groups to which the client belongs, and the degree to which that client is compliant with corporate governance policy. If a client is not compliant, NAP provides a mechanism to automatically bring the client back into compliance and then dynamically increase its level of network access.

In short is your OS AV up to date if not I am going to use WSUS and and the AV server to patch your system before I allow you to access the network.

TechNet Network Access Protection