OC Setup Wizard used to deploy robots created OS-level default profiles and default alarm policies and populated the wrong group (Windows).
Steps followed:
Downloaded and followed an example csv file, creating a new .csv file with 3 Windows servers.
Information used: IP, OS, Arch, username and password.
Imported the file and waited for about an hour with no result for the servers in the file. Cancelled the action and tried it again, letting it wait for a couple more hours with the same lack of results (no robot installation for the servers).
Received an after-hours call from the NOC team stating that hundreds of alerts were splashing SOI with alerts that made no sense. I quickly discovered that the importing of the CSV file created CDM MCS profiles and default Alarm Policies for the Inventory Group Operating System Windows which had never previously had either. These servers were already part of a managed Windows Robot group in OC which had MCS and Alarm Policies deployed.
After disabling the Alarm Policies and removing the MCS profiles for the new group, SOI was still being splashed with alarms from the now removed Alarm Policies. The only way to successfully get this fixed was to change the Priority in the good Windows Robot group Alarm Policies to 150. Only after that did SOI get the correct alarms.
The actual deployment of robots is working as expected.
The techdocs were updated on September 11, 2025 to clarify the overall OC Setup Wizard process, options and results.
Updating is in process for the OC UI messages on the Setup Wizard deployment screens to highlight the importance of how to use the Next button so that customers are clearly guided through the process without unexpected results. This is planned to be a part of DX UIM 23.4 CU6.
Tentatively, CU6 will be released in Nov. 2025.