Comparison of Windows7 and WINDOWS2008R2

Watch the post captured on the Internet, hope to help small partners!

WIN7 have, R2 not:
1, 32-bit version
2. The Game Explorer files can be extracted from Win7 and the game will be completely out of play.
3. Media Center (Find third-party software)
4, TV card support (Server 2008 Someone extracted a package from Vista, R2 temporarily not)
5, Bluetooth support (this has not been studied)
6, Superprefech (originally on the mixed, other personal feeling R2 no SP also faster than WIN7+SP)
7, side bar (this is very good to solve, the forum on a lot of posts)
8, Win7 already has OEM KEY,R2 now only 180 days trial KEY, but also can rearm 4 times, that is, two years can not be re-installed.
9. Voice Recognition (TX provided on 42 floor)

If you do not have the above or believe that you have the ability to solve, and you need to use the software is not limited to the installation of the server version, install R2 bar:
1, hard disk performance/network performance, from the online view of the test results, Win7 are worse than R2. Actually use down the feeling, I feel R2 's response is much faster, including but not limited to: A, the various file operations in the resource Manager, B, google/Microsoft Pinyin Input method appears the candidate Word speed (I only use Google, Microsoft Pinyin comes with, others have not tried); C, Web browsing speed (Ie8/chrome,firefox not used); D, a lot of software to the menu operation response speed.
PS:R2 has already turned on aero, and the system Properties "performance" has been set to "best effect".

2, as a student, you can familiarize yourself with the server system. If the machine configuration is good (dual-core, 4G memory, the best dual hard drives, graphics card does not matter), you can also install a VMware Workstation, on the VM installed other operating systems to simulate a LAN, learning to build a network environment.
PS: Although R2 comes with Hyper-v2, but desktop users are not recommended to use HYPER-V,VM many places convenient point, and virtual machine performance is not much worse than Hyper-V. Unless you're learning to build a server cluster with Hyper-V.

Misunderstanding:
1, Server R2 than Win 7 stable. Not necessarily, the stability of the system is affected by too many factors, the elimination of hardware factors, personal use of the habit is a very important issue. Often some people say that they use the server system is more stable, in fact, the people with R2 relatively high technical level, computer use habits are also relatively good, in fact, if they use the workstation system and maintain the use of the server, it is also very stable. And if there is no good use of computer habits, often on some of the chaotic site, often download, run some unknown program/game, install a lot of so-called beautification interface, a heard what software so download to play ... Even the server system can not help but this kind of toss.

2, the server System compatibility is poor. From a statistical point of view, this is true, but in fact: A, if there are 95% of the software can be run smoothly under the Win7 x64, then the R2 under the smooth operation will not be less than 93%;b, if you want to use the software is not compatible with the problem, then this problem is not a problem for you. In addition, in fact, many software have similar functions of other products can be replaced, one can't change another try.
PS: Of course, if you have a non-use software, you can no longer R2 the above run, it is still loaded back win 7.

Here is an introduction to the version of Win R2

Hardware has always played a relatively minor role relative to software, after all, the software really determines who can make the world's most remarkable achievements. However, when deploying new technologies, choosing the right hardware may be the most critical factor. In Microsoft Windows Server R2, for example, the software is used for most local and global networks. If the hardware selection and the requirements of the Administrator are not consistent with the problem, it may be that the application is running slowly, it may be over-budget, more serious may lead to the failure of this business application.

Choosing the right hardware for Windows Server R2 is certainly not as simple as verifying each option on the server order form. Before you try to narrow down your selection, several key steps and important considerations need to be carefully considered. The first step is to determine the version of Windows Server R2 (there are at least five versions) and which server roles will be used (there are dozens of types of server roles).

Windows Server R2 has specific requirements for CPUs. First, it requires a 64-bit processor, and when R2 is rolled out, Windows no longer supports a 32-bit processor. This may sound difficult to understand, but the vast majority of processors in today's market support 64-bit operating systems. This means that basically all new server hardware can meet this minimum requirement. Of course, as the name implies, the minimum requirement is minimal! Without increasing the burden on the network, you also need to select more hardware to meet your current and future needs, and all of these minimum requirements need to be within budget.

Windows Server R2 Basic Edition

