Symantec Management Platform (Notification Server)

hello

I have noticed this problem for a few weeks now, we deploy newly imaged computers but the agent takes about 1 week to be installed !!

Here are our configurations

• SMP 7.1
• Symantec Management Agent policy activated
• I noticed that the computers that do not have the agent are not in the filtre

Please advice the steps I could take to troubleshoot this problem

thank you in advance

What discovery method is being used to identify new computers?

The best way to image machines is to include the SMA in the image, and have it configured so that it connects to a redirection SMP (VM guest running just the SMP with TCPIP filters).

Hi SK,

Sorry, did not checkin to the site for a while. Thank you for your reply.

We are using AD import to identify new computers.

I was thinking to include SMA in the image but why would I configure it to redirect to SMP (VM guest ...) as you stated? What problems would I face if I install the agent manually on a new computer and then create an image of that computer.

thank you in advance

regards

If you only have one SMP, then yes you could install the SMA and have it point to the live SMP; however, this would then cause that vanilla machine to become managed by that SMP before it has been imaged, which means that you would then have to delete its computer resource from the database and then delete its MachineGuid from the registry (I believe the new versions of DS do this as part of their prepare for imaging process).  Using this method also means that you could end up with solution plugins also being installed, some of which may write the MachineGuid to their own registry areas which may or may not be targeted by the DS process, so you should manually check this afterwards before image deployment.

If you have more than one SMP, then building a SMP only VM to act as your redirection SMP allows you to still only have one image.  This SMP also becomes usefull if you experience duplicate guid issues, as it can be used as part of your rectifying process.

Concerning your current setup, I assume you first import from AD, and then use the SMA's scheduled push feature to target the newly discovered machines, yes?  If this is the case, are the newly imported machines found in the Target associated with the push?  Also, how frequently is the push scheduled to run (by default its daily)?