none
New User not validly homed on target when setting PIN RRS feed

  • Question

  • This goes back to an issue that existed on Lync 2013 from this thread:

    https://social.technet.microsoft.com/Forums/lync/en-US/3b053fc9-08f1-4c79-a3ba-d2e410571bae/user-not-validly-homed-lync-2013?forum=lyncdeploy

    When creating a new user as part of a new user script, and trying to set the PIN this seems to happen. 

    Command: Set-CsClientPin -identity 'newuser' -pin 1234

    Error: User xyz@contoso.com is not validly homed on target 'poolname'.

    It works after waiting several minutes.

    Is there any command to run beforehand to push it along, or an expected wait time before setting the PIN?

    Thursday, November 10, 2016 11:13 PM

All replies

  • Hi Adam,

    I think you are looking for Start-Sleep

    https://technet.microsoft.com/en-us/library/ee177002.aspx

    Hope this helps,

    Mvh

    Friday, November 11, 2016 5:46 AM
  • Hi Adamfowler,

    Welcome to our forum.

    To this issue, we would like to you try to do the following steps, then run the command to check if the issue persist:

    1. Open Lync Deployment Wizard, then re-run “Prepare Active Directory”
    2. Run AD replication manually
    3. Re-run CsClientPin command

    If not, please make sure Lync server is a member of the following group, as the following snapshot:

    If there are any questions or issues, please be free to let me know.


    Best Regards,
    Jim Xu
    TechNet Community Support


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

    Tuesday, November 15, 2016 9:30 AM
    Moderator
  • Hi,

    I've tried start-sleep with 10 and 20 seconds, is there an expected wait time before this will work?

    Tuesday, November 22, 2016 12:27 AM
  • Hi Jim,

    If I wait several minutes of doing nothing, the command works - so is there a way to get a result back to check a sync has run before running the command, or any other workarounds?

    This problem makes it hard to automate user creation.

    Thanks

    Tuesday, November 22, 2016 12:28 AM
  • Hello,

    This is a known issue, either put a start-sleep for 30-40 seconds if you are creating the users in bulk or try creating the user's on 1 Go and do set the pin once finish creating all the users then try to set the pin for all of them in 1 go,,,,

    Regards

    S

    Tuesday, November 22, 2016 7:53 AM
  • Tested and still fails with a start-sleep 60...
    Sunday, December 11, 2016 1:43 AM
  • The problem is, if you create a new user, it depend on your active directory how fast the user data are replicated.

    You can query which is your used DC on your scrip and add the partameter domaincontroler to your script for enabling csuser. Maybe the set-csclientpin is working after 60 seconds?


    regards Holger Technical Specialist UC

    Sunday, December 11, 2016 7:41 AM