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
2010/07/21
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 工具列寄出"
How to Upgrade Default Address Lists from LDAP Filters to OPATH Filters: Exchange 2007 Help
How to Upgrade Default Address Lists from LDAP Filters to OPATH Filters: Exchange 2007 Help: "#
To upgrade the All Users default address list, run the following command:
Set-AddressList 'All Users' -IncludedRecipients MailboxUsers
#
To upgrade the All Groups default address list, run the following command:
Set-AddressList 'All Groups' -IncludedRecipients MailGroups
#
To upgrade the All Contacts default address list, run the following command:
Set-AddressList 'All Contacts' -IncludedRecipients MailContacts
#
To upgrade the Public Folders default address list, run the following command:
Set-AddressList 'PublicFolders' -RecipientFilter { RecipientType -eq 'PublicFolder' }
#
To upgrade the Default Global Address List, run the following command:
Set-GlobalAddressList 'Default Global Address List' -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact' -or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass -eq 'msExchDynamicDistributionList' -or ObjectClass -eq 'group' -or ObjectClass -eq 'publicFolder'))}
#
A warning appears asking if you are sure you want to perform this action. Type Y to confirm.
- 已使用 Google 工具列寄出"
To upgrade the All Users default address list, run the following command:
Set-AddressList 'All Users' -IncludedRecipients MailboxUsers
#
To upgrade the All Groups default address list, run the following command:
Set-AddressList 'All Groups' -IncludedRecipients MailGroups
#
To upgrade the All Contacts default address list, run the following command:
Set-AddressList 'All Contacts' -IncludedRecipients MailContacts
#
To upgrade the Public Folders default address list, run the following command:
Set-AddressList 'PublicFolders' -RecipientFilter { RecipientType -eq 'PublicFolder' }
#
To upgrade the Default Global Address List, run the following command:
Set-GlobalAddressList 'Default Global Address List' -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact' -or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass -eq 'msExchDynamicDistributionList' -or ObjectClass -eq 'group' -or ObjectClass -eq 'publicFolder'))}
#
A warning appears asking if you are sure you want to perform this action. Type Y to confirm.
- 已使用 Google 工具列寄出"
Implementing Exchange Server 2007 for coexistence with Exchange Server 2003
Implementing Exchange Server 2007 for coexistence with Exchange Server 2003:
"The Exchange Server 2003 Bridgehead Server is automatically added as a member of the Legacy Interop Universal Security Group. This group has the permission to send and receive e-mail through Exchange Server 2007.
- 已使用 Google 工具列寄出"
重點
"The Exchange Server 2003 Bridgehead Server is automatically added as a member of the Legacy Interop Universal Security Group. This group has the permission to send and receive e-mail through Exchange Server 2007.
- 已使用 Google 工具列寄出"
重點
Implementing Exchange Server 2007 for coexistence with Exchange Server 2003
Implementing Exchange Server 2007 for coexistence with Exchange Server 2003: "The Exchange Server 2003 Bridgehead Server is automatically added as a member of the Legacy Interop Universal Security Group. This group has the permission to send and receive e-mail through Exchange Server 2007.
- 已使用 Google 工具列寄出"
- 已使用 Google 工具列寄出"
Implementing Exchange Server 2007 for coexistence with Exchange Server 2003
Implementing Exchange Server 2007 for coexistence with Exchange Server 2003: "When the first Exchange 2007 Hub Transport server is installed into an existing Exchange 2003 organization, you must select an Exchange 2003 bridgehead server to which the routing group connector should establish a connection.
- 已使用 Google 工具列寄出"
- 已使用 Google 工具列寄出"
Implementing Exchange Server 2007 for coexistence with Exchange Server 2003
Implementing Exchange Server 2007 for coexistence with Exchange Server 2003:
"Exchange 2003 servers use Link State Routing to exchange routing table entries for the path that messages will take through the exchange organization. A routing group master collects information about the status of other Exchange Servers and creates a small table in memory, the Link State Table (LST). The LST is then distributed to other Exchange Servers and will be updated at fixed intervals. Based on the Information about the status of other Exchange servers, a lost connection to another Exchange Server will be saved in the LST and Exchange tries to route the message over another Exchange server to the destination.
Link state routing is not used by Exchange 2007 Hub Transport servers and Exchange 2007 can't propagate link state updates. When a Hub Transport server sends an e-mail to another Active Directory site where a Hub Transport server cannot be contacted, the Hub Transport server does not recalculate the route. Hub Transport servers always try to communicate directly with other Hub Transport servers.
If there is more than one Hub Transport Server in a site, messaging traffic is automatically load balanced and the sending Hub Transport Server tries to reach each Hub Transport Server in the destination site before the connection fails.
When the connection to the destination site is unavailable, Exchange Server 2007 uses the associated site link costs to an Active Directory site to deternmine the closest site to send the mail to. This behavior is known as queue at point of failure.
If multiple routing paths exist between the default Exchange 2007 Routing Group and any Exchange Server 2003 routing group, Link State updates must be suppressed to ensure that no message loops occur when a route is recalculated. Microsoft recommends suppressing Link State updates if multiple connections exist between Exchange Server 2007 and 2003. It is possible to disable Link State updates through a registry patch. Configuration changes such adding a connector in the Exchange organization is still propagated by using the Link State information.
- 已使用 Google 工具列寄出"
"Exchange 2003 servers use Link State Routing to exchange routing table entries for the path that messages will take through the exchange organization. A routing group master collects information about the status of other Exchange Servers and creates a small table in memory, the Link State Table (LST). The LST is then distributed to other Exchange Servers and will be updated at fixed intervals. Based on the Information about the status of other Exchange servers, a lost connection to another Exchange Server will be saved in the LST and Exchange tries to route the message over another Exchange server to the destination.
Link state routing is not used by Exchange 2007 Hub Transport servers and Exchange 2007 can't propagate link state updates. When a Hub Transport server sends an e-mail to another Active Directory site where a Hub Transport server cannot be contacted, the Hub Transport server does not recalculate the route. Hub Transport servers always try to communicate directly with other Hub Transport servers.
If there is more than one Hub Transport Server in a site, messaging traffic is automatically load balanced and the sending Hub Transport Server tries to reach each Hub Transport Server in the destination site before the connection fails.
When the connection to the destination site is unavailable, Exchange Server 2007 uses the associated site link costs to an Active Directory site to deternmine the closest site to send the mail to. This behavior is known as queue at point of failure.
If multiple routing paths exist between the default Exchange 2007 Routing Group and any Exchange Server 2003 routing group, Link State updates must be suppressed to ensure that no message loops occur when a route is recalculated. Microsoft recommends suppressing Link State updates if multiple connections exist between Exchange Server 2007 and 2003. It is possible to disable Link State updates through a registry patch. Configuration changes such adding a connector in the Exchange organization is still propagated by using the Link State information.
- 已使用 Google 工具列寄出"
2010/07/05
Step-by-Step: Migrating Exchange 2000 to Exchange 2003 Using New Hardware
Step-by-Step: Migrating Exchange 2000 to Exchange 2003 Using New Hardware
- There are a number of public folders on the Exchange 2000 server that do not need to be replicated and moved to the new server, including several that are part of the Exchange 2000 version of OWA. On my system these included:
- Controls
- Event Config_
- Events Root
- Exchweb
- Img
- Microsoft
- Offline Address Book – First Administrative Group
- Schema-root
- Views
Understanding EXOLEDB Default Folders
Understanding EXOLEDB Default Folders: "
schema-root
default
exchange v1
Do you need to replicate those folders when servers are decommissioned?
schema-root
default
exchange v1
Do you need to replicate those folders when servers are decommissioned? You do not have to replicate folder content as part of the replicate system folders procedures.
如何將離線通訊錄產生處理程序移至另一部伺服器: Exchange 2007 說明
如何將離線通訊錄產生處理程序移至另一部伺服器: Exchange 2007 說明: "- 已使用 Google 工具列寄出"
2010/07/02
2010/06/25
將預設電子郵件地址原則從 LDAP 篩選器升級為 OPATH 篩選器
Exchange 2010 中支援 LDAP 語法篩選，只有從 Exchange 2003 或更早版本遷移的物件上才會存在。有當您想要編輯來自 Exchange 2010 伺服器的篩選器時，才需要將這些 LDAP 篩選器升級為 OPATH 語法。例如，您的組織中若有 Exchange 2003 和 Exchange 2010 伺服器，便可以從 Exchange 2003 伺服器管理 LDAP 語法篩選器。您不能在 Exchange 2010 中管理或建立 LDAP 語法篩選器。
Set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients
Set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients
2010/06/23
2010/06/14
Failed to cleanup the source mailbox after the move.
Failed to cleanup the source mailbox after the move.
Warning: Failed to cleanup the source mailbox after the move.
Error details: MapiExceptionNotFound: Unable to delete mailbox. (hr=0x8004010f, ec=-2147221233)
KB940012
Warning: Failed to cleanup the source mailbox after the move.
Error details: MapiExceptionNotFound: Unable to delete mailbox. (hr=0x8004010f, ec=-2147221233)
KB940012
2010/06/11
2010/06/10
Understanding Client Access Server Namespaces
http://technet.microsoft.com/en-us/library/dd351198.aspx
We recommend that each Active Directory site in a region that has one or more Internet-facing Client Access servers have a unique namespace. This is usually represented in DNS by an A record, for example, mail.contoso.com or mail.europe.contoso.com.
Exchange 2010 Organizational Models This topic examines the following types of topology:
We recommend that each Active Directory site in a region that has one or more Internet-facing Client Access servers have a unique namespace. This is usually represented in DNS by an A record, for example, mail.contoso.com or mail.europe.contoso.com.
Exchange 2010 Organizational Models - Consolidated Datacenter Model This model consists of a single physical site. All servers are located within the site, and there's a single namespace, for example, mail.contoso.com.
- Single Namespace with Proxy Sites This model consists of multiple physical sites. Only one site contains an Internet-facing Client Access server. The other sites aren't exposed to the Internet. There's only one namespace for the sites in this model, for example, mail.contoso.com.
- Single Namespace and Multiple Sites This model consists of multiple physical sites. Each site can have an Internet-facing Client Access server. Or, there may be only a single site that contains Internet-facing Client Access servers. There's only one namespace for the sites in this model, for example, mail.contoso.com.
- Regional Namespaces This model consists of multiple physical sites and multiple namespaces. For example, a site that's located in New York City would have the namespace mail.usa.contoso.com, a site that's located in Toronto would have the namespace mail.canada.contoso.com, and a site that's located in London would have the namespace mail.europe.contoso.com.
- Multiple Forests This model consists of multiple forests that have multiple namespaces. An organization that uses this model could be made up of two partner companies, for example, Contoso and ContosoOnline. Namespaces might include mail.usa.contoso.com, mail.europe.contoso.com, mail.asia.contosoonline.com, and mail.europe.contosoonline.com.
 Important: |
