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.
訂閱：
文章 (Atom)