Previous Topic: General actionsNext Topic: Example


create—Create Target Computer

This action creates a target computer at the domain manager.

This action has the following format:

targetComputer  action=create
name=computer_name
computertype={machine|user profile| staging server | docking_device}
address=address 
[stagingserver=staging_server_name] 
os=os_name 
[calendarname=calendar_name] 
[user= user] 
[phone= phone] 
[location= location] 
[comment=comment] }
[softwaremanagedsystem [={y/n}] <default = n>]
[racpolicy={common | disabled | deferred | automatic} <default=common>] 
[hostname=host_name]
{[macaddress=mac_address] |
[bootserver=boot_server_name] macaddress=mac_address
osimage=os_image_name }
address

Specifies the network address of the computer.

bootserver

Specifies the name of the boot server the computer is attached to.

calendarname

Specifies the name of the calendar that drives the activities at the target computer

comment

Optional parameter where you can place a comment about the computer.

For instance, information not available in the Computer Attributes or Installation register.

The comment can hold 255 characters.

computertype

An identifier, which can be one of following types:

machine

The specified target is a computer system. It is assumed that a SD agent will be installed on the system.

user profile

Specifies a user profile for a target computer system.
The name of the user profile has the following format:
computer/[domain/]user
For example, a user "john" on system "doe" results in the name "doe/john".
The specified computer must be already defined to DSM when the user profile is created.
The type user_profile replaces the former types "domain_user" and "local_user" which have become obsolete. If they are coded they are mapped to the type user_profile.

Note: The following parameters will be ignored by CADSMCMD when being invoked for ‘targetComputer action=create computerType=“user profile”’:

- Address

- bootServer

- hostName

- macAddress

- os

- osImage

- stagingserver

staging server

The created target computer is a scalability server. It is assumed that SD is installed with this target.

docking device

The created target is a docking device. It is assumed that the address specified is the name of the docking station and that SD is installed with the systems.

hostname

Specifies the host name of the computer.

If not coded, the name of the target computer is used as default.

Note: The parameter “HostName” can only be modified as long as the specified target system has not been registered from the network.
If the system has already been registered, error CMD00149 is reported: “The target has already registered. The operation is not allowed.”

location

If coded, specifies the location of the computer.

macaddress

Specifies the MAC address of the system.

name

Specifies the name of the target.

The name of the target is of one of four types, depending on the value of the "computertype" parameter.

For example, if computertype= is from {machine| staging server| docking device}, then target is a computer system and its name is the name of the computer in the network.

If computertype=user profile, then the name of the user profile is composed of the machine name and the user-id separated by a slash. The user-id can be local machine user-id or a domain user-id.

os

Specifies the operating system type of the target.

For valid values for OS, see Usage of regproc.

The value that is set when creating a target (for instance, Any) will, in current SD server environments, be replaced by the current OS value of the computer when it registers automatically.

