

Using CA AppLogic › Appliance Developer Guide › Appliance OS Installations › Windows Installations › Windows OS › Windows VDI and VDS › Windows Server 2012 VDS
Windows Server 2012 VDS
You can import a Windows Server 2012 virtual dedicated server (VDS) template from the download directory to create your appliance.
The following template applications are available:
- VDS_Win12S_rX: Windows 2012 Standard Edition SP1 64-bit
- VDS_Win12DC_rX: Windows 2012 Data Center Edition SP1 64-bit
Import the VDS Template Application
Perform these steps:
- Go to the CA 3Tera AppLogic-version Download Directory on the BFC server.
For example, /opt/bfc/applogic-versions/<release number>.
- Copy the file VDS_WIN12<Edition>_r<Version>.tar file to the grid controller using the following command:
scp VDS_WIN12<Edition>_r<Version>.tar <controller IP>:/vol/_impex/
- SSH to the grid controller and untar the file using the following command:
tar -xf VDS_WIN12<Edition>_r<Version>.tar
- Import the application as follows:
3t app import VDS_WIN12<Edition>_r<Version> VDS_WIN12<Edition>_r<Version>.tar
SCSI-based Windows Server Appliances
Follow these steps:
- Select the VDS template application.
- Open the application in the Infrastructure Editor. You must have full access rights to the application. For more information, see application modify_acl.
- Right-click the singleton and select Modify Boundary in the context menu.
The Modify Boundary window displays.
- In General tab - Advanced section, click the Options button for Virtualization Modes, then select Device Schema as sda|sdb|sdc|sdd.
- Select the Volumes tab, then select the Boot volume device as sda.
- Click OK. The Infrastructure Editor displays.
- Save and close the application.
Create VDS Applications based on Windows Server 2012
In the following instructions:
- y placeholder in WIN12y and VDS_Win12y_rX represents the Windows 2012 Standard or DataCenter Edition that the appliance or application is based upon
- X placeholder in VDS_Win12y_rX represents the VDS application version for the platform edition.
You can verify the VDS application version for the platform and edition on the BFC server in /root/applogic/<release>. Perform an ls VDS* and locate the number after the r. For example, for the file VDS_Win12S_r17-1.2.4-1.tar, X would be 17.
Note: In all Windows VDS, the user name property must be different than the host name.
Perform these steps:
- Create a new singleton using WIN12y:
- Create a new application that includes an instance of WIN12y and branch the class.
- Start the application.
- SSH into the singleton by accessing the SSH/text console of the singleton using one of the following methods:
- Select the application in the application list in the GUI and click the Login (ssh) icon.
- Open the application in the editor and select the singleton WIN12y, then select Login (ssh) in the Appliance drop down menu.
- Set a new administrator password using net user administrator password - select a password.
- Access the graphic console of the singleton using one of the following methods:
- Select the application in the application list and click the Login (graphic) icon.
- Open the application in the editor and select the singleton WIN12y, then select Login (graphic) in the Appliance drop down menu.
- If installing on a Windows 64-bit, verify the executable chcp.com exists in the C:\Windows\SysWOW64\ directory.
If not, copy from C:\Windows\System32\ to C:\Windows\SysWOW64\ .
- Install the Windows VDS exe by downloading self-executing installer from the grid controller using the internal interface. This interface has been configured through DHCP.
- To locate the internal IP address of the controller, execute the following command in a command line shell. The IP address of the DHCP server is the last enumerated interface, such as Local Area Connection 5.
ipconfig /all
- Point IE at http://IP-address:8080/download and download the current Windows VDS exe. For example: VDS_Windows-*.exe.
- Right-click the exe file and download the file to the desktop.
- To install, double-click the exe file.
- Delete the exe file and empty the Recycle Bin.
- Delete the junction points on Windows volumes as described in the Windows Server appliance WIN12y.
- Within SSH session Bash shell:
- Set a new complex password, such as net user administrator pq398hpaowht0293j^LWOIFH9htfw9jfe.
- Exit the SSH session.
- SSH into the singleton and execute rm -f ~/.bash_history. The password is cleared from the bash history.
- Stop the application and copy the boot volume of the WIN12y singleton to the boot volume of the VDS_Win12y_rX application.
For example:
vol copy my-app:WIN12y.boot VDS_Win12y_rX:VDS_WIN12y.boot
The VDS_Win12y_rX template application is now ready for use.
Copyright © 2013 CA Technologies.
All rights reserved.
 
|
|