2010/05/31
2010/05/29
Understanding Backup, Restore and Disaster Recovery: Exchange 2010 Help
Understanding Backup, Restore and Disaster Recovery: Exchange 2010 Help
Almost all of the configuration settings for Mailbox, Client Access, Hub Transport, and Unified Messaging server roles are stored in Active Directory.
As with previous versions of Exchange, Exchange 2010 includes a Setup parameter for recovering lost servers. This parameter, /m:RecoverServer, is used to rebuild and re-create a lost server by using the settings and configuration information stored in Active Directory.
Recover an Exchange Server
Prerequisites Recover a Lost Exchange Server
Almost all of the configuration settings for Mailbox, Client Access, Hub Transport, and Unified Messaging server roles are stored in Active Directory.
As with previous versions of Exchange, Exchange 2010 includes a Setup parameter for recovering lost servers. This parameter, /m:RecoverServer, is used to rebuild and re-create a lost server by using the settings and configuration information stored in Active Directory.
Recover an Exchange Server
You can recover a lost server by using the Setup /m:RecoverServer switch in Microsoft Exchange Server 2010. Most of the settings for a computer running Exchange 2010 are stored in Active Directory. The /m:RecoverServer switch rebuilds an Exchange server with the same name by using the settings and other information stored in Active Directory.
Recovering a lost Exchange server is often accomplished by using new hardware. However, you can also use an existing server.
This topic shows you how to recover a lost Exchange 2010 server that isn't a member of a database availability group (DAG). For detailed steps about how to recover a server that was a member of a DAG, see Recover a Database Availability Group Member Server.
Prerequisites - The server on which recovery is being performed must be running the same operating system as the lost server. For example, you can't recover a server that was running Exchange 2010 and Windows Server 2008 on a server running Windows Server 2008 R2, or vice versa.
- The same disk drive letters on the failed server for mounted databases must exist on the server on which you're running recovery.
- The server on which recovery is being performed should have the same performance characteristics and hardware configuration as the lost server.
- The following procedure can be run on an Exchange 2010 server that has the Client Access, Hub Transport, Mailbox, or Unified Messaging server roles installed. You can't use Setup /m:RecoverServer to recover an Edge Transport server. For information about preserving Edge Transport server settings and applying saved settings to an Edge Transport server, see Edge Transport Server Cloned Configuration.
Recover a Lost Exchange Server You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Exchange infrastructure permissions" section in the Exchange and Shell Infrastructure Permissions topic.
- Reset the computer account for the lost server. For detailed steps, see Reset a Computer Account.
- Install the proper operating system and name the new server with the same name as the lost server. Recovery won't succeed if the server on which recovery is being performed doesn't have the same name as the lost server.
- Join the server to the same domain as the lost server.
- Install the necessary prerequisites and operating system components. For details, see Exchange 2010 System Requirements and Exchange 2010 Prerequisites.
- Log on to the server being recovered and open a command prompt.
- Navigate to the Exchange 2010 installation files, and run the following command:
Setup /m:RecoverServer
- After Setup has completed, but before the recovered server is put into production, reconfigure any custom settings that were previously present on the server.
2010/05/28
Error: ClassFactory cannot supply requested class, error code: -1056749262
http://www.itexperience.net/2008/06/14/error-classfactory-cannot-supply-requested-class-error-code-1056749262/
During a migration of Exchange 2000 or Exchange 2003 to Exchange 2007, the following error may occur:
During a migration of Exchange 2000 or Exchange 2003 to Exchange 2007, the following error may occur:
Error was found for Username(user mail address) because: Error occurred in the step: Opening source mailbox. Failed to open mailbox with error: ClassFactory cannot supply requested class, error code: -1056749262
In my case, this error occured because the user was disabled in Active Directory.
If you face this same error, try the following:
If you face this same error, try the following:
- Unhide the user in the Global Address Book (open the Properties of the User in Active Directory, go to the Exchange Advanced tab, and deselect the “Hide from Exchange Address Lists” checkbox)
- Enable the user, in case the user is Disabled. Also check whether the user is Locked out or not (open the Properties of the User in Active Directory and check the Account tab. Both the chekboxes should NOT be checked)
When one or both of the above were the case, wait for 10-30 minutes. Active Directory needs to replicate its changes. Then retry to move the mailbox to the other server.
If you still face the same error after 30 minutes, try to unmount en mount the Information Store. This should be your last chance for survival :)
2010/05/25
Redirecting OWA URLs in Exchange 2010 : Brian Desmond's Blog
Redirecting OWA URLs in Exchange 2010 : Brian Desmond's Blog
In order to work around this, you need to use the HTTP Redirection feature in IIS (the default.aspx trick mentioned above should work too), as well as remove the requirement for SSL at the top level Default Web Site object. You have to be careful doing this because when you set settings on the web site, IIS will push them down to any virtual directory below which does not explicitly set that setting itself. To setup the redirect, select the Default Web Site in IIS Manager, and open the HTTP Redirect option under IIS. Complete it like this:
Select the Default Web Site and open the SSL Settings properties. Uncheck the Require SSL checkbox as shown below:
Like the redirection settings, this change will be inherited down the tree for any virtual directory which does not explicitly set the setting independently. Ensure that SSL is required for the following virtual directories:
In order to work around this, you need to use the HTTP Redirection feature in IIS (the default.aspx trick mentioned above should work too), as well as remove the requirement for SSL at the top level Default Web Site object. You have to be careful doing this because when you set settings on the web site, IIS will push them down to any virtual directory below which does not explicitly set that setting itself. To setup the redirect, select the Default Web Site in IIS Manager, and open the HTTP Redirect option under IIS. Complete it like this:
Warning: It’s very important that you check the checkboxes exactly as shown in the screenshot above!
Once this step is complete, you need to remove the enforced redirect from each of the virtual directories under the Default Web Site. To do this, select each virtual directory individually, and then open the HTTP Redirect property and uncheck the “Redirect requests to this destination” checkbox. You’ll need to do this on the following virtual directories:- aspnet_client
- Autodiscover
- ecp
- EWS
- Microsoft-Server-ActiveSync
- OAB
- PowerShell
- Rpc
Note: The Exchange, Exchweb, and Public virtual directories should redirect to /owa.
If at this point you simply browse to http://cas01.customer.com, you’ll get an HTTP 403.4 error. This is because SSL is required at the top-level website. In order to get the redirect working, we need to disable SSL for the toplevel website while leaving it enabled for the relevant child virtual directories.Select the Default Web Site and open the SSL Settings properties. Uncheck the Require SSL checkbox as shown below:
Like the redirection settings, this change will be inherited down the tree for any virtual directory which does not explicitly set the setting independently. Ensure that SSL is required for the following virtual directories:
- Autodiscover
- ecp
- EWS
- Microsoft-Server-ActiveSync
- OAB
- owa
- Rpc
Warning: If you require SSL for the PowerShell virtual directory, you will render Remote PowerShell inoperable!
Once you’ve configured the redirection and SSL settings, open a command prompt and run iisreset. At this point you should be able to browse to http://localhost on the CAS server and get redirected to https://owa.customer.com/owa. These steps were tested on Windows Server 2008 R2. While they should be similar under Windows Server 2008, they may not be identical.
2010/05/21
Exchange 2010 Legacy Hostname - Questions and answers to issues related to Microsoft: OS, Applications, Development, Hardware, Server, Internet Protocols, Database, Exchange .
Exchange 2010 Legacy Hostname - Questions and answers to issues related to Microsoft: OS, Applications, Development, Hardware, Server, Internet Protocols, Database, Exchange .
Do has demazter said and decomission your 2007 CAS moving everything to 2010 CAS server. To coexist with the 2003 OWA you need to configure the legacy url in exchange 2010 CAS. To do that run the following command:
Set-OWAVirtualDirectory\OWA* -Exchange2003URL https://legacy.contoso.com/exchange
exchange 2010 CAS will receive the request for OWA and if the mailbox is from 2003 it will redirect the user to the outside world and it will go in again to the 2003 url. for example if you have ISA publishing OWA you will need publishing rules for both 2010 and 2003.
Note that to create a publish rule for 2010 on ISA use the 2007 template and add the /ecp/* on the paths tab.
Also note that forms based authentication must be enabled on exchange 2003 for you to get a single sign on scenario.
you also need to change point all external urls to the 2010 CAS and configure 2010 CAS external url atributes on the server.
see this link for help:
http://technet.microsoft.com/en-us/library/ee332348.aspx
it's very usefull
hope it helps
Do has demazter said and decomission your 2007 CAS moving everything to 2010 CAS server. To coexist with the 2003 OWA you need to configure the legacy url in exchange 2010 CAS. To do that run the following command:
Set-OWAVirtualDirectory
exchange 2010 CAS will receive the request for OWA and if the mailbox is from 2003 it will redirect the user to the outside world and it will go in again to the 2003 url. for example if you have ISA publishing OWA you will need publishing rules for both 2010 and 2003.
Note that to create a publish rule for 2010 on ISA use the 2007 template and add the /ecp/* on the paths tab.
Also note that forms based authentication must be enabled on exchange 2003 for you to get a single sign on scenario.
you also need to change point all external urls to the 2010 CAS and configure 2010 CAS external url atributes on the server.
see this link for help:
http://technet.microsoft.c
it's very usefull
hope it helps
Transitioning CAS to Exchange Server 2010 from standalone Exchange Server 2003
Transitioning CAS to Exchange Server 2010 from standalone Exchange Server 2003
According to the Exchange 2010 Deployment Assistant, the process is:
- you must first install one Exchange 2003 front-end server in order to provide your users with a unified namespace
- Exchange2003URL - set this parameter to the legacy DNS endpoint, for example, http://legacy.contoso.com (This parameter is only necessary when you have users with mailboxes on Exchange 2003 at the same time as users with mailboxes on Exchange 2010).
- associate the legacy host name e.g. legacy.contoso.com with your existing Exchange 2003 front-end server and associate your current host name (for example, mail.contoso.com) with your Exchange 2010 Client Access server or array - via DNS host (A) records in your internal and external DNS servers. Your end-users will not see or use this namespace. It will be used by Autodiscover and Client Access servers when redirecting legacy users to a legacy server.
- Create legacy publishing rules in your reverse proxy or firewall solution to point to your Exchange 2003 front-end server. Refer to your solution's user manual for instructions on how to do this.
So, in summary, following these steps should allow for a unified namespace for OWA + EA + Outlook Anywhere during mailbox moves without any user intervention required: (a) Install Exchange 2003 front-end server (b) set Exchange2003URL parameter for CAS array to legacy.contoso.com (c) create internal and external DNS host records pointing legacy.contoso.com to Exchange 2003 front-end server/ public IP (d) create port-forwarding/ NAT rule on corporate firewall publishing CAS array on public IP.
This suggests I don't really need a reverse proxy infrastructure, but can use port forwarding only - assuming a new Exchange 2003 front-end server is installed.
Does anyone have experience with this? Exchange 2003 to Exchange 2007 was so easy for ensuring consistent OWA + EA + Outlook Anywhere access with a unified namespace during enterprise transitions!
Thanks in advance.
IR8
2010/05/19
Active Directory Error 0x51 occurred when trying to check the suitability of server ''. Error: 'Active directory response: The LDAP server is unavailable'. It was running the command
Active Directory Error 0x51 occurred when trying to check the suitability of server '<servername>'. Error: 'Active directory response: The LDAP server is unavailable'. It was running the command
描述:
(PID 7988，執行緒 77) 在處理索引 0 的記錄時發生工作 Get-Recipient 寫入錯誤。錯誤: Microsoft.Exchange.Data.Directory.SuitabilityDirectoryException: 嘗試檢查伺服器 'directory.xxx.com.tw' 適用性時發生 Active Directory 錯誤 0x51。錯誤：'Active Directory 回應: LDAP 伺服器無法使用。' ---> System.DirectoryServices.Protocols.LdapException: LDAP 伺服器無法使用。
http://support.microsoft.com/default.aspx?scid=kb;en-us;2019500&sd=rss&spid=13965
解決方法：
Go to the following location and delete the Exchange Management Console file.
C:\users\\AppData\Roaming\Microsoft\MMC\Exchange Management Console
Close EMC and Reopen it.
NOTE: Be aware, that You may loose certain filtering preconfigurations You made for that user.
描述:
(PID 7988，執行緒 77) 在處理索引 0 的記錄時發生工作 Get-Recipient 寫入錯誤。錯誤: Microsoft.Exchange.Data.Directory.SuitabilityDirectoryException: 嘗試檢查伺服器 'directory.xxx.com.tw' 適用性時發生 Active Directory 錯誤 0x51。錯誤：'Active Directory 回應: LDAP 伺服器無法使用。' ---> System.DirectoryServices.Protocols.LdapException: LDAP 伺服器無法使用。
http://support.microsoft.com/default.aspx?scid=kb;en-us;2019500&sd=rss&spid=13965
解決方法：
Go to the following location and delete the Exchange Management Console file.
C:\users\
Close EMC and Reopen it.
NOTE: Be aware, that You may loose certain filtering preconfigurations You made for that user.
2010/05/14
轉寄: VirtualizationAdmin.com - Installing Data Protection Manager (DPM) 2010 (Part 1)
Try MSExchange.org's Email Security Silver Award on a VM modusGate Email Security gateway received a Silver Award from MSExchange.org as reviewer J. Peter Bruzzese evaluated the software in a virtualized environment connected to a Microsoft Exchange 2010 server. modusGate VM protects your email server against spam, viruses, phishing, botnets, fraud and other electronic threats. Just PublishedDate - May 13th, 2010 How to install, configure and utilize DPM 2010 to backup and restore virtual machines and Hyper-V servers. Recent ArticlesLatest NewsTechGenix Sites
|
Visit the Subscription Management section to unsubscribe.
VirtualizationAdmin.com is in no way affiliated with Microsoft Corp.
Click here for sponsorship information or contact us at advertising@virtualizationadmin.com.
Copyright © VirtualizationAdmin.com 2010. All rights reserved.
VirtualizationAdmin.com is in no way affiliated with Microsoft Corp.
Click here for sponsorship information or contact us at advertising@virtualizationadmin.com.
Copyright © VirtualizationAdmin.com 2010. All rights reserved.
2010/05/12
Volume Activation Planning Guide
Volume Activation Planning Guide
The KMS client computers are activated after meeting the activation threshold. The computers running Windows server 2008 or Windows Server 2008 R2 the activation threshold is five. For computers running Windows Vista or Windows 7 the activation threshold is 25. The thresholds include clients and servers that are running on physical computers or virtual machines.
The KMS client computers are activated after meeting the activation threshold. The computers running Windows server 2008 or Windows Server 2008 R2 the activation threshold is five. For computers running Windows Vista or Windows 7 the activation threshold is 25. The thresholds include clients and servers that are running on physical computers or virtual machines.
Retail
Windows 7 and Windows Server 2008 R2 products that are acquired through a retail store are individually licensed and are activated in the same way as retail versions of the Windows Vista and Windows Server 2008 operating systems. Each purchased copy comes with one unique product key (printed on the product packaging), which the user enters during the product installation. The computer uses this product key to complete the activation after the installation of the operating system is complete. This final activation step can be accomplished online or by telephone.
Volume Activation Deployment Guide
Volume Activation Deployment Guide
Windows 7 and Windows Server 2008 R2
Converting Retail Editions to Volume Activation
Retail editions of Windows 7 Professional and Windows Server 2008 R2 can be converted to KMS clients, provided that the organization has acquired the appropriate volume licenses and conforms to the Product Use Rights. To convert Windows 7 Professional and all editions of Windows Server 2008 R2 from retail to a KMS client, skip the Product Key page during operating system installation. When installation is complete, open an elevated Command Prompt window and type:Slmgr.vbs /ipk
Prepare Active Directory and Domains
Prepare Active Directory and Domains
http://technet.microsoft.com/en-us/library/bb125224.aspx
http://technet.microsoft.com/en-us/library/bb125224.aspx
CA brightstor R11.1 use SQL DB
install SQL 2000 DB and apply SP4
run SQLSetup.exe (在program files\ca的資料夾裡面)
重新restart all ca services
check 管理員-資料庫-為SQL
30天會固定清除資料庫
利用"合併" 功能，可以將磁帶裡面的db合併進來.
run SQLSetup.exe (在program files\ca的資料夾裡面)
重新restart all ca services
check 管理員-資料庫-為SQL
30天會固定清除資料庫
利用"合併" 功能，可以將磁帶裡面的db合併進來.
2010/05/11
mcs.ireland.blog/infrastructure : Using Key Management Services (KMS) Across Domains
mcs.ireland.blog/infrastructure : Using Key Management Services (KMS) Across Domains: "- 已使用 Google 工具列寄出"
child domain 連線kms server
child domain 連線kms server
2010/05/10
mail tips
Each of these MailTips can be turned on or off in the MailTips options (accessible in the Mail section of the Outlook options). They can also be turned on or off by the Exchange administrator – ensuring that they can be configured depending on the characteristics of any given organization.
2010/05/07
2010/05/06
Outlook 2007在x64平台上無法預覽信件的PDF附件檔
http://www.pretentiousname.com/adobe_pdf_x64_fix/#downl
Outlook 2007在x64平台上無法預覽信件的PDF附件檔，會出現:
Outlook 2007在x64平台上無法預覽信件的PDF附件檔，會出現:
網域控制站無法正常運作
網域控制站無法正常運作
AD DC1 & DC2 無法同步 ： dc1 event 正常
dc2 有很多錯誤事件:
開啟replmon檢查複寫:"目標帳戶名稱不正確"
KB 837513 - check 時間同步
DC2快了10分鐘
重新設定net time到外部時間來源
AD DC1 & DC2 無法同步 ： dc1 event 正常
dc2 有很多錯誤事件:
開啟replmon檢查複寫:"目標帳戶名稱不正確"
KB 837513 - check 時間同步
DC2快了10分鐘
重新設定net time到外部時間來源
2010/05/05
公用資料夾 衝突
如果您的組織把公用資料夾保存在一部以上的 Microsoft Exchange Server 上，並且在不同的電腦上對相同的項目作修改，而這些電腦又同步作業的話，您可能會看到衡突的訊息。
若要解決衝突，請開啟衝突的訊息。此訊息包含該項目所有衝突的版本。若要把所有資訊合併為一個項目，開啟在衝突訊息中的其中一個項目，然後 從其他項目複製任何您需要的資訊到此項目。然後按一下 [保存此項目]。其他衝突的項目則會被刪除。
若要將所有衝突項目個別儲存在公用資料夾中，按一下 [保存所有]。
若要解決衝突，請開啟衝突的訊息。此訊息包含該項目所有衝突的版本。若要把所有資訊合併為一個項目，開啟在衝突訊息中的其中一個項目，然後 從其他項目複製任何您需要的資訊到此項目。然後按一下 [保存此項目]。其他衝突的項目則會被刪除。
若要將所有衝突項目個別儲存在公用資料夾中，按一下 [保存所有]。
2010/05/03
Windows server 2008 R2 dcpromo 一直無法成功
從windows 2000 server run adprep32 升級 schema 是可以的.
期間遇到幾個失敗
1.FSMO:domain naming and schema master miss, use seize 取回OK
2.adprep32 /forestprep 一半失敗，AD架構要開啟允許修改
3.prepare OK之後，開始 dcpromo , but 一直無法成功 結果在 kb 找到答案：KB 2000939
期間遇到幾個失敗
1.FSMO:domain naming and schema master miss, use seize 取回OK
2.adprep32 /forestprep 一半失敗，AD架構要開啟允許修改
3.prepare OK之後，開始 dcpromo , but 一直無法成功 結果在 kb 找到答案：KB 2000939
troubleshoot public folder replicate is stop between ad site. - Windows Live
troubleshoot public folder replicate is stop between ad site. - Windows Live
公用資料夾的問題終於處理ok
原因是Public folder 的 proxyaddress衝突
利用adsiedit錯開即可。
公用資料夾的問題終於處理ok
原因是Public folder 的 proxyaddress衝突
利用adsiedit錯開即可。
Windows Server 2008 R2: Windows Storage Server 2008
Windows Server 2008 R2: Windows Storage Server 2008
Microsoft Windows Storage Server 2008 is built upon an optimized release of the reliable and flexible file services of Windows Server 2008 for better file serving performance. Microsoft then adds advanced storage technologies such as file de-duplication and an iSCSI software target for unified file- and block-based storage and packages it for delivery within storage appliances. Similarly, Microsoft partners then offer specialized hardware and introduce additional software components to create WSS08-based appliances. Windows-powered storage appliances give customers new storage capabilities, simplified deployment and easier management while assuring seamless synergy in their Windows infrastructure in a cost-effective and high-performance platform, and is delivered through our OEM Partners.
Microsoft Windows Storage Server 2008 is built upon an optimized release of the reliable and flexible file services of Windows Server 2008 for better file serving performance. Microsoft then adds advanced storage technologies such as file de-duplication and an iSCSI software target for unified file- and block-based storage and packages it for delivery within storage appliances. Similarly, Microsoft partners then offer specialized hardware and introduce additional software components to create WSS08-based appliances. Windows-powered storage appliances give customers new storage capabilities, simplified deployment and easier management while assuring seamless synergy in their Windows infrastructure in a cost-effective and high-performance platform, and is delivered through our OEM Partners.
Exchange 2003 - Planning Roadmap for Upgrade and Coexistence: Exchange 2010 Help
Exchange 2003 - Planning Roadmap for Upgrade and Coexistence: Exchange 2010 Help
First, you upgrade all Internet-facing Active Directory sites by doing
the following:
- Upgrade existing Exchange 2003 servers to Exchange 2003 SP2.
- Deploy Exchange 2010 servers in this order:
- Client Access
- Hub Transport
- Unified Messaging
- Mailbox
- Client Access
- Configure the Exchange 2003 front-end server and the Exchange 2010 Client Access server
- Configure the Exchange 2010 Hub Transport servers (s)
- Configure the Unified Messaging server(s)
- Move mailboxes from Exchange 2003 to Exchange 2010
Then, you upgrade all internal Active Directory sites in the same manner.
訂閱：
文章 (Atom)