Symantec Management Platform (Notification Server)

Hello,

we want to replicate dedicated SW-Pakages to dedicated NS Servers with stand-alone Replication because we have to many child NS to replicate in a Hierarchy. There is one zentral NS where all Packages will be stored. The packages are SWD-Packages and OS-Installations(Deployment-Packages). Example: Package A and B should be replicate to NS A and Package B and C should be replicate to NS B .

Any Ideas?

Thanks

You could create an organizational view that includes organizational groups, then add software resources, packages, policies, reports, etc to the organizational groups based on where you want it to replicate.  Then base your replication rule on that organizational group, replicating everything within that target.  It'll end up within the same organizational view and group.

Hello Mike,

thanks for your responds!

I have tried your solution and this works, but i have one more question. When i want to manage the package at the destination NS i need to replicate the "Software release", Software Package", "Software Command lines" and the "MSI Installation file". Is there a way that i do not need to select this resources separately?

Thanks

Guido

sorry, but i have another question. How to replicate dedicated filter and Jobs/Tasks? The filters, Jobs and Tasks have a fix part in there names, or they are in a special folder.

Put filters, jobs, tasks, policies, software releases, packages, etc in the organizational group, then replicate the entire organizational group -- or select (one time) filters, jobs, tasks, policies, software releases, packages, etc for that group.  You shouldn't have a replication rule for each software resource.

i have an automation rule that shows me some Filters and Tasks but they will not shows them in the organizational group. I use the same automation rule(only a different query) for adding computers into the organizational group, and that works.

I also have no idea, how to manually add an item(Filter, Task) to an organizational group.

So, backing up a bit, how many child NS's are there when you say there are 'too many'?  Is this really just about packages, or all resources?  Can you explain a little bit more about your hierarchy design and site design?

We have one parent NS and 15 child NS's. At the child NS's are the clients connected. We don't have a hierarchy implemented. We only want to do a stand-alone replication between the parent and child systems. We want to replicate the dedicated SW-Packages, Filters and Tasks. Futhermore we replicate Inventory. 

At the moment we have Inventory- and Package-Replication successfully implemented.

Why 15 child NS's?  Are you aware that Symantec only supports up to 5 child NS's?  You must be a worldwide corporation with 100k+ nodes?