我的 Blog: 3月 2009

2009/03/31

KMS SERVER ERROR

KMS_Error_0xC004C008_Activating_Client
here

MS
VA2.0 Deployment Guide

2009/03/28

upgrade from Windows Server 2000 to Windows 2003 Server

We will in this article not go into a step by step guide on how you carry out the actual upgrade from Windows Server 2000 to Windows 2003 Server, as all you need to do is to insert the Windows 2003 Server CD > Navigate to the i386 folder > Execute Winnt32.exe and > Select Upgrade (Recommended), then its just a simple matter of following the on-screen instructions.

2009/03/26

printer spooler fail to start

sc config spooler depend= RPCSS

2009/03/20

Exchange 2003 升級 2007 電子郵件地址原則

here

cisco asa 5505 設定

here

Step 1 Locate an RJ-45 to RJ-45 Ethernet cable.

Step 2 Connect one end of the Ethernet cable to an Ethernet port (ports 0 through 7), as shown in Figure 4-2. (Typically Ethernet port 0 is used to connect to an Internet router.)
===

Step 1 Make sure that the speed of the PC interface to be connected to one of the ASA 5505 inside ports is set to autonegotiate. This setting provides the best performance.

By default, the ASA 5505 automatically negotiates the inside interface speed. If autonegotiate is not an option for the PC interface, set the speed to either 10 or 100 Mbps half duplex. Do not set the interface to full duplex; this causes a duplex mismatch that significantly impacts the total throughput capabilities of the interface.

Step 2 Configure the PC to use DHCP (to receive an IP address automatically from the ASA 5505), which enables the PC to communicate with the ASA 5505 and the Internet as well as to run ASDM for configuration and management tasks.

Alternatively, you can assign a static IP address to your PC by selecting an address in the 192.168.1.0 subnet. (Valid addresses are 192.168.1.2 through 192.168.1.254, with a mask of 255.255.255.0 and default route of 192.168.1.1.)

When you connect other devices to any of the inside ports, make sure that they do not have the same IP address.

Note The MGMT interface of the adaptive security appliance is assigned 192.168.1.1 by default, so this address is unavailable.

Step 3 Use an Ethernet cable to connect the PC to a switched inside port on the rear panel of the ASA 5505 (one of the ports numbered 1 through 7).

Step 4 Check the LINK LED to verify that the PC has basic connectivity to the ASA 5505.

When connectivity is established, the LINK LED on the front panel of the ASA 5505 lights up solid green.

2009/03/18

Session Directory and Load Balancing Using Terminal Server

here

Summary

Terminal Server Session Directory is a feature that allows users to easily and automatically reconnect to a disconnected session in a load balanced Terminal Server farm. The session directory keeps a list of sessions indexed by user name and server name. This enables a user, after disconnecting a session, to reconnect to the correct terminal server where the disconnected session resides to resume working in that session. This reconnection will work even if the user connects from a different client computer.

This white paper discusses how to plan and deploy a load balanced terminal server farm using session directory, and how the session directory operates in a load balanced environment.

Included in This Document•
Session Directory Overview
•
Load Balanced Configurations
•
Session Directory
•
Summary
•
Appendix

以 Windows 負載平衡服務使用終端機伺服器 243523

您可以使用 WLBS (或 Windows 2000 中的 NLB) 在一組「終端機伺服器」中散佈眾多的「終端機伺服器」用戶端。下列清單包含設定 WLBS 或 NLB 的指導方針。將使用者資訊、系統資訊和一般資料儲存在一個位置上，例如 SQL 伺服器內，這樣每個「終端機伺服器」便能服務網路上的所有使用者。我們建議您使用 Microsoft Cluster Services (MSCS) 共用資料。

WLBS/NLB 要靠用戶端的 IP 位址 (如果您使用「無相似性」，則為連接埠編號) 來判斷哪一個「終端機伺服器」為用戶端提供服務。如果您將 WLBS/NLB 設定為使用「相似性」，則只要您不變更「終端機伺服器」叢集，用戶端所用的 IP 位址會由相同的「終端機伺服器」提供。

在工作階段中，當「終端機伺服器」用戶端從「終端機伺服器」中斷連線時，「終端機伺服器」會將該用戶端的工作階段標示為「中斷連線」。您在該工作階段內所用的用戶端程序和虛擬記憶體空間，仍會保留在伺服器上，只要「中斷連線」的工作階段狀態沒有結束，這些資訊便會對應至使用者的「工作階段識別碼」。如果您將用戶端電腦重新連線到「終端機伺服器」而該工作階段仍處於「中斷連線」狀態的話，可以用該工作階段狀態資訊繼續使用在中斷連線之前所用的相同程序和程式。

「終端機伺服器」不支援將記憶體內的工作階段狀態複製到其他的「終端機伺服器」或與其他的「終端機伺服器」共用這些資訊。如果您在工作階段時從「WLBS/NLB 終端機伺服器」叢集成員之一的「終端機伺服器」中斷連線，而在重新連接到該「終端機伺服器」之前，用戶端的 IP 位址變更了，這時候，連線的要求可能會由叢集中，不同的「終端機伺服器」提供服務。如果發生這種現象，記憶體內的工作階段便會繼續使用原始伺服器上的資訊。您需要在新的「終端機伺服器」上啟動新的工作階段。

如果您需要中斷連線的用戶端連線到相同的「終端機伺服器」，才能回復「中斷連線」工作階段，用戶端的電腦需要使用靜態的 IP 位址，而 WLBS/NLB 必須設定為使用「單一相似性」。請注意，透過您的 ISP、從 LAN 上的 DHCP 伺服器所取得的 IP 位址可能會變更，如同漫遊使用者的 IP 位址。如果固定 IP 不是必要條件，則您可以在從「終端機伺服器」叢集要求服務時，使用用戶端電腦上的不同 IP 位址，且可將 WLBS/NLB 設定成不使用「相似性」。

2009/03/10

NLB 單點及多點

NLB 單點及多點
今天設定單點不通,ping 不到168.95.1.1 , 改成多點就OK.
文件說:預設用單點即可.

A Windows NLB cluster can be configured in either unicast or multicast mode, where unicast is the default mode.

Unicast Mode
With the WNLB cluster configured in unicast mode, the MAC address of each server’s network adapter will be changed to a virtual cluster MAC address, which is the MAC address that will be used by all servers in the Windows NLB cluster. When unicast mode is enabled, clients can only connect to the servers using the cluster MAC address.

Multicast mode
With the Windows NLB cluster configured in multicast mode, a multicast MAC address is added to the cluster adapter of each server in the cluster. Note that I write “is added”, as each server will retain their original MAC addresses.

A Windows NLB cluster, no matter what mode it is configured in, works with just a single network adapter installed in each server, but it is recommended to install a second network adapter in each server, in order to achieve optimal performance, and to separate ordinary and cluster related network traffic.

So what mode should I use for my Exchange 2007 Client Access solution and how many network adapters should I install in each Client Access server? Well, best practice recommendations are to install two network adapters and use unicast mode, so that the host and cluster network traffic are each separated in their own respective network adapter