Note: The credit for this explanation does not belongs to me. I got this few years ago and save on my notepad but I forget to give credit to the author. If you read this, please comment.
The conversation history you are seeing in outlook is nothing to do with your archiving. Implementing Lync/SfB along side Exchange is giving you that functionality. This is a users personal conversation history, that they can refer to and manage as they see fit – and yes it contributes to the size of their mailbox but it’s insignificant size.
An archiving server on the other hand, stores IM and conferencing data to SQL. Archiving is normally deployed if a company needs to meet regulatory requirements, or would like to archive IM data for a period of time for their own personal ‘safety net’ reasons. If a user deletes something from their personal conversation history (mailbox) it is not removed from the server side archiving.
Retention policies and configuration is used on the server side archiving to determine how long you would like to keep data in the store, and how often to purge said data etc.
Question: Are we duplicating data?
Answer: Yes, but for two very different reasons.
One is manageable by the end user, and exists for their use, reference and history purposes. The other managed by administrators and used as the ‘go to’ point regarding incidents etc. A user could send an abusive IM then delete it from his own history, the purpose of an archiving server nullifies his attempts at covering things up.
Mailbox impact is trivial regarding conversation history.
Moving Standard Lync CMS to Enterprise Lync/SfB
- Backup the CMS from Standard FE server.
- Export-CsConfiguration -Filename Customerconfig.zip
- Export-CsLisConfiguration –Filename Customerlis.zip
- Run as Administrator: Open Lync Management Shell from Enterprise Edition Server and type below.
- Install-CsDatabase –CentralManagementDatabase –UseDefaultSQL Paths -SqlServerFQDN sg-lyncdb.contoso.com –clean
- Run as Administrator: Enable from the Lync topology
- Run as Administrator: Move the CMS
- Restart both Master Replica Service and File-Transfer Agent service on Front end Servers
- Verify if CMS is installed on the EE pool
- Verify if replication is UpToDate
- Re-run “Install or Update Lync Server System” from Front end Servers
Remove the CM store files after a move
- Warning! Do not proceed if Get-CsManagementStoreReplication status isn’t UpToDate yet.
- Login to Standard FE server and remove CMS database files
- Uninstall-CsDatabase –CentralManagementDatabase –SqlServerfqdn sg-LyncTMP.contoso.com –SqlInstanceName rtc
Looks easy, isn’t it?
This guide will set the DHCP options using DHCPUtil.exe command to support Lync Phone Devices and other Lync related UC devices. Options include 1, 2, 3, 4, 5, 6, 15, 42, 119 and 120. Copy below files from Lync server C:\Program Files\Common Files\Microsoft Lync Server 2013
- Setting of Time Server and NTP Server
- Go to DHCP Scope Options -> Configure Options
- Set Option 4 Time Server
- Set Option 42 NTP Server
Note: The time server should be the PDC emulator and the NTP server is found by w32tm /query /configuration
- Setting of DHCP option 119
- R-click the IPV4 -> Set Predefined Options
- Click Add button
- Enter below details:
- Click OK.
- Option 119 should now be available from Configure Options list
- Go to DHCP Scope Options -> Configure Options
- Type contoso.com;contoso.local;contoso.com.sg at the String value section
- For DHCP Server 64-bit
- Copy the files (DHCPConfigScript.bat and DHCPUtil.exe) to temp location in DHCP server like e.g. C:\DHCPFolder
- Run from windows command shell as Administrator in DHCP server:
- C:\DHCPFolder>DHCPUtil.exe -SipServer Lyncpool.contoso.local –WebServer Lyncpool.contoso.local –RunConfigScript
- For DHCP Server 32-bit
- DHCPUtil.exe will not work with 32-bit server. So we have to run the DHCPUtil.exe command from Lync Server or any 64-bit server and paste the result to DHCP server.
- Copy the file (DHCPUtil.exe) to temp location in Lync server like e.g. C:\LyncFolder
- Copy the file (DHCPConfigScript.bat) to temp location in DHCP server like e.g. C:\DHCPFolder
- Run from windows command shell as Administrator in Lync server:
- C:\LyncFolder>DHCPUtil.exe -SipServer Lyncpool.contoso.local –WebServer Lyncpool.contoso.local
- Output looks like:
- Copy the output above from .\DHCPConfigScript.bat …..up to …37663, make sure copy as it is without deleting or adding spaces (I suggest to copy it first to notepad).
- On the 32-bit DHCP server, run the command like below:
- C:\DHCPFolder>DHCPConfigScript.bat Configure MS-UC-Client 0000….up to 7663
- Both 64 bit and 32 bit will have a result of additional options from the DHCP server like below.
Hope it helps!
You will encounter this issue when:
- The user you are trying to make change/s has elevated rights in Active Directory e.g. Domain Admins
- The account login in Lync Control Panel has lower rights compared to the user you are making change/s.
Use Lync Management Shell to make change/s on the user properties. And your account used to run Lync powershell should at least have same rights or higher.
When you are sure and confident that you have already configured DHCP server to support Lync phones however PIN authentication still not working with Polycom CX and VVX series, try to check the version of your NTP servers in the environment.
I had an issue before that AudioCodes 4xxHD phones are surprisingly working with PIN auth while Polycom CX and VVX weren’t.
Wireshark Trace from NTP version 3.
With all the NTP servers listed, all of them replied version 3 only. And from the packet, it seems the clock is not synced.
Wireshark Trace from NTP version 4
One NTP server is on version 4 and from the packet, clock has no warning.
By standard, NTP version 4 should be compatible with version 3, but for some reasons version 3 does not works well on Polycom phone. So ask your customer to setup a new NTPv4 to support your VVX or CX phones and add it to your DHCP configuration. PIN authentication should work after that.