Values:
os={AIX|AIX_3.2_RS/6000|AIX_4.1_RS/6000
...|AIX_4.2_RS/6000|AIX_4.3_RS/6000
...|AIX_5.0_RS/6000|AIX_5.1_RS/6000
...|AIX_5.2_RS/6000|AIX_5.3_RS/6000
...|AIX_5.4_RS/6000|AIX_5.5_RS/6000
...|AIX_5.6_RS/6000|AIX_5.7_RS/6000
...|AIX_5.8_RS/6000|ANY|COMPAQ_TRU64_(DEC)
...|COMPAQ_TRU64_5.X_ALPHA
...|DEC_3.0_ALPHA|DEC_3.2_ALPHA
...|DEC_4.0_ALPHA|DGUX|DGUX_4.1_INTEL
...|DGUX_4.1_MC88|DGUX_4.2_INTEL
...|DOS|DRS/NX_7MP_SPARC|DRS/NX_7_SPARC
...|DRS/NX_SPARC|DYNIX|DYNIX_4.2.X_INTEL
...|DYNIX_4.4.X_INTEL|HPUX
...|HPUX_10|HPUX_10_700|HPUX_10_800
...|HPUX_11|HPUX_11I_V2|HPUX_11_700
...|HPUX_11_800|HPUX_11_IA64
...|HPUX_12|HPUX_12I_V2|HPUX_12_700
...|HPUX_12_800|HPUX_12_IA64
...|HPUX_9|HPUX_9_700|HPUX_9_800
...|IRIX|IRIX_6.2|IRIX_6.3
...|IRIX_6.4|IRIX_6.5|LINUX
...|LINUX_2.1_INTEL|LINUX_2.2_INTEL
...|LINUX_2.2_S/390|LINUX_2.3_INTEL
...|LINUX_2.3_S/390|LINUX_2.4_INTEL
...|LINUX_2.4_S/390|LINUX_2.5_INTEL
...|LINUX_2.5_S/390|LINUX_2.6_INTEL
...|LINUX_2.6_INTEL_64-BIT
...|LINUX_2.6_S/390|MACINTOSH
...|MACINTOSH_10.0_PPC|MACINTOSH_10.1_PPC
...|MACINTOSH_10.2_PPC|MACINTOSH_10.3_PPC
...|MACINTOSH_10.4_PPC|NCR_SST
...|NCR_SST_S4I_INTEL|NCR_SST_S4_INTEL
...|NCR_SV|NCR_SV_2X_INTEL
...|NCR_SV_3X_INTEL|NETWARE
...|NETWARE_3_INTEL|NETWARE_4_INTEL
...|NETWARE_5_INTEL|NETWARE_6_INTEL
...|NOKIA_ADMINSUITE|NOKIA_ADMINSUITE_1.0
...|OPENVMS|OPENVMS_5.5_VAX
...|OPENVMS_6.0_ALPHA|OPENVMS_6.0_VAX
...|OPENVMS_6.1_ALPHA|OPENVMS_6.1_VAX
...|OPENVMS_6.2_ALPHA|OPENVMS_6.2_VAX
...|OPENVMS_7.0_ALPHA|OPENVMS_7.0_VAX
...|OPENVMS_7.1_ALPHA|OPENVMS_7.1_VAX
...|OPENVMS_7.2_ALPHA|OPENVMS_7.2_VAX
...|OS/2_16-BIT|OS/2_32-BIT
...|PALM_OS|SCO|SCO_3.2_V5_INTEL
...|SCO_5.2_V5_INTEL|SINIX
...|SINIX_5.42_R4000|SINIX_5.43_R4000
...|SINIX_5.44_R4000|SINIX_5.45_R4000
...|SOLARIS|SOLARIS_10_INTEL
...|SOLARIS_10_SPARC|SOLARIS_2.3_SPARC
...|SOLARIS_2.4_INTEL|SOLARIS_2.4_SPARC
...|SOLARIS_2.5_INTEL|SOLARIS_2.5_SPARC
...|SOLARIS_2.6_INTEL|SOLARIS_2.6_SPARC
...|SOLARIS_7_INTEL|SOLARIS_7_SPARC
...|SOLARIS_8_INTEL|SOLARIS_8_SPARC
...|SOLARIS_9_INTEL|SOLARIS_9_SPARC
...|SUNOS|SUNOS_4.1.4_SPARC
...|UNIX|UNIXWARE|UNIXWARE2.0_INTEL
...|UNIXWARE2.1_INTEL|UNIXWARE7.X_INTEL
...|WINDOWS_16-BIT|WINDOWS_32-BIT
...|WINDOWS_95|WINDOWS_98
...|WINDOWS_ME|WIN_2000|WIN_2000_INTEL
...|WIN_CE|WIN_CE_2.00_MIPS
...|WIN_CE_2.00_SH3|WIN_CE_2.01_MIPS
...|WIN_CE_2.01_SH3|WIN_CE_2.11_ARM
...|WIN_CE_2.11_MIPS|WIN_CE_2.11_SH3
...|WIN_CE_2.11_SH4|WIN_CE_3.00_ARM
...|WIN_CE_3.00_MIPS|WIN_CE_3.00_PPC2002_ARM
...|WIN_CE_3.00_SH3|WIN_CE_3.00_SH4
...|WIN_CE_4.20_MOBILE2003_ARM
...|WIN_LONGHORN_SERVER_INTEL
...|WIN_LONGHORN_SERVER_ITANIUM
...|WIN_LONGHORN_SERVER_X64
...|WIN_NT|WIN_NT_ALPHA|WIN_NT_INTEL
...|WIN_NT_MIPS|WIN_SERVER_2003
...|WIN_SERVER_2003_INTEL
...|WIN_SERVER_2003_ITANIUM
...|WIN_SERVER_2003_X64|WIN_VISTA_INTEL
...|WIN_VISTA_ITANIUM|WIN_VISTA_X64
...|WIN_XP|WIN_XP_INTEL|WIN_XP_ITANIUM
...|WIN_XP_X64}

Note: For an up-to-date list of supported operating systems and their releases, issue the regproc command or the targetcomputer action=create command in verbose mode.

osimage

Specifies the name of the OS image that is assigned to the system created in a planned configuration.

Before activating the configuration to be installed at the target computer the OS image should become available at the boot server attached to the target computer.

This parameter should only be coded with the macAddress parameter. If the installation order should be deployed in advance also the bootserver should be coded.

phone

If coded, specifies the phone number or email address of the computer user.

racpolicy

Optional parameter which specifies the Reinstall after Crash (RAC) policy of the system.

The following values can be used:

common

The common policy will be used for this computer.

disabled

RAC is disabled on this computer. No job container is set up for this computer. However, its installation records in the installations folder on the SD server will be marked as removed, when the SD agent of the computer reports a new OS installation (by a changed UUID).

deferred

A RAC job container will be created. It can be reviewed and modified, since it has to be activated manually.

automatic

A RAC job container will be created and activated, starting the delivery of job orders to the computer.

Default = common.

Note: If you try to change the RAC policy of a computer when it is in the offline mode, the cadsmcmd targetComputer action=modify command generates an error message.

softwaremanagedsystem

This optional parameter marks a target computer as Software Managed System.

stagingserver

Specifies the name of the scalability server.

If coded the target computer to be created is assumed to be connected through the specified scalability server. The scalability server must already be known to the SD.

Note: If this option is not coded, the Domain Manager is becomes the default scalability server.

user

If coded, specifies the name of the user.

Note: For pre-registration of computers to be managed by OSIM, use the macaddress and osimage with targetcomputer action=create command.