Users Guide

Select Hypervisor Profile, Credential Profile, and Server IP from.
NOTE: Host Name, and Server Management NIC are always pool values. For server management NIC, provide the MAC
address of the network port through which you want the operating system to communicate to SCVMM.
If you select Server IP from as Static, and then ensure that you have configured the logical network in SCVMM, and the
following fields are pool values:
● Console Logical Network
● IP Subnet
● Static IP Address
NOTE: Windows Server 2016 operating system deployment on AMD platforms does not support x2apic. Ensure to disable
BIOS x2apic and logical processor settings before installing the operation system.
Non-Windows component for OMIMSSC console extensions
While creating or editing Operational Template for server, perform the following steps for non-windows component:
Select a non-windows operating system, operating system version, type of share folder, ISO file name, location of the ISO file
and the password for the root account of the operating system.
(Optional) Select a Windows type credential profile for accessing the CIFS share.
Host name is a pool value and if you disable DHCP option, and then the following fields are pool values:
● IP Address
● Subnet Mask
● Default Gateway
● Primary DNS
● Secondary DNS
NOTE:
Network File System (NFS) and Common Internet File System (CIFS) share types are supported for non-Windows
operating system deployment.
Create Operational Template from reference Modular
Systems
Before creating Operational Template, ensure that you complete the following tasks:
● Discover a Modular System by using the Discovery feature. For information about discovering Modular Systems, see
Discovering Modular System using manual discovery.
● If you are not using the default update source, and then create an update source. For more information, see Creating update
source.
You can create an Operational Template by capturing the configuration of the reference Modular Systems. After capturing the
configuration, you can directly save the template, or edit the attributes for update source and hardware configuration as per
your requirement. Now you can save the template, that can be used to configure other Modular Systems of the same model.
NOTE:
If you want to configure Active Directory (AD) users on other MX7000 devices ensure that you create an
Operational Template from an MX7000 Modular System where all the AD users are configured.
NOTE: User account’s passwords are not captured in Operational Template, from reference Modular System for security
reasons. Edit the Operational Template to add a new user account and password, and then apply the Operational Template
on the managed Modular Systems. Else, you can apply the Operational Template without any changes to user accounts, and
the same passwords that are used in the reference Modular System are applied on the managed Modular System.
1. In OMIMSSC, do any of the following to open an Operational Template:
● In the OMIMSSC dashboard, click Create Operational Template.
● In the navigation pane, click Profiles > Operational Template, and then click Create.
The Operational Template wizard is displayed.
2. Click Create.
The Operational Template wizard is displayed.
56
Manage Operational Templates