This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Endpoint Console Help

I have some issues with the Enterprise Management Console that I'm hoping someone might have some advice about.  We are considering purchasing the Endpoint Enterprise to manage our Anti Virus protection on our heavily mixed environement.  We have Macs, PCs and Linux Clusters.

I currently have a test environment on my OS X 10.6 MacBook Pro running Parallels VM

I have Server 2003 running on one VM to host the Management Console

I have Windows 7 on a second VM

I did not use Active Directory because our live environment currently doesn't either.

I installed the Management Console and downloaded the Windows, Mac, and Linux Clients.

I then installed the Mac client from the server share but it did not autoconfigure for my server???

So I manually added the update server and it is getting updates from the win2k3 server but on the server console my MacBookPro is still "grayed out"

Any Thoughts?

Thanks a bunch.

:11657


This thread was automatically locked due to age.
Parents
  • Hi,

    Does the WIndows 7 machine show in SEC sorrectly as connected and managed?  Is so this guarantees much of the server side setup if functioning correctly.

    The Windows and Mac clients both use the Remote Management System (RMS) to communicate with SEC.Where the Windows machine uses the registry to hold settings and such, the Mac uses files which emulate the registry.

    So the main things to check are:

    1. If the Mac is pointing at the right address, ie the ParentAddress contains the address of theSEC server.

    2. The Mac has both an Agent and Router certificate.

    One of the indications of this is the Router on the Mac starts listening on pors 8192,8193 and 8194. This is evidence that the Mac Router has a certificate.

    So as a test, can you connect to port 8192 and 8194 on the Mac?  You should be able to telnet from the server to the Mac.  E.g.

    telnet macaddress 8192
    telnet macaddress 8194

    The server doesn't connect to port 8192 but this will present a string and prove the router has a certificate, connecting to port 8194 connects but doesn't display anthing this is expected.

    That being said it is worth mentioning is that the Mac needs to be able to connect to ports 8192 and 8194 of the server and the server needs to be able to connect to port 8194 of the Mac to ensure fast downstream message delivery.  

    I hope this helps.


    Jak

    :11661
Reply
  • Hi,

    Does the WIndows 7 machine show in SEC sorrectly as connected and managed?  Is so this guarantees much of the server side setup if functioning correctly.

    The Windows and Mac clients both use the Remote Management System (RMS) to communicate with SEC.Where the Windows machine uses the registry to hold settings and such, the Mac uses files which emulate the registry.

    So the main things to check are:

    1. If the Mac is pointing at the right address, ie the ParentAddress contains the address of theSEC server.

    2. The Mac has both an Agent and Router certificate.

    One of the indications of this is the Router on the Mac starts listening on pors 8192,8193 and 8194. This is evidence that the Mac Router has a certificate.

    So as a test, can you connect to port 8192 and 8194 on the Mac?  You should be able to telnet from the server to the Mac.  E.g.

    telnet macaddress 8192
    telnet macaddress 8194

    The server doesn't connect to port 8192 but this will present a string and prove the router has a certificate, connecting to port 8194 connects but doesn't display anthing this is expected.

    That being said it is worth mentioning is that the Mac needs to be able to connect to ports 8192 and 8194 of the server and the server needs to be able to connect to port 8194 of the Mac to ensure fast downstream message delivery.  

    I hope this helps.


    Jak

    :11661
Children
No Data