Limitation on Proxy Exceptions in Windows 2003 Group Policy Object Editor

From Microsoft KB302224

Description
When you use the Group Policy Object Editor, and you configure the proxy settings, the text box that contains the proxy exception list may be truncated if more than 255 characters are used. Also, if you previously clicked to select the Do not use proxy server for local check box, the check box may be cleared. Because of a limitation in the way INS files are read, the proxy exception list is limited to 255 characters. The Do not use proxy server for local check box appends the text ";" to the end of the list. This text is eight characters long, and the 255 characters must include these characters. Therefore, when you click to select the Do not use proxy server for local check box, the total length of the exception list is actually 247 characters.

Resolution
Apply Windows Server 2003 Service Pack 2. After you install this hotfix, the proxy exception list is limited to 1024 characters.

Missing Files in Certain Folders on Windows Server

Description
On your Windows 2003 server some files in certain folders are missing. However when you rename the folder to other name, the missing files suddenly appear. If you rename the folder back to the original name, the files are missing again. You already check the security permission, possible viruses and malware, but everything seems to be normal.

Resolution
You should check whether you had programs that hide/lock/protect those files from appearing. One of the example is a program called Lock Folder XP. These programs run on Kernel mode and cannot be seen from user mode process monitoring. You can use Rootkit Revealer and Process Explorer from Microsoft SysInternals to try to watch the process.
After you found the program that cause the issue, you can try to uninstall it.
You may need to supply the correct password to uninstall or modify the program.

"Messages awaiting directory lookup" SMTP queue in Exchange 2003

Description
Suddenly you see an error "Messages awaiting directory lookup" on one of your Exchange Server 2003. Email cannot be send to/from those Exchange Server. They just stuck on your SMTP queue. Your other email server is working normally.

Resolution
One area that you might want to check when you see this error message in your Exchange Server is whether your storage group configured for Journalling or not.
If the answer is yes, you might want to check about the account that you use for Journalling.
In my case the account was move to other OU and simply return it back to the original OU resolve the issue.

There is a Microsoft Knowledge Base 884996 that you might want to check for further Information regarding this matter.

Supported Guest OS on Windows Server 2008 Hyper-V

Supported Guest OS

The following is the list of guest operating systems that will be supported on Hyper-V.

Windows Server 2008 x64 (VM configured as 1-, 2-, or 4-way SMP)

• Window Server 2008 Standard x64
• Window Server 2008 Enterprise x64
• Window Server 2008 Datacenter x64
• Windows Web Server 2008 x64

Windows Server 2008 x86 (VM configured as 1-, 2-, or 4-way SMP)

• Window Server 2008 Standard x86
• Window Server 2008 Enterprise x86
• Window Server 2008 Datacenter x86
• Windows Web Server 2008 x86

Windows Server 2003 x86 (VMs configured as 1- or 2-way SMP only)

• Window Server 2003 Standard x86 Edition with Service Pack 2
• Window Server 2003 Enterprise x86 Edition with Service Pack 2
• Window Server 2003 Datacenter x86 Edition with Service Pack 2
  

Windows Server 2003 x64 (VMs configured as 1-way only)

• Window Server 2003 Standard x64 Edition with Service Pack 2
• Window Server 2003 Enterprise x64 Edition with Service Pack 2
• Window Server 2003 Datacenter x64 Edition with Service Pack 2
  

Linux Distributions (VMs configured as 1-way only)

• SUSE Linux Enterprise Server 10 with Service Pack 1 x86 Edition
• SUSE Linux Enterprise Server 10 with Service Pack 1 x64 Edition
  

Supported Client Operating Systems

• Windows Vista Business x86 with Service Pack 1 (VMs configured as 1-way only)
• Windows Vista Enterprise x86 with Service Pack 1 (VMs configured as 1-way only)
• Windows Vista Ultimate x86 with Service Pack 1 (VMs configured as 1-way only)
• Windows XP Professional x86 with Service Pack 3 (VMs configured as 1-way only)

How to Install Active Directory Using Restored Backup Media

By installing Active Directory from restored backup media, you can reduce the replication traffic that is initiated during the installation of an additional domain controller in an Active Directory domain. Reducing the replication traffic reduces the time necessary to install the additional domain controller. The procedures in this task are particularly useful for installing domain controllers in remote sites.

To install Active Directory from restored backup media:
1. Click Start, click Run, type dcpromo /adv, and then press ENTER.
2. In the Active Directory Installation Wizard, select Additional domain controller for existing domain.
3. Select From these restored backup files, and point to the same location where you restored the system state data.
4. If the domain controller whose system state backup you are using is a global catalog server, the Active Directory Installation Wizard asks you whether you want this server to also be a global catalog server.
5. Give appropriate credentials for the operation.
6. Enter the domain of the new domain controller. This domain must be the domain of the domain controller whose system state backup you are using.
7. Complete the remaining pages of the Active Directory Installation Wizard.

Dcpromo.exe will install Active Directory using the data present in the restored files, which eliminates the need to replicate every object from a partner domain controller. However, objects that were modified, added, or deleted since the backup was taken must be replicated. If the backup was recent, the amount of replication required will be considerably less than that required for a regular Active Directory installation.