Nine features of Windows Server 2008 that are ignored

  

The release of Windows Server 2008 is just around the corner, and its first candidate version has been released, and the official version will be released soon.

The previous server version of Windows or Windows Server 2003, although Microsoft released Windows Server 2003 R2, but after all, is not a separate new version. Therefore, the upcoming Windows Server 2008 is highly valued by Microsoft, and the major features related to Windows Server 2008 have been repeatedly rendered by the media. Among them, there are many features that are familiar to most IT experts, such as the installation version Server Core without Powered Interface, PowerShell and virtualization technology Windows Server Virtualization (the development code is Viridian, referred to as WSV). But Windows Server 2008 still has some unknown features, or features that most people ignore.

Here, the author lists the first nine technical features that are generally ignored in Windows Server 2008. Through the information published by the Windows Server 2008 Candidate version and Microsoft, the author has a detailed understanding of these nine features. Unlike the technologies mentioned above, these technical features have not yet attracted enough attention from the news media, nor have they been able to get big publicity. But these technologies are equally important, and perhaps even more important for corporate networks. The following are the nine features that are ignored by everyone. Windows Server 2008 features

◆1, potential network speed improvement. The network carries the responsibility of delivering more data. Since 1995, the network packet size that can be sent out in a packet has been maintained at 64 KB, and its data transmission traffic is about 5 MB. It's like a big truck with only a small box in it. It's big, but it doesn't improve transportation. The same is true for today's networks. If the transmission capacity of the network is strong, but the size of the data packet is still small, then it does not make much sense. The network stack package, which was almost rewritten in Windows Server 2008, has a number of new technologies, such as allowing larger packets to enter the network. At the same time, it can also instantly change the size of the packets in the network transmission, making it more efficient in transmission. The upper limit of the packet size was modified to 512KB, so it can be converted to a throughput of approximately 40MB. In other words, if the network is properly configured and tuned, it can run at 8 times the previous speed. This is indeed an exciting improvement.

◆2, one of the most concerned issues for IT administrators when migrating or upgrading to a new operating system is the ease of installation. At this time, we can't find more specific details about Windows Server 2008. From the official blog of Microsoft, Windows Server 2008 will give customers as much explanatory guidance as possible during the upgrade or migration. It will provide administrators with tools to help deploy, upgrade, and maintain Windows Server 2008. According to Microsoft, more information will be available in November.

◆3, group strategy improvement. Ralston said that there are two improvements to the group strategy, which are issues that administrators are concerned about. The first is a searchable database for group policy settings. Many administrators have used Excel tables to track the settings of their group policies. If there are thousands of similar settings, then obviously the way through the Excel table will bring a lot of trouble. Now, with the Group Policy Management Console, administrators can search for policies without the need for an Excel spreadsheet, which can significantly improve efficiency.

The upgrade of the second group policy is the ability to add annotations to the group policy settings. Adding annotations to your settings will not only help your current administrator, but will also help future administrators with fault detection for group policies. For example, when an administrator configures a group policy, the administrator can add annotations, why do I need to configure such a special policy; then, if a failure detection or reconfiguration of the policy is required, then the administrator (or its successor) Can understand the ins and outs of configuring this strategy. In addition, when the administrator performs group policy modeling, it points out the different meanings of different strategies, and those annotations can therefore be displayed in the report, which can simplify the structure of the group policy.

◆4, new password policy. In Active Directory (AD), a domain is a security dividing line. As an early version of Windows Server 2008, the security demarcation line for Windows Server 2003 is limited to having one password policy per domain. This is a relatively limited measure and has therefore been removed in Windows Server 2008. Now administrators don't need to create a new domain to get a new password policy. Administrators only need to set password policies for specific groups or users. If the CEO or CIO in the enterprise needs a stricter password policy, this is easy to achieve in Windows Server 2008.

◆5, AD RMS (Active Directory Rights Management Services, Active Directory Rights Management Services). In Windows Server 2003, the function corresponding to AD RMS is Windows Rights Management Services. It exists as a plug-in product only in Windows Server 2003 and requires additional purchases. In Windows Server 2008, AD RMS became a built-in feature and included some upgrade features. AD RMS helps create rights-protected files, listens for rights protection information, and ensures that the right users have the right permissions to access rights-protected data. For Windows Server 2008, some improvements to AD RMS include the ability to manage AD RMS through MMC.

◆6, event advancement. This feature makes sense for enterprise users who run Vista on the desktop. The event advancement feature aggregates the logs of selected computers and pushes them to the central console, making administrator management more efficient. For example, the administrator received a request from the client user for help. The user said that he saw an error message with the code "Event 51" displayed on his screen, indicating that a login problem has occurred. Different from the previous application of sniffing technology in the LAN to detect security, the administrator only needs to “subscribe” the event information of the Vista computer in the console of the server, so that the Vista desktop machine will automatically send the management. The information required by the staff is in the console.

◆ 7, WinRS (Windows Remote Shell, Windows Remote Shell). In order to connect to the command line interface on a remote computer in Windows Server 2003, the administrator must use the Terminal service. The so-called Terminal service is good, but the scalability is not very good, you need to connect to the console on each remote computer. WinRS can create secure connections to any remote computer when necessary, and only needs to do this from a single console. This will bring significant time and cost reductions to the administrator.

◆8, Auditpol.Auditpol is a detailed login tool that allows users to configure, create, backup and restore audit policies on any machine in the enterprise. Auditing is more important than ever before, especially with regard to compliance, so Auditpol may end the need for third-party auditing applications. It includes a greatly expanded list of audit accounts, not just the simple auditing tools shown in Windows Server 2003, and there are hundreds of different categories in Auditpol. Therefore, as Ralston said, it allows customers to "create detailed tracking of what is happening in the operating system."

◆ 9, PMC (Print Management Console, print management console). This feature was first released in Windows Server 2003 R2. But unlike Windows Server 2003 R2, in Windows Server 2008, PMC became a native feature that is available to every user. PMC is part of the Microsoft Management Console (MMC), which allows each administrator to monitor every printer in the entire enterprise from a single console. In addition, administrators can use Group Policy to map printers to specific groups of users so that the group can be used without actually installing the printer.


Copyright © Windows knowledge All Rights Reserved