Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 5736 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

Re-adding devices to ASSIGNED

Weeboo

We have upwards of 500 Devices protected by Enterprise console 5.5.0

When I discover a device that has previously been infected - and has been rebuilt - I generally remove it from the enterprise console and then scan for new devices - this clears the reported infection and reprotects the device as a fresh/new device

We currently have at least one device that this process has been done to - that refuses to move from unassigned

How do I manually move a device from "unassigned" to "assigned" ?



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

    Hello Weeboo,

    one remark and an answer first:
    Remark: Unassigned is the special group that can't be deleted and has no associated policies. All other groups have associated policies, but if there's an ASSIGNED group its name is your choice.
    Answer: You move a computer from one group to another either by drag and drop or cut and paste.

    Your description of the procedure sounds somewhat [no insult intended] fanciful. Lez me explain why I think so.
    A Delete of a computer from the console actually only flags the entry and hides it from the console. It keeps most associated data including its group membership.
    When a scan (I assume you are referring to Discover?) finds yet unknown computers it puts them in the Unassigned group. As this group has no updating policy you can't use Protect (even less is the computer automatically protected). A deleted computer is known and might re-appear in the group it has been in at the time of the deletion. Nevertheless discover does not automatically protect a computer.   
    There are likely some details missing from the description of the process. Does rebuilt mean it gets the same name? After the so-called scan, in which group do the computers appear? Who or what initiates the reprotection?

    Christian

Reply
  • 0

    Hello Weeboo,

    one remark and an answer first:
    Remark: Unassigned is the special group that can't be deleted and has no associated policies. All other groups have associated policies, but if there's an ASSIGNED group its name is your choice.
    Answer: You move a computer from one group to another either by drag and drop or cut and paste.

    Your description of the procedure sounds somewhat [no insult intended] fanciful. Lez me explain why I think so.
    A Delete of a computer from the console actually only flags the entry and hides it from the console. It keeps most associated data including its group membership.
    When a scan (I assume you are referring to Discover?) finds yet unknown computers it puts them in the Unassigned group. As this group has no updating policy you can't use Protect (even less is the computer automatically protected). A deleted computer is known and might re-appear in the group it has been in at the time of the deletion. Nevertheless discover does not automatically protect a computer.   
    There are likely some details missing from the description of the process. Does rebuilt mean it gets the same name? After the so-called scan, in which group do the computers appear? Who or what initiates the reprotection?

    Christian

Children
  • 0 in reply to QC

    "REBUILT" generally means same name (we have to otherwise the teachers get confused) - this is a school.

    Re-protection is carried out manually

    When scanned / discover is run - many devices do not appear to be moved into their correct groups (assigned from AD) !!

    I have tried dragging and dropping - they won't move !

    How do I clear the historic infection details from the Server ?

  • 0 in reply to Weeboo

    Hello Weeboo,

    clear the historic infection details
    why do you want to do this? Arguably they details don't "belong to" the rebuilt computer but there was a detection. BTW - are these really infections ? PurgeDB.exe is the supported interface to purge alerts and events if needed.

    moved into their correct groups
    so you have (initially) imported the groups from AD or are you using AD sync?

    Christian

Unfiltered HTML