Endpoint Protection

 View Only
Expand all | Collapse all

Client installation using Find Unmanaged Computers failing

  • 1.  Client installation using Find Unmanaged Computers failing

    Posted May 29, 2009 02:08 PM
    Hello

    I am testing the client installation option using "Find Unmanaged Computers" option. I can find my test computer under 'Unknown Computers', but when I try to run the remote installation, I get the Deployment Status "Failed". I can't find any logs showing details of why the installation is failing. Is there a FAQ available discussing troubleshooting steps for client installation issues? Are there any logs on the server which can be helpful in this case? Thanks.

    Regards

    Marcin


  • 2.  RE: Client installation using Find Unmanaged Computers failing

    Posted May 29, 2009 02:38 PM
    Hi

    Here are some reading - You do have admin right on the client :-)

    Installation fails when client package is deployed using 'Find Unmanaged Computers' in Symantec Endpoint Protection Manager (SEPM) Console
    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/066a68ac96a654c58825733f0060824d?OpenDocument

    Deploying client software using "Find Unmanaged Computers" in Symantec Endpoint Protection Manager (SEPM) fails without error messages
    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/653759a32c530ab6882573a900735f27?OpenDocument

    Howto do it:
    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/300aefa98822767c882573b20068c884?OpenDocument

    Common Symantec Endpoint Protection Client Installation Issues
    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/6388ea89c86d0afa882574e1007a4d0a?OpenDocument


  • 3.  RE: Client installation using Find Unmanaged Computers failing
    Best Answer

    Posted May 29, 2009 02:46 PM
    There has been a lot of confusion between Unknown and Unmanaged computers in Find Unmanaged computers.

    After entering the login credentials and domain/workgroup name when you hit search.
    It starts scanning your network using those credentials.
    On the computers on which these credentials does not work this tool Classifies it to be Unknown Computers thats the reason you will also see your routers, switches,printers and other networking devices in Unknown Computers.

    On the computers on which these credential works then this tool checks if that compters is registered with this SEPM console,If it finds its entry in the sepm console it will not list it otherwise it will show up as Unamanaged computer that is either that computer has SEP but its Unmanaged or it does not have sep at all.
    Thats the reason earlier when you had AD integration this tool does not find any computers but now thats rectified.


  • 4.  RE: Client installation using Find Unmanaged Computers failing

    Posted Jun 02, 2009 12:46 PM
    Hi, jrudbecka. Thanks for the links. Yes, I am using a domain admin account to log on to the client machines.
    Regards
    Marcin



  • 5.  RE: Client installation using Find Unmanaged Computers failing

    Posted Jun 02, 2009 01:06 PM
    Hi, Vikram
    Thank you very much for your explanation. It helps to understand the 'Find Unmanaged Computers' tool better.The problem I am seeing is that on my test subnet I have several categories of machines:
    1. machines which show up under the Unmanaged tab; the client software can be installed on them without any problem
    2. machines which show up under the Unknown tab, with the following subgroups:
       a. machines on which I can install client software using ClientRemote.exe
       b. machines on which using ClientRemote.exe causes an error (cannot copy a file)
       c. machines on which authentication part of ClientRemote.exe fails, despite the fact that domain admin account is used and all machines are part of the domain

    So, the problem I have is with the b. and c. machines. The full error message for b. is:
    "The proces cannot access the file because it is being used by another process
    m_nError: -6
    m_dwApiError: 32
    m_strMessage: Failed to copy the following file to the remote client computer:..."
    I tried several times, always with the same error.

    As for the c. category, those machines are on a different subnet, but there is no filtering on the router, and no firewalls on any of the machines (servers and workstations). Packet capture shows a reset from the client during the TCP handshake on port 139.

    I am continuing digging, but any hints and tips regarding b. and c. would be very much appreciated. Thanks.

    Regards

    Marcin



  • 6.  RE: Client installation using Find Unmanaged Computers failing

    Posted Jun 03, 2009 05:53 AM
    Follow this document as this is some network issue that has be fixed either network or permission.


    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/3e95d7f0ebf56f6088257393005bd82b?OpenDocument


  • 7.  RE: Client installation using Find Unmanaged Computers failing

    Posted Jun 03, 2009 10:34 AM
    Thanks, Vikram
    Regarding my previous post, the group 2b apparently is a set of virtual interfaces on some servers. The "real" interfaces accepted the client installation, so the only problem left is 2c. I used the method discribed in the document you quoted (Add or Import Computer) and am getting invalid username/password for a workstation, which is a member of the domain and the credentials I'm using are of a Domian Admin. As I said, that workstation is on a different subnet (VLAN) and also not visible in the MS domain browser. If I use the same credentials directly on that workstation, I can log on without any problems. I will have to digg deeper. Thank you very much for your help so far.
    Regards
    Marcin



  • 8.  RE: Client installation using Find Unmanaged Computers failing

    Posted Jun 03, 2009 07:33 PM
     If you are able to ping them ..you can just copy the Clientremote.exe from cd2 and the package to any computer on that VLAN and deploy it from there.


  • 9.  RE: Client installation using Find Unmanaged Computers failing

    Posted Jun 04, 2009 02:35 PM
    Hi, Vikram

    Thanks for the tip. That would be the method of last resort. I would prefer to be able to install the clients remotely from the central server, if at all possible.

    I went over the document you showed me (Error: "No Network Provider accepted given the network path") and both the server and the workstation meet all the requirements listed there. However, I still get that exact error, using the Deployment Wizard. I wonder if Symantec depends in any way on the Microsoft Windows browsing for client deployment. We don't have WINS in our environment, and cannot browse between VLANs. Could that be the reason for the problem I am seeing? I am just trying to get to the bottom of it. Thank you very much for your help.

    Regards
    Marcin


  • 10.  RE: Client installation using Find Unmanaged Computers failing

    Posted Jun 04, 2009 02:43 PM
     You should be able to access the root drive of the client in order to deploy it remotely.
    As when you deploy first it copies the install package in <root drive>:\temp\CLT-INST folder then it starts the installation locally.If it is unable to browse root drive it fails


  • 11.  RE: Client installation using Find Unmanaged Computers failing

    Posted Jul 10, 2009 07:40 AM
    I have same problem.. If i search unmanage computer, in unknown computer will be apper. pls help...