none
Cannot access Lync Powershell mobility cmdlets using PS remoting

    Question

  • Hi there,

    I've followed the process of configuring Powershell remoting to allow our Help Desk to administer Lync remotely. http://blogs.technet.com/b/ilvancri/archive/2010/11/25/using-remote-powershell-to-connect-to-lync.aspx 

    This all works fine, and all typical Lync PS cmdlets functions are accessible... except for anything to do with Lync Mobility: ie. grant-csmobilitypolicy or get-csmobilitypolicy

    For some reasons, these command just don't appear to be accessible. I'm not sure whether it's because they came later in CU4. I need to allow our Help Desk to assign these policies, and of course MS don't provide a mechanism to do it via the Control Panel which just leaves PowerShell, and I don't want to allow them logon access to the Lync servers themselves.

    Does anyone have any ideas why Lync Mobility cmdlets would be inaccessible via PowerShell remoting?

    Regards, James


    James Frost

    Monday, April 16, 2012 2:11 PM

All replies

  • Hi,

    I find I also can not use the mobility cmdlets in remote powershell. Looks like the lync server did not add the mobility cmdlets to the ocspowershell. I will have a try to find a way to add the mobility cmdlets to the ocspowershell.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, April 18, 2012 10:03 AM
  • What is the error you are getting?
    Thursday, April 19, 2012 11:49 PM
  • Hi,

    Looks the powershell didnot recognize the cmdlets:

    The term 'Get-CsMobilityPolicy' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, April 20, 2012 4:20 AM
  • Going to open a ticket with PSS, as I need to get this working. Will you keep posted.

    James Frost

    Saturday, April 21, 2012 1:05 AM
  •  

    Yes just to back you up, I am experiencing exactly the same behaviour. ie all std Lync PS commands work fine but mobility commands fail.

    eg The term 'Grant-CsMobilityPolicy' is not recognized as the name of a cmdlet, function, script file, or operable program. ....

    Please let me know if you get an answer from PSS

    (Running commands locally on the server is fine, but issues occur when remoting to the server)


    Alistair

    Monday, April 23, 2012 3:24 PM
  • Response from PSS:

    Actually, this is an known issue for Lync Mobility Component, the Fix will be contained in Lync 2010 CU6 release.

    Resolution shouldn't be far away hopefully. Thx


    James Frost

    Wednesday, May 02, 2012 1:49 PM
  • Update: PSS have just confirmed this wasn't fixed in the last release of CU6 (sigh).

    James Frost

    Monday, July 02, 2012 8:08 AM
  • Hi,

    For information, the cmdlet "Grant-CsMobilityPolicy" is working fine from a remote PSSession now after the installation of CU9 on Lync2010.

    It also works fine with Lync2013 RTM.

    You must also give required permissions using "Update-CsAdminRole" cmdlet to the user that will use the cmdlet.

    Best Regards

    Friday, September 27, 2013 9:02 AM