leedesmond’s blog

Here is a condensed list of the common FAQ that I put together as part of my current technologist / evangelist role for the Windows Server 2008 customer tour in the Gulf region

1. Is WSv included in Windows Server 2008 Standard Edition?
Yes, Standard, Enterprise and Data Center Editions of Windows Server 2008.

2. Hardware requirements to run WSv?
x64 platform with hardware assisted virtulization technology from Intel VT or AMD-V (and lots of RAM memory plus plenty of storage space on a fast n-core CPU machine).

3. Can x64 applications (64-bit) such as Exchange Server 2007 run on WSv?
Yes. Besides 32-bit guest operating system (virtual machines), 64-bit is now supported.

4. Does Virtual Machine Additions still work?
This has been replaced by the improved Windows Server virtualization Integration Components. Virtual Machine Additions must first be uninstalled if present.

5. The network adapter in the VM ported from Virtual Server to WSv is no longer recognized.
Workaround is to add a legacy network adapter to the VM. In WSv, the network adapter seen by the guest OS is not an emulated device (DEC/Intel 21140 Ethernet adapter). It is an entirely new, high performance, purely synthetic device available as part of the Windows Server virtualization Integration Components call Microsoft VMBus Network Adapter.

6. How do I backup my live, running VMs?
WSv supports Volume Shadow Services (VSS) natively, meaning no downtime for backup is needed.

7. Can I add a Windows Server 2008 to an existing Windows 2003 Active Directory environment?
Yes. For more information, search my blog post for “Windows Server 2008 in Windows Server 2003 Active Directory”.

8. Is upgrade from Windows 2000 Server to Windows Server 2008 supported?
No. Only an upgrade from Windows Server 2003 is possible.

No Comments »

You have Windows Server 2008 RC0 (full version) or Windows Server Core 2008 RC0 virtual machines built using Virtual PC 2007 and intend to port them over to Windows Server Virtualization (WSv). There are a number of points that you must take care of to make this work for you. In essence, you have to go through the entire process of creating a new VM and attach the existing VHD.

• commit changes from Undo disks if needed
• cleanly shut down the VM (not left in saved state)
• audio if enabled will be ignored
• network adapter will no longer be recognized
• add a legacy network adapter (before starting VM). This will show up as Intel 21140-Based PCI Fast Ethernet Adapter (Emulated).
• take a snapshot to establish the initial undo state (previously enabled Undo setting is lost)
• Virtual Machine Additions must be removed before you can install the Virtualization Guest Components (Integration Services Setup Disk)
• after the 2 mandatory machine restarts to complete the Virtualization Guest Components setup, the desktop wallpaper will have the words Test Mode plastered at the 4 corners
• a number of components and integration services such as the WSV network adapter, OS shutdown and seamless mouse pointer integration do not work
• the vmc file will no longer be used (replaced by new XML files and GUID named folders under Virtual Machines and Snapshots)
• use Ctrl-Alt-left arrow key to release the captured mouse
• Ctrl-Alt-End key instead of Right Alt-Del to send Ctrl-Alt-Del to the guest OS

Due to significant hardware changes detected, Windows Product Activation may be triggered and you have only 3 days to activate the product (even if previously activated).

Tested on Windows Server 2008 x64 RC0 with WSv.

Technorati tags: Longhorn, Windows Server 2008, Windows Server Core 2008, Windows Server Virtualization

No Comments »

With Windows Server 2008 Virtualization (WSV), the Virtual Network terminology and configuration has changed slightly. When you first start the WSV Virtualization Management Console, you are prompted to specify two physical network adapters to create the initial virtual network switches on the host - one for use by guest OS and the other dedicated for remote administration purposes. Having the latter is optional but recommended.

For the selected physical network adapter, a new Local Area Connection - Virtual Network will be created and the TCP/IP settings will also be automatically configured. For those familiar with VMware Workstation, this setup will look somewhat familiar.

From the Virtual Network Switch Management console, this maps to the ‘Physical network adapter’ connection type that is associated with the External network switch type . Similarly, the network switch types Internal and None correspond to the connection types Host and None (Not Connected) respectively.

More information:

Virtual Server 2005 R2 by default creates a number of virtual networks depending on the physical count of network adapters on the host machine. Say you have one wired and one wireless network adapter each. In this case, two virtual networks will be automatically created and their names have the form External Network (Manufacturer name and adapter type). These are stored on disks with the vnc file extension. Additionally, Internal Network is created that is not bound to any physical network adapter. This is used typically to setup a pristine network where communications is confined among virtual machines. You can then use the Virtual Server Administration WebSite or the Virtual Machine Remote Control Client to access the guest operating system.

Technorati tags: Longhorn, Windows Server 2008, Windows Server Core 2008, Windows Server Virtualization

No Comments »

One common task most IT Administrators often have to deal with is the addition of new domain controllers to an existing Active Directory infrastructure. You can easily add a machine installed with Windows Server 2008 as a DC to a Windows Server 2003 AD environment.

Take for example you have a single forest, single AD domain call swissitpro.local that has 2 DCs on WS03 R2 (SP1). To successfully add WS08 to this configuration, take note of the following points:

1. switch to Windows 2003 domain functional level for the target domain (default: Windows 2000 mixed mode)
2. Windows 2000 forest functional level (default) and above
3. run adprep /forestprep on the WS03 DC with the Schema Master role*
4. execute adprep /domainprep on a WS03 DC with the Infrastructure Master role*
5. run adprep /rodcprep on a WS03 DC*
   This optional step is recommended as early as possible if you are planning to deploy read-only domain controllers in the future.
