Volume Activation Management Tool (VAMT) – Links and Notes

Managing Activation Using the Volume Activation Management Tool (VAMT)

Manage Activation Using VAMT 2.0_White Paper

Using VAMT 2.0 – Video

Manage Activations Using VAMT_ [www.diendansvitc.net] – Video

Managing Office 2010 Activations using the Volume Activation Management Tool (VAMT 2.0) – Video

Volume Activation Management Tool (VAMT) 2.0 – Download

Product Activation Using VAMT 2.0 – Download


Microsoft Licensing – Links and Notes

Key Management Service (KMS).
KMS uses a host computer to establish an activation service on your local company network. With a KMS host you can activate thousands of computers at the same time when they regularly connect to the company network. If you use a KMS host to activate Windows, you can use the same host to activate Office 2010.

Multiple Activation Key (MAK).
With MAK, each computer activates Office 2010 with the Microsoft hosted activation servers over the Internet or by phone. MAK is recommended when you have fewer than 50 computers to activate, and for computers that are not regularly connected to the company network.

Volume Activation

Volume Activation 2.0 Technical Guidance – Downloads

Frequently Asked Questions About Volume License Keys

Fundamentals of Volume Activation

Multiple Activation Key (MAK) Activation

Key Management Service (KMS) Activation

Microsoft Office 2010 KMS Host License Pack

Adding Drivers into a Windows Server 2008 Windows Deployment Services Boot Image – Links and Notes

The functionality as described here is only available when installing images of the following operating systems:
Windows Vista with SP1 / Windows 7
Windows Server 2008 / Windows Server 2008 R2

If you use or have used Windows Deployment Services (WDS) to deploy Windows Vista, Windows 7 or Windows Server 2008 images, one of the more common problems you may encounter is having the deployment process fail as a result of a missing compatible network driver in the boot image (boot.wim) used by the deployment server.  The network driver provides the neccesary level of communication needed between the deployment server and the system receiving a Windows image to allow for a successful deployment.

The process begins at the system receiving an image by the invocation of a Network Boot (usually a PXE boot).  The system will request an IP address via DHCP.  Once the system has an IP address, an administrator will have an option to proceed with a network service boot and begin the deployment process using WDS.  The boot image (boot.wim) is provided by WDS during this phase of the deployment.  The boot.wim needs to contain a compatible network driver for the network adapter on the system receiving the image.  Once the Boot.wim has a compatible network device driver available, the image deployment process can proceed.

With previous versions of WDS, the process to inject a new driver was command line driven, and that option is still available. It was an involved enough process that I never got around to working through the steps.  I tended to use what I felt were simple, alternative methods to complete the deployment, such as having a common network card I could quickly drop into a system, or use a compatible USB NIC.

With the version of Windows Deployment Services that comes with Windows Server 2008, Microsoft has included a GUI driven utility within WDS that makes adding new network and graphics drivers to the boot.wim pretty easy.

PeteNetLive.com has created a video that quickly steps you through the process of injecting a driver into the boot.wim.  I link to it below.  To help make the process go a bit more smoothly, I suggest creating a folder on the WDS server to hold any drivers you add. I created a folder called !DriverInjection within the Remote Install folder (RemInst share) on the deployment server. You can than make a subfolder for each driver you intend to add to the boot.wim.  Even if you are only adding one driver now, creating a simple structure to organize these drivers and keep them available will help if you add new drivers in the future, or need to round up the drivers again.

The link to the video that shows how to add drivers to a Windows Deployment Services boot image is currently available at PetNetLive.com and at YouTube.  See the links below


Adding Drivers into a Boot Image on Windows Deployment Services

Managing and Deploying Driver Packages

Managing Driver Packages:

-> Extract and Add Driver Packages:

-> Scenario 1: Deploy Driver Packages Based on the Plug and Play Hardware of the Client:

Error message when you start a PXE client to connect to a WDS server on a Windows Server 2008-based computer:
“WdsClient: An error occurred while starting networking”

