Windows Filer

Using CA AppLogic › Appliance Developer Guide › Appliance OS Installations › Windows Installations › Windows OS › Windows Filer

Windows Filer

Filesystem level operations over ntfs08 volumes are provided by the Sys_Filer_Window08 template application and the /system_ms:Filer_Windows08 appliance. You can import these from your CA AppLogic software version. You must be a grid maintainer to perform these operations.

Windows Server 2008 Filer

You can import and configure the Windows Server 2008 Filer. The Server Windows exe contains the APK. The APK performs an automated prep script prior to installing the APK. You can disable the automated prep script, if you have already prepared the machine. During the Install, select Custom and disable the Prep script. You can then manually perform the APK prep script. To review the manual steps, refer to Manually Perform APK Prep Script.

Follow these steps:

Import the Sys_Filer_Windows08 application:
1. Go to the CA AppLogic-version Download Directory on the BFC server. For example, /opt/bfc/applogic-versions/<release number>.
2. Copy the file Sys_Filer_Windows08-<version>.tar to the grid controller using following command
```
scp Sys_Filer_Windows08-<version>.tar <controller IP>:/vol/_impex/
```
3. SSH to the grid controller and untar the file using command
```
tar -xf Sys_Filer_Windows08-<version>.tar
```
4. Import the application as follows
```
3t app import Sys_Filer_Windows08 Sys_Filer_Windows08 
```
Import the system_ms catalog:
1. Go to the CA AppLogic-version Download Directory on BFC server.
2. Copy the file system_ms-<version>.tar to the grid controller using following command
```
scp system_ms-<version>.tar <controller IP>:/vol/_impex/
```
3. SSH to the grid controller and untar the file using command
```
tar -xf system_ms-<version>.tar
```
4. Import the catalog /system_ms as follows
```
3t cat import /system_ms system_ms 
```

Note: The /system_ms:Filer_Windows08 appliance has an empty boot volume which is replaced with a working boot volume during the installation procedure detailed below.

Follow these instructions to create a Windows Server 2008 filer appliance (/system_ms:Filer_Windows08). The Filer_Windows08 appliance is based on Windows Server 2008 Standard Edition Core Install 32-bit (either SP1 or SP2). The Core Install is used to reduce the size of the filer appliance boot volume.

The first step in creating this appliance is to create a base server class using the same OS as follows:

Copy a Windows 2008 Server 32-bit ISO image to the impex volume of the grid controller. Use either SP1 or SP2 ISOs.
This example uses the ISO image en_windows_server_2008_datacenter_enterprise_standard_sp2_x86_dvd_342333.iso downloaded from the Microsoft MSDN site.
Open a 3t shell and use the iso2class utility to begin an installation of Windows Server 2008 Standard Edition Core Install 32-bit:
- Execute the following command:
```
util iso2class app_name=win08sc-install iso_volume1=en_windows_server_2008_datacenter_enterprise_standard_sp2_x86_dvd_342333.iso os=windows install_size=4.5G console_type=graphic virt_options=acpi=1 cpu=1 mem=1G. 
```
Note: install_size may vary depending on the operating system installation size.

This command creates and starts the win08sc-install application, booting the singleton iso2class from the specified ISO image.
Access the graphical console of the singleton with one of the following methods:
- Select the win08sc-install application in the application list in the GUI and click the icon for Login (graphic).
- Open the application win08sc-install in the infrastructure editor and select the singleton iso2class.
  Select the Appliance menu, then select Login.
After the graphical console displays, the Windows 2008 Server installation interface should be visible. Proceed to install the OS.
The singleton reboots during installation, rendering the graphical console inoperative. When this occurs, simply close and reopen the graphical console.
When the installation completes, the singleton reboots itself and Windows prompts for the setting of a new password.
Enter your new password and press Enter.

Windows sets a new password for Administrator and displays a message indicating that the Administrator password set successfully.

Click OK.

