justin ho

Microsoft Deployment Toolkit 2008 Update 1 is offered in two versions to support Solution Accelerator component installation on x64 or x86 hosts. Select the version that corresponds with your host hardware type. Both versions of Microsoft Deployment Toolkit support deployment of x86 and x64 Windows operating systems.

Microsoft Deployment Toolkit (MDT) 2008 Update 1 unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance. The fourth generation deployment accelerator adds integration with recently released Microsoft deployment technologies to create a single path for image creation and automated installation. MDT’s tools and end-to-end guidance reduce deployment time, standardize desktop and server images, limit service disruptions, reduce post-deployment help desk costs, and improve security and ongoing configuration management.

Microsoft Deployment Toolkit technologies eliminate interaction time required to install desktop and server operating systems. Interaction at the targeted computer may take a few moments using the Lite Touch Installation (LTI) method or it can be completely automated using Zero Touch Installation (ZTI). Zero Touch Installation utilizes Microsoft System Center Configuration Manager 2007 or Systems Management Server 2003 with the Operating System Deployment Feature Pack. Lite Touch Installation can be used when software distribution tools are not in place.
Microsoft Deployment Tookit 2008 Update 1 also uses Configuration Manager 2007’s stand-alone media-initiated operating system deployment feature. This release offers project management guidance for all deployment roles and separates technical documentation for the products and technologies to facilitate automation tasks.

http://www.microsoft.com/downloads/details.aspx?familyid=3bd8561f-77ac-4400-a0c1-fe871c461a89&displaylang=en

This walkthrough describes how to build a Windows Recovery Environment (Windows RE) image. Windows RE is a solution based on Windows PE 2.0. In this example, you create a customized Windows RE image on your technician computer.

http://technet2.microsoft.com/WindowsVista/en/library/61e08b15-82d8-46bd-a5f1-7947193e6ed81033.mspx?mfr=true

A USB key that boots like a Windows 98 boot disk is useful for BIOS flashing, firmware flashing, and other scenarios where WinPE or other environments are not suitable.  Most machines don't have floppy drives now, and USB keys are much, much faster.

HP has released a utility for this purpose, and this can be downloaded here.

Alternative download links:

• http://h50178.www5.hp.com/support/PB137UA/more_info_local_17550.html
• http://h50177.www5.hp.com/support/DW978A/more_info_local_18026.html
• http://www.google.com/search?q=SP27608+site%3Ahp.com
• Unverified: http://files.filefront.com/SP27608exe/;9868201;/fileinfo.html

Additionally, you will need Windows 98 boot disk files, which I have included here.

Remote Desktop Client (RDC) 6.1 now available for XP SP2 users
We have received a lot of feedback from customers about the need for the Remote Desktop Connection client 6.1 to be made available as a standalone install for Windows XP SP2 to ease deployments of Windows 2008 Terminal Services.

In response to this feedback, we have released the Remote Desktop Connection client (RDC 6.1) for Windows XP SP2 on x86 platforms.

You can download RDC6.1 for Windows XP SP2 from the Microsoft Download Center (KB 952155): http://www.microsoft.com/downloads/details.aspx?FamilyId=6E1EC93D-BDBD-4983-92F7-479E088570AD&displaylang=en

These are some of the supported features of Remote Desktop Client 6.1 for Windows XP SP2:

• Windows Server 2008 & Windows Vista feature support
• TS Web Access support
• TS Easy Print support
• TS Remote Programs support
• TS Gateway support
• Please review the complete list of features and details about RDC6.1 for Windows XP SP2 in this Knowledge Base article: http://support.microsoft.com/?kbid=952155

RDC6.1 is now available on the following platforms:

• Windows Server 2008
• Windows Vista SP1: http://technet.microsoft.com/en-us/windows/bb738089.aspx
• Windows XP SP3: http://www.microsoft.com/downloads/details.aspx?FamilyID=68c48dad-bc34-40be-8d85-6bb4f56f5110&displaylang=en
• Windows XP SP2 (KB 952155): http://www.microsoft.com/downloads/details.aspx?FamilyId=6E1EC93D-BDBD-4983-92F7-479E088570AD&displaylang=en

More:
http://blogs.technet.com/nmercer/archive/2008/06/26/remote-desktop-client-rdc-6-1-now-available-for-xp-sp2-users.aspx

