But I have heard that Hyper-V is one of the best things about 2008 R2 from a few other ppl from are currently running it as their main OS. I asked them and they said that they are not members of this forum/site and in fact have never heard of it. All of them have jobs in the IT sector.
The hypervisor in Hyper-V by design is very secure. Hyper-V is not monolithic which means the hardware device drivers do not directly communicate with the guest VMs. All the requests instead are made on behalf of a virtual bus (VMBus) that goes out to the physical machine and makes the request on behalf. This process makes Hyper-V very secure but you pay a price for 3D performance. This is the one of the main reasons why running Hyper-V as a workstation is not a great idea. This overhead causes a performance degradation of your UI. Things are less snappier, FPS in games decrease, etc.
This problem is even documented by Microsoft themselves. http://support.microsoft.com/kb/961661
In your post you also state that Hyper-V has known incompatibility issues with the ITB and 3D graphics rendering. Can you provide documentation (hyperlinks) that back this up (especially the 1st comment)? Not saying I dont believe you, I just would like to read up on it. Tried searching Google but nothing specific there.
Check out user b0w_bender: http://forums.lenovo.com/t5/T400-T500-a ... d-p/235107
This forum documents an issue with Turbo Boost directly with Hyper-V. http://blogs.msdn.com/b/project_program ... reens.aspx
The forum user suggests disabling virtualization in your BIOS and then installing SP1, then turning Turbo Boost + virtualization back on once SP1 is installed. But I think you already have SP1 installed so it doesn't seem that this fixes the problem?!
What is the difference between the Hyper-V Role and the Hyper-V Feature? seems kinda redundant to me................
I think maybe you mean Hyper-V Server vs. Hyper-V role. Simply Windows Server 2008 R2 Hyper-V Server contains JUST hyper-V and thats it. Very small footprint...used for virtualization purposes only. Hyper-V role is included in the suite of additional 2008 r2 roles/features (DHCP,DNS, Active Directory, FTP, DirectAccess,etc). Hyper-V Server cannot be used as a workstation so its irrelevant to you. If you are interested in Hyper-V I would suggest looking into putting it on a portable USB drive. It's a bit tedious but it can be done. Requires some technical knowledge though, so KNOW WHAT YOU'RE DOING!http://archive.msdn.microsoft.com/BootHVSR2FromUSB
Would also like to get your take on Windows 8 Server/ Windows Server 8. has microsoft officially named it yet? how similiar/different will it be to Win8? I've tried the Win8 developers preview in a VM, it's ok but needs alot of impovement before MS unleashes it upon the masses. I have heard that the Server version of 8 will include Hyper-V.
I was able to snag a copy of the windows 8 server developer preview and I tried it out in a dual boot on my laptop, but I was not impressed at all with it. It is not really a fair assessment right now but thats because the current build is very buggy, so I am going to hold off on my initial "true" reponse until ATLEAST it hits beta...even then my real judgement won't come until the RTM of Windows 8 Server.
On the contrary, Hyper-V will be available on the home editions of Windows 8 (though not sure if just professional + ultimate editions) making the first time Hyper-V is available on client and server.
And the last thing i'd like to mention is that I feel i shouldnt have to do all this tinkering and modding etc just to get features like Bluetooth working correctly, whereas in 7 they work out of the box without all the extra effort. On the other hand doing such things are part of the joy of being a true hacker (NOT cracker!), they love to fix stuff. Thats part of the reason why i've been test-drive Linux and FreeBSD. Do you have any experience with either?
No experience with FreeBSD, but I hear its very secure.
I've played around on Linux Mint, Ubuntu, Backtrack 5, OpenSUSE. Linux dominates the market share of web servers and the community is growing...i wouldn't be surprised if they own a 10% market share in desktops by 2016. They used to dominate the netbook industry and some OEMs use a variant of the Linux kernel for their "Instant-on" technology which ultimately is based on Splashtop.
As Mark Russinovich has pointed out several times before the kernel differences of NT between Windows Server and its desktop counterpart are minimal. The difference you see is not the kernel itself, but rather the features that Microsoft restricts. For example Windows Server 2008 R2 standard is limited to only 50 RRAS connections while Windows Server 2008 R2 Enterprise is unlimited. The function of both behaves precisely the same. Both Windows 7 and Windows Server 2008 R2 are essentially derived from the MinWin kernel. http://www.zdnet.com/blog/microsoft/mic ... r-all/1690
This idea of compartmentalizing all your functions was introduced in Windows Server 2008. As a matter of fact you might be surprised to hear that Windows 7 is basically an evolution of Windows Server 2008, which in turn is an evolution of the previous Vista kernel. http://www.tgdaily.com/software-feature ... osoft-says
The revamped Vista kernel that you see today is what people like to call "Windows 7". Yes, Windows 7 is pretty much Vista 2.0. It is not a completely new kernel. If you notice, Windows Server 2008 R2 is a "minor" release which lead me to believe that we had to wait until Windows 8 to see a completely new kernel... and chances are we probably will...but I think it will most likely be an evolution of Windows 7/R2 kernel due to the hardware requirements Microsoft is pushing out due to its support for ARM processors now.
The purpose of running a Server operating system all boils down to practicality. Some convincing reasons to use Windows Server as a desktop include:
1. Security hardening
2. Minimalist by design
3. More management capabilities
4. Low hardware requirements
5. Small initial footprint
6. Remote Access capabilities
7. Simplified Backup Solution
8. High application/driver compatibility w/ 7
9. Centralized monitoring
10. Application/software control
11. Resource Allocation
12. SharePoint development
14. Advanced file sharing
I like having better control over my OS and I have never really cared to use any of the media features available in 7 (Homegroup, Media Center, etc). Compatibility is not an issue for the most part because I have a dual boot of Windows 7 to combat this problem. The point I am trying to make is you shouldn't run Windows Server because its more light or because its free and you can "hack it".. those are just some of the common logical fallacies I have heard.
"I run Windows Server because its light"
So what I could easily configure Tiny7 on my laptop with twice the less footprint of Windows Server.
If bluetooth compatibility is a must for you and you cannot find a proper way to get it to work on Windows Server then Windows Server is not the OS for you. I have segregated my partitions into functionality and not because I want to run Windows Server as a true desktop replacement. It will never be a true desktop replacement that it just foolish talk.
My 250GB HDD is partitioned as followed
1. 50GB Windows 7
Application compatibility (for those few apps that don't work in server)
2. 200GB Windows Server 2008 R2
Running FTP Server
Remote Access capabilities
Virtualization/VM testing or production
"General Purpose OS"
General media playback (listen to songs, movies, etc)
So if I ever wanted to play video games I would reboot my machine and play on Windows 7 and if i ever wanted to test VMs I would boot into Windows Server. I wanted to make Windows 7 really light on resources and make it strictly my "gaming OS" so that way I could benefit the most out of it due to no extra services running. I don't have any AV on 7 because I have disabled networking on 7... i copy all my ISOs and gamedata from server (where I downloaded all the games from) ... and then simply offline install them onto my 7 partition. I don't game very much so 90% of the time I am on Windows Server. As you have said you will undoubtedly run into compatability issues at one point or another (in your example with the Intel Turbo Boost monitor) so it might be wise to allocate your functionality (media, gaming on 7, general purpose on R2,etc)... to suit your needs. The performance increase you have seen as a result of running R2 is rather misleading.The performance benefit you see is most likely the direct cause of lowered resource consumption. A base Windows 7 Ultimate installation has over 40 services installed than a base Windows Server 2008 R2 installation. Even if Desktop Experience, .NET Framework 3.5, and Wireless LAN roles installed my laptop running R2 uses roughly 250MB less than its Windows 7 64-bit Ultimate counterpart. Also the behavior of the Disk I/O is designed differently in Server I believe which makes disk responsive behavior a little more responsive in R2 over 7... I have ran benchmarks of disk tests on 7 vs R2 and occasionally I do see a slight advantage toward R2. Theoretically I should not see a difference but ultimately I think this has to due with resource consumption than anything else.
Lastly,what is the main difference between 7 enterprise and 2008 r2? at first glance them seem very similiar. Which purposes are each best suited to?
Mostly you have to think of it from a client/server perspective. Windows 7 enterprise is optimized for a corporate environment. It has the ability to join a domain, connect to a DirectAccess server, enforce local policies (more so than Windows 7 home premium), BranchCache, BitLocker, ability to connect to virtual desktop infrastructure (VDI), as well as the string of media features you find in home edition of Windows 7. Pretty much in a nutshell Windows 7 enterprise has Windows 7 Home Premium features + enterprise-level functions...hence why it cost so much and you can only activate it via MAK or volume licensing. Keep in mind that all the corporate functions of 7 are purely client-side. You cannot become a domain, you can only join one. You cannot become a VDI you can only join one and so forth. As i said it all boils down to functionality.