Quantcast
Channel: Ivanti User Community : All Content - Patch Manager
Viewing all articles
Browse latest Browse all 1121

Syncing Patch Manger Content between two or more cores

$
0
0

Problem

 

You need to sync the patch content from one core to another one or multiple cores

 

You would also like your scan folder and your do not scan need to replicated as well.

 

In addition to this you need a custom group folder(s) copied as well

 

Setting up the Core syncing for this process

 

The first thing we need to do is to set up the core synchronisation component so that we have the other cores available to sync to later on.

Here is an article detailing how to do this

 

http://community.landesk.com/support/docs/DOC-7402

 

Below I have briefly described the process:

 

Firstly go into the core synchronisation window of the core:

From the top menu: Tools > Administration> Core synchronization

patchsyncacrosscores13.PNG

patchsyncacrosscores14.PNG

 

Click on the Plus button

patchsyncacrosscores15.PNGpatchsyncacrosscores16.PNG

 

You are now ready to sync patch content between your core and other cores in your infrastructure

Enter the details of the core you would like to send data to in the window that appears, test and save.

Tick the synchronize this core box if you want the sync to go both ways or you wish for the auto sync option to work when you right click on a patch.

 

If you wish to add another core, Just follow through with the same process

 

Copying Patch content from one core to another

 

This article describes how to copy content between two cores with the software distribution packages:

http://community.landesk.com/support/docs/DOC-16849

 

Here is brief description of the process but using the patch component as our content that we want to copy

 

Select the content that you want to copy.

 

For example we want to copy contents of the scan folder exactly to another core, so that clients attached to that core scan for the same definitions as the main/master core.

As you cannot right click and copy the content of the main scan folder, as it is a default folder and core synchronisation is designed for custom content we are going to have to select the contents of the folder, by click a definition and pressing CTRL + A, this will select all the definitions contained in the folder

patchsyncacrosscores19.PNG

patchsyncacrosscores20.PNG

Now right click a highlighted definition and click "copy to other core(s)……"

The copy content to other cores  window will open

patchsyncacrosscores21.PNG

 

Select the core(s) you want to copy the content to and select copy content, The status column will let you know if the core is available and if the content copy will be successful, a preliminary diagnostics check of the connection between cores.

Once you have selected 'copy status' w this will keep you updated on the status of the copy

patchsyncacrosscores22.PNG

This same process can be applied to the 'Do not scan' folder and on custom folders.

Custom folders have the added benefit that you can sync the whole folder as opposed to just the content., This is because this is custom content that the core sync is designed for.

patchsyncacrosscores23.PNGpatchsyncacrosscores20.PNG

 

As you can see in these two menus you can 'Auto Sync' from this core to other cores.

This option will only work if you selected 'Synchronize to this core' in the setup of the core Synchronisation earlier.

 

Please beware of the following when using the auto sync settings.

With the custom folder's as the whole folder has the option to auto sync, whatever it contains will be auto synced as well.

But with the default folders , such as 'Scan' and 'Do not scan' as you can only setup auto sync on the definitions themselves, when you put definitions in these folders, they will not automatically acquire the auto sync status as with the rest of the definition's, you will have to set these manually.

 

You can also sync the settings of the patch downloads to other cores:

patchsyncacrosscores24.PNG

 

This will further add to the synchronisation of the patch content on the  core, because if you have custom 'Definition group settings' on the main core, you can replicate them onto another core quite easily


Viewing all articles
Browse latest Browse all 1121

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>