Skip to main content

Windows Server Division: RTM Viridian and Longhorn on schedule



It is good to see the Windows Server Division coming out and saying it all. Especially when press starts publishing inaccurate news.

Yesterday, IT Pro magazine (UK) posted an article about Longhorn and Windows Server virtualization (codename Viridian), and it contained errors about the timing of Windows Server virtualization and Longhorn. In this case, the reporter wasn't aware of the product milestones we announced at last year's WinHEC, and once shown what we announced last year, he admitted the error of his ways. As you'll recall, at WinHEC (May 2006) we announced the planned RTM timeframe for Windows Server virtualization as "within 180 days of the release to manufacturing of Windows Server Longhorn." The transcript from Bob Muglia's MMS 2007 keynote yesterday will be posted, and he reiterated the RTM timing of Longhorn (2nd half 2007) and Windows Server virtualization.


Check it out.
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more