Share iT…

I am curious what hardware you all use for lab / test environment(s)?

Maybe it is nice if you can tell a bit where you use it for?
Leave it in the comments

On a Windows 2008 R2 Hyper-V configuration with 2 network adapters I experienced the following problem: I installed a Windows 2008 R2 guest this was no problem, but when I try to do windows updates I got an “Windows could not search for new updates, An error occurred while checking for new updates for your computer. Error(s) found: Code 80072EE2” error message.

Everthing else looks fine, dns resolving works fine, network browsing looks good, I could access internet pages even the windows update page, but trying to update gives this particulary error.
Tried the same on a windows 2003 guest and everything looks fine. Installed another Windows 2008 R2 server same problem occurres.

Solution: After some more trouble shooting I found that when I start the windows update I lost network connection on that particulary network adapter, even on all other VM’s using that adapter and on the Host. Now I was connected with the other adapter so I didn’t see this behaviour in first place. So I bound the other network adapter to one of the Windows 2008 R2 guests and I could windows update with no error.

Because I would like to know what was causing this problem I found after some more troubleshooting and testing that the problem was caused by the Large send Offload setting enabled on the network adapter. After disabling this setting everything works fine.

The network adapter was causing the trouble was a D-Link DGE-528T Gigabit Ethernet Adapter.

When you try to to start a Hyper-V virtual machine on a Windows 2008 R2 server, you receive the following error:

An error occurred while attempting to start the selected virtual machine(s).

‘ServerName’ could not create or access saved state file E:\Hyper-V\ServerName\Virtual Machine\”Virtual Machine GUID”.vsv.
(Virtual machine ID “Virtual Machine GUID”)

Solution: I have no clue what caused this issue but the solution is add list permissions to the “Authenticated Users” group on the root drive where the virtual machines are placed (in this case E:). You only have to add list rights for “this folder only”.
So go to the security tab and choose advanced permissions, add Authenticated users and choose at Apply to: “This folder only”, check List permission and be sure you don’t check the replace all child object permissions with inheritable permissions from this object, otherwise you may have to restore the rights on all virtual machines permissions.

There are 3 levels to control the message size limits for sending and receiving emails through a Exchange 2007 or 2010 mail server. Mail transport is controlled by the hub transport role so settings are made on the hub transport role.

Global settings: In Exchange Management Console, on Organization level, Hub Transport, Global Settings tab, select Transport settings properties you can set the Maximum receive size (KB) and Maximum send size (KB) at Transport limits for the whole Organization.

Connector settings, Receive connector: In Exchange Management Console, on Server Configuration level, Hub Transport, select the server and receive connector you want to set the Maximum message size (KB) for. You can set different values for all servers and receive connectors, so be sure you change the settings for the right Hub Transport server and the right receive connector.

Connector settings, Send connector: In Exchange Management Console, on Organization level, Hub Transport, Send Connector tab, you can set the Maximum message size (KB) for your Send connector(s). The setting is organization wide so for all servers if you have multiple send connectors you can make differences for the specific send connectors.

Last possibility is to set it on a User Mailbox: In Exchange Management Console, on Recipient Configuration level, Mailbox, select a User you want to set the limit for, properties, on the tab Mail Flow Settings select Message size restrictions