Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 8 replies
  • Subscribers 4 subscribers
  • Views 11427 views
  • Users 0 members are here
Options
Suggested
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

PCs are showing as unmanaged on SEC

Tharaka Koggalahewa

Hi, 

We are having installed SEC and managing around 4000 number of end systems using that.  But there are around 500 PCs which are categorized under unmanaged section of the console. we have integrated with the active directory to get the PC list. those unmanged PCs are list under several OUs of the AD. when I check some of those PCs they are updating correctly and also mrinit.conf file is same as managed PC. console IP address is there under the "ParentRouterAddress" and "MRParentAddress". I cannot find a reason for this behavior and please help me to get thing sorted out.

cpnsole version 5.4

Endpoint version 10.6

 

BR.

Tharaka 



This thread was automatically locked due to age.
Parents
  • 0

    Hello Tharaka,

    integrated with the active directory
    you mean you are using AD synchronization? Please use the same terms as SEC - this helps to avoid misunderstandings.

    categorized under unmanaged section
    you are talking about the Unmanaged     view (either selected with the View: drop-down or by clicking the link in Dashboard's Computers pane)? And the computers are in the correct groups mirrored from the AD OUs?
    Please check the Network Communications Report on one of these endpoints. If it shows the correct Current parent address the endpoint should be in the console as managed - it should be in the Unassigned (or even some other) group if the corresponding computer from AD is in the correct group but unmanaged. In other words - you should see these computers twice.

    Christian

  • 0 in reply to QC

    Hello Christian,

    integrated with the active directory
    you mean you are using AD synchronization? Please use the same terms as SEC - this helps to avoid misunderstandings.

    Yes, I am using AD synchronization to import the PC list. I am not using the discover computer option of the SEC to detect end PCs.

     

    categorized under unmanaged section
    you are talking about the Unmanaged    view (either selected with the View: drop-down or by clicking the link in Dashboard's Computers pane)? And the computers are in the correct groups mirrored from the AD OUs?
    Please check the Network Communications Report on one of these endpoints. If it shows the correct Current parent address the endpoint should be in the console as managed - it should be in the Unassigned (or even some other) group if the corresponding computer from AD is in the correct group but unmanaged. In other words - you should see these computers twice.

     

    I am talking about the unmanaged section appears by clicking the link in the dashboard. and i cannot understand what you meant from " 
    If it shows the correct Current parent address the endpoint should be in the console as managed - it should be in the Unassigned (or even some other) group if the corresponding computer from AD is in the correct group but unmanaged. ". I will look at the Network Communication Report for the further details. As I said before ParentRouterAddress" and "MRParentAddress" are correct. That is why I am confused about this scenario.

     

     

     

    Thanks.

    Tharaka.

  • +1 in reply to Tharaka Koggalahewa

    Hello Tharaka,

    thanks for the clarification.
    As for mrinit.conf: It is stored in the CID and unless have modified it at some point or have message relays (and therefore several CIDs and mrinit.conf) the one on the endpoint is the same as in the CID. But even if it is correct and successfully applied by RMS communication can fail. A simple example is an off-network endpoint which won't be able to connect to a management server which has no public IP (directly or port-forwarded). Thus only the Network Communications Report is significant for determining the actual communication status.

    Trying to rephrase what's not clear to you:
    A common error scenario is that for whatever reason an endpoint (say OU1-PC001) which contacts the management server is not recognized as the computer synched with AD. Then you'll see an unmanaged OU1-PC001 in group \OU1 and another OU1-PC001 as managed and up-to-date in (usually) the Unassigned group. Thus you should check if there are (many) duplicates in the All computers view. This should also be obvious from the total number of computers of course.
    It's possible that (again for whatever reason) some endpoints can't successfully register with the management server. The synched computers will simply show as unmanaged, the total number will be more or less correct.
    Yet another option is that some computers have been cloned incorrectly (i.e. after Sophos has been fully installed and the required steps omitted). You'd likely have noticed though as in this case some of the managed computers would continuously change their name and unmanaged ones "move" from their AD group to Unassigned and back.

    Christian 

Reply
  • +1 in reply to Tharaka Koggalahewa

    Hello Tharaka,

    thanks for the clarification.
    As for mrinit.conf: It is stored in the CID and unless have modified it at some point or have message relays (and therefore several CIDs and mrinit.conf) the one on the endpoint is the same as in the CID. But even if it is correct and successfully applied by RMS communication can fail. A simple example is an off-network endpoint which won't be able to connect to a management server which has no public IP (directly or port-forwarded). Thus only the Network Communications Report is significant for determining the actual communication status.

    Trying to rephrase what's not clear to you:
    A common error scenario is that for whatever reason an endpoint (say OU1-PC001) which contacts the management server is not recognized as the computer synched with AD. Then you'll see an unmanaged OU1-PC001 in group \OU1 and another OU1-PC001 as managed and up-to-date in (usually) the Unassigned group. Thus you should check if there are (many) duplicates in the All computers view. This should also be obvious from the total number of computers of course.
    It's possible that (again for whatever reason) some endpoints can't successfully register with the management server. The synched computers will simply show as unmanaged, the total number will be more or less correct.
    Yet another option is that some computers have been cloned incorrectly (i.e. after Sophos has been fully installed and the required steps omitted). You'd likely have noticed though as in this case some of the managed computers would continuously change their name and unmanaged ones "move" from their AD group to Unassigned and back.

    Christian 

Children
Unfiltered HTML