Mostly for fun, I installed Windows Server 2008 x64 on my Dell Optiplex 745 tonight.  It is an Intel Core 2 Duo E6300 1.86GHz, 2 GB RAM, WD Raptor 74GB, with a Pioneer DVR-212D DVD burner.

Started Windows 2008 Enterprise x64 install @ 12:26am
91% expanding files @ 12:33am
Reboot @ 12:34am
Completing installation @ 12:36am
Reboot @ 12:39am
Logon screen / changed password @ 12:40am
Start menu opened @ 12:41am

Zero to OS menu in 15 minutes flat.  Nice.

Symptoms:

Some of my users are unable to change their passwords via OWA on Exchange 2007 on Server 2008.  My DCs are running Server 2003.

 

Argh.

Installing the Hyper-V RC0 update for Windows Server 2008 rendered my virtual machines unable to connect to the network.

I installed the hypervisor - Hyper-V RC0 build today.  After rebooting, my network configuration would not function.  I was unable to add an External network and bind it to the NIC successfully.

I'm running Windows Server 2008 RTM x64, and I had the beta (in-box) Hyper-V code running with virtual machines.  My physical machine has two onboard NICs; one was dedicated for the host, and the other was for the virtual machines.

So I removed the HyperV role, and rebooted the box.

The box hung like this, at 78%.  I power cycled it, which restored service.  The configuration was "resumed" and the role was successfully removed, with an error.  Unfortunately, the Virtual Switches stayed in Network Connections.  I then reattempted install of the Hyper-V role.  This completed, but with an error: it wasn't able to set up the networking components.

Note that http://support.microsoft.com/default.aspx/kb/950792 describes a hang at 75%, not 78%.  I also am not using HP NICs...

Log Name:      Microsoft-Windows-Hyper-V-Network-Admin
Source:        Microsoft-Windows-Hyper-V-Network
Event ID:      14070
Level:         Error
User:          SYSTEM
Description:
Switch set up failed, name='6d861a9b-39ef-4d01-a181-e163e5a21908', external port='f6400f7a-0dea-4b1f-bf91-3a78b00092f5', internal port='30b4be1c-5c03-48a6-84ed-7f590a3ffae7', NIC='{506E5818-0E27-4E13-8835-DDC8B7393D36}', internal name='9e3e1874-09ab-423b-904e-75420369499f', internal friendly name='New Virtual Network', error=2147749889, mof code=0.
Event Xml:
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-Network" Guid="{0a18ff18-5362-4739-9671-78023d747b70}" />
    <EventID>14070</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <EventRecordID>88</EventRecordID>
    <Correlation />
    <Execution ProcessID="1088" ThreadID="1196" />
    <Channel>Microsoft-Windows-Hyper-V-Network-Admin</Channel>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
      <Switch>6d861a9b-39ef-4d01-a181-e163e5a21908</Switch>
      <ExternalPortName>f6400f7a-0dea-4b1f-bf91-3a78b00092f5</ExternalPortName>
      <InternalPortName>30b4be1c-5c03-48a6-84ed-7f590a3ffae7</InternalPortName>
      <NIC>{506E5818-0E27-4E13-8835-DDC8B7393D36}</NIC>
      <InternalName>9e3e1874-09ab-423b-904e-75420369499f</InternalName>
      <InternalFriendlyName>New Virtual Network</InternalFriendlyName>
      <Error>2147749889</Error>
      <MofCode>0</MofCode>
    </NvspSwitchSetupError>
  </UserData>
</Event>

I've posted to some MSDN blogs' comments... but I doubt I'll hear back.

So now, I have no Hyper-V machines running anymore, and I can't get rid of the Virtual Network Switches.  I have heard from some people that manually removing the entries in the registry for the NICs will cause everything to "blow up".  I'm unable to delete the Virtual Switches in Network Connections, or in Device Manager.

My physical box has production workloads on it, so I can't blast it away.  Since the "finish line is in sight," I was kind of hoping that these kinds of things wouldn't happen, especially since they shipped the beta I was running inbox with the RTM code.

I can't find any evidence of Hyper-V on Connect, so there doesn't appear to be a way to report this.

Advice:

I would suggest that you remove not only the machines, but also the virtual networks, AND the Hyper-V role, before applying the update for Hyper-V RC0.  Then reinstall the role to make sure things are cleanly in place.

Solution: (Thanks to John Howard and Keith Mange)

"netcfg -u vms_pp"
Run ProcMon and set permissions on keys as necessary (Look for ACCESS_DENIED entries) to allow this to proceed.

After this process, I rebooted and found the Virtual Network Switch adapters were still present.

1. Click Start, click Run, type msinfo32.exe in the Open box, and then click OK.
2. Expand Components, expand Network, and then click Adapter. 
3. In the right pane, you see a list of items.
4. You can see entries for the Ethernet network adaptors. 
5. Find all adapters with the name "Microsoft Virtual Switch" and note the network adapter index number. Should be something like Name [00000009] Microsoft Virtual Network Switch Adapter
6. Locate the following registry key, and then change the following registry value to 0:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\the false Ethernet network adaptor index number\Characteristics
7. Use device manager to “uninstall” the adapter.

In my case, step 7 hung - so I grabbed ProcMon and watched to see what key was causing the problem.

• 1095635 2:03:20.8945136 PM mmc.exe 2764 RegOpenKey HKLM\System\CurrentControlSet\Services\{B0E4253B-9A56-4D69-BA80-20FA4821CD5D}\Parameters\Tcpip ACCESS DENIED Desired Access: Read/Write, Delete
• 19 2:07:24.8307575 PM mmc.exe 2764 RegEnumKey HKLM\System\CurrentControlSet\Services\{B227EB3A-4453-4496-B378-D84FB0A46CFA}\Parameters SUCCESS Index: 0, Name: Tcpip
• 151188 2:11:59.6214689 PM mmc.exe 2764 RegOpenKey HKLM\System\CurrentControlSet\Services\{A17F68AB-654D-47C3-87CF-4ADFAC9C9239}\Parameters\Tcpip ACCESS DENIED Desired Access: Read/Write, Delete

Go into regedit, and set permissions on the Tcpip key so that the currently logged in user (Domain Admins, for my case) has full control.
Device manager should remove the key/adapter correctly.

Update (May 20th 2008):

Having Exchange 2007 SP1 on the physical host prevents Hyper-V from working on builds prior to RC1.  I have just installed Hyper-V RC1 today on my physical host and Hyper-V is now fully functional.  This was related to permissions in the registry at HKLM\system\currentcontrolset\services.

See also:

http://support.microsoft.com/kb/949222/ and http://support.microsoft.com/kb/949219

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3272554&SiteID=17

http://support.microsoft.com/kb/899868

Abstract:

Windows Server 2008 introduces a DNS block feature that may affect the ISA Server automatic discovery mechanism when implementing WPAD using a Windows Server 2008 DNS Server.  Therefore, additional configuration steps are necessary to get WPAD to work, when clients are running against a 2008 DNS server.

Details:

The block feature provides a global query block list to reduce vulnerability associated with dynamic DNS updates. Dynamic update makes it possible for DNS client computers to register and dynamically update their resource records with a DNS server whenever a client changes its network address or host name.  This reduces the need for manual administration of zone records, especially for clients that frequently move or change locations and use DHCP to obtain an IP address. This convenience comes at a cost, however, because an authorized client can register any unused host name, even a host name that might have special significance for certain applications. This can allow a malicious user to "hijack" a special name and divert certain types of network traffic to that user's computer. WPAD is a commonly deployed protocol vulnerable to this type of hijacking, and by default WPAD look up is disabled by the blocking mechanism.

If you want to use WPAD with a Windows Server 2008 DNS, note the following behavior:

• If WPAD entries are configured in DNS before the DNS server is upgraded to Windows Server 2008, no action is required.
• If you configure or remove WPAD after you deploy the DNS server role on a server running Windows Server 2008, you must update the block list on all DNS servers that host the zones affected by the change. The affected zones are those where you registered the WPAD servers.
• To update the block list, use the dnscmd command-line tool. Open a command line prompt, and do the following:
• To check whether the global query block is enabled, type:
  dnscmd /info /enableglobalqueryblocklist. A value of 1 is returned if the block list is enabled.
• To display the host names in the current block list, type:
  dnscmd /info /globalqueryblocklist