Network Service Boot

Access Your Work PC From a Remote Location Using Remote Web Workplace

Important Notes:

  • These instructions were written for Small Business Server 2003 Remote Web Workplace
  • Remote Web Workplace requires Internet Explorer
  • Before you attempt to connect to your workstation, you will need to know the name of the workstation you are connecting to

Using Internet Explorer, go to the Small Business Server Remote Web Workplace Website.
If you are presented with the notice There is a problem with this website’s security certificate, select Continue to this website (not recommended).

From the Welcome to Windows Small Business Server 2003 page.
Select Remote Web Workplace.

If not presented with this welcome screen, proceed to the next step.

Enter your username and password and select Log On.

From the Main Menu, select Connect to Client Desktops.

Scroll thru the list of Computers and locate your workstation.
Highlight your workstation, then select Connect.

A Remote Desktop Connection window will pop up.
Select Connect.

You should now be presented with your work PC’s desktop and can logon and use your workstation PC.

Determine the Name of Your Windows 7 or Vista Computer

Enable and configure the Remote Web Workplace

Unable to Enter Text Within the Body of an Email Using Outlook Web Access (OWA)

When accessing your email using Outlook Web Access on an Exchange 2003 mail server, you find you are unable to compose or reply to a message.  Instead of being able to place your cursor in the body of the email message, you see a square with a red “x” in the body of the message.

This problem can occur as a result of a security update applied to the Exchange 2003 Server.  The workstation attempting to access Outlook Webmail does not have the current security update applied.

To resolve this issue:
Connect to your Outlook Web Access (OWA)
From your OWA, click on the “options” in the left Task Pane.

In the right hand frame, under the ‘E-mail Security’ option, select ‘Download’ to install or upgrade the S/MIME Control. This will download the S/MIME add-on.

A ‘Security Warning’ window should pop-up asking  ‘Do you want to run or save this file? Select ‘Run’.
Follow the prompts to complete the installation.

After installing the security update you may be presented with the notification: ‘This website wants to run the following add-on: Microsoft (R) Dynamic HTML Editing Control’.
Right click on the notification and select ‘Run Add-on’ to activate the control

The Red X should be gone and you should now be able to compose an email.

Implementing Outlook Web Access with the S/MIME Control

How to Install the Outlook Web Access S/MIME Control

Configure Message Security in OWA 2003

Windows 7 Service Pack 1 – Links

 Service Pack 1 (SP1) for Windows Server 2008 R2 and Windows 7 (Technet)


Steps to Follow Before you Install Windows 7 Service Pack 1 From the Microsoft Download Center

Learn How to Install Windows 7 Service Pack 1 (SP1)

How to Uninstall Windows 7 Service Pack 1 (SP1)

Service Pack Center

Windows Recovery Environment (Windows RE) – Links


Windows Recovery Technical Reference

 Windows Recovery Environment (RE): The Solution When A Computer Won’t Boot (Windows 7)

Replace Default Windows 7/Server 2008 R2 Recovery Environment in Diagnostic and Recovery Toolset Version 6.5

Remote Server Administration Tools for Windows Server 2008


Remote Server Administration Tools for Windows 7 enables IT administrators to manage roles and features that are installed on computers running Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003, from a remote computer that is running Windows 7.

Some of the tools in this download package include:
DHCP Server Tools
DNS Server Tools
Failover Clustering Tools
Group Policy Management Tools
Hyper-V Tools
Server Manager

Remote Server Administration Tools for Windows 7 can be installed ONLY on computers that are running the Enterprise, Professional, or Ultimate editions of Windows 7.

Installing Remote Server Administration Tools for Windows 7
Excerpted from the RSA Tools Download page

You must be an Administrator on the computer on which you want to install the Administration Tools pack.

Only one copy of Remote Server Administration Tools for Windows 7 can be installed on a computer at one time.  Before you install a new package, remove any existing copies of Remote Server Administration Tools for Windows 7. This includes going from the Windows 7 version to the Windows 7 version with SP1 or installing RSAT for a different languages.

