1.Check the Lync pool A record and SRV record (_sipinternalts) in the DNS .
2.Go to Internet Information Services (IIS) Manager, click Edit Bindings on Lync Server Internal Web Site. 
2012年4月23日 星期一
Lync Server 2010 Control panel not loading (Navigation to the webpage was canceled)
2012年4月13日 星期五
This slide couldn't be downloaded. Please contact...., Error reason: Name not resolved
Another features: A/V conf, desktop sharing, whiteboard still works. When two external client (different LAN) trying to share a PPT slide, sender can see notification about uploading success and see the slide, another one got an error:
"This slide couldn't be downloaded. Please contact...., Error reason: Name not resolved"
I've resolved my problem by doing these step:
1.Get right permission for share folder on front end.
2.Reconfigure DNS record for external-web (you can get its name from topo builder)
3.Open requirement ports.
"This slide couldn't be downloaded. Please contact...., Error reason: Name not resolved"
I've resolved my problem by doing these step:
1.Get right permission for share folder on front end.
2.Reconfigure DNS record for external-web (you can get its name from topo builder)
3.Open requirement ports.
2012年4月6日 星期五
Lync External Web Services without Reverse Proxy
While working on a Lync deployment for a small customer, it came up during the planning stages that they didn't have a reverse proxy server (like ISA/TMG) to publish the Meet/Dialin simple URLs and web components URL, nor were they planning to. In the past, I had tried to make OCS work without a reverse proxy, but some things just didn't work right. After advising them about the risks involved with opening up an internal domain-joined computer to the Internet, I told them I would try to make Lync work without a reverse proxy, but cautioned that it may not work.
During Lync installation, it creates two web sites: Lync Server Internal Web Site and Lync Server External Web Site. As the names suggest, each website is configured for either internal or external access. The internal site is published on ports 80/443, while the external site is published on 8080/4443. Microsoft's documentation says you should use a reverse proxy server to publish the external simple URLs and web components URL and redirect ports 80/443 from the web to the internal Lync server over 8080/4443.
After a few unsuccessful tries at making their firewall proxy 80/443 to 8080/4443, I thought I would try to configure their front-end server with an additional IP address, and setup the Lync Server External Web Site with 80/443 on the new IP address. We updated the firewall rules to redirect 80/443 from the simple URL and web components URL external IP addresses to the new internal IP address over 80/443. We tested external client address book downloading, meeting/dialin URL access, and meeting content downloading. All worked without issue.
Before going the route of adding a new IP address, try to make your firewall redirect 80/443 to 8080/4443. If it works, then you don't have to create the new IP. Please note, if you add any additional components, like the Lync Mobility Service, you may have to reset the ports because it seems that the setup process resets the ports back to 8080/4443.
During Lync installation, it creates two web sites: Lync Server Internal Web Site and Lync Server External Web Site. As the names suggest, each website is configured for either internal or external access. The internal site is published on ports 80/443, while the external site is published on 8080/4443. Microsoft's documentation says you should use a reverse proxy server to publish the external simple URLs and web components URL and redirect ports 80/443 from the web to the internal Lync server over 8080/4443.
After a few unsuccessful tries at making their firewall proxy 80/443 to 8080/4443, I thought I would try to configure their front-end server with an additional IP address, and setup the Lync Server External Web Site with 80/443 on the new IP address. We updated the firewall rules to redirect 80/443 from the simple URL and web components URL external IP addresses to the new internal IP address over 80/443. We tested external client address book downloading, meeting/dialin URL access, and meeting content downloading. All worked without issue.
Before going the route of adding a new IP address, try to make your firewall redirect 80/443 to 8080/4443. If it works, then you don't have to create the new IP. Please note, if you add any additional components, like the Lync Mobility Service, you may have to reset the ports because it seems that the setup process resets the ports back to 8080/4443.
Microsoft Lync Server Public IM Connectivity Provisioning
雖然目前Microsoft Lync PIM服務是免費的,如需要此整合服務,還是要到下列網站提出申請才行喔!
Microsoft Lync Server Public IM Connectivity Provisioning
https://pic.lync.com/provision/Logon/Logon.aspx?rret=https%3a%2f%2fpic.lync.com%2fprovision%2fAgreementNumber.aspx
Microsoft Lync Server Public IM Connectivity Provisioning
https://pic.lync.com/provision/Logon/Logon.aspx?rret=https%3a%2f%2fpic.lync.com%2fprovision%2fAgreementNumber.aspx
Ignore Offline CRL Errors on the CA
Normally, a Windows Server 2003 CA will always check revocation on all certificates in the PKI hierarchy (except the root CA certificate) before issuing an end-entity certificate.
You have imported the CA root to the Lync-edge server, and You can see the detail in the Certificate Store under Trusted Root CA.
You generated the certificate for the internal interface, have it signed, and then assigned it. You got the Error Message
There are two possibilities to get this Error working:
- Recommended: Modify your CA Configuration to include a HTTP CRL Publishing point, publish the CRL to this location and request a new certificate for the internal Lync server with this new CRL location. Make sure that the edge server can download the CRL from this location
- Disable CRL checking on the Edge server. By doing this, you configure the system to no longer check CRL's for certificate revocation. While this is not a recommended practice from a security perspective, it will work.
Or You can try disabling it in IE advanced properties ("Check for publishers certificate revocation" option) and reboot the server and see if it has any affect on lync
The other way to disable this feature, use the following command on the CA, and then restart the CA service:
certutil –setreg ca\CRLFlags +CRLF_REVCHECK_IGNORE_OFFLINE
You have imported the CA root to the Lync-edge server, and You can see the detail in the Certificate Store under Trusted Root CA.
You generated the certificate for the internal interface, have it signed, and then assigned it. You got the Error Message
There are two possibilities to get this Error working:
- Recommended: Modify your CA Configuration to include a HTTP CRL Publishing point, publish the CRL to this location and request a new certificate for the internal Lync server with this new CRL location. Make sure that the edge server can download the CRL from this location
- Disable CRL checking on the Edge server. By doing this, you configure the system to no longer check CRL's for certificate revocation. While this is not a recommended practice from a security perspective, it will work.
Or You can try disabling it in IE advanced properties ("Check for publishers certificate revocation" option) and reboot the server and see if it has any affect on lync
The other way to disable this feature, use the following command on the CA, and then restart the CA service:
certutil –setreg ca\CRLFlags +CRLF_REVCHECK_IGNORE_OFFLINE
2012年4月4日 星期三
INSUFF_ACCESS_RIGHTS Error
在Lync Control Panel管理介面上,當執行新增使用者帳號會有下面的錯誤訊息:
“Insufficient access rights to perform the operation 00002098: SecErr:DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0″
解決方法:
You have to go to Active Directory Users and Computers (with Advanced Features turned on in the View Menu), then go to Properties on the User that you can't enable on Lync, and in the Security tab, clic on Advanced. Then check "Include Inheritable Permissions from this object’s parent", accept and the problem will be instantly solved.
“Insufficient access rights to perform the operation 00002098: SecErr:DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0″
解決方法:
You have to go to Active Directory Users and Computers (with Advanced Features turned on in the View Menu), then go to Properties on the User that you can't enable on Lync, and in the Security tab, clic on Advanced. Then check "Include Inheritable Permissions from this object’s parent", accept and the problem will be instantly solved.
2012年3月31日 星期六
Publishing the Lync Sever EE topology failed
中央管理儲存區 (CMS) 資料庫建立執行在Lync Server後端的SQL Server上,當拓樸設定完成後,正當要發布拓樸時,執行過程中就會發生失敗,並且在Log上回傳下列的錯誤訊息：
發生的原因:
主要是後端SQL Server上的本機Windows防火牆擋住遠端服務連結的通訊埠所造成
解決方法請參照下列步驟,在本機 Windows 防火牆中開啟通訊埠以便存取:
1.在 [控制台] 中，開啟 [網路連線]、以滑鼠右鍵按一下使用中連線，然後按一下 [內容]。
2.按一下 [進階] 索引標籤，然後再按一下 [Windows 防火牆設定]。
3.在 [Windows 防火牆] 對話方塊中，按一下 [例外狀況] 索引標籤，然後按一下 [加入通訊埠]。
4.在 [加入通訊埠] 對話方塊的 [名稱] 方塊中，輸入 SQL Server。
5.在 [通訊埠號碼] 文字方塊中，輸入 Database Engine 執行個體的通訊埠編號，例如預設執行個體的通訊埠編號是 1433。
6.確認已選取 [TCP]，然後按一下 [確定]。
7.若要開啟通訊埠以便公開 SQL Server Browser 服務，請按一下 [加入通訊埠]，在 [名稱] 文字方塊中輸入 SQL Server Browser，在 [通訊埠編號] 文字方塊中輸入 1434，選取 [UDP]，然後按一下 [確定]。
8.關閉 [Windows 防火牆] 和 [內容] 對話方塊。
發生的原因:
主要是後端SQL Server上的本機Windows防火牆擋住遠端服務連結的通訊埠所造成
解決方法請參照下列步驟,在本機 Windows 防火牆中開啟通訊埠以便存取:
1.在 [控制台] 中，開啟 [網路連線]、以滑鼠右鍵按一下使用中連線，然後按一下 [內容]。
2.按一下 [進階] 索引標籤，然後再按一下 [Windows 防火牆設定]。
3.在 [Windows 防火牆] 對話方塊中，按一下 [例外狀況] 索引標籤，然後按一下 [加入通訊埠]。
4.在 [加入通訊埠] 對話方塊的 [名稱] 方塊中，輸入 SQL Server
5.在 [通訊埠號碼] 文字方塊中，輸入 Database Engine 執行個體的通訊埠編號，例如預設執行個體的通訊埠編號是 1433。
6.確認已選取 [TCP]，然後按一下 [確定]。
7.若要開啟通訊埠以便公開 SQL Server Browser 服務，請按一下 [加入通訊埠]，在 [名稱] 文字方塊中輸入 SQL Server Browser，在 [通訊埠編號] 文字方塊中輸入 1434，選取 [UDP]，然後按一下 [確定]。
8.關閉 [Windows 防火牆] 和 [內容] 對話方塊。
2012年3月29日 星期四
Spesified SIP domain (SipDomain) is not valid. Specify a valid SIP domain and then try again
預設的SIP網域跟對外E-Mail不一樣時,在啟用Lync帳號時,就會產生下列錯誤
接著透過拓樸產生器,再新增一筆其他支援的SIP網域,重新啟用帳號時,錯誤訊息就不再產生
接著透過拓樸產生器,再新增一筆其他支援的SIP網域,重新啟用帳號時,錯誤訊息就不再產生
Lync Server 2010 Setup or Remove Lync Components fails on Windows Server 2008 R2 SP1
在執行安裝或者移除 Lync 元件時,會有如下的錯誤訊息
針對錯誤訊息展開後的詳細內容如下
造成的原因
The Lync Server 2010 Setup or Remove Component installation prerequisite check cannot locate the Server 2008 R2 SP1 version of Microsoft Windows Media Format.
解決方法
To resolve this problem, install Windows Desktop Experience. To do this, follow these steps:
1.Click Start, click Administrative Tools, and then double-click Server Manager
2.In Server Manager, click Add Features under Features Summary
3.In the Add Features Wizard dialog box, make sure that the Desktop Experience option is selected
4.Click Next, and then click Install
5.After the installation process is complete, click Close, and then close Server Manager
Note After you install Windows Desktop Experience, you must restart the computer
或者參考下列資料
http://support.microsoft.com/kb/2522454
針對錯誤訊息展開後的詳細內容如下
造成的原因
The Lync Server 2010 Setup or Remove Component installation prerequisite check cannot locate the Server 2008 R2 SP1 version of Microsoft Windows Media Format.
解決方法
To resolve this problem, install Windows Desktop Experience. To do this, follow these steps:
1.Click Start, click Administrative Tools, and then double-click Server Manager
2.In Server Manager, click Add Features under Features Summary
3.In the Add Features Wizard dialog box, make sure that the Desktop Experience option is selected
4.Click Next, and then click Install
5.After the installation process is complete, click Close, and then close Server Manager
Note After you install Windows Desktop Experience, you must restart the computer
或者參考下列資料
http://support.microsoft.com/kb/2522454
2011年11月12日 星期六
使用AD GPO部署Lync Client
解決方法：
透過Windows Active Directory Domain的Group Policy來部署Lync Client有下列三大步驟：
* 取得Lync.msi的封裝檔案
* 替需要部署的用戶端新增加UseMSIForLyncInstallation (DWORD)的Registry Key
* 建立Windows Active Directory GPO部署Lync.msi檔案
另外,您可以參考下列整理的參考資訊：
取得Lync.msi的封裝檔案：
請先找一台Windows Client安裝完整的Lync Client軟體，完成安裝後，可以在%Program Files%\OCSetup\ 或 %Program Files(x86)%\OCSetup 的目錄中取得Lync.msi的封裝檔案。
替用戶端增加Registry Key以允許Lync.msi封裝檔的部署：
請參考知識庫文件中的說明：http://support.microsoft.com/kb/2477965/en-us 替每一台需要部署Lync Client的Windows用戶端新增加UseMSIForLyncInstallation (DWORD)值為1的Registry Key。
您可以參考下列文件為每一台Windows Client增加上述的Registry Key。
How to add, modify, or delete registry subkeys and values by using a registration entries (.reg) file
http://support.microsoft.com/kb/310516/en-us
Distributing Registry Changes
http://technet.microsoft.com/en-us/library/bb727154.aspx
透過Active Directory Group Policy部署Lync.msi：
透過AD GPO部署應用程式的作法您可以參考下列知識庫文件中的說明：
How to use Group Policy to remotely install software in Windows Server 2003 and in Windows Server 2008
http://support.microsoft.com/kb/816102/en-us
How to use Windows Installer and Group Policy to deploy the VPModule.msi in an Active Directory domain
http://support.microsoft.com/kb/887405/en-us (請將此案例中的VPModule.msi替換成Lync.msi)
How to assign software to a specific group by using Group Policy
http://support.microsoft.com/kb/302430/en-us
透過Windows Active Directory Domain的Group Policy來部署Lync Client有下列三大步驟：
* 取得Lync.msi的封裝檔案
* 替需要部署的用戶端新增加UseMSIForLyncInstallation (DWORD)的Registry Key
* 建立Windows Active Directory GPO部署Lync.msi檔案
另外,您可以參考下列整理的參考資訊：
取得Lync.msi的封裝檔案：
請先找一台Windows Client安裝完整的Lync Client軟體，完成安裝後，可以在%Program Files%\OCSetup\ 或 %Program Files(x86)%\OCSetup 的目錄中取得Lync.msi的封裝檔案。
替用戶端增加Registry Key以允許Lync.msi封裝檔的部署：
請參考知識庫文件中的說明：http://support.microsoft.com/kb/2477965/en-us 替每一台需要部署Lync Client的Windows用戶端新增加UseMSIForLyncInstallation (DWORD)值為1的Registry Key。
您可以參考下列文件為每一台Windows Client增加上述的Registry Key。
How to add, modify, or delete registry subkeys and values by using a registration entries (.reg) file
http://support.microsoft.com/kb/310516/en-us
Distributing Registry Changes
http://technet.microsoft.com/en-us/library/bb727154.aspx
透過Active Directory Group Policy部署Lync.msi：
透過AD GPO部署應用程式的作法您可以參考下列知識庫文件中的說明：
How to use Group Policy to remotely install software in Windows Server 2003 and in Windows Server 2008
http://support.microsoft.com/kb/816102/en-us
How to use Windows Installer and Group Policy to deploy the VPModule.msi in an Active Directory domain
http://support.microsoft.com/kb/887405/en-us (請將此案例中的VPModule.msi替換成Lync.msi)
How to assign software to a specific group by using Group Policy
http://support.microsoft.com/kb/302430/en-us
2011年7月14日 星期四
Error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. (Exception from HRESULT: 0x800B0109)
You may get this error during certificate request/assign.
Error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. (Exception from HRESULT: 0x800B0109)
Install the Root CA cert chain on the server and run the wizard again to resolve the problem.
Error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. (Exception from HRESULT: 0x800B0109)
Install the Root CA cert chain on the server and run the wizard again to resolve the problem.
Lync 2010 Server Control Panel returns that error "Insufficient access rights to perform the operation" when attempting a move user or enable user command
When using the Lync 2010 Server Control Panel to enable or move an Active Directory, directory service domain user for use with Lync Server 2010 the following errors are returned:
Active Directory operation failed on "DC1.contoso.com". You cannot retry this operation: "Insufficient access rights to perform the operation"
The error that is described in the SYMPTOMS section of this article is caused by the combination of the following two reasons:
*The user account that is part of the Lync 2010 Server move or enable operation is a member of an Active Directory, directory service protected domain security group. Since the user account belongs to a protected domain security group it is unable to keep the RTCUniversalUserAdmins and RTCuniversalUserReadOnlyGroup Universal Security groups and their permissions as Access Control Entries (ACEs) to the protected domain security group's default Access Control List (ACL).
*The Lync 2010 Server Control Panel is not designed to delegate the permissions that are needed to complete the user account move or enable operation
Use the Lync Server Management shell to administer the following Lync 2010 Server PowerShell cmdlets to perform the user account enable of move operations:
Enable-CsUser -Identity "Bill Anderson" -RegistrarPool "pool01.contoso.com" -SipAddressType EmailAddress -SipDomain contoso.com
To view a list of examples for the usage of the Enable-CsUser Lync Server 2010 PowerShell cmdlet use the Lync Management Shell and enter the following PowerShell cmdlet: Get-Help Enable-CsUser -Examples
Move-CsUser -Identity "Bill Anderson" -Target "pool01.contoso.com"
To view a list of examples for the usage of the Move-CsUser Lync Server 2010 PowerShell cmdlet use the Lync Management Shell and enter the following PowerShell cmdlet: Get-Help Move-CsUser -Examples
Move-CsLegacyUser -Identity "Bill Anderson" -Target "pool01.contoso.com"
To view a list of examples for the usage of the Move-CsLegacyUser Lync Server 2010 PowerShell cmdlet use the Lync Management Shell and enter the following PowerShell cmdlet: Get-Help Move-LegacyCsUser -Examples
KB2466000
Active Directory operation failed on "DC1.contoso.com". You cannot retry this operation: "Insufficient access rights to perform the operation"
The error that is described in the SYMPTOMS section of this article is caused by the combination of the following two reasons:
*The user account that is part of the Lync 2010 Server move or enable operation is a member of an Active Directory, directory service protected domain security group. Since the user account belongs to a protected domain security group it is unable to keep the RTCUniversalUserAdmins and RTCuniversalUserReadOnlyGroup Universal Security groups and their permissions as Access Control Entries (ACEs) to the protected domain security group's default Access Control List (ACL).
*The Lync 2010 Server Control Panel is not designed to delegate the permissions that are needed to complete the user account move or enable operation
Use the Lync Server Management shell to administer the following Lync 2010 Server PowerShell cmdlets to perform the user account enable of move operations:
Enable-CsUser -Identity "Bill Anderson" -RegistrarPool "pool01.contoso.com" -SipAddressType EmailAddress -SipDomain contoso.com
To view a list of examples for the usage of the Enable-CsUser Lync Server 2010 PowerShell cmdlet use the Lync Management Shell and enter the following PowerShell cmdlet: Get-Help Enable-CsUser -Examples
Move-CsUser -Identity "Bill Anderson" -Target "pool01.contoso.com"
To view a list of examples for the usage of the Move-CsUser Lync Server 2010 PowerShell cmdlet use the Lync Management Shell and enter the following PowerShell cmdlet: Get-Help Move-CsUser -Examples
Move-CsLegacyUser -Identity "Bill Anderson" -Target "pool01.contoso.com"
To view a list of examples for the usage of the Move-CsLegacyUser Lync Server 2010 PowerShell cmdlet use the Lync Management Shell and enter the following PowerShell cmdlet: Get-Help Move-LegacyCsUser -Examples
KB2466000
Lync Server Installation Error: Prerequisite installation failed: Wmf2008R2
Trying to Install Lync 2010 on Server 2008 R2 SP1, the installation failed with the following error while adding the first Lync Server Components:
“C:\Windows\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum” Cannot be found.
I looked for that file. It’s no where to be found. But it looks like it has a different version:
%systemroot%\system32\dism.exe /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.mum
I copied the file name mentioned in the error message, changed both file names (both .cat and .mum, didn’t know if they need each other during installation) and tried installing again.That Solved the problem. YA!!!
The official workaround for this issue has been released in Microsoft KB2522454
“C:\Windows\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum” Cannot be found.
I looked for that file. It’s no where to be found. But it looks like it has a different version:
%systemroot%\system32\dism.exe /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.mum
I copied the file name mentioned in the error message, changed both file names (both .cat and .mum, didn’t know if they need each other during installation) and tried installing again.That Solved the problem. YA!!!
The official workaround for this issue has been released in Microsoft KB2522454
2011年4月28日 星期四
Understanding the Lync Server 2010 Planning Tool
The Microsoft Lync Server 2010 Planning Tool helps design Lync Server 2010 deployments. A new feature of the Lync Server Planning Tool gives you the ability to design a virtualized server environment as well as physical deployments. There has been some confusion on the output generated by the Planning Tool. This article discusses some issues with the tool and how to interpret the data generated. It also highlights other tools to help with your designs.
Understanding the Lync Server 2010 Planning Tool
Understanding the Lync Server 2010 Planning Tool
2011年4月22日 星期五
Enable presence status “Appear Offline”
透過 PowerShell 在 Lync Server 上,執行下列指令來啟用 Lync Client "Appear Offline" 的狀態
Set-CsClientPolicy -EnableAppearOffline $true
Get-CsClientPolicy
Set-CsClientPolicy -EnableAppearOffline $true
Get-CsClientPolicy
Lync Database Creation Error
安裝佈署 Lync Server 的 Monitoring Server role 時,安裝過程中,且在建立新增資料庫時,會發生如下的錯誤訊息,
Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft
Lync Server 2010\DbSetup\RtcCdrDbSetup.wsf" /sqlserver:sql.schertz.local\lync
/serveracct:SCHERTZ\RTCComponentUniversalServices /dbpath:C:\CsData\MonitoringStore\
lync\dbpath /logpath:C:\CsData\MonitoringStore\lync\logpath /logsize:1024 /verbose
—————
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on sql.schertz.local\lync
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
Opened database LcsCDR
Db version unknown. Clean install required.
(Major upgrade of database required.)
Due to schema changes this database cannot be re-used. It must be dropped and a new one created.
To preserve data, you must use this product’s backup/export restore/import solution. Examine the product documentation for instructions.
—————
Exit code: ERROR_NEED_MAJOR_UPGRADE_USE_IMP_EXP (-50)
—————
解決方法:
■ 執行 Topology Builder 並且從 Topology Builder 移除 Monitoring Server Role ,移除後關閉 Topology Builder 套用更改後的設定
■ 連線 SQL server 在 SQL Management Studio 上尋找並且移除 LcsCDR and QoEMetrics 特定的 DB
■ 重新執行 Topology Builder ,並且重新選擇安裝 Monitoring Server Role ,此時安裝過程順利進行,之前 SQL ‘Db server unknown’ 的錯誤訊息也不在發生
Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft
Lync Server 2010\DbSetup\RtcCdrDbSetup.wsf" /sqlserver:sql.schertz.local\lync
/serveracct:SCHERTZ\RTCComponentUniversalServices /dbpath:C:\CsData\MonitoringStore\
lync\dbpath /logpath:C:\CsData\MonitoringStore\lync\logpath /logsize:1024 /verbose
—————
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on sql.schertz.local\lync
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
Opened database LcsCDR
Db version unknown. Clean install required.
(Major upgrade of database required.)
Due to schema changes this database cannot be re-used. It must be dropped and a new one created.
To preserve data, you must use this product’s backup/export restore/import solution. Examine the product documentation for instructions.
—————
Exit code: ERROR_NEED_MAJOR_UPGRADE_USE_IMP_EXP (-50)
—————
解決方法:
■ 執行 Topology Builder 並且從 Topology Builder 移除 Monitoring Server Role ,移除後關閉 Topology Builder 套用更改後的設定
■ 連線 SQL server 在 SQL Management Studio 上尋找並且移除 LcsCDR and QoEMetrics 特定的 DB
■ 重新執行 Topology Builder ,並且重新選擇安裝 Monitoring Server Role ,此時安裝過程順利進行,之前 SQL ‘Db server unknown’ 的錯誤訊息也不在發生
SQL Server Error During Lync Install
在安裝 Lync Server 的過程中,會發生如下的錯誤訊息,也就是 ERROR_VALIDATE_BAD_SQL_VERSION
Error: Script failed (code "ERROR_VALIDATE_BAD_SQL_VERSION") when installing "CentralMgmtStore" on "N-HCLT-LYNCSQL.hclt.corp.hcl.in". For details, see the following log file: "C:\Users\hcltocs\AppData\Local\Temp\Create-CentralMgmtStore-N-HCLT-LYNCSQL.hclt.corp.hcl.in-[2010_10_18][14_11_55].log"
Error: An error occurred: "Microsoft.Rtc.Common.Data.SqlConnectionException" "Cannot open database "xds" requested by the login. The login failed.
Login failed for user 'HCLTECH\hcltocs'."
而發生上述的問題,主要是Lync Server 後端的 SQL Server 有相對應的版本,也就是安裝時選擇的後端 SQL Server 版本目前不支援 Lync Server,而目前 Lync Server 支援的 SQL Server 版本如下,提供給各位參考.
*Standard or Enterprise Edition of SQL Server 2005 with Service Pack 3
*Standard or Enterprise Edition of SQL Server 2008 with Service Pack 1
Error: Script failed (code "ERROR_VALIDATE_BAD_SQL_VERSION") when installing "CentralMgmtStore" on "N-HCLT-LYNCSQL.hclt.corp.hcl.in". For details, see the following log file: "C:\Users\hcltocs\AppData\Local\Temp\Create-CentralMgmtStore-N-HCLT-LYNCSQL.hclt.corp.hcl.in-[2010_10_18][14_11_55].log"
Error: An error occurred: "Microsoft.Rtc.Common.Data.SqlConnectionException" "Cannot open database "xds" requested by the login. The login failed.
Login failed for user 'HCLTECH\hcltocs'."
而發生上述的問題,主要是Lync Server 後端的 SQL Server 有相對應的版本,也就是安裝時選擇的後端 SQL Server 版本目前不支援 Lync Server,而目前 Lync Server 支援的 SQL Server 版本如下,提供給各位參考.
*Standard or Enterprise Edition of SQL Server 2005 with Service Pack 3
*Standard or Enterprise Edition of SQL Server 2008 with Service Pack 1
2011年2月5日 星期六
Migration from Office Communications Server 2007 R2 to Lync Server 2010
Before You Begin the Migration
Phase 1: Plan Your Migration from Office Communications Server 2007 R2
Phase 2: Prepare for Migration
Phase 3: Deploy Lync Server 2010 Pilot Pool
Phase 4: Merge Topologies
Phase 5: Configure the Pilot Pool
Phase 6: Verify Your Pilot Migration
Phase 7: Add Lync Server 2010 Edge Server and Director to Pilot Pool
Phase 8: Move from Pilot Deployment into Production
Phase 9: Complete Post-Migration Tasks
Phase 10: Decommission Legacy Site
Migrate Using Lync Server 2010 Management Shell (optional)
Phase 1: Plan Your Migration from Office Communications Server 2007 R2
Phase 2: Prepare for Migration
Phase 3: Deploy Lync Server 2010 Pilot Pool
Phase 4: Merge Topologies
Phase 5: Configure the Pilot Pool
Phase 6: Verify Your Pilot Migration
Phase 7: Add Lync Server 2010 Edge Server and Director to Pilot Pool
Phase 8: Move from Pilot Deployment into Production
Phase 9: Complete Post-Migration Tasks
Phase 10: Decommission Legacy Site
Migrate Using Lync Server 2010 Management Shell (optional)
2011年1月30日 星期日
Lync Server 2010 相關授權的參考資訊
Lync Server 2010 提供了下列兩種版本：
在 Lync Server 2010 的用戶端存取授權則有下列三種類型：
與先前 OCS 2007 R2 的授權比較如下圖內容所示：
任何一種用戶端存取授權 (Lync CAL) 都可以在 Lync Server 2010 的 Enterprise or Standard 伺服器上運作,您可以參考如下圖內容所示：
而您可以參考官方網址中的說明：Microsoft Lync Licensing
在 Lync Server 2010 的用戶端存取授權則有下列三種類型：
與先前 OCS 2007 R2 的授權比較如下圖內容所示：
任何一種用戶端存取授權 (Lync CAL) 都可以在 Lync Server 2010 的 Enterprise or Standard 伺服器上運作,您可以參考如下圖內容所示：
而您可以參考官方網址中的說明：Microsoft Lync Licensing
2010年11月25日 星期四
訂閱：
文章 (Atom)
-
錯誤訊息如下: 解決方法: 試試看檢查下面幾項動作 1.Netlogon Service有沒有啟動或者服務重新啟動 2.是否有此值 HKLM\System\CCS\Services\NTDS\Parameters 底下的 "DSA Not Writable... -
當在更新 Exchange 2010 SP1 時,會產生下列錯誤訊息,而造成無法繼續更新 SP1,錯誤訊息如下: Some controls aren't valid. Setup previously failed while performing the act...