locked
Move-csUser with parameter "-MoveToTeams" fails RRS feed

  • Question

  • Hi,

    Has anybody tested the new parameter on the Move-csUser: MoveToTeams? When you look the documentation Move-csUser It says from that parameter: "If specified, the user will be moved to Office 365 as a Teams-only user."

    But my problem is, when tested it gives quite strange issue:

    PS C:\> Move-CsUser -Identity SkypeUser02 -ProxyPool pool01.domain.net -Target sipfed.online.lync.com  -Verbose -MoveToTeams
    VERBOSE: CN=SkypeUser02,OU=Accounts,DC=domain,DC=net

    Confirm
    Move-CsUser
    [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"):
    VERBOSE: Validating parameters for move operation.
    VERBOSE: Calculating new server information for user [sipfed.online.lync.com].
    Move-CsUser : A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
    At line:1 char:1
    + Move-CsUser -Identity SkypeUser02 -ProxyPool pool01.domain.net -Target  ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (CN=SkypeUser02...C=domain,DC=net:OCSADUser) [Move-CsUser], SqlConnectionException
        + FullyQualifiedErrorId : MoveError,Microsoft.Rtc.Management.AD.Cmdlets.MoveOcsUserCmdlet

    There should be no single reasons to look the SQL server on this case. Also, when taking the network trace, I could see pretty normal SQL traffic to the BackEnd of ProxyPool's BE. Anybody success with this?


    Petri

    Wednesday, September 4, 2019 4:18 PM

All replies

  • Hi Petri,

    Do you deploy hybrid connectivity between Skype for Business server and Skype for Business Online?

    What is your Skype for Business version?

    The MoveToTeams switch is only available on Skype for Business Server 2019 and Skype for Business Server 2015 CU8 later.

    In the article, we use the following command:

    $cred=get-credential

    Move-CsUser -Identity "PilarA@contoso.com" -Target "sipfed.online.lync.com" -MoveToTeams -Credential $cred

    I don’t find the parameter ProxyPool in Move-CsUser command.

    In addition, you could try to move the user in Control Panel. You can refer to the following link:

    https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/move-users-from-on-premises-to-teams


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, September 5, 2019 2:50 AM
  • Hi Sharon,

    Great that you pointed that! Indeed, the documenation does not speak about the proxy pool. But if you take "get-help move-csuser" it says:

    " -ProxyPool <Fqdn>
         This parameter is used only for Skype for Business Server 2015. It should not be used with an on-premises implementation of Skype for Business Server 2015.
    "

    If I run the move-csuser without -proxyPool I get the following error:

    Move-CsUser : Multiple federated Edge Servers have been defined in the current topology. Specify the ProxyPool parameter to indicate which Registrar pool should be used to proxy this user for
    deployments running earlier versions. Edge Server FQDNs found:"SfBEdgeSiteA.domain.net, SfBEdgeSiteB.domain.net"

    So that seems to be still required.

    Looks like the documentation is not correct for move-csuser.


    Petri

    Thursday, September 5, 2019 7:24 AM
  • Hi Petri,

    In my research, if the environment still has legacy Edge servers deployed and they are the primary route for federation.

    According to your error, it maybe related to the SQL server. Please refer to the following thread: https://social.technet.microsoft.com/Forums/en-US/b43775b9-cd96-4f14-bd1e-b40172c5fc83/a-networkrelated-or-instancespecific-error-occurred-while-establishing-a-connection-to-sql-server?forum=sqlsecurity

    You could create a new account and have a try to move it.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 6, 2019 10:02 AM
  • Hi Petri,

    Is there any update on this case?

    Please feel free to drop us a note if there is any update.

    Have a nice day!



    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, September 12, 2019 9:12 AM