I dont have a script for exporting patch groups, but I wrote a script for exporting and importing Server groups
same idea, just need to switch the BLCLI syntax to have PatchGroups instead of ServerGroups.
Export and Import nested server groups from one BSA environment to another
Thank you Mike. I tried to download the NSH script (both import1.nsh and export1.nsh), and could not download. If possible, can you please give me any alternate location?
Thank you Mike for sharing the script. I was checking the script and have a doubt.
This export script is actually exporting the Server Group. I see the following commands mainly.
blcli_execute ServerGroup groupNameToId
blcli_execute ServerGroup findAllByParentGroup
blcli_execute ServerGroup getGroupId >/dev/null && blcli_storeenv GROUP_ID_LIST
blcli_execute ServerGroup groupNameToDBKey "$PARENT_GROUP"/"$GROUP_NAME" >/dev/null &&
blcli_execute ImportExport exportObject 5007 $GROUP_KEY $EXPORT_PATH/$GROUP_ID >/dev/null
blcli_execute StaticServerGroup createGroupWithParentName
I have not tested the script though, but curious if this Server Group blcli commands are applicable for Depot items as well?
1 of 1 people found this helpful
why don't you just change the file system paths in the original catalog to the new location. copy the files over and run a cuj ?
Thank you Bill.
We face some strange issues with the existing catalog. Some of the Irrelevant Patches do not get deleted. When I delete them, I used to get "Failed to delete Object Graph" and some times, when I delete the Irrelevant Patches after the CUJ, some of the Patch Analysis Jobs (that was created for some other critical Patch analyse only and no irrelevant patch in the include list) are getting deleted - RBAC report helped to identify this.
EVery Irrelevant Patch deletion deletes some or the other PA Jobs. And for most of the Catalog issues, I see creating a new catalog is a suggestion. So, we created a new catalog.
I guess this email clubs many other issues that we face in our environment. Please share your views.
If you delete irrelevant patches, and that causes the deletion of some patching jobs, that usually means that those jobs are explicitly using those patches in an include or exclude list. why are you doing the irrelevant deletion though ?
If I did not delete the Irrelevant Patches, then while creating a new PA Job, I get an error "Smart Groups containing Irrelevant Patches are not allowed in Include/Exclude list" - So, we delete them regularly.
Secondly, the user who created the job (which gets deleted) confirmed that they are not irrelevant patches and are regular and Critical Patches.
Why don’t you just exclude the irrelevant patches from the smart group then ? that works better than having to remember to clean out the catalog.
We do have the default "Irrelevant Patches" Smart Group. However, we still get the error during Analysis. Is this not expected? Should I look in to some other question?
Look at the conditions in that group. one of them will be to include irrelevant patches. add the same property condition in your other smart groups w/ the opposite value of the value in ‘irrelevant patches’ smart group.
1 of 1 people found this helpful
There is a defect where obsolete patches/bulletins can incorrectly be marked/treated as irrelevant
The solution is delivered in BSA 8,7.00, and the workaround is to have these conditions in any Smart Group definition used in an Includes option for a Patch Analysis Job:
Any HotFix Where ??SOFTWARE_PATCH_STATUS_FLAGS*?? does not equal 1 OR
Any Windows Bulletin Where ??SOFTWARE_PATCH_STATUS_FLAGS*?? does not equal 1
Thank you Bill and Jim.
I will check this option and get back.