- Dec 22, 2009 by the_angry_angel
- Geek, Unix-like, Windows and Personal
If you've noticed that the next Ubuntu Server version (10.4, Lucid Lynx) has the Hyper-V kernel modules packaged, alebit in drivers/staging, I'd suggest not dist-upgrade'ing even your development servers for the moment. The reason is simply that you need to devote time to ensuring that the kernel modules will continue to work with each kernel version - right now you can't seem to rely on the modules actually loading successfully from the corresponding /lib/modules/2.6.*/kernel/drivers/staging/hv directory. Which isn't a problem, provided that you have the time to deal with it.
The long and short of it is that if you're currently looking to use any flavour of Linux under Hyper-V the "old" rules still apply;
- Use the legacy network adapter
- Set static MAC addresses under the VM settings (unless you want to faff with udev)
- and learn to live with the performance penalty
- Nov 30, 2009 by the_angry_angel
- Geek, Windows and Work
If you've got a Windows Server 2008 R2 box, running Nehalem based hardware you might find it handy to bookmark KB975530, which details a hotfix and workaround for CLOCK_WATCHDOG_TIMEOUT STOP errors you might receive with this configuration.
The Virtual PC Guy (Ben Armstrong) has a few more details on the problem.
- Nov 24, 2009 by the_angry_angel
- Geek, Windows, Work and Mindless Hatred
If you've got an application that sends messages via your Exchange 2010 server, using SMTP, you might've noticed that things have slowed down a bit. The reason for this is because the Exchange 2010 receive connectors have a "MaxAcknowledgementDelay" setting, that will inform you if the delivery is successful, within a certain time frame. If the timelimit is hit, it then acks the submission.
To disable this you can set your receive connector not to use this feature: Set-ReceiveConnector "Connector Name" -MaxAcknowledgementDelay 0
Further details are available on technet.
- Nov 16, 2009 by the_angry_angel
- Geek, Windows and Work
If you're having fun with a pre-2007 version of Outlook, or any non-Microsoft product trying to talk MAPI to an Exchange 2010 server you might be interested in knowing that the defaults have now changed in the new version, and it expects traffic to be encrypted. This caught us out today as we'd only tested Outlook 2007 before rolling one of our boxes over to 2010 over the weekend.
Two options;
- Disable the encryption requirement, although this isn't recommended
Set-RpcClientAccess –identity SERVERNAME –EncryptionRequired $false - Enable encryption for the MAPI connection (for Outlook 2003 this is under the More Settings, Security tab)
- Nov 05, 2009 by the_angry_angel
- Geek, Windows and Personal
"Engineers are really good at labeling and branding things," said his sarcasm. "If we had named Kentucky Fried Chicken, it would have been Hot Dead Birds." - Vint Cerf
