Endpoint Protection

 View Only
  • 1.  SEPM migration from 2003 to 2008 R2 Errors

    Posted Jul 21, 2010 04:51 PM
    Hello,

    I'm following the instructions outlined in document 2008031204405448 "How do I move Symantec Endpoint Protection Manager from one server to another with a different IP address and hostname?", with 11.0.6 installed on the source and target.

    I'm doing this in a lab before doing it on the production network and I'm running into a few errors, the first was "Unable to communicate with the reporting component".  I followed the steps in article "Unable to communicate with the reporting component after logging into the Symantec Endpoint Protection Manager", doc # 2008042212582048.

    Which led me to see that the ODBC connection was not listed under System DSN at all --- it is correctly listed on the source server.

    So I rolled back my VMs to a previous snapshot and tried the install again, but again, no ODBC connection is created.

    I've installed all the prerequisites for 2008 R2, IIS, ASP.NET, CGI, IIS 6 Mangement and so forth.  I've disabled the firewall on the 2008 R2 machine completely, and disabled UAC, but it doesn't seem to make a difference.

    Any suggestions?

    Thanks, 

    Tyler


  • 2.  RE: SEPM migration from 2003 to 2008 R2 Errors
    Best Answer

    Posted Jul 21, 2010 05:02 PM


  • 3.  RE: SEPM migration from 2003 to 2008 R2 Errors

    Posted Jul 21, 2010 09:52 PM
    The ODBC would be under the syswow64 folder under c:\wondows. 
    Even after establishing the ODBC if you are not able to login then try to open the http://Loclhost:8014/reporting link from the IE on the server and see what happens?


  • 4.  RE: SEPM migration from 2003 to 2008 R2 Errors

    Posted Jul 22, 2010 08:25 AM
    Thank you -- the ODBC connection was created and showed up when viewed using the odbcad32.

    This time the installation seems to have taken, no more reporting component errors, so maybe disabling UAC or the firewall did the trick.

    Hopefully the rest of the migration goes smoothly.  Thanks for your help.



  • 5.  RE: SEPM migration from 2003 to 2008 R2 Errors

    Posted Jul 22, 2010 08:40 AM
    Good to know that fixing the ODBC fixed the issue,