IBM License Metric Tool (ILMT)

Dear Colleagues,

We have a couple of endpoints affected by an issue of missing IBM ILMT Hardware Capacity scan from OS Task scheduler on windows machines.
As of our current investigation issue caused by the setup.bat and/or configure scripts which were notable to handle the situation when the system environment set with time separator character comma instead of colons.

I found this in configure.log:
(2022-11-15T16:52:34Z) "Running command: SCHTASKS /CREATE /F /SC minute /MO 30 /ST 17.52 /TN IBM ILMT hardware capacity scan /TR C:\PROGRA~1\ansible\GTS\ILMT\bin\run_hw.bat"

Where start time is: /ST 17.52 that might be an issue for setup.bat and causes the "stderr": "ERROR: Invalid starttime value.

Deployment originally done via Ansible playbooks, but we tested manually via PS, same issue happens.
Instead of Successful schedule of the task, we got "Error: Invalid starttime value"

------------------------------
Tamás Maczkó
------------------------------

Dear Colleagues,

We have a couple of endpoints affected by an issue of missing IBM ILMT Hardware Capacity scan from OS Task scheduler on windows machines.
As of our current investigation issue caused by the setup.bat and/or configure scripts which were notable to handle the situation when the system environment set with time separator character comma instead of colons.

I found this in configure.log:
(2022-11-15T16:52:34Z) "Running command: SCHTASKS /CREATE /F /SC minute /MO 30 /ST 17.52 /TN IBM ILMT hardware capacity scan /TR C:\PROGRA~1\ansible\GTS\ILMT\bin\run_hw.bat"

Where start time is: /ST 17.52 that might be an issue for setup.bat and causes the "stderr": "ERROR: Invalid starttime value.

Deployment originally done via Ansible playbooks, but we tested manually via PS, same issue happens.
Instead of Successful schedule of the task, we got "Error: Invalid starttime value"

------------------------------
Tamás Maczkó
------------------------------

Dear Colleagues,

We have a couple of endpoints affected by an issue of missing IBM ILMT Hardware Capacity scan from OS Task scheduler on windows machines.
As of our current investigation issue caused by the setup.bat and/or configure scripts which were notable to handle the situation when the system environment set with time separator character comma instead of colons.

I found this in configure.log:
(2022-11-15T16:52:34Z) "Running command: SCHTASKS /CREATE /F /SC minute /MO 30 /ST 17.52 /TN IBM ILMT hardware capacity scan /TR C:\PROGRA~1\ansible\GTS\ILMT\bin\run_hw.bat"

Where start time is: /ST 17.52 that might be an issue for setup.bat and causes the "stderr": "ERROR: Invalid starttime value.

Deployment originally done via Ansible playbooks, but we tested manually via PS, same issue happens.
Instead of Successful schedule of the task, we got "Error: Invalid starttime value"

------------------------------
Tamás Maczkó
------------------------------

Dear Colleagues,

We have a couple of endpoints affected by an issue of missing IBM ILMT Hardware Capacity scan from OS Task scheduler on windows machines.
As of our current investigation issue caused by the setup.bat and/or configure scripts which were notable to handle the situation when the system environment set with time separator character comma instead of colons.

I found this in configure.log:
(2022-11-15T16:52:34Z) "Running command: SCHTASKS /CREATE /F /SC minute /MO 30 /ST 17.52 /TN IBM ILMT hardware capacity scan /TR C:\PROGRA~1\ansible\GTS\ILMT\bin\run_hw.bat"

Where start time is: /ST 17.52 that might be an issue for setup.bat and causes the "stderr": "ERROR: Invalid starttime value.

Deployment originally done via Ansible playbooks, but we tested manually via PS, same issue happens.
Instead of Successful schedule of the task, we got "Error: Invalid starttime value"

------------------------------
Tamás Maczkó
------------------------------

Hello Oktawian,

Your suggested fix seems to work, tested on one host.
Is it possible to get this fix published in the next ILMT version?

xmltools.vbs is able to provide time with colons:
Note: screenshot taken before the first scheduled run, therefore Last run results was not zero, but schedule went fine.

Also setup.bat executed which added properly the HW scan task to task scheduler.

Dear Colleagues,

We have a couple of endpoints affected by an issue of missing IBM ILMT Hardware Capacity scan from OS Task scheduler on windows machines.
As of our current investigation issue caused by the setup.bat and/or configure scripts which were notable to handle the situation when the system environment set with time separator character comma instead of colons.

