Nine characteristics of Windows Server2008 Server System _windows2008

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

The previous server version of Windows or Windows Server 2003, although Microsoft has published Windows Server 2003 R2, is not a stand-alone new version. As a result, the upcoming Windows Server 2008 is highly valued by Microsoft, and the significant features associated with Windows Server 2008 are being repeatedly rendered by the media. Many of these features are already familiar to most IT professionals, such as the installation version of Server Core, PowerShell, and virtualization technology with no graphical interface, Windows Server virtualization, whose development code is Viridian, Referred to as WSv). But Windows Server 2008 still has some unknown features, or features that are overlooked by most people.

Here, the author lists the top nine technical features that are generally overlooked in Windows Server 2008. Through the Windows Server 2008 candidate version and the information published by Microsoft, the author has a detailed understanding of these nine features. Unlike the technologies mentioned above, these technical features have not been able to attract enough attention from the media and have not been widely publicized. But these technologies are equally important, perhaps even more important for corporate networks. The following are the nine features of Windows Server 2008 that have been overlooked by the list

1, the potential network speed upgrade. The network carries the burden of delivering more data. Since 1995, the size of the network packets that can be sent out in one packet is maintained at 64KB, and its data traffic is about 5MB in size. It was like a big truck with only a small box in it, and even though the car was big, it didn't improve the transportation capacity at all. Today's network is also so, if the network transmission ability is very strong, but the packet size is still very small, then also not much significance. The network stacks that are almost rewritten in Windows Server 2008 live with new technologies, such as allowing larger packets into the network. At the same time, it can change the size of the packet in the network transmission, making it more efficient in transmission. The upper limit of packet size is modified to 512KB, so it can be converted to approximately 40MB of throughput. In other words, if the network is properly configured and tuned, it can run at 8 times times the previous speed. This is indeed an exciting improvement.

2, IT administrators in the migration or upgrade to a new operating system, one of the most concern is the convenience of installation. No more specific details about Windows Server 2008 are currently being found, and from Microsoft's official blog, Windows Server 2008 will give customers as much descriptive guidance as possible when upgrading or migrating. It will provide administrators with tools to help deploy, upgrade, and maintain Windows Server 2008. According to Microsoft's information, more information will be released in November.

3, the Group strategy improvement. Ralston indicates that there are two improvements to the group strategy, which are the concerns of the administrator. The first is a searchable database for Group Policy settings. Many administrators have used Excel tables to track their Group Policy settings. If there are thousands of similar settings, then obviously the way through the Excel table will cause a lot of trouble. Now, through the Group Policy Management console, administrators can search for policies without Excel tables, thereby significantly improving efficiency.

The upgrade of the second Group Policy is the ability to add annotations to the Group Policy settings. Adding annotations to the settings will not only help the current administrator, but also help future administrators to troubleshoot Group Policy. For example, when an administrator configures a group Policy, an administrator can add annotations, why such a special policy needs to be configured, and then the administrator (or his successor) can understand the ins and outs of configuring the policy if it is needed for fault detection or reconfiguration of the policy. In addition, when an administrator models a group Policy, it points out the different meanings of different policies, which can therefore be displayed in the report and simplifies the architecture of the Group Policy.

4, the new password policy. In the Active Directory (AD), the domain is a security demarcation line. As a previous version of Windows Server 2008, the security demarcation line for Windows Server 2003 is limited to one password policy per domain. This is a more restrictive measure, so it has been canceled in Windows Server 2008. Now administrators do not need to create a new domain to obtain a new password policy, the administrator needs only for specific groups or users to set password policy. If the CEO or CIO in the enterprise needs a tighter password policy, this is easy to achieve in Windows Server 2008.

5, AD RMS (Active Directory Rights Management services, Active Directory Rights Management Service). In Windows Server 2003, the function of the AD RMS corresponds to the Windows Rights Management Service (Windows Rights Management Services). It exists only as a plug-in product in Windows Server 2003 and requires additional purchases. In Windows Server 2008, AD RMS becomes an builtin feature and includes some upgrade features. AD RMS helps create rights-protected files, listens for rights-protected information, and ensures that appropriate users have the appropriate permissions to access the data that is protected by the rights. For Windows Server 2008来, some of the improvements to AD RMS include the ability to manage AD RMS through MMC.

6, the incident advance. This feature is useful for enterprise users who are running Vista on the desktop side. Event propulsion enables administrators to manage more efficiently by aggregating logs from selected computers and pushing them to the central console. For example, the administrator received a call from a client, and the user said that he saw an error message named "event 51" displayed on its screen, indicating that a logon problem had occurred. Unlike previously applied sniffing techniques in local area networks to detect security issues, administrators simply "subscribe" to the Vista computer's event information in the server's console, so that the Vista desktop machine automatically sends the information the administrator needs to 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, an administrator must use the Terminal service. The so-called Terminal Service is good, but scalability is not very good and needs to be connected to the console on each remote computer. WinRS can create a secure connection to any remote computer when necessary, and it only needs to be done from a single console. This will lead to a significant reduction in time costs for administrators.

8. Auditpol.auditpol is a detailed login tool that allows users to configure, create, back up, and restore audit policies on any machine in the enterprise. With particular emphasis on compliance, auditing is more important than ever, so auditpol may end up demanding third-party auditing applications. It includes a vastly expanded list of audit accounts, not just the simple auditing tools that are shown in Windows Server 2003, and the AuditPol includes hundreds of different categories. So, as Ralston says, it allows customers to "create a detailed track of what is happening in the operating system."

9, PMC (print Management console, printing management Console). This feature was first published in Windows Server 2003 R2. However, unlike in the Windows Server 2003 R2 version, in Windows Server 2008, PMC becomes a native feature that is available to each user. PMC becomes part of the Microsoft Management Console (MMC), allowing each administrator to monitor every printer in the enterprise from a single console. In addition, an administrator can use Group Policy to map a printer to a specific user group so that the group does not need to actually install a printer.