Ncomputing over windows 2003 server problem and solution

Symptom

Error “Server yet not ready, try again a bit later” an error where the hpvcard.dll failed to initialize.

Solution 1

Add the following key to the host:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
“SessionImageSize”=dword:00000020

Solution 2

Remove Security Update KB956572 also remove update KB958690

Symptom

Error "to log on to this remote computer, you must be granted the Allow log on through Terminal Services right. By default, members of the Remote Desktop Users group have this right. If you are not a memeber of the Remote Desktop Users group or another group that has this right , or if the Remote Desktop Users group doesn not have this right, you must be granted this right manually"

Solution 1 

Add user to Remote Desktop User Group

Solution 2 

Configure the security setting in Default Domain Controller Policy GPO:

1.    Run gpmc.msc  to open the Group Policy Management console.
2.    Expand  Domain Controllers, right-click Default Domain Controller Policy, and click Edit.
3.    In the Group Policy Management Editor window, expand Computer Configuration\Windows Settings\Security Settings\Local Policies\User Right Assignment\Allow log on locally
4.    Add User or Group and click OK three times to apply the settings.
5.    Run gpupdate /force to apply the policy.

Excel 2003 opens slower across the network

Symptoms:
After you install MS11-021 and the Office File Validation (OFV) Add-in for Office 2003 (KB 2501584), workbooks stored in a network location open slower over the network in Excel 2003 than they did without the OFV installedcompare to open from local drive.

Cause:
The OFV reads the file to determine whether the file is trustworthy before it opens the file. When this is done over the network it reduces performance because of the network traffic when reading in the parts of the workbook.

Solution:
You can use the EnableOnLoad registry entry to configure how you want Excel to handle opening workbooks for the OFV. By default, the EnableOnLoad entry is not present in the Windows registry.

1. Start regedit


2. Locate HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\


3. Add New Key: Excel


4. Under Excel, add New Key: Security


5. Under Security, add New Key: FileValidation


6. Under FileValidation, add DWORD Value: EnableOnLoad with default value is 0 which disables the validation.

Or you can create a reg files contain below text and execute them

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Security\FileValidation]"EnableOnLoad"=dword:00000000

More Info: http://support.microsoft.com/kb/2570623

Event ID: 7023 DHCP Client service does not start

Symptoms:

The DHCP Client service does not start after you upgrade a Windows 2000 Server-based domain controller to Windows Server 2003

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: Date
Time: Time
User: N/A
Computer: ServerName
Description: The DHCP Client service terminated with the following error: Access is denied.

Cause:
This problem occurs because the Network Service account does not have sufficient permissions to access the following registry subkeys when you upgrade to Windows Server 2003:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip

Solution:

To resolve this problem, assign the Network Service account Full Control access to the following registry subkeys and subkeys under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip

http://support.microsoft.com/kb/895149

Prevent the network adapter from detecting a link state

To prevent the network adapter from detecting a link state, follow these steps.

Note The NetBEUI protocol and the IPX protocol do not support Media Sensing.

1. Start Registry Editor.
2. Locate the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

3. Add the following registry entry to the Parameters subkey:

Name: DisableDHCPMediaSense
Data type: REG_DWORD (Boolean)
Value: 1

Note This entry controls the behavior of Media Sensing. By default, Media Sensing events trigger a DHCP client to take an action. For example, when a connect event occurs, the client tries to obtain a lease. When a disconnect event occurs, the client may invalidate the interface and routes. If you set this value data to 1, DHCP clients and non-DHCP clients ignore Media Sensing events.

4. Restart the computer.

Note Microsoft Windows Server 2003 supports Media Sensing when it is used in a server cluster environment. By default, however, Media Sensing is disabled in a Windows Server 2003-based server cluster, and the DisableDHCPMediaSense registry entry has no effect. In Windows Server 2003 Service Pack 1 (SP1), the DisableClusSvcMediaSense registry entry was introduced. You can use this registry entry to enable Media Sensing on the Windows Server 2003-based nodes of a server cluster. The details of the DisableClusSvcMediaSense registry entry are as follows:

Key: HKEY_LOCAL_MACHINE\Cluster\Parameters
Name: DisableClusSvcMediaSense
Data type: REG_DWORD (Boolean)
Default value: 0

By default, the DisableClusSvcMediaSense entry is set to 0. When this entry is set to 0, Media Sensing is disabled. If you set the DisableClusSvcMediaSense entry to 1, you can use the DisableDHCPMediaSense entry to enable Media Sensing. This behavior matches the behavior of a Microsoft Windows 2000 Server cluster environment.

More info: http://support.microsoft.com/kb/239924/

Handling Exchange IMF & SCL

To enable IMF auto-updates:

1. In Registry Editor, navigate to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange

2. Create the following value (DWORD):

ContentFilterState

and give it a value of 1.

To configure IMF to also add the SCL rating to the archived message:

1. In Registry Editor, navigate to the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\ContentFilter

Note: You might not find this key in place. If that is the case, create a new key under the Exchange key and call it ContentFilter

2. Within the ContentFilter key, create the following value (REG_DWORD):

ArchiveSCL

and give it a value of 1.

restart the Simple Mail Transfer Protocol (SMTP) service

The registry key for a TCP IP printer port

The registry key for a TCP IP printer port looks like this :

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Monitors\Standard TCP/IP Port\Ports]
"StatusUpdateInterval"=dword:0000000a
"StatusUpdateEnabled"=dword:00000001

;all defaults : RAW, port 9100

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Monitors\Standard TCP/IP Port\Ports\IP_1.92.1.2]
"Protocol"=dword:00000001
"Version"=dword:00000001
"HostName"=""
"IPAddress"="1.92.1.2"
"HWAddress"=""
"PortNumber"=dword:0000238c
"SNMP Community"="public"
"SNMP Enabled"=dword:00000000
"SNMP Index"=dword:00000001

;customized: LPR, LPR Queue Name, port 515

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Monitors\Standard TCP/IP Port\Ports\IP_192.168.1.123]
"Protocol"=dword:00000002
"Version"=dword:00000001
"HostName"=""
"IPAddress"="192.168.1.123"
"HWAddress"=""
"PortNumber"=dword:00000203
"SNMP Community"="public"
"SNMP Enabled"=dword:00000000
"SNMP Index"=dword:00000001
"Queue"="this_is_a_user_defined_lpr_ue"
"Double Spool"=dword:00000000

Remotely Adding Firewall Exception List

Purposes:
You want to add Firewall Exception List under Client PC remotely

Solution:
1. Make sure you can remote registry Client PC
2. Open regedit.exe
3. File > Connect Remote Registry...
4. Browse your Client PC Name
5. Add this entry: (in this sample I add Radmin access)
[HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\GloballyOpenPorts\List]
"4899:TCP"="4899:TCP:LocalSubNet:Enabled:Radmin"

6. To Enable Open File and Sharing Access
[HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\GloballyOpenPorts\List]
"139:TCP"="139:TCP:*:Enabled:@xpsp2res.dll,-22004"
"445:TCP"="445:TCP:*:Enabled:@xpsp2res.dll,-22005"
"137:UDP"="137:UDP:*:Enabled:@xpsp2res.dll,-22001"
"138:UDP"="138:UDP:*:Enabled:@xpsp2res.dll,-22002"

7. To Enable Disable Firewall, using this Key
[HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile]
"EnableFirewall"=dword:00000001
"DisableNotifications"=dword:00000000
"DoNotAllowExceptions"=dword:00000000