I found this in configure.log:
(2022-11-15T16:52:34Z) "Running command: SCHTASKS /CREATE /F /SC minute /MO 30 /ST 17.52 /TN IBM ILMT hardware capacity scan /TR C:\PROGRA~1\ansible\GTS\ILMT\bin\run_hw.bat"

Where start time is: /ST 17.52 that might be an issue for setup.bat and causes the "stderr": "ERROR: Invalid starttime value.

Deployment originally done via Ansible playbooks, but we tested manually via PS, same issue happens.
Instead of Successful schedule of the task, we got "Error: Invalid starttime value"

------------------------------
Tamás Maczkó
------------------------------

Hello Oktawian,

Your suggested fix seems to work, tested on one host.
Is it possible to get this fix published in the next ILMT version?

xmltools.vbs is able to provide time with colons:
Note: screenshot taken before the first scheduled run, therefore Last run results was not zero, but schedule went fine.

Also setup.bat executed which added properly the HW scan task to task scheduler.

Dear Colleagues,

We have a couple of endpoints affected by an issue of missing IBM ILMT Hardware Capacity scan from OS Task scheduler on windows machines.
As of our current investigation issue caused by the setup.bat and/or configure scripts which were notable to handle the situation when the system environment set with time separator character comma instead of colons.

I found this in configure.log:
(2022-11-15T16:52:34Z) "Running command: SCHTASKS /CREATE /F /SC minute /MO 30 /ST 17.52 /TN IBM ILMT hardware capacity scan /TR C:\PROGRA~1\ansible\GTS\ILMT\bin\run_hw.bat"

Where start time is: /ST 17.52 that might be an issue for setup.bat and causes the "stderr": "ERROR: Invalid starttime value.

Deployment originally done via Ansible playbooks, but we tested manually via PS, same issue happens.
Instead of Successful schedule of the task, we got "Error: Invalid starttime value"

------------------------------
Tamás Maczkó
------------------------------

Hello Oktawian,

I can see ilmt 9.2.30 is available already. Can you please update me if this release is ready for my upgrades with the above fix? It would b timely to go for some endpoints and I plan to do it when covered.

Thank you in advance!

Hello Oktawian,

Your suggested fix seems to work, tested on one host.
Is it possible to get this fix published in the next ILMT version?

xmltools.vbs is able to provide time with colons:
Note: screenshot taken before the first scheduled run, therefore Last run results was not zero, but schedule went fine.

Also setup.bat executed which added properly the HW scan task to task scheduler.

Dear Colleagues,

We have a couple of endpoints affected by an issue of missing IBM ILMT Hardware Capacity scan from OS Task scheduler on windows machines.
As of our current investigation issue caused by the setup.bat and/or configure scripts which were notable to handle the situation when the system environment set with time separator character comma instead of colons.

I found this in configure.log:
(2022-11-15T16:52:34Z) "Running command: SCHTASKS /CREATE /F /SC minute /MO 30 /ST 17.52 /TN IBM ILMT hardware capacity scan /TR C:\PROGRA~1\ansible\GTS\ILMT\bin\run_hw.bat"

Where start time is: /ST 17.52 that might be an issue for setup.bat and causes the "stderr": "ERROR: Invalid starttime value.

Deployment originally done via Ansible playbooks, but we tested manually via PS, same issue happens.
Instead of Successful schedule of the task, we got "Error: Invalid starttime value"

------------------------------
Tamás Maczkó
------------------------------

Hello Oktawian,

Your suggested fix seems to work, tested on one host.
Is it possible to get this fix published in the next ILMT version?

xmltools.vbs is able to provide time with colons:
Note: screenshot taken before the first scheduled run, therefore Last run results was not zero, but schedule went fine.

Also setup.bat executed which added properly the HW scan task to task scheduler.

Dear Colleagues,

We have a couple of endpoints affected by an issue of missing IBM ILMT Hardware Capacity scan from OS Task scheduler on windows machines.
As of our current investigation issue caused by the setup.bat and/or configure scripts which were notable to handle the situation when the system environment set with time separator character comma instead of colons.

I found this in configure.log:
(2022-11-15T16:52:34Z) "Running command: SCHTASKS /CREATE /F /SC minute /MO 30 /ST 17.52 /TN IBM ILMT hardware capacity scan /TR C:\PROGRA~1\ansible\GTS\ILMT\bin\run_hw.bat"

Where start time is: /ST 17.52 that might be an issue for setup.bat and causes the "stderr": "ERROR: Invalid starttime value.

Deployment originally done via Ansible playbooks, but we tested manually via PS, same issue happens.
Instead of Successful schedule of the task, we got "Error: Invalid starttime value"

------------------------------
Tamás Maczkó
------------------------------