Hi , I created a baseline and copied to the custom windows patching site but fixlets are originally stored at the main site and got out of sync as below.
So should i copy the fixlets as well to the custom site to get rid of out of sync issue? Or if i exported the baseline action and saved it to re-use once again at some point of time , does it make any issue with out of sync fixlets?
The Baseline Synchronization Dashboard can be quite useful here, both in terms of reporting/monitoring baseline sync status, as well as to re-synchronize the components within a baseline.
Ok, i am using this dashboard for syn up , but question is do i need to sync up baseline if i save the fixlets and baseline into custom site?
Can i re-use the saved fixlet which is out of syn cut saved in the custom site?
Hi!
I think it might be useful to explain why the fixlets are out-of-sync.
Out-of-sync fixlets occur because IBM has updated the content in question since you added it to a baseline. This means you should press edit on the baseline and sync the individual components to bring them to their newer versions.
Fixlets will continue to work if they are out-of-sync so nothing will break!
You definitely don’t want to ignore these out-of-sync fixlets and you definitely don’t want to make copies of them to avoid getting content jpdates.
Once you synced the baseline then you should re-action it and replace any old actions.
The Baseline Syncronization Dashboard that @aram mentioned is useful for spotting baselines that have these out-of-sync components.
Ok, if i understand correctly there is no need to save a copy of fixlets into custom site but just need to sync all fixlets those are out of sync in the baselines.
But intention to use the fixlet copy to save them into custom site so that if in case of superseded it would not be disabled and windows still can still deploy the old package which they have tested before.
I have seen in the baseline which are out of sync disabled the action execution part, and we can’t execute out of sync components as i have attached the screen dump.
If you want to keep using the old version of the Fixlets (and possibly deploy patches that have been superseded by other updates), then do not resync the baseline. The Baseline has a full copy of the fixlet content, as it existed at the time you created the baseline
If you want to always deploy the latest version of the patch, then do synchronize the baseline. Fixlets are updated when the original patch is superseded by another patch; when Microsoft re-releases the download because they’ve fixed an issue with the patch installer; or when IBM has corrected an issue with the Fixlet (such as faulty detection logic or incorrect installer commands).
Usually I export my baselines from the console before I resynch them, just in case I have to document or go back to the old version of the baseline. But in practice I haven’t had a need to do that yet.
Thanks for your suggestions.
