Based on the Windows 2008 environment, some of the main objectives of the management test

test are based on the following considerations:

The current management scenario of the enterprise is still complex and diverse. Many enterprises choose Windows Server 2000, Windows Server 2003. , Windows Server 2003 R2+SP2, of course, in my scene also contains some early adopters, using Windows Server 2008, then the corresponding client is the same, including Windows 2000, Windows XP Professional, Windows Vista, Windows Vista sp1, What content should you pay attention to in many system combination applications? I believe this is all the content that the company will consider in the future, so I did some testing and shared some content with you.

Test Environment Description:

Windows Server 2003 R2+Windows Vista SP1

Windows Server 2008 + Windows Vista

Windows Server 2008 + Windows Vista SP1< Br>

Test Content:

Group Policy Management and Remote Management in Windows Server 2003 R2+Windows Vista SP1

Group Policy Management and Remote Management in Windows Server 2008 + Windows Vista SP1 Br>

Windows Server 2008 + Windows Vista Group Policy Management and Remote Management

Environment Construction Instructions:

Ordinary Active Directory Environment Creation, there are already too many articles, here is not Again, the only point to note is that in the Windows Server 2003 era, if you join the Windows 2000 domain environment, you need to use the adprep command. Also, if you need to execute this command in a non-pure Windows Server 2008 environment, adprep, this command is on the installation CD. Under the \\sources\\adprep folder, users who need to use the Schema Master identity first need to execute adprep /forestprep, and then need to be in each domain in the forest. Line extensions, adprep /domainprep /gpprep, you can, if the plan is to have the read-only domain controller (Windows Server 2008 new features), you need to perform adprep /rodcprep.

Some experiences in the test environment:

1: If you manage Windows Vista In terms of using Windows Server 2008, it is a perfect match, but many companies will not easily upgrade to the new system, so it is necessary to have Windows 2000 Server to manage Windows XP scenarios, but this is changed to Windows Server 2003 to manage Windows Vista. What is the problem here?

First of all, I will give you a description. In Windows Vista, there are more than 2747 group policies. The main updates are focused on the following aspects:

1. Mobile Device Management

2. UAC

3. NAP

4. Windows Defender

5. Power Management

6. IE Management, etc.

In these aspects, the Windows 2003 Group Policy is no longer supported by default. Can you import the vista group policy as before? There is a new problem here. The Windows Vista group policy has been changed to the new mode admx file format, so There is no way to simply import to solve this problem.

2: The group strategy in Vista has adopted the new format admx, its benefits I see the two most obvious is that the first file gets smaller, imagine if multiple domains in a large forest The related group policy file copy is still a relatively large traffic (a few days ago and the old leaf test through the CDMA test OCS voice call delay rate, so bandwidth is always a topic of insufficient), the size of a specific group policy file, you can Look at your sysvol folder. If there are multiple OUs, it’s even more horrible, so Microsoft is aware of this (in Windows Server 2003, DNS condition forwarding is not the case), improved in size, the second It is the support of multi-language environment, so different versions of the Group Policy language in different language versions of the Windows environment can also be very well supported. The original horror, so many enterprise regulations only allow English group policy.

3: Group Policy files in XP and 2000 2003 environments are adm files, but Microsoft also provides related tools for conversion (ADMX Migrator), and then try to import after conversion. However, I still recommend using the ADMX and ADML version group policy files, after all, this is the trend of the future.

4: Some documents explain that managing Windows Vista in Windows Server 2003 environment can be solved by installing adminpak.msi, but note that Windows Server 2008 is managed by Windows Vista SP1, which is not familiar to everyone. Adminpak.msi, but RSAT, of course you can use it to manage some parts of the Windows Server 2003 environment), so it is recommended to solve the problem of low-level server management high-version client by copying the group policy file.