The following is the known issue in this release.
The following are the key known problems with Windows appliances in this release. Also, see the Windows Appliance Installation Reference for additional procedures and notes.
32-bit Windows 8 is currently not supported by the Halsign Turbogate Drivers; however the 64-bit version of Windows 8 is supported. This issue will be fixed in a subsequent release.
The Windows APK currently does not correctly detect duplicate IP address assignments. Therefore it is up to the user to determine if they have accidentally assigned duplicate IP addresses. This issue will be fixed in a subsequent release.
The Windows filer can fail a volume resize operation if the source volume contains a corrupt directory entry/file. The main source of this problem comes from the fact that some of the Microsoft software installations purposely contain invalid directory entries (we are not sure why this is; this has been observed when a user installed a version of Microsoft SQL Server in their appliance). Additionally, the source volume can be corrupt due to normal wear and tear. This issue can be worked around by running a file system repair on the volume (vol fsrepair) before resizing the volume.
It has been observed by CA that the NTFS volume resize operation fails about two times out of 100. These two failures occurred because the Windows filer failed to start correctly on the grid. If this issue is observed, repeating the resize operation a second time should succeed. This issue however should be resolved in this release; if this issue is observed, notify CA technical support.
The Windows filer uses a Microsoft utility named diskpart to deal with the Windows NTFS volumes. Occasionally diskpart fails to obtain volume information or may fail to mount the volume. This is a very rare failure and may cause either vol create or vol resize to fail over NTFS volumes.
If the user has an application that contains a Windows appliance and one or more Windows appliances are added to the app or terminals are added or removed from the Windows appliances, during the first app start some of the Windows appliances may detect duplicate IPs on their internal network (this can only happen during the first app start after the application is modified). This should not cause any operational failure of the application or require user intervention; the duplicate IP addresses are purely temporary. Worse case, some of the network communication involving any of the Windows appliances may be delayed for up to 30-60 seconds.
Occasionally zeros are reported for the following disk I/O counters for Windows appliances (even though sustained I/O is being generated): Total bytes written/read, # of volume writes/reads, time spent in writes/reads. This is due to a bug in the Windows perfmon API - the zero values is what is being reported by the Windows perfmon API.
Other than the filer MSI, localized Japanese Windows should work under CA AppLogic.
A windows appliance fails to start if the MagicISO virtual DVD-ROM device is installed. Virtual DVD-ROM devices are not currently supported in CA AppLogic for windows-based appliances.
Occasionally it takes several minutes for Windows to detect new NICs inside of an appliance. This occurs when the user adds/removes terminals for a Windows appliance singleton. The extra time it takes to detect these new NICs may cause appliance boot timeouts. To workaround this, increase the boot timeout of your Windows appliance.
If a user has a Windows appliance on their grid and they migrate the appliance to another grid that has different hardware, the Windows appliance may require re-activation (Microsoft's Windows re-activation). The re-activation is triggered when a specific amount of hardware has changed (it is unknown to CA exactly what hardware changes trigger the re-activation). Note that re-activation may require access to the internet from within the Windows appliance. This particular problem was observed after resizing the Windows appliance boot volume and migrating the appliance to a different grid.
This issue only affects Windows 2008 Server 32/64-bit (Windows 2003 server works OK). When accessing a Windows 2008 volume either through the filer using ssh to an appliance, the user may not be able to access/modify files due to permission issues. To access and modify files using the command shell, log in through the graphical console to the Windows desktop and open up a command shell. The command shell can be used to access and modify files.
Currently Windows 2008 DataCenter edition appliances fail to start if configured to use more than eight CPUs (only on Xen-based grids).
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|