Here it comes powerfull and with new so desperately awaited features… Hyper-V 2.0…
http://www.virtualization.info/2009/01/microsoft-releases-hyper-v-20-and.html
http://edge.technet.com/Media/Demo-Hyper-V-Server-and-Live-Migration/
http://www.microsoft.com/virtualization/downloads.mspx
Take a look / give it a try!
PS. take a look at new redesigned Microsoft Virtualization site… Where you can find all information about all MS virtualization products …:
This weekend I was playing crawler… I know almost all internet sites describing the problems around 0X8004010F – damn error regarding Offline address book distribution…
But nowhere I have encountered the problem describing this error code in combination with Windows Server 2008 and Exchange 2007 SP1 with rollup 5.
Well… As I figured out it apparently does not work – if you want OAB to be distributed by Web-based distribution…
You get this error in your Outlook 2007 SP1 clients (on Windows XP and on Windows Vista)
As I can see there is somekind of permission problem becoues OAB virtual directory points to:
C:Program FilesMicrosoftExchange ServerClientAccessOAB
This directory has NO NTFS permissions for Auhtenticated users… but in IIS there is on this folder a parameter: Pass-through authentication – but as I know it can not work becouse your credentials are not covered in NTFS permissions of that folder.
But it does not work even if you give NTFS permissions to authenticated users… (you are still prompted for username and password in Outlook…)
Maybe I am missing something but weekend is almost over and my users need to use Exchange and RPC over HTTP(s) feature in their Outlooks tomorow… What I did is that I disabled Web-based distribution of Offline address book and I left only Public folder distribution. It took a couple of minutes for autodiscover.xml to update and Outlooks to get new parameters about Offline address book distribution.
Everything works correctly now…
Comments / suggestions appriaciated…
PS.
Hey all you Exchangegurus!
I think you will find this link useful: https://www.testexchangeconnectivity.com/
Yes! I managed to make it work…
Exchange transport won’t start if you are installing Exchange 2007 SP1 on Windows server 2008 with Active directory on it even if you UNCHECK IPv6 on your network card properties…
The installation won’t complete… 😦
You need to do it this way:
1. Uncheck Internet protocol version 6 (TCP/IPv6) in your network card properties
2. Delete localhost value for ipv6 in file called HOSTS in C:WindowsSystem32driversetc
::1 localhost
or comment it by using # at the start of line
3. Create/add a 32 bit DWORD with name DisabledComponents and value 0xFFFFFFFF to:
HKLMSYSTEMCurrentControlSetServicesTcpip6Parameters
My setup was Windows server 2008 standard as Hyper-V platform, inside Windows server 2008 standard with Active directory in functional level 2008 – everything updated and clean.
When I changed this three parameters exchange setup completed sucessfuly and now my testing Exchange 2007 is working! Wiiiii!!! 🙂
I would like to share with you fantastic experince of using Terminal services gateway – a new feature of Windows server 2008 terminal services.
It does allow user to use gateway that listens on port 443 (HTTPS / SSL) and then “route” remote desktop protocol to workstations inside network and FOR ME GREAT FEATURE even on other servers on the internet (so now you can lock RDP client to your IP address (where you have your TS Gateway server) and you will be able to access your servers through your TS Gateway and in this way even more secure your remote access).
I hope you will enjoy this fantastic feature!
To understand better I have some pictures to show…
(here you can download Visio files if you need to reedit something)
WAN to LAN example …
 |
| From Windows server 2008 – TS Gateway examples |
WAN to LAN & WAN example …
 |