1. On a computer that is running Windows 7, download the Remote Server Administration Tools for Windows 7 package.

2. Double-click to start the Remote Server Administration Tools for Windows 7 Setup Wizard.

3. Complete the steps presented by the installation wizard, and then click Finish to exit the wizard when installation is completed.

Accessing the Remote Server Administration Tools for Windows 7
1. Click Start, click Control Panel, and then click Programs and Features.

2. In the Programs and Features area, click Turn Windows features on or off (See image).

3. Click Continue if you are prompted by User Account Control .

4. In the Windows Features dialog box, expand Remote Server Administration Tools.

5. Select the remote management tools that you want to install (See image).

6. Click OK.

Configure the Start menu to display the Administration Tools shortcut, if it is not already there.
1. Right-click Start, and then click Properties.

2. On the Start Menu tab, click Customize.

3. In the Customize Start Menu dialog box, scroll down to System Administrative Tools, and then select Display on the All Programs menu and the Start menu. Click OK.  Shortcuts for snap-ins installed by Remote Server Administration Tools for Windows 7 are added to the Administrative Tools list on the Start menu.


Description of Remote Server Administration Tools for Windows 7 (KB958830)

Download the Remote Server Administration Tools for Windows 7 with Service Pack 1 (SP1)

Installing Remote Server Administration Tools (RSAT) for Windows 7

Group Policy management for IT pros

Symantec Mail Security 6.x for MS Exchange (Links)

 Mail Security for Microsoft Exchange 6.x

Pre-install FAQ for Symantec Mail Security 6.5 for Microsoft Exchange

How to Install Symantec Information Foundation Mail Security 6.x for Microsoft Exchange 2000/2003

Cannot Establish Remote Desktop Connection With Windows 2008 Server

  • This article makes an assumption that you are generally familiar with creating a Remote Desktop Connection, or have followed instructions available elsewhere to create a Remote Desktop Connection.
  • There are documents on the internet that do a fine job covering the building of a remote connection.  For information on configuring a Remote Desktop Connection see the article ‘Use Remote Desktop To Access Other Computers On a Small Office or Home Network’ under the Links section.
  • This article addresses a specific issue I have encountered with both Windows Server 2008 and Windows 7.  This problem and a possible solution are covered here.

Issue:  One of the common tasks you might want to complete after building a Windows 2008 Server is to set up a Remote Desktop Connection to allow you access from your workstation or other remote location.  However, after you finish building a Windows 2008 Server, either as a stand-alone or a workgroup server, you are unable to establish a Remote Desktop Connection.

After creating the Remote Desktop Connection for your Windows Server, you get the following error:

Remote Desktop can’t find the computer “(Server Name)” . This might mean that “(Server Name)” does not belong to the specified network. Verify the computer name and domain that you are trying to connect to.

This can be caused by something as simple as typing in an incorrect Machine name in the Computer field.

However, the issue I have been encountering after completing the server installation is that (by default) the Network type is set to Public Network. This is a secure setting that limits discovery of other computers and the use of the network by the Windows Server.

If the server is on a secure network, or are using the server for training purposes, you can quickly open up the security on the system by setting the network to Private Network.  This will allow the server to see computers and devices, and makes the server discoverable. It also opens the port that allows the Remote Desktop Connection.

To Set the Network Location from Public to Private:
Open the Control Panel
Select Network and Sharing Center
The default Network is set to (Public Network)
Select Customize

Under Set Network Location
Set the Location Type to  Private
Select Next
Select Close

You should now be able to use Remote Desktop Connection software to remotely control the server.

Remote Desktop Services in Windows Server 2008 R2

Use Remote Desktop To Access Other Computers On a Small Office or Home Network

Enable Remote Desktop

How to Remotely Enable Remote Desktop (Terminal Services or RDP) via Registry in Windows 2000/XP/2000/Vista/2008

Configuring Windows Server 2008 Remote Desktop Administration