lcsaddcontacts.wsf

잠김 lcsaddcontacts.wsf

  • 2007년 4월 19일 목요일 오후 9:05
     
     

    Technet,

    So, I've got my installation done and configured for the 07 beta.  My users can im and do voice.  HOWEVER, I cannot get the lcsaddcontacts script to work correctly on the backend server.  This is a pain to my test users who don't enjoy having to add people manually as once you get over 20 folks it gets ridiculous.  So, I tried using the script.  It runs and finishes with no errors just as it had for 05 when I was testing it.  But, when you go to the client and sign off, sign back on, the contact list goes from (whatever it had) to empty.  I figured this was an issue with group policy of some sort and attempted to run the other script lcsaddaces.wsf but it fails when I attempt to run it.  I've set it up as the whitepapers and other newsgroups have suggested.  Does anyone else no of a fix/work around?

     

    Dan

모든 응답

  • 2007년 4월 26일 목요일 오후 11:30
     
     
    Do you get any errors/events on the servers or client computers?
  • 2007년 4월 27일 금요일 오후 9:58
     
     

    After running the lcsaddcontacts.wsf?

     

    None, it actually looked perfect.  It looked exactly the same as 2005 when it worked.

  • 2007년 5월 9일 수요일 오후 7:49
     
     
    Here are a few suggestions to get started:

    1. Run the lcsaddcontacts,wsf file from the OCS 2007 FE server itself. All the *.wsf file requires is the insallation of OCS Administration tools. This will add the necesarry objects to the local WMI along with the needed fuctionality to move the information to the SQL BE database.

    2. When you run the lcsaddcontacts.wsf file to add contactsjust use the script in a single instance from a command prompt. Do not include it in a batch file that will run the same process with the /delete switch.
  • 2007년 5월 10일 목요일 오후 4:43
     
     

    Thom,

     

    I also tried to use the lcsaddcontacts.wsf to import contacts with no success. I did exactly as you said, testing against my own account. The script runs fine from the command prompt and indicates " [+]   Put successful for contact:  (sip:xyz@contoso.com)" so there is no idication that anything went wrong. I am wondering about the fuctionality needed to move the information to the SQL BE database that you mention. Is there anyway to figure out if that is the piece that is failing?

  • 2007년 5월 15일 화요일 오후 4:06
     
     

    You can try to synchronise the client address book manually from the client by deleting the address book file and sign in again, or on the server with the command "abserver –syncnow"

    Regards

     

    Sylvain

  • 2007년 5월 21일 월요일 오후 8:15
     
     
    thanks as I thought I was the only one with this issue for quite a while.  Still isn't working btw.
  • 2007년 5월 23일 수요일 오후 3:02
     
     
    Krups, thanks for the suggestion. In our scenario we need to be able to use the import command. We are upgrading from LCS 2003. What I have found so far is that peoples contacts are being automatically discovered and then they are being prompted to add them as contacts. However in a lot of cases not all of their contacts are being retained. I will give your suggestion a try, but It sure would be convenient if the lcsaddcontacts.wsf worked as it should.
  • 2007년 5월 29일 화요일 오후 1:21
     
     

    Could you post the result of the lcsaddcontacts.wsf command?

    I use it on my testing platform without problem.

     

    Sylvain

  • 2007년 5월 30일 수요일 오전 1:59
     
     

    Joec

     

    You need to run and configure the LCSAddACEs.wsf to suppress prompting for adding users in MOC 2007 when users log in.

     

    regards

     

    Adrian

     

     

  • 2007년 5월 30일 수요일 오후 12:47
     
     

    Krups, here is the the command I ran and the results:

     

    C:\Contacts>cscript lcsaddcontacts.wsf /usersfile:UsersFile.txt /ContactsFile:ContactsFile.txt
    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    @------------------------------------------------------------
    @ Text file with Users:       usersfile.txt
    @ Text file with Contacts:    contactsfile.txt
    @ Contact Group for Contacts:
    @------------------------------------------------------------


    @------------------------------------------------------------
    @ Adding contacts...
    @  PrimaryURI:     sip:zzxwhi@contoso.com
    @  InstanceID:     {A103F1E9-E176-F04A-81C7-E8148DCA80D2}
    @  ContactGroupID:
    @------------------------------------------------------------
    [+]   Put successful for contact:  (sip:jcalvi@contoso.com)
    [+]   Put successful for contact:  (sipTongue Tiedczesak@contoso.com)
    [+]   Put successful for contact:  (sipBig Smilevelasquez@contoso.com)
    [+]   Put successful for contact:  (sip:nmignott@contoso.com)
    [+]   Put successful for contact:  (sip:bbrown@contoso.com)
    [+]   Put successful for contact:  (sip:jcouncil@contoso.com)
    [+]   Put successful for contact:  (sip:aevangelista@contoso.com)
    [+]   Put successful for contact:  (sip:jpanycia@contoso.com)
    [+]   Put successful for contact:  (sip:mereynolds@contoso.com)

  • 2007년 5월 31일 목요일 오전 9:29
     
     

    Quite strange...

    Maybe you can try to specify a group in the command line in order to let the previous list the users have.

  • 2007년 6월 22일 금요일 오후 3:47
     
     

    Hi Dan,

    Can you let us know the status of your issue? If you have been able to find a resolution, can you share it with the forums? If not, please let us know asap.

    Thanks. 

  • 2007년 6월 27일 수요일 오후 6:25
     
     

    Hi Dan and Krups,

    Can you let us know the status of your issues?

  • 2007년 6월 27일 수요일 오후 11:17
     
     답변됨

    Here are some general guidelines as mentioned in the readme for the script. Once the script has been run, you can use Wbemtest to see if the contacts were populated correctly.

    Q: How do I confirm whether the contacts have been added?

    A: Run Wbemtest.exe. Connect to root\CIMv2, and then click Query. Run the following query: SELECT * FROM MSFT_SIPESUserContactData WHERE UserInstanceID = {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}.

    Also, always run script with the a group specified. i.e.

    cscript LCSAddContacts.wsf /usersFile:value /contactsFile:value /contactsGroup:value

    If a group is not specified the contacts will not show up in Communicator.

     

    Please let me know if there are still any unresolved issues around this?

  • 2007년 7월 10일 화요일 오후 7:57
     
     

    Salman, thanks for the suggestion. Interesting, when I run the lcsaddcontacts.wsf with the /contactsGroup switch I get the following error output:

     

    C:\Contacts>cscript LCSAddContacts.wsf /usersFile:UsersFile.txt /contactsFile:ContactsFile.txt /contactsGroup:Team
    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    @------------------------------------------------------------
    @ Text file with Users:       usersfile.txt
    @ Text file with Contacts:    contactsfile.txt
    @ Contact Group for Contacts: Team
    @------------------------------------------------------------


    @------------------------------------------------------------
    @ Adding contacts...
    @  PrimaryURI:     sip:zzxwhi@malcolmpirnie.com
    @  InstanceID:     {A103F1E9-E176-F04A-81C7-E8148DCA80D2}
    @  ContactGroupID: 6
    @------------------------------------------------------------
    C:\Contacts\LCSAddContacts.wsf(253, 7) Microsoft VBScript runtime error: Type mismatch: 'UBound'

     

    I have tried to specify pre-existing groups as well as new (i.e. Personal, Company; Friends, Test) but I get the error each time. However, If I eliminate the  /contactsGroup switch, it runs successfully everytime (as shown in my earlier post). Strange thing is the groups are created. However the contacts never get populated under them.

     

     

     

  • 2007년 7월 11일 수요일 오후 12:02
     
     

    The error you have is due to a bug in the script. You have certainly tried to first add users without the group in parameter. After this it's not possible anymore to add a user in a group.

    We have corrected the script to manage this problem, it's not so difficult.

     

    Sylvain

  • 2007년 7월 11일 수요일 오후 1:50
     
     
    Thanks for clearing that up Krups. Is the new script available for download yet?
  • 2007년 7월 12일 목요일 오전 9:08
     
     

    No it's not available as it's an internal modification we have done.

    In fact the users have been created in an empty group. To solve the problem you can go to SQL Server in order to delete the users view entries in the tables. I think that you have to check 2 or 3 tables.

    When the clean is done you can launch the script again with a correct group in parameter.

    I don't remember the name of the tables but you can add comment in the script to know exactly what you have to check.

     

    Sylvain

  • 2007년 7월 18일 수요일 오전 12:42
     
     

    Sylvain: Are you able to tell us which line(s) you changed in the script to get it to work for you?

    Or what we can do to resolve this problem?

     

    We are running the Release Candidate version and the script still does not work for adding users (it works for creating groups and deleting users however)

     

    When you say "You have certainly tried to first add users without the group in parameter. After this it's not possible anymore to add a user in a group." Do you mean after you have atttempted to add users without the scripts group parameter, you won't be able to add them even with it? But if you always remember to use the group parameter it will always work??

     

    We really need this to work as our user id's are impossible for other users to remember off the top of their heads, and we've been unable to get our reverse proxy working for external client address books (friendly names).

     

     

  • 2007년 7월 18일 수요일 오후 1:49
     
     

    I mean that if you have attempted to add user without group you won't be able to add user in a group anymore.

    The problem is that "oInstance.GroupId" is null line 253 and they don't manage this case. So the Ubound function crash.

    The best way I think is not to correct the script but to clean the following tables in SQL Server in order to start from scratch :

    - Contact

    - ContactGroup

    - ContactGroupAssoc

     

    After this you can try the script again. Don't forget to put the group ;-)

     

    Sylvain

  • 2007년 7월 19일 목요일 오전 4:17
     
     

    Ok thanks for the tip..

     

    Taking a look into them all I can see are premary keys / numbers and <binary data>

    How do we find the 'dirty records' or do we have to delete all the records in them?

     

    This would clear everybody's existing contact lists right Sad

  • 2007년 7월 19일 목요일 오전 6:58
     
     

    Yes you're right it will clear everybody...but with the script you can add them again.

    Just backup the tables if you want to be sure...

  • 2007년 7월 24일 화요일 오후 3:48
     
     

    Krups, is there a way to export contacts for all the OCS 2007 clients from the server? There doesnt seem to be a way to do it from either the client or the server. I plan on clearing out the sql tables but wont proceed until I have an export of everyones current contact list. Backing up the sql tables is not an option for me.

     

    Nevermind, I was able to get a complete dump using the DBImpExp.exe utility. It can be found here: C:\Program Files\Office Communications Server 2007\Server\Support

  • 2009년 3월 6일 금요일 오후 3:30
     
     
    Hi everyone,

    I've got here something, and i can't figure it out yet. LCSAddContacts does not delete contacts of removed users. Any suggestions anyone?

    Any help would be appreciated.

    Best wishes,
    Nikolai
  • 2009년 3월 17일 화요일 오전 11:00
     
     
    By removed users i mean: The user removed from the group. So if the user is removed from the group contact shoud also be removed from comunicator. But this didn't happen. :(
  • 2009년 12월 20일 일요일 오후 8:51
     
     제안된 답변

    You may use   (OCSCM) Microsoft Office Communications Server Contact Manager.It's an administration mmc tool that will integrate with Microsoft Office Communication Server 2007 and Active Directory to provide an easy way to provision OCS users’ contacts list.   OCSCM is designed to show you how to manage the contacts and groups for individual ocs users by interacting with the Active Directory Domain Services and Microsoft Office Communication Server 2007/R2 and lcs 2005.

    download from http://www.ocscm.com

    • 답변으로 제안됨 Ahmed M. Ibrahim 2009년 12월 20일 일요일 오후 8:51
    •