In one lab Windows Services & Windows Services (Enhanced) do not show up when trying to add a new profile but Setup ntservices is seen.
In another lab Windows Services & Windows Services (Enhanced) are seen but Setup ntservices does not show up. mcs callback get_probe_templates_package_status reports
template_name |
Setup ntservices |
String |
template_version |
1.18 |
string |
final_time |
2021-03-05T08:00:38:300 |
string |
final_message |
Template with name 'Setup ntservices' and version '1.18' does not exist |
string |
1 nt_services_all_version_templates.zip has been attached.
download and extract.
It containes ntservices_mcs_templates-3.42-auto-migrate.zip, ntservices_mcs_templates-3.43-auto-migrate.zip, ntservices_mcs_templates-3.51-auto-migrate.zip.
Import all three into your local archive.
2 Go to Admin Console > primary hub > mon_config_service > raw configure > migration > enable_auto_migration >
if it is set to false, exit raw configure
if it is set to true > edit value > change to false
3 db clean up steps for your DBA
A) confirm what's there is what's expected.
select * from SSRV2Template where probe = 'ntservices'
the expected return is:
columns are templateName, version, probeversion
Windows Services(Enhanced) 3.5 3.5
ntservices_policy 1.0.0 3.5
ntservices_metric 1.0.0 3.5
ntservices_match_filter 1.0.0 3.5
ntservices_alarm_def 1.0.0 3.5
ntservices_threshold 1.0.0 3.5
Windows Services(Enhanced) 3.42.1 3.3
Windows Services 2.34 null
Windows Services 2.33 null
B) Next is to remove all of these except Windows Services 2.34 null, since it has some existing profiles.
This is to be run four times, each time with a different version so all but 2.34 are removed.
After running this one time, change set @VERSION = '3.5'; to set @VERSION = '1.0.0'; and run, and then set @VERSION = '3.42.1'; and run, and then set @VERSION = '2.33';
set @PROBE = 'ntservices';
declare @VERSION varchar(20);
set @VERSION = '3.5';
delete from SSRV2PackageTemplate where template in (select templateid from ssrv2template where probe = @PROBE and version=@VERSION);
delete from ssrv2container where template in (select templateid from ssrv2template where probe = @PROBE and version=@VERSION);
delete from ssrv2removal where template in (select templateid from ssrv2template where probe = @PROBE and version=@VERSION);
delete from ssrv2configvalue where field in (select id from ssrv2field where template in (select templateid from ssrv2template where probe = @PROBE and version=@VERSION));
delete from ssrv2field where template in (select templateid from ssrv2template where probe = @PROBE and version=@VERSION);
delete from ssrv2profile where template in (select templateid from ssrv2template where probe = @PROBE and version=@VERSION);
delete from ssrv2template where templateid in (select templateid from ssrv2template where probe = @PROBE and version=@VERSION);
4 deploying and activating the templates.
A) deploy ntservices_mcs_templates-3.42-auto-migrate.zip to the primary hub
Go to Admin Console > primary hub > mon_config_service > View Probe Utility in New Window
Select activate_probe_templates_package, enter probe_name: ntservices, templates_package_version 3.42
now verify it as successful the DBA can do this via the probeTemplateupgrade and probetemplatespackage tables (It will show the status as migrated)
You can verify via this callback that we used before.
get_probe_templates_package_status, enter probe_name: ntservices, templates_package_version 3.42.
It should report 'Probe template and all profiles migrated successfully' for Setup ntservices, Windows Services, & Windows Services (Enhanced)
B) repeat the above for ntservices_mcs_templates-3.43-auto-migrate.zip, changing the templates_package_version to 3.43.
C) repeat the above for ntservices_mcs_templates-3.43-auto-migrate.zip, changing the templates_package_version to 3.51.