| From Windows server 2008 – TS Gateway examples |
For testing and presentation puropuses I have installed inside my full Windows server 2008 64 BIT installation with Hyper-V another standalone Microsoft Hyper-V Server 2008 – everything works – you can even manage it using Hyper-V manager from other server but you can not (obviously! :)) run virtual machines. You get an error saying unable to create partition. You should be a wirdo to even think about souch stuff but I had a chance and I just could not resist pressing the START button. 🙂 So you know now… Hyper-V inside Hyper-V does not work! 🙂
First of all I would like to thank Dusan Kosaric to keep my moral up during this operation and for his help when I was trying to restore my virtual machine …
I was very sad when I was not able to make it work… You know something happened to my Hyper-V server and needed to reinstall it. I made a clean installation and after it was set up I tried to import / run existing virtual machine back in… But then I read the articles about import and export of virtual machines… And I already saw myself reinstalling my virtual machine again. 😦 But NO! You can put it back to life folowing this steps:
Let’s assume that:
I have a VM folder located on D: so D:VM and in it my virtual machine called machine01 with vhd called machine01.vhd (I had also a snapshot but it was lost during this procedure becouse I did not copied it… So I did not tested if it also restore snapshots… I only wanted my machine back to work…).
When you establish Hyper-V system again rename your current machine folder to let say machine01old – after that create a new virtual machine with the same hardware configuration as it was the machine before (and also with same location so d:vmmachine01). When machine is created use Export to export it (not only configuration files but everything). It will create let say d:Export and in this folder there will be three other folders. Move or copy your original VHD to the location in ExportVirtual harddisk and you are ready… Your machine will start without problems.
As I said this test was made a hour ago and I lost my snapshots but I did not care to restore them I just wanted my virtual machine to get back to life…
So as a conclusion… Hyper-V can be restored even if you are a bad administrator 🙂 like I was in this case. 🙂
Finaly we have a true solution for FreeBSD hanging when you want to reboot or stop it in Hyper-V server…
Today I recieved a comment on my article FreeBSD in Hyper-V – WORKS!!!. You can now patch FreeBSD kernel to shut down correctly…
Check this blog too: http://shell.peach.ne.jp/aoyama/
Aoyama Says:
October 7th, 2008 at 11:02 edit
I made an easy patch for the kernel.
As a result, a virtual machine comes never to stop.
I expect someone to make the patch by a smarter method.
My patch can be downloaded from the following blogs.
http://shell.peach.ne.jp/aoyama/archives/40
This patched kernel confirmed the operation with
Server 2008 Enterprise w/Hyper-V and Hyper-V Server.
http://picasaweb.google.com/manojlovicluka/HyperVServer2008BasicConfiguration
In this photo-slide-show you can see some basic configuration of Hyper-V server. In the last picture there is shown a remote connection with Hyper-V management tool from one of my servers to Hyper-V server.
First of all you will see that Hyper-V server is very similar to Core version of Windows server 2008. To help you with basic configuration Hyper-V server does include somekind of “menu” to do some basic tasks.
🙂 First problem that I see here is… What happens if I close this menu? How I get to it once again? Well… I did not find the answer on the internet as Hyper-V server is just to “fresh”. But I searched the registry and I found where this menu is located:
c:WindowsSystem32hvconfig.cmd
So if you accidentally close the menu you can find and run it from this location.
Next is… Microsoft Hyper-V Server 2008 needs to be managed from other machine with Hyper-V tools installed. But out-of-the-box Hyper-V Server has firewall enabled. Now you have two options. Or to disable firewall or to add ports to remotely manage Hyper-V service using Hyper-V tools (you can manage Hyper-V server from another Windows server 2008 with Hyper-V tools (even on 32-bit edition) or from Windows Vista workstation with Hyper-V tools installed).
To open firwall to allow remote management of HyperV service type folowing line in your Hyper-V Server command prompt:
netsh firewall set portopening ALL 137 “Hyper-V Management”
This allows remote connections from other machines using Hyper-V Manager.
I also like to be able to copy ISO images to Hyper-V server and for this reason you need to open another two ports or enable sharing. I did it in this way:
netsh firewall set portopening ALL 139 “Sharing 01”
netsh firewall set portopening ALL 445 “Sharing 02”
This two ports allow SMB over TCP you can read more on this on:
Here you can get a step-by-step install of Hyper-V server 2008
http://picasaweb.google.com/manojlovicluka/InstallingMicrosoftHyperVServer2008
In this first post we only install our Hyper-V server 2008 in next post you can see some basic configuration you should do after installation.
In this article I assume that you have already enabled virtualization on your hardware. I used HP ML 380 as a server for this demo and in my previous Hyper-V articles you can see how hardware virtualization (do not forget to completly TURN FF your server after enabling virtualization – reboot is not enough!!!) is enabled on this kind of server.
I believe in Hyper-V! 🙂
I welcome you to join virtualisation experience with this fantastic product… At the moment of writing I am testing Microsoft Hyper-V server 2008 and it works great… In next days I will post some screenshots on how to install, configure and manage Microsoft Hyper-V server 2008…
http://www.microsoft.com/servers/hyper-v-server/default.mspx
Luka Manojlovic 