Hi
I am afraid that the signal completion mechanism cannot be used with the Windows images yet.
I have already created an idea on this that has been wishlisted
OSIM signal completion on windows
please feel free to add your vote and comments on the idea
The status change is documented in the original DSM r11 green book
Status Change to Current
Agent install=
his parameter controls when the status change for a specific configuration will change from Installing to Current.
Agent install = No
With this option, the status will change to Current the first time the target boots from hard disk after the boot images have completed their processes.
Agent install = Yes
With this option, the status will remain Installing until the agent plug-in has been installed. When the new agent registers with its scalability server this information is passed to the OSIM system and the status is then changed to current.
BMSConfigID
The BMSConfgID is the ID of the OS installation job in the database. The manager sends the BMSConfgID as a job parameter to the target.
After the installation of the common agent the agent (CSM plug-in) reads the BMSConfigID from c:\osimconf.ini and sends it with the report to the manager.
The manager compares the reported BMSConfigID with the job ID in the database. If it fits, the installation job becomes current. Otherwise we assume the installation has not finished correctly and it is set to Failed with the following error:
[OSM010018] A started OS installation has been aborted on the target.
C:\osimconf.ini is created during the execution of the custom.cmd file contained in the OSImage. If the Custom.cmd is customized, care must be taken to not change any of the entries relating to BMSConfigID or osimconf.ini. If these are modified, it can lead to all future OS installations failing because the agent will not be able to report the BMSConfigID to the Manager.
Does this help?
Rich