Symantec Management Platform (Notification Server)

 View Only
  • 1.  ismanaged back from 0 to 1

    Posted Feb 15, 2012 08:58 AM

    Hi,

     

    I have a pc on server 001, parent. I redirect it to 002, child. After the pc sends its basic inventory, the child now says ismanaged=1. However the parent says ismanaged=0. I thought that after any inventory was forwarded on that pc from child to the parent, that the parent would flip to ismanaged=1 but as far as I can tell it isn't. ResourceUpdateSummary shows datalastchanged for aex swd status being an hour ago. I wish to know what requirements there are for the parent turning the ismanaged back from 0 to 1, and what process does this, so I can hurry it up.

     

    Thanks in advance



  • 2.  RE: ismanaged back from 0 to 1

    Posted Feb 15, 2012 10:25 AM

    This is going to be handled when your resources replicate, it has nothing to do with inventory replication.  What is your schedule for resource replication, and how have you confirmed that the resource in question was included?



  • 3.  RE: ismanaged back from 0 to 1

    Posted Feb 15, 2012 01:29 PM

    Mike,

    I have the Resource standard built in "Computer Replication" resource type replicating up (with the 21 data classes) with the built in standard schedule. Our differential replication happens every night at 1AM (child server #1) and 3AM (child server #2). Also I have an additional Resource type rule called "USPTO Policy Compliance Status and Client Inventory" with Computer resource and 5 selected data classes (including aex_ac_client_agent). That replicates up every 2 hours.

    This PC was replicated at 7:30AM from w-altns-003 (the child server) yet still shows unmanaged.