• To disable the block list and ensure that the DNS Server service does not ignore queries for names in the block list, type:
  dnscmd /config /enableglobalqueryblocklist 0
• To remove all names from the block list, type:
  dnscmd /config /globalqueryblocklist

Further reading:

   "DNS Server Global Query Block List" from TechNet at http://technet.microsoft.com/en-us/network/bb629410.aspx.

Source:

http://blogs.technet.com/isablog/archive/2008/02/19/windows-server-2008-dns-block-feature.aspx

Abstract:

My quest to eliminate the Dell CERC 1.5/6ch SATA (due to its poor performance) from my production environment has been a long one as I opted to wait for Windows Server 2008 and Exchange 2007 before migrating to my 3Ware card.  This post contains a summary of all the issues I encounter, and will be updated as I proceed.

Solutions:

• Backup headaches - Setting up Exchange 2007 to back up on a Windows 2008 Server:
  "Exchange 2007 Aware Backups on Windows Server 2008"
  http://blog.justinho.com/2008/03/10/Exchange2007AwareBackupsOnWindowsServer2008.aspx
• CAS problems with RPC proxy - Some tweaks are necessary to get Outlook Anywhere to work with Exchange 2007 on Server 2008
  "Outlook Anywhere RPC over HTTPS Proxy on Windows Server 2008 Fails to Communicate with Exchange 2007"
  http://blog.justinho.com/2008/03/10/OutlookAnywhereRPCOverHTTPSProxyOnWindowsServer2008FailsToCommunicateWithExchange2007.aspx
• More to come...

 

Abstract:

Outlook Anywhere may not work properly on a Windows Server 2008 machine with Exchange 2007.  The DSAccess RPC proxy listens on ports 6001 and 6002 on the IPv6 stack, and listens on ports 6001, 6002, and 6004 on IPv4.  The missing listener on port 6004 causes connectivity to fail.
A workaround exists and is documented which gets this working, regardless of where the RPC proxy is installed (on the Exchange box, or otherwise.)

Details:

If your RPC proxy is on 2008, but not on the same box as Exchange 2007, remove the IPv6 binding to force the proxy to communicate with Exchange on IPv4.

Otherwise, modify your host file, as per: http://weblog.bassq.nl/?p=79

• Comment out the line “:::1 localhost”
• Add the following two lines:
  <IPv4 address> <hostname of the computer>
  <IPv4 address> <FQDN of the computer>

So, for my server, I have:
10.0.0.5 servername
10.0.0.5 servername.subdomain.domain.com

To confirm functionality:

Open telnet to localhost 6004

Sources:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2975122&SiteID=17

Abstract:

Exchange 2007 SP1 on Server 2008 can't back up using in-box tools.  Either use DPM, or a 3rd party tool ($$$), or hack NTBackup to run on 2008 Server.  A workaround/hack is provided that allows NTBackup to run on Server 2008 x64 with Exchange 2007 SP1.

Background:

The Exchange Team Blog has the following text:

Unlike previous versions of Windows, Windows Server 2008 does not include a backup utility that supports the Exchange ESE streaming backup APIs. The Windows 2008 backup application, Windows Server Backup, cannot be used to take backups of Exchange.

Exchange still includes the ESE streaming backup APIs, but the absence of an Exchange-aware backup application in Windows may come as a surprise to many. Another change we made that may also affect you is the removal of remote streaming backup support on Windows 2008.

This leaves you with two choices for taking Exchange-aware online backups when running Exchange 2007 SP1 on Windows 2008:

1. Move to a Volume Shadow Copy Service (VSS)-based backup application. You can use Microsoft System Center Data Protection Manager (DPM) 2007 or a third-party backup application that supports Exchange-aware VSS-based backups of Exchange 2007 SP1 on Windows Server 2008. Windows Server Backup in Windows 2008 is a VSS-based backup application, but it does not include a VSS requestor for Exchange, which is a necessary component in order to use VSS to take an Exchange-aware backup.
2. Use a Third-Party application that supports ESE streaming backups using a local backup agent on the Exchange server. Because the ESE streaming APIs remain in Exchange 2007, you can still use them to backup Exchange. But to do that, you must use a third-party backup application that runs a local agent on the Exchange server so that the streaming backup is made locally, and not remotely. You cannot take remote streaming backups of Exchange 2007 SP1 on Windows 2008 with or without a third-party product. Any streaming backups that are performed must be performed locally on the Exchange server.