Windows logs into the administrator desktop automatically.
When the desktop becomes visible, perform the following operations in the command shell:
1. Set the page file size to 16M:
2. wmic computersystem where name="%COMPUTERNAME%" set AutomaticManagedPagefile=False
3. wmic pagefileset where name="C:\\pagefile.sys" set InitialSize=16,MaximumSize=16
4. Reboot: shutdown –r –t 0
After approximately one minute, reopen the graphical console and log in to the Windows desktop.
Note: The following optional steps are also performed in the Prep Script. If you opted to not run the prep script, you need to manually perform these steps,
(Optional) Disable power management hibernation support: powercfg -h off. Execute dir. There should be approximately 1GB of free space on the disk.
(Optional) Set the default Windows disk device timeout value to 60 seconds:
1. Execute regedit to open the registry editor.
2. Navigate to the key HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Disk.
3. Right-click disk in the left pane and select New=>DWORD.
4. Enter TimeOutValue
5. Press Enter.
6. Right-click TimeOutValue and select Modify.
7. Set the type to decimal and enter 60 for the value.
8. Click OK and Save.
If installing the TurboGate PV drivers, then disable TCP checksum offload:
1. In the registry editor, navigate to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Tcpip/Parameters.
2. Right-click Parameters in the left pane and select New=>DWORD. Type DisableTaskOffload, then <enter>.
  Right-click DisableTaskOffload and select Modify.
  
  Enter 1 for the value, then click OK.
3. Close the registry editor.
Activate windows as follows:
Configure external network access:
1. netsh interface ipv4 set address name="Local Area Connection" source=static address=X.X.X.X mask=X.X.X.X gateway=X.X.X.X (use valid network settings)
2. netsh interface ipv4 add dnsserver name="Local Area Connection" X.X.X.X index=Y (where X.X.X.X is the IP address of the DNS Server and Y is its place in the list, for example 1)
Verify external network access. For example, ping www.google.com.
Update the Windows 2008 Server product key and activate Windows:
1. Update the product key: slmgr.vbs –ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (use the appropriate product key); wait approximately 30 seconds for the command to complete asynchronously
2. Activate Windows: slmgr.vbs –ato; wait approximately 1 minute for the command to complete asynchronously
3. Verify activation: slmgr.vbs –xpr. A pop-up window should display, indicating Windows is activated. If not, repeat the previous steps
Shutdown the OS and continue the iso2class install as follows:
1. Shutdown -s -t 0
2. Wait approximately 5 seconds and then, in the 3t shell running the iso2class utility: press the <enter> key and then the Y key followed by the <enter> key. This allows the second volume to become available to the singleton.
After approximately 1 minute, reopen the graphical console and login to the Windows desktop.
To transform the singleton to a fully managed appliance, install the current Windows Server msi.
The installer can now be located on the E drive of the singleton.

In the command shell type E: and <enter> to navigate to the E drive.

Execute Server_Windows.msi For example, Server_Windows-2.0.2-1.msi
If installing the TurboGate PV drivers, copy E:\TurboGate_GTools-3.0.1exe to C:\.
Complete the basic installation:
1. Shutdown -s -t 0
2. Wait approximately 5 seconds and then, in the 3t shell running the iso2class utility. press the <enter> key and then the Y key followed by the <enter> key to continue.
3. When prompted in the 3t shell, select The appliance is fully managed.
  The iso2class stops the application, changes the singleton boundary to a generic server appliance, and restarts the application. The appliance enters the maintenance mode during the restart.
If installing the TurboGate PV drivers:
1. From a 3t shell, ssh into the singleton ssh win08sc-install:main.iso2class.
2. Set the Administrator password, such as net user administrator password (select a password).
3. Login through the graphical console and execute C:\TurboGate_Tools-Setup-V3.0.1.exe.
  Select Install Anyway as required.
  
  Do not reboot after the install. Select ‘I want to reboot later’ and click the Finish button.
4. Execute the following command within a 3t shell:
  app restart win08sc-install --debug
5. If performing the installation on a Xen grid, wait approximately 1 minute after the application begins to start, log in using the graphical console and wait for approximately 1 minute until the driver installation completes. This is indicated by the result of ipconfig /all delineating each ethernet adapter as Halsign GK Ethernet Adapter #X).
  At this point:
  - If the application start has not timed out, it may complete normally; otherwise shutdown the OS from in the graphical console.This causes the app start --debug to fail. Next, execute app stop win08sc-install in the 3T shell
  - If the application start has timed out, execute app stop win08sc-install in the 3T shell followed by shutdown within the graphical console.