Windows Server R2 Basic Edition is an entry-level version for small businesses. It is the cheapest of all versions, and of course there are some advanced features, such as only a simplified version of the Active Directory and no Hyper-V virtualization capabilities. In addition, the basic version also restricts existing functionality, such as restricting the number of concurrent Remote Desktop Services connections to 50, and using up to one processor and 8G of memory. So, with this release, you don't need to buy multiple processors and more than 8G of memory, in other words, the entry-level server will use the basic version of Windows Sever R2.

Windows Server R2 Standard Edition

The Standard Edition is also an entry-level server system. This version supports only 64-bit operating systems, and for hardware, the standard version supports up to 4GB of memory and four processors.

Windows Server 2008 focuses on the SME market, providing perfect domain, WEB, DNS, remote access, printing, file management, and application services. However, the Standard Edition does not support clustering, so it cannot be used in a fault-tolerant environment, data centers, or other large enterprise environment deployments. But the Standard Edition helps reduce hardware requirements. And if the standard version is deployed for a multitasking environment, the ability to support multiple processors can be useful. In addition, if you want to consider for the future, add more features to the server, upgrade is also very convenient. Windows Server R2 Standard Edition supports direct upgrade from Windows Server 2008, Windows Server 2003, and Standard Edition of Windows servers.

Windows Server R2 Enterprise Edition

Windows Server R2 Enterprise Edition offers more powerful features and scalability than Standard Edition, including cluster and Active Directory Federated Services (ADFS) that support up to 16 nodes. The core operating system also supports more advanced features such as support for up to 8 processors and up to 2TB of memory.

For the Enterprise Edition, hardware considerations become a bit more complex. IT managers need to consider how many users a server has to support, how to plan a cluster, how many other services and roles will need to be deployed (such as SQL Server, Sharepoint, and so on). Each increase in services and roles consumes resources and storage space.

Other features, such as Hyper-V virtual services, firewall services, Terminal Services, Remote Desktop, failover, and synchronization services, each of these features increase the burden on the server. Windows Server 2000, Windows 2000 Advanced Server, Windows Server 2003 Standard Edition, and Windows Server 2003 Enterprise Edition can all be upgraded directly to Windows Server R2 Enterprise Edition.

Windows Server R2 Data Center Edition

Data Center Edition is the highest-end product in the Windows Server R2 product family, primarily for business-critical businesses that require stability and high availability. Windows Server R2 Data Center Edition supports up to 2TB of memory and 8 to 64 processors. You can upgrade directly from the Datacenter Edition of Windows Server 2008, Windows 2000, and 2003 to Windows Server R2 Data Center Edition.

For data center editions, IT managers will find themselves in a world of rack-based blade servers, San arrays, and other high-end rack equipment. Here, technical support, like all features and functions, plays an equally important role in turning hardware devices into a more manageable, highly fault-tolerant environment.

Windows Web Server R2

Windows Web Server R2 2008 is essentially a version that is dedicated to providing WEB services. It includes IIS 7.0 and related services, such as Simple Mail Transfer Protocol (SMTP) and Telnet. Up to 4 processors can be supported, but only 32GB of memory is supported. Compared to other entry-level products, Windows Web Server R2 2008 lacks many features, such as clustering, BitLocker-driven encryption, multipath I/O, Windows Internet Naming Service (WINS), Removable Storage management, and San Management.

The Web Server Edition can run on low-end server devices or run at minimal hardware cost, and it can deploy Windows servers in a less expensive form. Because there is no traditional upgradeable path, the Web Server Edition is easy to install and requires no additional hardware configuration considerations. But the price is that as demand increases, you may have to migrate it to a different Web server platform to ensure hardware matching.

At this point, we have introduced the hardware selection from the basic aspect, but it is much more than that. Perhaps the biggest problem is the network's expectation of its growth in the future, and whether there will be an upgrade plan in the future.

Important factors also include whether you want to deploy a cluster/blade or SAN, as well as future network conditions. For many, the simplest approach is to discuss network requirements and desires with the server provider, and then select a hardware plan that includes the provider's technical support, simply upgrading and pre-installing Windows Server. That way, the scale is left to engineers, and deployment lets IT staff do it.

The main selection decision depends on whether you are looking for a deployment cluster/blade or SAN, and the expected activity on the network. For many, the simplest approach is to discuss network requirements and the needs of the server manufacturer and pick a bundled product that provides vendor-supported hardware that is easy to upgrade and pre-installed in Windows Server. In so doing, the standard is left to the engineer, and the deployment is handed to the IT staff for hands-on.