Annoyances and anger aside, NTBackup (the old utility) can be made to run on Server 2008.  I found this: http://cs.thefoleyhouse.co.uk/blogs/karl/archive/2008/02/10/how-to-backup-exchange-2007-on-server-2008.aspx

To Install and use NTBackup on a Server 2008 Machine to Backup Exchange 2007 SP1:

1. Install NTBackup, as per http://www.petri.co.il/installing_windows_xp_ntbackup_on_windows_vista.htm
   1. Copy these files from a 2003 server (C:\Windows\System32\) to Server 2008 (C:\Program Files\NTBackup\):
      1. ntbackup.exe
      2. ntmsapi.dll
      3. vssapi.dll
2. Install the Removable Storage Manager from Server Manager.  (Features, Add Features, Removable Storage Manager.)
3. Copy Exchange DLLs to access Exchange (as per http://support.microsoft.com/kb/275876).  You need to copy esebcli2.dll from 2003 (C:\Program Files\Exchsrvr\Bin) to 2008 (C:\Program Files\NTBackup)
4. Run regedit and change the esebcli2 key from C:\Program Files\Micrsoft\Exchange Server\Bin\esebcli2.dll to C:\Program Files\NTBackup\esebcli2.dll

Discussion:

I would seem that several product groups at Microsoft have failed to do comprehensive use-case analyses of customer requirements.  This has happened with Vista (poor file copy performance, poor video card gaming performance, 4GB RAM BSOD with RTM, to name a few), and with Exchange 2007 (Exporting to PST in 2007 requires a 32-bit box, Server 2008 CAS does not work properly with single server deployments since DSAccess fails to listen on the IPv6 on port 6004, and Server 2008 does not provide an in-box backup solution for Exchange 2007.)

Summary:

The latest firmware/drivers (February 2008 beta) with 3Ware 9650SE (8LP) and Windows Server 2008 do not get along.  The system gets to the boot screen with the progress indicator, then locks up.

The problem is resolved with older firmware version 9.4.0.1 with bootloader 3.05.00.002, using the latest beta drivers (3wareDrv.sys is version 3.0.3.108).  I have Windows Server 2008 Enterprise running now.

Workarounds:

1. (March 20th 2008) Use the latest in-engineering firmware and drivers, as per http://www.3ware.com/KB/article.aspx?id=14928
   Firmware 3.08.00.022 or newer should be compatible, when using the driver 3.0.3.108.
2. (March 2nd 2008) Downgrade the firmware.  Download firmware/bootloader: http://www.3ware.com/KB/article.aspx?id=15103 (older firmware 9.4.0.1 with bootloader 3.05.00.002)
   Drivers: http://www.3ware.com/download/productseng/Driver/windrv_x64.zip (I'm using 3wareDrv.sys, version 3.0.3.108)

Known Issues:

• Back up your RAID containers before downgrading - I had some weird errors.  I ended up nuking my RAID containers, then recreating them.
• I'm running the latest management utilities - no problems so far.

Details:

January 13th 2008

I have a Tyan FT48 with a quad core Xeon E5335.  I moved my 3Ware 9650SE (8LP) over to it this afternoon to do a Windows Server 2008 RC (Hyper V) install and discovered that the drivers provided for 3Ware are non-functional with Server 2008.  The system hangs at start up, at the Server 2008 boot up screen.  The green progress indicator locks up.

This is also happening with a 9550SX on a different system.  But just to be safe: The system BIOS is the latest available, 2.00b, from Tyan.

The 3Ware 9.5.0 production driver, and the in-engineering drivers have been tested.
Both cards have been updated to the latest firmware.

http://www.3ware.com/KB/article.aspx?id=14928 is not very helpful.  Has anyone tried the 9650SE with Vista?  Any boot problems?

My server remains on Server 2003 R2 x64 until this issue is resolved.  I'm disappointed that 3Ware doesn't have functioning drivers, still.

January 15th 2008

My email to 3Ware was promptly replied to. They've sent me updated drivers, soon to be posted on their website under "In Engineering", I'm told.  Bypassing the signature requirement is still necessary at this point, via http://www.3ware.com/KB/article.aspx?id=14928 I'm told.

I will get these tested the coming weekend.

February 2nd 2008

I got the 2008 RTM bits off Connect today - and I'll try to find some time to get this tested this coming weekend, using the latest engineering drivers.

February 6th 2008

I'm not checking the 3ware KB daily at http://www.3ware.com/KB/article.aspx?id=14928 , but some more 'information' has been posted: 64-bit Vista/Windows 2008 support is not currently available.  A firmware upgrade for the 9550SX(U)/9590SE/9650SE is required.  This will be officially supported with the 9.5.1 code set (due out August 2008), but a beta version will be posted to the 'In Engineering Phase' section of the 3ware web site soon (February 2008).

Later this month?  This is surely a problem that became obvious in earlier builds.  Perhaps I will dig up some older beta builds of 2008 that I have, and test.  I'm curious as to why they've done so little.  I'm very disappointed.

February 6th 2008 (again)

3Ware says they found the current bug last week (week of January 28th.)  They say they should have updated code by the end of this week (week of February 4th) and testing will be done next week (week of February 11th).  I'm told the code will be posted to the "in-engineering" section the week after (week of February 18th).

Pretty disappointing.  But at least they respond to emails, with real answers, unlike Adaptec.

February 26th 2008

Tried this past weekend with latest beta firmware on the 9650SE with the latest driver.  No boot.  Argh.

March 2nd 2008

Success!  I booted from a Windows 98SE floppy, and flashed my 9650SE (8LP) to 9.4.0.1 with bootloader 3.05.00.002 from http://www.3ware.com/KB/article.aspx?id=15103 .
My RAID containers were a bit wonky in the BIOS after, so make sure you do a complete backup of your RAID containers first.  I ended up re-creating the containers - and everything seems functional, so far.  Using that firmware and bootloader, coupled with the latest beta driver (3wareDrv.sys is version 3.0.3.108) I'm able to get Windows Server 2008 x64 RTM booting.

Thank you to the person who left the comment!  I have contacted 3Ware support, and they have updated the KB article to reflect this workaround.

What is PowerGUI?

PowerGUI is an extensible graphical administrative console for managing systems based on Windows PowerShell. These include Windows OS (XP, 2003, Vista), Exchange 2007, Operations Manager 2007 and other new systems from Microsoft. The tool allows to use the rich capabilities of Windows PowerShell in a familiar and intuitive GUI console.

How much does it cost and is registration required?

PowerGUI is a freeware product thanks to the support we are getting from Quest Software. You can download the product and access all information on this site absolutely for free and without any registration or login. You will have to register only if you want to post information to the discussion forums or library, or subscribe to notifications by email (RSS subscription does not require registration.)

What are the system requirements?

The main system requirement is Windows PowerShell (which in its turn requires .net framework 2.0). If you don't have this installed on your computer PowerGUI setup will detect that and open a web page from which the system can be downloaded. In terms of operating systems we support Windows XP, 2003, Vista, and Longhorn; both 32- and 64-bit. Particular snapins may add their specific system requirements. For example the Exchange 2007 snapin we ship today naturally requires Exchange 2007 or its administrative tools.

What can I do with PowerGUI?

Pretty much anything that the underlying system permits. You can browse through the system, filter/sort what you get, select the columns, perform actions on selected objects, change their properties, export data to clipboard, Excel, xml, or just html reports, and much more. And if you don't believe this is all being done by Windows PowerShell just switch to another tab and you'll see the PowerShell code behind what you've been doing.

Download: http://powergui.org/downloads.jspa

What will support Windows Server 2008 at RTM?

• .NET Framework 2.0 (installed)
• .NET Framework 3.0 SP1 ( part of Application Server role )
• .NET Framework 3.5
• Dynamics CRM 4.0
• Exchange Server 2007 SP1
• Forefront Security Server 1.0
• MOSS SP1 ( installation notes for Windows Server 2008)  http://support.microsoft.com/kb/936988
• SQL Server 2005 SP2
• System Center Data Protection Manager 2007
• System Center Configuration Manager 2007 (Formerly SMS)
• System Center Operations Manager 2007
• Windows Sharepoint Services 3.0 SP1 ( installation notes for Windows Server 2008 ) http://support.microsoft.com/kb/936988
• Visual Studio 2008
• WSUS 3.0 SP1

What are we planning to support in the first half of 2008?

• We will ship the Hyper-V technology 180days after RTM
• Dynamics AX 2009
• MOM SP1
• SCCM 2007SP1
• System Center Essentials 2001
• Forefront Client Security SP1

What are we planning to support in the second half of 2008?

• Application Virtualization 4.5
• Commerce Server 2007 SP2
• HIS 2006 SP1
• MOM 2005 SP1
• SQL Server 2008
• System Center Essentials 2001
• Windows System Center VMM 2.0
• Windows Essential Business Server
• Windows Home Server vNext
• Windows HPC Server 2008

So what will not be supported?

• SMS 2003
• System Center Reporting Manager
• Internet Security and Acceleration Server 2006 and earlier

Source:

http://blogs.msdn.com/neilhut/archive/2008/02/07/microsoft-server-and-tools-support-for-windows-server-2008.aspx

Windows Media Services

To obtain the new features and tools available in Windows Media Services for Windows Server 2008, such as the built-in WMS Cache/Proxy plug-in, you must obtain and run the appropriate Streaming Media Services role installer file on the updated platform.

• Windows Media Services and the rest of the Streaming Media Services role in Server Manager, on “full” installations of Standard and Enterprise editions of Windows Server 2008
• The Streaming Media Services Server Core role, on “Server Core” installations of Standard and Enterprise editions of Windows Server 2008
• The Windows Media Services snap-in for Microsoft Management Console (MMC) on a computer that is running the Business, Enterprise, or Ultimate edition of the Microsoft Windows Vista operating system

http://www.microsoft.com/downloads/details.aspx?familyid=9ccf6312-723b-4577-be58-7caab2e1c5b7&displaylang=en&tm

Problem:

"Windows could not determine if this computer contains a valid system volume"

I had booted Windows Server 2008 RC, loaded my RAID (3Ware 9650) drivers from USB stick, and created a partition and formatted it.  I go to install, and Windows stops dead in its tracks.

Solution:

Leave the stick plugged in, reboot the system, and go into the BIOS and REMOVE the stick from the boot order entirely.  Ensure the RAID array is 1st in the list, and give it a try again.

See also:

After I discovered this, I also read these websites, which I thought might be useful...
http://www.nforcershq.com/forum/vista-and-nforce4-sataraid-an-installation-guide-vt66299.html
http://www.dashken.net/index.php?/archives/204-Windows-could-not-determine-if-this-computer-contains-a-valid-system-volume.html#extended
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2201257&SiteID=17

I started the install of Vista SP1 Beta at 9:40pm this evening on my ThinkPad T60p. It finished installing at 10:22pm.  My laptop HDD was quite warm by the end of the install; it had been cranking along for quite some time.

I also grabbed the September QFE testing packages: Windows6.0-KB941649, Windows6.0-KB941651, and Windows6.0-KB941229.

My thoughts?

• I can burn a recovery CD/DVD now... yay?
• All the IBM OEM utilities appear to continue to function.  I'm running Windows Ultimate x86 (July, 2007) from the Lenovo pre-install.  I had removed a bunch of the junk in the preload using the Base Software Administrator.
• Outlook 2007, Remote Desktop client, MSN Live Messenger, Skype all seem to work.  XviD video files are playing fine, VLC works fine.
• My laptop recovers from hibernation faster - there's less HDD cranking... this is PROBABLY a result of the correction of the ReadyBoost bug that caused the entire cache to be flushed after a resume from hibernation.
• Browsing a network share of pictures, and video files loaded faster.  Thumbnails are being cached/read more intelligently.
• Moving files on the local computer is much, much faster.  It used to sit and crank while it "counted" files and "thought" about the process.
• SSTP!  I'm going to set this up in the next few days, time permitting...

I finished downloading the RC0 bits for x86 and x64 a few minutes ago.  I'll have to burn the stuff to disk sometime tomorrow before I can play.

• Hypervisor in x64 bits - I'm going to put this on a Core 2 6300 machine with 3 GB of RAM sometime this coming weekend - and see how it goes. =)