6. Execute the following command within the 3Tshell and verify the appliance starts without error:
```
app start win08sc-install
```
ssh into the singleton and set the Administrator password (net user administrator password).
Login through the graphical console and in the command shell, change the computername: wmic computersystem where name="%COMPUTERNAME%" rename name="WIN08SC"
In the SSH session Bash shell:
1. rm -f /appliance/passwd.stamp
2. As required, rm -f /cygdrive/c/TurboGate_Tools-Setup-V3.0.1.exe
3. Set a complex Administrator password. This prevents other users from logging in to the appliance as the Administrator without first setting a new password in an SSH session. For example, net user administrator pq398hpaowht0293j^LWOIFH9htfw9jfe.
4. Exit the ssh session.
5. Execute rm -f ~/.bash_history. This clears the password from the Bash history.
6. Exit the ssh session.
Change the singleton to a WIN08SC catalog appliance class:
1. Stop the application
2. Open the application in the Infrastructure Editor.
3. Right-click the singleton and select Attributes.
  - Change the instance name to WIN08SC.
4. Right-click the singleton and select Modify Boundary:
  - Change the class name to WIN08SC.
  - Enter the description. For example: Windows Server Appliance - based on Windows Server 2008 Standard Edition Core Install SP2 32-bit.
  - Change the following resource settings:
    CPU (num)
    
    Min: 0.25
    
    Max: 4
    
    Default: 0.5
    
    Memory (bytes)
    
    Min: 512
    
    Max: 4G
    
    Default: 768M
    
    Bandwidth (bits/sec)
    
    Min: 1M
    
    Max: 2G
    
    Default: 100M
5. Click Save, then click OK. The Infrastructure Editor displays.
Move the singleton into the /system_ms catalog where you have the required privileges. You must assign yourself full access rights to the catalog before you can move the singleton. See catalog modify_acl in the Command Line Shell Reference Guide for more information.
The WIN08SC base class is now created.

Create Windows Server 2008 File Appliance

Perform these steps to create a Windows Server 2008 filer appliance (/system_ms:Filer_Windows08):

In the Infrastructure Editor, branch the WIN08SC instance in the win08sc-install application.
Right-click the appliance and select Modify Boundary, then the Volumes tab.
1. Add a new placeholder volume to use apk_volume for the placeholder volume with a mount point of D:\.
  This volume is available because of the os=windows options used with iso2class.
  
  If apk_volume is not present, then copy the apk_windows volume from 3t shell using command vol copy _GLOBAL_RO:apk_windows appname:apk_volume
2. Save and then start the application.
ssh into the singleton and set the Administrator password (net user administrator password).
Login to the graphical console of the singleton and in the command shell D:\Filer_Windows-3.0.8-1.msi to install the current Windows Filer MSI.
In the SSH session Bash shell:
1. Set a complex Administrator password that prevents other users from logging to the appliance as the Administrator without first setting a new password in an SSH session. For example, net user administrator pq398hpaowht0293j^LWOIFH9htfw9jfe.
2. Log in to the ssh shell again.
3. Execute rm -f ~/.bash_history. This clears the password from the Bash history.
4. Exit the ssh session.
Stop the application.
Unlock /system_ms:Filer_Windows08
Create a new application win08filer-install with an instance of /system_ms:Filer_Windows08 and branch the instance.
Modify the boundary of the resulting singleton and set the Documentation URL to
```
http://doc.3tera.net/AppLogicxx/en/CatFilerWindows08.html
where xx is the version of AppLogic
```
Save the application.

Execute the following commands in a 3t shell:

vol destroy win08filer-install:Filer_Windows08.boot --force 
vol copy win08sc-install:WIN08SC.boot win08filer-install:Filer_Windows08.boot 
class destroy /system_ms:Filer_Windows08 --force

Access the gui and open the Infrastructure Editor, then drag the singleton into the /system_ms catalog.
In the /system_ms catalog, lock the Filer_Windows08 by executing the following command:
```
class lock /system_ms:Filer_Windows08
```
The /system_ms:Filer_Windows08 appliance class is now located in the catalog and ready for use.