Detailed explanation of the top ten features of Windows Server 2008

Many users know that Microsoft summarized the top ten features of WS2K8 in WinHEC 2007 conference, changing the way enterprises use Windows, and the physical and logical architecture of the network. Let’s take a look.

10, self-repair NTFS file system

From the DOS era, the file system error means that the corresponding volume must be repaired offline, and in WS2K8, a new system service will be in The background works silently, detects file system errors, and can automatically fix it without shutting down the server.

With this new service, when the file system is in error, the server will only temporarily be unable to access some of the data, and the overall operation is basically unaffected, so CHKDSK can basically retire.

9. Parallel Session Creation

If you have a terminal server system, or if multiple users are simultaneously logged into the home system, these are Sessions. Prior to WS2K8, the creation of Sessions was done one by one, which was a bottleneck for large systems. For example, when hundreds of people returned to work on Monday morning, many people had to wait for the Session to initialize.

Vista and WS2K8 have added a new Session model that can launch at least 4 at the same time, and if the server has more than four processors, it can also launch more at the same time. For example, if you have a media center in your home, each family member can open the media terminal in their own room and get the video stream from the Vista server at the same time, and the speed will not be affected.

8, fast shutdown service

A major historical problem with Windows is that the shutdown process is slow. In Windows XP, once the shutdown starts, the system will start a 20-second timer, then remind users whether they need to manually close the program, and in Windows Server, the impact of this problem will be more obvious.

When it comes to WS2K8, the 20-second countdown is replaced by a new service that can always signal when the application needs to be shut down. Developers are beginning to wonder if this new approach will deprive the application of the right, but now they have accepted it and think it's worth it.

7, Core Transaction Manager (KTM)

This feature is especially important for developers because it can greatly reduce or even eliminate the most frequently caused system

registration Reason for table or file system crash: Multiple threads attempting to access the same resource.

There is also a new component of KTM in the core of Vista, which is designed to facilitate a lot of error recovery work, and the process is almost transparent, and KTM can do this because it can be used as A transaction manager accessed by the transaction client works.

6, SMB2 network file system

A long time ago, Windows introduced SMB as a network file system, but SMB is now too old, the historical mission has been completed, so WS2K8 adopts SMB2 to better manage the growing volume of media files.

In Microsoft's internal testing, the SMB2 media server can reach four to five times the speed of Windows Server 2003, which is equivalent to 4000% efficiency improvement.

5, Random Address Space Distribution (ASLR)

ASLR has appeared in 64-bit Vista, which ensures that any two concurrent instances of the operating system are loaded into different ones at a time. On the memory address.

Microsoft said that malware is actually a bunch of unregulated code that does not follow the normal procedures required by the operating system, but if it wants to write files on the user's disk, you must know the system service. Where? On 32-bit Windows XP SP2, if malware needs to call KERNEL32.DLL, the file will be loaded into the same memory space address each time, so it is very easy to use maliciously.

But with ASLR, the address space of each system service is random, so malware wants to find them easily, basically no play.

4, Windows Hardware Error Architecture (WHEA)

In the end, Microsoft decided to standardize the error. To be precise, the application reported to the system that the protocol that found the error was standardized.

The big problem with the current error report is that there are many ways for the device to report errors. There is no standard between various hardware systems. Therefore, it is difficult to collect all the error resources and uniformly present when writing the application. This means writing a lot of specific code for each specific situation.

In WS2K8, all hardware related errors are reported to the system using the same interface. Third-party software can easily manage and eliminate errors, and the development of management tools will be easier.

3. Virtualization

Although Microsoft has streamlined its virtualization software "Viridian", it is still a boon for businesses to reduce overall costs. Although VMware is unique in the virtual machine space, Viridian has enabled both Intel and AMD to provide support for hardware-based virtualization, providing a virtual hardware support platform that VMware can't do.

According to IDC statistics, US companies have already spent billions of dollars on processor resources that they simply don't use, but this is not their fault, but the operating system management problem causes up to 85%. CPU resources are often idle. A major goal of WS2K8 plus virtualization is to enhance the use of idle resources and reduce waste.

2, PowerShell Command Line

PowerShell was originally planned as part of Vista, but as an enhancement to the free download, it became a key component of Exchange Server 2007, and then it will be A member of WS2K8 that is indispensable. This new command line tool can be used as a complement to graphical interface management or it can be completely replaced.

Iain McDonald, Director of Windows Server, declares: "If everything is up to me, I would be happy to set PowerShell as the default shell for Windows." I like this thing too much. ”

At the TechEd 2007 conference early next month, Microsoft will showcase some of PowerShell's new applications.

1, Server Core

This is the real change of Microsoft. If you are a Unix and Linux administrator, you may be familiar with low-power, virtualized, graphics-free, server systems that require only one terminal management in a protected environment that acts as a DHCP and DNS server, but Windows can do the same. Done.

As a server operating system, Windows Server has always been a problem, it is "Windows", because administrators do not need to install graphics drivers, DirectX, ADO, OLE, etc., after all, they do not User programs need to be run; moreover, graphical interfaces have always been an important factor influencing Windows stability.

Starting with WS2K8, these things will become an option when installing. The current Beta 3 version can handle eight roles, and eventually there will be more official versions, such as file servers, domain controllers, DHCP servers, DNS servers, etc., and its location is also very clear: a small and secure server that is secure and stable.

In addition, if the configuration is reasonable, the administrator can also remotely manage the Server Core installation without a graphical interface, just open the TCP 3389 port.

PowerShell can also run on Server Core, but obviously, the graphical interface program will not work, and the .NET Framework will not be supported. The game naturally does not need to mention it.