Use Cases and Deployment Scope
We have been using Cisco UCS in legacy UMM (UCSM managed mode) for over 13 years. When Cisco released a newer generation of product (Cisco UCS-X), we were steered in the direction of Cisco Intersight Infrastructure Service and domains in Intersight Managed Mode. We use Cisco UCS domains in UMM to give us a single pane of glass of all our servers and domains, even though in UMM the domain is read-only. The base (free) features in Cisco Intersight Infrastructure Service give us all the features we need for our legacy domains (Connected TAC, auto Support Request generation and TAC's ability to extract log files). For the domains that we have built in UMM and then transitioned to IMM, the IMM Transition Tool has been indispensable. We found it easier to transition an existing domain with settings that have been in use for years, than configuring policies and profiles from scratch. We heavily rely on Cisco PowerTool commandlets to extract and configure settings on our UMM domains and service profiles and were concerned that we had to adopt usage of the Intersight API to get feature equivalency. This ended up not being an issue in Intersight Managed Mode, since all profiles (domain, server, chassis, etc) are associated with updating templates for each, and consume policies which can be reused. Being "nudged" to use server updating templates (this is the only option, whereas in UMM and Cisco UCS Central we always used initial templates only) allowed for a high level of standardisation in our footprint.
Other Software Used
VMware vSphere, VMware vSAN, Cisco UCS Manager