How to expand a particular property in the powershell

When i ran a command Get-CsAdminRole -Identity "SamAccountName of the security group"
If the security group exists and the role is already created in the Lync Infrastructure, i will be able to see below output

Identity: SAMAccountName of the security group
SID: 
IsStandardRole: False
Cmdlets: {Name=Disable-CSUser, Name=Enable-CSUser, Name=Get-CSAdUser, Name=Get-CSUser...}
ConfigScopes: {Site:2}
UserScopes: {OU:ou=Name of the OU,dc=Domain,dc=com...}
Template: CSUserAdministrator

In order to see the complete output instead of three dots, we need to run the below command to expand a particular property

 Get-CsAdminRole -Identity "SamAccountName of the security group" | Select-Object -ExpandProperty userscopes

Decommission of Lync Servers

Before you decommission a deployment

• Provide users with sufficient notice to ensure that they can plan for the down time.
• Deactivate the server roles on the weekend or holiday, or during other off-peak hours.
• Disable monitoring in System Center Operations Manager or third-party monitoring system

The following checklist defines the phases of the decommissioning process in the order in which we strongly recommend that you perform the tasks:

Phase 1: Disable all users that are enabled for Lync Server

You can move existing users to a different Lync Pool or you can remove the users if the accounts are no longer needed

Phase 2: Delete all conference directories

Get-CsConferenceDirectory (This command will provide the list of conference directories and associated Lync Pool

You can find the Identity of the Lync Pool for which you are decommissioning

For eg. Remove-CsConferenceDirectory -Identity 2 -Force

If you want to move the directory, you can run the below command

For eg. Move-CsConferenceDirectory -Identity 2  -Target <DestinationServerPoolFqdn> -Force

Phase 3: Remove Voice Components as needed:

Delete all Contact objects enabled for Lync Server Enterprise Voice features by using Lync Server Management Shell.

If the Lync Server 2010 response groups have been migrated to a Lync Server 2013 deployment, do not remove the contact objects of the migrated response groups. If response groups have been migrated, skip the document “Remove Response Group Service Workflow Contact Objects” that is listed in the “Documentation” column. For more information, see http://technet.microsoft.com/en-us/library/jj204854.aspx.

Remove Enterprise Voice routes by using Lync Server Control Panel.

Remove all Call Park orbits by using Lync Server Control Panel.

Remove all tables for Enterprise Voice unassigned phone numbers.

Back up the Location Information service database.

Back up the custom music on hold file.

Delete Enterprise Voice routes.

Reassign the public switched telephone network (PSTN) gateway.

Phase 4: Confirm that the Front End Server or pool is empty.

Phase 5: Run the Remove Deployment Wizard in Topology Builder.

Phase 6: Publish the finalized topology by using Lync Server Management Shell.

Phase 7: Verify that replication is complete by using Lync Server Management Shell.

Phase 8: Remove local component files on each server by using the Deployment Wizard.

Phase 9: Publish a final, empty topology using the FinalizeUninstall parameter of Publish-CsTopology cmdlet.

Phase 10: Remove all SQL Server databases, instances, and the Central Management store by using Lync Server Management Shell.

Phase 11: (Optional) Remove any prerequisite software from the Front End Server.

Phase 12: (Optional) Remove any local groups that remain on the Front End Server.

Reference Article