Endpoint Protection

 View Only
Expand all | Collapse all

MoveClient.vbs scripts

ℬrίαη

ℬrίαηMay 03, 2012 01:17 PM

ℬrίαη

ℬrίαηMay 03, 2012 02:09 PM

ℬrίαη

ℬrίαηMay 03, 2012 02:26 PM

  • 1.  MoveClient.vbs scripts

    Posted May 03, 2012 08:39 AM

    Does anyone have experience with using this tool that they can share?

    The problem I'm having is that I can easily move clients based on IP address but than all my servers move as well. We have workstations and servers separate due to different policy requirements.

    It would seem that I should create one file to move clients by IP address than create another so I can move the servers back into the correct group(s).

    Just curious what everyone else is doing (if anyone if is actually using this)

    I noticed the tool is under the NoSupport folder so I take that to mean I can't open a support case.

    Any thoughts would be appreciated.



  • 2.  RE: MoveClient.vbs scripts

    Broadcom Employee
    Posted May 03, 2012 08:50 AM

    you can set a script for server and one for workstations so that it can be moved to respective groups.



  • 3.  RE: MoveClient.vbs scripts

    Posted May 03, 2012 08:51 AM

    Check the following links:-

     

    https://www-secure.symantec.com/connect/forums/moveclientvbs-error

    https://www-secure.symantec.com/connect/forums/using-moveclientvbs

    https://www-secure.symantec.com/connect/forums/moveclientsvbs-issue



  • 4.  RE: MoveClient.vbs scripts

    Posted May 03, 2012 10:04 AM

    Let's assume your network is 192.168.0.0/24. For historical reasons, your servers are between 192.168.0.50 and 192.168.0.60. You want to move the workstations to NewGroup and keep the servers in their old group. You can write an IPGroups.txt file like this:

    192.168.0.1-192.168.0.49,NewGroup
    192.168.0.61-192.168.0.254,NewGroup

    Another possibility: If all your clients are Windows XP boxes, edit the OSGroups.txt file this way:

    Windows XP*,NewGroup

    IPGroups.txt, OSGroups.txt and some other files are controlling MoveClient.vbs. Have a look at MoveClient.pdf in the MoveClient folder on the CD.



  • 5.  RE: MoveClient.vbs scripts

    Posted May 03, 2012 01:17 PM

    Does this work with 12.1?



  • 6.  RE: MoveClient.vbs scripts

    Broadcom Employee
    Posted May 03, 2012 01:27 PM

    the second CD or install media under no support tool you will have these scripts.



  • 7.  RE: MoveClient.vbs scripts

    Posted May 03, 2012 01:34 PM

    I have the scripts but I'm running into an error where after running, none of the clients are moved and get "The new group is invalid" error msg.

    I've verified everything and the group name is correct.

    But since it's under no support, I assume I cannot call Symantec and open a case?



  • 8.  RE: MoveClient.vbs scripts

    Posted May 03, 2012 01:46 PM

    Yes, it works. If I remember correctly, it was revamped for SEP 12.1 (different text file names).

    You have to configure the vbs file for db user name, password and default group and then just create a IPGroups.txt file (and/or OSGroups.txt etc.). See the pdf documentation on <SEP 12.1 CD2>:\Tools \NoSupport\MoveClient.



  • 9.  RE: MoveClient.vbs scripts

    Broadcom Employee
    Posted May 03, 2012 01:46 PM

    i guess the log is created after script is run in the tomcat log folder, can you post the logs?



  • 10.  RE: MoveClient.vbs scripts

    Posted May 03, 2012 01:51 PM

    I'll post a snippet, I had to sanitize to client and user section:

     

    ::Temp Group for this run: Default Group
            ::Success
        ::Root Group Name: My Company
        ::Domain Name: cbi
        ::DomainID: AD935C470A01128001E5424BA434F4AF
            ::Success
        ::Get Temp GroupID: 5095EE970A011280001CB1809A533BCF
            ::Success
        ::Get NewUSN: 142073001
            ::Success
    5/3/2012 11:59:28 AM : Start structure metadata Query
        ::Get group structure metadata
            ::Success

    ::Checking for clients to move

            ::Failed to move Client '*' User '*'.  The new group is invalid.
            ::Failed to move Client '*' User '*'.  The new group is invalid.
            ::Failed to move Client '*' User '*".  The new group is invalid.
            ::Failed to move Client '*' User '*'.  The new group is invalid.
            ::Failed to move Client '*' User '*'.  The new group is invalid.
            ::Failed to move Client '*' User '*'.  The new group is invalid.
            ::Failed to move Client '*' User '*'.  The new group is invalid.
            ::Failed to move Client '*' User '*'.  The new group is invalid.
           



  • 11.  RE: MoveClient.vbs scripts

    Posted May 03, 2012 02:09 PM

    Yep, that is all done.



  • 12.  RE: MoveClient.vbs scripts

    Posted May 03, 2012 02:10 PM

    Are you using the current version? It's MoveClients.vbs 3.0 (SEP 12.1).

    Do one or more XYZGroups.txt files exist? The log entry "::Processing IPGroups.txt" is missing (should be after "::Get group structure metadata".



  • 13.  RE: MoveClient.vbs scripts

    Posted May 03, 2012 02:19 PM

    The version I show is 3.06. I got it from the 12.1 RU1 MP1 download.

    I edited out a lot because there were so many entries for PCs not being moved..here was more:

    :Temp Group for this run: Default Group
            ::Success
        ::Root Group Name: My Company
        ::Domain Name: cbi
        ::DomainID: AD935C470A01128001E5424BA434F4AF
            ::Success
        ::Get Temp GroupID: 5095EE970A011280001CB1809A533BCF
            ::Success
        ::Get NewUSN: 142073001
            ::Success
    5/3/2012 11:59:28 AM : Start structure metadata Query
        ::Get group structure metadata
            ::Success
        ::Processing IPgroups.txt
        ::010001017001 - 010001017254 -|- <edited>
        ::010001018001 - 010001018254 -|- <edited>
        ::010001019001 - 010001019254 -|- <edited>
        ::010001145001 - 010001145254 -|- <edited>
        ::Checking for clients to move



  • 14.  RE: MoveClient.vbs scripts

    Posted May 03, 2012 02:21 PM

    Did you change the DomainName setting to "cbi" in the MoveClient.vbs script?

    Quote from the MoveClient.vbs doc:

    DomainName
    This will configure what domain the tool uses.  If “%” is specified then it will default to the first domain.  Note: if a domain name is specified in the text file it will override this value.  Default value is: "%"



  • 15.  RE: MoveClient.vbs scripts

    Posted May 03, 2012 02:26 PM

    I did but still with same result.



  • 16.  RE: MoveClient.vbs scripts

    Posted Aug 29, 2012 02:43 PM

    Hello Brian,

    The error message "::Failed to move Client '*' User '*'.  The new group is invalid." means that the MoveClient tool could not get the Group ID of the group name specified in the the txt file.

    It looks like you are using the IPgroup.txt file.  Can you confirm if the group name in this text file specified for this IP range has any white spaces or any other characters that are non-alphanumeric?

    Thanks,



  • 17.  RE: MoveClient.vbs scripts

    Posted Aug 29, 2012 02:54 PM

    Hi Elisha,

    Thanks for the reply.

    Yes, I'm using the IPgroup.txt file.

    I do have spaces, so for example my first line in the text file reads(Full IP range redacted):

    10.x.x.x-10.x.x.x,My Company\CBI America Servers\North Region\Plainfield

     



  • 18.  RE: MoveClient.vbs scripts
    Best Answer

    Posted Aug 29, 2012 03:29 PM

    Try it without the "My Company\" at the beginning.  The script will automatically add this.  The file should look like this:

    10.x.x.x-10.x.x.x,CBI America Servers\North Region\Plainfield



  • 19.  RE: MoveClient.vbs scripts

    Posted Aug 29, 2012 04:01 PM

    Figures, I knew it was something simple cool

    Thanks for you help!