|---|
| We don't recommend deploying a topology that has a single namespace and multiple Active Directory sites. If your topology uses multiple Active Directory sites, consider using a regional namespace model. |
Client Access Server Planning
Client Access Server Planning http://technet.microsoft.com/en-us/library/bb125239.aspx
When planning your Exchange 2010 deployment, you must have at least one computer with the Client Access server role installed in every Active Directory site that contains Exchange 2010 mailboxes. You can have multiple computers with the Client Access server role installed within each Active Directory site. To provide external client access, at least one Client Access server within your organization must be Internet-facing.
For more information about namespace planning and Client Access servers, see Understanding Client Access Server Namespaces.
2010/06/07
You Had Me At EHLO... : Public Folder Replication Troubleshooting – Part 1: Troubleshooting the Replication of New Changes
You Had Me At EHLO... : Public Folder Replication Troubleshooting – Part 1: Troubleshooting the Replication of New Changes
Public Folder Replication Troubleshooting – Part 1: Troubleshooting the Replication of New Changes
2010/06/04
2010 個人封存
Question: PST import in the new Personal Archive: will that be possibile only through Outlook (so, 1 mbox at a time), or will an administrator be able to perform the task form the EMC?
Answer: Only through Outlook. Essentially, the user will open up the PST and drag and drop folders / items into the Archive Mailbox..
Answer: Only through Outlook. Essentially, the user will open up the PST and drag and drop folders / items into the Archive Mailbox..
Site Migration from MOSS 2007 to MOSS 2010
Site Migration from MOSS 2007 to MOSS 2010
Here is my case
Install and configure SharePoint 2010, on a new environment
- Determine hardware and software requirements (SharePoint Server 2010) http://technet.microsoft.com/en-us/library/cc262485(office.14).aspx
- Planning Logical architecture components http://technet.microsoft.com/en-us/library/cc263121(office.14).aspx
- deployment guide for Microsoft SharePoint Server 2010 http://technet.microsoft.com/en-us/library/cc262957(office.14).aspx
After installing and configuring your new SharePoint 2010,
After installing and configuring your new SharePoint 2010,
Moving Content Database from SP 2007 to SP 2010
1) Find the content Database; These are listed under Central Admin->Application Management->Site Collection List
2) Backup the content database, You could alternatively detach it, and copy it. Just doing a backup in SQL Server Management studio is easier.
3) Restore content database to new server, Copy the BAK file to new server. Create an empty DB in Management Studio, restore from backup, you may need to change an option in the "options" tab of the restore dialog to get it to work. (Overwrite db).
4) Create Web App on SharePoint 2010
5) Remove Content Database from the new web app.
Now use STSADM to add restored DB to this web app
c:\program files\common files\microsoft shared\web server extentions\14\bin on new server is where you can find the STSADM.
run this command from there. Which will upgrade the content db to 2010?
stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver
6) Run ISSRESET from command prompt
2010/06/03
2010/06/01
exchange 2007 move-mailbox
不論是搬信箱或者是搬完信箱後第一次登入OWA，都需要一些時間來等待。
開啟來源信箱，管理員必須具有原來exchange 2000的exchange 2000 full administrator.
開啟來源信箱，管理員必須具有原來exchange 2000的exchange 2000 full administrator.
2010/05/31
How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003
How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003
http://support.microsoft.com/?scid=kb%3Ben-us%3B842273&x=19&y=13
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
訂閱：
文章 (Atom)