How to Create a Custom Windows Provisioning Profile (Command Line Interface)

Steps

1. To create a variable set for the WindowsImage component, type a command similar to the following example:

   # cr_cli -cmd cdb.vs.add -comp NM:/com/sun/n1osp/untyped/WindowsImage \ -name "windows2003custom" -u admin -p admin -vars \ "osp_server=masterserver-osp;os_name="WIN2003_trial"version=2003; \ installPath="2003customprofile"; \ description=test windows image 2003;min_disk_size=10GB; \ boot_server_name=biwl;boot_server_subnet_address=10.42.42.0; \ boot_server_subnet_ip_address=10.42.42.4;\ boot_srv_active_directory_domain=n1.west.example.com;\ windows_product_directory=D:\\\\RemoteInstall\\\\Setup\\\\English \\\\Images\\\\Win2003_trial"

   ---

   Note –

   The windows_product_directory should be included all on one line. For display purposes, this entry appears on two separate lines.

   ---

   For more information about the variables, see Windows Provisioning Profile Variables.

2. Create a file named /tmp/windows-profile with the following entries.

   custom Windows 2003 EE x86 Profile true

   The entries in this file correspond to the following plan variables.

   • custom specifies the Profile Name.

   • Windows 2003 EE x86 Profile specifies the Profile Description.

   • true specifies that this plan will generate a custom profile.

3. To run the plan, type a command similar to the following example:

   # cr_cli -cmd pe.p.run -u admin -p admin \ -PID NM:/com/sun/n1osp/untyped/WindowsImage-create-profile \ -tar H:NM:risserver-windows -comp - -vs windows2003custom -pto 30 -nto 10 \ -f /tmp/windows-profile

   Note the default N1 SPS user value you specified with the -u option. This user must exist after the OS installation for the N1 SPS Remote Agent software to start on the target host.