2010/12/31
Downloads | Remote Administration For Windows
Downloads | Remote Administration For Windows: "- 已使用 Google 工具列寄出"
A Networker's Log File: Migrating KMS Host for Windows Activation
A Networker's Log File: Migrating KMS Host for Windows Activation: "
Two types of activation for Microsoft OS, MAK (Multiple Activation Key) and KMS (Key Management Service). The former activation is mainly used for less than 5 servers. If you use KMS, the first four hosts won't be activated until the fifth is activated. Earlier, we did a mistake of keying in the KMS host license key into some of our servers instead of the KMS client keys. As a result, multiple SRV of _VLMCS._tcp. appears on the DNS servers. Furthermore, the current KMS server is not supposed to have Internet access. Hence, we decided to migrate the KMS to another VM.
- 已使用 Google 工具列寄出"
Two types of activation for Microsoft OS, MAK (Multiple Activation Key) and KMS (Key Management Service). The former activation is mainly used for less than 5 servers. If you use KMS, the first four hosts won't be activated until the fifth is activated. Earlier, we did a mistake of keying in the KMS host license key into some of our servers instead of the KMS client keys. As a result, multiple SRV of _VLMCS._tcp. appears on the DNS servers. Furthermore, the current KMS server is not supposed to have Internet access. Hence, we decided to migrate the KMS to another VM.
- 已使用 Google 工具列寄出"
KMS Client Setup Keys
KMS Client Setup Keys:
"By default, the Windows 7 and Windows Server 2008 R2 operating systems use KMS for activation. In volume installations, the setup key is installed by default, which makes the system a KMS client. If you are converting a computer from a KMS host, MAK, or retail edition of Windows to a KMS client, install the applicable setup key (GVLK) from Table 9 using slmgr /ipk .
- 已使用 Google 工具列寄出"
"By default, the Windows 7 and Windows Server 2008 R2 operating systems use KMS for activation. In volume installations, the setup key is installed by default, which makes the system a KMS client. If you are converting a computer from a KMS host, MAK, or retail edition of Windows to a KMS client, install the applicable setup key (GVLK) from Table 9 using slmgr /ipk .
- 已使用 Google 工具列寄出"
KMS on Windows Server 2008 R2 (Network Steve Forum)
KMS on Windows Server 2008 R2 (Network Steve Forum): "KMS on Windows Server 2008 R2
- 已使用 Google 工具列寄出"
- 已使用 Google 工具列寄出"
Count KMS Activation (Network Steve Forum)
Count KMS Activation (Network Steve Forum): "- 已使用 Google 工具列寄出"
Configuring KMS Hosts
Configuring KMS Hosts:
Table 1 Slmgr.vbs Parameters
/sprt PortNumber
Sets the TCP communications port on a KMS host. Replace PortNumber with the TCP port number to use. The default setting is 1688.
/cdns
Disables automatic DNS publishing by a KMS host.
/sdns
Enables automatic DNS publishing by the KMS host.
/cpri
Lowers the priority of KMS host processes.
/spri
Sets the priority of KMS host processes to Normal.
/sai ActivationInterval
Changes how often a KMS client attempts to activate itself when it cannot find a KMS host. Replace ActivationInterval with a number of minutes. The default setting is 120.
/sri RenewalInterval
Changes how often a KMS client attempts to renew its activation by contacting a KMS host. Replace RenewalInterval with a number of minutes. The default setting is 10080 (7 days). This setting overrides the local KMS client settings.
/dli
Retrieves the current KMS activation count from the KMS host.
- 已使用 Google 工具列寄出"
Table 1 Slmgr.vbs Parameters
/sprt PortNumber
Sets the TCP communications port on a KMS host. Replace PortNumber with the TCP port number to use. The default setting is 1688.
/cdns
Disables automatic DNS publishing by a KMS host.
/sdns
Enables automatic DNS publishing by the KMS host.
/cpri
Lowers the priority of KMS host processes.
/spri
Sets the priority of KMS host processes to Normal.
/sai ActivationInterval
Changes how often a KMS client attempts to activate itself when it cannot find a KMS host. Replace ActivationInterval with a number of minutes. The default setting is 120.
/sri RenewalInterval
Changes how often a KMS client attempts to renew its activation by contacting a KMS host. Replace RenewalInterval with a number of minutes. The default setting is 10080 (7 days). This setting overrides the local KMS client settings.
/dli
Retrieves the current KMS activation count from the KMS host.
- 已使用 Google 工具列寄出"
Configuring KMS Clients
Configuring KMS Clients:
"Enable Auto-discovery for a KMS Client
By default, KMS clients automatically attempt to discover KMS hosts. Auto-discovery can be disabled by manually assigning a KMS host to a KMS client. This action also clears the KMS host name from the KMS client’s cache. If auto-discovery is disabled, it can be re-enable by running slmgr.vbs /ckms at a command prompt.
- 已使用 Google 工具列寄出"
"Enable Auto-discovery for a KMS Client
By default, KMS clients automatically attempt to discover KMS hosts. Auto-discovery can be disabled by manually assigning a KMS host to a KMS client. This action also clears the KMS host name from the KMS client’s cache. If auto-discovery is disabled, it can be re-enable by running slmgr.vbs /ckms at a command prompt.
- 已使用 Google 工具列寄出"
slmgr.vbs 完整用法 - 小胡's Blog - 漫步人生，总是舍不得，放不下，珍惜一切
slmgr.vbs 完整用法 - 小胡's Blog - 漫步人生，总是舍不得，放不下，珍惜一切: "Windows 软件授权管理工具(slmgr.vbs)完整用法
计算机名: 远程计算机的名称(默认为本地计算机)
用户: 远程计算机上具有所需特权的帐户
密码: 帐户的密码
可用选项:
-ipk
安装产品密钥(替换现有密钥)
-upk
卸载产品密钥
-ato
激活 Windows
-dli [激活 ID | All]
显示许可证信息(默认: 当前许可证)
-dlv [激活 ID | All]
显示详细的许可证信息(默认: 当前许可证)
-xpr
当前许可证状态的截止日期
- 已使用 Google 工具列寄出"
计算机名: 远程计算机的名称(默认为本地计算机)
用户: 远程计算机上具有所需特权的帐户
密码: 帐户的密码
可用选项:
-ipk
安装产品密钥(替换现有密钥)
-upk
卸载产品密钥
-ato
激活 Windows
-dli [激活 ID | All]
显示许可证信息(默认: 当前许可证)
-dlv [激活 ID | All]
显示详细的许可证信息(默认: 当前许可证)
-xpr
当前许可证状态的截止日期
- 已使用 Google 工具列寄出"
Moving KMS to a new box in Windows Server
Moving KMS to a new box in Windows Server: "
My understanding of KMS is that kms machines operate independently of each other, you are not moving it as such you just need to install a new machine. Clients find kms servers by querying dns and your new kms server will automatically publish its srv record. James. --
- 已使用 Google 工具列寄出"
My understanding of KMS is that kms machines operate independently of each other, you are not moving it as such you just need to install a new machine. Clients find kms servers by querying dns and your new kms server will automatically publish its srv record. James. --
- 已使用 Google 工具列寄出"
2010/12/30
Windows Server 2008 R2 maximum NTFS volume size - Operating Systems
Windows Server 2008 R2 maximum NTFS volume size - Operating Systems: "
For NTFS the default size of allocation units is 4096 bytes.
- 已使用 Google 工具列寄出"
For NTFS the default size of allocation units is 4096 bytes.
- 已使用 Google 工具列寄出"
sector size
記錄檔複製器無法繼續處理資料庫 ''，因為目標伺服器
發生錯誤: 連續複寫 - 已終止區塊模式。錯誤: the log file sector
size does not match the current volume's se
ctor size (-546) [HResult: 0x80131500].。複製器在
短暫延遲後將自動重試。
發生錯誤: 連續複寫 - 已終止區塊模式。錯誤: the log file sector
size does not match the current volume's se
ctor size (-546) [HResult: 0x80131500].。複製器在
短暫延遲後將自動重試。
How can I get the cluster size on Windows 2008? - Server Fault
How can I get the cluster size on Windows 2008? - Server Fault: "Use the following command:
fsutil fsinfo ntfsinfo c: (where c: is the volume/path to obtain the data for)
This will show you smilar to the following:
NTFS Volume Serial Number : 0x9e800d87800d675d
Version : 3.1
Number Sectors : 0x000000000c7fffff
Total Clusters : 0x00000000018fffff
Free Clusters : 0x000000000091cfd1
Total Reserved : 0x00000000000001b0
Bytes Per Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000009fc0000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000c7ffff
Mft Zone Start : 0x00000000000c9ca0
Mft Zone End : 0x00000000000ca7e0
RM Identifier: 07A1930B-353D-11DE-AB63-E15CC5EE82D6
- 已使用 Google 工具列寄出"
fsutil fsinfo ntfsinfo c: (where c: is the volume/path to obtain the data for)
This will show you smilar to the following:
NTFS Volume Serial Number : 0x9e800d87800d675d
Version : 3.1
Number Sectors : 0x000000000c7fffff
Total Clusters : 0x00000000018fffff
Free Clusters : 0x000000000091cfd1
Total Reserved : 0x00000000000001b0
Bytes Per Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000009fc0000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000c7ffff
Mft Zone Start : 0x00000000000c9ca0
Mft Zone End : 0x00000000000ca7e0
RM Identifier: 07A1930B-353D-11DE-AB63-E15CC5EE82D6
- 已使用 Google 工具列寄出"
2010/12/29
sending & receiving sms messages using outlook 2010 or outlook web app, and windows mobile - Ilse Van Criekinge's Weblog - Site Home - TechNet Blogs
sending & receiving sms messages using outlook 2010 or outlook web app, and windows mobile - Ilse Van Criekinge's Weblog - Site Home - TechNet Blogs: "How does it work?
When a text (sms) message is created using Outlook/OWA, it will be sent to Exchange. Exchange will use EAS to send/sync the message to the users cell phone. The user’s cell phone will then send that message out over SMS.
When a user receives a text message, the sent message will be synced to the user’s mailbox using EAS.
- 已使用 Google 工具列寄出"
When a text (sms) message is created using Outlook/OWA, it will be sent to Exchange. Exchange will use EAS to send/sync the message to the users cell phone. The user’s cell phone will then send that message out over SMS.
When a user receives a text message, the sent message will be synced to the user’s mailbox using EAS.
- 已使用 Google 工具列寄出"
Outlook 2010, Windows Mobile & SMS Sync: Send and receive text messages from your e-mail account - Le Café Central de DeVa - Site Home - MSDN Blogs
Outlook 2010, Windows Mobile & SMS Sync: Send and receive text messages from your e-mail account - Le Café Central de DeVa - Site Home - MSDN Blogs: "- 已使用 Google 工具列寄出"
sending & receiving sms messages using outlook 2010 or outlook web app, and windows mobile - Ilse Van Criekinge's Weblog - Site Home - TechNet Blogs
sending & receiving sms messages using outlook 2010 or outlook web app, and windows mobile - Ilse Van Criekinge's Weblog - Site Home - TechNet Blogs: "- 已使用 Google 工具列寄出"
A while ago I got a question from someone regarding one of the new features in Exchange 2010, being text messaging. Question was “is it available”…
Looking at the TechNet article he referred to, it does state:
Source = http://technet.microsoft.com/en-us/library/dd298136.aspx
The following is a list of new text messaging features included in Exchange 2010:
- Missed call and voice mail notifications
- Calendar and agenda updates
- Text messages sent and received through Outlook Web App and Outlook 2010
- Text message synchronization with a mobile phone
So let’s see.
Requirements
You need to have a Windows Mobile device:
- Windows Mobile 6.1 + https://update.outlook.com/cabs/OutlookLiveSetup.cab
- Windows Mobile 6.5
- Exchange 2010
Text Messages (SMS) Synching with Exchange 2010 and Rule to move Text Messages (SMS) to a folder using Outlook 2010 - AVIRAJ AJGEKAR'S BLOG... - Site Home - TechNet Blogs
Text Messages (SMS) Synching with Exchange 2010 and Rule to move Text Messages (SMS) to a folder using Outlook 2010 - AVIRAJ AJGEKAR'S BLOG... - Site Home - TechNet Blogs: "- 已使用 Google 工具列寄出"
How to send/receive SMS in MS Exchange 2010
How to send/receive SMS in MS Exchange 2010: "- 已使用 Google 工具列寄出"
2010/12/27
Error message when users use an SMTP client to send e-mail messages in Exchange Server 2007 Service Pack 1: "454 4.7.0 Temporary authentication failure"
Error message when users use an SMTP client to send e-mail messages in Exchange Server 2007 Service Pack 1: "454 4.7.0 Temporary authentication failure": "- 已使用 Google 工具列寄出"
Authentication Prob between 2 hub servers - cannot send/receive.
Authentication Prob between 2 hub servers - cannot send/receive.: "- 已使用 Google 工具列寄出"
"454 4.7.0 temporary authentication failure"
"454 4.7.0 temporary authentication failure"
2010/12/22
x64? My Terminal Servers Run Just Fine With 32 Bits and 8/12/16 GB RAM! | sepago
x64? My Terminal Servers Run Just Fine With 32 Bits and 8/12/16 GB RAM! | sepago: "x64? My Terminal Servers Run Just Fine With 32 Bits and 8/12/16 GB RAM!
PAE
Windows can be booted with the /PAE option. PAE makes the kernel use 4 additional address lines which are built into (nearly) every CPU since the Pentium Pro. Modern CPUs have 36 instead of 32 address lines and support a maximum of 64 GB RAM (with PAE enabled).
But how can a traditional 32-bit application that can only count to 2^32 and that knows nothing of AWE access such "high" memory?
Easy: all the hard work is done by the operating system. Remember that each application has its private virtual address space that always ranges from 0x00000000 to 0xFFFFFFFF. But programs cannot simply access any address in that range. Doing so would result in the well-known general protection fault. Instead applications must request memory from the OS. The OS then chooses the appropriate amount of free pages (RAM is managed in units of pages with a size of 4 KB each). Finally the pages are mapped from physical RAM into the virtual memory of the requesting process.
By virtualizing the address space of processes, it has become irrelevant to applications where a page actually is located. It could have been moved to disk (to the page file, of course) to make room for other process's demands. Or it could reside in the area above 4 GB. Since applications only work with virtual addresses in the 32-bit range they need not be modified as long as they use less than 2 GB of memory.
With PAE, multiple 32-bit processes without AWE support can still only use 2 GB each. But it is perfectly possible to have 20 applications on a terminal server that each need 300 MB RAM if the machine is equipped with 8 GB (leaving room for the kernel and OS). This is because the map from virtual to physical memory is different for every process.
PAE
Windows can be booted with the /PAE option. PAE makes the kernel use 4 additional address lines which are built into (nearly) every CPU since the Pentium Pro. Modern CPUs have 36 instead of 32 address lines and support a maximum of 64 GB RAM (with PAE enabled).
But how can a traditional 32-bit application that can only count to 2^32 and that knows nothing of AWE access such "high" memory?
Easy: all the hard work is done by the operating system. Remember that each application has its private virtual address space that always ranges from 0x00000000 to 0xFFFFFFFF. But programs cannot simply access any address in that range. Doing so would result in the well-known general protection fault. Instead applications must request memory from the OS. The OS then chooses the appropriate amount of free pages (RAM is managed in units of pages with a size of 4 KB each). Finally the pages are mapped from physical RAM into the virtual memory of the requesting process.
By virtualizing the address space of processes, it has become irrelevant to applications where a page actually is located. It could have been moved to disk (to the page file, of course) to make room for other process's demands. Or it could reside in the area above 4 GB. Since applications only work with virtual addresses in the 32-bit range they need not be modified as long as they use less than 2 GB of memory.
With PAE, multiple 32-bit processes without AWE support can still only use 2 GB each. But it is perfectly possible to have 20 applications on a terminal server that each need 300 MB RAM if the machine is equipped with 8 GB (leaving room for the kernel and OS). This is because the map from virtual to physical memory is different for every process.
Physical Address Extension (Windows)
Physical Address Extension (Windows): "Enabling PAE
Windows automatically enables PAE if DEP is enabled on a computer that supports hardware-enabled DEP, or if the computer is configured for hot-add memory devices in memory ranges beyond 4 GB. If the computer does not support hardware-enabled DEP or is not configured for hot-add memory devices in memory ranges beyond 4 GB, PAE must be explicitly enabled.
To explicitly enable PAE, use the following BCDEdit /set command to set the pae boot entry option:
bcdedit /set [{ID}] pae ForceEnable
IF DEP is enabled, PAE cannot be disabled. Use the following BCDEdit /set commands to disable both DEP and PAE:
bcdedit /set [{ID}] nx AlwaysOff
bcdedit /set [{ID}] pae ForceDisable
Windows Server 2003 and Windows XP/2000: To enable PAE, use the /PAE switch in the Boot.ini file. To disable PAE, use the /NOPAE switch. To disable DEP, use the /EXECUTE switch.
- 已使用 Google 工具列寄出"
Windows automatically enables PAE if DEP is enabled on a computer that supports hardware-enabled DEP, or if the computer is configured for hot-add memory devices in memory ranges beyond 4 GB. If the computer does not support hardware-enabled DEP or is not configured for hot-add memory devices in memory ranges beyond 4 GB, PAE must be explicitly enabled.
To explicitly enable PAE, use the following BCDEdit /set command to set the pae boot entry option:
bcdedit /set [{ID}] pae ForceEnable
IF DEP is enabled, PAE cannot be disabled. Use the following BCDEdit /set commands to disable both DEP and PAE:
bcdedit /set [{ID}] nx AlwaysOff
bcdedit /set [{ID}] pae ForceDisable
Windows Server 2003 and Windows XP/2000: To enable PAE, use the /PAE switch in the Boot.ini file. To disable PAE, use the /NOPAE switch. To disable DEP, use the /EXECUTE switch.
- 已使用 Google 工具列寄出"
2010/12/10
Exchange Server 2007 and Public Folder Replicas | Aaron Parker
Exchange Server 2007 and Public Folder Replicas | Aaron Parker: "In our case I missed the SCHEDULE+ FREE BUSY folder. This resulted in Outlook 2003 clients unable to see Free/Busy information when creating a meeting request. The user would see this error in Outlook when attempting to see another users schedule:
- 已使用 Google 工具列寄出"
- 已使用 Google 工具列寄出"
2010/12/06
2010/11/15
MSExchange Store Driver
MSExchange Store Driver: "- 已使用 Google 工具列寄出"
Event Type: Error
Event Source: MSExchange Store Driver
Event Category: MSExchangeStoreDriver
Event ID: 1020
Date: 2009-11-26
Time: 03:20:17
User: N/A
Computer: SE-EX003
Description:
The store driver couldn't deliver the public folder replication message "Status (MY-EX002-IS@logicacmg.com)" because the following error occurred: MapiExceptionDuplicateDelivery: Unable to deliver message. (hr=0x80004005, ec=2603)
Event Type: Error
Event Source: MSExchange Store Driver
Event Category: MSExchangeStoreDriver
Event ID: 1020
Date: 2009-11-26
Time: 03:20:17
User: N/A
Computer: SE-EX003
Description:
The store driver couldn't deliver the public folder replication message "Status (MY-EX002-IS@logicacmg.com)" because the following error occurred: MapiExceptionDuplicateDelivery: Unable to deliver message. (hr=0x80004005, ec=2603)
2010/11/12
Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster
Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster: "Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster
- 已使用 Google 工具列寄出"
- 已使用 Google 工具列寄出"
2010/11/09
Deploying High Availability and Site Resilience: Exchange 2010 Help
Deploying High Availability and Site Resilience: Exchange 2010 Help:
"Overview of the Deployment Process
While the actual steps used by each organization may vary slightly, the overall process for deploying Exchange 2010 in a highly available or site resilient configuration is generally the same. After performing the necessary planning and design tasks for building and deploying a database availability group (DAG) and creating mailbox database copies, you would:
1. Create a DAG. For detailed steps, see Create a Database Availability Group.
2. Add two or more Mailbox servers to the DAG. For detailed steps, see Manage Database Availability Group Membership.
3. Configure the DAG properties as needed:
1. Optionally configure DAG encryption and compression, replication port, DAG IP addresses, and other DAG properties. For detailed steps, see Configure Database Availability Group Properties.
2. If the DAG contains three or more Mailbox servers that are deployed in multiple Active Directory sites, Datacenter Activation Coordination (DAC) mode should be enabled. For more information, see Understanding Datacenter Activation Coordination Mode.
3. For detailed steps about how to create a DAG network, see Create a Database Availability Group Network. To manage a DAG network, see Configure Database Availability Group Network Properties.
4. Add mailbox database copies across Mailbox servers in the DAG. For detailed steps, see Add a Mailbox Database Copy.
- 已使用 Google 工具列寄出"
"Overview of the Deployment Process
While the actual steps used by each organization may vary slightly, the overall process for deploying Exchange 2010 in a highly available or site resilient configuration is generally the same. After performing the necessary planning and design tasks for building and deploying a database availability group (DAG) and creating mailbox database copies, you would:
1. Create a DAG. For detailed steps, see Create a Database Availability Group.
2. Add two or more Mailbox servers to the DAG. For detailed steps, see Manage Database Availability Group Membership.
3. Configure the DAG properties as needed:
1. Optionally configure DAG encryption and compression, replication port, DAG IP addresses, and other DAG properties. For detailed steps, see Configure Database Availability Group Properties.
2. If the DAG contains three or more Mailbox servers that are deployed in multiple Active Directory sites, Datacenter Activation Coordination (DAC) mode should be enabled. For more information, see Understanding Datacenter Activation Coordination Mode.
3. For detailed steps about how to create a DAG network, see Create a Database Availability Group Network. To manage a DAG network, see Configure Database Availability Group Network Properties.
4. Add mailbox database copies across Mailbox servers in the DAG. For detailed steps, see Add a Mailbox Database Copy.
- 已使用 Google 工具列寄出"
Database Availability Group Design Examples: Exchange 2010 Help
Database Availability Group Design Examples: Exchange 2010 Help: "
A two-member DAG is the smallest possible DAG that can provide high availability. Two-member DAGs are best suited for organizations that require some form of high availability for mailbox services and data, but that don't require site resilience. This configuration works especially well in small office and branch office deployments because it enables redundancy for the Client Access, Mailbox, and Hub Transport server roles using only two Exchange servers. The following figure illustrates this configuration.
Two-member database availability group
Two-Member Database Availability Group
- 已使用 Google 工具列寄出"
A two-member DAG is the smallest possible DAG that can provide high availability. Two-member DAGs are best suited for organizations that require some form of high availability for mailbox services and data, but that don't require site resilience. This configuration works especially well in small office and branch office deployments because it enables redundancy for the Client Access, Mailbox, and Hub Transport server roles using only two Exchange servers. The following figure illustrates this configuration.
Two-member database availability group
Two-Member Database Availability Group
- 已使用 Google 工具列寄出"
Create a Database Availability Group: Exchange 2010 Help
Create a Database Availability Group: Exchange 2010 Help: "- 已使用 Google 工具列寄出"
This example creates a DAG named DAG1 that is configured to use the witness server EXHUB1 and the local directory C:\DAG1. DAG1 is also configured to use DHCP for the DAG's IP addresses.
New-DatabaseAvailabilityGroup -Name DAG1 -WitnessServer EXHUB1 -WitnessDirectory C:\DAG1
2010/11/08
Outlook Connectivity Test
Outlook Connectivity Test: "
Test-OutlookWebServices
- 已使用 Google 工具列寄出"
Watson report about to be sent for process id: 6156, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, RemotePowershell, M.Exchange.Management, M.E.M.TestOutlookConnectivityTask.GetDefaultTestAccount, M.E.Monitoring.MailboxNotFoundException, 327c, 14.01.0218.013.
Failed to find the mailbox. Mailbox ='extest_95536ac1a0374@newvsi.local'.
Test-OutlookWebServices
- 已使用 Google 工具列寄出"
Watson report about to be sent for process id: 6156, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, RemotePowershell, M.Exchange.Management, M.E.M.TestOutlookConnectivityTask.GetDefaultTestAccount, M.E.Monitoring.MailboxNotFoundException, 327c, 14.01.0218.013.
Failed to find the mailbox. Mailbox ='extest_95536ac1a0374@newvsi.local'.
Diagnose Availability Service Issues: Exchange 2010 SP1 Help
Diagnose Availability Service Issues: Exchange 2010 SP1 Help:
"Test-OutlookWebServices -Identity: User1@Contoso.com
- 已使用 Google 工具列寄出"
"Test-OutlookWebServices -Identity: User1@Contoso.com
- 已使用 Google 工具列寄出"
Understanding the Availability Service: Exchange 2010 SP1 Help
Understanding the Availability Service: Exchange 2010 SP1 Help:
"You can use the Exchange Management Shell to configure the Availability service. You can't use the Exchange Management Console to configure the Availability service.
- 已使用 Google 工具列寄出"
"You can use the Exchange Management Shell to configure the Availability service. You can't use the Exchange Management Console to configure the Availability service.
- 已使用 Google 工具列寄出"
GALsync Special - Part 7:: Free Busy with Exchange 2010 - Tools for Exchange & Active Directory
GALsync Special - Part 7:: Free Busy with Exchange 2010 - Tools for Exchange & Active Directory:
"So all clients must be Outlook 2007 or Outlook 2010 to use availability service whcih collects free/busy information directly from mailbox stores.
- 已使用 Google 工具列寄出"
"So all clients must be Outlook 2007 or Outlook 2010 to use availability service whcih collects free/busy information directly from mailbox stores.
- 已使用 Google 工具列寄出"
2010/11/05
如何疑難排解 Exchange 2000 Server 和 Exchange Server 2003 中公用資料夾複寫的問題
如何疑難排解 Exchange 2000 Server 和 Exchange Server 2003 中公用資料夾複寫的問題:
"注意「複寫旗標」登錄值會造成每個公用資料夾均會產生複寫狀態訊息。在產生這些狀態要求訊息後的 6 到 12 小時之間，會針對未同步處理的公用資料夾複本啟動回填作業。有時回填處理程序可能要花 48 到 72 小時或更長的時間才能完成。「在啟動時啟用複寫郵件」登錄值會對公用資料夾階層執行相同的功能。然而，如果要在 Exchange 2000 Server 中設定公用資料夾內容狀態要求訊息的產生，必須設定這兩份「Microsoft 知識庫」文件中所述的登錄值，卸載，然後重新裝載公用資料夾儲存區。啟用公用資料夾內容複寫的狀態要求訊息的能力會先供 2003 年 9 月的 Exchange 2000 Server Post-Service Pack 3 Rollup 使用。
如果要設定公用資料夾複寫狀態要求訊息，請依照下列步驟執行：
1. 請執行「Microsoft 知識庫」文件 321082 中的步驟來設定沒有最新的公用資料夾階層資訊的 Exchange 2000 Server 電腦和 Exchange Server 2003 電腦上公用資料夾複寫狀態要求訊息的登錄值。
2. 卸載後再在設定此登錄機碼的各台 Exchange Server 電腦上重新裝載公用資料夾儲存區。如果要執行這項操作，請依照下列步驟執行：
1. 啟動 [Exchange 系統管理員]。
2. 依序展開 [伺服器]、您的 Exchange Server 電腦、包含要卸載的公用資料夾儲存區的儲存群組以及 [公用資料夾儲存區 (computername)]。
3. 用滑鼠右鍵按一下 [公用資料夾儲存區 (computername)]，然後按一下 [卸載儲存區]。
4. 當您收到下列訊息時，按一下 [是]：
卸載此儲存區會讓所有使用者均無法存取它。
要繼續？
5. 用滑鼠右鍵按一下 [公用資料夾儲存區 (computername)]，然後按一下 [裝載儲存區]。
6. 當您收到下列訊息時，按一下 [確定]：
儲存區已成功裝載。
3. 等候約 12 至 24 小時或更久，然後確認已將整個公用資料夾階層複寫到有此問題的電腦上。
重要您必須先確定已成功複寫公用資料夾階層，才能讓登錄機碼複寫公用資料夾內容。如果伺服器收到階層中不存在的公用資料夾的內容複寫郵件，便會捨棄內容複寫郵件。
4. 在成功複寫公用資料夾階層之後，請執行下列「Microsoft 知識庫」文件中的步驟來設定登錄機碼，以啟用公用資料夾內容複寫狀態訊息：
813629 (http://support.microsoft.com/kb/813629/ ) Update to send status request messages in Exchange 2000 Server
5. 公用資料夾內容複寫的完成時間比公用資料夾階層複寫更長。請等候至少 48 至 72 小時或更久，然後確認已複寫在該公用資料夾儲存區上有複本的所有公用資料夾的公用資料夾內容。
注意如果只要設定公用資料夾階層狀態要求訊息的產生，而不是公用資料夾的內容，則只要設定「Microsoft 知識庫」文件 321082 中所述的登錄機碼就足夠了。
然而，請確定階層中已成功複寫的所有資料夾均包含應有的所有的內容。如果在等候 48 到 72 小時或更長的時間之後，它們並未具備應有的所有內容，請設定「Microsoft 知識庫」文件 813629 中所述的登錄機碼。
- 已使用 Google 工具列寄出"
"注意「複寫旗標」登錄值會造成每個公用資料夾均會產生複寫狀態訊息。在產生這些狀態要求訊息後的 6 到 12 小時之間，會針對未同步處理的公用資料夾複本啟動回填作業。有時回填處理程序可能要花 48 到 72 小時或更長的時間才能完成。「在啟動時啟用複寫郵件」登錄值會對公用資料夾階層執行相同的功能。然而，如果要在 Exchange 2000 Server 中設定公用資料夾內容狀態要求訊息的產生，必須設定這兩份「Microsoft 知識庫」文件中所述的登錄值，卸載，然後重新裝載公用資料夾儲存區。啟用公用資料夾內容複寫的狀態要求訊息的能力會先供 2003 年 9 月的 Exchange 2000 Server Post-Service Pack 3 Rollup 使用。
如果要設定公用資料夾複寫狀態要求訊息，請依照下列步驟執行：
1. 請執行「Microsoft 知識庫」文件 321082 中的步驟來設定沒有最新的公用資料夾階層資訊的 Exchange 2000 Server 電腦和 Exchange Server 2003 電腦上公用資料夾複寫狀態要求訊息的登錄值。
2. 卸載後再在設定此登錄機碼的各台 Exchange Server 電腦上重新裝載公用資料夾儲存區。如果要執行這項操作，請依照下列步驟執行：
1. 啟動 [Exchange 系統管理員]。
2. 依序展開 [伺服器]、您的 Exchange Server 電腦、包含要卸載的公用資料夾儲存區的儲存群組以及 [公用資料夾儲存區 (computername)]。
3. 用滑鼠右鍵按一下 [公用資料夾儲存區 (computername)]，然後按一下 [卸載儲存區]。
4. 當您收到下列訊息時，按一下 [是]：
卸載此儲存區會讓所有使用者均無法存取它。
要繼續？
5. 用滑鼠右鍵按一下 [公用資料夾儲存區 (computername)]，然後按一下 [裝載儲存區]。
6. 當您收到下列訊息時，按一下 [確定]：
儲存區已成功裝載。
3. 等候約 12 至 24 小時或更久，然後確認已將整個公用資料夾階層複寫到有此問題的電腦上。
重要您必須先確定已成功複寫公用資料夾階層，才能讓登錄機碼複寫公用資料夾內容。如果伺服器收到階層中不存在的公用資料夾的內容複寫郵件，便會捨棄內容複寫郵件。
4. 在成功複寫公用資料夾階層之後，請執行下列「Microsoft 知識庫」文件中的步驟來設定登錄機碼，以啟用公用資料夾內容複寫狀態訊息：
813629 (http://support.microsoft.com/kb/813629/ ) Update to send status request messages in Exchange 2000 Server
5. 公用資料夾內容複寫的完成時間比公用資料夾階層複寫更長。請等候至少 48 至 72 小時或更久，然後確認已複寫在該公用資料夾儲存區上有複本的所有公用資料夾的公用資料夾內容。
注意如果只要設定公用資料夾階層狀態要求訊息的產生，而不是公用資料夾的內容，則只要設定「Microsoft 知識庫」文件 321082 中所述的登錄機碼就足夠了。
然而，請確定階層中已成功複寫的所有資料夾均包含應有的所有的內容。如果在等候 48 到 72 小時或更長的時間之後，它們並未具備應有的所有內容，請設定「Microsoft 知識庫」文件 813629 中所述的登錄機碼。
- 已使用 Google 工具列寄出"
XADM: How to Send Replication Status Request Messages in Exchange 2000 Server
XADM: How to Send Replication Status Request Messages in Exchange 2000 Server:
"In Microsoft Exchange Server 5.5, each computer that has a public folder store sends a nightly status request message to determine the state of the public folder hierarchy. Exchange 2000 Server does not do this. Typically, in Exchange 2000 the status request message is only sent out one time during the lifetime of the public folder store; it is sent when the store is created.
However, in certain circumstances you may have to generate a status request message. For example, if the public folder hierarchy on the Exchange 2000 computer does not seem to replicate, or the public folder hierarchy replicates very slowly, the generation of a status request message may permit the public folder hierarchy replication to continue. Issues with public folder hierarchy replication may occur if the original status request message that was sent when the public folder store was created was dropped and never acknowledged, or if the message was sent to a server with a substantially incomplete hierarchy.
A supported feature that modifies Exchange 2000 Server's default behavior is now available from Microsoft. This feature is included in Exchange 2000 Service Pack 3.
- 已使用 Google 工具列寄出"
"In Microsoft Exchange Server 5.5, each computer that has a public folder store sends a nightly status request message to determine the state of the public folder hierarchy. Exchange 2000 Server does not do this. Typically, in Exchange 2000 the status request message is only sent out one time during the lifetime of the public folder store; it is sent when the store is created.
However, in certain circumstances you may have to generate a status request message. For example, if the public folder hierarchy on the Exchange 2000 computer does not seem to replicate, or the public folder hierarchy replicates very slowly, the generation of a status request message may permit the public folder hierarchy replication to continue. Issues with public folder hierarchy replication may occur if the original status request message that was sent when the public folder store was created was dropped and never acknowledged, or if the message was sent to a server with a substantially incomplete hierarchy.
A supported feature that modifies Exchange 2000 Server's default behavior is now available from Microsoft. This feature is included in Exchange 2000 Service Pack 3.
- 已使用 Google 工具列寄出"
XADM: How to Send Replication Status Request Messages in Exchange 2000 Server
XADM: How to Send Replication Status Request Messages in Exchange 2000 Server:
"After you install this feature, you can configure Exchange 2000 Server to generate status request messages for the public folder hierarchy. To do so, you must add the Enable Replication Messages At Startup registry value. To add the registry value, follow these steps.WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
1. Click Start, click Run, type regedt32 in the Open box, and then click OK to start Registry Editor.
2. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MsExchangeIS\\Public-(guid)
3. On the Edit menu, click Add Value.
4. In the Value Name box, type Enable Replication Messages At Startup.
5. In the Data Type list, click REG_DWORD, and then click OK.
6. In the Data box, type 1 (one), and then click OK.
Note If you set this value to 1, each time the public store starts, a status request message is sent. If you set the value to 0 (the default setting), no status request message is sent when the public store starts.
7. Quit Registry Editor.
- 已使用 Google 工具列寄出"
"After you install this feature, you can configure Exchange 2000 Server to generate status request messages for the public folder hierarchy. To do so, you must add the Enable Replication Messages At Startup registry value. To add the registry value, follow these steps.WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
1. Click Start, click Run, type regedt32 in the Open box, and then click OK to start Registry Editor.
2. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MsExchangeIS\\Public-(guid)
3. On the Edit menu, click Add Value.
4. In the Value Name box, type Enable Replication Messages At Startup.
5. In the Data Type list, click REG_DWORD, and then click OK.
6. In the Data box, type 1 (one), and then click OK.
Note If you set this value to 1, each time the public store starts, a status request message is sent. If you set the value to 0 (the default setting), no status request message is sent when the public store starts.
7. Quit Registry Editor.
- 已使用 Google 工具列寄出"
Update to send status request messages in Exchange 2000 Server
Update to send status request messages in Exchange 2000 Server:
"After you install the hotfix that this article describes, you can configure Exchange 2000 to generate a status request message for each public folder in a public folder store. To do so:
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
1. Start Registry Editor (Regedt32.exe).
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MsExchangeIS\\Public-
3. On the Edit menu, click Add Value.
4. In the Value Name box, type Replication Flags.
5. In the Data Type list, click REG_DWORD, and then click OK.
6. In the Data box, type 1 (one), and then click OK.
7. Quit Registry Editor.
8. Dismount and then remount the public folder store that corresponds to the Public- registry subkey.
When you set the Replication Flags registry value to 1, and then dismount and remount the public folder store, status request messages are generated, and the Replication Flags registry value is automatically reset to 0 (zero).
- 已使用 Google 工具列寄出"
"After you install the hotfix that this article describes, you can configure Exchange 2000 to generate a status request message for each public folder in a public folder store. To do so:
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
1. Start Registry Editor (Regedt32.exe).
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MsExchangeIS\\Public-
3. On the Edit menu, click Add Value.
4. In the Value Name box, type Replication Flags.
5. In the Data Type list, click REG_DWORD, and then click OK.
6. In the Data box, type 1 (one), and then click OK.
7. Quit Registry Editor.
8. Dismount and then remount the public folder store that corresponds to the Public- registry subkey.
When you set the Replication Flags registry value to 1, and then dismount and remount the public folder store, status request messages are generated, and the Replication Flags registry value is automatically reset to 0 (zero).
- 已使用 Google 工具列寄出"
Update to send status request messages in Exchange 2000 Server
Update to send status request messages in Exchange 2000 Server: "
1. Start Registry Editor (Regedt32.exe).
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MsExchangeIS\\Public-
3. On the Edit menu, click Add Value.
4. In the Value Name box, type Replication Flags.
5. In the Data Type list, click REG_DWORD, and then click OK.
6. In the Data box, type 1 (one), and then click OK.
7. Quit Registry Editor.
8. Dismount and then remount the public folder store that corresponds to the Public- registry subkey.
When you set the Replication Flags registry value to 1, and then dismount and remount the public folder store, status request messages are generated, and the Replication Flags registry value is automatically reset to 0 (zero).
- 已使用 Google 工具列寄出"
1. Start Registry Editor (Regedt32.exe).
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MsExchangeIS\\Public-
3. On the Edit menu, click Add Value.
4. In the Value Name box, type Replication Flags.
5. In the Data Type list, click REG_DWORD, and then click OK.
6. In the Data box, type 1 (one), and then click OK.
7. Quit Registry Editor.
8. Dismount and then remount the public folder store that corresponds to the Public- registry subkey.
When you set the Replication Flags registry value to 1, and then dismount and remount the public folder store, status request messages are generated, and the Replication Flags registry value is automatically reset to 0 (zero).
- 已使用 Google 工具列寄出"
XADM: How to Send Replication Status Request Messages in Exchange 2000 Server
XADM: How to Send Replication Status Request Messages in Exchange 2000 Server: "- 已使用 Google 工具列寄出"
After you install this feature, you can configure Exchange 2000 Server to generate status request messages for the public folder hierarchy. To do so, you must add the Enable Replication Messages At Startup registry value. To add the registry value, follow these steps.WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
After you install this feature, you can configure Exchange 2000 Server to generate status request messages for the public folder hierarchy. To do so, you must add the Enable Replication Messages At Startup registry value. To add the registry value, follow these steps.WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
You Had Me At EHLO... : Public Folder Replication Troubleshooting – Part 2: Troubleshooting the Replication of Existing Data
You Had Me At EHLO... : Public Folder Replication Troubleshooting – Part 2: Troubleshooting the Replication of Existing Data: "Use the Synchronize Content option in Exchange 2003 ESM. This is a well-hidden but very useful option. To find it, go under the Public Folders tree and go to the folder in question. Highlight the folder in the left-hand pane. In the right-hand pane click the Status tab. Right-click on the server that has all the data and choose Synchronize Content. This does two things - it causes the server to issue a status request 0x20 for the folder, and it causes it to immediately timeout any backfill entries. Notice that I said you should Synchronize Content from the server that already has the data. You may wonder why you would do that, when it's the other server that has the backfill entries that need to be timed out. Remember that at this point we're just trying to ensure that the server missing the data KNOWS it has something to backfill. To that end, we can use Synchronize Content from the server that has the data to send a 0x20 to the server that doesn't. In this case we're not really interested in seeing a status 0x10 response to the 0x20. We just want the store missing content to receive a replication message for the folder from a store with content, so it can add the appropriate entries to the backfill array. The 0x20 from the server with the data serves this purpose. Note that in Exchange 2003 Sp2, Synchronize Content is now available for the hierarchy by right-clicking on the Public Folders node itself.
- 已使用 Google 工具列寄出"
force public folder replication to Exchange 2007?
- 已使用 Google 工具列寄出"
force public folder replication to Exchange 2007?
You Had Me At EHLO... : Administration of Public Folders with the introduction of Exchange 2007
You Had Me At EHLO... : Administration of Public Folders with the introduction of Exchange 2007: "4. How can I force public folder replication to Exchange 2007?
Replication of information from Exchange 2003 to Exchange 2007 is a combination of the hierarchy information and the content for each of the replicas.
To initiate hierarchy and content replication, use the 'Resend changes' and 'Synchronize content' options in Exchange 2003 ESM. Read more about those here.
Use the following Exchange Management Shell script to push hierarchy from a 2007 server:
Update-publicfolderhierarchy –server <2007 server that is the source of the replication hierarchy>
Use the following Exchange Management Shell script to push content from a 2007 server :
Update-publicfolder –id -server <2007 server that is the source of the replication data>
Of course, you can read more about CMDlets used above in Exchange 2007 documentation.
- 已使用 Google 工具列寄出"
Replication of information from Exchange 2003 to Exchange 2007 is a combination of the hierarchy information and the content for each of the replicas.
To initiate hierarchy and content replication, use the 'Resend changes' and 'Synchronize content' options in Exchange 2003 ESM. Read more about those here.
Use the following Exchange Management Shell script to push hierarchy from a 2007 server:
Update-publicfolderhierarchy –server <2007 server that is the source of the replication hierarchy>
Use the following Exchange Management Shell script to push content from a 2007 server :
Update-publicfolder –id -server <2007 server that is the source of the replication data>
Of course, you can read more about CMDlets used above in Exchange 2007 documentation.
- 已使用 Google 工具列寄出"
You Had Me At EHLO... : Public Folder Replication Fails Due To Empty Legacy Administrative Group
You Had Me At EHLO... : Public Folder Replication Fails Due To Empty Legacy Administrative Group: "- 已使用 Google 工具列寄出"
Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:The store driver couldnt deliver the public folder replication message "Hierarchy (PublicFolder@contoso.com)" because the following error occurred: The Active Directory user wasn't found.
2010/11/04
MSExchange Store Driver
MSExchange Store Driver: "- 已使用 Google 工具列寄出"
Description:
The store driver couldn't deliver the public folder replication message "Status (MY-EX002-IS@logicacmg.com)" because the following error occurred: MapiExceptionDuplicateDelivery: Unable to deliver message. (hr=0x80004005, ec=2603)
Diagnostic context:
Description:
The store driver couldn't deliver the public folder replication message "Status (MY-EX002-IS@logicacmg.com)" because the following error occurred: MapiExceptionDuplicateDelivery: Unable to deliver message. (hr=0x80004005, ec=2603)
Diagnostic context:
2010/11/02
Exchange 2007 Issues: Mailbox Management
Exchange 2007 Issues: Mailbox Management: "- 已使用 Google 工具列寄出"
Exchange 2003 move mail to exchange 2010 fail
error msg :
錯誤:
kh-srvdc.xxxx.com 上的 Active Directory 作業失敗。此錯誤無法重試。其他資訊: 存取權限不足，無法執行操作。。
Active Directory 回應: 00002098: SecErr: DSID-03150E8A, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
使用者的存取權限不足。
開啟 dsa.msc 已驗證的使用者要能繼承權限
Exchange 2003 move mail to exchange 2010 fail
error msg :
錯誤:
kh-srvdc.xxxx.com 上的 Active Directory 作業失敗。此錯誤無法重試。其他資訊: 存取權限不足，無法執行操作。。
Active Directory 回應: 00002098: SecErr: DSID-03150E8A, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
使用者的存取權限不足。
開啟 dsa.msc 已驗證的使用者要能繼承權限
2010/10/29
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] 項目，然後按一下
![[移除] 圖示](http://i.technet.microsoft.com/Bb232021.39ee936b-e5b5-476a-97c9-4fd660441ab7%28zh-tw,EXCHG.140%29.gif)
。
- 按一下 [新增]。在 [新增接收連接器繫結] 對話方塊中，選取 [指定 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 工具列寄出"
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: "Moving public folder replicas from Exchange 2000 to Exchange 2007
- 已使用 Google 工具列寄出"
Moving public folder replicas from Exchange 2000 to Exchange 2007
- 已使用 Google 工具列寄出"
Moving public folder replicas from Exchange 2000 to Exchange 2007
Exchange Server: Moving public folder replicas from Exchange 2000 to Exchange 2007
Exchange Server: Moving public folder replicas from Exchange 2000 to Exchange 2007: "Moving public folder replicas from Exchange 2000 to Exchange 2007
- 已使用 Google 工具列寄出"
Moving public folder replicas from Exchange 2000 to Exchange 2007
- 已使用 Google 工具列寄出"
Moving public folder replicas from Exchange 2000 to Exchange 2007
Propagating Permissions in Exchange 2007 Public Folders
Propagating Permissions in Exchange 2007 Public Folders: "- 已使用 Google 工具列寄出"
exchange 2010 public folder propagate permission
Note: PFDAVAdmin is supported when running with Exchange 2000 Server, Exchange Server 2003 and Exchange Server 2007.
exchange 2010 public folder propagate permission
Note: PFDAVAdmin is supported when running with Exchange 2000 Server, Exchange Server 2003 and Exchange Server 2007.
2010/07/19
Event ID 1388 or 1988: A lingering object is detected: Active Directory
Event ID 1388 or 1988: A lingering object is detected: Active Directory: "- 已使用 Google 工具列寄出"
To identify the GUID of a domain controller
1.
At a command prompt, type the following command, and then press ENTER:
repadmin /showrepl ServerName
where ServerName is the name of the domain controller for which you want to display the GUID.
2.
In the first section of the output, locate the objectGuid entry. Select and copy the GUID value into a text file so that you can use it elsewhere.
repadmin /removelingeringobjects kh-srvdc2 bbbc6ee6-ce1b-4897-8014-7dba7b08d3b9 "CN=Configuration,DC=wahlee,DC=com " /advisory_mode
To identify the GUID of a domain controller
1.
At a command prompt, type the following command, and then press ENTER:
repadmin /showrepl ServerName
where ServerName is the name of the domain controller for which you want to display the GUID.
2.
In the first section of the output, locate the objectGuid entry. Select and copy the GUID value into a text file so that you can use it elsewhere.
repadmin /removelingeringobjects kh-srvdc2 bbbc6ee6-ce1b-4897-8014-7dba7b08d3b9 "CN=Configuration,DC=wahlee,DC=com " /advisory_mode
2010/07/17
OAB Never Downloads for Outlook 2007 Clients with Exchange 2007 on Server 2008 | Confused Amused
OAB Never Downloads for Outlook 2007 Clients with Exchange 2007 on Server 2008 | Confused Amused
The fix is pretty easy. Open the web.config in the OAB folder, and give Authenticated Users both the read and read and execute permissions. Run a iisreset /noforce on the CAS server to bounce IIS
outlook 2007 傳送接收 50%
The fix is pretty easy. Open the web.config in the OAB folder, and give Authenticated Users both the read and read and execute permissions. Run a iisreset /noforce on the CAS server to bounce IIS
outlook 2007 傳送接收 50%
2010/07/14
如何抑制伺服器上的連結狀態資訊
如何抑制伺服器上的連結狀態資訊: "#
啟動 [登錄編輯程式] (regedit)
#
巡覽至下列機碼，並按一下滑鼠右鍵：
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RESvc\Parameters
#
在 [編輯] 功能表上按一下 [新增]，然後新增下列登錄值：
值的名稱：SuppressStateChanges
資料類型：REG_DWORD
資料： 1
底數：十進位
#
關閉 [登錄編輯程式]。
#
重新啟動下列服務：
* Microsoft Exchange Routing Engine (RESvc)
* SMTP Service (SMTPSVC)
* Microsoft Exchange MTA Stacks (MSExchangeMTA)
- 已使用 Google 工具列寄出"
啟動 [登錄編輯程式] (regedit)
#
巡覽至下列機碼，並按一下滑鼠右鍵：
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RESvc\Parameters
#
在 [編輯] 功能表上按一下 [新增]，然後新增下列登錄值：
值的名稱：SuppressStateChanges
資料類型：REG_DWORD
資料： 1
底數：十進位
#
關閉 [登錄編輯程式]。
#
重新啟動下列服務：
* Microsoft Exchange Routing Engine (RESvc)
* SMTP Service (SMTPSVC)
* Microsoft Exchange MTA Stacks (MSExchangeMTA)
- 已使用 Google 工具列寄出"
2010/07/13
2010/07/09
[OS] AD管理TOOLS CSVDE.EXE - Windows SRV Maneger - Windows伺服器系統管理 - AUTOIT@tw - Powered by Discuz!
[OS] AD管理TOOLS CSVDE.EXE - Windows SRV Maneger - Windows伺服器系統管理 - AUTOIT@tw - Powered by Discuz!: "範例下列範例會將 Active Directory 資料匯出至名為 search.txt 的檔案、將搜尋領域設定為樹狀子目錄，並且針對搜尋中所找到的每個物件列出 sAMAccountName、CN 和 distinguished name 屬性：
csvde -f search.txt -p subtree -l SamAccountName,CN,Distinguishname
下列範例會從目前網域 (您所登入的網域) 中名為 input.csv 的檔案匯入資料：
csvde -i -f input.csv
下列範例會將資料從目前網域 (您所登入的網域) 匯出至名為 output.csv 的檔案：
csvde -f output.csv
csvde -f -u -n output.csv
這指令會出資料 並且以UFT8匯出
- 已使用 Google 工具列寄出"
csvde -f search.txt -p subtree -l SamAccountName,CN,Distinguishname
下列範例會從目前網域 (您所登入的網域) 中名為 input.csv 的檔案匯入資料：
csvde -i -f input.csv
下列範例會將資料從目前網域 (您所登入的網域) 匯出至名為 output.csv 的檔案：
csvde -f output.csv
csvde -f -u -n output.csv
這指令會出資料 並且以UFT8匯出
- 已使用 Google 工具列寄出"
How To Export Active Directory User to CSV File | configuration-guide.com
How To Export Active Directory User to CSV File | configuration-guide.com:
"csvde -f domain.csv -r (objectclass=user) -l 'sn,givenname,department,mail'
- 已使用 Google 工具列寄出"
"csvde -f domain.csv -r (objectclass=user) -l 'sn,givenname,department,mail'
- 已使用 Google 工具列寄出"
Installing a New Child Domain by Using the Windows Interface
Installing a New Child Domain by Using the Windows Interface:
Installing a New Child Domain by Using the Windows Interface
Installing a New Child Domain by Using the Windows Interface
HOW TO: Display and Administer All Users in Active Directory
HOW TO: Display and Administer All Users in Active Directory:
HOW TO: Display and Administer All Users in Active Directory
Displaying a List of All Users in Active Directory
- Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
- Right-click the domain name, and then click Find.
- In the Find box, click Custom Search.
- In the In box, click Entire Directory.
- Click Field, click User, and then click Logon Name.
- Leave the Condition box set to Starts With and the Criteria box set to "*".
- Click Find Now
Exporting a list of details from Active Directory | Ask MetaFilter
Exporting a list of details from Active Directory | Ask MetaFilter:
Exporting a list of details from Active Directory
Tutorial for VBScript. Example add members to Active Directory group
Tutorial for VBScript. Example add members to Active Directory group:
How VBScript Adds Users to a Group
Download details: Microsoft Exchange Server Mailbox Merge Wizard (ExMerge)
Download details: Microsoft Exchange Server Mailbox Merge Wizard (ExMerge)
What Others Are Downloading
Others who downloaded Microsoft Exchange Server Mailbox Merge Wizard (ExMerge) also downloaded:
2010/07/07
Message Routing in a Coexistence Environment: Exchange 2007 Help
Message Routing in a Coexistence Environment: Exchange 2007 Help: "When minor link state updates are suppressed, Exchange 2003 also only uses least cost routing.
- 已使用 Google 工具列寄出"
- 已使用 Google 工具列寄出"
Message Routing in a Coexistence Environment: Exchange 2007 Help
Message Routing in a Coexistence Environment: Exchange 2007 Help:
"To avoid routing loops, you must suppress minor link state updates before introducing additional routing group connectors.
- 已使用 Google 工具列寄出"
"To avoid routing loops, you must suppress minor link state updates before introducing additional routing group connectors.
- 已使用 Google 工具列寄出"
Message Routing in a Coexistence Environment: Exchange 2007 Help
Message Routing in a Coexistence Environment: Exchange 2007 Help:
"For example, suppose you have routing groups in Hong Kong, London, and Chicago. If your first Exchange 2007 server is deployed in Chicago, it makes sense to establish the first routing group connector to a bridgehead server in Chicago. However, if you then deploy an Exchange 2007 server in Hong Kong, when messages are sent from users whose mailboxes are on Exchange 2003 servers in Hong Kong to users whose mailboxes are on Exchange 2007 servers in Hong Kong, the messages will be routed through Chicago.
- 已使用 Google 工具列寄出"
"For example, suppose you have routing groups in Hong Kong, London, and Chicago. If your first Exchange 2007 server is deployed in Chicago, it makes sense to establish the first routing group connector to a bridgehead server in Chicago. However, if you then deploy an Exchange 2007 server in Hong Kong, when messages are sent from users whose mailboxes are on Exchange 2003 servers in Hong Kong to users whose mailboxes are on Exchange 2007 servers in Hong Kong, the messages will be routed through Chicago.
- 已使用 Google 工具列寄出"
Message Routing in a Coexistence Environment: Exchange 2007 Help
Message Routing in a Coexistence Environment: Exchange 2007 Help:
"Creating Additional Routing Group Connectors "
"Creating Additional Routing Group Connectors "
Getting to know the legacy Routing Group Connector in Exchange 2007
Getting to know the legacy Routing Group Connector in Exchange 2007:
"For those of you running bigger organizations, you may need to have multiple legacy RGCs. There are several things to consider before you do this, and as usual, the Exchange team blog tells you all you need to know. Before you go run off and read that link, though, here's a summary of the highlights:
Add the legacy bridgehead servers to the "ExchangeLegacyInterop" group so they have the proper permissions to authenticate to the Exchange 2007 HT servers
"For those of you running bigger organizations, you may need to have multiple legacy RGCs. There are several things to consider before you do this, and as usual, the Exchange team blog tells you all you need to know. Before you go run off and read that link, though, here's a summary of the highlights:
Add the legacy bridgehead servers to the "ExchangeLegacyInterop" group so they have the proper permissions to authenticate to the Exchange 2007 HT servers
Getting to know the legacy Routing Group Connector in Exchange 2007
Getting to know the legacy Routing Group Connector in Exchange 2007:
"For those of you running bigger organizations, you may need to have multiple legacy RGCs. There are several things to consider before you do this, and as usual, the Exchange team blog tells you all you need to know. Before you go run off and read that link, though, here's a summary of the highlights:
- 已使用 Google 工具列寄出"
"For those of you running bigger organizations, you may need to have multiple legacy RGCs. There are several things to consider before you do this, and as usual, the Exchange team blog tells you all you need to know. Before you go run off and read that link, though, here's a summary of the highlights:
- 已使用 Google 工具列寄出"
Getting to know the legacy Routing Group Connector in Exchange 2007
Getting to know the legacy Routing Group Connector in Exchange 2007: "
For small organizations, having a single legacy Exchange server connecting the legacy portion of the org to Exchange 2007 probably isn't that horrible, but in a larger org you may need to specify additional bridghead servers. The answer is found, of course, in the Exchange Management Shell.
- 已使用 Google 工具列寄出"
For small organizations, having a single legacy Exchange server connecting the legacy portion of the org to Exchange 2007 probably isn't that horrible, but in a larger org you may need to specify additional bridghead servers. The answer is found, of course, in the Exchange Management Shell.
- 已使用 Google 工具列寄出"
訂閱：
文章 (Atom)