6. on the WS08, run dcpromo and specify the FQDN of the target AD. Tick the additional options DNS and GC. The former will by default be AD-integrated and the DNS zone can take some time to replicate. You do not need to join the WS08 as a member server in advance.

A minimum of one WS08 machine (full, not Server Core) must be present to enable a RODC or Server Core to be added as domain controllers to AD. In addition, Windows 2003 forest functional level or higher is needed.

* from WS08 DVD

See also:
Migration from Windows 2003 server to Longhorn server
Known Issues for Installing and Removing AD DS (updated Feb 2009)

Technorati tags: Longhorn, Windows Server 2008, Windows Server Core 2008, Windows Server Virtualization

No Comments »

PowerGadgets is a neat application that extends PowerShell to crunch and transform your data into great looking charts, gauges or maps. Use it to visually plot an executive summary of current Exchange mailbox sizes in the server farm and walk away with that elusive budget to upgrade or expand your hardware and storage capacity.

You can change to a favorite chart type from the gallery on the fly, toggle on or off the data grid, data points or legend, or move the mouse pointer over an area of interest and all similar data type will be highlighted for you, all automatically without additional programming.

This is one power pack that belongs to every PowerShell user’s toolbox.

Technorati tags: PowerShell, Exchange Server

No Comments »

In case you are not aware, there are a number of new applications, Windows components, services or updates that were released for or work with Windows Server 2008 RC0. Here is a short list I have put together to date:

• Internet Information Services (IIS) 7.0 Manager (XP / 2003 / Windows Vista SP1)
• Windows Media Services 2008 for Windows Server 2008 RC0
• FTP7 for Windows Server 2008 RC0
• Deployment 4 Beta 3 for Automated Operating System Deployment
• Windows Vista SP1* (Windows Vista and Window Server 2008—Better Together!)
• Windows XP SP3 Beta Preview*

* sign up online at http://connect.microsoft.com

No Comments »

You can use Windows PowerShell even if you’re still on Exchange Server 2003. Walk through straightforward command examples to learn how to use PowerShell and WMI to automate administrative tasks.

The above is a brief synopsis of my latest feature article “Manage Exchange Server 2003 Using Windows PowerShell and WMI” published online at Exchange & Outlook Pro VIP (9 Oct 2007). Check it out and share with all of us on what you think.

Technorati tags: PowerShell, Exchange Server

No Comments »

In addition to the list I outlined in the previous post, the Microsoft Management Console (MMC) 3.0 must also be installed as a pre-requisite in an Exchange 2007 setup. However, this already comes as part of Windows Server 2003 R2 and above (SP1 included - read more here) so you do not need to install it separately.

Here is the text version of the E2k7 setup screen:

Plan
Read about Microsoft Exchange Server 2007

Install
Step 1: Install .NET Framework 2.0
Step 2: Install Microsoft Management Console (MMC)
Step 3: Install Microsoft Windows PowerShell
Step 4: Install Microsoft Exchange
Step 5: Get Critical Updates for Microsoft Exchange

Enhance
Read about Microsoft Exchange Hosted Services
Read about Microsoft Forefront Security for Exchange Server
Install Forefront Security for Exchange Server

Note that Step 4 will remain enabled as the same option can be used to add or modify Exchange Server 2007 roles, for example.

See also KB907265 (MMC 3.0 update is available for Windows Server 2003 and for Windows XP)

Technorati tags: Exchange Server

No Comments »

There are a number of prerequisites that must be fulfilled before you start the journey to install Exchange 2007 on a newly built Windows Server 2003 SP1 machine. Besides the necessary hardware platform - 64-bit for production and 32-bit for test/lab/administrative workstation - the setup program lists them on the very first page, namely .NET Framework 2.0 and Windows PowerShell*. Nevertheless, it will run a readiness check in preparation for actual install only after these pre-requisites have been satisfied. You can leave setup running while you install the latter and setup is smart enough to recognize them.

In order to pass the readiness check for setup to commence installation, the World Wide Web service and .NET Framework 2.0 patch (KB926776) must already be in place. And do not forget some of the core infrastructure requirements for a basic setup as well (more info here and here).

Preparation is key so save yourself some time and frustration before you pop that Exchange 2007 CD in.

* both link to x86 versions; x64 versions are available separately.

Technorati tags: Exchange Server

No Comments »

For a heavily pounded domain controller server that also holds the global catalog role, Exchange 2003 may cause the following error to be logged in the Application log. At first glance, this points squarely at Active Directory, which is a reasonable assumption as a result of AD replication or network latency issues, for instance:

Severity: Major Node: EXserver
State: Active Service: Directory Access
Owner: Group: EXSPI-DSACCESS
First Received: 09/10/2003 16:27:33 Object: LDAP
Last Received: 09/10/2003 20:28:03 Application: MSExchangeDSAccess
Message Text:
EventID: 0xC004080D (2061) - Process MAD.EXE (PID=1234). An LDAP search call
failed - Server=dcgc.domain.local Error code=80040957. Base DN=,
Filter=(legacyExchangeDN=), Scope=2.

Look closer, this event may not get logged immediately when the Exchange server first comes online. It actually shows up only after a certain period of time in production. After some investigations, the error was traced to the MSExchangeMTA / Directory Access diagnostics settings in Exchange 2003. Out-of-the-box, Exchange 2003 has diagnostics turned off. Even if DSAccess diagnostic is at the minimum setting, the event continued to be logged. Left unchecked, it could seriously degrade Exchange’s performance.

Best practice: toggle it on only when instructed by Microsoft or certified partners. Ensure that all diagnostics settings are set to None; this is the resolution found for this issue (thanks to all my colleagues involved).

Technorati tags: Exchange Server

No Comments »