Hello,   I think it changed in 3.4, but at any rate, under "Configuration," there is a section for templates and another for profiles. When a template is deployed it creates a profile and assigns it to a server, and additional templates cannot be deployed until they are removed from that profile. You might check these sections to see if this is the issue.
Hi, we are having some issues with OME 3.5.0 and template deployments. We have some configuration templates that we use to set the parameters we want about authentication, power settings, boot options and such, but we configured it to re-create the raid array when we execute this action. So we are using this for new servers and for repurposing the decommissioned ones. For some reason in 3.5.0, after we do a deployment, those servers are greyed out and no longer are elegible for the template deployment. We have seen that you introduced a new warning about production or no new servers should go through configuration compliance, but this will break the automations we already have.    Is this known? Is there any option to disable this failsafe measure?
Template deployment changed its logic in 3.5.0