Export Lync User Configuration (former DBIMPEXP)

-
You for your information, with Lync 2013 some former tools are depreciated.

While in LCS, OCS and Lync 2010 exporting the user data was done with the dbimpexp.exe utility.

Now with Lync 2013 new EXPORT-CSxxx commands are integrated within the Lync Management Shell.

Convert-CsUserData
Import-CsUserData
Sync-CsUserData
Update-CsUserData

As we now from former days, we had to use DBIMPEXP to extract the user data, e.g. the Lync buddy list, to export data directly out of the RTC database.

Lync 2013 made the export functions more convenient and added PowerShell commands to do a more simplified export. With this EXPORT-CSxxx commands, you can export:
  • User Data
  • Conference Directories
  • LIS (Location Information Service) - E911 Data
  • RGS - Response Group Data
  • Persistent Chat Data

With the Convert-CsUserData command, you are able to convert former XML formats into the actual Lync 2013 format. But if you need to convert Lync 2013 data backward to Lync 2010, you need to do this during the Export-CsUserData command with the option parameter: -LegacyFormat

Other helpful parameter are:
-UserFilter: filter for dedicated user or bulk users
-ConfDirectoryFilter : Filter for Conference Directories, with you should first identity with Get-CsConferenceDirectory and than use the number display as the identifier.

NOTE/ WARNING:
The Export-CsUserData command also exports Lync Application User.
If you for example had a deployment, where you changed the default SIP domain and deleted this default SIP domain (Which by the way is UNSUPPORTED), you will have to clean up the XML file or you make sure, that only Lync Users are exported, which you need for this.

Best Practice:
You run a command and export the User names:
Get-CsUser | fl *sip* > C:\CsUser.txt
and
Export-CsUserData -PoolFqdn "frontend.pool.fqdn" -FileName C:\UserDataExport.zip
Than if you import, do so selective, that means write a script, which will use the CsUser.txt to import only the user you need and make sure you excluded the Lync Application users.
Make sure the txt file has the SIP identifier in first row.
SIP
usera@sip.com
userb@sip.com

Import-csv C:\scripts\CsUser.txt | ForEach-Object {Import-CsUserData -PoolFqdn "frontend.pool.fqdn" -FileName C:\UserDataExport.zip -UserFilter $_.SIP}

Comments

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modify the AD hide at
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more