Free Ping Tools, Ping IP Tools, Ping Software for Network Engineer - Colasoft: "-
已使用 Google 工具列寄出"
2010/10/28
You Had Me At EHLO... : Released: Update Rollup 2 for Exchange Server 2010
You Had Me At EHLO... : Released: Update Rollup 2 for Exchange Server 2010:
"KB 979431 When user migrated from Exchange Server 2003 to Exchange Server 2010, and that user connected via POP3, the POP3 service crashed. This was fixed up so it will not crash.
- 已使用 Google 工具列寄出"
"KB 979431 When user migrated from Exchange Server 2003 to Exchange Server 2010, and that user connected via POP3, the POP3 service crashed. This was fixed up so it will not crash.
- 已使用 Google 工具列寄出"
Moved (2003 to 2010) Users are getting” Receiving Reported error (0x800CCC0F)” while downloading emails using POP3
Moved (2003 to 2010) Users are getting” Receiving Reported error (0x800CCC0F)” while downloading emails using POP3: "- 已使用 Google 工具列寄出"
it's a BUG is exchange 2010 and expected to solve in RU2. meantime I was trying for any workaround by editing the AD attributes of the moved user and solve the issue.
it's a BUG is exchange 2010 and expected to solve in RU2. meantime I was trying for any workaround by editing the AD attributes of the moved user and solve the issue.
2010/10/21
RAID 6詳解
RAID 6詳解:
"RAID 6是由一些大型企業提出來的私有RAID級別標准，它的全稱叫“Independent Data disks with two independent distributed parity schemes（帶有兩個獨立分布式校驗方案的獨立數据磁盤）”。這种RAID級別是在RAID 5的基礎上發展而成，因此它的工作模式与RAID 5有异曲同工之妙，不同的是RAID 5將校驗碼寫入到一個驅動器里面，而RAID 6將校驗碼寫入到兩個驅動器里面，這樣就增強了磁盤的容錯能力，同時RAID 6陣列中允許出現故障的磁盤也就達到了兩個，但相應的陣列磁盤數量最少也要4個。
下圖是RAID 6的圖解。
RAID6圖解
從圖中我們可以看到每個磁盤中都具有兩個校驗值，而RAID 5里面只能為每一個磁盤提供一個校驗值，由于校驗值的使用可以達到恢复數据的目的，因此多增加一位校驗位☆禤⑺炴奈的能力就越強。不過在增加一位校驗位后，就需要一個比較复雜的控制器來進行控制，同時也使磁盤的寫能力降低，并且還需要占用一定的磁盤空間。因此，這种RAID級別應用還比較少，相信隨著RAID 6技術的不斷完善，RAID 6將得到廣泛應用。RAID 6的磁盤數量為N+2個。
附件：
RAID6資料救援
- 已使用 Google 工具列寄出"
"RAID 6是由一些大型企業提出來的私有RAID級別標准，它的全稱叫“Independent Data disks with two independent distributed parity schemes（帶有兩個獨立分布式校驗方案的獨立數据磁盤）”。這种RAID級別是在RAID 5的基礎上發展而成，因此它的工作模式与RAID 5有异曲同工之妙，不同的是RAID 5將校驗碼寫入到一個驅動器里面，而RAID 6將校驗碼寫入到兩個驅動器里面，這樣就增強了磁盤的容錯能力，同時RAID 6陣列中允許出現故障的磁盤也就達到了兩個，但相應的陣列磁盤數量最少也要4個。
下圖是RAID 6的圖解。
RAID6圖解
從圖中我們可以看到每個磁盤中都具有兩個校驗值，而RAID 5里面只能為每一個磁盤提供一個校驗值，由于校驗值的使用可以達到恢复數据的目的，因此多增加一位校驗位☆禤⑺炴奈的能力就越強。不過在增加一位校驗位后，就需要一個比較复雜的控制器來進行控制，同時也使磁盤的寫能力降低，并且還需要占用一定的磁盤空間。因此，這种RAID級別應用還比較少，相信隨著RAID 6技術的不斷完善，RAID 6將得到廣泛應用。RAID 6的磁盤數量為N+2個。
附件：
RAID6資料救援
- 已使用 Google 工具列寄出"
Upgrade Default Address Lists from LDAP Filters to OPATH Filters: Exchange 2010 SP1 Help
Upgrade Default Address Lists from LDAP Filters to OPATH Filters: Exchange 2010 SP1 Help:
"Upgrade Default Address Lists from LDAP Filters to OPATH Filters
LDAP syntax filters are supported in Exchange 2010 and will exist only on objects that have been migrated from Exchange 2003 or earlier versions. You must upgrade these LDAP filters to the OPATH syntax only if you want to edit the filter from an Exchange 2010 server. For example, if you have Exchange 2003 servers in your organization, you can manage the LDAP syntax filter from an Exchange 2003 server. You can't manage or create LDAP syntax filters in Exchange 2010.
"Upgrade Default Address Lists from LDAP Filters to OPATH Filters
LDAP syntax filters are supported in Exchange 2010 and will exist only on objects that have been migrated from Exchange 2003 or earlier versions. You must upgrade these LDAP filters to the OPATH syntax only if you want to edit the filter from an Exchange 2010 server. For example, if you have Exchange 2003 servers in your organization, you can manage the LDAP syntax filter from an Exchange 2003 server. You can't manage or create LDAP syntax filters in Exchange 2010.
The following default address lists may need to be upgraded:
- All Users
- All Groups
- All Contacts
- Public Folders
- Default Global Address List
Set-AddressList "All Users" -IncludedRecipients MailboxUsers
Upgrade Custom LDAP Filters to OPATH Filters: Exchange 2010 SP1 Help
Upgrade Custom LDAP Filters to OPATH Filters: Exchange 2010 SP1 Help:
Upgrade Custom LDAP Filters to OPATH Filters
set-addresslist
Upgrade Custom LDAP Filters to OPATH Filters
set-addresslist
2010/10/15
Cannot connect to Windows 2K3 server using Remote Desktop | 26 of 26
Cannot connect to Windows 2K3 server using Remote Desktop | 26 of 26:
"THIS IS THE FIX !!
The issue is with one of two things... most likely the latter. Either a security update that affects the files currently running in the process stack has been changed which means the server needs to be restarted OR...
Most likely, the port used to remote into your server has been changed... it's very common. Instead of 3389 for RDC, someone changed it and forgot. You can always load the registry hive for that server remotely (assuming you cannot easily access the console itself) and go to HKLM\SYSTEM\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp
You will see what port is being used to remote in. To connect to that port using Remote Desktop, simply add a colon followed by the new port number (no spaces). it will look something like mysvr1:3390
- 已使用 Google 工具列寄出"
"THIS IS THE FIX !!
The issue is with one of two things... most likely the latter. Either a security update that affects the files currently running in the process stack has been changed which means the server needs to be restarted OR...
Most likely, the port used to remote into your server has been changed... it's very common. Instead of 3389 for RDC, someone changed it and forgot. You can always load the registry hive for that server remotely (assuming you cannot easily access the console itself) and go to HKLM\SYSTEM\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp
You will see what port is being used to remote in. To connect to that port using Remote Desktop, simply add a colon followed by the new port number (no spaces). it will look something like mysvr1:3390
- 已使用 Google 工具列寄出"
2010/10/14
行動通訊標準HSDPA/UMTS/GPR等名詞解釋 - 3.5G無線網卡技術資料 - 悠活客棧 - Powered by Discuz!
行動通訊標準HSDPA/UMTS/GPR等名詞解釋 - 3.5G無線網卡技術資料 - 悠活客棧 - Powered by Discuz!: "行動通訊標準HSDPA/UMTS/GPR等名詞解釋
GPRS
GPRS是General Packet Radio Service 的縮寫，稱為整合封包無線電服務技術，是由歐洲電信標準協會 (European Telecommunications Standards Institute) 發展出來的通訊技術標準。
GPRS是跨入第三代行動通訊(3G)的重要技術。它強化了GSM的數據傳輸能力，以「封包交換」(packet switch)取代「電路交換」(circuit switch)，大幅提升傳輸速率，有效運用頻譜資源，讓更多人加入使用。當資料在GPRS系統傳送時，是被分成一連串小「封包」，而不是獨佔一整條「電路」來進行傳輸。因此可讓多人共享網路資源，充份利用有限頻寬。
GPRS為高速寬頻 (Broadband) 的無線行動通訊網路，可以降低阻塞與中斷情形的發生，不但比無線應用通訊協定 (WAP ) 的速度來的快，而且擁有良好語音品質，對於商務人士或經常需要利用大哥大上網的人士而言，是非常先進的服務。GPRS恆久連線、瞬間上網、高速傳輸、以量計費四大特點更符合通訊、資訊、多媒體三合一的消費趨勢。透過GPRS技術最高速率可達100K，而支援GPRS的手機只要一開機便已經連上網，GPRS的網路系統能充分利用網路資源，作最有效率的運用。
3G
3G是Third Generation的縮寫，稱為第三代行動電話，第三代行動電話車行速度時傳輸速率達144kbps、步行時384kbps、室內或固定時2Mbps，全球漫遊採單一家族式技術，使用二GH Z頻率，如果對照目前GSM第二代行動電話的傳輸速率僅9.6kbps，二點五代行動電話GPRS 的115kbps，可知在手機傳輸數據或上網將比GSM的手機上網更快。
WCDMA
WCDMA是Wideband Code Division Multiple Access的縮寫，稱為寬頻分工多重擷取系統，是第三代行動電話 (３G ) 系統的一種，由GSM網路核心發展出來系統,由於採用了5MHz的寬頻網路,跟現在一般所使用200KHz的窄頻GSM比較下，WCDMA的數據傳送的速度在室內可達每秒2Mbit。由此可以理解，將來藉由WCDMA進行上網、視訊會議、聽MP3或做語音傳送時，收訊將比現行系統更清晰。
UMTS
UMTS 是Universal Mobile Telecommunications System的縮寫，稱為通用移動通訊系統，是一種第三代（3G） 行動電話技術。它使用WCDMA作為底層標準，由 3GPP定型。UMTS有時也叫3GSM，強調結合了3G技術而且是GSM標準的後續標準。UMTS 封包交換系統是由 GPRS 系統所演進而來，故系統的架構頗為相像。
HSDPA
HSDPA是High Speed Downlink Packet Access的縮寫，稱為高速下行封包接入，是一種行動通訊協議，亦稱為3.5G(3½G)。該協議在WCDMA下行鏈路中提供封包數據業務，在一個5MHz載波上的傳輸速率可達8-10 Mbit/s（如採用MIMO技術，則可達20 Mbit/s）。在具體實現中，採用了自適應調變編碼（AMC）、多輸入多輸出（MIMO）、混合自動重傳請求（HARQ）、快速調度、快速小區選擇等技術。
資料來源：各電信公司、維基百科
- 已使用 Google 工具列寄出"
GPRS
GPRS是General Packet Radio Service 的縮寫，稱為整合封包無線電服務技術，是由歐洲電信標準協會 (European Telecommunications Standards Institute) 發展出來的通訊技術標準。
GPRS是跨入第三代行動通訊(3G)的重要技術。它強化了GSM的數據傳輸能力，以「封包交換」(packet switch)取代「電路交換」(circuit switch)，大幅提升傳輸速率，有效運用頻譜資源，讓更多人加入使用。當資料在GPRS系統傳送時，是被分成一連串小「封包」，而不是獨佔一整條「電路」來進行傳輸。因此可讓多人共享網路資源，充份利用有限頻寬。
GPRS為高速寬頻 (Broadband) 的無線行動通訊網路，可以降低阻塞與中斷情形的發生，不但比無線應用通訊協定 (WAP ) 的速度來的快，而且擁有良好語音品質，對於商務人士或經常需要利用大哥大上網的人士而言，是非常先進的服務。GPRS恆久連線、瞬間上網、高速傳輸、以量計費四大特點更符合通訊、資訊、多媒體三合一的消費趨勢。透過GPRS技術最高速率可達100K，而支援GPRS的手機只要一開機便已經連上網，GPRS的網路系統能充分利用網路資源，作最有效率的運用。
3G
3G是Third Generation的縮寫，稱為第三代行動電話，第三代行動電話車行速度時傳輸速率達144kbps、步行時384kbps、室內或固定時2Mbps，全球漫遊採單一家族式技術，使用二GH Z頻率，如果對照目前GSM第二代行動電話的傳輸速率僅9.6kbps，二點五代行動電話GPRS 的115kbps，可知在手機傳輸數據或上網將比GSM的手機上網更快。
WCDMA
WCDMA是Wideband Code Division Multiple Access的縮寫，稱為寬頻分工多重擷取系統，是第三代行動電話 (３G ) 系統的一種，由GSM網路核心發展出來系統,由於採用了5MHz的寬頻網路,跟現在一般所使用200KHz的窄頻GSM比較下，WCDMA的數據傳送的速度在室內可達每秒2Mbit。由此可以理解，將來藉由WCDMA進行上網、視訊會議、聽MP3或做語音傳送時，收訊將比現行系統更清晰。
UMTS
UMTS 是Universal Mobile Telecommunications System的縮寫，稱為通用移動通訊系統，是一種第三代（3G） 行動電話技術。它使用WCDMA作為底層標準，由 3GPP定型。UMTS有時也叫3GSM，強調結合了3G技術而且是GSM標準的後續標準。UMTS 封包交換系統是由 GPRS 系統所演進而來，故系統的架構頗為相像。
HSDPA
HSDPA是High Speed Downlink Packet Access的縮寫，稱為高速下行封包接入，是一種行動通訊協議，亦稱為3.5G(3½G)。該協議在WCDMA下行鏈路中提供封包數據業務，在一個5MHz載波上的傳輸速率可達8-10 Mbit/s（如採用MIMO技術，則可達20 Mbit/s）。在具體實現中，採用了自適應調變編碼（AMC）、多輸入多輸出（MIMO）、混合自動重傳請求（HARQ）、快速調度、快速小區選擇等技術。
資料來源：各電信公司、維基百科
- 已使用 Google 工具列寄出"
Cannot connect to Win2003 with Remote Desktop "Reason 516
Cannot connect to Win2003 with Remote Desktop "Reason 516:
"Resolution:
1) Click Start>Control Panel>Administrative Tools> Open Terminal Services COnfiguration
2) Click on 'Connections' right click on the existing RDP (Notice the red X on it) {Mine said it was disabled because of some many network changes. I tried re-enabling with no success}
3) Right click on the RDP connection in the right pane and select delete
4) Right click on the 'Connections' folder on the left and select 'Create New Connection' run through the wizard and viola it works again.
Thanks,
"Resolution:
1) Click Start>Control Panel>Administrative Tools> Open Terminal Services COnfiguration
2) Click on 'Connections' right click on the existing RDP (Notice the red X on it) {Mine said it was disabled because of some many network changes. I tried re-enabling with no success}
3) Right click on the RDP connection in the right pane and select delete
4) Right click on the 'Connections' folder on the left and select 'Create New Connection' run through the wizard and viola it works again.
Thanks,
信箱搬移失敗from ex 2003 to ex2010
從ex2003 搬到 ex2010,搬了15個小時，只搬了32%
在ex2010 移除移動要求，user回報 mail 無法使用,outlook 不能登入,owa不能用
exchange 2003 有 event 9660 1022 錯誤
解決方式：將 exchange 2003 mailbox store dismount 再 remount 即可
在ex2010 移除移動要求，user回報 mail 無法使用,outlook 不能登入,owa不能用
exchange 2003 有 event 9660 1022 錯誤
解決方式：將 exchange 2003 mailbox store dismount 再 remount 即可
2010/10/12
Migrating Exchange 2007 ActiveSync to Exchange 2010. And why your Android may work but your Apple iphone / ipad may not. « Exchange for the Working Man
Migrating Exchange 2007 ActiveSync to Exchange 2010. And why your Android may work but your Apple iphone / ipad may not. « Exchange for the Working Man:
"When doing a migration from Exchange 2007 to Exchange 2010, one of the biggest item’s you need to watch out for is the migration of the ActiveSync environment, and be aware of how it can affect your end users. You should also be aware of potential issues depending on the TYPE of active sync device you are using, as some will work, and other’s will have issues.
- 已使用 Google 工具列寄出"
"When doing a migration from Exchange 2007 to Exchange 2010, one of the biggest item’s you need to watch out for is the migration of the ActiveSync environment, and be aware of how it can affect your end users. You should also be aware of potential issues depending on the TYPE of active sync device you are using, as some will work, and other’s will have issues.
- 已使用 Google 工具列寄出"
Migrating Exchange 2007 ActiveSync to Exchange 2010. And why your Android may work but your Apple iphone / ipad may not. « Exchange for the Working Man
Migrating Exchange 2007 ActiveSync to Exchange 2010. And why your Android may work but your Apple iphone / ipad may not. « Exchange for the Working Man:
"When doing a migration from Exchange 2007 to Exchange 2010, one of the biggest item’s you need to watch out for is the migration of the ActiveSync environment, and be aware of how it can affect your end users. You should also be aware of potential issues depending on the TYPE of active sync device you are using, as some will work, and other’s will have issues.
- 已使用 Google 工具列寄出"
"When doing a migration from Exchange 2007 to Exchange 2010, one of the biggest item’s you need to watch out for is the migration of the ActiveSync environment, and be aware of how it can affect your end users. You should also be aware of potential issues depending on the TYPE of active sync device you are using, as some will work, and other’s will have issues.
- 已使用 Google 工具列寄出"
You Had Me At EHLO... : Moving mailboxes, Exchange 2010 way
You Had Me At EHLO... : Moving mailboxes, Exchange 2010 way:
"Exchange Server 2007 used the Move-Mailbox cmdlet to move mailboxes between mailbox stores. Move-Mailbox makes a RPC connection to both the source and target mailbox databases and then starts the move process. Exchange Server 2010 uses the Mailbox Replication Service (MRS), a service that runs on all Exchange 2010 Client Access Servers, for mailbox move operations. MRS handles all mailbox moves including offline and online moves.
- 已使用 Google 工具列寄出"
"Exchange Server 2007 used the Move-Mailbox cmdlet to move mailboxes between mailbox stores. Move-Mailbox makes a RPC connection to both the source and target mailbox databases and then starts the move process. Exchange Server 2010 uses the Mailbox Replication Service (MRS), a service that runs on all Exchange 2010 Client Access Servers, for mailbox move operations. MRS handles all mailbox moves including offline and online moves.
- 已使用 Google 工具列寄出"
2010/10/07
Non working Search Service, Event ID 10039
Non working Search Service, Event ID 10039: "- 已使用 Google 工具列寄出"
事件類型: 警告
事件來源: Windows SharePoint Services 3 Search
事件類別目錄: 搜尋服務
事件識別碼: 10039
日期: 2010/10/7
時間: 下午 02:50:04
使用者: N/A
電腦: ADSERVER
描述:
由於發生 存取被拒。 0x80070005 的錯誤，查詢機器 'ADSERVER' 的重新測試失敗。900 秒之後會再試一次。元件: d50334e7-91dd-41d4-9464-9e56def6192f
請在 http://go.microsoft.com/fwlink/events.asp 查看說明及支援中心，以取得其他資訊。
the solution for me was to change the web application pool from network service to a domain account.
事件類型: 警告
事件來源: Windows SharePoint Services 3 Search
事件類別目錄: 搜尋服務
事件識別碼: 10039
日期: 2010/10/7
時間: 下午 02:50:04
使用者: N/A
電腦: ADSERVER
描述:
由於發生 存取被拒。 0x80070005 的錯誤，查詢機器 'ADSERVER' 的重新測試失敗。900 秒之後會再試一次。元件: d50334e7-91dd-41d4-9464-9e56def6192f
請在 http://go.microsoft.com/fwlink/events.asp 查看說明及支援中心，以取得其他資訊。
the solution for me was to change the web application pool from network service to a domain account.
2010/10/06
You Had Me At EHLO... : Upgrading Exchange ActiveSync to Exchange 2010
You Had Me At EHLO... : Upgrading Exchange ActiveSync to Exchange 2010:
"What happens when the user's mailbox is moved to Exchange 2010?
For this scenario, the important thing to understand is how is the device currently configured? Either the device is utilizing the legacy.contoso.com namespace (due to Autodiscover during device setup or due to the redirect), or the device is utilizing the mail.contoso.com namespace (and thus CAS2010 is proxying to the legacy CAS or Exchange 2003 mailbox server).
For the Autodiscover-supported device scenario case:
1. User3's device is already configured to use the namespace legacy.contoso.com.
2. User3's device attempts to synchronize.
3. CAS2007 will authenticate the user and access Active Directory and retrieve the following information:
1. User's mailbox version
2. User's mailbox location (AD Site)
3. The EAS virtual directory ExternalURL of the Client Access Server(s) that matches the mailbox version, located within the mailbox's AD site
4. Since the user's mailbox version is now greater than the CAS2007 version, CAS2007 must either respond with a 403 or 451 response code. Since the ActiveSync protocol version of User3's device is 12.1 or later, the device supports Autodiscover. Therefore, CAS2007 will return a response (HTTP error code 451) indicating that the device should use mail.contoso.com namespace for all synchronization events.
5. The device updates its profile to use mail.contoso.com and attempts to synchronize with mail.contoso.com.
6. CAS2010 will authenticate the user and retrieve and render the mailbox data from the Exchange 2010 mailbox server and will provide the rendered data back to the device.
For the legacy device case:
1. User1's device is already configured to use the namespace mail.contoso.com.
2. User1's device attempts to synchronize.
3. CAS2010 will authenticate the user and access Active Directory and retrieve the following information:
1. User's mailbox version
2. User's mailbox location (AD Site)
3. The EAS virtual directory ExternalURL of the Client Access Server(s) that matches the mailbox version, located within the mailbox's AD site
4. The EAS virtual directory InternalURL of the Client Access Server(s) that matches the mailbox version, located within the mailbox's AD site
4. Because the device does not support Autodiscover (protocol version is less than 12.1), prior to the mailbox move, CAS2010 simply proxied the ActiveSync traffic to CAS2007. Now that the mailbox is moved, CAS2010 simply retrieves and renders the mailbox data from the Exchange 2010 mailbox server.
5. CAS2010 will expose the data to the end user.
- 已使用 Google 工具列寄出"
"What happens when the user's mailbox is moved to Exchange 2010?
For this scenario, the important thing to understand is how is the device currently configured? Either the device is utilizing the legacy.contoso.com namespace (due to Autodiscover during device setup or due to the redirect), or the device is utilizing the mail.contoso.com namespace (and thus CAS2010 is proxying to the legacy CAS or Exchange 2003 mailbox server).
For the Autodiscover-supported device scenario case:
1. User3's device is already configured to use the namespace legacy.contoso.com.
2. User3's device attempts to synchronize.
3. CAS2007 will authenticate the user and access Active Directory and retrieve the following information:
1. User's mailbox version
2. User's mailbox location (AD Site)
3. The EAS virtual directory ExternalURL of the Client Access Server(s) that matches the mailbox version, located within the mailbox's AD site
4. Since the user's mailbox version is now greater than the CAS2007 version, CAS2007 must either respond with a 403 or 451 response code. Since the ActiveSync protocol version of User3's device is 12.1 or later, the device supports Autodiscover. Therefore, CAS2007 will return a response (HTTP error code 451) indicating that the device should use mail.contoso.com namespace for all synchronization events.
5. The device updates its profile to use mail.contoso.com and attempts to synchronize with mail.contoso.com.
6. CAS2010 will authenticate the user and retrieve and render the mailbox data from the Exchange 2010 mailbox server and will provide the rendered data back to the device.
For the legacy device case:
1. User1's device is already configured to use the namespace mail.contoso.com.
2. User1's device attempts to synchronize.
3. CAS2010 will authenticate the user and access Active Directory and retrieve the following information:
1. User's mailbox version
2. User's mailbox location (AD Site)
3. The EAS virtual directory ExternalURL of the Client Access Server(s) that matches the mailbox version, located within the mailbox's AD site
4. The EAS virtual directory InternalURL of the Client Access Server(s) that matches the mailbox version, located within the mailbox's AD site
4. Because the device does not support Autodiscover (protocol version is less than 12.1), prior to the mailbox move, CAS2010 simply proxied the ActiveSync traffic to CAS2007. Now that the mailbox is moved, CAS2010 simply retrieves and renders the mailbox data from the Exchange 2010 mailbox server.
5. CAS2010 will expose the data to the end user.
- 已使用 Google 工具列寄出"
Understanding Proxying and Redirection: Exchange 2010 SP1 Help
Understanding Proxying and Redirection: Exchange 2010 SP1 Help:
測試 active sync
CAS 為 ex2010 + mb 為 ex2003 , mail box 在 2003
要在 exchange 2003 Microsoft-Server-ActiveSync virtual directory 設定 Integrated Windows authentication
"Users who have mailboxes on an Exchange 2003 server who try to use Exchange ActiveSync through an Exchange 2010 Client Access server will receive an error and be unable to synchronize unless Integrated Windows authentication is enabled on the Microsoft-Server-ActiveSync virtual directory on the Exchange 2003 server. Integrated Windows authentication enables the Exchange 2010 Client Access server and the Exchange 2003 back-end server to communicate.
- 已使用 Google 工具列寄出"
測試 active sync
CAS 為 ex2010 + mb 為 ex2003 , mail box 在 2003
要在 exchange 2003 Microsoft-Server-ActiveSync virtual directory 設定 Integrated Windows authentication
"Users who have mailboxes on an Exchange 2003 server who try to use Exchange ActiveSync through an Exchange 2010 Client Access server will receive an error and be unable to synchronize unless Integrated Windows authentication is enabled on the Microsoft-Server-ActiveSync virtual directory on the Exchange 2003 server. Integrated Windows authentication enables the Exchange 2010 Client Access server and the Exchange 2003 back-end server to communicate.
- 已使用 Google 工具列寄出"
2010/10/04
2010/10/01
Error message when you try to start Exchange Management Shell (EMS) or Exchange Management Console (EMC): "The WinRM client... cannot determine the content type of the HTTP response from the destination computer"
Error message when you try to start Exchange Management Shell (EMS) or Exchange Management Console (EMC): "The WinRM client... cannot determine the content type of the HTTP response from the destination computer":
"When you try to start Exchange Management Shell (EMS) or Exchange Management Console (EMC) on a computer that is running Microsoft Exchange Server 2010, you receive the following error message:
Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
"When you try to start Exchange Management Shell (EMS) or Exchange Management Console (EMC) on a computer that is running Microsoft Exchange Server 2010, you receive the following error message:
Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
2010/09/27
PeteNetLive - KB0000259 - Upgrade Exchange 2000 to Exchange 2003
PeteNetLive - KB0000259 - Upgrade Exchange 2000 to Exchange 2003:
Now wait! - Public folder replication takes ages! Wait at least a week (I'm not joking) then check the replication status of all the public folders you added replicas for above, to make sure they are in sync. Also during this time your Outlook 2000/2003 clients have a chance to connect, and get updated with the new location of their mailbox before you kill the old Exchange server.
Now wait! - Public folder replication takes ages! Wait at least a week (I'm not joking) then check the replication status of all the public folders you added replicas for above, to make sure they are in sync. Also during this time your Outlook 2000/2003 clients have a chance to connect, and get updated with the new location of their mailbox before you kill the old Exchange server.
2010/09/15
Troubleshooting Free/Busy Information for Outlook 2007: Exchange 2007 Help
Troubleshooting Free/Busy Information for Outlook 2007: Exchange 2007 Help: "#
In Outlook 2007, on the Tools menu, click Options, click the Other tab, and then click Advanced Options.
# On the Advanced Options page, select Enable logging (troubleshooting), and then click OK.
# Restart Outlook 2007, and then try to view free/busy information for another user.
# In Microsoft Windows, click Start, click Run, and then type %temp%.
# In Windows Explorer, open the olkdisc.log file and locate the files in the olkas directory.
# The information that is contained in this directory can frequently provide information about which service is not functioning correctly.
- 已使用 Google 工具列寄出"
In Outlook 2007, on the Tools menu, click Options, click the Other tab, and then click Advanced Options.
# On the Advanced Options page, select Enable logging (troubleshooting), and then click OK.
# Restart Outlook 2007, and then try to view free/busy information for another user.
# In Microsoft Windows, click Start, click Run, and then type %temp%.
# In Windows Explorer, open the olkdisc.log file and locate the files in the olkas directory.
# The information that is contained in this directory can frequently provide information about which service is not functioning correctly.
- 已使用 Google 工具列寄出"
2010/09/10
2010/09/09
AD RMS Firewall Considerations
AD RMS Firewall Considerations: "Port Exception Description
TCP 80
HTTP
TCP 443
HTTPS or SSL communication
- 已使用 Google 工具列寄出"
TCP 80
HTTP
TCP 443
HTTPS or SSL communication
- 已使用 Google 工具列寄出"
2010/09/07
如何同步Google Chrome瀏覽器書籤？
如何同步Google Chrome瀏覽器書籤？: "
其實，在Google瀏覽器內有內建類似Xmark一樣的「書籤同步功能」，它可以幫你同步書籤到你的Google Doc上面，除了可以在Google瀏覽器內讀取外，若人在其他電腦上臨時要查個書籤，登入Google文件中就可以查到書籤了，把書籤也雲端化，讓資料可以帶著跑，完全不煩惱。
其實，在Google瀏覽器內有內建類似Xmark一樣的「書籤同步功能」，它可以幫你同步書籤到你的Google Doc上面，除了可以在Google瀏覽器內讀取外，若人在其他電腦上臨時要查個書籤，登入Google文件中就可以查到書籤了，把書籤也雲端化，讓資料可以帶著跑，完全不煩惱。
2010/09/03
Office Communicator 2007 and Outlook 2007 Integration Errors « Inside OCS
Office Communicator 2007 and Outlook 2007 Integration Errors « Inside OCS: "- 已使用 Google 工具列寄出"
OC client 用戶錯誤訊息
OC client 用戶錯誤訊息
2010/09/02
Where does autocomplete gets stored in OWA? - Le Café Central de DeVa - Site Home - MSDN Blogs
Where does autocomplete gets stored in OWA? - Le Café Central de DeVa - Site Home - MSDN Blogs: "By default, the AutoComplete Cache list is saved in your mailbox. It is loaded when you click the New button to open a new message.
In order to proceed further i can suggest you the following two ways (non-programmatic options):
1. Delete an entry from the list using OWA
2. Delete the entire list using OWA
1. Delete an entry from the list using OWA:
To remove one entry of the list, highlight the name in the list (arrow up and arrow down allow you to highlight the name you want to remove, and press the Delete button on your keyboard).
2. Delete the entire list using OWA
To remove all entries in the list, you can log on to your mailbox using Outlook Web Access Light
Go to Options - Messaging - Under Email Name Resolution - Click “Clear Most Recent Recipients List”
Try this out and let me know whether this helps or not.
Deva
- 已使用 Google 工具列寄出"
In order to proceed further i can suggest you the following two ways (non-programmatic options):
1. Delete an entry from the list using OWA
2. Delete the entire list using OWA
1. Delete an entry from the list using OWA:
To remove one entry of the list, highlight the name in the list (arrow up and arrow down allow you to highlight the name you want to remove, and press the Delete button on your keyboard).
2. Delete the entire list using OWA
To remove all entries in the list, you can log on to your mailbox using Outlook Web Access Light
Go to Options - Messaging - Under Email Name Resolution - Click “Clear Most Recent Recipients List”
Try this out and let me know whether this helps or not.
Deva
- 已使用 Google 工具列寄出"
2010/09/01
You Had Me At EHLO... : Moving public folder replicas from Exchange 2000 to Exchange 2007
You Had Me At EHLO... : Moving public folder replicas from Exchange 2000 to Exchange 2007:
"Exchange 2003 and Exchange 2007 will not let you delete a database that still has data within, but Exchange 2000 will. The only way to tell that the database is empty is to use Exchange 2000's System Manager and inspect the Public Folder Instances node under the public folder database object itself. When the right-hand side of the window lists no folders present (occasionally hit F5 to refresh), the database is empty and it's safe to remove it.
"Exchange 2003 and Exchange 2007 will not let you delete a database that still has data within, but Exchange 2000 will. The only way to tell that the database is empty is to use Exchange 2000's System Manager and inspect the Public Folder Instances node under the public folder database object itself. When the right-hand side of the window lists no folders present (occasionally hit F5 to refresh), the database is empty and it's safe to remove it.
2010/08/30
2010/08/27
RE: Exchange Server Reported Error (0x8004010F)
RE: Exchange Server Reported Error (0x8004010F): "This worked for me:
One of my Outlook users had the same error 0x8004010F when synchronizing his mailbox.
The solution was:
1) Remove the checkmark from 'Download Offline Address Book' (OAB) in Send/rec. settings.
2) Download OAB from Send/receive menu.
3) Sync. w/ F9
4) Set the checkmark in 1)
5) Sunc. w/ F9
Done !
- 已使用 Google 工具列寄出"
One of my Outlook users had the same error 0x8004010F when synchronizing his mailbox.
The solution was:
1) Remove the checkmark from 'Download Offline Address Book' (OAB) in Send/rec. settings.
2) Download OAB from Send/receive menu.
3) Sync. w/ F9
4) Set the checkmark in 1)
5) Sunc. w/ F9
Done !
- 已使用 Google 工具列寄出"
You Had Me At EHLO... : Transitioning Client Access to Exchange Server 2010
You Had Me At EHLO... : Transitioning Client Access to Exchange Server 2010: "# To add CAS2010 as a web distribution point:
* $OABVDir=Get-OABVirtualDirectory -Server
* $OAB=Get-OfflineAddressBook 'Default Offline Address List'
* $OAB.VirtualDirectories += $OABVdir.DistinguishedName
* Set-OfflineAddressBook 'Default Offline Address List' -VirtualDirectories $OAB.VirtualDirectories
- 已使用 Google 工具列寄出"
* $OABVDir=Get-OABVirtualDirectory -Server
* $OAB=Get-OfflineAddressBook 'Default Offline Address List'
* $OAB.VirtualDirectories += $OABVdir.DistinguishedName
* Set-OfflineAddressBook 'Default Offline Address List' -VirtualDirectories $OAB.VirtualDirectories
- 已使用 Google 工具列寄出"
Parative - Offering Migration management, infrastructure services, quest preferred partners using Quest software, Microsoft IO, Virtualization and Training - Parative
Parative - Offering Migration management, infrastructure services, quest preferred partners using Quest software, Microsoft IO, Virtualization and Training - Parative: "- 已使用 Google 工具列寄出"
2010/08/26
RAID
JBOD (Just Bunch of Disks)
這種組成方式嚴格來說不算RAID，因為它的功能就跟它的全名一樣，「只是將多顆磁碟湊在一起」， 當作一顆超大硬碟來用。假設是4顆250GB的大硬碟，在JBOD模式下就成了一顆1TB﹙=1000GB﹚的超高容量硬碟，但是除了容量提升之外，它的 速度還是跟單一硬碟相同，也沒有額外的安全性。RAID 0 (Striped)
這是最簡單也最猛的一種磁碟陣列，它的功能是在資料寫入時，將資料分割成幾個小區塊，分別存到各顆硬碟裡，因此可以提升寫入速度。當需要讀取時，再分別由所有硬碟裡將小區塊抓出來，所以也有較高的讀取速度。但它的缺點是只要其中一顆硬碟壞掉，或只是小小的出點問題，都可能因為一小部分資料的不完整，就造成整個磁碟陣列無法正常讀取，全部的資料就這樣毀 於一旦，完全沒有安全性可言。儘管如此，RAID 0存取效能隨著組成硬碟數目增加而提升的特性，對於「效能至上」的玩家們還是有不小的吸引力。
2010/08/25
2010/08/24
Configure Shadow Redundancy: Exchange 2010 Help
Configure Shadow Redundancy: Exchange 2010 Help:
"Set-TransportConfig -ShadowRedundancyEnabled $true
- 已使用 Google 工具列寄出"
"Set-TransportConfig -ShadowRedundancyEnabled $true
- 已使用 Google 工具列寄出"
RPC Server is Unavailable Error
RPC Server is Unavailable Error:
"Fix “RPC Server is Unavailable” Error in Windows Server 2008 R2 Remote Disk Management
- 已使用 Google 工具列寄出"
"Fix “RPC Server is Unavailable” Error in Windows Server 2008 R2 Remote Disk Management
- 已使用 Google 工具列寄出"
Windows Remote Management with Server 2008 R2
Windows Remote Management with Server 2008 R2: "- 已使用 Google 工具列寄出"
Enabling Remote Management in Windows Server 2008 R2
Enabling Remote Management in Windows Server 2008 R2
2010/08/23
Overview of Exchange Management Shell: Exchange 2010 Help
Overview of Exchange Management Shell: Exchange 2010 Help:
"In Exchange 2010, when you click the Shell shortcut, Windows PowerShell opens. Unlike in Exchange 2007, a Windows PowerShell snap-in for Exchange isn't loaded. Instead, Windows PowerShell connects to the closest Exchange 2010 server using a new required component called Windows Remote Management 2.0, performs authentication checks, and then creates a remote session for you to use. When the remote session is created, you're given access only to the cmdlets and the parameters associated with the management roles you've been assigned. For more information about management roles, see Understanding Role Based Access Control.
- 已使用 Google 工具列寄出"
"In Exchange 2010, when you click the Shell shortcut, Windows PowerShell opens. Unlike in Exchange 2007, a Windows PowerShell snap-in for Exchange isn't loaded. Instead, Windows PowerShell connects to the closest Exchange 2010 server using a new required component called Windows Remote Management 2.0, performs authentication checks, and then creates a remote session for you to use. When the remote session is created, you're given access only to the cmdlets and the parameters associated with the management roles you've been assigned. For more information about management roles, see Understanding Role Based Access Control.
- 已使用 Google 工具列寄出"
EMC 2010 failed with getting CAS configuration Event ID 4 ( Access denied ) « All about Microsoft Exchange
EMC 2010 failed with getting CAS configuration Event ID 4 ( Access denied ) « All about Microsoft Exchange: "At this step it was clear that the failure is due to inability of the Exchange 2010 EMC to query the OWA virtual directory of the old – 2007 – Exchange server due to lack of permission so the solution was to add “Exchange Trusted Subsystem” group to the local admins of all Exchange 2007 servers . If Exchange 2007 is on a domain controller , as in my case – only for test purposes - adding this group to the domain “Administrators” group solve the problem. For me every thing now is working as it should.
- 已使用 Google 工具列寄出"
- 已使用 Google 工具列寄出"
2010/08/20
Error 0x80190194 when using an Outlook 2007 client to download a Web Distribution enabled OAB - Dgoldman's WebLog - Site Home - MSDN Blogs
Error 0x80190194 when using an Outlook 2007 client to download a Web Distribution enabled OAB - Dgoldman's WebLog - Site Home - MSDN Blogs:
"Error 0x80190194 when using an Outlook 2007 client to download a Web Distribution enabled OAB
- 已使用 Google 工具列寄出"
"Error 0x80190194 when using an Outlook 2007 client to download a Web Distribution enabled OAB
- 已使用 Google 工具列寄出"
2010/08/18
2010/08/13
2010/08/10
Event id 9359 is generated after OAB update process is completed
Event id 9359 is generated after OAB update process is completed: "- 已使用 Google 工具列寄出"
OAB event 9359
OAB event 9359
2010/08/06
windows 7 顯示異常 ( 來吧~~~電腦 - 社群文章 )
windows 7 顯示異常 ( 來吧~~~電腦 - 社群文章 ):
out of range
真是太厲害了
搞了一個下午
3C這麼難搞，這篇文章救了我，感恩。
LCD接上NB,解析度調為 1600*1200 就回不來了，用了很多方式都不ok
只要LCD接上NB-就直接顯示到LCD,
最後利用ultraVNC修正回來。按
out of range
真是太厲害了
搞了一個下午
3C這麼難搞，這篇文章救了我，感恩。
LCD接上NB,解析度調為 1600*1200 就回不來了，用了很多方式都不ok
只要LCD接上NB-就直接顯示到LCD,
最後利用ultraVNC修正回來。按
2010/08/04
Blank email messages in Microsoft Outlook 2007 | Beyond Tecknology
Blank email messages in Microsoft Outlook 2007 | Beyond Tecknology: "- 已使用 Google 工具列寄出"
outlook 2007 看不見郵件本文
跟防毒軟體有關
本例為nod32
outlook 2007 看不見郵件本文
跟防毒軟體有關
本例為nod32
2010/08/03
允許接收連接器上的匿名轉送: Exchange 2010 說明
允許接收連接器上的匿名轉送: Exchange 2010 說明: "- 已使用 Google 工具列寄出"
exchange 2010 relay
請執行下列其中一個步驟：
在執行窗格中，按一下 [新增接收連接器]。[新增接收連接器] 嚮導便會啟動。
在 [簡介] 頁面上，執行下列步驟：
在 [區域網路設定] 頁面上，遵循下列步驟：
在 [遠端網路設定] 頁面上，執行下列步驟：
在 [新增連接器] 頁面上，檢閱連接器的組態摘要。若要修改設定，請按 [上一步]。若要使用組態摘要中的設定來建立接收連接器，請按一下 [新增]。
在 [完成] 頁面上，按一下 [完成]。
在工作窗格中，選取您建立的接收連接器。
在執行窗格的接收連接器名稱下按一下 [內容]，開啟 [內容] 頁面。
按一下 [權限群組] 索引標籤。選取 [匿名使用者]。
按一下 [確定] 儲存變更，並結束 [內容] 頁面。
最後還要加上這一行指令
exchange 2010 relay
- 若要在已安裝邊際傳輸伺服器角色的電腦上建立接收連接器，請選取 [邊際傳輸]，然後在工作窗格中按一下 [接收連接器] 索引標籤。
- 若要在集線傳輸伺服器角色上建立接收連接器，請在主控台樹狀目錄中，展開 [伺服器組態]，並選取 [集線傳輸]。在結果窗格中，選取要建立連接器的伺服器，然後按一下 [接收連接器] 索引標籤。
- 在 [名稱] 欄位中，為這個連接器輸入一個有意義的名稱。此名稱是用來識別連接器。
- 在 [選取此接收連接器的用途] 欄位中，選取 [自訂]。
- 按 [下一步]。
- 選取現有的 [所有可用的 IPv4] 項目，然後按一下
。
- 按一下 [新增]。在 [新增接收連接器繫結] 對話方塊中，選取 [指定 IP 位址]。輸入指派給本機伺服器之網路介面卡的 IP 位址，以便與遠端訊息伺服器進行最佳的通訊。在 [通訊埠] 欄位中，輸入 25，然後按一下 [確定]。將 [指定此連接器為了回應 HELO 或 EHLO 所將提供的 FQDN] 欄位保留空白。
- 按 [下一步]。
- 選取現有的 [0.0.0.0 - 255.255.255.255] 項目，然後按一下
- 按一下 [新增] 或 [新增] 旁邊的下拉箭頭，然後輸入可轉送此伺服器之郵件的遠端郵件伺服器的 IP 位址或 IP 位址範圍。輸入完 IP 位址後，請按一下 [確定]。
- 按 [下一步]。
最後還要加上這一行指令
Get-ReceiveConnector "Anonymous Relay" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"
2010/08/02
2010/07/30
Changes in Outlook 2010 (英文)
Changes in Outlook 2010 (英文):
新功能：good
"Multiple Exchange accounts
Outlook 2010 can connect to multiple Exchange accounts at the same time. The Exchange accounts can be in the same or different domains or servers.
- 已使用 Google 工具列寄出"
新功能：good
"Multiple Exchange accounts
Outlook 2010 can connect to multiple Exchange accounts at the same time. The Exchange accounts can be in the same or different domains or servers.
- 已使用 Google 工具列寄出"
Changes in Outlook 2010 (英文)
Changes in Outlook 2010 (英文):
outlook 2010 才有的功能嗎？
"Calendar Preview in meeting requests
Microsoft Outlook shows a preview of your calendar in meeting requests. The Calendar Preview feature shows where the meeting appears in your Calendar together with any conflicting and adjacent meetings. When you view a meeting request for a recurring meeting, you can use the Calendar Preview feature to navigate between meeting instances in the series.
- 已使用 Google 工具列寄出"
outlook 2010 才有的功能嗎？
"Calendar Preview in meeting requests
Microsoft Outlook shows a preview of your calendar in meeting requests. The Calendar Preview feature shows where the meeting appears in your Calendar together with any conflicting and adjacent meetings. When you view a meeting request for a recurring meeting, you can use the Calendar Preview feature to navigate between meeting instances in the series.
- 已使用 Google 工具列寄出"
Outlook 2007: Working With Resource Calendars | IS&T
Outlook 2007: Working With Resource Calendars | IS&T: "- 已使用 Google 工具列寄出"
Resources are anything other than people which can be scheduled. Resources are generally rooms or equipment, but special types of resources can be created, such as a group-wide vacation calendar or other scheduling calendar.
Resources are anything other than people which can be scheduled. Resources are generally rooms or equipment, but special types of resources can be created, such as a group-wide vacation calendar or other scheduling calendar.
2010/07/27
Event ID 11 — Service Principal Name Configuration
Event ID 11 — Service Principal Name Configuration: "To identify the duplicate SPN:
1. Log on to the computer referenced in the event log message. If this computer is not running Windows Server 2008, you must download and install the Windows Server 2003 Resource Kit, which includes setspn.exe.
2. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
4. Type setspn -X.
5. The output of this command will show the duplicate SPNs.
6. Use the following procedure to remove one of the duplicate SPNs.
- 已使用 Google 工具列寄出"
1. Log on to the computer referenced in the event log message. If this computer is not running Windows Server 2008, you must download and install the Windows Server 2003 Resource Kit, which includes setspn.exe.
2. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
4. Type setspn -X.
5. The output of this command will show the duplicate SPNs.
6. Use the following procedure to remove one of the duplicate SPNs.
- 已使用 Google 工具列寄出"
IT-Pro Knowledge: Error: Communicator could not retrieve calendar
出"
Communicator could not retrieve calendar or Out of Office information from Exchange Web Services. Communicator will automatically continue to retry. If this problem persists, contact your system administrator.
2010/07/26
Migraton from Exchange 2007 > 2010 IIS issue
Migraton from Exchange 2007 > 2010 IIS issue: "- 已使用 Google 工具列寄出"
You cannot manage OWA, ActiveSync, ECP, or OAB virtual directories from Exchange Management Console in Exchange Server 2010
You cannot manage OWA, ActiveSync, ECP, or OAB virtual directories from Exchange Management Console in Exchange Server 2010: "- 已使用 Google 工具列寄出"
exchange 2010 RPC server is unavailable get-owavirtualdirectory
exchange 2010 RPC server is unavailable get-owavirtualdirectory
2010/07/24
2010/07/23
Tomek's DS World : "Access denied" while promoting RODC in a domain
Tomek's DS World : "Access denied" while promoting RODC in a domain: "Two of these new One of entries being added is grant of 'Replicate Directory Changes' right for 'Enterprise Read-Only Domain Controller' (ERODC) group .
- 已使用 Google 工具列寄出"
Two of these new One of entries being added is grant of "Replicate Directory Changes" right for "Enterprise Read-Only Domain Controller" (ERODC) group .
event 1168
- 已使用 Google 工具列寄出"
Two of these new One of entries being added is grant of "Replicate Directory Changes" right for "Enterprise Read-Only Domain Controller" (ERODC) group .
event 1168
Tomek's DS World : "Access denied" while promoting RODC in a domain
Tomek's DS World : "Access denied" while promoting RODC in a domain: "- 已使用 Google 工具列寄出"
RODC event 1168
windows server 2008
RODC event 1168
windows server 2008
Exchange Server 2007 Deployment: 10 Tips When Installing
Exchange Server 2007 Deployment: 10 Tips When Installing: "In a coexistence scenario with Exchange 2007 and either Exchange 2003 or Exchange 2000, make sure your routing group connectors are configured correctly. By default, when you install the first Exchange 2007 Hub Transport server in an existing Exchange 2003 or Exchange 2000 organization, Setup creates a new routing group for all Exchange 2007 servers and requires you to specify an Exchange 2003 or Exchange 2000 bridgehead server to which it will connect the new Exchange 2007 routing group. By default, the Exchange 2007 routing group that is created is called the Exchange Routing Group (DWBGZMFD01QNBJR), and must not be renamed. Setup creates two reciprocal routing group connectors between the specified bridgehead server and the Hub Transport server that you are installing.
By default, you now have one Exchange 2007 routing group and two reciprocal routing group connectors between the first Hub Transport server that you installed and one bridgehead Exchange 2003 or Exchange 2000 server. You may want to consider creating additional routing group connectors. For redundancy, it is a good idea to connect additional Hub Transport servers in your Exchange 2007 routing group to the bridgehead servers in your Exchange 2003 or Exchange 2000 routing group. If your existing Exchange 2003 or Exchange 2000 organization had more than one routing group, you may want to consider installing the first Hub Transport server in the 'hub' Exchange 2003 or Exchange 2000 site. As you add more Hub Transport servers to different sites, you may want to create routing group connectors between these Hub Transport servers and the existing routing groups in other sites as well. This provides for a logical mail route between Exchange 2007 servers and legacy servers in different sites.
When Setup creates the initial routing group connector between the first Hub Transport server and the specified legacy bridgehead server, that legacy bridgehead server is automatically added to a universal security group (USG) called ExchangeLegacyInterop. Members of this USG have the permissions required to send e-mail to and receive e-mail from Exchange 2007. If you create additional routing group connectors between the Exchange 2007 routing group and routing groups from your existing Exchange 2003 or Exchange 2000 organization, you must use the New-RoutingGroupConnector cmdlet in the Exchange Management Shell. If you use this cmdlet, the Exchange 2003 or Exchange 2000 bridgehead server to which you connect will also be added to the ExchangeLegacyInterop.
- 已使用 Google 工具列寄出"
By default, you now have one Exchange 2007 routing group and two reciprocal routing group connectors between the first Hub Transport server that you installed and one bridgehead Exchange 2003 or Exchange 2000 server. You may want to consider creating additional routing group connectors. For redundancy, it is a good idea to connect additional Hub Transport servers in your Exchange 2007 routing group to the bridgehead servers in your Exchange 2003 or Exchange 2000 routing group. If your existing Exchange 2003 or Exchange 2000 organization had more than one routing group, you may want to consider installing the first Hub Transport server in the 'hub' Exchange 2003 or Exchange 2000 site. As you add more Hub Transport servers to different sites, you may want to create routing group connectors between these Hub Transport servers and the existing routing groups in other sites as well. This provides for a logical mail route between Exchange 2007 servers and legacy servers in different sites.
When Setup creates the initial routing group connector between the first Hub Transport server and the specified legacy bridgehead server, that legacy bridgehead server is automatically added to a universal security group (USG) called ExchangeLegacyInterop. Members of this USG have the permissions required to send e-mail to and receive e-mail from Exchange 2007. If you create additional routing group connectors between the Exchange 2007 routing group and routing groups from your existing Exchange 2003 or Exchange 2000 organization, you must use the New-RoutingGroupConnector cmdlet in the Exchange Management Shell. If you use this cmdlet, the Exchange 2003 or Exchange 2000 bridgehead server to which you connect will also be added to the ExchangeLegacyInterop.
- 已使用 Google 工具列寄出"
2010/07/21
You Had Me At EHLO... : Exchange, meet ExFolders
You Had Me At EHLO... : Exchange, meet ExFolders: "- 已使用 Google 工具列寄出"\
ExFolders must be run from an Exchange 2010 server - it cannot be run from a workstation as PFDAVAdmin could. It can connect to Exchange 2010 or Exchange 2007, but not older versions.
ExFolders must be run from an Exchange 2010 server - it cannot be run from a workstation as PFDAVAdmin could. It can connect to Exchange 2010 or Exchange 2007, but not older versions.
Microsoft Exchange Server Public Folder DAV-based Administration (PFDAVAdmin) Tool
Microsoft Exchange Server Public Folder DAV-based Administration (PFDAVAdmin) Tool:
"PFDAVAdmin still cannot connect to Exchange 2010 servers, because WebDAV is gone from 2010. If you need similar functionality for Exchange 2010, use ExFolders instead,” Microsoft.
- 已使用 Google 工具列寄出"
"PFDAVAdmin still cannot connect to Exchange 2010 servers, because WebDAV is gone from 2010. If you need similar functionality for Exchange 2010, use ExFolders instead,” Microsoft.
- 已使用 Google 工具列寄出"
訂閱：
文章 (Atom)