Johnny Yao WorkSpace

  公司環境啟用 Windows 2008 Terminal server, 並將剪貼簿功能開啟, 但 user 於遠端連線 terminal 後, 並無法將 local 複製的東西貼到遠端server內. 解決方式 ： 1. 請先進行下列確認，XP client端的服務確認下列已啟用，在進行測試 開始→執行→輸入「services.msc」開啟系統服務視窗後， 依序 啟動以下服務： Network DDE DSDM Network DDE ClipBook   步驟 : 遠端工作階段剪下及貼上 許多 [遠端桌面] 和 [終端機服務] 連線都會提供剪貼簿共用，讓您從遠端工作階段中使用的程式中剪下資訊，並貼到本機電腦 (您目前使用的電腦) 上執行的程式中，反之亦然。 會將從應用程式中剪下或複製的資訊移到 [剪貼簿] 上，並保存在那裡，直到清除 [剪貼簿] 或者剪下或複製另一個資訊為止。 由於本機和遠端電腦共用剪貼簿，您可以從 [遠端桌面連線] 視窗內的文件複製文字或圖形，並貼到本機電腦上的文件中。如需更多關於在遠端桌面工作階段中複製、貼上和使用本機檔案與資料夾的資訊，請參閱 在遠端工作階段中存取本機檔案及資料夾 。 注意事項 根據網路原則及遠端電腦上執行的 Windows 版本，剪貼簿共用對一些遠端桌面連線可能沒有作用。 1. 確認GPO   2. 可能狀況 Blog Extended Reading More Information & Reference 1. Cutting and pasting to and from remote sessions 2. Why does my shared clipboard not work? (Part 1) 3. Why does my shared clipboard not work? (Part 2) 4. Windows Server 2008 Terminal Services Web Access (Part 1)

      Blog Extended Reading   More Information & Reference 1. Understanding Memory Configurations and Exchange Performance

  1. CAS 有大量RPC client access，CAS請準備充足的CPU Core & MEM 2. Mailbox:HUB ---> 5:1 (with AntiVirus Scanning) 3. Mailbox:CAS ---> 4:3 (很高的比例) 4. Mailbox role 上，每個處理器核心，處理基準為500U 5. 建議佈署兩部HUB & CAS 在上述比率中，必須注意這是 處理器核心的比率 ，不是處理器的比率。因此，計算比率時， 雙核心處理器會算成 2。 Important: The Mailbox to Client Access server role ratios detailed in the chart above contains recommendations based on the Exchange 2010 feature, RPC Client Access. This feature requires a larger memory and processor configuration to manage the increase loads placed on the Client Access server role. The RPC Client Access feature is enabled by default. When considering these recommendations, be aware of the following: The preceding ratios are a general rule, and they may not be valid for every topology. A general rule means that the ratios are not a requirement for support or a definitive rule. Ratios can change dramatically based on user profiles. A user that creates a larg

    Send and Receive Connectors Exchange Server 2003 uses SMTP virtual server interfaces for each protocol to send and receive messages between Exchange servers. Configuration is required only when you modify the default values or create connectors that are specific to another organization. The Exchange 2010 Hub Transport servers use an implicit connector to route messages between sites. This connector is called the intra-organization Send connector. During installation, explicit Receive connectors are automatically created on each Hub Transport server. One Receive connector is configured to receive SMTP traffic from all sources by listening on port 25. A second Receive connector is configured to receive SMTP traffic from non-MAPI clients by listening on port 587. Explicit Send connectors and Receive connectors are created on Hub Transport servers only when you want to create a connector that sends messages to a specific address space or receives messages from a specific addres

  組織內傳送連接器  Intra-organization Send Connector 組織內傳送連接器是隱含且隱藏的傳送連接器 ， 是由 Exchange Server 2007 自動計算而來，而且會讓相同組織中的 Hub Transport Server 彼此轉送郵件，而不需要使用明確的傳送連接器 。因為 Edge 訂閱的 Active Directory 中內含具有 Active Directory 站台關聯的組態物件，所以也可以使用組織內傳送連接器將郵件轉送至該 Edge Transport Server。 只有位在已訂閱 Edge Transport Server 之相同 Active Directory 站台中的 Hub Transport Server，才可以直接與已訂閱 Edge Transport Server 進行電子郵件的傳送及接收。如果您擁有多站台樹系，而且 Exchange 2007 已部署在多個站台中，則非訂閱站台中的 Hub Transport Server 會將輸出電子郵件路由傳送至已訂閱站台。已訂閱站台中的 Hub Transport Server 會將輸出電子郵件路由傳送至 Edge Transport Server。 下圖顯示來自 Exchange 組織中之非訂閱 Active Directory 站台的輸出郵件流程。具有兩個站台的 Active Directory 樹系就已經建立 Edge 訂閱與站台 A 的關聯。如果郵件是從站台 B 傳送給網際網路收件者，則會先將郵件轉送至站台 A。而站台 A 中的接收 Hub Transport Server 會使用組織內傳送連接器將該郵件轉送至 Edge Transport Server。Edge Transport Server 接著會將郵件路由傳送至自動建立的 EdgeSync - Site-A to Internet 傳送連接器，以傳遞至收件者網域。   Blog Extended Reading 1. REF: Exchange 2010 - Upgrading from Exchange 2003 Transport (Part1) 2. REF: Exchange 2010 - Upgrading from Excha

  1. E2K3 使用 link state routing table 2. E14 則不使用，採HUB直接對連 3. HUB 直接對連不通時，Exchange HUB 會去參考 IP site link costs 來找尋最接近目的的site 來暫存郵件 ---> queue at point of failure 4. 這邊又再次提到， 抑制連結狀態更新 的重要，避免E2K3重新計算Routing 及不斷重送 (意思就是說，現在最低成本的路由不通，先queue 信等路由通了再重送吧，不要重新計算路由到處重送) 5. 最後一段的意思還要再了解 Link State Updates in a Coexistence Environment When connecting the Exchange 2010 routing group to the Exchange Server 2003 organization, you must consider the behavior of link state routing . Exchange Server 2003 servers maintain a link state routing table that is updated through communication with the Routing Group master. Each connector that has been created between Exchange Server 2003 routing groups is considered a link. Exchange Server 2003 servers determine how a message is routed inside the organization by using the cost that is assigned to these links. If a particular routing group is inaccessible by using the lowest cost route, the link state table is updated by the

  1. 重點就是不要用Exchange 2003 的管理介面來建立E14 & E2K3 間的RGC 2. 使用 New-RoutingGroupConnector 來建立RGC 3. 先去了解 抑制連結狀態更新 **(多個E2K3 routing group 與E14 的連接方式) If your existing Exchange environment includes more than one routing group, you may want to create additional connection points between Exchange 2003 and Exchange 2010 to optimize mail flow. To create additional connection points, you follow these steps: Determine how you will upgrade the organization to Exchange 2010. The order in which you decommission routing groups will determine which Exchange 2003 routing groups should connect directly with Exchange 2010. **Modify the registry to suppress minor link state updates on all the Exchange 2003 servers . This configuration change prevents connector state messages from being relayed throughout the organization by using link state updates, but does not prevent configuration change messages from being relayed. For more information, see Suppress Link State Up

  1. Site to Site 間的HUB傳輸是透過 intra-organization Send connector to route 2. 承上，base on Active Directory site and IP site link 3. 混合模式下，AG及RG 會自動建立 4. E14 的AG & RG及成員不要亂動，更別透過ESM 來操作   Upgrading from Exchange 2003 Transport [This is pre-release documentation and subject to change in future releases. This topic's current status is: Editing .] Applies to: Exchange Server 2010 Topic Last Modified: 2009-08-19 When upgrading from Exchange 2003 to Exchange 2010, there will be a period of time where both versions coexist in production. This topic provides information to help you make sure that the message flow isn't negatively affected during this period of coexistence. Important: If you deploy Exchange 2010 as a new organization, you cannot later install Exchange 2003 in the Exchange 2010 organization. This is not a supported scenario. If you anticipate requiring Exchange 2003 func

  如何抑制連結狀態更新 Applies to: Exchange Server 2010 Topic Last Modified: 2009-05-01 當 Exchange 組織中的電腦上安裝第一個 Hub Transport server role 時會建立第一個路由群組連接器。在建立其他路由群組連接器之前，請先在組織中的每個 Exchange 2000 和 Exchange 2003 伺服器上執行此程序。 當您抑制少量連結狀態更新時，執行 Exchange 2000 和 Exchange 2003 的伺服器不會將連接器標示為關閉。此程序可確保舊版的 Exchange 只使用最低成本的路由，且不會嘗試計算替代路由。 此程序的目的是確保不會發生路由迴圈。Exchange 2007 不使用連結狀態路由表，也不支援轉送連結狀態資訊。如果不抑制少量連結狀態更新，則可能發生路由迴圈 。如需在包含 Exchange 2007 伺服器和 Exchange 2003 或 Exchange 2000 伺服器的 Exchange 組織中如何發生路由迴圈的相關資訊 This topic explains how to use Registry Editor to suppress propagation of minor link state updates between routing groups in Microsoft Exchange Server 2010 and Exchange Server 2003. We recommend that you perform this procedure if the following conditions are true: You have installed the Exchange 2010 Hub Transport server role in an existing Exchange 2003 organization. For more information about this step, see Installing Exchange 2010 in an Existing Exchange 2003 Organization . The ex

  Planning Roadmap for Upgrade and Coexistence - Exchange 2003   Applies to: Exchange Server 2010 Topic Last Modified: 2009-08-19 You can deploy Exchange 2010 in an existing Exchange Server 2003 organization that is operating in native mode. Coexistence with these two Exchange versions is supported. This topic provides an overview of the planning considerations and configuration steps that you must take when Exchange 2010 will coexist with Exchange Server 2003.   Existing Exchange Organization Planning Requirements Check Exchange Server 2003 servers must have a minimum version of Exchange Server 2003 SP2 installed. [F] At least one Windows Server 2003 Service Pack 2 (SP2) or later global catalog in each Active Directory site. [F]