Microsoft Hyper-V Server 2008 R2 Memory Supported

Memory Support for more than 32GB for the Host OS previously required Windows Server 2008 Enterprise or Datacenter Editions. Even though Windows Server 2008 R2 Standard only supports 32GB, the free Microsoft Hyper-V Server 2008 R2 supports greater than 32GB. Very Cool!

Also noteworthy, similar to the Enterprise and Datacenter Editions, the free Microsoft Hyper-V Server 2008 R2 includes: Host Clustering, Live Migration and Support for greater than 4 Physical Processors (Host OS).

Check out the table on Microsoft's Hyper-V Server page.

Volvo XC90 versus Chevy 2500 HD - Volvo Saved My Life

After reading this account and looking at the photos, how fast do you think the truck was going? Let me know by leaving a comment. I know since both airbags in the truck deployed that he was going at least 25 MPH. After looking at the photos, an auto body estimator guessed the truck had to be going between 40 to 50 MPH maybe as high as 60. Even though the damage looks minor and the XC90 was driveable after the accident, the XC90 has been totalled with repairs right around $13,000.

This was my Tuesday, September 22nd at 4:20 PM, I was headed to a dinner with friends (fellow Small Business Specialists). I was on I-280 southbound in the slow lane. Totally normal for rush hour the traffic ahead slowed down quickly. I had room to slowed down and stop leaving enough room in front of me so I could see road between my car and the Honda Civic in front of me.

I then looked in my rear-view mirror and saw a white truck (Chevy 2500 HD) behind me approaching too fast to stop before hitting my vehicle. Since I was at a stop and I knew I was going to be hit, I did all I could do which was push the brake pedal down as hard as I could.

As the truck impacted my vehicle I felt the back end of the vehicle go up and I saw no sky. I now knew I was going to be pushed into the Honda Civic in front of me, so I turned the steering wheel to the left to try to avoid hitting the Honda Civic in front of me. But, the white truck kept pushing me into the left-side of the rear of the Honda Civic and pushed the Honda Civic into the car in front of it.

After we all stopped moving, the cars in front of me pulled to the side of the freeway. I tried pulling over to the side of the road too but my car would not move. All of the drivers involved got out of their cars and checked to make sure we were all alright. The general consensus was okay but shaken. The Chevy driver said, "I didn't even see you." We called some tow trucks and the Highway Patrol. After seeing how well the Volvo survived the accident the Honda Civic driver said her next vehicle would be a Volvo.

After taking some pictures with my iPhone (I am a PC but, sorry Microsoft, I use an iPhone) I saw my car should be drivable but was attached to the truck, so I got back into my vehicle, started it, put it in low gear and broke away from the truck and pulled to the side of the freeway.

I then took some more pictures and finally gave a ride home to the driver of the Honda Civic. What a day!

For the first day or so, I felt fine. Since then, I have noticed some pain, weakness and numbness. Rhonda, my wife, says I am ‘off’ and I don’t look ‘right’. I guess this is to be expected, after all the damage to the XC90 exceeded $12,800!

I know my injuries would be far greater if my car was not equipped with Volvo’s WHIPS. If I was not in my Volvo XC90 then, well let’s just say Volvo Saved My Life! Safe to say my next car will be a Volvo!


Here are some pictures:

My Tires were straight when I was first hit; but, I tried to avoid being pushed into the Civic in front of me so I turned left.


White Truck versus Volvo Photo #1


White Truck versus Volvo Photo #2


Front of White Truck that hit my Volvo, how fast was it going?


Another shot of the front of the White Truck.


Side of White Truck.


Both of the White Truck's Airbags deployed


Rear of my Volvo after breaking free of the White Truck


Door won't close all the way.


How did the hood from front of my Volvo hit so low on the rear of the Honda Civic?


Rear of Honda Civic in front of my Volvo.

When will I get my Windows 7 RTM bits?

Per the Windows 7 Team Blog, you can get the Windows 7 Release english language bits:

• Approximately 2 Days after official RTM if you are an OEM


• Shortly after RTM by downloading an evaulation of Windows 7 Professional via http://www.microsoft.com/springboard


• August 6th for ISVs & IHVs via Microsoft Connect or MSDN


• August 6th for TechNet Subscribers via TechNet


• August 7th for Volume License Customers with Software Assurance via Volume License Service Center


• August 16th for Gold & Certified Partners via Microsoft Partner Network Portal


• August 23rd for Microsoft Action Pack Subscribers via Microsoft Partner Network Portal


