Windows Server Virtualization (Viridian) Announcement (sad)
Oh come on now! (Windows Server Division Blog)
They already are releasing the product late (the BETA will be released in conjunction with the RTM of Longhorn), and now they are removing some of the most highly-touted features that actually were going to set the product apart from the leader? Some of the ground-breaking features being axed:
- Hot-add of resources (memory, processor, storage and networking)
- Live migration (this is a killer app currently being offered by VMWare in their VMotion technology)
- Support limit of 16 cores (4 processor, quad core) though I don’t see this as a big issue. I think you’d need some pretty hefty hardware for your host to even get close to that many cores being useful. My vision probably isn’t as broad as the developers though – I’m sure we’ll see Quad-proc, Octo-Core boxes on the desktop a few years out.
Stings, doesn’t it? Time to start looking at VMWare…
Two DRAC III / ERA Issues and solutions
While working with some DRACs (Dell Remote Access Controller) today I was able to figure out a few issues that have been giving me trouble for quite some time:
DRAC / ERA internal address registered in DNS on Domain Controller
DRACs installed on Domain Controllers were registering their RAC PPP connection in DNS with the hostname of the computer the DRAC is installed in. This creates a problem for clients looking in DNS for a domain controller - they get an address that is either non-routable (192.168.234.235) or doesn’t respond at all. For most systems, you can simply uncheck “Register this connection’s address in DNS” in the DNS tab under Advanced options for the connection. Windows Server 2003 SP1 installed as a domain controller however ignores this setting and continues to register the address in DNS. There is a hotfix (included in Windows Server 2003 Service Pack 2) that addresses this issue, but you have to call Microsoft to get it (I think I’ll just install the service pack).
http://support.microsoft.com/kb/832478
Thanks to Neal’s Admin Notes:
Dual NIC Problems with NetLogon and DNS
DRAC / ERA Console Redirection Fails with Warning – Reintstall PPP Connection
The other issue was that the graphical console redirection on some of my ERA (Embedded Remote Access) devices (basically an embedded DRAC III) was not working. The console window would launch, but I would get no video and the message: “Warning: Remote Console is not available” The first step is to wait a few minutes (sometimes it takes awhile to initialize). Check. If it’s still a no-go, check the RAC services (Remote Access Connection Service and RAC VNC Service) and restart them if necessary. Check. Still no-go. Then I found this gem (note command is run from C:\Program Files\Dell\SysMgt\RAC in default Windows installs):
Root Cause:Â
During RAC3 installation, the modem is disabled and enabled for the default name of the modem to be changed to RAC PPP connection Using RACPORT after modem driver installation. The OS fails to recognize the modem name change and the installer code is not able to find modem device to establish the connection.
Solution:Â
From the command prompt run the command installppp createRacConnection. The following message will be displayed confirming that the installation was successful:Â
Installing PPP connection
Successfully Installed the RAC connection
Here: http://support.dell.com/support/edocs/stor-sys/spv745N/en/RN/RelNotes.htm (it’s an obscure Release Notes for a Dell NAS device). The instructions fixed the issue immediately – no reboot required. Kinda bizarre, but as long as it’s working, right?