• September 1st via Volume Licensing


• October 22nd via Retail (Full Package Product or on a new PC

This information was culled from http://windowsteamblog.com/blogs/windows7/archive/2009/07/21/when-will-you-get-windows-7-rtm.aspx.

Microsoft IT Environment Health Scanner

This diagnostic tool is designed for administrators of small or medium-sized networks (recommended up to 20 servers and up to 500 client computers) who want to assess the overall health of their network infrastructure. The tool identifies common problems that can prevent your network environment from functioning properly as well as problems that can interfere with infrastructure upgrades, deployments, and migration.

When run from a computer with the proper network access, the tool takes a few minutes to scan your IT environment, perform more than 100 separate checks, and collect and analyze information about the following:

• Configuration of sites and subnets in Active Directory


• Replication of Active Directory, the file system, and SYSVOL shared folders


• Name resolution by the Domain Name System (DNS)


• Configuration of the network adapters of all domain controllers, DNS servers, and e-mail servers running Microsoft Exchange Server


• Health of the domain controllers


• Configuration of the Network Time Protocol (NTP) for all domain controllers

If a problem is found, the tool describes the problem, indicates the severity, and links you to guidance at the Microsoft Web site (such as a Knowledge Base article) to help you resolve the problem. You can save or print a report for later review. The tool does not change anything on your computer or your network.

Here's a link to download the tool and for more information. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=dd7a00df-1a5b-4fb6-a8a6-657a7968bd11

Uninstalling Exchange 2007 Anti-spam system

If from some reason, you would like to uninstall the Anti-Spam system from the Hub Transport role, follow the next steps:

1. Close the EMC (Exchange Management Console).
2. Open the PowerShell and navigate using the following path: "Program Files\Microsoft\Exchange Server\Scripts".
3. Run the "uninstall-AntispamAgents.ps1" script as shown in window (with ./ before the script name) below: Note: You will be prompt to disable and then uninstall each agent of the Anti-spam system like the Connection filtering, content filter, Sender filtering etc.
4. Restart the "Microsoft Exchange Transport" service in order to apply configuration changes.
5. Open the Exchange Management Console, and on the Organization configuration list, select Hub Transport. You will see that the "Anti-Spam" tab has been removed from the Hub Transport properties.

This tip was provided by Jason Metcalfe from Platte River Networks after the Denver SBS 2008 Build Day.

XPPro connecting to Terminal Server 2008 with NLA required

Do your Windows Vista machines connect to Terminal Server 2008 but your Windows XP machines won't?

First, Windows XP needs the RDC version 6.1 to connect to Terminal Server 2008, so you need to have Service Pack 3 installed.

Second, if Terminal Server 2008 requires NLA (Network Layer Authentication) then you need “CredSSP” to be turned on on your machine.

You need to modify the registry to turn on CredSSP. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully.

Click Start, click Run, type regedit, and then press ENTER.
1. In the navigation pane, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
2. In the details pane, right-click Security Packages, and then click Modify.
3. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
4. In the navigation pane, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
5. In the details pane, right-click SecurityProviders, and then click Modify.
6. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.
7. Exit Registry Editor.
8. Restart the computer.

This information was originally found on http://support.microsoft.com/kb/951608

Microsoft Exchange Active Directory Topology Service Fails to Start after Windows Server 2008 Service Pack 2 is Installed

It appears that Windows Server 2008 Service Pack 2 add a DependOnService registry key with a value of Netlogin (instead of Netlogon), this causes Microsoft Exchange 2007 to not start when a reboot occurs, nor will Exchange start if you try to manually as you get an Error 1075 “The dependency service does not exist or has been marked for deletion.”

To fix this issue, change the value of the DependOnService registry key to Netlogon for the MSExchangeADTopology Service and Reboot the Server. After the reboot, check your Services to make sure all of Exchange has properly started.

This key is found at Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeADTopology. Remember using Regedit can be dangerous if you do not know what you are doing, so be careful!

Here is what the MSExchangeADTopology Service looked like before Windows Server 2008 Service Pack 2 was installed.



Here is what the MSExchangeADTopology Service looked like after Windows Server 2008 Service Pack 2 was installed.



Here is what the MSExchangeADTopology Service looked like after I edited the Registry Key.



Here is the order of recently installed Updates.



This error occurred on two Windows Small Business Server 2008 machines. I would not be surprised if we saw this issue on Windows Server 2008 machines running Exchange 2007 as well.