2016-01-19 15:15:59 +01:00
<?xml version="1.0" encoding="utf-8"?>
2013-06-24 13:41:48 +02:00
<root>
<!--
Microsoft ResX Schema
Version 2.0
The primary goals of this format is to allow a simple XML format
that is mostly human readable. The generation and parsing of the
various data types are done through the TypeConverter classes
associated with the data types.
Example:
... ado.net/XML headers & schema ...
<resheader name="resmimetype">text/microsoft-resx</resheader>
<resheader name="version">2.0</resheader>
<resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
<resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
<data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
<data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
<data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
<value>[base64 mime encoded serialized .NET Framework object]</value>
</data>
<data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
<value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
<comment>This is a comment</comment>
</data>
There are any number of "resheader" rows that contain simple
name/value pairs.
Each data row contains a name, and value. The row also contains a
type or mimetype. Type corresponds to a .NET class that support
text/value conversion through the TypeConverter architecture.
Classes that don't support this are serialized and stored with the
mimetype set.
The mimetype is used for serialized objects, and tells the
ResXResourceReader how to depersist the object. This is currently not
extensible. For a given mimetype the value must be set accordingly:
Note - application/x-microsoft.net.object.binary.base64 is the format
that the ResXResourceWriter will generate, however the reader can
read any of the formats listed below.
mimetype: application/x-microsoft.net.object.binary.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.soap.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Soap.SoapFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.bytearray.base64
value : The object must be serialized into a byte array
: using a System.ComponentModel.TypeConverter
: and then encoded with base64 encoding.
-->
<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
<xsd:element name="root" msdata:IsDataSet="true">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<xsd:element name="metadata">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" />
</xsd:sequence>
<xsd:attribute name="name" use="required" type="xsd:string" />
<xsd:attribute name="type" type="xsd:string" />
<xsd:attribute name="mimetype" type="xsd:string" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="assembly">
<xsd:complexType>
<xsd:attribute name="alias" type="xsd:string" />
<xsd:attribute name="name" type="xsd:string" />
</xsd:complexType>
</xsd:element>
<xsd:element name="data">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
<xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
<xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
<xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="resheader">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" />
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<resheader name="resmimetype">
<value>text/microsoft-resx</value>
</resheader>
<resheader name="version">
<value>2.0</value>
</resheader>
<resheader name="reader">
2014-01-06 16:48:14 +01:00
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
2013-06-24 13:41:48 +02:00
</resheader>
<resheader name="writer">
2014-01-06 16:48:14 +01:00
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
2013-06-24 13:41:48 +02:00
</resheader>
<data name="ACTION_ACTIVATING_MULTIPLE_VDIS_STATUS" xml:space="preserve">
<value>Activating virtual disks...</value>
</data>
<data name="ACTION_ACTIVATING_MULTIPLE_VDIS_TITLE" xml:space="preserve">
<value>Activating Multiple Virtual Disks</value>
</data>
<data name="ACTION_CHANGED_DISK_SIZE_FOR" xml:space="preserve">
<value>Disk size changed for '{0}'.</value>
</data>
2016-08-01 10:25:10 +02:00
<data name="ACTION_CHANGE_CONTROL_DOMAIN_MEMORY" xml:space="preserve">
<value>Changing control domain memory settings on '{0}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_CHANGE_DISK_SIZE" xml:space="preserve">
<value>Change disk size</value>
</data>
<data name="ACTION_CHANGE_EMAIL_OPTIONS" xml:space="preserve">
<value>Change email options</value>
</data>
<data name="ACTION_CHANGE_HOME_SERVER" xml:space="preserve">
<value>Change home server</value>
</data>
<data name="ACTION_CHANGE_HOST_PASSWORD_DONE" xml:space="preserve">
<value>Administrator password changed</value>
</data>
<data name="ACTION_CHANGE_HOST_PASSWORD_IN_PROGRESS" xml:space="preserve">
<value>Changing administrator password...</value>
</data>
<data name="ACTION_CHANGE_HOST_PASSWORD_TITLE" xml:space="preserve">
<value>Changing administrator password on {0}</value>
</data>
<data name="ACTION_CHANGE_LOG_DESTINATION" xml:space="preserve">
<value>Change log destination</value>
</data>
<data name="ACTION_CHANGE_MEMORY_SETTINGS" xml:space="preserve">
<value>Changing memory settings for {0}...</value>
</data>
<data name="ACTION_CHANGE_MEMORY_SETTINGS_DONE" xml:space="preserve">
<value>Changed memory settings for {0}</value>
</data>
<data name="ACTION_CHANGE_MULTIPATH" xml:space="preserve">
<value>Change multipath setting</value>
</data>
<data name="ACTION_CHANGE_NETWORKING_BRINGING_DOWN" xml:space="preserve">
<value>Removing IP address from {0}...</value>
</data>
<data name="ACTION_CHANGE_NETWORKING_BRINGING_DOWN_DONE" xml:space="preserve">
<value>IP address on {0} deconfigured</value>
</data>
<data name="ACTION_CHANGE_NETWORKING_BRINGING_UP" xml:space="preserve">
<value>Configuring IP address on {0}...</value>
</data>
<data name="ACTION_CHANGE_NETWORKING_BRINGING_UP_DONE" xml:space="preserve">
<value>IP address on {0} configured</value>
</data>
<data name="ACTION_CHANGE_NETWORKING_DEPURPOSED" xml:space="preserve">
<value>Management facility on {0} deconfigured</value>
</data>
<data name="ACTION_CHANGE_NETWORKING_DEPURPOSING" xml:space="preserve">
<value>Deconfiguring management facility on {0}...</value>
</data>
<data name="ACTION_CHANGE_NETWORKING_DONE" xml:space="preserve">
<value>Networking reconfiguration done</value>
</data>
<data name="ACTION_CHANGE_NETWORKING_MANAGEMENT_RECONFIGURED" xml:space="preserve">
<value>Management interface on {0} configured</value>
</data>
<data name="ACTION_CHANGE_NETWORKING_MANAGEMENT_RECONFIGURING" xml:space="preserve">
<value>Configuring management interface on {0}...</value>
</data>
<data name="ACTION_CHANGE_NETWORKING_TITLE" xml:space="preserve">
<value>Reconfiguring server networking</value>
</data>
<data name="ACTION_CHANGE_POWER_ON" xml:space="preserve">
<value>Change power on settings</value>
</data>
<data name="ACTION_CHANGE_SHADOW_MULTIPLIER" xml:space="preserve">
<value>Change shadow multiplier</value>
</data>
<data name="ACTION_CHANGING_DISK_SIZE_FOR" xml:space="preserve">
<value>Changing disk size for '{0}'...</value>
</data>
<data name="ACTION_CHANGING_EMAIL_OPTIONS_FOR" xml:space="preserve">
<value>Changing email options for '{0}'...</value>
</data>
<data name="ACTION_CHANGING_HOME_SERVER_FOR" xml:space="preserve">
<value>Changing home server for '{0}'...</value>
</data>
<data name="ACTION_CHANGING_LOG_DESTINATION_FOR" xml:space="preserve">
<value>Changing log destination for '{0}'...</value>
</data>
<data name="ACTION_CHANGING_MULTIPATH_FOR" xml:space="preserve">
<value>Changing multipath setting for '{0}'...</value>
</data>
<data name="ACTION_CHANGING_POWER_ON" xml:space="preserve">
<value>Changing power on settings...</value>
</data>
<data name="ACTION_CHANGING_SHADOW_MULTIPLIER_FOR" xml:space="preserve">
<value>Changing shadow multiplier for '{0}'...</value>
</data>
2015-02-05 18:01:14 +01:00
<data name="ACTION_CHECK_DISK_SPACE_DESCRIPTION" xml:space="preserve">
<value>Checking disk space on {0}</value>
</data>
<data name="ACTION_CHECK_DISK_SPACE_TITLE" xml:space="preserve">
<value>Check disk space</value>
</data>
<data name="ACTION_CLEANUP_DISK_SPACE_DESCRIPTION" xml:space="preserve">
<value>Cleaning up disk space on {0}</value>
</data>
<data name="ACTION_CLEANUP_DISK_SPACE_SUCCESS" xml:space="preserve">
<value>Successfully cleaned up disk space on {0}</value>
</data>
<data name="ACTION_CLEANUP_DISK_SPACE_TITLE" xml:space="preserve">
<value>Clean up disk space</value>
</data>
2016-09-26 18:44:17 +02:00
<data name="ACTION_CONFUGURE_PVS_SITE_DESCRIPTION" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Configuring PVS-Accelerator</value>
2016-09-26 18:44:17 +02:00
</data>
<data name="ACTION_CONFUGURE_PVS_SITE_DONE" xml:space="preserve">
<value>Configured</value>
</data>
<data name="ACTION_CONFUGURE_PVS_SITE_TITLE" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Configure PVS-Accelerator on '{0}'</value>
2016-09-26 18:44:17 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_CREATE_BOND_DESCRIPTION" xml:space="preserve">
<value>Creating {0} ...</value>
</data>
<data name="ACTION_CREATE_BOND_DONE" xml:space="preserve">
<value>{0} created</value>
</data>
<data name="ACTION_CREATE_BOND_TITLE" xml:space="preserve">
<value>Creating {0}</value>
</data>
<data name="ACTION_DEACTIVATING_MULTIPLE_VDIS_STATUS" xml:space="preserve">
<value>Deactivating virtual disks...</value>
</data>
<data name="ACTION_DEACTIVATING_MULTIPLE_VDIS_TITLE" xml:space="preserve">
<value>Deactivating Multiple Virtual Disks</value>
</data>
2016-09-26 18:44:17 +02:00
<data name="ACTION_DELETE_PVS_SITE_DESCRIPTION" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Deleting cache configuration</value>
2016-09-26 18:44:17 +02:00
</data>
<data name="ACTION_DELETE_PVS_SITE_DONE" xml:space="preserve">
<value>Done</value>
</data>
<data name="ACTION_DELETE_PVS_SITE_TITLE" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Deleting cache configuration on '{0}'</value>
2016-09-26 18:44:17 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_DELETING_MULTIPLE_STORAGE_ITEMS_STATUS" xml:space="preserve">
<value>Deleting storage items...</value>
</data>
<data name="ACTION_DELETING_MULTIPLE_STORAGE_ITEMS_TITLE" xml:space="preserve">
<value>Deleting Multiple Storage Items</value>
</data>
<data name="ACTION_DESTROY_BOND_DESCRIPTION" xml:space="preserve">
<value>Destroying {0} ...</value>
</data>
<data name="ACTION_DESTROY_BOND_DONE" xml:space="preserve">
<value>{0} destroyed</value>
</data>
<data name="ACTION_DESTROY_BOND_TITLE" xml:space="preserve">
<value>Destroying {0}</value>
</data>
2016-09-06 15:53:46 +02:00
<data name="ACTION_DETACHING_MULTIPLE_VDIS_STATUS" xml:space="preserve">
<value>Detaching storage items...</value>
2013-06-24 13:41:48 +02:00
</data>
2016-09-06 15:53:46 +02:00
<data name="ACTION_DETACHING_MULTIPLE_VDIS_TITLE" xml:space="preserve">
2013-06-24 13:41:48 +02:00
<value>Detaching Multiple Storage Items</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="ACTION_DISABLED_PVS_READ_CACHING" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Disabled PVS-Accelerator for selected VMs</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
2016-09-01 15:59:37 +02:00
<data name="ACTION_DISABLE_LIVE_PATCHING" xml:space="preserve">
<value>Disable live patching</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="ACTION_DISABLE_PVS_READ_CACHING" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Disable PVS-Accelerator</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
<data name="ACTION_DISABLE_PVS_READ_CACHING_FOR" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Disabling PVS-Accelerator for VM '{0}'</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
2015-02-06 18:46:58 +01:00
<data name="ACTION_DISABLE_VM_ENLIGHTENMENT_DESCRIPTION" xml:space="preserve">
2015-02-10 12:42:29 +01:00
<value>Disabling </value>
2015-02-06 18:46:58 +01:00
</data>
<data name="ACTION_DISABLE_VM_ENLIGHTENMENT_TITLE" xml:space="preserve">
2015-02-24 11:46:11 +01:00
<value>Disable container management on VM '{0}'</value>
2015-02-06 18:46:58 +01:00
</data>
2016-09-01 15:59:37 +02:00
<data name="ACTION_DISABLING_LIVE_PATCHING" xml:space="preserve">
<value>Disabling live patching for '{0}'</value>
</data>
2016-10-11 14:13:50 +02:00
<data name="ACTION_DISABLING_PVS_READ_CACHING" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Disabling PVS-Accelerator for selected VMs</value>
2016-10-11 14:13:50 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_DISK_ACTIVATED" xml:space="preserve">
<value>Activated disk...</value>
</data>
<data name="ACTION_DISK_ACTIVATING" xml:space="preserve">
<value>Activating disk...</value>
</data>
<data name="ACTION_DISK_ACTIVATING_TITLE" xml:space="preserve">
<value>Activating disk '{0}' on VM '{1}'...</value>
</data>
<data name="ACTION_DISK_ADDED" xml:space="preserve">
<value>Added disk</value>
</data>
<data name="ACTION_DISK_ADDING" xml:space="preserve">
<value>Adding disk</value>
</data>
<data name="ACTION_DISK_ADDING_TITLE" xml:space="preserve">
<value>Creating disk '{0}' on SR '{1}'</value>
</data>
<data name="ACTION_DISK_ATTACHING" xml:space="preserve">
<value>Attaching disk to VM '{0}'...</value>
</data>
<data name="ACTION_DISK_DEACTIVATED" xml:space="preserve">
<value>Deactivated disk</value>
</data>
<data name="ACTION_DISK_DEACTIVATING" xml:space="preserve">
<value>Deactivating disk...</value>
</data>
<data name="ACTION_DISK_DEACTIVATING_TITLE" xml:space="preserve">
<value>Deactivating disk '{0}' on VM '{1}'...</value>
</data>
<data name="ACTION_DISK_DELETING_TITLE" xml:space="preserve">
<value>Deleting disk '{0}' from SR '{1}'</value>
</data>
<data name="ACTION_DISK_DETACHED" xml:space="preserve">
<value>Detached disk</value>
</data>
<data name="ACTION_DISK_DETACHING" xml:space="preserve">
<value>Detaching disk</value>
</data>
<data name="ACTION_DISK_DETACHING_TITLE" xml:space="preserve">
<value>Detaching disk '{0}' from VM '{1}'</value>
</data>
<data name="ACTION_DISK_WAITING_FOR_AVAILABLE" xml:space="preserve">
<value>Waiting for the volume to become available...</value>
</data>
<data name="ACTION_DR_CONFIGURING" xml:space="preserve">
<value>Configuring DR</value>
</data>
<data name="ACTION_DR_DISABLED" xml:space="preserve">
<value>Pool metadata replication disabled</value>
</data>
<data name="ACTION_DR_DISABLING" xml:space="preserve">
<value>Disabling pool metadata replication</value>
</data>
<data name="ACTION_DR_DISABLING_ON" xml:space="preserve">
<value>Disabling pool metadata replication on storage {0}</value>
</data>
<data name="ACTION_DR_ENABLED" xml:space="preserve">
<value>Pool metadata replication enabled</value>
</data>
<data name="ACTION_DR_ENABLING" xml:space="preserve">
<value>Enabling pool metadata replication</value>
</data>
<data name="ACTION_DR_ENABLING_ON" xml:space="preserve">
<value>Enabling pool metadata replication on storage '{0}'</value>
</data>
<data name="ACTION_DR_RECOVER_APPLIANCE_TITLE" xml:space="preserve">
<value>Recover vApp '{0}'</value>
</data>
<data name="ACTION_DR_RECOVER_DONE" xml:space="preserve">
<value>'{0}' recovered</value>
</data>
<data name="ACTION_DR_RECOVER_STATUS" xml:space="preserve">
<value>Recovering</value>
</data>
<data name="ACTION_DR_RECOVER_VM_TITLE" xml:space="preserve">
<value>Recover VM '{0}'</value>
</data>
<data name="ACTION_DR_TASK_CREATE_DONE" xml:space="preserve">
<value>Storage Repositories prepared</value>
</data>
<data name="ACTION_DR_TASK_CREATE_STATUS" xml:space="preserve">
<value>Preparing Storage Repositories</value>
</data>
<data name="ACTION_DR_TASK_CREATE_TITLE" xml:space="preserve">
<value>Prepare Storage Repositories</value>
</data>
<data name="ACTION_DR_TASK_DESTROY_DONE" xml:space="preserve">
<value>DR cleanup completed</value>
</data>
<data name="ACTION_DR_TASK_DESTROY_STATUS" xml:space="preserve">
<value>Performing DR cleanup...</value>
</data>
<data name="ACTION_DR_TASK_DESTROY_TITLE" xml:space="preserve">
<value>DR cleanup ({0})</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="ACTION_ENABLED_PVS_READ_CACHING" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Enabled PVS-Accelerator for selected VMs</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
2016-09-01 15:59:37 +02:00
<data name="ACTION_ENABLE_LIVE_PATCHING" xml:space="preserve">
<value>Enable live patching</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="ACTION_ENABLE_PVS_READ_CACHING" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Enable PVS-Accelerator</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
<data name="ACTION_ENABLE_PVS_READ_CACHING_FOR" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Enabling PVS-Accelerator for VM '{0}' on '{1}'</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
2015-02-06 18:46:58 +01:00
<data name="ACTION_ENABLE_VM_ENLIGHTENMENT_DESCRIPTION" xml:space="preserve">
2015-02-10 12:42:29 +01:00
<value>Enabling</value>
2015-02-06 18:46:58 +01:00
</data>
<data name="ACTION_ENABLE_VM_ENLIGHTENMENT_TITLE" xml:space="preserve">
2015-02-24 11:46:11 +01:00
<value>Enable container management on VM '{0}'</value>
2015-02-06 18:46:58 +01:00
</data>
2016-09-01 15:59:37 +02:00
<data name="ACTION_ENABLING_LIVE_PATCHING" xml:space="preserve">
<value>Enabling live patching for '{0}'</value>
</data>
2016-10-11 14:13:50 +02:00
<data name="ACTION_ENABLING_PVS_READ_CACHING" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Enabling PVS-Accelerator for selected VMs</value>
2016-10-11 14:13:50 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_EXPORT_DESCRIPTION_BLOCK_CHECKSUM_FAILED" xml:space="preserve">
<value>Export failed due to a block checksum mismatch. Please retry the export.</value>
</data>
<data name="ACTION_EXPORT_DESCRIPTION_CANCELLED" xml:space="preserve">
<value>Export canceled</value>
</data>
<data name="ACTION_EXPORT_DESCRIPTION_DISK_FULL" xml:space="preserve">
<value>Export failed: disk full.</value>
</data>
<data name="ACTION_EXPORT_DESCRIPTION_FAILED" xml:space="preserve">
<value>Export failed</value>
</data>
2014-08-04 11:38:49 +02:00
<data name="ACTION_EXPORT_DESCRIPTION_FAILED_OF_OPEN_FILE" xml:space="preserve">
<value>Export failed due to open destination file {0} failed</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_EXPORT_DESCRIPTION_HEADER_CHECKSUM_FAILED" xml:space="preserve">
<value>Export failed due to a header checksum mismatch. Please retry the export.</value>
</data>
<data name="ACTION_EXPORT_DESCRIPTION_IN_PROGRESS" xml:space="preserve">
<value>Exporting...</value>
</data>
<data name="ACTION_EXPORT_DESCRIPTION_PREPARING" xml:space="preserve">
<value>Preparing to export</value>
</data>
<data name="ACTION_EXPORT_DESCRIPTION_SUCCESSFUL" xml:space="preserve">
<value>Exported</value>
</data>
<data name="ACTION_EXPORT_DESCRIPTION_VDI_IN_USE" xml:space="preserve">
<value>Export failed: disk in use elsewhere.</value>
</data>
2014-07-25 09:35:18 +02:00
<data name="ACTION_EXPORT_POOL_RESOURCE_CANCEL_AND_FILE_UNDELETE" xml:space="preserve">
<value>Export canceled and deleting destination file '{0}' failed</value>
</data>
<data name="ACTION_EXPORT_POOL_RESOURCE_LIST_FROM_X" xml:space="preserve">
<value>Exporting pool resource list from '{0}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_EXPORT_TASK_DESCRIPTION" xml:space="preserve">
<value>Exporting {0} to backup file</value>
</data>
<data name="ACTION_EXPORT_TASK_NAME" xml:space="preserve">
<value>Exporting {0}</value>
</data>
<data name="ACTION_EXPORT_VERIFY" xml:space="preserve">
<value>Verifying Export...</value>
</data>
2013-09-26 15:45:26 +02:00
<data name="ACTION_GETTING_DATASOURCES" xml:space="preserve">
<value>Fetching data sources</value>
</data>
<data name="ACTION_GET_DATASOURCES" xml:space="preserve">
<value>Fetch data sources</value>
</data>
2015-02-05 18:01:14 +01:00
<data name="ACTION_GET_DISK_SPACE_REQUIREMENTS_DESCRIPTION" xml:space="preserve">
<value>Getting space requirements on {0}</value>
</data>
<data name="ACTION_GET_DISK_SPACE_REQUIREMENTS_TITLE" xml:space="preserve">
<value>Get space requirements</value>
</data>
2015-08-27 01:30:02 +02:00
<data name="ACTION_GET_HEALTH_CHECK_RESULT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Get Health Check analysis result from [Citrix] Insight Services</value>
2015-08-27 01:30:02 +02:00
</data>
<data name="ACTION_GET_HEALTH_CHECK_RESULT_FAILED" xml:space="preserve">
<value>Failed to get the analysis result</value>
</data>
<data name="ACTION_GET_HEALTH_CHECK_RESULT_PROGRESS" xml:space="preserve">
<value>Getting the analysis result</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_GET_METADATA_VDIS_DONE" xml:space="preserve">
<value>Action completed. {0} VDIs found.</value>
</data>
<data name="ACTION_GET_METADATA_VDIS_STATUS" xml:space="preserve">
<value>Looking for metadata VDIs on '{0}'</value>
</data>
<data name="ACTION_GET_METADATA_VDIS_TITLE" xml:space="preserve">
<value>Get metadata VDIs</value>
</data>
<data name="ACTION_GET_SYSTEM_STATUS_CAPABILITIES" xml:space="preserve">
<value>Retrieving system status capabilities</value>
</data>
<data name="ACTION_GET_SYSTEM_STATUS_CAPABILITIES_DONE" xml:space="preserve">
<value>Retrieved system status capabilities</value>
</data>
<data name="ACTION_GET_SYSTEM_STATUS_CAPABILITIES_ON" xml:space="preserve">
<value>Retrieving system status capabilities from server {0}</value>
</data>
<data name="ACTION_HA_UNPROTECT_VM_DESCRIPTION" xml:space="preserve">
<value>Setting HA restart priority</value>
</data>
<data name="ACTION_HA_UNPROTECT_VM_TITLE" xml:space="preserve">
<value>Setting HA restart priority on '{0}' to '{1}'</value>
</data>
2015-07-29 09:44:41 +02:00
<data name="ACTION_HEALTHCHECK_AUTHENTICATION" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Authentication with [Citrix] Insight Services</value>
2015-07-29 09:44:41 +02:00
</data>
<data name="ACTION_HEALTHCHECK_AUTHENTICATION_PROGRESS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Authenticating with [Citrix] Insight Services</value>
2015-07-29 09:44:41 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_HOSTS_REBOOTED" xml:space="preserve">
<value>Servers rebooted</value>
</data>
<data name="ACTION_HOSTS_REBOOTING" xml:space="preserve">
<value>Rebooting servers</value>
</data>
<data name="ACTION_HOSTS_SHUTDOWN" xml:space="preserve">
<value>Servers shut down</value>
</data>
<data name="ACTION_HOSTS_SHUTTING_DOWN" xml:space="preserve">
<value>Shutting down servers</value>
</data>
<data name="ACTION_HOST_REBOOTED" xml:space="preserve">
<value>Server '{0}' rebooted</value>
</data>
<data name="ACTION_HOST_REBOOTING" xml:space="preserve">
<value>Server '{0}' rebooting</value>
</data>
<data name="ACTION_HOST_SHUTDOWN" xml:space="preserve">
<value>Server '{0}' shut down</value>
</data>
<data name="ACTION_HOST_SHUTTING_DOWN" xml:space="preserve">
<value>Server '{0}' shutting down</value>
</data>
<data name="ACTION_HOST_STARTED" xml:space="preserve">
<value>Powered on</value>
</data>
<data name="ACTION_HOST_STARTING" xml:space="preserve">
<value>Sending remote power-on request...</value>
</data>
<data name="ACTION_HOST_START_FAILED" xml:space="preserve">
<value>Server '{0}' failed to respond to the remote power-on request.</value>
</data>
<data name="ACTION_HOST_START_TITLE" xml:space="preserve">
<value>Powering on server '{0}'</value>
</data>
<data name="ACTION_ISCSI_IQN_SCANNING" xml:space="preserve">
<value>Scanning for IQNs on iSCSI filer {0}</value>
</data>
<data name="ACTION_ISCSI_LUN_SCANNING" xml:space="preserve">
<value>Scanning for LUNs on iSCSI filer {0}</value>
</data>
<data name="ACTION_MIGRATING_X_VDIS" xml:space="preserve">
<value>Migrating {0} virtual disks to {1}</value>
</data>
2016-09-27 22:14:07 +02:00
<data name="ACTION_MIGRATING_X_VDIS_COMPLETED" xml:space="preserve">
<value>Completed migrating virtual disks</value>
</data>
<data name="ACTION_MIGRATING_X_VDIS_STARTED" xml:space="preserve">
<value>Started migrating virtual disks</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_MOVING_VDI_STATUS" xml:space="preserve">
<value>Moving virtual disk '{0}'...</value>
</data>
<data name="ACTION_MOVING_VDI_TITLE" xml:space="preserve">
<value>Moving Virtual Disk '{0}' to SR '{1}'</value>
</data>
<data name="ACTION_MOVING_X_VDIS" xml:space="preserve">
<value>Moving {0} virtual disks to {1}</value>
</data>
2016-09-27 22:14:07 +02:00
<data name="ACTION_MOVING_X_VDIS_COMPLETED" xml:space="preserve">
<value>Completed moving virtual disks</value>
</data>
<data name="ACTION_MOVING_X_VDIS_STARTED" xml:space="preserve">
<value>Started moving virtual disks</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_MULTIPLE_DR_TASK_CREATE_END" xml:space="preserve">
2013-07-03 15:54:05 +02:00
<value>Storage Repositories prepared</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_MULTIPLE_DR_TASK_CREATE_START" xml:space="preserve">
2013-07-03 15:54:05 +02:00
<value>Preparing Storage Repositories</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_MULTIPLE_DR_TASK_CREATE_TITLE" xml:space="preserve">
<value>Prepare Storage Repositories</value>
</data>
2015-02-09 17:53:29 +01:00
<data name="ACTION_PAUSE_CONTAINER_DESCRIPTION" xml:space="preserve">
<value>Pausing</value>
</data>
<data name="ACTION_PAUSE_CONTAINER_END_DESCRIPTION" xml:space="preserve">
<value>Paused</value>
</data>
<data name="ACTION_PAUSE_CONTAINER_TITLE" xml:space="preserve">
<value>Pausing Docker Container '{0}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_PIF_SCAN_START_DESC" xml:space="preserve">
<value>Scanning...</value>
</data>
<data name="ACTION_PIF_SCAN_TITLE" xml:space="preserve">
<value>Scanning NICs on server '{0}'</value>
</data>
<data name="ACTION_PIF_UNPLUG_PLUG_DESC" xml:space="preserve">
<value>Refreshing networks...</value>
</data>
<data name="ACTION_PIF_UNPLUG_PLUG_TITLE" xml:space="preserve">
<value>Refreshing Networks</value>
</data>
<data name="ACTION_POOL_WIZARD_CREATE_DESCRIPTION_ADDING_MEMBERS" xml:space="preserve">
<value>Adding members...</value>
</data>
<data name="ACTION_POOL_WIZARD_CREATE_DESCRIPTION_DISCONNECTING" xml:space="preserve">
<value>Dropping connections to members...</value>
</data>
<data name="ACTION_POOL_WIZARD_CREATE_DESCRIPTION_DONE" xml:space="preserve">
<value>Creating pool completed</value>
</data>
<data name="ACTION_PREPARING" xml:space="preserve">
<value>Preparing...</value>
</data>
<data name="ACTION_REMOVE_ALERTS_DESCRIPTION" xml:space="preserve">
<value>Removing alerts...</value>
</data>
<data name="ACTION_REMOVE_ALERTS_DONE" xml:space="preserve">
<value>Removed {0} alerts</value>
</data>
<data name="ACTION_REMOVE_ALERTS_DONE_ONE" xml:space="preserve">
<value>Removed 1 alert</value>
</data>
<data name="ACTION_REMOVE_ALERTS_ON_CLIENT_TITLE" xml:space="preserve">
2014-07-29 11:19:54 +02:00
<value>Removing {0} client alerts</value>
</data>
<data name="ACTION_REMOVE_ALERTS_ON_CLIENT_TITLE_ONE" xml:space="preserve">
<value>Removing client alert</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_REMOVE_ALERTS_ON_CONNECTION_TITLE" xml:space="preserve">
2014-07-29 11:19:54 +02:00
<value>Removing {0} alerts on '{1}'</value>
</data>
<data name="ACTION_REMOVE_ALERTS_ON_CONNECTION_TITLE_ONE" xml:space="preserve">
<value>Removing alert on '{0}'</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_REMOVE_ALERTS_PROGRESS_DESCRIPTION" xml:space="preserve">
<value>Removing alert {0} of {1}...</value>
</data>
2015-02-19 15:09:08 +01:00
<data name="ACTION_RESTART_CONTAINER_DESCRIPTION" xml:space="preserve">
<value>Restarting</value>
</data>
<data name="ACTION_RESTART_CONTAINER_END_DESCRIPTION" xml:space="preserve">
<value>Restarted</value>
</data>
<data name="ACTION_RESTART_CONTAINER_TITLE" xml:space="preserve">
<value>Restarting Docker Container '{0}'</value>
</data>
2013-09-26 16:01:14 +02:00
<data name="ACTION_RESUMEANDSTARTVMS_PREPARING" xml:space="preserve">
<value>Preparing to resume and start VMs...</value>
</data>
<data name="ACTION_RESUMEANDSTARTVMS_RESUMINGN" xml:space="preserve">
<value>Resuming VM {0} of {1}</value>
</data>
<data name="ACTION_RESUMEANDSTARTVMS_STARTINGN" xml:space="preserve">
<value>Starting VM {0} of {1}</value>
</data>
2015-02-09 17:53:29 +01:00
<data name="ACTION_RESUME_CONTAINER_DESCRIPTION" xml:space="preserve">
<value>Resuming</value>
</data>
<data name="ACTION_RESUME_CONTAINER_END_DESCRIPTION" xml:space="preserve">
<value>Resumed</value>
</data>
<data name="ACTION_RESUME_CONTAINER_TITLE" xml:space="preserve">
<value>Resuming Docker Container '{0}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_SAVE_ALERTS" xml:space="preserve">
<value>Save alerts</value>
</data>
<data name="ACTION_SAVE_CHANGES_IN_PROGRESS" xml:space="preserve">
<value>Saving settings...</value>
</data>
<data name="ACTION_SAVE_CHANGES_SUCCESSFUL" xml:space="preserve">
<value>Settings saved</value>
</data>
<data name="ACTION_SAVE_CHANGES_TITLE" xml:space="preserve">
<value>Save settings</value>
</data>
<data name="ACTION_SAVE_CUSTOM_FIELDS" xml:space="preserve">
<value>Save Custom Fields</value>
</data>
2013-09-26 15:45:26 +02:00
<data name="ACTION_SAVE_DATASOURCES" xml:space="preserve">
<value>Save data sources</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_SAVE_FOLDER_TAGS" xml:space="preserve">
<value>Save folder and tags</value>
</data>
2015-07-29 09:44:41 +02:00
<data name="ACTION_SAVE_HEALTHCHECK_SETTINGS" xml:space="preserve">
<value>Save Health Check settings</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_SAVE_SETTINGS" xml:space="preserve">
<value>Save settings for '{0}'...</value>
</data>
<data name="ACTION_SAVING_ALERTS_FOR" xml:space="preserve">
<value>Saving alerts for '{0}'...</value>
</data>
<data name="ACTION_SAVING_CUSTOM_FIELDS_FOR" xml:space="preserve">
<value>Saving Custom Fields for '{0}'...</value>
</data>
2013-09-26 15:45:26 +02:00
<data name="ACTION_SAVING_DATASOURCES" xml:space="preserve">
<value>Saving data sources</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_SAVING_FOLDER_TAGS_FOR" xml:space="preserve">
<value>Saving folder and tags for '{0}'...</value>
</data>
2015-07-29 09:44:41 +02:00
<data name="ACTION_SAVING_HEALTHCHECK_SETTINGS" xml:space="preserve">
<value>Saving Health Check settings for '{0}'...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_SAVING_SETTINGS_FOR" xml:space="preserve">
<value>Saving settings for '{0}'...</value>
</data>
<data name="ACTION_SAVING_TAGS_DESCRIPTION" xml:space="preserve">
<value>Saving tags for the selected items.</value>
</data>
<data name="ACTION_SAVING_TAGS_TITLE" xml:space="preserve">
<value>Saving tags.</value>
</data>
<data name="ACTION_SCANNING_SR_FROM" xml:space="preserve">
<value>Performing SR scan from '{0}'</value>
</data>
2016-08-15 18:43:20 +02:00
<data name="ACTION_SET_VM_OTHER_CONFIG_TITLE" xml:space="preserve">
2016-09-19 18:50:10 +02:00
<value>Saving VM Configuration</value>
2016-08-15 18:43:20 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_SHUTDOWN_AND_DESTROY_VMS_TITLE" xml:space="preserve">
<value>Delete VMs</value>
</data>
<data name="ACTION_SHUTDOWN_AND_DESTROY_VM_TITLE" xml:space="preserve">
<value>Delete VM</value>
</data>
2016-01-12 20:13:10 +01:00
<data name="ACTION_SHUTTING_DOWN" xml:space="preserve">
<value>Shutting down</value>
</data>
<data name="ACTION_SHUT_DOWN" xml:space="preserve">
<value>Shut down</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_SRS_DESTROYING" xml:space="preserve">
<value>Destroying SRs</value>
</data>
<data name="ACTION_SRS_DETACHING" xml:space="preserve">
<value>Detaching SRs</value>
</data>
<data name="ACTION_SRS_DETACH_SUCCESSFUL" xml:space="preserve">
<value>Detached SRs</value>
</data>
<data name="ACTION_SRS_FORGETTING" xml:space="preserve">
<value>Forgetting SRs</value>
</data>
<data name="ACTION_SRS_UPGRADE" xml:space="preserve">
<value>Upgrade SRs</value>
</data>
<data name="ACTION_SRS_UPGRADED" xml:space="preserve">
<value>Upgraded SRS</value>
</data>
<data name="ACTION_SRS_UPGRADING" xml:space="preserve">
<value>Upgrading SRs</value>
</data>
<data name="ACTION_SR_ATTACHING" xml:space="preserve">
<value>Attaching SR</value>
</data>
<data name="ACTION_SR_ATTACHING_TITLE" xml:space="preserve">
<value>Attaching SR '{0}' to '{1}'</value>
</data>
<data name="ACTION_SR_ATTACH_SUCCESSFUL" xml:space="preserve">
<value>Attached SR</value>
</data>
2015-09-08 16:32:47 +02:00
<data name="ACTION_SR_CONVERT" xml:space="preserve">
<value>Convert SR '{0}' on '{1}'</value>
</data>
<data name="ACTION_SR_CONVERTED" xml:space="preserve">
<value>Converted SR</value>
</data>
<data name="ACTION_SR_CONVERTED_TO_THIN" xml:space="preserve">
<value>Converted SR '{0}' to thin provisioning</value>
</data>
<data name="ACTION_SR_CONVERTING" xml:space="preserve">
<value>Converting SR</value>
</data>
<data name="ACTION_SR_CONVERTING_TO_THIN" xml:space="preserve">
<value>Converting SR '{0}' to thin provisioning</value>
</data>
<data name="ACTION_SR_CONVERT_TO_THIN" xml:space="preserve">
<value>Convert SR '{0}' to thin provisioning</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_SR_CREATE_SUCCESSFUL" xml:space="preserve">
<value>Created SR</value>
</data>
<data name="ACTION_SR_CREATING" xml:space="preserve">
<value>Creating SR</value>
</data>
<data name="ACTION_SR_CREATING_TITLE" xml:space="preserve">
<value>Creating {0} SR '{1}' on '{2}'</value>
</data>
<data name="ACTION_SR_DESTROYING" xml:space="preserve">
<value>Destroying SR '{0}' on '{1}'...</value>
</data>
<data name="ACTION_SR_DESTROY_SUCCESSFUL" xml:space="preserve">
<value>SR destroyed</value>
</data>
<data name="ACTION_SR_DETACHING" xml:space="preserve">
<value>Detaching SR '{0}' from '{1}'</value>
</data>
<data name="ACTION_SR_DETACH_SUCCESSFUL" xml:space="preserve">
<value>Detached SR {0}</value>
</data>
<data name="ACTION_SR_FORGETTING" xml:space="preserve">
<value>Forgetting SR '{0}' on '{1}'...</value>
</data>
<data name="ACTION_SR_REPAIRING" xml:space="preserve">
<value>Repairing SR {0}</value>
</data>
<data name="ACTION_SR_REPAIR_CANCELLED" xml:space="preserve">
<value>SR repair canceled</value>
</data>
<data name="ACTION_SR_REPAIR_CREATE_PBD" xml:space="preserve">
<value>Creating PBD for {0}</value>
</data>
<data name="ACTION_SR_REPAIR_FAILED" xml:space="preserve">
<value>Repair failed: the number of PBDs was not equal to the number of servers. Try running the action again.</value>
</data>
<data name="ACTION_SR_REPAIR_PLUGGING_PBD" xml:space="preserve">
<value>Plugging PBD for {0}</value>
</data>
<data name="ACTION_SR_REPAIR_SUCCESSFUL" xml:space="preserve">
<value>Repaired SR {0}</value>
</data>
<data name="ACTION_SR_SCANNING" xml:space="preserve">
<value>Scanning for {0} SRs on {1}</value>
</data>
<data name="ACTION_SR_SCAN_DESCRIPTION" xml:space="preserve">
<value>Scanning {0} filer {1} for existing SRs...</value>
</data>
<data name="ACTION_SR_SCAN_NAME" xml:space="preserve">
<value>Scanning filer {0}</value>
</data>
<data name="ACTION_SR_SCAN_NAME_CSLG" xml:space="preserve">
<value>Scanning {0}</value>
</data>
<data name="ACTION_SR_SCAN_SUCCESSFUL" xml:space="preserve">
<value>Scanned for SRs</value>
</data>
<data name="ACTION_SR_SETTING_DEFAULT" xml:space="preserve">
<value>Setting '{0}' as default SR on '{1}'</value>
</data>
<data name="ACTION_SR_SET_DEFAULT_SUCCESSFUL" xml:space="preserve">
<value>Set default SR</value>
</data>
<data name="ACTION_SR_SHARE_SUCCESSFUL" xml:space="preserve">
<value>Shared SR {0}</value>
</data>
<data name="ACTION_SR_SHARING" xml:space="preserve">
<value>Sharing SR {0}</value>
</data>
2014-06-24 12:32:36 +02:00
<data name="ACTION_SR_TRIM_DESCRIPTION" xml:space="preserve">
<value>Reclaiming freed space</value>
</data>
<data name="ACTION_SR_TRIM_DONE" xml:space="preserve">
<value>Completed</value>
</data>
<data name="ACTION_SR_TRIM_TITLE" xml:space="preserve">
<value>Reclaiming freed space on SR '{0}'</value>
</data>
2015-02-09 17:53:29 +01:00
<data name="ACTION_START_CONTAINER_DESCRIPTION" xml:space="preserve">
<value>Starting</value>
</data>
<data name="ACTION_START_CONTAINER_END_DESCRIPTION" xml:space="preserve">
<value>Started</value>
</data>
<data name="ACTION_START_CONTAINER_TITLE" xml:space="preserve">
<value>Starting Docker Container '{0}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_START_VMS_AND_APPLIANCES_NONE_SELECTED" xml:space="preserve">
<value>There are no VMs or vApps to start</value>
</data>
<data name="ACTION_START_VMS_AND_APPLIANCES_TITLE" xml:space="preserve">
<value>Start VMs and vApps</value>
</data>
2013-12-10 12:29:31 +01:00
<data name="ACTION_STATUS_CANCELLED" xml:space="preserve">
<value>Canceled</value>
</data>
<data name="ACTION_STATUS_FAILED" xml:space="preserve">
<value>Failed</value>
</data>
<data name="ACTION_STATUS_IN_PROGRESS" xml:space="preserve">
<value>In Progress</value>
</data>
<data name="ACTION_STATUS_SUCCEEDED" xml:space="preserve">
<value>Succeeded</value>
</data>
2015-02-09 17:53:29 +01:00
<data name="ACTION_STOP_CONTAINER_DESCRIPTION" xml:space="preserve">
<value>Stopping</value>
</data>
<data name="ACTION_STOP_CONTAINER_END_DESCRIPTION" xml:space="preserve">
<value>Stopped</value>
</data>
<data name="ACTION_STOP_CONTAINER_TITLE" xml:space="preserve">
<value>Stopping Docker Container '{0}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_SYSTEM_STATUS_CANCELLED" xml:space="preserve">
<value>Getting system status canceled</value>
</data>
<data name="ACTION_SYSTEM_STATUS_COMPILING" xml:space="preserve">
<value>Compiling status report for {0}</value>
</data>
<data name="ACTION_SYSTEM_STATUS_DESCRIPTION" xml:space="preserve">
<value>Getting system status from {0}</value>
</data>
<data name="ACTION_SYSTEM_STATUS_DISK_FULL" xml:space="preserve">
<value>Getting system status failed: disk full</value>
</data>
<data name="ACTION_SYSTEM_STATUS_FAILED" xml:space="preserve">
<value>Failed to compile status report </value>
</data>
<data name="ACTION_SYSTEM_STATUS_NONE_SUCCEEDED" xml:space="preserve">
<value>No data was compiled</value>
</data>
<data name="ACTION_SYSTEM_STATUS_NONE_SUCCEEDED_GUI" xml:space="preserve">
<value>No data was compiled. Press previous to select new items or servers and try again.</value>
</data>
<data name="ACTION_SYSTEM_STATUS_SUCCESSFUL" xml:space="preserve">
<value>Finished compiling status report</value>
</data>
<data name="ACTION_SYSTEM_STATUS_SUCCESSFUL_WITH_ERROR" xml:space="preserve">
<value>Finished compiling status report (with errors). A partial status report was compiled.</value>
</data>
<data name="ACTION_SYSTEM_STATUS_SUCCESSFUL_WITH_ERRORS_XCLOGS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Finished compiling status report (with errors). Only [XenCenter] logs were compiled.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_SYSTEM_STATUS_TITLE" xml:space="preserve">
<value>Getting system status information</value>
</data>
<data name="ACTION_TEMPLATE_CLONED" xml:space="preserve">
<value>Duplicated</value>
</data>
<data name="ACTION_TEMPLATE_CLONE_NEW_NAME" xml:space="preserve">
<value>Copy of {0}</value>
</data>
<data name="ACTION_TEMPLATE_CLONING" xml:space="preserve">
<value>Duplicating</value>
</data>
<data name="ACTION_TOOLSTACK_RESTARTED" xml:space="preserve">
<value>Toolstack restarted.</value>
</data>
<data name="ACTION_TOOLSTACK_RESTARTED_ON" xml:space="preserve">
<value>Toolstack restarted on '{0}'.</value>
</data>
<data name="ACTION_TOOLSTACK_RESTARTING" xml:space="preserve">
<value>Restarting toolstack...</value>
</data>
<data name="ACTION_TOOLSTACK_RESTARTING_ON" xml:space="preserve">
<value>Restarting toolstack on '{0}'...</value>
</data>
<data name="ACTION_TOOLSTACK_RESTART_ON" xml:space="preserve">
<value>Restart toolstack on '{0}'</value>
</data>
2015-07-29 09:44:41 +02:00
<data name="ACTION_TRANSFER_HEALTHCHECK_SETTINGS" xml:space="preserve">
2015-07-08 18:35:50 +02:00
<value>Transfer Health Check settings</value>
2015-07-01 04:35:59 +02:00
</data>
2015-02-25 14:01:03 +01:00
<data name="ACTION_UPDATE_INTEGRATED_GPU_PASSTHROUGH_TITLE" xml:space="preserve">
<value>Updating integrated GPU passthrough on '{0}'</value>
</data>
2016-06-27 20:39:49 +02:00
<data name="ACTION_UPLOADPATCHTOMASTERPLANACTION_FAILED" xml:space="preserve">
<value>Upload error. The patch was uploaded, but it cannot be found on the host.</value>
</data>
2015-07-15 16:39:37 +02:00
<data name="ACTION_UPLOAD_SERVER_STATUS_REPORT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upload server status report to [Citrix] Insight Services</value>
2015-07-15 16:39:37 +02:00
</data>
<data name="ACTION_UPLOAD_SERVER_STATUS_REPORT_FAILED" xml:space="preserve">
<value>Failed to upload the status report.</value>
</data>
<data name="ACTION_UPLOAD_SERVER_STATUS_REPORT_PROGRESS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Uploading report to [Citrix] Insight Services</value>
2015-07-15 16:39:37 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_VDI_CREATED" xml:space="preserve">
<value>Virtual disk created</value>
</data>
<data name="ACTION_VDI_CREATING" xml:space="preserve">
<value>Creating virtual disk...</value>
</data>
<data name="ACTION_VDI_CREATING_TITLE" xml:space="preserve">
<value>Creating disk '{0}' on SR '{1}'</value>
</data>
<data name="ACTION_VDI_DELETED" xml:space="preserve">
<value>Virtual disk deleted</value>
</data>
<data name="ACTION_VDI_DELETING" xml:space="preserve">
<value>Deleting virtual disk...</value>
</data>
<data name="ACTION_VDI_LOAD_METADATA_DONE" xml:space="preserve">
<value>Metadata loaded</value>
</data>
<data name="ACTION_VDI_LOAD_METADATA_STATUS" xml:space="preserve">
<value>Loading metadata from SR '{0}'</value>
</data>
<data name="ACTION_VDI_LOAD_METADATA_TITLE" xml:space="preserve">
<value>Load metadata from SR '{0}'</value>
</data>
<data name="ACTION_VDI_OPEN_DATABASE_DONE" xml:space="preserve">
<value>Metadata database opened</value>
</data>
<data name="ACTION_VDI_OPEN_DATABASE_STATUS" xml:space="preserve">
<value>Opening metadata database from SR '{0}'</value>
</data>
<data name="ACTION_VDI_OPEN_DATABASE_TITLE" xml:space="preserve">
<value>Open metadata database from SR '{0}'</value>
</data>
2013-11-14 12:11:24 +01:00
<data name="ACTION_VGPU_CONFIGURATION_SAVED" xml:space="preserve">
2015-03-30 17:21:46 +02:00
<value>Virtual GPU configuration saved</value>
2013-11-14 12:11:24 +01:00
</data>
<data name="ACTION_VGPU_CONFIGURATION_SAVING" xml:space="preserve">
2015-03-30 17:21:46 +02:00
<value>Saving virtual GPU configuration</value>
2013-11-14 12:11:24 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_VIF_CREATED" xml:space="preserve">
<value>Virtual network interface created</value>
</data>
<data name="ACTION_VIF_CREATING" xml:space="preserve">
<value>Creating virtual network interface</value>
</data>
<data name="ACTION_VIF_CREATING_TITLE" xml:space="preserve">
<value>Creating new virtual network interface on VM {0}</value>
</data>
<data name="ACTION_VIF_DELETED" xml:space="preserve">
<value>Virtual network interface deleted</value>
</data>
<data name="ACTION_VIF_DELETING" xml:space="preserve">
<value>Deleting virtual network interface</value>
</data>
<data name="ACTION_VIF_DELETING_TITLE" xml:space="preserve">
<value>Deleting virtual network interface '{0}' from VM '{1}'</value>
</data>
<data name="ACTION_VIF_PLUGGED" xml:space="preserve">
<value>Activated virtual network interface</value>
</data>
<data name="ACTION_VIF_PLUGGING" xml:space="preserve">
<value>Activating virtual network interface...</value>
</data>
<data name="ACTION_VIF_PLUG_TITLE" xml:space="preserve">
<value>Activating virtual network interface on VM '{0}'</value>
</data>
<data name="ACTION_VIF_UNPLUGGED" xml:space="preserve">
<value>Deactivated virtual network interface</value>
</data>
<data name="ACTION_VIF_UNPLUGGING" xml:space="preserve">
<value>Deactiviting virtual network interface...</value>
</data>
<data name="ACTION_VIF_UNPLUG_TITLE" xml:space="preserve">
<value>Deactivating virtual network interface on VM '{0}'</value>
</data>
<data name="ACTION_VIF_UPDATED" xml:space="preserve">
<value>Virtual network interface updated</value>
</data>
<data name="ACTION_VIF_UPDATING" xml:space="preserve">
<value>Updating virtual network interface</value>
</data>
<data name="ACTION_VIF_UPDATING_TITLE" xml:space="preserve">
<value>Updating virtual network interface '{0}' on VM '{1}'</value>
</data>
<data name="ACTION_VMS_DESTROYING_TITLE" xml:space="preserve">
<value>Deleting selected VMs</value>
</data>
<data name="ACTION_VMS_MIGRATING_TITLE" xml:space="preserve">
<value>Migrating VMs</value>
</data>
<data name="ACTION_VMS_RESUMING_ON_TITLE" xml:space="preserve">
<value>Resuming VMs</value>
</data>
2016-03-30 12:37:09 +02:00
<data name="ACTION_VMS_SHUTTING_DOWN_TITLE" xml:space="preserve">
<value>Shutting Down VMs</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_VMS_STARTING_ON_TITLE" xml:space="preserve">
<value>Starting VMs</value>
</data>
<data name="ACTION_VM_COPIED" xml:space="preserve">
<value>Copied</value>
</data>
<data name="ACTION_VM_COPYING" xml:space="preserve">
<value>Copying</value>
</data>
<data name="ACTION_VM_COPYING_TITLE" xml:space="preserve">
<value>Copying VM '{0}' to '{1}' on SR '{2}'</value>
</data>
<data name="ACTION_VM_COPYING_TITLE_MEDDLING" xml:space="preserve">
<value>Copying VM '{0}'</value>
</data>
2015-03-31 15:27:04 +02:00
<data name="ACTION_VM_CROSS_POOL_COPY_CANCELLED" xml:space="preserve">
<value>Copying {0} canceled</value>
</data>
<data name="ACTION_VM_CROSS_POOL_COPY_TITLE" xml:space="preserve">
<value>Copying VM '{0}' to '{1}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ACTION_VM_DELETE_SNAPSHOTS_TITLE" xml:space="preserve">
<value>Deleting snapshots</value>
</data>
<data name="ACTION_VM_DELETE_SNAPSHOT_TITLE" xml:space="preserve">
<value>Deleting snapshot '{0}'...</value>
</data>
<data name="ACTION_VM_DESTROYED" xml:space="preserve">
<value>Deleted</value>
</data>
<data name="ACTION_VM_DESTROYING" xml:space="preserve">
<value>Deleting</value>
</data>
<data name="ACTION_VM_DESTROYING_TITLE" xml:space="preserve">
<value>Deleting VM '{0}' from '{1}'</value>
</data>
<data name="ACTION_VM_MIGRATED" xml:space="preserve">
<value>Migrated</value>
</data>
<data name="ACTION_VM_MIGRATE_CANCELLED" xml:space="preserve">
2013-12-13 14:51:16 +01:00
<value>Migrating {0} canceled</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_VM_MIGRATING" xml:space="preserve">
<value>Migrating</value>
</data>
2016-09-30 13:39:26 +02:00
<data name="ACTION_VM_MIGRATING_NON_RESIDENT" xml:space="preserve">
<value>Migrating VM '{0}' to '{1}'</value>
</data>
<data name="ACTION_VM_MIGRATING_RESIDENT" xml:space="preserve">
2013-06-24 13:41:48 +02:00
<value>Migrating VM '{0}' from '{1}' to '{2}'</value>
</data>
<data name="ACTION_VM_MOVING" xml:space="preserve">
<value>Moving VM to new storage...</value>
</data>
<data name="ACTION_VM_MOVING_TITLE" xml:space="preserve">
<value>Moving VM '{0}' to '{1}' on SR '{2}'</value>
</data>
<data name="ACTION_VM_REBOOTED" xml:space="preserve">
<value>Rebooted</value>
</data>
<data name="ACTION_VM_REBOOTING" xml:space="preserve">
2016-01-12 20:13:10 +01:00
<value>Rebooting VM</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_VM_REBOOTING_TITLE" xml:space="preserve">
<value>Rebooting VM '{0}' on '{1}'</value>
</data>
<data name="ACTION_VM_RESUMED" xml:space="preserve">
<value>Resumed</value>
</data>
<data name="ACTION_VM_RESUMING" xml:space="preserve">
2016-01-12 20:13:10 +01:00
<value>Resuming VM</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_VM_RESUMING_ON_TITLE" xml:space="preserve">
<value>Resuming VM '{0}' on '{1}'</value>
</data>
<data name="ACTION_VM_RESUMING_TITLE" xml:space="preserve">
<value>Resuming VM '{0}'</value>
</data>
<data name="ACTION_VM_REVERT_SNAPSHOT_DONE" xml:space="preserve">
<value>Snapshot reverted</value>
</data>
<data name="ACTION_VM_REVERT_SNAPSHOT_STATUS" xml:space="preserve">
<value>Reverting snapshot '{0}'...</value>
</data>
<data name="ACTION_VM_REVERT_SNAPSHOT_TITLE" xml:space="preserve">
<value>Revert snapshot '{0}'</value>
</data>
<data name="ACTION_VM_SHUTTING_DOWN" xml:space="preserve">
2016-01-12 20:13:10 +01:00
<value>Shutting down VM</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_VM_SHUTTING_DOWN_TITLE" xml:space="preserve">
<value>Shutting down VM '{0}' on '{1}'</value>
</data>
<data name="ACTION_VM_SHUT_DOWN" xml:space="preserve">
<value>Shut down</value>
</data>
<data name="ACTION_VM_SNAPSHOT_TITLE" xml:space="preserve">
<value>Snapshotting VM '{0}'...</value>
</data>
<data name="ACTION_VM_STARTED" xml:space="preserve">
<value>Started</value>
</data>
<data name="ACTION_VM_STARTED_PAUSED" xml:space="preserve">
<value>Started paused</value>
</data>
<data name="ACTION_VM_STARTING" xml:space="preserve">
2016-01-12 20:13:10 +01:00
<value>Starting VM</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_VM_STARTING_ON_TITLE" xml:space="preserve">
<value>Starting VM '{0}' on '{1}'</value>
</data>
<data name="ACTION_VM_STARTING_PAUSED" xml:space="preserve">
<value>Starting paused</value>
</data>
<data name="ACTION_VM_STARTING_PAUSED_ON_TITLE" xml:space="preserve">
<value>Starting VM '{0}' paused on '{1}'</value>
</data>
<data name="ACTION_VM_STARTING_PAUSED_TITLE" xml:space="preserve">
<value>Starting VM '{0}' paused</value>
</data>
<data name="ACTION_VM_STARTING_TITLE" xml:space="preserve">
<value>Starting VM '{0}'</value>
</data>
<data name="ACTION_VM_SUSPENDED" xml:space="preserve">
<value>Suspended</value>
</data>
<data name="ACTION_VM_SUSPENDING" xml:space="preserve">
2016-01-12 20:13:10 +01:00
<value>Suspending VM</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_VM_SUSPENDING_TITLE" xml:space="preserve">
<value>Suspending VM '{0}'</value>
</data>
<data name="ACTION_VM_TEMPLATIZED" xml:space="preserve">
<value>Conversion to template complete</value>
</data>
<data name="ACTION_VM_TEMPLATIZING" xml:space="preserve">
<value>Converting to template</value>
</data>
<data name="ACTION_VM_TEMPLATIZING_TITLE" xml:space="preserve">
<value>Converting VM '{0}' to template</value>
</data>
<data name="ACTION_WLB_DECONFIGURE_FAILED" xml:space="preserve">
<value>Disconnecting Workload Balancing failed on pool {0}: {1} Workload Balancing has been paused.</value>
</data>
<data name="ACTION_WLB_POOL_OPTIMIZING" xml:space="preserve">
<value>Optimizing</value>
</data>
<data name="ACTION_WLB_REPORT" xml:space="preserve">
<value>Downloading WLB report '{0}' from '{1}' ({2})</value>
</data>
<data name="ACTION_WLB_REPORT_CANCELLED" xml:space="preserve">
2013-12-13 14:51:16 +01:00
<value>Download canceled</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ACTION_WLB_REPORT_DOWNLOADING" xml:space="preserve">
<value>Downloading...</value>
</data>
<data name="ACTION_WLB_REPORT_FAILED" xml:space="preserve">
<value>Download failed</value>
</data>
<data name="ACTION_WLB_REPORT_SUCCESSFUL" xml:space="preserve">
<value>Downloaded</value>
</data>
<data name="ACTION_WLB_REPORT_TASK_DESCRIPTION" xml:space="preserve">
<value>Downloading WLB report {0}</value>
</data>
<data name="ACTION_WLB_REPORT_TASK_NAME" xml:space="preserve">
<value>Downloading WLB report {0}</value>
</data>
<data name="ACTIVATE" xml:space="preserve">
<value>A&ctivate</value>
</data>
<data name="ACTIVATION_FAILED_MESSAGE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] is unable to contact the activation server.
2013-06-24 13:41:48 +02:00
If you are not currently connected to the internet, we can save
the activation request to a file, for you to upload at a later date.
To use this file, visit https://{0}.</value>
</data>
<data name="ACTIVATION_REQUEST_SAVED" xml:space="preserve">
<value>Saved activation request to {0}.</value>
</data>
<data name="ACTIVATION_REQUEST_TITLE" xml:space="preserve">
<value>Sending activation request</value>
</data>
<data name="ACTIVATION_SAVE" xml:space="preserve">
<value>Save...</value>
</data>
<data name="ACTIVE_DIRECTORY_TAB_TITLE" xml:space="preserve">
<value>Active Directory Users</value>
</data>
<data name="ADD" xml:space="preserve">
<value>&Add</value>
</data>
<data name="ADDED_CUSTOM_FIELD" xml:space="preserve">
<value>Added custom field '{0}'</value>
</data>
<data name="ADDED_TAG" xml:space="preserve">
<value>Added tag '{0}' </value>
</data>
<data name="ADDED_TAGS" xml:space="preserve">
<value>Added tags '{0}' </value>
</data>
<data name="ADDED_TO_ACCESS_LIST" xml:space="preserve">
<value>Added to access list</value>
</data>
<data name="ADDING_CUSTOM_FIELD" xml:space="preserve">
<value>Adding custom field '{0}'</value>
</data>
<data name="ADDING_EULAS" xml:space="preserve">
<value>Adding EULAS...</value>
</data>
<data name="ADDING_RESOLVED_TO_ACCESS_LIST" xml:space="preserve">
<value>Adding resolved names to access list...</value>
</data>
<data name="ADDING_SERVERS_TO_POOL" xml:space="preserve">
<value>Adding selected servers to pool '{0}'</value>
</data>
<data name="ADDING_SERVER_TO_POOL" xml:space="preserve">
<value>Adding server '{0}' to pool '{1}'</value>
</data>
<data name="ADDING_TAG" xml:space="preserve">
<value>Adding tag '{0}'</value>
</data>
<data name="ADDING_TAGS" xml:space="preserve">
<value>Adding tags '{0}'</value>
</data>
<data name="ADDING_TO_ACCESS_LIST" xml:space="preserve">
<value>Adding to access list...</value>
</data>
<data name="ADDRESS" xml:space="preserve">
<value>Address</value>
</data>
<data name="ADDSERVER_PASS_NEW" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] can no longer authenticate with the existing credentials for this server. Enter new credentials to proceed.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ADD_CUSTOM_FIELD" xml:space="preserve">
<value>Add custom field '{0}'</value>
</data>
<data name="ADD_HOST_TO_POOL_AD_MESSAGE" xml:space="preserve">
<value>You are attempting to add the server '{0}' to a pool that is configured to use AD authentication. All pool members must use the same authentication method.
Do you want to enable AD authentication on your server and join it to the same domain as the pool?</value>
</data>
<data name="ADD_HOST_TO_POOL_AD_MESSAGE_MULTIPLE" xml:space="preserve">
<value>You are attempting to add the following servers to a pool that is configured to use AD authentication:
{0}
All pool members must use the same authentication method. Do you want to enable AD authentication on these servers and join them to the same domain as the pool?</value>
2015-10-30 16:52:24 +01:00
</data>
<data name="ADD_HOST_TO_POOL_CPU_DOWN_LEVEL_HOST_MESSAGE" xml:space="preserve">
<value>You are attempting to add the server '{0}' to a pool that is using older CPUs.
VMs running in the pool will only use the CPU features common to all the servers in the pool.
Do you want to do this?</value>
</data>
<data name="ADD_HOST_TO_POOL_CPU_DOWN_LEVEL_HOST_MESSAGE_MULTIPLE" xml:space="preserve">
<value>You are attempting to add the following servers to a pool that is using older CPUs.
{0}
VMs running in the pool will only use the CPU features common to all the servers in the pool.
Do you want to do this?</value>
</data>
<data name="ADD_HOST_TO_POOL_CPU_DOWN_LEVEL_POOL_AND_HOST_MESSAGE" xml:space="preserve">
<value>You are attempting to add the server '{0}' to a pool that is using different CPUs.
VMs starting on the pool in future will only use the reduced set of CPU features common to all the servers in the pool. VMs already running in the pool will not be able to migrate to the new server until they are restarted.
Do you want to do this?</value>
</data>
<data name="ADD_HOST_TO_POOL_CPU_DOWN_LEVEL_POOL_AND_HOST_MESSAGE_MULTIPLE" xml:space="preserve">
<value>You are attempting to add the following servers to a pool that is using different CPUs.
{0}
VMs starting on the pool in future will only use the reduced set of CPU features common to all the servers in the pool. VMs already running in the pool will not be able to migrate to the new servers until they are restarted.
Do you want to do this?</value>
</data>
<data name="ADD_HOST_TO_POOL_CPU_DOWN_LEVEL_POOL_MESSAGE" xml:space="preserve">
<value>You are attempting to add the server '{0}' to a pool that is using newer CPUs.
VMs starting on the pool in future will only use the reduced set of CPU features common to all the servers in the pool. VMs already running in the pool will not be able to migrate to the new server until they are restarted.
Do you want to do this?</value>
</data>
<data name="ADD_HOST_TO_POOL_CPU_DOWN_LEVEL_POOL_MESSAGE_MULTIPLE" xml:space="preserve">
<value>You are attempting to add the following servers to a pool that is using newer CPUs.
{0}
VMs starting on the pool in future will only use the reduced set of CPU features common to all the servers in the pool. VMs already running in the pool will not be able to migrate to the new servers until they are restarted.
Do you want to do this?</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ADD_HOST_TO_POOL_CPU_MASKING_MESSAGE" xml:space="preserve">
<value>You are attempting to add the server '{0}' to a pool that is using older CPUs.
2016-02-10 12:52:30 +01:00
[XenServer] can continue by rebooting the server and reducing its CPU to the level of the existing servers in the pool. This will shut down any VMs running on the server. This feature is supported for CPU combinations listed in the [XenServer] Hardware Compatibility List.
2013-06-24 13:41:48 +02:00
Do you want to do this?</value>
</data>
<data name="ADD_HOST_TO_POOL_CPU_MASKING_MESSAGE_MULTIPLE" xml:space="preserve">
<value>You are attempting to add the following servers to a pool that is using older CPUs:
{0}
2016-02-10 12:52:30 +01:00
[XenServer] can continue by rebooting the servers and reducing their CPUs to the level of the existing servers in the pool. This will shut down any VMs running on the servers. This feature is supported for CPU combinations listed in the [XenServer] Hardware Compatibility List.
2013-06-24 13:41:48 +02:00
Do you want to do this?</value>
</data>
<data name="ADD_HOST_TO_POOL_DISCONNECTED_POOL" xml:space="preserve">
<value>Unable to move the server '{0}' into the pool '{1}': the pool is no longer connected.</value>
</data>
<data name="ADD_HOST_TO_POOL_DISCONNECTED_POOL_MULTIPLE" xml:space="preserve">
<value>Unable to move selected servers into the pool '{0}': the pool is no longer connected.</value>
</data>
<data name="ADD_HOST_TO_POOL_LICENSE_MESSAGE" xml:space="preserve">
2015-01-23 11:20:07 +01:00
<value>You are attempting to add the server '{0}' to a licensed pool.
2013-06-24 13:41:48 +02:00
Do you want to apply the licensing from the pool to this server?</value>
</data>
<data name="ADD_HOST_TO_POOL_LICENSE_MESSAGE_MULTIPLE" xml:space="preserve">
2015-01-23 11:20:07 +01:00
<value>You are attempting to add the following servers to a licensed pool.
2013-06-24 13:41:48 +02:00
{0}
Do you want to apply the licensing from the pool to these servers?</value>
</data>
<data name="ADD_HOST_TO_POOL_SUPP_PACK" xml:space="preserve">
<value>The following supplemental pack should be installed on all servers in a pool, but currently is not:
{0}
It is strongly recommended that you Cancel and apply the latest version of the pack to all servers before expanding the pool.</value>
</data>
<data name="ADD_HOST_TO_POOL_SUPP_PACKS" xml:space="preserve">
<value>The following supplemental packs should be installed on all servers in a pool, but currently are not:
{0}
It is strongly recommended that you Cancel and apply the latest version of the packs to all servers before expanding the pool.</value>
</data>
<data name="ADD_NEW_CONNECT_TO" xml:space="preserve">
<value>Add New Server</value>
</data>
<data name="ADD_NEW_ENTER_CREDENTIALS" xml:space="preserve">
<value>Enter the host name or IP address of the server you want to add and your user login credentials for that server.</value>
</data>
<data name="ADD_NEW_INCORRECT" xml:space="preserve">
2016-12-16 19:36:35 +01:00
<value>Incorrect user name and/or password.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ADD_NEW_SERVER_MENU_ITEM" xml:space="preserve">
<value>&Add New Server...</value>
</data>
<data name="ADD_POOL_OR_SERVER" xml:space="preserve">
<value>Add a pool or standalone server...</value>
</data>
<data name="ADD_SL_VOLUME" xml:space="preserve">
<value>Import &StorageLink Volume...</value>
</data>
<data name="ADD_TAG" xml:space="preserve">
<value>Add tag '{0}'</value>
</data>
<data name="ADD_TAGS" xml:space="preserve">
<value>Add tags '{0}'</value>
</data>
<data name="ADD_VIRTUAL_DISK" xml:space="preserve">
<value>New &Virtual Disk...</value>
</data>
<data name="ADVANCED_OPTIONS" xml:space="preserve">
<value>Advanced Options</value>
</data>
<data name="AD_ADDING_REMOVING" xml:space="preserve">
<value>Adding/removing users from Active Directory ACL</value>
</data>
<data name="AD_ADDING_REMOVING_ON" xml:space="preserve">
<value>Adding/removing users from Active Directory ACL on '{0}'</value>
</data>
<data name="AD_ADDING_REMOVING_ROLES" xml:space="preserve">
<value>Adding/removing roles from subject</value>
</data>
<data name="AD_ADDING_REMOVING_ROLES_ON" xml:space="preserve">
<value>Adding/removing roles from subject '{0}'</value>
</data>
<data name="AD_ALWAYS_GRANTED_ACCESS" xml:space="preserve">
<value>(Always granted access)</value>
</data>
<data name="AD_CANNOT_CHANGE_PASSWORD" xml:space="preserve">
<value>You are logged in using your AD user account. You can only change the password when logged in using the local root account.</value>
</data>
<data name="AD_CANNOT_MODIFY_ROOT" xml:space="preserve">
<value>Cannot modify the root account</value>
</data>
<data name="AD_CHANGE_DOMAIN_BLURB" xml:space="preserve">
<value>'{0}' is joined to the Active Directory domain '{1}', while the pool '{2}' is joined to the Active Directory domain '{3}'.
'{0}' can only join the pool if they both have the same AD configuration.
To join '{0}' to the pool '{2}', first disable AD on '{0}'.</value>
</data>
<data name="AD_CONFIGURED_BLURB" xml:space="preserve">
<value>Pool '{0}' belongs to domain '{1}'.</value>
</data>
<data name="AD_CONFIGURED_BLURB_HOST" xml:space="preserve">
<value>Server '{0}' belongs to domain '{1}'.</value>
</data>
<data name="AD_CONFIGURING_BLURB" xml:space="preserve">
2013-10-08 15:51:39 +02:00
<value>AD authentication is currently being configured for pool '{0}'.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="AD_CONFIGURING_BLURB_HOST" xml:space="preserve">
2013-10-08 15:51:39 +02:00
<value>AD authentication is currently being configured for server '{0}'.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="AD_CONFIRM_SELF_TERMINATE" xml:space="preserve">
<value>Are you sure you want to terminate this user session?
This will disconnect you from '{0}'.</value>
</data>
<data name="AD_CONFIRM_SELF_TERMINATE_OK" xml:space="preserve">
<value>Terminate Session</value>
</data>
<data name="AD_CONFIRM_SUICIDE" xml:space="preserve">
<value>You are about to revoke the permissions for user '{0}'.
You are currently logged in as '{0}' on '{1}', and doing this will disconnect you from '{1}'. To reconnect, you will need to supply the local root account credentials, or the credentials for another authorized AD user.
Do you wish to continue?</value>
</data>
<data name="AD_CONFIRM_SUICIDE_GROUP" xml:space="preserve">
<value>You are about to revoke the permissions for group '{0}'.
The user you are currently logged into '{1}' with is a member of '{0}'. Proceeding will disconnect you and any other members of this group from '{1}'. To reconnect, you will need to supply the local root account credentials, or the credentials for another authorized AD user.
Do you wish to continue?</value>
</data>
<data name="AD_COULD_NOT_RESOLVE_SUFFIX" xml:space="preserve">
<value>Subject could not be resolved in your AD</value>
</data>
<data name="AD_DISABLING" xml:space="preserve">
<value>Disabling AD authentication</value>
</data>
<data name="AD_FAILURE_WITH_HOST" xml:space="preserve">
<value>{0}
Host: {1}</value>
</data>
<data name="AD_FEATURE_NAME" xml:space="preserve">
<value>AD Authentication</value>
</data>
<data name="AD_JOIN_DOMAIN" xml:space="preserve">
<value>&Join Domain</value>
</data>
<data name="AD_JOIN_DOMAIN_BLURB" xml:space="preserve">
<value>Pool '{0}' has Active Directory authentication enabled. In order for '{1}' to join the pool, it must share the same AD configuration.
To join '{1}' to the Active Directory domain '{2}', enter a domain user account name and password, then click OK.
You must use a user account with sufficient privileges.</value>
</data>
<data name="AD_JOIN_DOMAIN_BLURB_SHORT" xml:space="preserve">
2016-12-16 19:36:35 +01:00
<value>Enter your fully qualified AD domain name, and a user name and password with sufficient privileges to add servers to your domain.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="AD_JOIN_DOMAIN_BLURB_SHORT_HOST" xml:space="preserve">
2016-12-16 19:36:35 +01:00
<value>Enter your fully qualified AD domain name, and a user name and password with sufficient privileges to add servers to your domain.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="AD_LEAVE_CONFIRM" xml:space="preserve">
2016-03-16 14:17:47 +01:00
<value>You are about to remove '{0}' from the AD domain '{1}'. Any users authenticated using AD will be disconnected.
2013-06-24 13:41:48 +02:00
Do you want to continue?</value>
</data>
<data name="AD_LEAVE_DOMAIN" xml:space="preserve">
<value>L&eave Domain</value>
</data>
<data name="AD_LEAVE_WARNING" xml:space="preserve">
<value>You are currently connected to pool '{0}' using Active Directory authentication.
If you leave the AD domain '{1}', you will be disconnected from the pool.
To reconnect, you will need to supply the local root account credentials.
Do you want to continue?</value>
</data>
<data name="AD_LEAVE_WARNING_HOST" xml:space="preserve">
<value>You are currently connected to server '{0}' using Active Directory authentication.
If you leave the AD domain '{1}', you will be disconnected from the server.
To reconnect, you will need to supply the local root account credentials.
Do you want to continue?</value>
</data>
<data name="AD_LEAVING_ADDITIONAL_BLURB" xml:space="preserve">
<value>Alternatively, select ignore to leave the machine account enabled.</value>
</data>
<data name="AD_LOCAL_ROOT_ACCOUNT" xml:space="preserve">
<value>Local root account</value>
</data>
<data name="AD_LOGOUT_SUICIDE_MANY" xml:space="preserve">
<value>You are currently logged in as one of the selected users. If you continue you will be logged out of '{0}'.
Do you wish to continue?</value>
</data>
<data name="AD_LOGOUT_SUICIDE_ONE" xml:space="preserve">
<value>You are currently logged in as the selected user. If you continue you will be logged out of '{0}'.
Do you wish to continue?</value>
</data>
<data name="AD_MASTER_UNAVAILABLE_BLURB" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Please wait while [XenCenter] establishes your current external authentication configuration.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="AD_NOT_CONFIGURED_BLURB" xml:space="preserve">
<value>AD is not currently configured for pool '{0}'. To enable AD authentication, click Join Domain.</value>
</data>
<data name="AD_NOT_CONFIGURED_BLURB_HOST" xml:space="preserve">
<value>AD is not currently configured for server '{0}'. To enable AD authentication, click Join Domain.</value>
</data>
<data name="AD_RESOLVING_NAMES" xml:space="preserve">
<value>Resolving AD names</value>
</data>
<data name="AD_RESOLVING_NAMES_ON" xml:space="preserve">
<value>Resolving AD names on '{0}'</value>
</data>
<data name="AD_RESOLVING_SUFFIX" xml:space="preserve">
<value>Resolving...</value>
</data>
<data name="AD_ROLE_POOL_ADMIN" xml:space="preserve">
<value>Pool Admin</value>
</data>
<data name="AD_ROLE_POOL_OPERATOR" xml:space="preserve">
<value>Pool Operator</value>
</data>
<data name="AD_ROLE_READ_ONLY" xml:space="preserve">
<value>Read Only</value>
</data>
<data name="AD_ROLE_VM_ADMIN" xml:space="preserve">
<value>VM Admin</value>
</data>
<data name="AD_ROLE_VM_OPERATOR" xml:space="preserve">
<value>VM Operator</value>
</data>
<data name="AD_ROLE_VM_POWER_ADMIN" xml:space="preserve">
<value>VM Power Admin</value>
</data>
<data name="AD_SELECT_ROLE_GROUP" xml:space="preserve">
<value>Select the role you wish to assign to group '{0}'. Each role inherits all the privileges of the subordinate role below it in the list.</value>
</data>
<data name="AD_SELECT_ROLE_MIXED" xml:space="preserve">
<value>Select the role you wish to assign to these users and groups. Each role inherits all the privileges of the subordinate role below it in the list.</value>
</data>
<data name="AD_SELECT_ROLE_USER" xml:space="preserve">
<value>Select the role you wish to assign to user '{0}'. Each role inherits all the privileges of the subordinate role below it in the list.</value>
</data>
<data name="AD_SELECT_SINGLE_SUBJECT" xml:space="preserve">
<value>Select a single subject to change their role</value>
</data>
<data name="AD_USER_ALREADY_HAS_ACCESS" xml:space="preserve">
<value>Subject '{0}' already has access to the server.</value>
</data>
2013-09-27 14:33:57 +02:00
<data name="AFFINITY_PICKER_DYNAMIC_NOT_SHARED_SR" xml:space="preserve">
<value>&Don't assign this VM a home server. The VM will be started on any server with the necessary resources. (Shared storage required).</value>
</data>
<data name="AFFINITY_PICKER_DYNAMIC_SHARED_SR" xml:space="preserve">
<value>&Don't assign this VM a home server. The VM will be started on any server with the necessary resources.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="AFTER" xml:space="preserve">
<value>is after</value>
</data>
<data name="AGGREGATE" xml:space="preserve">
<value>Aggregate</value>
</data>
<data name="AGILE" xml:space="preserve">
<value>Agile</value>
</data>
<data name="ALERTS" xml:space="preserve">
<value>Alerts</value>
</data>
<data name="ALERTS_FOUND" xml:space="preserve">
<value>Alerts found: {0}</value>
</data>
<data name="ALERTS_TOTAL" xml:space="preserve">
<value>Total alerts: {0}</value>
</data>
2013-07-18 14:56:40 +02:00
<data name="ALERT_ACTIONS" xml:space="preserve">
<value>Actions</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ALERT_ALARM_ACTION" xml:space="preserve">
<value>Alarm Settings</value>
</data>
<data name="ALERT_ALARM_CPU" xml:space="preserve">
<value>CPU Usage Alarm</value>
</data>
<data name="ALERT_ALARM_CPU_DESCRIPTION" xml:space="preserve">
<value>CPU usage on {0} has been on average {1} for the last {2}.
This alarm is set to be triggered when CPU usage is more than {3}.</value>
</data>
<data name="ALERT_ALARM_DISK" xml:space="preserve">
<value>Disk Usage Alarm</value>
</data>
<data name="ALERT_ALARM_DISK_DESCRIPTION" xml:space="preserve">
<value>Disk usage on {0} has been on average {1} for the last {2}.
This alarm is set to be triggered when disk usage is more than {3}.</value>
2014-08-05 22:40:26 +02:00
</data>
<data name="ALERT_ALARM_DOM0_MEMORY" xml:space="preserve">
<value>Control Domain Memory Usage</value>
</data>
<data name="ALERT_ALARM_DOM0_MEMORY_DEMAND" xml:space="preserve">
<value>Control Domain Memory Demand Alarm</value>
</data>
<data name="ALERT_ALARM_DOM0_MEMORY_DEMAND_DESCRIPTION" xml:space="preserve">
2015-12-08 19:06:30 +01:00
<value>The memory required by the control domain on {0} is {1} of its allocated memory. Occasional performance degradation can be expected when memory swapping is forced to happen.
This alarm is set to be triggered when the memory required by the control domain is above {2} of its allocated memory.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ALERT_ALARM_FILESYSTEM" xml:space="preserve">
<value>File System on Control Domain Full</value>
</data>
<data name="ALERT_ALARM_FILESYSTEM_DESCRIPTION" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Disk usage for the Control Domain on {0} has reached {1}. [XenServer]'s performance will be critically affected if this disk becomes full. Log files or other non-essential (user created) files should be removed.</value>
2013-06-24 13:41:48 +02:00
</data>
2015-07-24 17:01:56 +02:00
<data name="ALERT_ALARM_LOG_FILESYSTEM" xml:space="preserve">
<value>File System on Logs Partition Full</value>
</data>
<data name="ALERT_ALARM_LOG_FILESYSTEM_DESCRIPTION" xml:space="preserve">
<value>The disk usage for the Logs Partition on {0} has reached {1}. Logging will be critically affected if this disk becomes full. Old log files should be removed.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ALERT_ALARM_MEMORY" xml:space="preserve">
<value>Memory Usage Alarm</value>
</data>
<data name="ALERT_ALARM_MEMORY_DESCRIPTION" xml:space="preserve">
<value>Free memory on {0} has been {1} for the last {2}.
This alarm is set to be triggered when free memory falls below {3}.</value>
</data>
<data name="ALERT_ALARM_NETWORK" xml:space="preserve">
<value>Network Usage Alarm</value>
</data>
<data name="ALERT_ALARM_NETWORK_DESCRIPTION" xml:space="preserve">
<value>Network usage on {0} has been on average {1} for the last {2}.
This alarm is set to be triggered when network usage is more than {3}.</value>
2015-09-10 16:18:26 +02:00
</data>
<data name="ALERT_ALARM_SR_PHYSICAL_UTILISATION" xml:space="preserve">
<value>SR Disk Space Alarm</value>
</data>
<data name="ALERT_ALARM_SR_PHYSICAL_UTILISATION_DESCRIPTION" xml:space="preserve">
2015-09-23 15:26:11 +02:00
<value>The physical utilization on {0} is about {1} of its capacity.
2015-09-10 16:18:26 +02:00
This alarm is set to be triggered when the physical utilisation of the SR goes above {2}.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ALERT_ALARM_STORAGE" xml:space="preserve">
<value>Storage Throughput Alarm</value>
</data>
<data name="ALERT_ALARM_STORAGE_DESCRIPTION" xml:space="preserve">
2017-01-16 17:49:10 +01:00
<value>The total read and write throughput of {0} on storage repository '{1}' has been {2} for the last {3}.
This alarm is set to be triggered when the total throughput exceeds {4}.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ALERT_CAP_LABEL" xml:space="preserve">
<value>(Showing first {0} entries)</value>
</data>
<data name="ALERT_CPUS_SUB_TEXT" xml:space="preserve">
<value>When CPU usage exceeds {0}% for {1} min(s)</value>
</data>
<data name="ALERT_DISK_SUB_TEXT" xml:space="preserve">
<value>When disk usage exceeds {0} for {1} min(s)</value>
</data>
2013-07-18 14:56:40 +02:00
<data name="ALERT_DISMISS" xml:space="preserve">
<value>Dismiss</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ALERT_DISMISS_ALL_CONTINUE" xml:space="preserve">
2013-08-14 17:59:25 +02:00
<value>You have applied filters to the list of alerts. Do you wish to dismiss all alerts from every connected server, or only the alerts you have chosen to view? In both cases the dismissed alerts will be removed from the servers permanently.
2013-06-24 13:41:48 +02:00
2013-08-14 17:59:25 +02:00
Note that if RBAC is enabled, only alerts which you have privileges to dismiss will be affected.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ALERT_DISMISS_ALL_NO_FILTER_CONTINUE" xml:space="preserve">
2013-08-14 17:59:25 +02:00
<value>This operation will remove permanently all alerts from every connected server. Do you wish to continue?
2013-06-24 13:41:48 +02:00
2013-08-14 17:59:25 +02:00
Note that if RBAC is enabled, only alerts which you have privileges to dismiss will be affected.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ALERT_DISMISS_CONFIRM" xml:space="preserve">
<value>Once a system alert is dismissed it will be removed from the server permanently. Do you wish to continue?</value>
</data>
2014-07-29 11:19:54 +02:00
<data name="ALERT_DISMISS_SELECTED_CONFIRM" xml:space="preserve">
<value>This operation will remove the selected alerts from the servers permanently. Do you wish to continue?
Note that if RBAC is enabled, only alerts which you have privileges to dismiss will be affected.</value>
</data>
2014-08-05 22:40:26 +02:00
<data name="ALERT_DOM0_MEMORY_SUB_TEXT" xml:space="preserve">
<value>When control domain memory usage exceeds {0} for {1} min(s)</value>
</data>
2013-08-14 18:12:39 +02:00
<data name="ALERT_EXPORT_ALL_BUTTON" xml:space="preserve">
<value>Export &all</value>
</data>
<data name="ALERT_EXPORT_ALL_OR_FILTERED" xml:space="preserve">
<value>You have applied filters to the list of alerts. Do you wish to export all alerts from every connected server, or only the alerts you have chosen to view?</value>
</data>
<data name="ALERT_EXPORT_FILTERED_BUTTON" xml:space="preserve">
2014-08-05 17:13:48 +02:00
<value>Only export &visible</value>
2013-08-14 18:12:39 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ALERT_GENERIC_HELP" xml:space="preserve">
2013-07-18 14:56:40 +02:00
<value>Help</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ALERT_MEMORY_SUB_TEXT" xml:space="preserve">
<value>When free memory falls below {0} for {1} min(s)</value>
</data>
<data name="ALERT_NET_SUB_TEXT" xml:space="preserve">
<value>When network usage exceeds {0} for {1} min(s)</value>
</data>
<data name="ALERT_NEW_PATCH_DOWNLOAD" xml:space="preserve">
2013-07-18 14:56:40 +02:00
<value>Go to Web Page</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ALERT_NEW_VERSION" xml:space="preserve">
2017-03-14 18:31:32 +01:00
<value>{0} is now available</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ALERT_NEW_VERSION_DETAILS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>{0} is now available. Download the new version from the [Citrix] website.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ALERT_NEW_VERSION_DOWNLOAD" xml:space="preserve">
2013-07-18 14:56:40 +02:00
<value>Go to Web Page</value>
2013-06-24 13:41:48 +02:00
</data>
2015-09-21 01:04:46 +02:00
<data name="ALERT_SR_PHYSICAL_UTILISATION_SUB_TEXT" xml:space="preserve">
2015-09-23 15:26:11 +02:00
<value>When SR physical utilization exceeds {0} for {1} min(s)</value>
2015-09-21 01:04:46 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ALERT_SR_SUB_TEXT" xml:space="preserve">
<value>When storage throughput exceeds {0} for {1} min(s)</value>
</data>
2015-12-18 19:35:17 +01:00
<data name="ALLOWED_MTU_RANGE" xml:space="preserve">
<value>Allowed MTU range: {0} to {1}</value>
</data>
<data name="ALLOWED_MTU_VALUE" xml:space="preserve">
<value>Allowed MTU value: {0}</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ALLOW_TO_CONTINUE" xml:space="preserve">
<value>&Allow to continue</value>
</data>
<data name="ALL_FILES" xml:space="preserve">
<value>All Files</value>
</data>
<data name="ALL_OF" xml:space="preserve">
<value>All of the following:</value>
</data>
<data name="ALL_SERVERS_LICENSED" xml:space="preserve">
<value>All your managed servers are fully licensed.</value>
</data>
<data name="ALL_SRS" xml:space="preserve">
<value>All Storage Repositories</value>
</data>
<data name="ALL_TYPES" xml:space="preserve">
<value>All resources</value>
</data>
<data name="ALL_TYPES_AND_FOLDERS" xml:space="preserve">
<value>All resources and folders</value>
</data>
<data name="ALL_UPDATES_APPLIED" xml:space="preserve">
<value>All Updates Applied</value>
</data>
<data name="ALL_UPDATES_UPLOADED" xml:space="preserve">
<value>All Updates Uploaded</value>
</data>
<data name="ALREADY_ATTACHED_ELSEWHERE" xml:space="preserve">
<value>The SR '{0}' is currently attached elsewhere. Do you want to attach it to '{1}'?
2016-02-10 12:52:30 +01:00
Warning: you must ensure that the SR is not in use by any server not connected to [XenCenter]. Failure to do so may result in data loss.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ALREADY_CONNECTED" xml:space="preserve">
<value>You are already connected to server '{0}'.</value>
</data>
<data name="ALREADY_IN_BOND" xml:space="preserve">
<value>already in {0}</value>
</data>
<data name="ANCESTOR_FOLDERS" xml:space="preserve">
<value>Any ancestor folder</value>
</data>
<data name="ANY_OF" xml:space="preserve">
<value>Any of the following:</value>
</data>
<data name="APPLIED_ON" xml:space="preserve">
<value>Applied on: </value>
</data>
<data name="APPLIES_TO" xml:space="preserve">
<value>Applies To</value>
</data>
<data name="APPLYING_HOTFIX_TO_HOST" xml:space="preserve">
<value>Applying hotfix to '{0}'</value>
</data>
<data name="APPLYING_PATCH" xml:space="preserve">
<value>Applying Update '{0}' to Server '{1}'...</value>
</data>
<data name="APPLYLICENSE_APPLIED" xml:space="preserve">
<value>License applied</value>
</data>
<data name="APPLYLICENSE_APPLYING" xml:space="preserve">
<value>Applying license {0}...</value>
</data>
<data name="APPLYLICENSE_PREP" xml:space="preserve">
<value>Preparing to apply license</value>
</data>
<data name="APPLYLICENSE_TITLE" xml:space="preserve">
<value>Applying license to server {0}</value>
</data>
<data name="APPLYLICENSE_UPDATED" xml:space="preserve">
<value>License updated</value>
</data>
<data name="APPLY_ACTIVATION_KEY" xml:space="preserve">
<value>Apply Activation Key</value>
</data>
<data name="APPLY_HOTFIX" xml:space="preserve">
<value>Apply hotfix</value>
</data>
<data name="APPLY_PATCH_FAILED_LOG_MESSAGE" xml:space="preserve">
<value>Applying this update failed. Logs:
</value>
</data>
<data name="APPLY_PATCH_LOG_MESSAGE" xml:space="preserve">
<value>
Apply update '{0}' to server '{1}'...
</value>
</data>
<data name="ARCHIVED_SNAPSHOT_X" xml:space="preserve">
<value>Archived snapshot '{0}'</value>
</data>
<data name="ARCHIVE_SNAPSHOTS" xml:space="preserve">
<value>Archive Options</value>
</data>
<data name="ARCHIVE_SNAPSHOTS_TITLE" xml:space="preserve">
<value>Automatically archive scheduled snapshots</value>
</data>
<data name="ARCHIVE_SNAPSHOT_NOW_TEXT_MULTIPLE" xml:space="preserve">
<value>Do you want to archive the selected snapshots now?
Archive destination: {0}</value>
</data>
<data name="ARCHIVE_SNAPSHOT_NOW_TEXT_SINGLE" xml:space="preserve">
<value>Do you want to archive the selected snapshot now?
Archive destination: {0}</value>
</data>
<data name="ARCHIVE_SNAPSHOT_X" xml:space="preserve">
<value>Archive snapshot '{0}'</value>
</data>
<data name="ARCHIVE_VMPP_EXAMPLE_STORAGE_PATH" xml:space="preserve">
<value>Example: \\server\sharename (CIFS) or server:/sharename (NFS)</value>
</data>
<data name="ARCHIVE_VM_PROTECTION_TITLE" xml:space="preserve">
<value>Archive Snapshot Now</value>
</data>
<data name="ARCHIVING_SNAPSHOT_X" xml:space="preserve">
<value>Archiving snapshot '{0}'</value>
</data>
<data name="ARE_EMPTY" xml:space="preserve">
<value>are empty</value>
</data>
<data name="ARE_NOT_EMPTY" xml:space="preserve">
<value>are not empty</value>
</data>
<data name="ASAPSNAPSHOTTAKEN" xml:space="preserve">
<value>As soon as the snapshot is taken</value>
</data>
<data name="ASIS_CAPABLE" xml:space="preserve">
<value>A-SIS capable</value>
</data>
<data name="ASSERT_CAN_EVACUATE_CHECK_DESCRIPTION" xml:space="preserve">
2014-06-06 14:50:13 +02:00
<value>VM migration status</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ASSERT_VM_CAN_BE_RECOVERED_CHECK_DESCRIPTION" xml:space="preserve">
<value>{0}: Can recover VM check</value>
</data>
<data name="ASSIGNED_PROTECTION_POLICY" xml:space="preserve">
<value>Protection policy assigned.</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="ASSIGNED_VMSS_POLICY" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Snapshot schedule assigned.</value>
2016-01-27 11:36:48 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ASSIGNED_VM_APPLIANCE" xml:space="preserve">
<value>vApp assigned.</value>
</data>
<data name="ASSIGNING_PROTECTION_POLICY" xml:space="preserve">
<value>Assigning protection policy...</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="ASSIGNING_VMSS_POLICY" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Assigning to a snapshot schedule...</value>
2016-01-27 11:36:48 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ASSIGNING_VM_APPLIANCE" xml:space="preserve">
<value>Assigning vApp...</value>
</data>
<data name="ASSIGN_LICENSE_DIALOG_COLLAPSE_MESSAGE" xml:space="preserve">
<value>License Details</value>
</data>
<data name="ASSIGN_LICENSE_DIALOG_EXPAND_MESSAGE" xml:space="preserve">
<value>License Details</value>
</data>
<data name="ASSIGN_PROTECTION_POLICY" xml:space="preserve">
<value>Assign to VM Protection Polic&y</value>
</data>
<data name="ASSIGN_PROTECTION_POLICY_CONTEXT_MENU" xml:space="preserve">
<value>Assign to VM Protection Polic&y</value>
</data>
<data name="ASSIGN_PROTECTION_POLICY_NOAMP" xml:space="preserve">
<value>Assign to VM Protection Policy...</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="ASSIGN_VMSS_POLICY" xml:space="preserve">
2016-02-19 06:49:24 +01:00
<value>Assign VM to snapsh&ot schedule</value>
2016-01-27 11:36:48 +01:00
</data>
<data name="ASSIGN_VMSS_POLICY_CONTEXT_MENU" xml:space="preserve">
2016-02-19 06:49:24 +01:00
<value>Assign VM to snapshot schedule</value>
2016-01-27 11:36:48 +01:00
</data>
<data name="ASSIGN_VMSS_POLICY_NOAMP" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Assign VM to snapshot schedule...</value>
2016-01-27 11:36:48 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ASSIGN_VMS_TO_VAPP" xml:space="preserve">
<value>Assign VMs to vApp '{0}'</value>
</data>
<data name="ASSIGN_VM_APPLIANCE" xml:space="preserve">
<value>Assign to vA&pp</value>
</data>
<data name="ASSIGN_VM_TO_VAPP" xml:space="preserve">
<value>Assign VM '{0}' to vApp '{1}'</value>
</data>
<data name="ATTACHDISKWIZARD_ATTACHED" xml:space="preserve">
<value>Attached</value>
</data>
<data name="ATTACHDISK_SIZE_DESCRIPTION" xml:space="preserve">
<value>{0} - {1} </value>
</data>
<data name="ATTACHED_TO" xml:space="preserve">
<value>attached to</value>
</data>
<data name="ATTACHED_VIRTUAL_DISKS" xml:space="preserve">
<value>Attached virtual disks</value>
</data>
<data name="ATTACHING_VIRTUAL_DISK" xml:space="preserve">
<value>Attaching virtual disk '{0}' to VM '{1}'</value>
</data>
<data name="ATTACH_DISK_DIALOG_READONLY_DISABLED_FOR_HVM" xml:space="preserve">
<value>The selected disk can only be attached in read/write mode</value>
</data>
<data name="ATTACH_SR" xml:space="preserve">
<value>&Attach SR</value>
</data>
<data name="AUTHORIZING_USER" xml:space="preserve">
<value>Authorizing User</value>
</data>
<data name="AUTOSTART" xml:space="preserve">
<value>Auto-start on server boot</value>
</data>
<data name="AUTOSTART_ENABLED_CHECK_DESCRIPTION" xml:space="preserve">
<value>VM {0} has autostart enabled</value>
</data>
<data name="AVAILABLE" xml:space="preserve">
<value>available</value>
</data>
<data name="AVAILABLE_UPDATES_DOWNLOAD_TEXT" xml:space="preserve">
<value>Download</value>
</data>
<data name="AVAILABLE_UPDATES_ERROR" xml:space="preserve">
<value>An error occurred when searching for updates: {0}</value>
</data>
<data name="AVAILABLE_UPDATES_FOUND" xml:space="preserve">
<value>The following software updates for your system are available online.</value>
</data>
<data name="AVAILABLE_UPDATES_INTERNAL_ERROR" xml:space="preserve">
<value>There was an internal error when searching for available updates. Please see the logs for more information.</value>
</data>
<data name="AVAILABLE_UPDATES_NETWORK_ERROR" xml:space="preserve">
<value>There was a network error when searching for available updates. Please see the logs for more information.</value>
</data>
<data name="AVAILABLE_UPDATES_NOT_FOUND" xml:space="preserve">
<value>No updates found.</value>
</data>
<data name="AVAILABLE_UPDATES_SEARCHING" xml:space="preserve">
<value>Searching for updates...</value>
</data>
<data name="BACKINGUP_HOST" xml:space="preserve">
<value>Backing up server '{0}'</value>
</data>
<data name="BACKINGUP_HOST_WITH_DATA" xml:space="preserve">
<value>Backing up server '{0}', {1} received... </value>
</data>
<data name="BACKUP_HOST" xml:space="preserve">
<value>Back Up Server...</value>
</data>
<data name="BACKUP_NAME" xml:space="preserve">
<value>Backup name</value>
</data>
<data name="BACKUP_SELECT_HOST" xml:space="preserve">
<value>Select the server to restore from the list below. If the server you want is not listed here, you can add it by clicking Add New Server.</value>
</data>
<data name="BACKUP_SELECT_HOST_BUTTON" xml:space="preserve">
<value>Restore</value>
</data>
<data name="BACKUP_SELECT_HOST_TITLE" xml:space="preserve">
<value>Restore from Backup</value>
</data>
<data name="BAD_RESTORE_DETECTED" xml:space="preserve">
<value>The server you are connecting to has been restored from a backup of '{0}', a server you are already connected to.
This is a potentially dangerous operation and is not allowed.</value>
</data>
<data name="BAD_SERVER_RESPONSE" xml:space="preserve">
<value>The server '{0}' gave a bad response to the query.</value>
</data>
<data name="BALLOONING_PAGE_CHOOSEVMS_PAGETITLE" xml:space="preserve">
<value>Choose the VMs whose memory settings you wish to adjust</value>
</data>
<data name="BALLOONING_PAGE_CHOOSEVMS_TEXT" xml:space="preserve">
<value>Select VMs</value>
</data>
<data name="BALLOONING_PAGE_MEMORY_PAGETITLE" xml:space="preserve">
<value>Configure the memory settings for your selected VMs</value>
</data>
<data name="BALLOONING_PAGE_MEMORY_TEXT" xml:space="preserve">
<value>Adjust memory settings</value>
</data>
<data name="BALLOONING_RUBRIC" xml:space="preserve">
<value>Set a fixed memory for this VM, or set a memory range and allow the VM's memory allocation to be adjusted automatically.</value>
</data>
<data name="BALLOONING_RUBRIC_ADVANCED" xml:space="preserve">
<value>Set the memory range and static maximum memory for this VM.</value>
</data>
<data name="BALLOONING_RUBRIC_ADVANCED_TEMPLATE" xml:space="preserve">
<value>Set the memory range and static maximum memory for VMs created from this template.</value>
</data>
<data name="BALLOONING_RUBRIC_TEMPLATE" xml:space="preserve">
<value>Set a fixed memory for VMs created from this template, or set a memory range and allow the VMs' memory allocation to be adjusted automatically.</value>
</data>
<data name="BASE" xml:space="preserve">
<value>Base</value>
</data>
<data name="BEFORE" xml:space="preserve">
<value>is before</value>
</data>
<data name="BEFORE_YOU_START" xml:space="preserve">
<value>Before You Start</value>
</data>
<data name="BIGGER_THAN" xml:space="preserve">
<value>bigger than</value>
</data>
<data name="BIOS_STRINGS_COPIED" xml:space="preserve">
<value>BIOS strings copied</value>
</data>
2014-08-04 11:38:49 +02:00
<data name="BOND" xml:space="preserve">
2014-08-04 05:16:47 +02:00
<value>Bonded network</value>
2014-08-04 11:38:49 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="BOND_CREATE" xml:space="preserve">
<value>Create Bond</value>
</data>
<data name="BOND_CREATE_CONTINUE" xml:space="preserve">
<value>&Create bond anyway</value>
</data>
<data name="BOND_CREATE_HA_ENABLED" xml:space="preserve">
<value>Can’ t create this bond while HA is enabled
A management interface exists on one of the selected NICs. Moving the management interface to the bond could result in HA network heartbeat failure, so this action is not allowed while HA is on.
To continue, either select different NICs for the bond, or disable HA, create the bond, and then enable HA again.</value>
</data>
<data name="BOND_CREATE_WILL_DISTURB_BOTH" xml:space="preserve">
<value>This bond cannot be created because both management and secondary interfaces exist on your selected bond members.
Both types of interface cannot be added to the same bond. Choose different bond members, or move the management interfaces before creating the bond.</value>
</data>
<data name="BOND_CREATE_WILL_DISTURB_PRIMARY" xml:space="preserve">
<value>Creating this bond will automatically move the management interface on one of your selected bond members to the bond itself:
2016-02-10 12:52:30 +01:00
- [XenCenter] connections to the pool will temporarily be disturbed
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
- If your network configuration is incorrect then [XenCenter] may permanently lose the connection to the pool, or pool members may be unable to contact each other.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="BOND_CREATE_WILL_DISTURB_SECONDARY" xml:space="preserve">
<value>Creating this bond will disrupt traffic through the secondary interfaces on the bond members while the interfaces are moved onto the bond itself.</value>
</data>
<data name="BOND_DELETE_CONTINUE" xml:space="preserve">
<value>&Delete bond anyway</value>
</data>
<data name="BOND_DELETE_HA_ENABLED" xml:space="preserve">
<value>Can’ t delete this bond while HA is enabled
A management interface exists on one of the bonded NICs. Deleting the bond could result in HA network heartbeat failure, so this action is not allowed while HA is on.
To continue, disable HA, delete the bond, and then enable HA again.</value>
</data>
<data name="BOND_DELETE_WILL_DISTURB_BOTH" xml:space="preserve">
<value>{0}
Deleting this bond will automatically transfer the management and secondary interfaces on the bond to the first slave member of the bond:
2016-02-10 12:52:30 +01:00
- [XenCenter] connections to the pool will temporarily be disturbed
2013-06-24 13:41:48 +02:00
- Traffic through the secondary interface will be disrupted
2016-02-10 12:52:30 +01:00
- If your network configuration is incorrect then [XenCenter] may permanently lose the connection to the pool, or pool members may be unable to contact each other.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="BOND_DELETE_WILL_DISTURB_PRIMARY" xml:space="preserve">
<value>{0}
Deleting this bond will automatically transfer the management interface on the bond to the first slave member of the bond:
2016-02-10 12:52:30 +01:00
- [XenCenter] connections to the pool will temporarily be disturbed
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
- If your network configuration is incorrect then [XenCenter] may permanently lose the connection to the pool, or pool members may be unable to contact each other.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="BOND_DELETE_WILL_DISTURB_SECONDARY" xml:space="preserve">
<value>{0}
Deleting this bond will disrupt traffic through the secondary interface on the bond while the interface is moved to the first slave of the bond.</value>
</data>
<data name="BOOTORDER" xml:space="preserve">
<value>Boot order: {0}</value>
</data>
<data name="BOOT_DEVICE_DISABLED_ROW_TEXT" xml:space="preserve">
<value>VM will not boot from devices below this line</value>
</data>
<data name="BOOT_DVD_DRIVE" xml:space="preserve">
<value>DVD-Drive</value>
</data>
<data name="BOOT_HARD_DISK" xml:space="preserve">
<value>Hard Disk</value>
</data>
<data name="BROKEN_SRS_AFTER_UPGRADE" xml:space="preserve">
<value>There are broken SRs after the upgrade. To solve this problem you should reattach the SRs.</value>
</data>
<data name="BROKEN_TOOLS_PROMPT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Your Tools ISO is on a broken SR, [XenCenter] will attempt to fix it before proceeding. Do you wish to continue?</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="BUGTOOL_FILE_PREFIX" xml:space="preserve">
<value>status-report-</value>
</data>
<data name="BUGTOOL_HOST_STATUS_COMPILING" xml:space="preserve">
<value>Compiling</value>
</data>
<data name="BUGTOOL_HOST_STATUS_DOWNLOADING" xml:space="preserve">
<value>Downloading - {0}</value>
</data>
<data name="BUGTOOL_HOST_STATUS_FAILED" xml:space="preserve">
<value>Failed</value>
</data>
<data name="BUGTOOL_HOST_STATUS_FAILED_WITH_ERROR" xml:space="preserve">
<value>Failed - {0}</value>
</data>
<data name="BUGTOOL_HOST_STATUS_PENDING" xml:space="preserve">
<value>Pending</value>
</data>
<data name="BUGTOOL_PAGE_CAPABILITIES_PAGETITLE" xml:space="preserve">
<value>Select the data you wish to include in your report</value>
</data>
<data name="BUGTOOL_PAGE_CAPABILITIES_TEXT" xml:space="preserve">
<value>Select Report Contents</value>
</data>
2015-11-03 16:45:59 +01:00
<data name="BUGTOOL_PAGE_DESTINATION_INVALID_CASE_NO" xml:space="preserve">
<value>Case number is invalid.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="BUGTOOL_PAGE_DESTINATION_INVALID_FOLDER" xml:space="preserve">
<value>Destination directory is invalid.</value>
</data>
<data name="BUGTOOL_PAGE_DESTINATION_INVALID_NAME" xml:space="preserve">
<value>File name is invalid.</value>
</data>
<data name="BUGTOOL_PAGE_DESTINATION_PAGETITLE" xml:space="preserve">
<value>Select a destination folder for the report files</value>
</data>
<data name="BUGTOOL_PAGE_DESTINATION_TEXT" xml:space="preserve">
<value>Report Destination</value>
</data>
<data name="BUGTOOL_PAGE_RETRIEVEDATA_CONFIRM_CANCEL" xml:space="preserve">
<value>Are you sure you wish to cancel the current action?</value>
</data>
<data name="BUGTOOL_PAGE_RETRIEVEDATA_PAGE_TITLE" xml:space="preserve">
<value>Compiling Status Report</value>
</data>
<data name="BUGTOOL_PAGE_RETRIEVEDATA_TEXT" xml:space="preserve">
<value>Compile Report</value>
</data>
<data name="BUGTOOL_PAGE_SERVERS_TEXT" xml:space="preserve">
<value>Select Servers</value>
</data>
<data name="BUGTOOL_PAGE_SERVERS_TITLE" xml:space="preserve">
<value>Select the servers you wish to include in the report</value>
</data>
<data name="BUGTOOL_RBAC_FAILURE" xml:space="preserve">
<value>A {0} user cannot retrieve all the specified items.</value>
</data>
<data name="BUGTOOL_SAVING" xml:space="preserve">
<value>Saving server status report</value>
</data>
2014-08-04 05:16:47 +02:00
<data name="BUILTIN_NETWORK" xml:space="preserve">
<value>Built-in network</value>
2014-08-07 08:18:29 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="BUS_PATH" xml:space="preserve">
<value>PCI Bus Path</value>
</data>
<data name="BUTTON_DISCLOSURE_TOOLTIP" xml:space="preserve">
<value>Open or Collapse the Properties</value>
</data>
<data name="CACHE_NOT_YET_POPULATED" xml:space="preserve">
<value>Cache not yet populated</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="CACHING" xml:space="preserve">
<value>Caching</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CANCEL" xml:space="preserve">
<value>Cancel</value>
</data>
<data name="CANCELING" xml:space="preserve">
<value>Canceling...</value>
</data>
<data name="CANCELING_TASKS" xml:space="preserve">
<value>Canceling Tasks</value>
</data>
<data name="CANCELLED_BY_USER" xml:space="preserve">
<value>Cancelled by user</value>
</data>
<data name="CANCEL_CONNECT" xml:space="preserve">
<value>Cancel Connect</value>
</data>
<data name="CANNOT_ACTIVATE_ISO_IN_USE" xml:space="preserve">
<value>This ISO storage is in use and cannot be activated.</value>
</data>
<data name="CANNOT_ACTIVATE_SNAPSHOT_IN_USE" xml:space="preserve">
<value>This snapshot is in use and cannot be activated.</value>
</data>
<data name="CANNOT_ACTIVATE_VD_ALREADY_ACTIVE" xml:space="preserve">
<value>This virtual disk is already activated on VM '{0}'.</value>
</data>
<data name="CANNOT_ACTIVATE_VD_IN_USE" xml:space="preserve">
<value>This virtual disk is in use and cannot be activated.</value>
</data>
<data name="CANNOT_ACTIVATE_VD_VM_HALTED" xml:space="preserve">
<value>It is not possible to activate this virtual disk on VM '{0}' as the VM is not running.</value>
</data>
2015-09-14 17:21:44 +02:00
<data name="CANNOT_ACTIVATE_VD_VM_NEEDS_IO_DRIVERS" xml:space="preserve">
2015-09-21 17:09:12 +02:00
<value>You must install I/O drivers on VM '{0}' before you can activate this virtual disk for the VM.</value>
2015-09-14 17:21:44 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CANNOT_ACTIVATE_VD_VM_NEEDS_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>You must install [XenServer product] Tools on VM '{0}' before you can activate this virtual disk for the VM.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CANNOT_CONFIGURE_JUMBO_DISTURB_MANAGEMENT" xml:space="preserve">
<value>(The network's MTU cannot be changed as it is in use as the management interface '{0}')</value>
</data>
<data name="CANNOT_CONFIGURE_JUMBO_VM_NO_TOOLS" xml:space="preserve">
<value>(The network's MTU cannot be changed as there are active VMs attached without tools installed)</value>
</data>
<data name="CANNOT_CONFIGURE_MORE_FREQ_ARCHIVE" xml:space="preserve">
<value>You cannot configure an archive that is more frequent than the snapshot schedule</value>
</data>
<data name="CANNOT_CONFIGURE_NET_DISTURB_MANAGEMENT" xml:space="preserve">
<value>(The network's NIC and VLAN cannot be changed as it is in use as the management interface '{0}')</value>
</data>
<data name="CANNOT_CONFIGURE_NET_VMS_ATTACHED" xml:space="preserve">
<value>(The network's NIC and VLAN cannot be changed as there are active VMs attached)</value>
</data>
<data name="CANNOT_DEACTIVATE_ISO_IN_USE" xml:space="preserve">
<value>This ISO storage is in use and cannot be deactivated.</value>
</data>
<data name="CANNOT_DEACTIVATE_NOT_ACTIVE" xml:space="preserve">
<value>This virtual disk is already deactivated on VM '{0}'.</value>
</data>
<data name="CANNOT_DEACTIVATE_SNAPSHOT_IN_USE" xml:space="preserve">
<value>This snapshot is in use and cannot be deactivated.</value>
</data>
<data name="CANNOT_DEACTIVATE_VDI_IN_USE" xml:space="preserve">
<value>This virtual disk is in use and cannot be deactivated.</value>
</data>
2015-09-14 17:21:44 +02:00
<data name="CANNOT_DEACTIVATE_VDI_NEEDS_IO_DRIVERS" xml:space="preserve">
2015-09-21 17:09:12 +02:00
<value>You must install I/O drivers on VM '{0}' before you can deactivate this virtual disk for the VM.</value>
2015-09-14 17:21:44 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CANNOT_DEACTIVATE_VDI_NEEDS_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>You must install [XenServer product] Tools on VM '{0}' before you can deactivate this virtual disk for the VM.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CANNOT_DEACTIVATE_VDI_VM_NOT_RUNNING" xml:space="preserve">
<value>It is not possible to deactivate this virtual disk on VM '{0}' as the VM is not running.</value>
</data>
<data name="CANNOT_DELETE_ACTIVE_VDI" xml:space="preserve">
<value>Virtual disks must be deactivated before being deleted. This virtual disk is in use by the VM '{0}'.</value>
</data>
<data name="CANNOT_DELETE_ACTIVE_VDI_ISO" xml:space="preserve">
<value>ISO storage must be ejected from VMs before being deleted. This storage is in use by the VM '{0}'.</value>
</data>
<data name="CANNOT_DELETE_CANNOT_DEACTIVATE_REASON" xml:space="preserve">
<value>It is not possible to deactivate and delete this virtual disk on the VM '{0}':
{1}</value>
</data>
<data name="CANNOT_DELETE_DEFAULT_TEMPLATE" xml:space="preserve">
2016-11-11 18:24:57 +01:00
<value>[XenServer] templates cannot be deleted.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CANNOT_DELETE_DR_VD" xml:space="preserve">
<value>This virtual disk is used for DR. To delete it, configure DR not to save data to this storage repository.</value>
</data>
<data name="CANNOT_DELETE_HA_VD" xml:space="preserve">
<value>This virtual disk is used for HA. To delete it, first disable HA.</value>
</data>
<data name="CANNOT_DELETE_IN_USE_SYS_VD" xml:space="preserve">
<value>Cannot delete this system disk as it is in use by the running VM '{0}'.</value>
</data>
<data name="CANNOT_DELETE_ISO_GENERIC" xml:space="preserve">
<value>It is not possible to delete this ISO storage. Try again later and confirm your SR supports this operation.</value>
</data>
<data name="CANNOT_DELETE_ISO_IN_USE" xml:space="preserve">
<value>This ISO storage is currently in use and cannot be deleted.</value>
</data>
<data name="CANNOT_DELETE_SNAPSHOT_GENERIC" xml:space="preserve">
<value>It is not possible to delete this snapshot. Try again later and confirm your SR supports this operation.</value>
</data>
<data name="CANNOT_DELETE_SNAPSHOT_IN_USE" xml:space="preserve">
<value>This snapshot is currently in use and cannot be deleted.</value>
</data>
<data name="CANNOT_DELETE_TOOLS_SR" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Deleting the [XenServer product] Tools ISO storage is not supported.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CANNOT_DELETE_VDI_ACTIVE_ON" xml:space="preserve">
<value>This virtual disk is active on VM '{0}'. Deactivate the virtual disk before deleting.</value>
</data>
<data name="CANNOT_DELETE_VDI_MULTIPLE_VBDS" xml:space="preserve">
<value>This virtual disk is attached to multiple VMs. Detach your virtual disk from these VMs before deleting it.</value>
</data>
<data name="CANNOT_DELETE_VDI_RUNNING_VM_NO_TOOLS" xml:space="preserve">
<value>Running VMs require tools to be installed before you can delete their virtual disks. This disk is in us by the running VM '{0}'.</value>
</data>
<data name="CANNOT_DELETE_VDI_SUSPENDED_VM" xml:space="preserve">
<value>Virtual disks cannot be deleted from suspended VMs. This virtual disk is used by the suspended VM '{0}'.</value>
</data>
<data name="CANNOT_DELETE_VD_GENERIC" xml:space="preserve">
<value>It is not possible to delete this virtual disk. Try again later and confirm your SR supports this operation.</value>
</data>
<data name="CANNOT_DELETE_VD_IN_USE" xml:space="preserve">
<value>This virtual disk is currently in use and cannot be deleted.</value>
</data>
<data name="CANNOT_FIND_SR_WIZARD_TYPE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>You cannot configure an SR of type '{0}' using [XenCenter].</value>
2013-06-24 13:41:48 +02:00
</data>
2015-05-19 15:02:10 +02:00
<data name="CANNOT_MIGRATE_VDI_NON_RUNNING_VM" xml:space="preserve">
<value>Cannot move this virtual disk as it is attached to a non running VM.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CANNOT_MOVE_DR_VD" xml:space="preserve">
<value>This virtual disk is used for DR. It cannot be moved to another storage repository.</value>
</data>
<data name="CANNOT_MOVE_HA_VD" xml:space="preserve">
<value>This virtual disk is used for HA. It cannot be moved to another storage repository.</value>
</data>
<data name="CANNOT_MOVE_VDI_IN_USE" xml:space="preserve">
<value>This virtual disk is in use and cannot be moved.</value>
</data>
<data name="CANNOT_MOVE_VDI_IS_SNAPSHOT" xml:space="preserve">
<value>Snapshot disks cannot be moved</value>
</data>
<data name="CANNOT_MOVE_VDI_WITH_VBDS" xml:space="preserve">
2016-09-06 15:53:46 +02:00
<value>You must detach this virtual disk before it can be moved.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CANNOT_PARSE_NODE_PARAM" xml:space="preserve">
<value>Cannot parse required parameter '{1}' on XML node '{0}'</value>
</data>
<data name="CANNOT_REMOVE_SL_SERVER" xml:space="preserve">
<value>This StorageLink server cannot be removed because it is currently in use.</value>
</data>
<data name="CANT_JOIN_POOL_1" xml:space="preserve">
<value>The server '{0}' cannot join the pool '{1}' for the following reason:
{2}</value>
</data>
<data name="CANT_JOIN_POOL_N" xml:space="preserve">
<value>The following servers cannot join the pool '{0}':
{1}</value>
</data>
2015-05-15 16:16:46 +02:00
<data name="CDDRIVE_MAX_ALLOWED_VBDS" xml:space="preserve">
<value>The DVD drive cannot be created, because you have reached the maximum number of virtual disks allowed for this virtual machine.</value>
</data>
2014-04-14 17:44:14 +02:00
<data name="CD_DRIVE" xml:space="preserve">
<value>DVD drive on {0}</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CHANGE" xml:space="preserve">
<value>Change...</value>
</data>
<data name="CHANGED_MASTER_PASSWORD" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Changed [XenCenter] master password</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CHANGED_MASTER_PASSWORD_LONG" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Changed [XenCenter] master password for session restore</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CHANGED_SERVER_CD" xml:space="preserve">
<value>Server CD changed</value>
</data>
<data name="CHANGEPASS_DIALOG_TITLE" xml:space="preserve">
<value>Change Server Password - {0}</value>
</data>
<data name="CHANGEPASS_ROOT_PASS" xml:space="preserve">
<value>Please type the root password for {0}:</value>
</data>
<data name="CHANGE_POLICY_STATUS" xml:space="preserve">
<value>Change policy '{0}' status</value>
</data>
<data name="CHANGE_SERVER_CD" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Insert [XenServer] CD</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CHANGE_SERVER_PASSWORD" xml:space="preserve">
<value>Change Server Password...</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="CHANGE_VMSS_POLICY" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Assign VM to snapshot schedule</value>
2016-01-27 11:36:48 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CHANGE_VMS_APPLIANCE" xml:space="preserve">
<value>Assign VM to vApp</value>
</data>
<data name="CHANGE_VMS_APPLIANCES_WARNING" xml:space="preserve">
<value>Some of the VMs you selected are already assigned to a different vApp.
Do you want to assign these VMs to the vApp '{0}' instead?</value>
</data>
<data name="CHANGE_VMS_APPLIANCE_WARNING" xml:space="preserve">
<value>The VM '{0}' is already assigned to the vApp '{1}'.
Do you want to assign it to the vApp '{2}' instead?</value>
</data>
<data name="CHANGE_VMS_POLICIES_WARNING" xml:space="preserve">
<value>Some of the VMs you selected are already assigned to a different protection policy.
Do you want to assign these VMs to the policy '{0}' instead?</value>
</data>
<data name="CHANGE_VMS_POLICY" xml:space="preserve">
<value>Assign VM to Protection Policy</value>
</data>
<data name="CHANGE_VMS_POLICY_WARNING" xml:space="preserve">
<value>The VM '{0}' is already assigned to the protection policy '{1}'.
Do you want to assign it to the policy '{2}' instead?</value>
2016-01-27 11:36:48 +01:00
</data>
<data name="CHANGE_VMS_SNAPSHOT_SCHEDULE_WARNING" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Some of the VMs you selected are already assigned to a different snapshot schedule.
2016-01-27 11:36:48 +01:00
2016-02-18 11:49:40 +01:00
Do you want to assign these VMs to the schedule '{0}' instead?</value>
2016-01-27 11:36:48 +01:00
</data>
<data name="CHANGE_VM_SNAPSHOT_SCHEDULE_WARNING" xml:space="preserve">
<value>The VM '{0}' is already assigned to the snashot schedule '{1}'.
Do you want to assign it to the schedule '{2}' instead?</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CHECKING_CANEVACUATE_STATUS" xml:space="preserve">
2014-06-06 14:50:13 +02:00
<value>Checking VM migration status</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CHECKING_HA_STATUS" xml:space="preserve">
<value>Checking HA and WLB status</value>
</data>
<data name="CHECKING_HOST_LIVENESS_STATUS" xml:space="preserve">
<value>Checking host liveness status</value>
</data>
<data name="CHECKING_LICENSING_STATUS" xml:space="preserve">
<value>Checking license status</value>
</data>
<data name="CHECKING_ROLE" xml:space="preserve">
<value>Checking role...</value>
</data>
2015-06-04 16:24:04 +02:00
<data name="CHECKING_SAFE_TO_UPGRADE" xml:space="preserve">
2016-03-07 14:38:22 +01:00
<value>Checking partition layout</value>
2015-06-04 16:24:04 +02:00
</data>
2016-10-19 14:10:24 +02:00
<data name="CHECKING_SERVER_NEEDS_REBOOT" xml:space="preserve">
2016-10-20 14:09:48 +02:00
<value>Checking reboots required</value>
2016-10-19 14:10:24 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CHECKING_SERVER_SIDE_STATUS" xml:space="preserve">
<value>Checking server side status</value>
</data>
<data name="CHECKING_STORAGELINK_CONNECTIONS" xml:space="preserve">
<value>Checking StorageLink connections</value>
</data>
2014-05-21 14:47:51 +02:00
<data name="CHECKING_STORAGELINK_STATUS" xml:space="preserve">
<value>Checking StorageLink status</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CHECKING_STORAGE_CONNECTIONS_STATUS" xml:space="preserve">
<value>Checking storage connections status</value>
</data>
<data name="CHECKING_UPGRADE_HOTFIX_STATUS" xml:space="preserve">
<value>Checking upgrade hotfix status</value>
</data>
<data name="CHECKING_VMPR_STATUS" xml:space="preserve">
<value>Checking the presence of VM Protection Policies</value>
</data>
<data name="CHECKING_WSS_STATUS" xml:space="preserve">
<value>Checking the possible presence of WSS appliances</value>
</data>
<data name="CHECK_WLB_ENABLED" xml:space="preserve">
2014-04-22 13:14:53 +02:00
<value>Pool '{0}' cannot have WLB enabled</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CHIN" xml:space="preserve">
<value>Cross-server private network</value>
</data>
<data name="CHINS" xml:space="preserve">
<value>Cross-server private networks</value>
</data>
<data name="CHINS_NEED_VSWITCHCONTROLLER" xml:space="preserve">
<value>Cross-server private networks require the vSwitch Controller to be configured and running.</value>
</data>
<data name="CHOOSE_ANOTHER_DESTINATION" xml:space="preserve">
<value>Choose another &destination</value>
</data>
<data name="CHOOSE_SR_TYPE_PAGE_TITLE" xml:space="preserve">
<value>Choose the type of new storage</value>
</data>
<data name="CHOOSE_VMS_VAPP_RUBRIC" xml:space="preserve">
<value>Select a checkbox to add a VM to the vApp; clear its checkbox to remove it from the vApp.</value>
</data>
<data name="CHOOSE_VMS_VMPP_RUBRIC" xml:space="preserve">
<value>Select a checkbox to add a VM to the protection policy; clear its checkbox to remove it from the policy.</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="CHOOSE_VMS_VMSS_RUBRIC" xml:space="preserve">
2016-02-16 10:49:39 +01:00
<value>Select a checkbox to add a VM to the snapshot schedule; clear its checkbox to remove it from the schedule.</value>
2016-01-27 11:36:48 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CLEAR_SEARCH" xml:space="preserve">
<value>Clear Search</value>
</data>
<data name="CLONING_TEMPLATE" xml:space="preserve">
<value>Cloning template '{0}'</value>
</data>
<data name="CLOSE" xml:space="preserve">
<value>Close</value>
</data>
<data name="CLOSE_WIZARD_CLICK_FINISH" xml:space="preserve">
<value>To close this wizard, click Finish</value>
</data>
<data name="COLLAPSE_CHILDREN" xml:space="preserve">
<value>&Collapse Children</value>
</data>
<data name="COMMON_CRITERIA_TEXT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>for use with Common Criteria versions of [XenServer] only</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="COMPLETED" xml:space="preserve">
<value>Completed</value>
</data>
<data name="COMPLETED_WITH_ERRORS" xml:space="preserve">
<value>Completed, with some errors encountered. See the application log files for more information.</value>
</data>
<data name="COMPRESSING_FILES" xml:space="preserve">
<value>Compressing appliance files...</value>
</data>
<data name="CONFIGURE_HA_ELLIPSIS" xml:space="preserve">
<value>&Configure HA...</value>
</data>
<data name="CONFIGURING_WLB" xml:space="preserve">
<value>Configuring Workload Balancing </value>
</data>
<data name="CONFIGURING_WLB_ON" xml:space="preserve">
<value>Configuring Workload Balancing on pool '{0}'</value>
</data>
2016-11-17 14:35:31 +01:00
<data name="CONFIRMATIONS" xml:space="preserve">
<value>Confirmations</value>
</data>
<data name="CONFIRMATIONS_DETAIL" xml:space="preserve">
<value>Confirm dismissal of notifications</value>
</data>
2016-08-01 10:25:10 +02:00
<data name="CONFIRM_CHANGE_CONTROL_DOMAIN_MEMORY" xml:space="preserve">
<value>Changing the Control Domain memory will cause the server to be rebooted.
Do you want to continue?</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CONFIRM_CHANGE_MEMORY_MAX_PLURAL" xml:space="preserve">
<value>Changing the maximum memory of these VMs will cause them to be rebooted.
Do you want to continue?</value>
</data>
<data name="CONFIRM_CHANGE_MEMORY_MAX_SINGULAR" xml:space="preserve">
<value>Changing the maximum memory of this VM will cause it to be rebooted.
Do you want to continue?</value>
</data>
<data name="CONFIRM_CHANGE_MEMORY_PLURAL" xml:space="preserve">
<value>Changing the memory of these VMs while they are running will cause them to be forcibly rebooted. This operation can lose data.
Do you want to continue?</value>
</data>
<data name="CONFIRM_CHANGE_MEMORY_SINGULAR" xml:space="preserve">
<value>Changing the memory of this VM while it is running will cause it to be forcibly rebooted. This operation can lose data.
Do you want to continue?</value>
</data>
<data name="CONFIRM_CHANGE_STATIC_MAX_PLURAL" xml:space="preserve">
<value>Changing the static maximum memory of these VMs will cause them to be rebooted.
Do you want to continue?</value>
</data>
<data name="CONFIRM_CHANGE_STATIC_MAX_SINGULAR" xml:space="preserve">
<value>Changing the static maximum memory of this VM will cause it to be rebooted.
Do you want to continue?</value>
</data>
<data name="CONFIRM_DELETE" xml:space="preserve">
<value>Are you sure you want to delete the selected {0}?</value>
</data>
<data name="CONFIRM_DELETE_ITEMS" xml:space="preserve">
<value>You want to delete these {0} selected items.</value>
</data>
<data name="CONFIRM_DELETE_ITEMS_TITLE" xml:space="preserve">
<value>Delete Multiple Items</value>
</data>
<data name="CONFIRM_DELETE_POLICIES" xml:space="preserve">
<value>Do you want to delete the selected policies?
{0} VMs are currently protected with these policies and will no longer be protected if you delete the policies.</value>
</data>
<data name="CONFIRM_DELETE_POLICIES_0" xml:space="preserve">
<value>Do you want to delete the selected policies?</value>
</data>
<data name="CONFIRM_DELETE_POLICY" xml:space="preserve">
<value>Do you want to delete policy '{0}'?
{1} VMs are currently protected with this policy and will no longer be protected if you delete the policy.</value>
</data>
<data name="CONFIRM_DELETE_POLICY_0" xml:space="preserve">
<value>Do you want to delete policy '{0}'?</value>
</data>
2016-10-11 14:13:50 +02:00
<data name="CONFIRM_DELETE_PVS_SITE" xml:space="preserve">
<value>Are you sure you want to delete '{0}'?</value>
</data>
2016-10-28 17:58:15 +02:00
<data name="CONFIRM_DELETE_PVS_SITE_IN_USE" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Are you sure you want to delete '{0}'? This configuration is in use by PVS-Accelerator.</value>
2016-10-28 17:58:15 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CONFIRM_DELETE_TAG" xml:space="preserve">
<value>Are you sure you want to delete the tag '{0}' from all managed resources?</value>
</data>
<data name="CONFIRM_DELETE_TAGS" xml:space="preserve">
<value>Are you sure you want to delete the selected tags from all managed resources?</value>
</data>
<data name="CONFIRM_DELETE_TAGS_TITLE" xml:space="preserve">
<value>Delete Tags</value>
</data>
<data name="CONFIRM_DELETE_TAG_TITLE" xml:space="preserve">
<value>Delete Tag</value>
</data>
<data name="CONFIRM_DELETE_TITLE" xml:space="preserve">
<value>Delete {0}</value>
</data>
<data name="CONFIRM_DELETE_VM" xml:space="preserve">
<value>Are you sure you want to delete VM '{0}' from '{1}'?</value>
</data>
<data name="CONFIRM_DELETE_VMS" xml:space="preserve">
<value>Are you sure you want to delete the following VMs from '{1}'?
{0}</value>
</data>
<data name="CONFIRM_DELETE_VM_APPLIANCE" xml:space="preserve">
<value>Do you want to delete vApp '{0}'?
{1} VMs are currently included in this vApp.</value>
</data>
<data name="CONFIRM_DELETE_VM_APPLIANCES" xml:space="preserve">
<value>Do you want to delete the selected vApps?
{0} VMs are currently included in these vApps.</value>
</data>
<data name="CONFIRM_DELETE_VM_APPLIANCES_0" xml:space="preserve">
<value>Do you want to delete the selected vApps?</value>
</data>
<data name="CONFIRM_DELETE_VM_APPLIANCES_1" xml:space="preserve">
<value>Do you want to delete the selected vApps?
{0} VM is currently included in one of these vApps.</value>
</data>
<data name="CONFIRM_DELETE_VM_APPLIANCE_0" xml:space="preserve">
<value>Do you want to delete vApp '{0}'?</value>
</data>
<data name="CONFIRM_DELETE_VM_APPLIANCE_1" xml:space="preserve">
<value>Do you want to delete vApp '{0}'?
{1} VM is currently included in this vApp.</value>
</data>
<data name="CONFIRM_DELETE_VM_APPLIANCE_AND_VMS" xml:space="preserve">
<value>Are you sure you want to delete vApp '{0}'?
This will also delete its VMs.</value>
</data>
<data name="CONFIRM_DESTROY_HOST" xml:space="preserve">
<value>Are you sure you want to destroy '{0}'?
2016-11-11 18:24:57 +01:00
You should only need to destroy a server if it has physically failed.
2014-04-15 17:07:36 +02:00
Destroying this server will permanently remove it from the pool along with its local SRs, DVD drives and removable storage. The server will need to be reinstalled before it can be used again.
2013-06-24 13:41:48 +02:00
This action is final and unrecoverable.</value>
</data>
<data name="CONFIRM_DESTROY_HOST_TITLE" xml:space="preserve">
<value>Destroy Server</value>
</data>
<data name="CONFIRM_DESTROY_HOST_YES_BUTTON_LABEL" xml:space="preserve">
<value>&Yes, Destroy</value>
</data>
2015-07-24 15:20:18 +02:00
<data name="CONFIRM_DISABLE_HEALTH_CHECK_POOL" xml:space="preserve">
<value>Are you sure you want to disable Health Check on the selected pool?</value>
</data>
<data name="CONFIRM_DISABLE_HEALTH_CHECK_SERVER" xml:space="preserve">
<value>Are you sure you want to disable Health Check on the selected server?</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CONFIRM_EXPORT_FAT" xml:space="preserve">
<value>The export file may be larger than your filesystem limit.
Estimated file size: {0}
Filesystem limit: {1}
Are you sure you want to export VM {2}?</value>
</data>
<data name="CONFIRM_EXPORT_NOT_ENOUGH_MEMORY" xml:space="preserve">
<value>There might not be enough free disk space for the export operation to complete.
Estimated space required: {0}
Free space: {1}
Are you sure you want to export VM {2}?</value>
</data>
<data name="CONFIRM_FORCEREBOOT_VM" xml:space="preserve">
<value>Are you sure you want to forcibly reboot the selected VM? This operation will cancel all running tasks for the VM and can result in data loss.</value>
</data>
<data name="CONFIRM_FORCEREBOOT_VMS" xml:space="preserve">
<value>Are you sure you want to forcibly reboot the selected VMs? This operation will cancel all running tasks for the VMs and can result in data loss.</value>
</data>
<data name="CONFIRM_FORCEREBOOT_VMS_NO_CANCEL_TASKS" xml:space="preserve">
<value>Are you sure you want to forcibly reboot the selected VMs? This operation can result in data loss.</value>
</data>
<data name="CONFIRM_FORCEREBOOT_VMS_TITLE" xml:space="preserve">
<value>Force Reboot Multiple VMs</value>
</data>
<data name="CONFIRM_FORCEREBOOT_VM_NO_CANCEL_TASKS" xml:space="preserve">
<value>Are you sure you want to forcibly reboot the selected VM? This operation can result in data loss.</value>
</data>
<data name="CONFIRM_FORCEREBOOT_VM_TITLE" xml:space="preserve">
<value>Force VM Reboot</value>
</data>
<data name="CONFIRM_FORCESHUTDOWN_VM" xml:space="preserve">
<value>Are you sure you want to forcibly shut down the selected VM? This operation will cancel all running tasks for the VM and can result in data loss.</value>
</data>
<data name="CONFIRM_FORCESHUTDOWN_VMS" xml:space="preserve">
<value>Are you sure you want to forcibly shut down the selected VMs? This operation will cancel all running tasks for each of the selected VMs and can result in data loss.</value>
</data>
<data name="CONFIRM_FORCESHUTDOWN_VMS_NO_CANCEL_TASKS" xml:space="preserve">
<value>Are you sure you want to forcibly shut down the selected VMs? This operation can result in data loss.</value>
</data>
<data name="CONFIRM_FORCESHUTDOWN_VMS_TITLE" xml:space="preserve">
<value>Force Shut Down Multiple VMs</value>
</data>
<data name="CONFIRM_FORCESHUTDOWN_VM_NO_CANCEL_TASKS" xml:space="preserve">
<value>Are you sure you want to forcibly shut down the selected VM? This operation can result in data loss.</value>
</data>
<data name="CONFIRM_FORCESHUTDOWN_VM_TITLE" xml:space="preserve">
<value>Force Shut Down VM</value>
</data>
2016-06-23 16:26:32 +02:00
<data name="CONFIRM_REBOOT_HCI_WARN_SERVER" xml:space="preserve">
<value>Rebooting a server will also shut down all the VMs running on it. '{0}' is running a storage virtual appliance and rebooting it might impact the availability of your storage. Are you sure you want to continue?</value>
</data>
<data name="CONFIRM_REBOOT_HCI_WARN_SERVERS" xml:space="preserve">
<value>Rebooting a server will also shut down all the VMs running on it. The following servers are running a storage virtual appliance and rebooting them might impact the availablity of your storage:
{0}
Are you sure you want to continue?</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CONFIRM_REBOOT_SERVER" xml:space="preserve">
2016-06-23 16:26:32 +02:00
<value>Are you sure you want to reboot '{0}'?
This will also shut down all the VMs currently running on it.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CONFIRM_REBOOT_SERVERS" xml:space="preserve">
2016-06-23 16:26:32 +02:00
<value>Are you sure you want to reboot the selected servers?
This will also shut down all the VMs currently running on them.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CONFIRM_REBOOT_SERVERS_NO_VMS" xml:space="preserve">
<value>Are you sure you want to reboot the selected servers?</value>
</data>
<data name="CONFIRM_REBOOT_SERVERS_TITLE" xml:space="preserve">
<value>Reboot Multiple Servers</value>
</data>
<data name="CONFIRM_REBOOT_SERVER_NO_VMS" xml:space="preserve">
2016-06-23 16:26:32 +02:00
<value>Are you sure you want to reboot '{0}'?</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CONFIRM_REBOOT_SERVER_TITLE" xml:space="preserve">
<value>Reboot Server</value>
</data>
2016-06-23 16:26:32 +02:00
<data name="CONFIRM_REBOOT_SERVER_YES_BUTTON_LABEL" xml:space="preserve">
2016-06-27 11:43:29 +02:00
<value>&Yes, Reboot</value>
2016-06-23 16:26:32 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CONFIRM_REBOOT_VM" xml:space="preserve">
<value>Are you sure you want to reboot the selected VM?</value>
</data>
<data name="CONFIRM_REBOOT_VMS" xml:space="preserve">
<value>Are you sure you want to reboot the selected VMs?</value>
</data>
<data name="CONFIRM_REBOOT_VMS_TITLE" xml:space="preserve">
<value>Reboot Multiple VMs</value>
</data>
<data name="CONFIRM_REBOOT_VM_TITLE" xml:space="preserve">
<value>Reboot VM</value>
</data>
<data name="CONFIRM_RESTART_TOOLSTACK_MANY_SERVERS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Are you sure you want to restart the toolstack on the selected servers? Note that [XenCenter] will temporarily lose connection to them.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CONFIRM_RESTART_TOOLSTACK_ONE_SERVER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Are you sure you want to restart the toolstack on '{0}'? Note that [XenCenter] will temporarily lose connection to the server.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CONFIRM_RESTART_TOOLSTACK_TITLE" xml:space="preserve">
<value>Restart Toolstack</value>
</data>
2016-06-23 16:26:32 +02:00
<data name="CONFIRM_SHUTDOWN_HCI_WARN_SERVER" xml:space="preserve">
<value>Shutting down a server will also shut down all the VMs running on it. '{0}' is running a storage virtual appliance and shutting it down might impact the availability of your storage. Are you sure you want to continue?</value>
</data>
<data name="CONFIRM_SHUTDOWN_HCI_WARN_SERVERS" xml:space="preserve">
<value>Shutting down a server will also shut down all the VMs running on it. The following servers are running a storage virtual appliance and shutting them down might impact the availablity of your storage:
{0}
Are you sure you want to continue?</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CONFIRM_SHUTDOWN_SERVER" xml:space="preserve">
<value>Are you sure you want to shut down '{0}'?
This will also shut down all the VMs currently running on it.</value>
</data>
<data name="CONFIRM_SHUTDOWN_SERVERS" xml:space="preserve">
<value>Are you sure you want to shut down the selected servers?
This will also shut down all the VMs currently running on them.</value>
</data>
<data name="CONFIRM_SHUTDOWN_SERVERS_NO_VMS" xml:space="preserve">
<value>Are you sure you want to shut down the selected servers?</value>
</data>
<data name="CONFIRM_SHUTDOWN_SERVERS_TITLE" xml:space="preserve">
<value>Shut Down Multiple Servers</value>
</data>
<data name="CONFIRM_SHUTDOWN_SERVER_NO_VMS" xml:space="preserve">
<value>Are you sure you want to shut down '{0}'?</value>
</data>
<data name="CONFIRM_SHUTDOWN_SERVER_TITLE" xml:space="preserve">
<value>Shut Down Server</value>
</data>
<data name="CONFIRM_SHUTDOWN_SERVER_YES_BUTTON_LABEL" xml:space="preserve">
<value>&Yes, Shut Down</value>
</data>
<data name="CONFIRM_SHUTDOWN_VM" xml:space="preserve">
<value>Are you sure you want to shut down the selected VM?</value>
</data>
<data name="CONFIRM_SHUTDOWN_VMS" xml:space="preserve">
<value>Are you sure you want to shut down the selected VMs?</value>
</data>
<data name="CONFIRM_SHUTDOWN_VMS_TITLE" xml:space="preserve">
<value>Shut Down Multiple VMs</value>
</data>
<data name="CONFIRM_SHUTDOWN_VM_TITLE" xml:space="preserve">
<value>Shut Down VM</value>
</data>
<data name="CONFIRM_SHUT_DOWN_APPLIANCE" xml:space="preserve">
<value>Are you sure you want to shut down the selected vApp?</value>
</data>
<data name="CONFIRM_SHUT_DOWN_APPLIANCES" xml:space="preserve">
<value>Are you sure you want to shut down the following vApps?
{0}</value>
</data>
<data name="CONFIRM_SUSPEND_VM" xml:space="preserve">
<value>Are you sure you want to suspend the selected VM?</value>
</data>
<data name="CONFIRM_SUSPEND_VMS" xml:space="preserve">
<value>Are you sure you want to suspend the selected VMs?</value>
</data>
<data name="CONFIRM_SUSPEND_VMS_TITLE" xml:space="preserve">
<value>Suspend Multiple VMs</value>
</data>
<data name="CONFIRM_SUSPEND_VM_TITLE" xml:space="preserve">
<value>Suspend VM</value>
</data>
2014-07-24 10:59:54 +02:00
<data name="CONFIRM_TRIM_SR" xml:space="preserve">
<value>The process of reclaiming space may place significant load on the storage controller, temporarily affecting the storage's performance.
Would you like to carry out the operation at this time?</value>
</data>
<data name="CONFIRM_TRIM_SR_TITLE" xml:space="preserve">
<value>Reclaim freed space</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CONNCET_CONNECTION_FAILURE" xml:space="preserve">
<value>Could not connect to {0}.</value>
</data>
<data name="CONNECT" xml:space="preserve">
<value>&Connect</value>
</data>
<data name="CONNECTED" xml:space="preserve">
<value>Connected</value>
</data>
<data name="CONNECTING" xml:space="preserve">
<value>Connecting...</value>
</data>
<data name="CONNECTING_NOTICE_TEXT" xml:space="preserve">
<value>Connecting to {0} in progress.</value>
</data>
<data name="CONNECTING_NOTICE_TITLE" xml:space="preserve">
<value>Connecting to {0}</value>
</data>
<data name="CONNECTION" xml:space="preserve">
<value>Connection</value>
</data>
<data name="CONNECTION_CLOSED_BY_SERVER" xml:space="preserve">
<value>The server closed the connection immediately.</value>
</data>
<data name="CONNECTION_CLOSED_NOTICE_TEXT" xml:space="preserve">
<value>Connection to {0} closed.</value>
</data>
<data name="CONNECTION_CLOSED_NOTICE_TITLE" xml:space="preserve">
<value>Disconnected from {0}</value>
</data>
<data name="CONNECTION_DESC" xml:space="preserve">
<value>Proxy and timeout options</value>
</data>
<data name="CONNECTION_EXISTS" xml:space="preserve">
<value>Connection Failed: A connection to {0} already exists</value>
</data>
<data name="CONNECTION_EXISTS_NULL" xml:space="preserve">
<value>Connection Failed: You tried to connect to an already connected server</value>
</data>
<data name="CONNECTION_FAILED_TITLE" xml:space="preserve">
<value>Failed to connect to {0}</value>
</data>
<data name="CONNECTION_FINDING_MASTER_DESCRIPTION" xml:space="preserve">
<value>Looking for master for {0} on {1}...</value>
</data>
<data name="CONNECTION_FINDING_MASTER_TITLE" xml:space="preserve">
<value>Looking for master for {0}</value>
</data>
<data name="CONNECTION_GENERAL_TAB_TITLE" xml:space="preserve">
<value>Connection General Properties</value>
</data>
<data name="CONNECTION_IO_EXCEPTION" xml:space="preserve">
<value>Could not contact server</value>
</data>
<data name="CONNECTION_LOST_NOTICE_MASTER_IN_X_SECONDS" xml:space="preserve">
<value>Lost connection to {0}. Will search for a new pool master in {1} seconds.</value>
</data>
<data name="CONNECTION_LOST_NOTICE_TITLE" xml:space="preserve">
<value>Lost connection to {0}</value>
</data>
<data name="CONNECTION_LOST_RECONNECT_IN_X_SECONDS" xml:space="preserve">
<value>Lost connection to {0}. Will reconnect in {1} seconds.</value>
</data>
<data name="CONNECTION_OK_NOTICE_TEXT" xml:space="preserve">
<value>Connection to {0} successful.</value>
</data>
<data name="CONNECTION_OK_NOTICE_TITLE" xml:space="preserve">
<value>Connected to {0}</value>
</data>
<data name="CONNECTION_REDIRECTING" xml:space="preserve">
<value>Connection to {0}: redirecting to the pool master at {1}</value>
</data>
<data name="CONNECTION_REFUSED" xml:space="preserve">
<value>The connection was refused.</value>
</data>
<data name="CONNECTION_REFUSED_TITLE" xml:space="preserve">
<value>Connection Refused</value>
</data>
<data name="CONNECTION_RESTRICTED_MESSAGE" xml:space="preserve">
<value>Connection to Server {0} restricted because a connection already exists to another XE Express Server ({1})</value>
<comment>Message shown when user attempts to connect to a second XE Express host from the UI</comment>
</data>
<data name="CONNECTION_RESTRICTED_MESSAGE_LONG" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Connection to server {0} restricted - a connection to a [Citrix] [XenServer product] Express Edition server ({1}) already exists.
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
You can only connect to a single [Citrix] [XenServer product] Express Edition server at a time. To find out how to upgrade your license, follow the link below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CONNECTION_RESTRICTED_NOTICE_TITLE" xml:space="preserve">
<value>Cannot connect to {0} because of license restriction</value>
<comment>Title of notice shown when connection to a host is restricted by license</comment>
</data>
<data name="CONNECTION_RETRYING_SLAVE" xml:space="preserve">
<value>Connection to {0}: trying to find pool at {1}</value>
</data>
<data name="CONNECTION_WAS_LOST" xml:space="preserve">
<value>The connection to the server was lost</value>
</data>
<data name="CONNECTION_WILL_RETRY_SLAVE" xml:space="preserve">
<value>Connection to {0}: will try to connect to another pool member in {1} seconds</value>
</data>
<data name="CONNECT_NO_XAPI_FAILURE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Could not find [XenServer] running on {0}.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CONNECT_RESOLUTION_FAILURE" xml:space="preserve">
<value>Could not find {0}.</value>
</data>
<data name="CONNECT_TO_SERVER" xml:space="preserve">
<value>Connect to Server</value>
</data>
<data name="CONNECT_TO_SERVER_BLURB" xml:space="preserve">
2016-12-16 19:36:35 +01:00
<value>Enter your user name and password to connect to this server.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CONSOLE" xml:space="preserve">
<value>Console</value>
</data>
<data name="CONSOLE_DESC" xml:space="preserve">
<value>Keyboard shortcuts and scaling options</value>
</data>
<data name="CONSOLE_HOST" xml:space="preserve">
<value>{0} server console</value>
</data>
<data name="CONSOLE_HOST_DEAD" xml:space="preserve">
<value>This server is unavailable.</value>
</data>
2016-07-08 10:19:39 +02:00
<data name="CONSOLE_HOST_NUTANIX" xml:space="preserve">
<value>{0} Nutanix CVM console</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CONSOLE_POWER_STATE_HALTED" xml:space="preserve">
<value>This VM is currently shut down.</value>
</data>
<data name="CONSOLE_POWER_STATE_HALTED_START" xml:space="preserve">
<value>This VM is currently shut down. Click here to start it.</value>
</data>
<data name="CONSOLE_POWER_STATE_PAUSED" xml:space="preserve">
<value>This VM is currently paused.</value>
</data>
<data name="CONSOLE_POWER_STATE_PAUSED_UNPAUSE" xml:space="preserve">
<value>This VM is currently paused. Click here to unpause it.</value>
</data>
<data name="CONSOLE_POWER_STATE_SUSPENDED" xml:space="preserve">
<value>This VM is currently suspended.</value>
</data>
<data name="CONSOLE_POWER_STATE_SUSPENDED_RESUME" xml:space="preserve">
<value>This VM is currently suspended. Click here to resume it.</value>
</data>
<data name="CONTAINED_IN" xml:space="preserve">
<value>contained in</value>
</data>
2015-02-10 04:03:53 +01:00
<data name="CONTAINER" xml:space="preserve">
<value>Container</value>
</data>
<data name="CONTAINER_COMMAND" xml:space="preserve">
<value>Command</value>
</data>
<data name="CONTAINER_CREATED" xml:space="preserve">
<value>Created</value>
</data>
<data name="CONTAINER_GENERAL_TAB_TITLE" xml:space="preserve">
<value>Container General Properties</value>
</data>
2015-03-09 16:32:07 +01:00
<data name="CONTAINER_IMAGE" xml:space="preserve">
<value>Image</value>
</data>
2015-02-24 11:03:10 +01:00
<data name="CONTAINER_ON_VM_TITLE" xml:space="preserve">
<value>{0} on '{1}' {2}</value>
</data>
2015-02-10 04:03:53 +01:00
<data name="CONTAINER_PORTS" xml:space="preserve">
<value>Ports</value>
</data>
2015-03-06 12:43:47 +01:00
<data name="CONTAINER_PORTS_ADDRESS" xml:space="preserve">
<value>Address: {0}</value>
</data>
<data name="CONTAINER_PORTS_PRIVATE_PORT" xml:space="preserve">
<value>Private port: {0}</value>
</data>
<data name="CONTAINER_PORTS_PROTOCOL" xml:space="preserve">
<value>Protocol: {0}</value>
</data>
<data name="CONTAINER_PORTS_PUBLIC_PORT" xml:space="preserve">
<value>Public port: {0}</value>
2015-02-10 04:03:53 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CONTAINS" xml:space="preserve">
<value>contains</value>
</data>
<data name="CONTINUE_WITH_EXPORT" xml:space="preserve">
<value>&Continue with export</value>
</data>
2016-08-01 10:25:10 +02:00
<data name="CONTROL_DOMAIN_MEMORY_DIALOG_TITLE" xml:space="preserve">
<value>Control Domain Memory Settings - {0}</value>
</data>
<data name="CONTROL_DOMAIN_MEMORY_LABEL" xml:space="preserve">
<value>&Control Domain Memory:</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CONTROL_DOM_ON_HOST" xml:space="preserve">
<value>Control domain on host {0}</value>
</data>
<data name="CONVERT" xml:space="preserve">
<value>&Convert</value>
</data>
<data name="CONVERT_TEMPLATE_DIALOG_TEXT" xml:space="preserve">
<value>Are you sure you want to convert VM '{0}' to a template? This cannot be undone.</value>
</data>
<data name="CONVERT_TO_TEMPLATE" xml:space="preserve">
<value>Convert VM to Template</value>
</data>
<data name="COPY" xml:space="preserve">
<value>Copy</value>
</data>
<data name="COPYRIGHT" xml:space="preserve">
<value>Copyright © {0} All rights reserved.</value>
</data>
<data name="COPY_MENU_ITEM" xml:space="preserve">
<value>&Copy</value>
</data>
<data name="COPY_TEMPLATE" xml:space="preserve">
<value>Copy Template</value>
</data>
<data name="COPY_TEMPLATE_FAST_CLONE_DESCRIPTION" xml:space="preserve">
<value>Clone the existing template, using a storage-level fast disk clone operation</value>
</data>
2015-03-31 18:40:05 +02:00
<data name="COPY_TEMPLATE_INTRA_POOL_RUBRIC" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Provide a name and a description (optional) for the new template and then select a copy mode.</value>
2015-03-31 18:40:05 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="COPY_TEMPLATE_REMOVE" xml:space="preserve">
<value>Delete original template after copy</value>
</data>
<data name="COPY_TEMPLATE_SELECT_SR" xml:space="preserve">
<value>Create a full copy of the existing template on this storage repository:</value>
</data>
2015-03-31 18:40:05 +02:00
<data name="COPY_TEMPLATE_WIZARD_TITLE" xml:space="preserve">
<value>Copy Template</value>
</data>
<data name="COPY_TEMPLATE_WIZARD_TITLE_AND_LOCATION" xml:space="preserve">
<value>Copy Template to {0}</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="COPY_TO_SHARED_CANCELLED" xml:space="preserve">
2013-12-13 14:51:16 +01:00
<value>Copying {0} canceled.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="COPY_VM" xml:space="preserve">
<value>Copy Virtual Machine</value>
</data>
<data name="COPY_VM_CLONE_TEMPLATE_SLOW" xml:space="preserve">
<value>Clone</value>
</data>
<data name="COPY_VM_FAST_CLONE_DESCRIPTION" xml:space="preserve">
<value>Clone the existing VM, using a storage-level fast disk clone operation</value>
</data>
2015-03-31 18:40:05 +02:00
<data name="COPY_VM_INTRA_POOL_RUBRIC" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Provide a name and a description (optional) for the new VM and then select a copy mode.</value>
2015-03-31 18:40:05 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="COPY_VM_REMOVE" xml:space="preserve">
<value>Delete original VM after copy</value>
</data>
<data name="COPY_VM_SELECT_SR" xml:space="preserve">
<value>Create a full copy of the existing VM on this storage repository:</value>
</data>
<data name="COPY_VM_SLOW_CLONE_DESCRIPTION" xml:space="preserve">
<value>Clone the existing template</value>
</data>
2016-02-24 11:44:37 +01:00
<data name="COPY_VM_WIZARD_RUBRIC_TEMPLATE" xml:space="preserve">
<value>Select where would you like to copy your template</value>
</data>
<data name="COPY_VM_WIZARD_RUBRIC_VM" xml:space="preserve">
<value>Select where would you like to copy your VM.</value>
</data>
2015-03-17 17:35:12 +01:00
<data name="COPY_VM_WIZARD_TITLE" xml:space="preserve">
<value>Copy VM</value>
</data>
<data name="COPY_VM_WIZARD_TITLE_AND_LOCATION" xml:space="preserve">
<value>Copy VM to {0}</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="COULD_NOT_OPEN_URL" xml:space="preserve">
<value>Could not open URL '{0}'</value>
</data>
<data name="COULD_NOT_WRITE_FILE" xml:space="preserve">
<value>Could not write to file '{0}'.
{1}</value>
</data>
<data name="COUNTS_PER_SEC_UNIT" xml:space="preserve">
2014-06-02 11:09:47 +02:00
<value>/sec</value>
2013-06-24 13:41:48 +02:00
</data>
2016-10-27 17:03:16 +02:00
<data name="CPM_FAILURE_REASON_HARDWARE_PLATFORM" xml:space="preserve">
<value>incompatible hardware platform version</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CPM_FAILURE_REASON_VERSION" xml:space="preserve">
<value>incompatible version numbers</value>
</data>
<data name="CPM_SUMMARY_AUTO_DELETE_FALSE" xml:space="preserve">
<value>Do not automatically delete source virtual disks</value>
</data>
<data name="CPM_SUMMARY_AUTO_DELETE_TRUE" xml:space="preserve">
<value>Automatically delete source virtual disks</value>
</data>
<data name="CPM_SUMMARY_KEY_DESTINATION" xml:space="preserve">
<value>Destination:</value>
</data>
2016-02-24 11:44:37 +01:00
<data name="CPM_SUMMARY_KEY_MIGRATE_TEMPLATE" xml:space="preserve">
<value>Template:</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CPM_SUMMARY_KEY_MIGRATE_VM" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>VM:</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_SUMMARY_KEY_NETWORK" xml:space="preserve">
<value>Networking:</value>
</data>
<data name="CPM_SUMMARY_KEY_STORAGE" xml:space="preserve">
<value>Storage:</value>
</data>
2016-08-15 15:22:18 +02:00
<data name="CPM_SUMMARY_KEY_TARGET_SERVER" xml:space="preserve">
<value>Target Server:</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CPM_SUMMARY_KEY_TRANSFER_NETWORK" xml:space="preserve">
2015-04-22 14:21:31 +02:00
<value>Migration Network:</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_SUMMARY_NETWORK_NOT_FOUND" xml:space="preserve">
<value>Network not found</value>
</data>
<data name="CPM_SUMMARY_UNSET" xml:space="preserve">
<value>Unset</value>
</data>
<data name="CPM_WIZARD_ALL_ON_SAME_SR_RADIO" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Pl&ace all virtual disks on the same SR:</value>
2013-06-24 13:41:48 +02:00
</data>
2015-03-31 16:13:46 +02:00
<data name="CPM_WIZARD_COPY_MODE_TAB_TITLE" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Destination</value>
2015-03-31 16:13:46 +02:00
</data>
<data name="CPM_WIZARD_COPY_MODE_TITLE" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Destination</value>
2015-03-31 16:13:46 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CPM_WIZARD_DESTINATION_DESTINATION" xml:space="preserve">
<value>&Destination:</value>
</data>
2015-04-21 15:30:41 +02:00
<data name="CPM_WIZARD_DESTINATION_INSTRUCTIONS_COPY" xml:space="preserve">
<value>Select the pool or standalone server where you want to copy the selected VMs to.</value>
</data>
<data name="CPM_WIZARD_DESTINATION_INSTRUCTIONS_COPY_SINGLE" xml:space="preserve">
<value>Select the pool or standalone server where you want to copy the selected VM to.</value>
</data>
2016-02-24 11:44:37 +01:00
<data name="CPM_WIZARD_DESTINATION_INSTRUCTIONS_COPY_TEMPLATE" xml:space="preserve">
<value>Select the pool or standalone server where you want to copy the selected templates to.</value>
</data>
2016-09-30 12:53:48 +02:00
<data name="CPM_WIZARD_DESTINATION_INSTRUCTIONS_COPY_TEMPLATE_SINGLE" xml:space="preserve">
<value>Select the pool or standalone server where you want to copy the selected template to.</value>
</data>
<data name="CPM_WIZARD_DESTINATION_INSTRUCTIONS_MIGRATE" xml:space="preserve">
<value>Select the pool or standalone server where you want to migrate the selected VMs to.</value>
</data>
<data name="CPM_WIZARD_DESTINATION_INSTRUCTIONS_MIGRATE_SINGLE" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Select the pool or standalone server where you want to migrate the selected VM to.</value>
2013-06-24 13:41:48 +02:00
</data>
2016-09-30 12:53:48 +02:00
<data name="CPM_WIZARD_DESTINATION_INSTRUCTIONS_MOVE" xml:space="preserve">
<value>Select the pool or standalone server where you want to move the selected VMs to.</value>
</data>
<data name="CPM_WIZARD_DESTINATION_INSTRUCTIONS_MOVE_SINGLE" xml:space="preserve">
<value>Select the pool or standalone server where you want to move the selected VM to.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CPM_WIZARD_DESTINATION_TABLE_INTRO" xml:space="preserve">
2016-08-15 15:22:18 +02:00
<value>Specify a &target server in the destination pool (optional):</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_WIZARD_DESTINATION_TAB_TITLE" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Destination Pool</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_WIZARD_DESTINATION_TITLE" xml:space="preserve">
<value>Select the destination pool or standalone server</value>
</data>
<data name="CPM_WIZARD_ERROR_TARGET_DISCONNECTED" xml:space="preserve">
<value>The destination host has become unreachable.
Please reconnect the host and try again.</value>
</data>
2015-04-21 15:30:41 +02:00
<data name="CPM_WIZARD_FINISH_PAGE_INTRO" xml:space="preserve">
2015-04-22 14:21:31 +02:00
<value>The wizard is ready to begin migrating the selected VMs using the settings shown below. Please review these settings and click Previous if you need to go back and make any changes, otherwise click Finish to migrate the VMs.</value>
2015-04-21 15:30:41 +02:00
</data>
<data name="CPM_WIZARD_FINISH_PAGE_INTRO_COPY" xml:space="preserve">
2015-04-22 14:21:31 +02:00
<value>The wizard is ready to begin copying the selected VMs using the settings shown below. Please review these settings and click Previous if you need to go back and make any changes, otherwise click Finish to copy the VMs.</value>
2015-04-21 15:30:41 +02:00
</data>
<data name="CPM_WIZARD_FINISH_PAGE_INTRO_COPY_SINGLE" xml:space="preserve">
2015-04-22 14:21:31 +02:00
<value>The wizard is ready to begin copying the selected VM using the settings shown below. Please review these settings and click Previous if you need to go back and make any changes, otherwise click Finish to copy the VM.</value>
2015-04-21 15:30:41 +02:00
</data>
2016-02-24 11:44:37 +01:00
<data name="CPM_WIZARD_FINISH_PAGE_INTRO_COPY_SINGLE_TEMPLATE" xml:space="preserve">
<value>The wizard is ready to begin copying the selected template using the settings shown below. Please review these settings and click Previous if you need to go back and make any changes, otherwise click Finish to copy the template.</value>
</data>
<data name="CPM_WIZARD_FINISH_PAGE_INTRO_COPY_TEMPLATE" xml:space="preserve">
<value>The wizard is ready to begin copying the selected templates using the settings shown below. Please review these settings and click Previous if you need to go back and make any changes, otherwise click Finish to copy the templates.</value>
</data>
2015-04-21 15:30:41 +02:00
<data name="CPM_WIZARD_FINISH_PAGE_INTRO_SINGLE" xml:space="preserve">
2015-04-22 14:21:31 +02:00
<value>The wizard is ready to begin migrating the selected VM using the settings shown below. Please review these settings and click Previous if you need to go back and make any changes, otherwise click Finish to migrate the VM.</value>
2015-04-21 15:30:41 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CPM_WIZARD_FINISH_PAGE_TITLE" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Review settings</value>
2013-06-24 13:41:48 +02:00
</data>
2015-03-31 18:40:05 +02:00
<data name="CPM_WIZARD_INTRA_POOL_COPY_TAB_TITLE" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Name and Storage</value>
2015-03-31 18:40:05 +02:00
</data>
<data name="CPM_WIZARD_INTRA_POOL_COPY_TITLE" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Name and Storage</value>
2015-03-31 18:40:05 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CPM_WIZARD_NETWORKING_INTRO" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Map the virtual network interfaces in the selected VMs to networks in the destination pool or standalone server.</value>
</data>
<data name="CPM_WIZARD_NETWORKING_INTRO_SINGLE" xml:space="preserve">
2015-04-22 14:21:31 +02:00
<value>Map the virtual network interfaces in the selected VM to networks in the destination pool or standalone server.</value>
2013-06-24 13:41:48 +02:00
</data>
2016-02-24 11:44:37 +01:00
<data name="CPM_WIZARD_NETWORKING_INTRO_TEMPLATE" xml:space="preserve">
<value>Map the virtual network interfaces in the selected templates to networks in the destination pool or standalone server.</value>
</data>
<data name="CPM_WIZARD_NETWORKING_INTRO_TEMPLATE_SINGLE" xml:space="preserve">
<value>Map the virtual network interfaces in the selected template to networks in the destination pool or standalone server.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CPM_WIZARD_SELECT_NETWORK_PAGE_TEXT" xml:space="preserve">
<value>Networking</value>
</data>
<data name="CPM_WIZARD_SELECT_NETWORK_PAGE_TITLE" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Configure networking</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_WIZARD_SELECT_STORAGE_PAGE_TEXT" xml:space="preserve">
<value>Storage</value>
</data>
<data name="CPM_WIZARD_SELECT_STORAGE_PAGE_TITLE" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Configure storage</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_WIZARD_SELECT_TRANSFER_NETWORK_PAGE_TEXT" xml:space="preserve">
2015-04-22 14:21:31 +02:00
<value>Migration Network</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_WIZARD_SELECT_TRANSFER_NETWORK_TITLE" xml:space="preserve">
2015-04-22 14:21:31 +02:00
<value>Configure storage migration settings</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_WIZARD_SPECIFIC_SR_RADIO" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>Pla&ce virtual disks onto specified SRs:</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_WIZARD_STORAGE_INSTRUCTIONS" xml:space="preserve">
2013-11-14 13:29:30 +01:00
<value>Select one or more storage repositories (SR) in the destination pool or standalone server.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_WIZARD_TITLE" xml:space="preserve">
<value>Migrate VM</value>
</data>
<data name="CPM_WIZARD_TITLE_AND_LOCATION" xml:space="preserve">
<value>Migrate VM to {0}</value>
</data>
<data name="CPM_WIZARD_VM_MISSING_ERROR" xml:space="preserve">
2013-12-19 15:30:38 +01:00
<value>The selected VMs are no longer available for migration. Please verify your selection is valid and relaunch the wizard.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_WIZARD_VM_SELECTION_INTRODUCTION" xml:space="preserve">
2015-04-21 15:30:41 +02:00
<value>&Virtual network interfaces:</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPM_WLB_ENABLED_ON_HOST_FAILURE_REASON" xml:space="preserve">
<value>WLB is enabled on the host</value>
</data>
<data name="CPM_WLB_ENABLED_ON_VM_FAILURE_REASON" xml:space="preserve">
<value>WLB is enabled on the source</value>
</data>
2016-02-24 11:44:37 +01:00
<data name="CPS_WIZARD_MIGRATION_PAGE_TITLE_TEMPLATE" xml:space="preserve">
<value>Select a storage network on the destination pool or standalone server that will be used for the live migration of the virtual disks.
For optimal performance and reliability during template migration, ensure that the network used for the storage migration is not being used for management or virtual machine traffic.</value>
</data>
<data name="CPS_WIZARD_MIGRATION_PAGE_TITLE_VM" xml:space="preserve">
<value>Select a storage network on the destination pool or standalone server that will be used for the live migration of the virtual disks.
For optimal performance and reliability during VM migration, ensure that the network used for the storage migration is not being used for management or virtual machine traffic.</value>
</data>
<data name="CPS_WIZARD_NETWORKING_NETWORK_COLUMN_TEMPLATE" xml:space="preserve">
<value>Template - Virtual Network Interface</value>
</data>
<data name="CPS_WIZARD_NETWORKING_NETWORK_COLUMN_VM" xml:space="preserve">
<value>VM - Virtual Network Interface</value>
</data>
<data name="CPS_WIZARD_STORAGE_PAGE_DISK_COLUMN_HEADER_FOR_TEMPLATE" xml:space="preserve">
<value>Template - Virtual Disk</value>
</data>
<data name="CPS_WIZARD_STORAGE_PAGE_DISK_COLUMN_HEADER_FOR_VM" xml:space="preserve">
<value>VM - Virtual Disk</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CPU" xml:space="preserve">
<value>CPU</value>
</data>
<data name="CPU_AND_MEMORY" xml:space="preserve">
<value>CPU and Memory</value>
</data>
<data name="CPU_AND_MEMORY_SUB" xml:space="preserve">
2013-11-14 12:58:43 +01:00
<value>{0} vCPU(s) & {1} MB RAM</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CPU_SUB" xml:space="preserve">
2013-11-14 12:58:43 +01:00
<value>{0} vCPU(s)</value>
2013-06-24 13:41:48 +02:00
</data>
2016-02-12 18:01:05 +01:00
<data name="CPU_TOPOLOGY_INVALID_REASON_MULTIPLE" xml:space="preserve">
<value>The number of vCPUs must be a multiple of the number of cores per socket</value>
</data>
<data name="CPU_TOPOLOGY_INVALID_REASON_SOCKETS" xml:space="preserve">
<value>The number of sockets must be at most 16</value>
</data>
2014-06-05 14:00:14 +02:00
<data name="CPU_TOPOLOGY_STRING_1_SOCKET_1_CORE" xml:space="preserve">
<value>1 socket with 1 core per socket</value>
</data>
<data name="CPU_TOPOLOGY_STRING_1_SOCKET_N_CORE" xml:space="preserve">
<value>1 socket with {0} cores per socket</value>
</data>
<data name="CPU_TOPOLOGY_STRING_INVALID_VALUE" xml:space="preserve">
<value>{0} cores per socket (Invalid configuration)</value>
</data>
2016-02-12 18:01:05 +01:00
<data name="CPU_TOPOLOGY_STRING_INVALID_VALUE_1" xml:space="preserve">
<value>1 core per socket (Invalid configuration)</value>
</data>
2014-06-05 14:00:14 +02:00
<data name="CPU_TOPOLOGY_STRING_N_SOCKET_1_CORE" xml:space="preserve">
<value>{0} sockets with 1 core per socket</value>
</data>
<data name="CPU_TOPOLOGY_STRING_N_SOCKET_N_CORE" xml:space="preserve">
<value>{0} sockets with {1} cores per socket</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CREATEDVM_CLONE" xml:space="preserve">
<value>Created '{0}' by cloning '{1}'</value>
</data>
<data name="CREATEDVM_COPY" xml:space="preserve">
<value>Created '{0}' by copying '{1}'</value>
</data>
<data name="CREATED_NEW_FOLDER" xml:space="preserve">
<value>Created new folder</value>
</data>
<data name="CREATED_NEW_FOLDERS" xml:space="preserve">
<value>Created new folders</value>
</data>
<data name="CREATED_VMPP" xml:space="preserve">
<value>VM protection policy '{0}' created.</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="CREATED_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Snapshot schedule '{0}' created.</value>
2016-01-29 12:34:44 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CREATED_VM_APPLIANCE" xml:space="preserve">
<value>vApp '{0}' created.</value>
</data>
<data name="CREATEVM_CANCELLED" xml:space="preserve">
<value>VM creation canceled</value>
</data>
<data name="CREATEVM_CD" xml:space="preserve">
<value>Configuring CD drive for {0}</value>
</data>
<data name="CREATEVM_CLONE" xml:space="preserve">
<value>Creating '{0}' by cloning '{1}'</value>
</data>
<data name="CREATEVM_COPY" xml:space="preserve">
<value>Creating '{0}' by copying '{1}'</value>
</data>
<data name="CREATEVM_DISKS" xml:space="preserve">
<value>Configuring disks for {0}</value>
</data>
<data name="CREATEVM_NETWORK" xml:space="preserve">
<value>Configuring network interfaces for {0}</value>
</data>
<data name="CREATEVM_PROVISIONING" xml:space="preserve">
<value>Provisioning new storage for {0}</value>
</data>
<data name="CREATE_CD_DRIVE" xml:space="preserve">
<value>Creating CD drive</value>
</data>
<data name="CREATE_MNEMONIC_R" xml:space="preserve">
<value>C&reate</value>
</data>
<data name="CREATE_NEW_FOLDER" xml:space="preserve">
<value>Create new folder '{0}'</value>
</data>
<data name="CREATE_NEW_FOLDERS" xml:space="preserve">
<value>Create new folders '{0}'</value>
</data>
<data name="CREATE_POLICY" xml:space="preserve">
<value>Create policy</value>
</data>
<data name="CREATE_TEMPLATE_FROM_SNAPSHOT_MENU_ITEM" xml:space="preserve">
<value>&Create Template From Snapshot...</value>
</data>
<data name="CREATE_VM" xml:space="preserve">
<value>Create VM '{0}'</value>
</data>
<data name="CREATE_VM_APPLIANCE" xml:space="preserve">
<value>Create vApp</value>
</data>
<data name="CREATE_VM_FROM_TEMPLATE" xml:space="preserve">
<value>Creating VM '{0}' from template '{1}'</value>
</data>
2015-02-19 15:48:52 +01:00
<data name="CREATING_CLOUD_CONFIG_DRIVE" xml:space="preserve">
<value>Creating cloud config drive</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CREATING_DISKS" xml:space="preserve">
<value>Creating disks</value>
</data>
<data name="CREATING_FILE" xml:space="preserve">
<value>Archiving appliance files into single package file {0}...</value>
</data>
<data name="CREATING_MANIFEST" xml:space="preserve">
<value>Creating manifest file...</value>
</data>
<data name="CREATING_NAMED_POOL_WITH_MASTER" xml:space="preserve">
<value>Creating new pool '{0}' with master '{1}'</value>
</data>
<data name="CREATING_NEW_FOLDER" xml:space="preserve">
<value>Creating new folder...</value>
</data>
<data name="CREATING_NEW_FOLDERS" xml:space="preserve">
<value>Creating new folders...</value>
</data>
<data name="CREATING_VMPP" xml:space="preserve">
<value>Creating VM protection policy '{0}'...</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="CREATING_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Creating snapshot schedule '{0}'...</value>
2016-01-29 12:34:44 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="CREATING_VM_APPLIANCE" xml:space="preserve">
<value>Creating vApp '{0}'...</value>
</data>
<data name="CREATION_TIME" xml:space="preserve">
<value>Creation time</value>
</data>
<data name="CREDENTIALS_CHECKING" xml:space="preserve">
2016-12-16 19:36:35 +01:00
<value>Checking user name and password...</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CREDENTIALS_CHECK_COMPLETE" xml:space="preserve">
2016-12-16 19:36:35 +01:00
<value>User name and password check complete</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="CSLG_DELL_DIRECT" xml:space="preserve">
<value>Dell EqualLogic</value>
</data>
<data name="CSLG_DIRECT_CONNECTION" xml:space="preserve">
<value>Direct Connection</value>
</data>
<data name="CSLG_NETAPP_DIRECT" xml:space="preserve">
<value>NetApp</value>
</data>
<data name="CSLG_STORAGEADAPTER" xml:space="preserve">
<value>&Storage adapter:</value>
</data>
<data name="CSLG_STORAGELINK_ADAPTERS" xml:space="preserve">
<value>StorageLink adapters</value>
</data>
<data name="CSLG_STORAGELINK_SERVER" xml:space="preserve">
<value>StorageLink Server ({0})</value>
</data>
<data name="CSV_DESCRIPTION" xml:space="preserve">
<value>Comma Separated Value</value>
</data>
<data name="CURRENT" xml:space="preserve">
<value>Current</value>
</data>
<data name="CURRENT_LOCATION" xml:space="preserve">
<value>Current location</value>
</data>
<data name="CURRENT_MEMORY_USAGE" xml:space="preserve">
<value>Current memory usage: {0}</value>
</data>
<data name="CURRENT_MEMORY_USAGE_MULTIPLE" xml:space="preserve">
<value>Current memory usage: {0} per VM</value>
</data>
<data name="CURRENT_POLICY" xml:space="preserve">
<value>Current policy</value>
</data>
2016-02-19 06:49:24 +01:00
<data name="CURRENT_SCHEDULE" xml:space="preserve">
<value>Current schedule</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="CURRENT_VAPP" xml:space="preserve">
<value>Current vApp</value>
</data>
<data name="CUSTOM" xml:space="preserve">
<value>Custom...</value>
</data>
<data name="CUSTOM_FIELDS" xml:space="preserve">
<value>Custom Fields</value>
</data>
<data name="CUSTOM_FIELD_NAME_AND_TYPE" xml:space="preserve">
<value>{0} ({1})</value>
</data>
<data name="CUSTOM_SEARCH" xml:space="preserve">
<value>Custom Search</value>
</data>
<data name="CUSTOM_TEMPLATES" xml:space="preserve">
<value>Custom Templates</value>
</data>
<data name="DAILY_SCHEDULE_FORMAT" xml:space="preserve">
<value>Daily; at {0}</value>
</data>
<data name="DATATYPE_CPU" xml:space="preserve">
<value>CPU</value>
</data>
<data name="DATATYPE_CUSTOM" xml:space="preserve">
<value>Custom</value>
</data>
<data name="DATATYPE_DISK" xml:space="preserve">
<value>Disk</value>
</data>
2013-11-14 12:33:59 +01:00
<data name="DATATYPE_GPU" xml:space="preserve">
<value>GPU</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="DATATYPE_LATENCY" xml:space="preserve">
<value>Latency</value>
</data>
<data name="DATATYPE_LOADAVERAGE" xml:space="preserve">
<value>Load Average</value>
</data>
<data name="DATATYPE_MEMORY" xml:space="preserve">
<value>Memory</value>
</data>
<data name="DATATYPE_NETWORK" xml:space="preserve">
<value>Network</value>
</data>
2016-10-11 14:13:50 +02:00
<data name="DATATYPE_PVS" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>PVS-Accelerator</value>
2016-10-11 14:13:50 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="DATATYPE_STORAGE" xml:space="preserve">
<value>Storage</value>
</data>
<data name="DATE" xml:space="preserve">
<value>Date</value>
</data>
<data name="DATEFORMAT_DM" xml:space="preserve">
<value>MMM d</value>
</data>
<data name="DATEFORMAT_DMY" xml:space="preserve">
<value>MMM d, yyyy</value>
</data>
<data name="DATEFORMAT_DMY_HM" xml:space="preserve">
<value>MMM d, yyyy h:mm tt</value>
</data>
<data name="DATEFORMAT_DMY_HMS" xml:space="preserve">
<value>MMM d, yyyy h:mm:ss tt</value>
</data>
<data name="DATEFORMAT_DMY_LONG" xml:space="preserve">
<value>MMMM d, yyyy</value>
</data>
<data name="DATEFORMAT_HM" xml:space="preserve">
<value>h:mm tt</value>
</data>
<data name="DATEFORMAT_HMS" xml:space="preserve">
<value>h:mm:ss tt</value>
</data>
<data name="DATEFORMAT_H_SHORT" xml:space="preserve">
<value>ht</value>
</data>
<data name="DATEFORMAT_WDMY_HM_LONG" xml:space="preserve">
<value>dddd, MMMM d, yyyy h:mm tt</value>
</data>
<data name="DATE_AND_TIME" xml:space="preserve">
<value>Date & Time</value>
</data>
2013-07-02 18:36:02 +02:00
<data name="DATE_FILTER_CUSTOM" xml:space="preserve">
<value>&Custom...</value>
</data>
<data name="DATE_FILTER_LAST_24_HOURS" xml:space="preserve">
<value>Last &24 Hours</value>
</data>
<data name="DATE_FILTER_LAST_30_DAYS" xml:space="preserve">
<value>Last 3&0 Days</value>
</data>
<data name="DATE_FILTER_LAST_3_DAYS" xml:space="preserve">
<value>Last &3 Days</value>
</data>
<data name="DATE_FILTER_LAST_7_DAYS" xml:space="preserve">
<value>Last &7 Days</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="DEACTIVATE" xml:space="preserve">
<value>Dea&ctivate</value>
</data>
<data name="DEBIAN_ETCH_40" xml:space="preserve">
<value>Debian Etch 4.0</value>
</data>
<data name="DEBIAN_SARGE_31" xml:space="preserve">
<value>Debian Sarge 3.1</value>
</data>
<data name="DECONFIGURING_WLB" xml:space="preserve">
<value>Disconnecting Workload Balancing.</value>
</data>
<data name="DECONFIGURING_WLB_ON" xml:space="preserve">
<value>Disconnecting Workload Balancing from pool '{0}'.</value>
</data>
<data name="DEFAULT" xml:space="preserve">
<value>Default</value>
</data>
<data name="DEFAULT_INSTALL_OF_XENSERVER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Default install of [XenServer]</value>
2013-06-24 13:41:48 +02:00
</data>
2013-09-24 16:47:38 +02:00
<data name="DEFAULT_SEARCH" xml:space="preserve">
<value>Default Search</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="DEFAULT_SEARCH_OBJECTS_BY_TAG" xml:space="preserve">
<value>Resources by Tag</value>
</data>
<data name="DEFAULT_SEARCH_SNAPSHOTS_BY_VM" xml:space="preserve">
<value>VMs and Snapshots</value>
</data>
<data name="DEFAULT_SEARCH_VMS_BY_APPLIANCE" xml:space="preserve">
<value>VMs by vApp</value>
</data>
<data name="DEFAULT_SEARCH_VMS_BY_NETWORK" xml:space="preserve">
<value>VMs by Network</value>
</data>
<data name="DEFAULT_SEARCH_VMS_BY_OS" xml:space="preserve">
<value>VMs by Operating System</value>
</data>
<data name="DEFAULT_SEARCH_VMS_BY_POWERSTATE" xml:space="preserve">
<value>VMs by Power State</value>
</data>
<data name="DEFAULT_SEARCH_VMS_WO_XS_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>VMs without [XenServer product] Tools</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DEFAULT_VDI_NAME" xml:space="preserve">
<value>New virtual disk</value>
</data>
<data name="DELAY_LOADED_COMBO_BOX_ITEM_FAILURE_REASON" xml:space="preserve">
<value>{0} - {1}</value>
</data>
<data name="DELAY_LOADED_COMBO_BOX_ITEM_FAILURE_UNKOWN" xml:space="preserve">
<value>unable to determine failure reason</value>
</data>
<data name="DELAY_LOADING_COMBO_BOX_WAITING" xml:space="preserve">
<value>waiting...</value>
</data>
<data name="DELETED_ALL_TAG" xml:space="preserve">
<value>Deleted tag '{0}'</value>
</data>
<data name="DELETED_CUSTOM_FIELD" xml:space="preserve">
<value>Deleted custom field '{0}'</value>
</data>
<data name="DELETED_FOLDER" xml:space="preserve">
<value>Deleted object</value>
</data>
<data name="DELETED_FOLDERS" xml:space="preserve">
<value>Deleted objects</value>
</data>
<data name="DELETED_TAG" xml:space="preserve">
<value>Deleted tag '{0}'</value>
</data>
<data name="DELETED_TAGS" xml:space="preserve">
<value>Deleted tags</value>
</data>
<data name="DELETED_VMPP" xml:space="preserve">
<value>VM protection policies deleted.</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="DELETED_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Snapshot schedules deleted.</value>
2016-01-29 12:34:44 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="DELETED_VM_APPLIANCES" xml:space="preserve">
<value>vApps deleted.</value>
</data>
<data name="DELETE_ALL_BUTTON_LABEL" xml:space="preserve">
<value>&Delete All</value>
</data>
<data name="DELETE_ALL_TAG" xml:space="preserve">
<value>Delete tag '{0}'</value>
</data>
<data name="DELETE_ANY_MESSAGE_RBAC_BLOCKED" xml:space="preserve">
<value>For every server that currently has system alerts your current role is not privileged enough to dismiss them.</value>
</data>
<data name="DELETE_BOND" xml:space="preserve">
<value>Delete Bond</value>
</data>
<data name="DELETE_BOND_MESSAGE" xml:space="preserve">
<value>Are you sure that you want to delete {0}?</value>
</data>
<data name="DELETE_BOND_WITH_VIFS_MESSAGE" xml:space="preserve">
<value>Are you sure that you want to delete {0}? This network is in use by virtual machines,
and so will be renamed '{1}'.</value>
</data>
<data name="DELETE_CUSTOM_FIELD" xml:space="preserve">
<value>Delete custom field '{0}'</value>
</data>
<data name="DELETE_FOLDERS_CONFIRM_CONTENTS" xml:space="preserve">
<value>Are you sure you want to permanently delete the selected folders?
If you do, contained resources will no longer be in any folder.</value>
</data>
<data name="DELETE_FOLDERS_CONFIRM_CONTENTS_AND_SUBFOLDERS" xml:space="preserve">
<value>Are you sure you want to permanently delete the selected folders?
This will also delete all subfolders, and any contained resources will no longer be in any folder.</value>
</data>
<data name="DELETE_FOLDERS_CONFIRM_EMPTY" xml:space="preserve">
<value>Are you sure you want to permanently delete the selected folders?</value>
</data>
<data name="DELETE_FOLDERS_CONFIRM_SUBFOLDERS" xml:space="preserve">
<value>Are you sure you want to permanently delete the selected folders?
This will also delete subfolders.</value>
</data>
<data name="DELETE_FOLDERS_DIALOG_TITLE" xml:space="preserve">
<value>Delete Folders</value>
</data>
<data name="DELETE_FOLDER_CONFIRM_CONTENTS" xml:space="preserve">
<value>Are you sure you want to permanently delete folder '{0}'?
If you do, the resources inside it will no longer be in any folder.</value>
</data>
<data name="DELETE_FOLDER_CONFIRM_CONTENTS_AND_SUBFOLDERS" xml:space="preserve">
<value>Are you sure you want to permanently delete folder '{0}'?
This will also delete its subfolders, and the resources inside it will no longer be in any folder.</value>
</data>
<data name="DELETE_FOLDER_CONFIRM_EMPTY" xml:space="preserve">
<value>Are you sure you want to permanently delete folder '{0}'?</value>
</data>
<data name="DELETE_FOLDER_CONFIRM_SUBFOLDERS" xml:space="preserve">
<value>Are you sure you want to permanently delete folder '{0}'?
This will also delete its subfolders.</value>
</data>
<data name="DELETE_FOLDER_DIALOG_TITLE" xml:space="preserve">
<value>Delete Folder</value>
</data>
<data name="DELETE_FOLDER_MENU" xml:space="preserve">
<value>&Delete Folder...</value>
</data>
<data name="DELETE_GRAPH_MESSAGE" xml:space="preserve">
<value>Are you sure you want to delete '{0}'? This operation cannot be undone.</value>
</data>
<data name="DELETE_MESSAGE_RBAC_BLOCKED" xml:space="preserve">
<value>There are no alerts remaining which you have permission to dismiss.</value>
</data>
<data name="DELETE_PATCH" xml:space="preserve">
<value>Delete Patch</value>
</data>
<data name="DELETE_POLICIES" xml:space="preserve">
<value>Delete policies</value>
</data>
<data name="DELETE_SEARCH" xml:space="preserve">
<value>Delete Search '{0}'</value>
</data>
2013-08-01 12:46:10 +02:00
<data name="DELETE_SEARCH_MENU_ITEM" xml:space="preserve">
<value>&Delete</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="DELETE_SEARCH_PROMPT" xml:space="preserve">
2013-08-01 12:46:10 +02:00
<value>Are you sure you want to delete saved search '{0}'?</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DELETE_SL_VOLUME_CONTEXT_MENU_ELIPS" xml:space="preserve">
<value>Remove &StorageLink volume...</value>
</data>
<data name="DELETE_SNAPSHOT_MENU_ITEM" xml:space="preserve">
<value>&Delete Snapshot</value>
</data>
<data name="DELETE_TAG" xml:space="preserve">
<value>Delete tag '{0}'</value>
</data>
<data name="DELETE_TAGS" xml:space="preserve">
<value>Delete tags</value>
</data>
<data name="DELETE_VIRTUAL_DISK" xml:space="preserve">
<value>&Delete Virtual Disk</value>
</data>
<data name="DELETE_VM_APPLIANCES" xml:space="preserve">
<value>Delete vApps</value>
</data>
<data name="DELETE_VM_APPLIANCE_TITLE" xml:space="preserve">
<value>Delete vApp</value>
</data>
<data name="DELETE_VM_PROTECTION_TITLE" xml:space="preserve">
<value>Delete VM Protection Policy</value>
</data>
2016-06-03 07:19:41 +02:00
<data name="DELETE_WLB_OPTIMIZATION_SCHEDULE_CAPTION" xml:space="preserve">
<value>Delete WLB Optimization Scheduler</value>
</data>
<data name="DELETE_WLB_OPTIMIZATION_SCHEDULE_WARNING" xml:space="preserve">
<value>This will delete the selected scheduler. Continue?</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="DELETING_ALL_TAG" xml:space="preserve">
<value>Deleting tag '{0}'</value>
</data>
<data name="DELETING_CUSTOM_FIELD" xml:space="preserve">
<value>Deleting custom field '{0}'</value>
</data>
<data name="DELETING_FOLDER" xml:space="preserve">
<value>Deleting object...</value>
</data>
<data name="DELETING_FOLDERS" xml:space="preserve">
<value>Deleting objects...</value>
</data>
<data name="DELETING_SEARCH" xml:space="preserve">
<value>Deleting search '{0}'...</value>
</data>
<data name="DELETING_TAG" xml:space="preserve">
<value>Deleting tag '{0}'</value>
</data>
<data name="DELETING_TAGS" xml:space="preserve">
<value>Deleting tags</value>
</data>
<data name="DELETING_VMPP" xml:space="preserve">
<value>Deleting VM protection policy '{0}'</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="DELETING_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Deleting snapshot schedule '{0}'</value>
2016-01-29 12:34:44 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="DELETING_VM_APPLIANCE" xml:space="preserve">
<value>Deleting vApp '{0}'</value>
</data>
<data name="DESCRIPTION" xml:space="preserve">
<value>Description</value>
</data>
<data name="DESTROYING_HOSTS_END_DESC" xml:space="preserve">
<value>Destroyed</value>
</data>
<data name="DESTROYING_HOSTS_START_DESC" xml:space="preserve">
<value>Destroying</value>
</data>
<data name="DESTROYING_HOSTS_TITLE" xml:space="preserve">
<value>Destroying servers</value>
</data>
<data name="DESTROYING_POOL" xml:space="preserve">
2014-05-15 19:47:13 +02:00
<value>Making pool '{0}' into standalone server</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DESTROY_HOST_ACTION_COMPLETED_DESC" xml:space="preserve">
<value>Host destroyed</value>
</data>
<data name="DESTROY_HOST_ACTION_COMPLETED_SRS_NOT_REMOVED_DESC" xml:space="preserve">
<value>Host destroyed, but could not remove its SRs</value>
</data>
<data name="DESTROY_HOST_ACTION_DESC" xml:space="preserve">
<value>Destroying host</value>
</data>
<data name="DESTROY_HOST_ACTION_REMOVE_SRS_DESC" xml:space="preserve">
<value>Removing SRs</value>
</data>
<data name="DESTROY_HOST_ACTION_TITLE" xml:space="preserve">
<value>Destroying host '{0}'</value>
</data>
<data name="DESTROY_HOST_CONTEXT_MENU_ITEM_TEXT" xml:space="preserve">
<value>D&estroy</value>
</data>
<data name="DESTROY_SR" xml:space="preserve">
<value>Destr&oy</value>
</data>
<data name="DETACHED" xml:space="preserve">
<value>Detached</value>
</data>
<data name="DETACHED_BRACKETS" xml:space="preserve">
<value>{0} (Detached)</value>
</data>
<data name="DETACHED_ISCI_DETECTED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] has detected that an SR already exists on this LUN. This SR is not currently in use by '{0}', would you like to attach it?</value>
2013-06-24 13:41:48 +02:00
</data>
2016-09-06 15:53:46 +02:00
<data name="DETACH_ALL_BUTTON_LABEL" xml:space="preserve">
<value>&Detach all</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="DETACH_SR" xml:space="preserve">
<value>&Detach</value>
</data>
<data name="DETAILS" xml:space="preserve">
<value>Details</value>
</data>
<data name="DEVICE_NAME" xml:space="preserve">
<value>Device</value>
</data>
<data name="DEVICE_POSITION" xml:space="preserve">
<value>Device {0}, ({1})</value>
</data>
<data name="DEVICE_POSITION_CONFLICT" xml:space="preserve">
<value>Position {0} is already in use. Your VM will not boot with two disks in the same position. Do you want to swap the disk at '{0}' with this disk?</value>
</data>
<data name="DEVICE_POSITION_IN_USE" xml:space="preserve">
<value>The selected device position is currently in use.</value>
</data>
<data name="DEVICE_POSITION_RESTART_REQUIRED" xml:space="preserve">
<value>You will have to restart the VM for changes in device position to take effect.</value>
</data>
<data name="DEVICE_POSITION_SCANNED" xml:space="preserve">
<value>Scanned for free device positions</value>
</data>
<data name="DEVICE_POSITION_SCANNING" xml:space="preserve">
<value>Scanning for free device positions</value>
</data>
<data name="DISABLE" xml:space="preserve">
<value>Disa&ble</value>
</data>
<data name="DISABLED" xml:space="preserve">
<value>Disabled</value>
</data>
2015-07-29 12:34:39 +02:00
<data name="DISABLED_UPDATE_AUTOMATIC_CHECK_WARNING" xml:space="preserve">
<value>No updates found because automatic checking for updates is disabled.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="DISABLED_VMPP" xml:space="preserve">
<value>VM protection policy '{0}' disabled.</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="DISABLED_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Snapshot schedule '{0}' disabled.</value>
2016-01-29 12:34:44 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="DISABLE_HA" xml:space="preserve">
<value>Disable HA</value>
</data>
<data name="DISABLE_HA_CONFIGURE_MANAGEMENT_INTERFACES" xml:space="preserve">
<value>Disable HA if you want to configure the management interfaces</value>
</data>
<data name="DISABLE_HA_ELLIPSIS" xml:space="preserve">
<value>&Disable HA...</value>
</data>
<data name="DISABLE_NOAMP" xml:space="preserve">
<value>Disable</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="DISABLE_PVS_READ_CACHING_BUTTON" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>&Disable PVS-Accelerator</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
<data name="DISABLE_PVS_READ_CACHING_MENU" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Disable P&VS-Accelerator</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="DISABLE_WLB" xml:space="preserve">
<value>Pause Workload Balancing </value>
</data>
<data name="DISABLE_WLB_ELLIPSIS" xml:space="preserve">
<value>Pa&use</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="DISABLING" xml:space="preserve">
<value>Disabling</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="DISABLING_AD" xml:space="preserve">
<value>Disabling Active Directory Authentication</value>
</data>
<data name="DISABLING_AD_ON" xml:space="preserve">
<value>Disabling Active Directory Authentication on pool '{0}'</value>
</data>
<data name="DISABLING_HA" xml:space="preserve">
<value>Disabling HA</value>
</data>
<data name="DISABLING_HA_ON" xml:space="preserve">
<value>Disabling HA on pool '{0}'</value>
</data>
<data name="DISABLING_VMPP" xml:space="preserve">
<value>Disabling VM protection policy '{0}'...</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="DISABLING_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Disabling snapshot schedule '{0}'...</value>
2016-01-29 12:34:44 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="DISABLING_WLB" xml:space="preserve">
<value>Pausing Workload Balancing </value>
</data>
<data name="DISABLING_WLB_ON" xml:space="preserve">
<value>Pausing Workload Balancing on pool '{0}'</value>
</data>
<data name="DISASTER_RECOVERY_AMP" xml:space="preserve">
<value>Disaster Reco&very</value>
</data>
<data name="DISASTER_RECOVERY_CONTEXT_MENU" xml:space="preserve">
<value>Di&saster Recovery</value>
</data>
<data name="DISCONNECT" xml:space="preserve">
<value>Disconnect</value>
</data>
<data name="DISCONNECTED" xml:space="preserve">
<value>Disconnected</value>
</data>
<data name="DISCONNECTED_BEFORE_ACTION_STARTED" xml:space="preserve">
<value>The connection to the pool was lost before this action could take place.</value>
</data>
<data name="DISCONNECTED_SERVERS" xml:space="preserve">
<value>Disconnected servers</value>
</data>
<data name="DISCONNECT_ANYWAY" xml:space="preserve">
<value>&Disconnect anyway</value>
</data>
<data name="DISCONNECT_CANCEL" xml:space="preserve">
<value>Do&n't disconnect</value>
</data>
<data name="DISCONNECT_WARNING" xml:space="preserve">
2013-12-13 14:51:16 +01:00
<value>Unfinished tasks will be canceled if you disconnect from '{0}' before they finish.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DISKMEMORY_SNAPSHOTS" xml:space="preserve">
<value>Disk and memory snapshots</value>
</data>
<data name="DISKS" xml:space="preserve">
<value>Disks</value>
</data>
<data name="DISKS_AND_MEMORY" xml:space="preserve">
<value>Disks and memory</value>
</data>
<data name="DISKS_ONLY" xml:space="preserve">
<value>Disks only</value>
</data>
<data name="DISK_ADD" xml:space="preserve">
<value>Add Virtual Disk</value>
</data>
<data name="DISK_ATTACH" xml:space="preserve">
<value>Attach Disk</value>
</data>
<data name="DISK_PERCENT_USED" xml:space="preserve">
<value>{0}% ({1} used)</value>
</data>
<data name="DISK_TOO_BIG" xml:space="preserve">
<value>There is not enough available space for this disk</value>
</data>
<data name="DISK_TOO_SMALL" xml:space="preserve">
<value>Disk size needs to be at least {0} {1}</value>
</data>
<data name="DISMISS_ALL_CONFIRM_BUTTON" xml:space="preserve">
<value>Dismiss &all</value>
</data>
<data name="DISMISS_ALL_YES_CONFIRM_BUTTON" xml:space="preserve">
<value>Yes, Dismiss &all</value>
</data>
<data name="DISMISS_FILTERED_CONFIRM_BUTTON" xml:space="preserve">
2014-08-05 17:13:48 +02:00
<value>Only dismiss &visible</value>
2013-06-24 13:41:48 +02:00
</data>
2015-10-19 18:07:12 +02:00
<data name="DISPLAY" xml:space="preserve">
<value>Display</value>
</data>
<data name="DISPLAY_DETAILS" xml:space="preserve">
<value>Display options</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="DMC_UNAVAILABLE_NOTOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>A memory range cannot be set because [XenServer product] Tools are not installed on this VM.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DMC_UNAVAILABLE_NOTOOLS_PLURAL" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>A memory range cannot be set because [XenServer product] Tools are not installed on these VMs.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DMC_UNAVAILABLE_NOTSUPPORTED" xml:space="preserve">
<value>A memory range cannot be set because the operating system on this VM does not support it.</value>
</data>
<data name="DMC_UNAVAILABLE_NOTSUPPORTED_PLURAL" xml:space="preserve">
<value>A memory range cannot be set because the operating systems on these VMs do not support it.</value>
</data>
2015-09-14 17:21:44 +02:00
<data name="DMC_UNAVAILABLE_NO_IO_NO_MGMNT" xml:space="preserve">
2015-09-18 16:48:59 +02:00
<value>A memory range cannot be set because I/O drivers are not installed on this VM.</value>
2015-09-14 17:21:44 +02:00
</data>
<data name="DMC_UNAVAILABLE_NO_IO_NO_MGMNT_PLURAL" xml:space="preserve">
2015-09-18 16:48:59 +02:00
<value>A memory range cannot be set because I/O drivers are not installed on these VMs.</value>
2015-09-14 17:21:44 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="DMC_UNAVAILABLE_OLDTOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>A memory range cannot be set because [XenServer product] Tools are out of date on this VM.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DMC_UNAVAILABLE_OLDTOOLS_PLURAL" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>A memory range cannot be set because [XenServer product] Tools are out of date on these VMs.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DMC_UNAVAILABLE_TEMPLATE" xml:space="preserve">
<value>A memory range cannot be set for this template.</value>
</data>
<data name="DMC_UNAVAILABLE_VM" xml:space="preserve">
<value>A memory range cannot be set for this VM.</value>
</data>
<data name="DMC_UNAVAILABLE_VMS" xml:space="preserve">
<value>A memory range cannot be set for these VMs.</value>
</data>
2015-02-09 08:42:00 +01:00
<data name="DOCKER_DETAIL_TAB_TITLE" xml:space="preserve">
CA-162989: Container Management GUI use-ability/homogeneity fixes
Implemented changes as follows (copied from ticket):
"I'd suggest the following use-ability/homogeneity fixes for the new container management tabs, if they are quick and easy:
Combine "Docker Version" and "Docker Information" on the VM-General-tab into "Container Management - Docker Status" with the following fields only:
API version
Version
Git Commit
Driver
Index Server Address
Execution Driver
IPv4 Forwarding
In the "Processes" tab, change the name from "Docker Processes" to "Container Processes"
In the "Details" tab, change the name from "Docker Detail" to "Container Details"
In the "Details" tab, drop the top level element "docker_inspect" (XML requires a single root-node, afaik the Windows form treenode does not), or alternatively open the root node by default and rename it to "Inspect Result"
In the "Details" tab, add the "Details"-headline in black on white - just like on the "Processes"-tab
Also, on the container's General tab, show Properties button disabled, instead on hiding it (to be consistent to other cases, e.g. disconnected servers)
"
Signed-off-by: Gabor Apati-Nagy <gabor.apati-nagy@citrix.com>
2015-03-05 20:10:54 +01:00
<value>Container Details</value>
2015-02-09 08:42:00 +01:00
</data>
2015-02-15 03:52:12 +01:00
<data name="DOCKER_INFO_API_VERSION" xml:space="preserve">
<value>Api Version</value>
</data>
<data name="DOCKER_INFO_ARCH" xml:space="preserve">
<value>Arch</value>
</data>
<data name="DOCKER_INFO_DEBUG" xml:space="preserve">
<value>Debug</value>
</data>
<data name="DOCKER_INFO_DRIVER" xml:space="preserve">
<value>Driver</value>
</data>
<data name="DOCKER_INFO_DRIVER_STATUS" xml:space="preserve">
<value>Driver Status</value>
</data>
<data name="DOCKER_INFO_EXECUTION_DRIVER" xml:space="preserve">
<value>Execution Driver</value>
</data>
<data name="DOCKER_INFO_GIT_COMMIT" xml:space="preserve">
<value>Git Commit</value>
</data>
<data name="DOCKER_INFO_GO_VERSION" xml:space="preserve">
<value>Go Version</value>
</data>
<data name="DOCKER_INFO_INDEX_SERVER_ADDRESS" xml:space="preserve">
<value>Index Server Address</value>
</data>
<data name="DOCKER_INFO_INITIATE_PATH" xml:space="preserve">
<value>Initiate Path</value>
</data>
<data name="DOCKER_INFO_INITIATE_SHA1" xml:space="preserve">
<value>Initiate Sha1</value>
</data>
<data name="DOCKER_INFO_IPV4_FORWARDING" xml:space="preserve">
<value>IPv4 Forwarding</value>
</data>
<data name="DOCKER_INFO_KERNEL_VERSION" xml:space="preserve">
<value>Kernel Version</value>
</data>
<data name="DOCKER_INFO_LABELS" xml:space="preserve">
<value>Labels</value>
</data>
<data name="DOCKER_INFO_MEMORY_LIMIT" xml:space="preserve">
<value>Memory Limit</value>
</data>
<data name="DOCKER_INFO_NCPU" xml:space="preserve">
<value>NCPU</value>
</data>
<data name="DOCKER_INFO_NEVENT_LISTENER" xml:space="preserve">
<value>NEvents Listener</value>
</data>
<data name="DOCKER_INFO_NFD" xml:space="preserve">
<value>NFd</value>
</data>
<data name="DOCKER_INFO_NGOROUTINES" xml:space="preserve">
<value>NGoroutines</value>
</data>
<data name="DOCKER_INFO_ROOT_DIR" xml:space="preserve">
<value>Root Directory</value>
</data>
<data name="DOCKER_INFO_SWAP_LIMIT" xml:space="preserve">
<value>Swap Limit</value>
</data>
<data name="DOCKER_INFO_VERSION" xml:space="preserve">
<value>Version</value>
</data>
2015-03-09 16:32:07 +01:00
<data name="DOCKER_PROCESS_TAB_TITLE" xml:space="preserve">
2015-03-09 18:51:33 +01:00
<value>Container Processes</value>
2015-03-09 16:32:07 +01:00
</data>
<data name="DOES_NOT_USE" xml:space="preserve">
<value>does not use</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="DONE" xml:space="preserve">
<value>done.</value>
</data>
2016-09-19 18:00:02 +02:00
<data name="DONT_SELECT_TARGET_SERVER" xml:space="preserve">
<value>Don't select a target server</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DOWLOAD_LATEST_XS_TITLE" xml:space="preserve">
<value>{0} is now available</value>
</data>
<data name="DOWNLOADING_PATCH_FROM" xml:space="preserve">
2015-02-20 14:39:13 +01:00
<value>Downloading update from '{0}'...</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DOWNLOAD_AND_EXTRACT_ACTION_DOWNLOADING_DESC" xml:space="preserve">
<value>Downloading {0}</value>
</data>
<data name="DOWNLOAD_AND_EXTRACT_ACTION_DOWNLOADING_DETAILS_DESC" xml:space="preserve">
<value>Downloading {0} ({1} of {2})</value>
</data>
<data name="DOWNLOAD_AND_EXTRACT_ACTION_DOWNLOAD_CANCELLED_DESC" xml:space="preserve">
2013-12-13 14:51:16 +01:00
<value>Download canceled</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DOWNLOAD_AND_EXTRACT_ACTION_EXTRACTING_DESC" xml:space="preserve">
<value>Extracting {0}</value>
</data>
<data name="DOWNLOAD_AND_EXTRACT_ACTION_EXTRACTING_ERROR" xml:space="preserve">
<value>Cannot extract the update file from downloaded archive. Please see application logs for more details.</value>
</data>
<data name="DOWNLOAD_AND_EXTRACT_ACTION_FILE_NOT_FOUND" xml:space="preserve">
<value>Update file could not be located. Please see application logs for more details.</value>
</data>
<data name="DOWNLOAD_AND_EXTRACT_ACTION_TITLE" xml:space="preserve">
<value>Download and extract {0}</value>
</data>
<data name="DOWNLOAD_ELLIPSES" xml:space="preserve">
<value>Download...</value>
</data>
<data name="DOWNLOAD_LATEST_XS_BODY" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>{0} is now available. Download the latest at the [Citrix] website.</value>
2013-06-24 13:41:48 +02:00
</data>
2016-11-17 14:35:31 +01:00
<data name="DO_NOT_SHOW_THIS_MESSAGE" xml:space="preserve">
<value>&Don't show this message again</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="DRAC_NO_SUPP_PACK" xml:space="preserve">
<value>Dell supplemental pack is not installed.</value>
</data>
<data name="DRAC_POWERON_FAILED" xml:space="preserve">
<value>DRAC power on failed. Check your credentials and connectivity.</value>
</data>
<data name="DRAG_DROP_LOCAL_CD_LOADED" xml:space="preserve">
<value>Cannot migrate this VM while a local CD is loaded.
Eject the CD and try again.</value>
</data>
<data name="DRAG_DROP_LOCAL_CD_LOADED_TITLE" xml:space="preserve">
<value>Cannot Migrate VM</value>
</data>
<data name="DR_CONFIGURE_AMP" xml:space="preserve">
<value>&Configure...</value>
</data>
<data name="DR_CONFIGURE_TITLE" xml:space="preserve">
<value>Configure DR on '{0}'</value>
</data>
<data name="DR_DRYRUN_AMP" xml:space="preserve">
<value>Dr&y-run...</value>
</data>
<data name="DR_FAILBACK_AMP" xml:space="preserve">
<value>Fail &back...</value>
</data>
<data name="DR_FAILOVER_AMP" xml:space="preserve">
<value>Fail &over...</value>
</data>
<data name="DR_HA_CHECK_DESCRIPTION" xml:space="preserve">
<value>HA on pool {0}</value>
</data>
<data name="DR_WIZARD_AMP" xml:space="preserve">
<value>&Disaster Recovery Wizard...</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_CURRENT_POOL" xml:space="preserve">
<value>Current pool</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_DESCRIPTION_FAILBACK" xml:space="preserve">
<value>Select the vApps and individual VMs you want to fail back and specify the required power state for them after they have been recovered to pool ‘ {0}’ .</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_DESCRIPTION_FAILOVER" xml:space="preserve">
<value>Select the vApps and individual VMs you want to recover and specify the required power state for them after they have been recovered.</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILBACK_DONOTSTART" xml:space="preserve">
<value>&Do not start up failed back vApps and VMs</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILBACK_DONOTSTART_NOAMP" xml:space="preserve">
<value>Do not start up failed back vApps and VMs</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILBACK_START" xml:space="preserve">
<value>S&tart up all failed back vApps and VMs immediately</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILBACK_STARTPAUSED" xml:space="preserve">
<value>Sta&rt up failed back vApps and VMs in a paused state</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILBACK_STARTPAUSED_NOAMP" xml:space="preserve">
<value>Start up failed back vApps and VMs in a paused state</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILBACK_START_NOAMP" xml:space="preserve">
<value>Start up all failed back vApps and VMs immediately</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILOVER_DONOTSTART" xml:space="preserve">
<value>&Do not start up recovered vApps and VMs</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILOVER_DONOTSTART_NOAMP" xml:space="preserve">
<value>Do not start up recovered vApps and VMs</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILOVER_START" xml:space="preserve">
<value>S&tart up all recovered vApps and VMs immediately</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILOVER_STARTPAUSED" xml:space="preserve">
<value>Sta&rt up recovered vApps and VMs in a paused state</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILOVER_STARTPAUSED_NOAMP" xml:space="preserve">
<value>Start up recovered vApps and VMs in a paused state</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_FAILOVER_START_NOAMP" xml:space="preserve">
<value>Start up all recovered vApps and VMs immediately</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_TEXT" xml:space="preserve">
<value>Select vApps && VMs</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_TITLE_FAILBACK" xml:space="preserve">
<value>Select the vApps or individual virtual machines to fail back to the target pool</value>
</data>
<data name="DR_WIZARD_APPLIANCESPAGE_TITLE_FAILOVER" xml:space="preserve">
<value>Select the vApps or individual virtual machines to fail over to the target pool</value>
</data>
<data name="DR_WIZARD_APPLIANCE_CHECK_DESCRIPTION" xml:space="preserve">
<value>vApp '{0}'</value>
</data>
<data name="DR_WIZARD_APPPLIANCESPAGE_POOL_DESCRIPTION" xml:space="preserve">
<value>[{0} on {1}]</value>
</data>
<data name="DR_WIZARD_CHECKING_EXISTING_APPLIANCES_AND_VMS" xml:space="preserve">
<value>Checking for existing vApps and VMs in '{0}'</value>
</data>
<data name="DR_WIZARD_CHECKING_HA_STATUS" xml:space="preserve">
<value>Checking HA status</value>
</data>
<data name="DR_WIZARD_CHECKING_POWER_STATE_IN_SOURCE_POOLS" xml:space="preserve">
<value>Checking power state in source pools</value>
</data>
<data name="DR_WIZARD_CHECKING_VMS_CAN_BE_RECOVERED" xml:space="preserve">
<value>Checking storage availability in '{0}'</value>
</data>
<data name="DR_WIZARD_DRYRUN_TITLE" xml:space="preserve">
<value>Disaster Recovery - Test Failover to pool '{0}'</value>
</data>
<data name="DR_WIZARD_FAILBACK_TITLE" xml:space="preserve">
<value>Disaster Recovery - Failback to pool '{0}'</value>
</data>
<data name="DR_WIZARD_FAILOVER_TITLE" xml:space="preserve">
<value>Disaster Recovery - Failover to pool '{0}'</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_DRYRUN_LINE1" xml:space="preserve">
<value>This wizard will take you through the steps needed to perform a test failover of your critical vApps and VMs. The vApps and VMs you select will be recovered to pool ‘ {0}’ on the DR site but will not be started up.</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_DRYRUN_LINE2" xml:space="preserve">
<value>Configuration information for the vApps and VMs to be failed over will be retrieved from remote storage mirrors. Before test failover begins, the wizard will run a number of checks to ensure that the selected vApps and VMs can be recovered to your DR site.</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_DRYRUN_LINE3" xml:space="preserve">
<value>You will need to provide information about the following as you step through this wizard:
* The storage mirrors where the vApp and VM configuration data is currently stored.
* Which vApps and VMs you want to fail over to the DR site.</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_FAILBACK_LINE1" xml:space="preserve">
<value>This wizard will take you through the steps needed to fail back vApps and VMs to your primary data site.</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_FAILBACK_LINE2" xml:space="preserve">
<value>Configuration information for the vApps and VMs to be failed back will be retrieved from remote storage mirrors. Before failback begins, the wizard will run a number of checks to ensure that the selected vApps and VMs can be recovered to your primary data site.</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_FAILBACK_LINE3" xml:space="preserve">
<value>You will need to provide information about the following as you step through this wizard:
* The storage mirrors where the vApp and VM configuration data is currently stored.
* Which vApps and VMs you want to fail back.</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_FAILBACK_LINE4" xml:space="preserve">
<value>Before failback can take place, storage mirroring – remote replication of your VM data – must be halted.</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_FAILOVER_LINE1" xml:space="preserve">
<value>This wizard will take you through the steps needed to fail over your critical vApps and VMs in the event of a site/datacenter failure at your primary data site.</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_FAILOVER_LINE2" xml:space="preserve">
<value>Configuration information for the vApps and VMs to be recovered will be retrieved from remote storage mirrors. Before failover begins, the wizard will run a number of checks to ensure that the selected vApps and VMs can be brought back up on your DR site.</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_FAILOVER_LINE3" xml:space="preserve">
<value>You will need to provide information about the following as you step though this wizard:
* The storage mirrors where the vApp and VM configuration data is currently stored.
* Which vApps and VMs you want to fail over to the DR site.</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_FAILOVER_LINE4" xml:space="preserve">
<value>Before failover can take place, storage mirroring – remote replication of your VM data – must be halted.</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_TEXT" xml:space="preserve">
<value>Before You Start</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_TITLE_DRYRUN" xml:space="preserve">
<value>Test failover prerequisites</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_TITLE_FAILBACK" xml:space="preserve">
<value>Failback prerequisites</value>
</data>
<data name="DR_WIZARD_FIRSTPAGE_TITLE_FAILOVER" xml:space="preserve">
<value>Failover prerequisites</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_CONTINUE_DRYRUN" xml:space="preserve">
<value>Click Fail Over to begin the test recovery of the selected vApps and VMs.</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_CONTINUE_FAILBACK" xml:space="preserve">
<value>Click Fail Back to begin recovery of the selected vApps and VMs to your primary data site.</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_CONTINUE_FAILOVER" xml:space="preserve">
<value>Click Fail Over to begin recovery of the selected vApps and VMs.</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_DESCRIPTION_FAILBACK" xml:space="preserve">
<value>Failover pre-checks are performed to ensure that the selected vApps and VMs can be failed back to the selected pool. Please take appropriate action to resolve any issues.</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_DESCRIPTION_FAILOVER" xml:space="preserve">
<value>Pre-checks are performed to ensure that the selected vApps and VMs can be failed over. Please take appropriate action to resolve any issues.</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_DESELECT" xml:space="preserve">
<value>Deselect</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_FAILED" xml:space="preserve">
<value>{0} Failed</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_HEADER" xml:space="preserve">
<value>Pre-check {0} of {1}: {2}</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_NEXT_FAILBACK" xml:space="preserve">
<value>F&ail Back</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_NEXT_FAILOVER" xml:space="preserve">
<value>F&ail Over</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_OK" xml:space="preserve">
<value>{0}: OK</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_PROBLEM" xml:space="preserve">
<value>{0}: {1}</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_RESOLVE" xml:space="preserve">
<value>Resolve</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_STATUS_FAILURE" xml:space="preserve">
<value>Failover prechecks completed: {0} issues found</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_STATUS_RUNNING" xml:space="preserve">
<value>Running failover pre-checks:</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_STATUS_SUCCESS" xml:space="preserve">
<value>Failover prechecks completed: No issues found</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_TEXT" xml:space="preserve">
<value>Pre-checks</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_TITLE_FAILBACK" xml:space="preserve">
<value>Check that the selected vApps and VMs can be failed back</value>
</data>
<data name="DR_WIZARD_PRECHECKPAGE_TITLE_FAILOVER" xml:space="preserve">
<value>Check that the selected vApps and VMs can be failed over</value>
</data>
<data name="DR_WIZARD_PROBLEM_EXISTING_APPLIANCE" xml:space="preserve">
<value>Newer versions of its VMs already exist on pool {0}</value>
</data>
<data name="DR_WIZARD_PROBLEM_EXISTING_APPLIANCE_HELPMESSAGE" xml:space="preserve">
<value>Delete VMs...</value>
</data>
<data name="DR_WIZARD_PROBLEM_EXISTING_VM" xml:space="preserve">
<value>Newer version already exists on pool {0}</value>
</data>
<data name="DR_WIZARD_PROBLEM_EXISTING_VM_HELPMESSAGE" xml:space="preserve">
<value>Delete VM</value>
</data>
<data name="DR_WIZARD_PROBLEM_HA_ENABLED" xml:space="preserve">
<value>Enabled</value>
</data>
<data name="DR_WIZARD_PROBLEM_LOCAL_STORAGE" xml:space="preserve">
<value>Uses local storage '{0}'</value>
</data>
<data name="DR_WIZARD_PROBLEM_LOCAL_STORAGE_HELPMESSAGE" xml:space="preserve">
<value>Local storage</value>
</data>
<data name="DR_WIZARD_PROBLEM_MISSING_MULTIPLE_SRS" xml:space="preserve">
<value>Missing {0} SRs</value>
</data>
<data name="DR_WIZARD_PROBLEM_MISSING_MULTIPLE_SRS_HELPMESSAGE" xml:space="preserve">
<value>Attach SRs</value>
</data>
<data name="DR_WIZARD_PROBLEM_MISSING_MULTIPLE_SRS_NO_INFO" xml:space="preserve">
<value>Missing SRs information not found</value>
</data>
<data name="DR_WIZARD_PROBLEM_MISSING_SR" xml:space="preserve">
<value>Missing SR '{0}'</value>
</data>
<data name="DR_WIZARD_PROBLEM_MISSING_SR_HELPMESSAGE" xml:space="preserve">
<value>Attach SR</value>
</data>
<data name="DR_WIZARD_PROBLEM_RUNNING_APPLIANCE" xml:space="preserve">
<value>Is running on pool '{0}'</value>
</data>
<data name="DR_WIZARD_PROBLEM_RUNNING_APPLIANCE_HELPMESSAGE" xml:space="preserve">
<value>Shut down vApp</value>
</data>
<data name="DR_WIZARD_PROBLEM_RUNNING_VM" xml:space="preserve">
<value>Is running on pool '{0}'</value>
</data>
<data name="DR_WIZARD_PROBLEM_RUNNING_VM_HELPMESSAGE" xml:space="preserve">
<value>Shut down VM</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_COMPLETE_DRYRUN" xml:space="preserve">
<value>Test failover to pool '{0}' is complete.</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_COMPLETE_FAILBACK" xml:space="preserve">
<value>Failback to pool '{0}' is complete.</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_COMPLETE_FAILOVER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] Disaster Recovery is complete.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DR_WIZARD_RECOVERPAGE_CONTINUE_DRYRUN" xml:space="preserve">
<value>Click Next to remove the vApps and VMs that were failed over and to see the summary report.</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_CONTINUE_FAILBACK" xml:space="preserve">
<value>Click Next to see the summary report.</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_CONTINUE_FAILOVER" xml:space="preserve">
<value>Click Next to see the summary report.</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_IN_PROGRESS_DRYRUN" xml:space="preserve">
<value>Test failover is in progress. This may take some time.</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_IN_PROGRESS_FAILBACK" xml:space="preserve">
<value>Failback is in progress. This may take some time.</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_IN_PROGRESS_FAILOVER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] Disaster Recovery is in progress. This may take some time.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DR_WIZARD_RECOVERPAGE_OVERALL_PROGRESS" xml:space="preserve">
<value>Overall progress: {0} of {1} tasks done</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_RECOVERING_FROM" xml:space="preserve">
<value>Recovering from {0}</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_RECOVER_FROM" xml:space="preserve">
<value>Recover from {0}</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_STATUS_COMPLETED" xml:space="preserve">
<value>Completed</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_STATUS_FAILED" xml:space="preserve">
<value>Failed</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_STATUS_PENDING" xml:space="preserve">
<value>Pending</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_STATUS_WORKING" xml:space="preserve">
<value>Working</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_TEXT" xml:space="preserve">
<value>Progress</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_TITLE_DRYRUN" xml:space="preserve">
<value>Progress of test failover to pool '{0}'</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_TITLE_FAILBACK" xml:space="preserve">
<value>Progress of failback to pool '{0}'</value>
</data>
<data name="DR_WIZARD_RECOVERPAGE_TITLE_FAILOVER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] Disaster Recovery progress</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DR_WIZARD_REPORTPAGE_TEXT" xml:space="preserve">
<value>Summary</value>
</data>
<data name="DR_WIZARD_REPORTPAGE_TITLE_DRYRUN" xml:space="preserve">
<value>Summary of test failover to pool '{0}'</value>
</data>
<data name="DR_WIZARD_REPORTPAGE_TITLE_FAILBACK" xml:space="preserve">
<value>Summary of failback to pool '{0}'</value>
</data>
<data name="DR_WIZARD_REPORTPAGE_TITLE_FAILOVER" xml:space="preserve">
<value>Summary of failover to pool '{0}'</value>
</data>
<data name="DR_WIZARD_REPORT_ACTION_FAILED" xml:space="preserve">
<value>{0} - Failed: {1}</value>
</data>
<data name="DR_WIZARD_REPORT_ACTION_SUCCEEDED" xml:space="preserve">
<value>{0} - Succeeded</value>
</data>
<data name="DR_WIZARD_REPORT_DRYRUN_CLEANUP" xml:space="preserve">
<value>Test Failover cleanup</value>
</data>
<data name="DR_WIZARD_REPORT_DR_CLEANUP" xml:space="preserve">
<value>DR cleanup</value>
</data>
<data name="DR_WIZARD_REPORT_INTRODUCED_SRS" xml:space="preserve">
<value>SRs introduced during this wizard: {0}</value>
</data>
<data name="DR_WIZARD_REPORT_INTRODUCED_SRS_NONE" xml:space="preserve">
<value>SRs introduced during this wizard: None</value>
</data>
<data name="DR_WIZARD_REPORT_PRECHECK_WARNINGS" xml:space="preserve">
<value>Warnings: </value>
</data>
<data name="DR_WIZARD_REPORT_PRECHECK_WARNINGS_NONE" xml:space="preserve">
<value>Warnings: None</value>
</data>
<data name="DR_WIZARD_REPORT_RECOVERY_STARTED" xml:space="preserve">
<value>Recovery process started</value>
</data>
<data name="DR_WIZARD_REPORT_SELECTED_METADATA" xml:space="preserve">
<value>Selected VMs and vApps, grouped by pool: </value>
</data>
<data name="DR_WIZARD_REPORT_SELECTED_POWER_STATE" xml:space="preserve">
<value>Power state after recovery: {0}</value>
</data>
<data name="DR_WIZARD_REPORT_SELECTED_SRS" xml:space="preserve">
<value>Selected SRs: </value>
</data>
<data name="DR_WIZARD_STORAGEPAGE_DESCRIPTION_FAILBACK" xml:space="preserve">
2013-06-25 13:42:17 +02:00
<value>Select the storage repositories (SRs) containing the configuration data for the VMs and vApps that you want to fail back. If you know which SRs contain your VMs' disks, you can also include them now.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DR_WIZARD_STORAGEPAGE_DESCRIPTION_FAILOVER" xml:space="preserve">
2013-06-25 13:42:17 +02:00
<value>Select the storage repositories (SRs) containing the VM configuration data for the VMs and vApps that you want to fail over. If you know which SRs contain your VMs' disks, you can also include them now.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="DR_WIZARD_STORAGEPAGE_SCAN_RESULT_NONE" xml:space="preserve">
<value>No Storage Repositories were found</value>
</data>
<data name="DR_WIZARD_STORAGEPAGE_SCAN_RESULT_TITLE" xml:space="preserve">
<value>The following Storage Repositories were found:
</value>
</data>
<data name="DR_WIZARD_STORAGEPAGE_TEXT" xml:space="preserve">
<value>Locate Mirrored SRs</value>
</data>
<data name="DR_WIZARD_STORAGEPAGE_TITLE" xml:space="preserve">
<value>Locate the storage repositories where your recovery data is stored</value>
</data>
<data name="DR_WIZARD_VM_CHECK_DESCRIPTION" xml:space="preserve">
<value>VM '{0}'</value>
</data>
<data name="DR_WIZARD_WARNING_EXISTING_VM" xml:space="preserve">
<value>Already exists on pool {0}. It will be replaced.</value>
</data>
<data name="DR_WIZARD_WELCOMEPAGE_TEXT" xml:space="preserve">
<value>Welcome</value>
</data>
<data name="DR_WIZARD_WELCOMEPAGE_TITLE" xml:space="preserve">
<value>What do you want to do?</value>
</data>
<data name="DUPLEX" xml:space="preserve">
<value>Duplex</value>
</data>
<data name="DVD_DRIVE" xml:space="preserve">
<value>DVD drive</value>
</data>
<data name="DVD_DRIVE_LABEL_NUMBERED" xml:space="preserve">
<value>DVD Drive {0}:</value>
</data>
<data name="DYNAMIC_MAX" xml:space="preserve">
<value>Maximum memory</value>
</data>
<data name="DYNAMIC_MAX_AMP" xml:space="preserve">
<value>Ma&ximum memory</value>
</data>
<data name="DYNAMIC_MAX_COLON" xml:space="preserve">
<value>Ma&ximum memory:</value>
</data>
<data name="DYNAMIC_MEMORY_CONTROL" xml:space="preserve">
<value>Memory</value>
</data>
<data name="DYNAMIC_MENUITEM_WITHOUT_ACCESS_KEY" xml:space="preserve">
<value> {0}</value>
</data>
<data name="DYNAMIC_MENUITEM_WITH_ACCESS_KEY" xml:space="preserve">
<value>&{0} {1}</value>
</data>
<data name="DYNAMIC_MIN" xml:space="preserve">
<value>Minimum memory</value>
</data>
<data name="DYNAMIC_MIN_AMP" xml:space="preserve">
<value>&Minimum memory</value>
</data>
<data name="DYNAMIC_MIN_COLON" xml:space="preserve">
<value>&Minimum memory:</value>
</data>
<data name="EDIT" xml:space="preserve">
<value>P&roperties</value>
</data>
<data name="EDIT_DISK" xml:space="preserve">
<value>Edit Disk</value>
</data>
<data name="EDIT_NETWORK_BLURB_PHYSICAL" xml:space="preserve">
<value>If you want this network to be automatically added to new VMs, check the box below.</value>
</data>
<data name="EDIT_NETWORK_BLURB_VIRTUAL" xml:space="preserve">
<value>If you want this network to be automatically added to new VMs, check the box below. You can also set whether you want the network to be internal only, or assign it a VLAN and NIC.</value>
</data>
<data name="EDIT_SYS_DISK_WARNING" xml:space="preserve">
<value>This will change the device position of one of this VM's system disks and may leave the VM unbootable. Are you sure you wish to continue?</value>
</data>
<data name="EDIT_SYS_DISK_WARNING_TITLE" xml:space="preserve">
<value>Edit Storage Settings</value>
</data>
<data name="EJECT_BEFORE_VM_START_MESSAGE_BOX" xml:space="preserve">
<value>It may not be possible to start the selected VMs as they are using ISOs from an SR which is unavailable.
Would you like to eject these ISOs before continuing?</value>
</data>
<data name="EJECT_BUTTON_LABEL" xml:space="preserve">
<value>&Eject</value>
</data>
<data name="EJECT_CD" xml:space="preserve">
<value>Eject CD</value>
</data>
<data name="EJECT_YOUR_CD" xml:space="preserve">
<value>Please eject your CD</value>
</data>
<data name="ELLIPSIS" xml:space="preserve">
<value>...</value>
</data>
<data name="EMAIL_ALERTS" xml:space="preserve">
<value>Email Alerts</value>
</data>
<data name="EMAIL_ALERTS_TITLE" xml:space="preserve">
2016-01-29 12:34:44 +01:00
<value>Configure email notification for policy alerts</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="EMAIL_OPTIONS" xml:space="preserve">
<value>Email Options</value>
</data>
<data name="EMPTY" xml:space="preserve">
<value><empty></value>
</data>
<data name="EMPTY_LIST_DISK_SNAPSHOTS" xml:space="preserve">
<value>There are no associated virtual disks or snapshots</value>
</data>
<data name="ENABLE" xml:space="preserve">
<value>Ena&ble</value>
</data>
<data name="ENABLED" xml:space="preserve">
<value>Enabled</value>
</data>
<data name="ENABLED_VMPP" xml:space="preserve">
<value>VM protection policy '{0}' enabled.</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="ENABLED_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Snapshot schedule '{0}' enabled.</value>
2016-01-29 12:34:44 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ENABLE_HA_ELLIPSIS" xml:space="preserve">
<value>&Enable HA...</value>
</data>
<data name="ENABLE_PLAIN" xml:space="preserve">
<value>Enable</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="ENABLE_PVS_READ_CACHING_BUTTON" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>E&nable PVS-Accelerator...</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
<data name="ENABLE_PVS_READ_CACHING_MENU" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>Ena&ble PVS-Accelerator...</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
<data name="ENABLE_PVS_READ_CACHING_RUBRIC_MULTIPLE" xml:space="preserve">
2016-10-13 13:32:56 +02:00
<value>Choose the PVS site from which the selected VMs are streamed.</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
<data name="ENABLE_PVS_READ_CACHING_RUBRIC_SINGLE" xml:space="preserve">
2016-10-13 13:32:56 +02:00
<value>Choose the PVS site from which the selected VM is streamed.</value>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ENABLE_WLB_ELLIPSIS" xml:space="preserve">
<value>Res&ume</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="ENABLING" xml:space="preserve">
<value>Enabling</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ENABLING_AD" xml:space="preserve">
<value>Enabling Active Directory Authentication</value>
</data>
<data name="ENABLING_AD_ON" xml:space="preserve">
<value>Enabling Active Directory Authentication on pool '{0}'</value>
</data>
<data name="ENABLING_HA" xml:space="preserve">
<value>Enabling HA</value>
</data>
<data name="ENABLING_HA_ON" xml:space="preserve">
<value>Enabling HA on pool '{0}'</value>
</data>
<data name="ENABLING_VMPP" xml:space="preserve">
<value>Enabling VM protection policy '{0}'...</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="ENABLING_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Enabling snapshot schedule '{0}'...</value>
2016-01-29 12:34:44 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ENABLING_WLB" xml:space="preserve">
<value>Resuming Workload Balancing </value>
</data>
<data name="ENABLING_WLB_ON" xml:space="preserve">
<value>Resuming Workload Balancing on pool '{0}'</value>
</data>
<data name="ENCRYPTING_FILES" xml:space="preserve">
<value>Encrypting appliance files...</value>
</data>
<data name="ENDS_WITH" xml:space="preserve">
<value>ends with</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="ENTERPRISE_PERSOCKET_LICENSES_X_REQUIRED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] &Enterprise Per-Socket ({0} required)</value>
2015-01-23 11:41:54 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="ENTER_MAINTENANCE_MODE" xml:space="preserve">
<value>Enter &Maintenance Mode...</value>
</data>
<data name="ENTER_MAINTENANCE_MODE_CONTEXT_MENU" xml:space="preserve">
<value>&Enter Maintenance Mode...</value>
</data>
<data name="ENTER_MASTER_PASSWORD_TO_ACCESS_SETTINGS_TT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>To access your saved session it is required that you enter the master password when starting [XenCenter]</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ENTER_VALID_QOS" xml:space="preserve">
<value>The value for your QoS limit needs to be greater than zero</value>
</data>
<data name="EQUALLOGICS_MEMBERS" xml:space="preserve">
<value>Members</value>
</data>
<data name="ERROR" xml:space="preserve">
<value>Error</value>
</data>
<data name="ERROR_ACTIVATING_VDIS_MESSAGE" xml:space="preserve">
<value>The following virtual disks could not be activated:</value>
</data>
<data name="ERROR_ACTIVATING_VDIS_TITLE" xml:space="preserve">
<value>Error Activating Virtual Disks</value>
</data>
<data name="ERROR_AUTHENTICATION" xml:space="preserve">
2016-12-16 19:36:35 +01:00
<value>User name and password mismatch.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ERROR_CONNECTING_BLURB" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] has encountered a problem connecting to this server.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ERROR_DEACTIVATING_MULTIPLE_VDIS_MESSAGE" xml:space="preserve">
<value>The following virtual disks could not be deactivated:</value>
</data>
<data name="ERROR_DEACTIVATING_MULTIPLE_VDIS_TITLE" xml:space="preserve">
<value>Error Deactivating Virtual Disks</value>
</data>
<data name="ERROR_DESTROYING_STORAGE_ITEMS_MESSAGE" xml:space="preserve">
<value>The following storage could not be destroyed:</value>
</data>
<data name="ERROR_DESTROYING_STORAGE_ITEMS_TITLE" xml:space="preserve">
<value>Error Destroying Storage Items</value>
</data>
2016-09-06 15:53:46 +02:00
<data name="ERROR_DETACHING_VDIS_MESSAGE" xml:space="preserve">
<value>The following virtual disks could not be detached:</value>
2013-06-24 13:41:48 +02:00
</data>
2016-09-06 15:53:46 +02:00
<data name="ERROR_DETACHING_VDIS_TITLE" xml:space="preserve">
<value>Error Detaching Virtual Disks</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ERROR_DIALOG_ADD_TO_POOL_TEXT" xml:space="preserve">
<value>The following servers could not be added to the pool '{0}':</value>
</data>
<data name="ERROR_DIALOG_ADD_TO_POOL_TITLE" xml:space="preserve">
<value>Error Adding Server to Pool</value>
</data>
<data name="ERROR_DIALOG_DELETE_TEMPLATE_TEXT" xml:space="preserve">
<value>The following templates could not be deleted:</value>
</data>
<data name="ERROR_DIALOG_DELETE_TEMPLATE_TITLE" xml:space="preserve">
<value>Error Deleting Template</value>
</data>
<data name="ERROR_DIALOG_DELETE_VM_OR_TEMPLATE_TEXT" xml:space="preserve">
<value>The following items could not be deleted:</value>
</data>
<data name="ERROR_DIALOG_DELETE_VM_OR_TEMPLATE_TITLE" xml:space="preserve">
<value>Error Deleting Items</value>
</data>
<data name="ERROR_DIALOG_DELETE_VM_TEXT" xml:space="preserve">
<value>The following VMs could not be deleted:</value>
</data>
<data name="ERROR_DIALOG_DELETE_VM_TITLE" xml:space="preserve">
<value>Error Deleting VM</value>
</data>
<data name="ERROR_DIALOG_DESTROY_SR_TEXT" xml:space="preserve">
<value>The following storage repositories could not be destroyed:</value>
</data>
<data name="ERROR_DIALOG_DESTROY_SR_TITLE" xml:space="preserve">
<value>Error Destroying Storage Repository</value>
</data>
<data name="ERROR_DIALOG_DETACH_SR_TEXT" xml:space="preserve">
<value>The following storage repositories could not be detached:</value>
</data>
<data name="ERROR_DIALOG_DETACH_SR_TITLE" xml:space="preserve">
<value>Error Detaching Storage Repository</value>
</data>
<data name="ERROR_DIALOG_FORCE_REBOOT_VM_TEXT" xml:space="preserve">
<value>The following VMs could not be forced to reboot:</value>
</data>
<data name="ERROR_DIALOG_FORCE_REBOOT_VM_TITLE" xml:space="preserve">
<value>Error Forcing VM Reboot</value>
</data>
<data name="ERROR_DIALOG_FORCE_SHUTDOWN_VM_TEXT" xml:space="preserve">
<value>The following VMs could not be forced to shut down:</value>
</data>
<data name="ERROR_DIALOG_FORCE_SHUTDOWN_VM_TITLE" xml:space="preserve">
<value>Error Shutting Down VM</value>
</data>
<data name="ERROR_DIALOG_FORGET_SR_TEXT" xml:space="preserve">
<value>There were errors while forgetting the following storage repositories:</value>
</data>
<data name="ERROR_DIALOG_FORGET_SR_TITLE" xml:space="preserve">
<value>Error Forgetting Storage Repository</value>
</data>
<data name="ERROR_DIALOG_MIGRATE_TEXT" xml:space="preserve">
<value>The following VMs could not be migrated to the selected server:</value>
</data>
<data name="ERROR_DIALOG_MIGRATE_TITLE" xml:space="preserve">
<value>Error Migrating VM to Server</value>
</data>
<data name="ERROR_DIALOG_POWER_ON_HOST_TEXT" xml:space="preserve">
<value>The following servers could not be powered on:</value>
</data>
<data name="ERROR_DIALOG_POWER_ON_HOST_TITLE" xml:space="preserve">
<value>Error Powering On Server</value>
</data>
<data name="ERROR_DIALOG_REBOOT_HOST_TEXT" xml:space="preserve">
<value>The following servers could not be rebooted:</value>
</data>
<data name="ERROR_DIALOG_REBOOT_HOST_TITLE" xml:space="preserve">
<value>Error Rebooting Server</value>
</data>
<data name="ERROR_DIALOG_REBOOT_VM_TEXT" xml:space="preserve">
<value>The following VMs could not be rebooted:</value>
</data>
<data name="ERROR_DIALOG_REBOOT_VM_TITLE" xml:space="preserve">
<value>Error Rebooting VM</value>
</data>
<data name="ERROR_DIALOG_RESUME_ON_TEXT" xml:space="preserve">
<value>The following VMs could not be resumed on the selected server:</value>
</data>
<data name="ERROR_DIALOG_RESUME_ON_TITLE" xml:space="preserve">
<value>Error Resuming VM on Server</value>
</data>
<data name="ERROR_DIALOG_RESUME_VM_TEXT" xml:space="preserve">
<value>The following Vms could not be resumed:</value>
</data>
<data name="ERROR_DIALOG_RESUME_VM_TITLE" xml:space="preserve">
<value>Error Resuming VM</value>
</data>
<data name="ERROR_DIALOG_SHUTDOWN_HOST_TEXT" xml:space="preserve">
<value>The following servers could not be shut down:</value>
</data>
<data name="ERROR_DIALOG_SHUTDOWN_HOST_TITLE" xml:space="preserve">
<value>Error Shutting Down Server</value>
</data>
<data name="ERROR_DIALOG_SHUTDOWN_VMS_TITLE" xml:space="preserve">
<value>The following VMs could not be shut down:</value>
</data>
<data name="ERROR_DIALOG_SHUTDOWN_VM_TITLE" xml:space="preserve">
<value>Error Shutting Down VM</value>
</data>
<data name="ERROR_DIALOG_START_ON_TEXT" xml:space="preserve">
<value>The following VMs could not be started on the selected server:</value>
</data>
<data name="ERROR_DIALOG_START_ON_TITLE" xml:space="preserve">
<value>Error Starting VM on Server</value>
</data>
<data name="ERROR_DIALOG_START_VM_TEXT" xml:space="preserve">
<value>There were no servers available to start VM '{0}'.</value>
</data>
<data name="ERROR_DIALOG_START_VM_TITLE" xml:space="preserve">
<value>Error Starting VM</value>
</data>
<data name="ERROR_DIALOG_SUSPEND_VM_TEXT" xml:space="preserve">
<value>The following VMs could not be suspended:</value>
</data>
<data name="ERROR_DIALOG_SUSPEND_VM_TITLE" xml:space="preserve">
<value>Error Suspending VM</value>
</data>
<data name="ERROR_FILE_NOT_FOUND" xml:space="preserve">
<value>File {0} not found</value>
</data>
<data name="ERROR_HOST_STILL_BOOTING" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] is still booting.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ERROR_INVALID_GATEWAY" xml:space="preserve">
<value>Gateway is invalid.</value>
</data>
<data name="ERROR_INVALID_IP" xml:space="preserve">
<value>IP address is invalid</value>
</data>
<data name="ERROR_INVALID_MASK" xml:space="preserve">
<value>Subnet mask is invalid.</value>
</data>
<data name="ERROR_INVALID_URI" xml:space="preserve">
<value>'{0}' is not a valid URI</value>
</data>
<data name="ERROR_NOT_FOUND" xml:space="preserve">
<value>The server '{0}' could not be found.</value>
</data>
<data name="ERROR_NO_PERMISSION" xml:space="preserve">
<value>You are not authorized to access this server.</value>
</data>
<data name="ERROR_NO_XENSERVER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Could not find [XenServer] on '{0}'.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="ERROR_PREPARING_HOST" xml:space="preserve">
<value>Error preparing host</value>
</data>
2017-02-21 17:33:00 +01:00
<data name="ERROR_PROXY_AUTHENTICATION" xml:space="preserve">
<value>Could not authenticate to proxy server on '{0}'.</value>
</data>
2015-05-07 18:54:42 +02:00
<data name="ERROR_PUTTY_LAUNCHING" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] has encountered a problem launching PuTTY.</value>
2015-05-07 18:54:42 +02:00
</data>
2016-05-23 13:48:01 +02:00
<data name="ERROR_SECURE_CHANNEL_FAILURE" xml:space="preserve">
<value>Could not create SSL/TLS secure channel.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ERROR_UNKNOWN" xml:space="preserve">
<value>An unknown error occurred.</value>
</data>
<data name="ERROR_UNSUPPORTED_FILE_TYPE" xml:space="preserve">
<value>Unknown file type.</value>
</data>
<data name="ERRO_IMPORTING_SERVER_LIST" xml:space="preserve">
<value>Error importing server list. Check that the xml format in the file is correct.</value>
</data>
<data name="EULA" xml:space="preserve">
<value>EULA</value>
</data>
<data name="EULAS" xml:space="preserve">
<value>EULAs</value>
</data>
2013-10-24 15:05:01 +02:00
<data name="EVACUATE_HOST_DIALOG_TITLE" xml:space="preserve">
<value>Enter Maintenance Mode - {0}</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="EVACUATE_HOST_EJECT_CD_PROMPT" xml:space="preserve">
2013-10-31 16:55:49 +01:00
<value>{0} Eject the CD</value>
2013-06-24 13:41:48 +02:00
</data>
2015-09-21 17:59:43 +02:00
<data name="EVACUATE_HOST_INSTALL_MGMNT_PROMPT" xml:space="preserve">
<value>{0} Install Management Agent</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="EVACUATE_HOST_INSTALL_TOOLS_PROMPT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>{0} Install [XenServer product] Tools</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="EVACUATE_HOST_LOCAL_CD" xml:space="preserve">
2013-10-31 16:55:49 +01:00
<value>This VM uses a local CD.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="EVACUATE_HOST_LOCAL_STORAGE" xml:space="preserve">
2013-10-31 16:55:49 +01:00
<value>This VM uses local storage.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="EVACUATE_HOST_NOT_ENOUGH_MEMORY" xml:space="preserve">
<value>There is not enough free memory available on the other servers in the pool to migrate all the running VMs off this server. Please suspend some of the VMs</value>
</data>
<data name="EVACUATE_HOST_NOT_ENOUGH_MEMORY_TITLE" xml:space="preserve">
<value>Not enough memory</value>
</data>
<data name="EVACUATE_HOST_NO_OTHER_HOSTS" xml:space="preserve">
<value>There are no other servers available in the pool to migrate the running VMs to. Please suspend the VMs instead.</value>
</data>
<data name="EVACUATE_HOST_NO_OTHER_HOSTS_TITLE" xml:space="preserve">
<value>No servers available</value>
</data>
2015-04-16 11:38:43 +02:00
<data name="EVACUATE_HOST_SHUTDOWN_VM_PROMPT" xml:space="preserve">
<value>{0} Shut down the VM</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="EVACUATE_HOST_SUSPEND_VM_PROMPT" xml:space="preserve">
2013-10-31 16:55:49 +01:00
<value>{0} Suspend the VM</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="EVACUATE_SOLUTION_IN_PROGRESS" xml:space="preserve">
<value>Action in progress...</value>
</data>
<data name="EXACT_MATCH" xml:space="preserve">
<value>exactly matches</value>
</data>
<data name="EXAMPLE" xml:space="preserve">
<value>Example: {0}</value>
</data>
<data name="EXCEPTION_GENERAL" xml:space="preserve">
<value>A general exception has occurred.</value>
</data>
<data name="EXCEPTION_USER_CANCELLED" xml:space="preserve">
2016-02-19 17:27:02 +01:00
<value>Canceled</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="EXCEPTION_USER_CANCELLED_MASTER" xml:space="preserve">
2013-12-13 14:51:16 +01:00
<value>User canceled. Master needs to be upgraded first.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="EXIT_MAINTENANCE_MODE" xml:space="preserve">
<value>Exit &Maintenance Mode</value>
</data>
<data name="EXIT_MAINTENANCE_MODE_CONTEXT_MENU" xml:space="preserve">
<value>&Exit Maintenance Mode</value>
</data>
<data name="EXIT_MAINTENANCE_MODE_PROMPT" xml:space="preserve">
<value>Do you wish to have the following VMs automatically migrated back to, resumed on or started on this server?
{0}</value>
</data>
<data name="EXIT_SERVER_FROM_MAINTENANCE_MODE" xml:space="preserve">
<value>Exit {0} from maintenance mode</value>
</data>
<data name="EXPAND_ALL" xml:space="preserve">
<value>E&xpand All</value>
</data>
<data name="EXPORTED_SYSTEM_ALERTS" xml:space="preserve">
<value>Exported system alerts to {0}</value>
</data>
2013-12-05 13:46:39 +01:00
<data name="EXPORTED_UPDATES" xml:space="preserve">
<value>Exported updates to {0}.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="EXPORTING" xml:space="preserve">
<value>Exporting</value>
</data>
<data name="EXPORTING_SYSTEM_ALERTS" xml:space="preserve">
<value>Exporting system alerts to {0}...</value>
</data>
2013-12-05 13:46:39 +01:00
<data name="EXPORTING_UPDATES" xml:space="preserve">
<value>Exporting updates to {0}...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="EXPORTING_VMS" xml:space="preserve">
<value>Exporting VMs...</value>
</data>
<data name="EXPORTVM_COULD_NOT_SHOW" xml:space="preserve">
<value>Couldn't show file open dialog - {0}</value>
</data>
<data name="EXPORTVM_NOT_HAPPEN" xml:space="preserve">
<value>Should not happen</value>
</data>
<data name="EXPORT_ALL" xml:space="preserve">
<value>Export All</value>
</data>
<data name="EXPORT_APPLIANCE" xml:space="preserve">
<value>Export OVF/OVA Package</value>
</data>
<data name="EXPORT_APPLIANCE_PAGE_ERROR_APP_EXISTS" xml:space="preserve">
<value>Appliance already exists, please select a new destination.</value>
</data>
<data name="EXPORT_APPLIANCE_PAGE_ERROR_INALID_APP" xml:space="preserve">
<value>Appliance name is invalid.</value>
</data>
<data name="EXPORT_APPLIANCE_PAGE_ERROR_INVALID_DIR" xml:space="preserve">
<value>Destination directory is invalid.</value>
</data>
<data name="EXPORT_APPLIANCE_PAGE_ERROR_NON_EXIST_DIR" xml:space="preserve">
<value>Destination directory does not exist.</value>
</data>
<data name="EXPORT_APPLIANCE_PAGE_ERROR_PERMISSIONS" xml:space="preserve">
<value>You do not have write permission on the destination directory.</value>
</data>
<data name="EXPORT_APPLIANCE_PAGE_FORMAT_OVFOVA" xml:space="preserve">
<value>OVF/OVA Package (*.ovf, *.ova)</value>
</data>
<data name="EXPORT_APPLIANCE_PAGE_FORMAT_XVA" xml:space="preserve">
<value>XVA File (*.xva)</value>
</data>
<data name="EXPORT_APPLIANCE_PAGE_TEXT" xml:space="preserve">
<value>Export File Details</value>
</data>
<data name="EXPORT_APPLIANCE_PAGE_TITLE" xml:space="preserve">
<value>Choose the VM export format, location and filename.</value>
</data>
<data name="EXPORT_AS_BACKUP" xml:space="preserve">
<value>Export to File...</value>
</data>
<data name="EXPORT_EULA_PAGE_FILETYPES" xml:space="preserve">
<value>Normal text file (*.txt)|*.txt|Rich text file (*.rtf)|*.rtf</value>
</data>
<data name="EXPORT_EULA_PAGE_FILE_LIMIT_WARNING" xml:space="preserve">
<value>The maximum number of EULAs that can be included in the appliance is {0}. Selected EULA documents exceeding this number will not be added to the appliance. Click OK to proceed or Cancel to go back and change you selection.</value>
</data>
<data name="EXPORT_EULA_PAGE_FILE_LIMIT_WARNING_CAPTION" xml:space="preserve">
<value>Maximum number of EULAs exceeded</value>
</data>
<data name="EXPORT_EULA_PAGE_INVALID_FILE" xml:space="preserve">
<value>{0} is not a valid EULA document.</value>
</data>
<data name="EXPORT_EULA_PAGE_TITLE" xml:space="preserve">
<value>Optionally, include EULAs in the OVF/OVA package</value>
</data>
<data name="EXPORT_EULA_PAGE_TOOLTIP" xml:space="preserve">
<value>Maximum number of EULAs ({0}) has been reached.</value>
</data>
<data name="EXPORT_OPTIONS_PAGE_TEXT" xml:space="preserve">
<value>Advanced Options</value>
</data>
<data name="EXPORT_OPTIONS_PAGE_TITLE" xml:space="preserve">
<value>Select the manifest, signing and output file format options you want</value>
</data>
2016-07-20 00:51:48 +02:00
<data name="EXPORT_OVA_PACKAGE" xml:space="preserve">
<value>Export OVA package '{0}' from '{1}'</value>
</data>
<data name="EXPORT_OVF_PACKAGE" xml:space="preserve">
<value>Export OVF package '{0}' from '{1}'</value>
</data>
2016-04-20 16:17:48 +02:00
<data name="EXPORT_SECURITY_PAGE_ERROR_CERTIFICATE_INVALID" xml:space="preserve">
<value>The certificate is invalid.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="EXPORT_SECURITY_PAGE_ERROR_CERT_NON_EXIST" xml:space="preserve">
<value>Certificate file does not exist.</value>
</data>
<data name="EXPORT_SECURITY_PAGE_ERROR_INVALID_CERT" xml:space="preserve">
<value>Certificate path is invalid.</value>
</data>
<data name="EXPORT_SECURITY_PAGE_ERROR_SIGN_INVALID" xml:space="preserve">
<value>The certificate is invalid or the private key's password is incorrect.</value>
</data>
<data name="EXPORT_SECURITY_PAGE_FILETYPES" xml:space="preserve">
<value>Personal Certificate Files (*.pfx) |*.pfx</value>
</data>
<data name="EXPORT_SECURITY_PAGE_TEXT" xml:space="preserve">
<value>Security</value>
</data>
<data name="EXPORT_SECURITY_PAGE_TITLE" xml:space="preserve">
<value>Select security options</value>
</data>
<data name="EXPORT_SELECTVMS_PAGE_ERROR_TARGET_SPACE_NOT_ENOUGH" xml:space="preserve">
<value>Target destination has only {0} of free space and you need at least {1} to export the selected VMs.</value>
</data>
<data name="EXPORT_SELECTVMS_PAGE_TEXT" xml:space="preserve">
<value>Virtual Machines</value>
</data>
<data name="EXPORT_SELECTVMS_PAGE_TITLE_OVF" xml:space="preserve">
<value>Confirm which VMs to include in the OVF/OVA package</value>
</data>
<data name="EXPORT_SELECTVMS_PAGE_TITLE_XVA" xml:space="preserve">
<value>Confirm which VM to export</value>
</data>
<data name="EXPORT_SNAPSHOT_AS_TEMPLATE_MENU_ITEM" xml:space="preserve">
<value>&Export Snapshot As Template...</value>
</data>
<data name="EXPORT_SYSTEM_ALERTS" xml:space="preserve">
<value>Export system alerts to {0}</value>
</data>
2013-12-05 13:46:39 +01:00
<data name="EXPORT_UPDATES" xml:space="preserve">
<value>Exported updates to {0}</value>
</data>
2016-07-20 00:51:48 +02:00
<data name="EXPORT_VM_TITLE" xml:space="preserve">
<value>Export VM '{0}' from '{1}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="EXPORT_VM_VERIFY_POST_INSTALL" xml:space="preserve">
<value>&Verify export on completion</value>
</data>
2014-08-07 08:18:29 +02:00
<data name="EXTERNAL_NETWORK" xml:space="preserve">
<value>External network</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="EXTERNAL_PLUGIN_BAD_EXIT" xml:space="preserve">
<value>External command exited with Exit Code: {0}</value>
</data>
<data name="EXTERNAL_PLUGIN_FINISHED" xml:space="preserve">
<value>Plugin finished executing</value>
</data>
<data name="EXTERNAL_PLUGIN_RUNNING" xml:space="preserve">
<value>Running '{0}'</value>
</data>
<data name="EXTERNAL_PLUGIN_TITLE" xml:space="preserve">
<value>Execute '{0}' from plugin '{1}'</value>
</data>
<data name="EXTERNAL_PLUGIN_WIN32" xml:space="preserve">
<value>Failed to run plugin executable. Please see the client log for details.</value>
</data>
<data name="FAILED" xml:space="preserve">
<value>Failed</value>
</data>
<data name="FAILED_TO_ADD_TO_ACCESS_LIST" xml:space="preserve">
<value>Failed to add to access list</value>
</data>
<data name="FAILOVER_MAX_CAPACITY" xml:space="preserve">
<value>Max failover capacity: {0}</value>
</data>
<data name="FAILOVER_TOLERANCE" xml:space="preserve">
<value>Server failure limit: {0}</value>
</data>
<data name="FALSE" xml:space="preserve">
<value>False</value>
</data>
<data name="FAST_CLONE_UNAVAILABLE" xml:space="preserve">
<value>Fast clone is not supported by this storage type</value>
</data>
<data name="FEATURE_DISABLED_IN_REGISTER" xml:space="preserve">
<value>Feature disabled in the registry</value>
</data>
2014-08-06 14:46:53 +02:00
<data name="FETCH_EARLIER_DATA" xml:space="preserve">
<value>&Next Section</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="FIBRECHANNEL_NO_RESULTS" xml:space="preserve">
<value>No LUNs were found. Please verify your hardware configuration.</value>
</data>
<data name="FIBRECHANNEL_XML_ERROR" xml:space="preserve">
<value>The scan failed. Please try again.</value>
</data>
<data name="FIELD_DISABLED" xml:space="preserve">
<value>This feature is disabled due to license restrictions on the server.</value>
</data>
<data name="FILER_PARAM_INVALID_CHAR" xml:space="preserve">
<value>You entered an invalid character in one of the filer parameters.</value>
</data>
<data name="FILE_ALL" xml:space="preserve">
<value>All files</value>
</data>
<data name="FILE_PDF" xml:space="preserve">
<value>Acrobat (PDF) file</value>
</data>
<data name="FILE_XLS" xml:space="preserve">
<value>Excel file</value>
</data>
<data name="FILE_X_EXISTS_OVERWRITE" xml:space="preserve">
<value>File {0} already exists. Overwrite?</value>
</data>
2013-07-03 12:10:21 +02:00
<data name="FILTERS_OFF" xml:space="preserve">
<value>Filters are OFF</value>
</data>
<data name="FILTERS_ON" xml:space="preserve">
<value>Filters are ON</value>
</data>
2013-07-11 18:47:06 +02:00
<data name="FILTER_SHOW_ALL" xml:space="preserve">
<value>Show &All</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="FINISH" xml:space="preserve">
<value>&Finish</value>
</data>
<data name="FINISH_PAGE_ADDSPACE" xml:space="preserve">
<value>Additional space:</value>
</data>
<data name="FINISH_PAGE_COMPRESS" xml:space="preserve">
<value>Files will be compressed:</value>
</data>
<data name="FINISH_PAGE_CPUCOUNT" xml:space="preserve">
<value>CPU count:</value>
</data>
<data name="FINISH_PAGE_CREATE_MANIFEST" xml:space="preserve">
<value>A manifest will be created:</value>
</data>
<data name="FINISH_PAGE_CREATE_OVA" xml:space="preserve">
<value>An OVA package will be created:</value>
</data>
<data name="FINISH_PAGE_DIGITAL_SIGNATURE" xml:space="preserve">
<value>The package will be digitally signed:</value>
</data>
<data name="FINISH_PAGE_ENCRYPT" xml:space="preserve">
<value>Appliance files will be encrypted: {0}</value>
</data>
<data name="FINISH_PAGE_IMAGEPATH" xml:space="preserve">
<value>Virtual Hard Disk image:</value>
</data>
<data name="FINISH_PAGE_ISOSR" xml:space="preserve">
<value>Selected ISO SR:</value>
</data>
<data name="FINISH_PAGE_MEMORY" xml:space="preserve">
<value>Memory:</value>
</data>
<data name="FINISH_PAGE_NETWORK" xml:space="preserve">
<value>Network:</value>
</data>
<data name="FINISH_PAGE_NETWORK_FOR_VM" xml:space="preserve">
<value>{0} network:</value>
</data>
<data name="FINISH_PAGE_REVIEW_APPLIANCE" xml:space="preserve">
<value>Package name:</value>
</data>
<data name="FINISH_PAGE_REVIEW_DESTINATION" xml:space="preserve">
<value>Destination path:</value>
</data>
<data name="FINISH_PAGE_REVIEW_EULA" xml:space="preserve">
<value>Selected EULA files:</value>
</data>
<data name="FINISH_PAGE_REVIEW_VMS" xml:space="preserve">
<value>Selected VMs:</value>
</data>
<data name="FINISH_PAGE_RUN_FIXUPS" xml:space="preserve">
<value>Use OS Fixup:</value>
</data>
<data name="FINISH_PAGE_STORAGE" xml:space="preserve">
<value>Storage:</value>
</data>
<data name="FINISH_PAGE_STORAGE_FOR_VM" xml:space="preserve">
<value>{0} storage:</value>
</data>
<data name="FINISH_PAGE_TARGET" xml:space="preserve">
<value>Target:</value>
</data>
<data name="FINISH_PAGE_TARGET_FOR_VM" xml:space="preserve">
<value>{0} target:</value>
</data>
<data name="FINISH_PAGE_TEXT" xml:space="preserve">
<value>Finish</value>
</data>
<data name="FINISH_PAGE_TITLE_EXPORT" xml:space="preserve">
<value>Review the export settings</value>
</data>
<data name="FINISH_PAGE_TITLE_IMPORT" xml:space="preserve">
<value>Review the import settings</value>
</data>
<data name="FINISH_PAGE_TVM_DHCP" xml:space="preserve">
<value>Obtain automatically through DHCP</value>
</data>
<data name="FINISH_PAGE_TVM_GATEWAY" xml:space="preserve">
<value>Transfer VM gateway:</value>
</data>
<data name="FINISH_PAGE_TVM_IP" xml:space="preserve">
<value>Transfer VM IP address:</value>
</data>
<data name="FINISH_PAGE_TVM_MASK" xml:space="preserve">
<value>Transfer VM subnet mask:</value>
</data>
<data name="FINISH_PAGE_TVM_NETWORK" xml:space="preserve">
<value>Transfer VM network interface:</value>
</data>
<data name="FINISH_PAGE_VERIFY_MANIFEST" xml:space="preserve">
<value>Verify manifest content:</value>
</data>
<data name="FINISH_PAGE_VERIFY_SIGNATURE" xml:space="preserve">
<value>Verify digital signature:</value>
</data>
<data name="FINISH_PAGE_VMNAME" xml:space="preserve">
<value>VM name:</value>
</data>
<data name="FLOPPY_DRIVE_LABEL_NUMBERED" xml:space="preserve">
<value>Floppy Drive {0}:</value>
</data>
<data name="FOLDER" xml:space="preserve">
<value>Folder</value>
</data>
<data name="FOLDERS" xml:space="preserve">
<value>Folders</value>
</data>
<data name="FOLDER_ALREADY_EXISTS" xml:space="preserve">
<value>Folder with this name already exists</value>
</data>
2016-07-22 09:31:58 +02:00
<data name="FOLDER_BROWSER_BUG_TOOL" xml:space="preserve">
<value>Specify the folder where your report will be saved.</value>
</data>
<data name="FOLDER_BROWSER_DOWNLOAD_APPLIANCE" xml:space="preserve">
<value>Specify the folder where the files will be downloaded.</value>
</data>
<data name="FOLDER_BROWSER_EXPORT_APPLIANCE" xml:space="preserve">
<value>Specify the folder where the exported file(s) will be saved.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="FOLDER_NO_CONNECTION" xml:space="preserve">
<value>Connect to a server to create your folder</value>
</data>
<data name="FORCE_CLOSE" xml:space="preserve">
<value>&Force close</value>
</data>
<data name="FORCE_CLOSE_PLUGIN_PROMPT" xml:space="preserve">
<value>Plugin {0} has not yet responded to your cancel request. Would you like to force close the process or allow it to continue to run in the background?</value>
</data>
2014-12-04 09:35:36 +01:00
<data name="FORCE_ENABLE_RDP" xml:space="preserve">
2015-01-22 06:58:22 +01:00
<value>Would you like to configure this VM to accept Remote Desktop connections, and then connect to it over Remote Desktop?</value>
2014-12-04 09:35:36 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="FORCE_REBOOT" xml:space="preserve">
<value>Force Reboot</value>
</data>
<data name="FORGETTING_SRS" xml:space="preserve">
<value>Forgetting SRs</value>
</data>
<data name="FORGETTING_SR_0" xml:space="preserve">
<value>Forgetting SR {0}</value>
</data>
<data name="FORGET_SR" xml:space="preserve">
<value>&Forget</value>
</data>
<data name="FREESPACE" xml:space="preserve">
<value>Free Space</value>
</data>
<data name="FREE_MEMORY" xml:space="preserve">
<value>Free memory</value>
</data>
<data name="FRIDAY_LONG" xml:space="preserve">
<value>Friday</value>
</data>
<data name="FRIDAY_SHORT" xml:space="preserve">
<value>Fri</value>
</data>
<data name="FULLY_APPLIED" xml:space="preserve">
<value>Fully applied</value>
</data>
<data name="GALLERYSEARCHBAR_MATCHES" xml:space="preserve">
<value>{0} matches</value>
</data>
<data name="GENERAL_CPU_MODEL" xml:space="preserve">
<value>Model: {0}</value>
</data>
<data name="GENERAL_CPU_SPEED" xml:space="preserve">
<value>Speed: {0} MHz</value>
</data>
<data name="GENERAL_CPU_VENDOR" xml:space="preserve">
<value>Vendor: {0}</value>
</data>
<data name="GENERAL_DETAILS_CPU_NUMBER" xml:space="preserve">
<value>CPU {0}</value>
</data>
<data name="GENERAL_EDIT_INVALID_HOSTNAME" xml:space="preserve">
<value>You must give a valid server name.</value>
</data>
<data name="GENERAL_EDIT_INVALID_IQN" xml:space="preserve">
<value>You must give a valid IQN, e.g. iqn.2007-11.com.example.subdomain:optional-domain-specific-string</value>
</data>
<data name="GENERAL_EDIT_INVALID_NAME" xml:space="preserve">
<value>You must give a valid name.</value>
</data>
<data name="GENERAL_HEADING_BOOT_OPTIONS" xml:space="preserve">
<value>Boot Options</value>
</data>
<data name="GENERAL_HEADING_CPUS" xml:space="preserve">
<value>CPUs</value>
</data>
<data name="GENERAL_HEADING_LICENSE_DETAILS" xml:space="preserve">
<value>License Details</value>
</data>
<data name="GENERAL_HEADING_MEMORY" xml:space="preserve">
<value>Memory</value>
</data>
<data name="GENERAL_HEADING_MEMORY_VCPUS" xml:space="preserve">
<value>Memory and VCPUs</value>
</data>
<data name="GENERAL_HEADING_STATUS" xml:space="preserve">
<value>Status</value>
</data>
<data name="GENERAL_HEADING_UPDATES" xml:space="preserve">
<value>Updates</value>
</data>
<data name="GENERAL_HEADING_VERSION_DETAILS" xml:space="preserve">
<value>Version Details</value>
</data>
<data name="GENERAL_MEMORY" xml:space="preserve">
<value>Memory:</value>
</data>
<data name="GENERAL_MEMORY_SERVER" xml:space="preserve">
<value>Server:</value>
</data>
<data name="GENERAL_MEMORY_SERVER_FREE" xml:space="preserve">
<value>{0} available ({1} total)</value>
</data>
<data name="GENERAL_MEMORY_VM" xml:space="preserve">
<value>VMs:</value>
</data>
<data name="GENERAL_MEMORY_VM_USED" xml:space="preserve">
<value>{0}: using {1}</value>
</data>
<data name="GENERAL_MEMORY_VM_USED_PLUS_OVERHEAD" xml:space="preserve">
<value>{0}: using {1} + {2} overhead</value>
</data>
<data name="GENERAL_MULTIPATH_FAILURE" xml:space="preserve">
<value>Multipath Failure</value>
</data>
<data name="GENERAL_PAGE_KVP_SEPARATOR" xml:space="preserve">
<value>: </value>
</data>
<data name="GENERAL_PAGE_VMPP_SETTINGS" xml:space="preserve">
<value>Enter the VM Protection Policy name and an optional description.</value>
</data>
2016-10-10 04:29:22 +02:00
<data name="GENERAL_PAGE_VMSS_SETTINGS" xml:space="preserve">
<value>Enter the snapshot schedule name and an optional description.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="GENERAL_PAGE_VM_APPLIANCE_SETTINGS" xml:space="preserve">
<value>Enter the vApp name and an optional description.</value>
</data>
2016-08-17 11:45:11 +02:00
<data name="GENERAL_PANEL_UPDATE_KEY" xml:space="preserve">
<value>{0} on {1}</value>
</data>
2016-10-27 15:27:20 +02:00
<data name="GENERAL_PANEL_UPDATE_REBOOT_WARNING" xml:space="preserve">
2013-06-24 13:41:48 +02:00
<value>The server '{0}' needs to be rebooted for update '{1}' to take effect</value>
</data>
2016-10-27 15:27:20 +02:00
<data name="GENERAL_PANEL_UPDATE_RESTART_TOOLSTACK_WARNING" xml:space="preserve">
2016-10-31 15:18:43 +01:00
<value>The toolstack on server '{0}' needs to be restarted for update '{1}' to take effect</value>
2016-10-27 15:27:20 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="GENERAL_SR_CONTEXT_REPAIR" xml:space="preserve">
<value>Repair</value>
</data>
<data name="GENERAL_SR_STATE_BROKEN" xml:space="preserve">
<value>Broken</value>
</data>
2016-01-19 10:22:30 +01:00
<data name="GENERAL_STATE_OK" xml:space="preserve">
2013-06-24 13:41:48 +02:00
<value>OK</value>
</data>
<data name="GENERAL_UNKNOWN" xml:space="preserve">
<value>Not Found</value>
</data>
<data name="GETPASSWORD" xml:space="preserve">
<value>Get Password</value>
</data>
<data name="GPU" xml:space="preserve">
<value>GPU</value>
</data>
2013-11-14 12:41:05 +01:00
<data name="GPU_EDIT_ALLOWED_TYPES_MULTIPLE" xml:space="preserve">
<value>&Edit Selected GPUs...</value>
</data>
<data name="GPU_EDIT_ALLOWED_TYPES_SINGLE" xml:space="preserve">
<value>&Edit...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="GPU_GROUP_NAME_AND_NO_OF_GPUS" xml:space="preserve">
<value>{0} ({1} GPUs)</value>
</data>
<data name="GPU_GROUP_NAME_AND_NO_OF_GPUS_ONE" xml:space="preserve">
<value>{0} (1 GPU)</value>
</data>
<data name="GPU_NONE" xml:space="preserve">
<value>None</value>
</data>
2013-11-14 12:23:35 +01:00
<data name="GPU_ON_HOST_LABEL" xml:space="preserve">
<value>On {0}:</value>
</data>
2013-11-14 12:15:52 +01:00
<data name="GPU_PLACEMENT_POLICY_DESCRIPTION" xml:space="preserve">
<value>Placement policy: {0}</value>
</data>
2013-11-14 11:35:48 +01:00
<data name="GPU_PLACEMENT_POLICY_MAX_DENSITY" xml:space="preserve">
<value>Maximum density</value>
</data>
2013-11-14 12:15:52 +01:00
<data name="GPU_PLACEMENT_POLICY_MAX_DENSITY_DESCRIPTION" xml:space="preserve">
<value>Maximum density: put as many VMs as possible on the same GPU</value>
</data>
2013-11-14 11:35:48 +01:00
<data name="GPU_PLACEMENT_POLICY_MAX_PERFORMANCE" xml:space="preserve">
<value>Maximum performance</value>
</data>
2013-11-14 12:15:52 +01:00
<data name="GPU_PLACEMENT_POLICY_MAX_PERFORMANCE_DESCRIPTION" xml:space="preserve">
<value>Maximum performance: put VMs on as many GPUs as possible</value>
</data>
<data name="GPU_PLACEMENT_POLICY_MIXED" xml:space="preserve">
<value>Mixed</value>
</data>
<data name="GPU_PLACEMENT_POLICY_MIXED_DESCRIPTION" xml:space="preserve">
<value>Mixed: different settings for different GPU groups</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="GPU_RUBRIC_NO_GPUS_POOL" xml:space="preserve">
<value>You can improve graphics performance by assigning a dedicated graphics processing unit (GPU) to a VM. However, no GPUs have been detected in this pool, so this option is not currently available.</value>
</data>
<data name="GPU_RUBRIC_NO_GPUS_SERVER" xml:space="preserve">
<value>You can improve graphics performance by assigning a dedicated graphics processing unit (GPU) to a VM. However, no GPUs have been detected in this server, so this option is not currently available.</value>
</data>
2013-11-14 12:11:24 +01:00
<data name="GPU_RUBRIC_PLEASE_SELECT_WHICH_GPU_MULTIPLE" xml:space="preserve">
2015-03-30 17:21:46 +02:00
<value>Select which virtual GPU types are allowed on these GPUs:</value>
2013-11-14 12:11:24 +01:00
</data>
<data name="GPU_RUBRIC_PLEASE_SELECT_WHICH_GPU_ONE" xml:space="preserve">
2015-03-30 17:21:46 +02:00
<value>Select which virtual GPU types are allowed on this GPU:</value>
2013-11-14 12:11:24 +01:00
</data>
2013-11-14 12:32:51 +01:00
<data name="GPU_UNAVAILABLE" xml:space="preserve">
<value>Not available</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="GRAPHS_CANNOT_ADD_VM_HALTED" xml:space="preserve">
<value>It is not possible to add new performance graphs on VM '{0}' as the VM is not running.</value>
</data>
<data name="GRAPHS_CANNOT_EDIT_VM_HALTED" xml:space="preserve">
<value>It is not possible to edit performance graphs on VM '{0}' as the VM is not running.</value>
</data>
<data name="GRAPHS_DEFAULT_NAME_CPU" xml:space="preserve">
<value>CPU Performance</value>
</data>
<data name="GRAPHS_DEFAULT_NAME_DISK" xml:space="preserve">
<value>Disk Performance</value>
</data>
<data name="GRAPHS_DEFAULT_NAME_MEMORY" xml:space="preserve">
<value>Memory Performance</value>
</data>
<data name="GRAPHS_DEFAULT_NAME_NETWORK" xml:space="preserve">
<value>Network Performance</value>
</data>
<data name="GRAPHS_DETAILS_TITLE" xml:space="preserve">
<value>'{0}' Details</value>
</data>
<data name="GRAPHS_EDIT" xml:space="preserve">
<value>Edit Graph...</value>
</data>
<data name="GRAPHS_NEW" xml:space="preserve">
<value>New Graph...</value>
</data>
<data name="GRAPHS_NEW_TITLE" xml:space="preserve">
<value>New Graph</value>
</data>
<data name="GRAPHS_NO_DATA" xml:space="preserve">
<value>no data</value>
</data>
<data name="GRAPHS_RESTORE_DEFAULT_MESSAGE" xml:space="preserve">
<value>Are you sure you want to restore the default graphs? This operation will delete existing graphs and cannot be undone.
Note: Any custom color selections will remain unchanged</value>
</data>
<data name="GRAPH_LOADING" xml:space="preserve">
<value>Loading Data...</value>
</data>
2016-11-10 15:42:45 +01:00
<data name="GRAPH_NAME" xml:space="preserve">
<value>Performance Graph</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="GRAPH_NEEDS_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>To view memory data for this VM, you need to install [XenServer product] Tools</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="GREATER_THAN" xml:space="preserve">
<value>> {0}</value>
</data>
<data name="GROUP" xml:space="preserve">
<value>Group</value>
</data>
<data name="GROUP_ROLES" xml:space="preserve">
<value>Group Roles</value>
</data>
<data name="GUI_OUT_OF_DATE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>This version of [XenCenter] is out of date and cannot connect to {0}.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="GUI_OUT_OF_DATE_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
You can get a compatible version of [XenCenter] from the following location:</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="HA" xml:space="preserve">
<value>HA</value>
</data>
<data name="HAPANEL_BLURB" xml:space="preserve">
<value>HA is not currently enabled for pool '{0}'.
Click Configure HA to enable HA for this pool and allow your virtual machines to be automatically restarted in the event of unexpected server failure.</value>
</data>
<data name="HAS_CUSTOM_FIELDS" xml:space="preserve">
<value>Has any custom field</value>
</data>
2015-10-26 17:01:55 +01:00
<data name="HAWIZARD_ASSIGNPRIORITIESPAGE_TEXT" xml:space="preserve">
2013-06-24 13:41:48 +02:00
<value>HA Plan</value>
</data>
2015-10-26 17:01:55 +01:00
<data name="HAWIZARD_ASSIGNPRIORITIESPAGE_TITLE" xml:space="preserve">
2013-06-24 13:41:48 +02:00
<value>Configure the HA restart priority, restart order and delay interval for the VMs in this pool</value>
</data>
<data name="HA_ASSIGN_PRIORITIES_MIXED_PROTECTION_LEVELS" xml:space="preserve">
<value>(Multiple values)</value>
</data>
<data name="HA_ASSIGN_PRIORITIES_NO_VMS_SELECTED" xml:space="preserve">
<value>No VMs selected.</value>
</data>
<data name="HA_BUTTON_TOOLTIP_STILL_CALCULATING" xml:space="preserve">
<value>Please wait while the HA wizard determines the agility of your VMs</value>
</data>
<data name="HA_CALCULATING_AGILITY" xml:space="preserve">
<value>Calculating...</value>
</data>
<data name="HA_CANNOT_EDIT_WITH_DEAD_HOSTS" xml:space="preserve">
<value>In order to edit the HA restart priorities of your virtual machines, all servers in the pool must be live. The following servers are not currently live:
{0}</value>
</data>
<data name="HA_CANNOT_EDIT_WITH_DEAD_HOSTS_SHORT" xml:space="preserve">
<value>HA is currently enabled for pool {0}. To edit VM restart priorities, all servers in the pool must be reachable.</value>
</data>
<data name="HA_CANNOT_EDIT_WITH_DEAD_HOSTS_WRAPPED" xml:space="preserve">
<value>In order to edit the HA restart priorities of your virtual machine,
all servers in the pool must be live. The following servers are
not currently live:
{0}</value>
</data>
<data name="HA_CANNOT_EVACUATE_MASTER" xml:space="preserve">
<value>Server '{0}' can not be placed in Maintenance Mode because it is the master of an HA-enabled pool.</value>
</data>
<data name="HA_CHECK_DESCRIPTION" xml:space="preserve">
<value>HA and WLB check</value>
</data>
<data name="HA_CHOOSESR_PAGE_PAGETITLE" xml:space="preserve">
<value>Choose a heartbeat SR</value>
</data>
<data name="HA_CHOOSESR_PAGE_TEXT" xml:space="preserve">
<value>Heartbeat SR</value>
</data>
<data name="HA_CONFIGURATION_TITLE" xml:space="preserve">
<value>Configuration</value>
</data>
<data name="HA_CONFIGURED" xml:space="preserve">
<value>HA is currently configured on pool '{0}' with these settings:</value>
</data>
<data name="HA_CONFIGURED_CAPACITY" xml:space="preserve">
<value>Configured failure capacity:</value>
</data>
<data name="HA_CONFIGURE_NOW" xml:space="preserve">
<value>Configure HA now...</value>
</data>
<data name="HA_CONFIRM_FORCESHUTDOWN_VM" xml:space="preserve">
<value>The selected VM is currently protected by HA. Are you sure you want to force the shut down of this VM? This operation will cancel all running tasks for the VM and can result in data loss.</value>
</data>
<data name="HA_CONFIRM_FORCESHUTDOWN_VMS" xml:space="preserve">
<value>At least one of the selected VMs is currently protected by HA. Are you sure you want to forcibly shut down the selected VMs? This operation will cancel all running tasks for each of the selected VMs and can result in data loss.</value>
</data>
<data name="HA_CONFIRM_FORCESHUTDOWN_VMS_NO_CANCEL_TASKS" xml:space="preserve">
<value>At least one of the selected VMs is currently protected by HA. Are you sure you want to forcibly shut down the selected VMs? This operation can result in data loss.</value>
</data>
<data name="HA_CONFIRM_FORCESHUTDOWN_VM_NO_CANCEL_TASKS" xml:space="preserve">
2013-09-11 18:44:55 +02:00
<value>The selected VM is currently protected by HA. Are you sure you want to force the shut down of this VM? This operation can result in data loss.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="HA_CONFIRM_SHUTDOWN_VM" xml:space="preserve">
<value>The selected VM is currently protected by HA. Are you sure you want to shut it down?</value>
</data>
<data name="HA_CONFIRM_SUSPEND_VM" xml:space="preserve">
<value>The selected VM is currently protected by HA. Are you sure you want to suspend it?</value>
</data>
<data name="HA_CURRENT_CAPACITY" xml:space="preserve">
<value>Current failure capacity:</value>
</data>
<data name="HA_DISABLE_QUERY" xml:space="preserve">
<value>Are you sure you want to disable HA for pool '{0}'?</value>
</data>
<data name="HA_EDIT_DIALOG_BLURB" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] High Availability (HA) allows virtual machines to automatically be restarted in the event of an underlying hardware failure or loss of an individual server. HA is enabled for '{0}'.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="HA_EDIT_NOW" xml:space="preserve">
<value>Change these HA settings now...</value>
</data>
<data name="HA_GUARANTEED_MESSAGE" xml:space="preserve">
<value>HA is guaranteed. The maximum number of server failures that HA can protect against is {0}.</value>
</data>
<data name="HA_HEARTBEAT_HEALTHY" xml:space="preserve">
<value>Healthy</value>
</data>
<data name="HA_HEARTBEAT_SERVERS" xml:space="preserve">
<value>{0} out of {1} servers</value>
</data>
<data name="HA_HEARTBEAT_SR" xml:space="preserve">
<value>HA Heartbeat SR</value>
</data>
<data name="HA_HEARTBEAT_UNHEALTHY" xml:space="preserve">
<value>Error</value>
</data>
<data name="HA_HOSTS_LACK_LICENSE" xml:space="preserve">
<value>The following servers do not have a license that permits HA:
{0}</value>
</data>
<data name="HA_HOST_DISABLE_NTOL_DROP" xml:space="preserve">
<value>Pool '{0}' has HA enabled, and failover tolerance is currently {1}. You cannot put server '{2}' into maintenance mode
and keep this configuration. Do you want to reduce the failover tolerance to {3} and continue?</value>
</data>
<data name="HA_HOST_DISABLE_NTOL_ZERO" xml:space="preserve">
<value>Pool '{0}' has HA enabled. If you put server '{1}' into maintenance mode, HA would no longer be guaranteed for this pool.
Are you sure you want to continue?</value>
</data>
<data name="HA_HOST_ENABLE_NTOL_RAISE_QUERY" xml:space="preserve">
<value>Pool '{0}' has HA enabled. You have just taken server '{1}' out of maintenance mode, and may now increase the pool's failover tolerance from {2} to {3}. Would you like to do this?</value>
</data>
<data name="HA_HOST_REBOOT_NTOL_DROP" xml:space="preserve">
<value>Pool '{0}' has HA enabled, and failover tolerance is currently {1}. You cannot reboot server '{2}' and keep this configuration.
Do you want to reduce the failover tolerance to {3} and continue?</value>
</data>
<data name="HA_HOST_REBOOT_NTOL_ZERO" xml:space="preserve">
<value>Pool '{0}' has HA enabled. If you reboot server '{1}', HA will no longer be guaranteed.
Are you sure you want to continue?</value>
</data>
<data name="HA_HOST_SHUTDOWN_NTOL_DROP" xml:space="preserve">
<value>Pool '{0}' has HA enabled, and failover tolerance is currently {1}. You cannot shut down server '{2}' and keep this configuration.
Do you want to reduce the failover tolerance to {3} and continue?</value>
</data>
<data name="HA_HOST_SHUTDOWN_NTOL_ZERO" xml:space="preserve">
<value>Pool '{0}' has HA enabled. If you shut down server '{1}', HA will no longer be guaranteed.
Are you sure you want to continue?</value>
</data>
<data name="HA_INTRO_PAGE_TITLE" xml:space="preserve">
<value>HA configuration prerequisites</value>
</data>
<data name="HA_INTRO_TEXT" xml:space="preserve">
<value>Prerequisites</value>
</data>
<data name="HA_INVALID_CONFIG_RESUME" xml:space="preserve">
<value>VM '{0}' has an invalid HA configuration that prevents it from being resumed. It is necessary to clear the VM's HA configuration to proceed.
Would you like to clear the VM's HA restart priority?</value>
</data>
<data name="HA_INVALID_CONFIG_START" xml:space="preserve">
<value>VM '{0}' has an invalid HA configuration that prevents it from starting. It is necessary to clear the VM's HA configuration to proceed.
Would you like to clear the VM's HA restart priority?</value>
</data>
<data name="HA_LICENSE_DISABLED" xml:space="preserve">
<value>The server does not have a license permitting HA.</value>
</data>
<data name="HA_LOWERING_NTOL" xml:space="preserve">
<value>Lowering failover tolerance and retrying</value>
</data>
<data name="HA_NOT_CONFIGURED" xml:space="preserve">
<value>HA is not currently configured on pool '{0}'.</value>
</data>
<data name="HA_NO_SHARED_SRS" xml:space="preserve">
<value>You have no shared SRs.</value>
</data>
<data name="HA_NTOL_BLURB" xml:space="preserve">
<value>The number of server failures that could be tolerated in this pool given these HA restart priorities is {0}.
Increasing the slack allows other users to start or reconfigure VMs without affecting the plan.</value>
</data>
<data name="HA_NTOL_UNKNOWN" xml:space="preserve">
<value>The number of server failures that can be tolerated could not be determined. Check the logs for more information.</value>
</data>
<data name="HA_NTOL_ZERO" xml:space="preserve">
<value>This pool cannot support the specified HA restart priorities and tolerate any server failures.</value>
</data>
<data name="HA_NTOL_ZERO_HAPAGE" xml:space="preserve">
<value>0 - HA cannot guarantee to restart your protected VMs after server failure</value>
</data>
<data name="HA_NTOL_ZERO_QUERY" xml:space="preserve">
<value>Under this HA configuration, the failover tolerance of your pool would be 0 (zero) and it may not be possible to restart your virtual machines in the event of a server failure.
Do you want to apply this HA configuration anyway?</value>
</data>
<data name="HA_OPTION_DO_NOT_RESTART" xml:space="preserve">
<value>Do not restart</value>
</data>
<data name="HA_OPTION_RESTART_IF_POSS" xml:space="preserve">
<value>Restart if possible</value>
</data>
<data name="HA_OPT_DISABLE_NTOL_DROP" xml:space="preserve">
<value>Pool '{0}' has HA enabled, and is currently configured to tolerate {1} server failures. You cannot relocate VM '{2}' and still tolerate this number of failures. Do you want to reduce the number of tolerable failures to {3} and try again?</value>
</data>
<data name="HA_OPT_ENABLE_NTOL_RAISE_QUERY" xml:space="preserve">
<value>Pool '{0}' has HA enabled. The pool optimization has been stopped. You may now increase the pool's failover tolerance from {1} to {2}. Would you like to do this?</value>
</data>
<data name="HA_OPT_VM_RELOCATE_NTOL_ZERO" xml:space="preserve">
<value>Pool '{0}' has HA enabled. If you relocate VM '{1}', the pool will not be able to tolerate any further server failures, and your HA configuration would no longer be able to restart your protected VMs. To perform the action anyway, turn off HA.</value>
</data>
<data name="HA_OVERCOMMITTED_NTOL" xml:space="preserve">
<value>{0} - pool is overcommitted</value>
</data>
<data name="HA_OVERCOMMIT_BLURB" xml:space="preserve">
<value>When overcommited the pool cannot guarantee to tolerate the number of server failures specified.
Reduce protection levels, or bring more servers online to increase the maximum supported capacity.</value>
</data>
<data name="HA_OVERCOMMIT_MESSAGE" xml:space="preserve">
<value>HA cannot be guaranteed with the specified settings and the current pool resources.</value>
</data>
<data name="HA_OVERCOMMIT_WARNING" xml:space="preserve">
<value>The number of servers you specified is greater than the maximum failover capacity ({0}). HA cannot be guaranteed if you allow this many server failures, given the specified VM restart priorities and the current pool configuration (number of servers and their CPU and memory capacity).</value>
</data>
<data name="HA_OVERCOMMIT_WARNING_NONE" xml:space="preserve">
<value>Maximum failover capacity is 0: HA cannot be guaranteed with the specified VM restart priorities and the current pool configuration (number of servers and their CPU and memory capacity).</value>
</data>
<data name="HA_PAGE_DISABLING" xml:space="preserve">
2013-10-08 15:51:39 +02:00
<value>HA is currently being disabled for '{0}'.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="HA_PAGE_ENABLING" xml:space="preserve">
2013-10-08 15:51:39 +02:00
<value>HA is currently being enabled for '{0}'.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="HA_RESTART_PRIORITY" xml:space="preserve">
<value>HA restart priority</value>
</data>
<data name="HA_SAVE_SETTINGS_FAILED_DEAD_HOSTS" xml:space="preserve">
<value>Your changes to HA settings for pool '{0}' may not take effect because not all servers in the pool are reachable. Ensure that all servers in the pool are reachable and then apply the changes again.</value>
</data>
<data name="HA_SCANNING_SRS" xml:space="preserve">
<value>Scanning for HA heartbeat SRs on {0}</value>
</data>
<data name="HA_SETTING_PRIORITIES" xml:space="preserve">
<value>Setting HA protection levels</value>
</data>
<data name="HA_SETTING_PRIORITY_ON_X" xml:space="preserve">
<value>Setting HA restart priority on {0}</value>
</data>
<data name="HA_SRS_BROKEN_WARNING" xml:space="preserve">
<value>The following SRs are broken. It is recommended you fix them before enabling HA.
{0}</value>
</data>
<data name="HA_STANDALONE_SERVER" xml:space="preserve">
<value>HA is not available on standalone servers.</value>
</data>
<data name="HA_TAB_CONFIGURED_BLURB" xml:space="preserve">
<value>HA is currently enabled for pool '{0}'.
Click Configure HA to alter the settings displayed below.</value>
</data>
<data name="HA_UNABLE_TO_CALCULATE_MESSAGE" xml:space="preserve">
<value>Unable to calculate maximum pool failure capacity.</value>
</data>
<data name="HA_VM_RESUME_NTOL_DROP" xml:space="preserve">
<value>Pool '{0}' has HA enabled, and is currently configured to tolerate {1} server failures. You cannot resume VM '{2}' and still tolerate this number of failures. Do you want to reduce the number of tolerable failures to {3} and try again?</value>
</data>
<data name="HA_VM_RESUME_NTOL_ZERO" xml:space="preserve">
<value>Pool '{0}' has HA enabled. If you resume VM '{1}', the pool will not be able to tolerate any further server failures, and your HA configuration would no longer be able to restart your protected VMs. To perform the action anyway, turn off HA.</value>
</data>
<data name="HA_VM_START_NTOL_DROP" xml:space="preserve">
<value>Pool '{0}' has HA enabled, and is currently configured to tolerate {1} server failures. You cannot start VM '{2}' and still tolerate this number of failures. Do you want to reduce the number of tolerable failures to {3} and try again?</value>
</data>
<data name="HA_VM_START_NTOL_ZERO" xml:space="preserve">
<value>Pool '{0}' has HA enabled. If you start VM '{1}', the pool will not be able to tolerate any further server failures, and your HA configuration would no longer be able to restart your protected VMs. To perform the action anyway, turn off HA.</value>
</data>
<data name="HA_WAS_DISABLED" xml:space="preserve">
<value>HA has been disabled on pool '{0}'.</value>
</data>
<data name="HA_WIZARD_FINISH_PAGE_TITLE" xml:space="preserve">
<value>Review configuration and activate HA</value>
</data>
2015-07-29 09:44:41 +02:00
<data name="HEALTHCHECK_AUTHENTICATION_RUBRIC_EXISTING_TOKEN" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Authentication with [Citrix] Insight Services is required in order to enable this feature. [XenCenter] detected a previous successful authentication for one of other connected pools. You can choose to re-use it or authenticate again.</value>
2015-07-29 09:44:41 +02:00
</data>
<data name="HEALTHCHECK_AUTHENTICATION_RUBRIC_NO_TOKEN" xml:space="preserve">
2017-02-09 16:16:11 +01:00
<value>Authentication with [Citrix] Insight Services is required in order to enable this feature. Please register by providing MyCitrix credentials (see {0}). These credentials will only be used to obtain an upload token and will not be stored on this machine or on your server.</value>
2015-07-29 09:44:41 +02:00
</data>
<data name="HEALTHCHECK_ENROLLMENT_CONFIRMATION_BUTTON_LABEL" xml:space="preserve">
<value>OK, Enable Health Check</value>
</data>
<data name="HEALTHCHECK_ENROLLMENT_TITLE" xml:space="preserve">
<value>Health Check Enrollment - {0}</value>
</data>
2015-06-30 11:04:16 +02:00
<data name="HEALTHCHECK_ON_DEMAND_REQUEST" xml:space="preserve">
2015-09-08 11:59:56 +02:00
<value>Request an additional upload now</value>
2015-06-30 11:04:16 +02:00
</data>
<data name="HEALTHCHECK_ON_DEMAND_REQUESTED_AT" xml:space="preserve">
2015-09-08 11:59:56 +02:00
<value>Additional upload requested at {0}</value>
2015-06-30 11:04:16 +02:00
</data>
2015-07-29 09:44:41 +02:00
<data name="HEALTHCHECK_SCHEDULE_DESCRIPTION" xml:space="preserve">
<value>Upload a Health Check report every {0} weeks on {1} starting at {2}</value>
</data>
<data name="HEALTHCHECK_STATUS_ISSUES_FOUND" xml:space="preserve">
2015-08-27 01:30:02 +02:00
<value>{0} issues detected</value>
2015-07-29 09:44:41 +02:00
</data>
<data name="HEALTHCHECK_STATUS_NOT_AVAILABLE_YET" xml:space="preserve">
<value>Analysis not yet available</value>
</data>
<data name="HEALTHCHECK_STATUS_NOT_ENROLLED" xml:space="preserve">
<value>Health Check not enabled</value>
</data>
<data name="HEALTHCHECK_STATUS_NO_ISSUES_FOUND" xml:space="preserve">
2015-08-27 01:30:02 +02:00
<value>No issues detected</value>
</data>
<data name="HEALTHCHECK_STATUS_NO_UPLOAD_YET" xml:space="preserve">
<value>No report uploaded yet</value>
</data>
<data name="HEALTHCHECK_STATUS_ONE_ISSUE_FOUND" xml:space="preserve">
<value>1 issue detected</value>
2015-07-29 09:44:41 +02:00
</data>
2015-07-24 10:01:04 +02:00
<data name="HEALTH_CHECK_AUTHENTICATION_FAILED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Authentication with [Citrix] Insight Services failed. See the application log files for more information.</value>
2015-07-24 10:01:04 +02:00
</data>
<data name="HEALTH_CHECK_AUTHENTICATION_INVALID_CREDENTIALS" xml:space="preserve">
2016-12-16 19:36:35 +01:00
<value>Invalid user name or password. Please try again.</value>
2015-07-24 10:01:04 +02:00
</data>
2015-11-09 23:34:32 +01:00
<data name="HEALTH_CHECK_USER_HAS_NO_PERMISSION_TO_CONNECT" xml:space="preserve">
<value>This user is not authorized to access this server.</value>
</data>
2015-09-15 14:48:50 +02:00
<data name="HEALTH_CHECK_USER_NOT_AUTHORIZED" xml:space="preserve">
<value>This user is not authorized to perform Health Check operations.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="HEARTBEATING_STATUS" xml:space="preserve">
<value>Heartbeating status</value>
</data>
<data name="HELP" xml:space="preserve">
<value>Help</value>
</data>
<data name="HELP_MESSAGE_DISABLE_WLB" xml:space="preserve">
2014-04-22 13:14:53 +02:00
<value>Pause WLB</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="HIDE_DETAILS" xml:space="preserve">
<value>Hide Details</value>
</data>
<data name="HIDE_RUN_HISTORY" xml:space="preserve">
<value>Hide Run History</value>
</data>
<data name="HIGH_AVAILABILITY" xml:space="preserve">
<value>High Availability</value>
</data>
2013-08-10 13:29:36 +02:00
<data name="HISTORYPAGE_GOTO" xml:space="preserve">
<value>Go to...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="HISTORYPANEL_COPY_FORMAT" xml:space="preserve">
<value>{3} {0}: {1} - {2}</value>
</data>
<data name="HISTORYROW_DETAILS" xml:space="preserve">
<value>Details: </value>
</data>
<data name="HISTORYROW_ERROR" xml:space="preserve">
<value>Error: </value>
</data>
<data name="HISTORYROW_ON" xml:space="preserve">
<value>On {0}, {1}</value>
</data>
<data name="HISTORYROW_ON_WITH" xml:space="preserve">
<value>On {0}, with {1}, {2}</value>
</data>
<data name="HISTORYROW_PROGRESS" xml:space="preserve">
<value>Progress:</value>
</data>
<data name="HISTORYROW_TIME" xml:space="preserve">
<value>Time:</value>
</data>
<data name="HISTORYROW_WITH" xml:space="preserve">
<value>With {0}, {1}</value>
</data>
<data name="HISTORY_FOR_POLICY" xml:space="preserve">
<value>Run history for policy '{0}':</value>
</data>
<data name="HOMEPAGE_ERROR_MESSAGE" xml:space="preserve">
<value>The default web browser could not be started.</value>
</data>
<data name="HOMESERVER_PICKER_HOST_NOT_LIVE" xml:space="preserve">
<value>This server cannot be contacted</value>
<comment>HOMESERVER_PICKER_HOST_NOT_LIVE description</comment>
</data>
<data name="HOME_SERVER" xml:space="preserve">
<value>Home Server</value>
</data>
<data name="HOME_SERVER_MENU_ITEM" xml:space="preserve">
<value>&Home Server</value>
</data>
<data name="HOSTACTION_EVACUATED" xml:space="preserve">
<value>Server '{0}' entered maintenance mode</value>
</data>
<data name="HOSTACTION_EVACUATING" xml:space="preserve">
<value>Server '{0}' entering maintenance mode...</value>
</data>
<data name="HOSTACTION_EXITED_MAINTENANCE_MODE" xml:space="preserve">
<value>Server '{0}' exited maintenance mode</value>
</data>
<data name="HOSTACTION_EXITING_MAINTENANCE_MODE" xml:space="preserve">
<value>Server '{0}' exiting maintenance mode...</value>
</data>
<data name="HOSTACTION_REBOOT_VM_SHUTDOWN" xml:space="preserve">
<value>Preparing to reboot server: shutting down {0} ({1} of {2})</value>
</data>
<data name="HOSTACTION_SHUTDOWN_VM_SHUTDOWN" xml:space="preserve">
<value>Preparing to shut down server: shutting down {0} ({1} of {2})</value>
</data>
<data name="HOSTACTION_TRANSITIONED_NEW_MASTER" xml:space="preserve">
<value>Nominated server {0} as new master</value>
</data>
<data name="HOSTACTION_TRANSITIONING_NEW_MASTER" xml:space="preserve">
<value>Nominating server {0} as new master...</value>
</data>
<data name="HOST_ACTION_IN_PROGRESS" xml:space="preserve">
<value>This server has an operation in progress.</value>
</data>
<data name="HOST_ALREADY_IN_POOL" xml:space="preserve">
<value>Cannot add server {0} to pool {1}: server is already in pool {2}.</value>
</data>
<data name="HOST_ALREADY_POWERED_ON" xml:space="preserve">
<value>This server is already powered on.</value>
</data>
<data name="HOST_ALREADY_SHUT_DOWN" xml:space="preserve">
<value>This server is already shut down.</value>
</data>
<data name="HOST_BACKEDUP" xml:space="preserve">
<value>Server '{0}' backed up.</value>
</data>
<data name="HOST_DISABLE" xml:space="preserve">
<value>Server entering maintenance mode</value>
</data>
<data name="HOST_ENABLE" xml:space="preserve">
<value>Server exiting maintenance mode</value>
</data>
<data name="HOST_EVACUATE" xml:space="preserve">
<value>Server entering maintenance mode</value>
</data>
<data name="HOST_GENERAL_TAB_TITLE" xml:space="preserve">
<value>Server General Properties</value>
</data>
<data name="HOST_INTERNAL_MANAGEMENT_NETWORK" xml:space="preserve">
<value>Host internal management network</value>
</data>
<data name="HOST_IN_MAINTENANCE_MODE" xml:space="preserve">
<value>In maintenance mode</value>
</data>
<data name="HOST_LIVENESS_CHECK_DESCRIPTION" xml:space="preserve">
<value>Host liveness check</value>
</data>
<data name="HOST_LOG_DESTINATION_LOCAL" xml:space="preserve">
<value>Local</value>
</data>
<data name="HOST_MENU_ADD_SERVER" xml:space="preserve">
<value>{0} (License restriction)</value>
</data>
<data name="HOST_MENU_ADD_TO_POOL" xml:space="preserve">
<value>Add to &Pool</value>
</data>
<data name="HOST_MENU_ADD_TO_POOL_CONTEXT_MENU" xml:space="preserve">
<value>Add to P&ool</value>
</data>
<data name="HOST_MENU_ADD_TO_POOL_LICENSE_RESTRICTION" xml:space="preserve">
<value>Add to &Pool (License restriction)</value>
</data>
<data name="HOST_MENU_COMPLETE_FAILURE" xml:space="preserve">
<value>(Error generating menu)</value>
</data>
2016-08-01 10:25:10 +02:00
<data name="HOST_MENU_CONTROL_DOMAIN_MEMORY" xml:space="preserve">
<value>Control &Domain Memory...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="HOST_MENU_CPM_TEXT" xml:space="preserve">
<value>&Migrate VM wizard...</value>
</data>
<data name="HOST_MENU_CURRENT_SERVER" xml:space="preserve">
<value>Current server</value>
</data>
<data name="HOST_MENU_EMPTY" xml:space="preserve">
<value>(empty)</value>
</data>
<data name="HOST_MENU_IMPORT_VM_TEXT" xml:space="preserve">
<value>&Import...</value>
</data>
<data name="HOST_MENU_UNKNOWN_ERROR" xml:space="preserve">
<value>Unknown error</value>
</data>
2016-10-19 14:10:24 +02:00
<data name="HOST_NEEDS_REBOOT_CHECK_DESCRIPTION" xml:space="preserve">
<value>Live patching status</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="HOST_NETWORK_TAB_ADD_BUTTON_LABEL" xml:space="preserve">
<value>&Add Network...</value>
</data>
<data name="HOST_NETWORK_TAB_EDIT_BUTTON_LABEL" xml:space="preserve">
<value>P&roperties</value>
</data>
<data name="HOST_NETWORK_TAB_REMOVE_BUTTON_LABEL" xml:space="preserve">
<value>R&emove Network</value>
</data>
<data name="HOST_NETWORK_TAB_TITLE" xml:space="preserve">
<value>Server Networks</value>
</data>
<data name="HOST_NOT_LIVE" xml:space="preserve">
<value>Server is not reachable</value>
</data>
<data name="HOST_NO_CRASHDUMPS" xml:space="preserve">
<value>No crashdumps to remove</value>
</data>
<data name="HOST_POWER_ON" xml:space="preserve">
<value>Server power on</value>
</data>
<data name="HOST_POWER_ON_MODE_NOT_SET" xml:space="preserve">
<value>This host does not have its Power On mode set.</value>
</data>
<data name="HOST_REBOOTED_SAME_VERSION" xml:space="preserve">
<value>Upgrade failed. The server rebooted with the same version.</value>
</data>
<data name="HOST_REBOOTING" xml:space="preserve">
<value>Rebooting server</value>
</data>
<data name="HOST_REBOOT_REQUIRED" xml:space="preserve">
<value>You must reboot your server '{0}' to complete the restore process.</value>
</data>
<data name="HOST_REMOVED_MANY_CRASHDUMPS" xml:space="preserve">
<value>Removed {0} crashdumps from {1}</value>
</data>
<data name="HOST_REMOVED_ONE_CRASHDUMP" xml:space="preserve">
<value>Removed 1 crashdump from {0}</value>
</data>
<data name="HOST_REMOVING_CRASHDUMP" xml:space="preserve">
<value>Removing crashdump {0} of {1} from {2}</value>
</data>
<data name="HOST_REMOVING_CRASHDUMPS_TITLE" xml:space="preserve">
<value>Removing crashdumps from {0}</value>
</data>
<data name="HOST_RESTORED" xml:space="preserve">
<value>Server '{0}' restored.</value>
</data>
<data name="HOST_SEES_NO_STORAGE" xml:space="preserve">
<value>This server cannot see any storage</value>
</data>
<data name="HOST_SHUTDOWN" xml:space="preserve">
<value>Shut down server</value>
</data>
<data name="HOST_X" xml:space="preserve">
<value>Host '{0}':</value>
</data>
<data name="HOTFIX_CHECK" xml:space="preserve">
<value>Hotfix check</value>
</data>
<data name="HOURLY_SCHEDULE_FORMAT" xml:space="preserve">
<value>Hourly; at {0} minutes past each hour</value>
</data>
<data name="HYPHEN" xml:space="preserve">
<value>-</value>
</data>
<data name="ID" xml:space="preserve">
<value>ID</value>
</data>
<data name="IGNORE_BUTTON_LABEL" xml:space="preserve">
<value>&Ignore</value>
</data>
<data name="ILO_CONNECTION_ERROR" xml:space="preserve">
<value>It is not possible to connect to the iLO service. Please review your configuration.</value>
</data>
<data name="ILO_POWERON_FAILED" xml:space="preserve">
2017-03-07 17:42:41 +01:00
<value>The iLO power-on request failed</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="IMAGE_DEFINITION_PAGE_TEXT" xml:space="preserve">
<value>VM Definition</value>
</data>
<data name="IMAGE_DEFINITION_PAGE_TITLE" xml:space="preserve">
<value>Define Virtual Machine</value>
</data>
<data name="IMAGE_SELECTION_PAGE_ERROR_CORRUPT_FILE" xml:space="preserve">
<value>The selected virtual hard disk image file is corrupt.</value>
</data>
<data name="IMAGE_SELECTION_PAGE_ERROR_INVALID_FILE_TYPE" xml:space="preserve">
<value>The selected file is not a valid virtual hard disk image file.</value>
</data>
<data name="IMAGE_SELECTION_PAGE_ERROR_INVALID_VMDK_DESCRIPTOR" xml:space="preserve">
<value>The selected file is a VMDK data file. Please select a VMDK descriptor file instead.</value>
</data>
<data name="IMPORTING" xml:space="preserve">
<value>Importing</value>
</data>
<data name="IMPORTING_DISK_IMAGE" xml:space="preserve">
<value>Importing Disk Image...</value>
</data>
<data name="IMPORTING_VMS" xml:space="preserve">
<value>Importing VMs...</value>
</data>
<data name="IMPORTVM_DESCRIP" xml:space="preserve">
<value>Importing VM from backup file</value>
</data>
<data name="IMPORTVM_IMPORTCOMPLETE" xml:space="preserve">
<value>Import VM complete</value>
</data>
<data name="IMPORTVM_IMPORTING" xml:space="preserve">
<value>Importing VM...</value>
</data>
<data name="IMPORTVM_PREP" xml:space="preserve">
<value>Preparing to Import VM</value>
</data>
<data name="IMPORTVM_STARTING" xml:space="preserve">
<value>Starting VM...</value>
</data>
<data name="IMPORTVM_TITLE" xml:space="preserve">
2016-07-20 00:51:48 +02:00
<value>Import VM from '{0}' to '{1}'</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="IMPORTVM_UPDATING_NETWORKS" xml:space="preserve">
<value>Updating VM networking...</value>
</data>
<data name="IMPORTVM_UPDATING_VM" xml:space="preserve">
<value>Updating VM...</value>
</data>
<data name="IMPORTVM_WAITING_FOR_WIZARD" xml:space="preserve">
<value>Waiting for Import VM wizard to complete...</value>
</data>
<data name="IMPORT_APPLIANCE" xml:space="preserve">
2016-07-20 00:51:48 +02:00
<value>Import Appliance '{0}' to '{1}'</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="IMPORT_DISK_IMAGE" xml:space="preserve">
2016-07-20 00:51:48 +02:00
<value>Import VM '{0}' from Disk Image to '{1}'</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="IMPORT_DOWNLOAD_ERROR" xml:space="preserve">
<value>Error downloading file '{0}'. {1}</value>
</data>
<data name="IMPORT_EULA_PAGE_MAX_TABS" xml:space="preserve">
<value>Too many EULAs to display, cannot continue.</value>
</data>
<data name="IMPORT_EULA_PAGE_TITLE" xml:space="preserve">
<value>Review End User License Agreement (EULA)</value>
</data>
<data name="IMPORT_GENERIC_FAIL" xml:space="preserve">
<value>The server could not complete the import due to an unkown error.</value>
</data>
<data name="IMPORT_INCOMPLETE_FILES" xml:space="preserve">
<value>The exported files are incomplete or in an unrecognised format.</value>
</data>
<data name="IMPORT_OPTIONS_PAGE_CHOOSE_ISO_SR" xml:space="preserve">
<value>[Choose an ISO SR]</value>
</data>
<data name="IMPORT_OPTIONS_PAGE_ERROR_NO_FIXUP_ISO_INSTALLED" xml:space="preserve">
<value>Could not locate the Fixup ISO</value>
</data>
<data name="IMPORT_OPTIONS_PAGE_ERROR_NO_ISO_SR_AVAILABLE" xml:space="preserve">
<value>Could not locate an appropriate ISO SR. Please review configuration requirements for fix-up execution and try again.</value>
</data>
<data name="IMPORT_OPTIONS_PAGE_FOUND_EXISTING_ISO" xml:space="preserve">
<value>The Fixup ISO in the SR above will be used to perform fixups</value>
</data>
<data name="IMPORT_OPTIONS_PAGE_NEW_ISO_LIBRARY" xml:space="preserve">
<value>New ISO library...</value>
</data>
<data name="IMPORT_OPTIONS_PAGE_TEXT" xml:space="preserve">
<value>OS Fixup Settings</value>
</data>
<data name="IMPORT_OPTIONS_PAGE_TITLE" xml:space="preserve">
<value>Use Operating System Fixup to ensure hypervisor interoperability</value>
</data>
<data name="IMPORT_OPTIONS_PAGE_USE_SELECTED_ISO_LIBRARY" xml:space="preserve">
<value>The Fixup ISO will be automatically copied to the selected SR</value>
</data>
<data name="IMPORT_SECURITY_PAGE_ERROR_MISSING_CERTIFICATE" xml:space="preserve">
<value>Could not find the appliance certificate. The file is missing.</value>
</data>
<data name="IMPORT_SECURITY_PAGE_ERROR_MISSING_MANIFEST" xml:space="preserve">
<value>Could not find the appliance manifest. The file is missing.</value>
</data>
<data name="IMPORT_SECURITY_PAGE_TEXT" xml:space="preserve">
<value>Security</value>
</data>
<data name="IMPORT_SECURITY_PAGE_TITLE" xml:space="preserve">
<value>Select your import security settings</value>
</data>
<data name="IMPORT_SECURITY_PAGE_VERIFY_CONTENT" xml:space="preserve">
<value>&Verify manifest content</value>
</data>
<data name="IMPORT_SECURITY_PAGE_VERIFY_CONTENT_DESCRIPTION" xml:space="preserve">
<value>Verify the manifest matches the appliance files. This option will only activate if the appliance has a manifest file.</value>
</data>
<data name="IMPORT_SECURITY_PAGE_VERIFY_PRODUCER" xml:space="preserve">
<value>&Verify digital signature</value>
</data>
<data name="IMPORT_SECURITY_PAGE_VERIFY_PRODUCER_DESCRIPTION" xml:space="preserve">
<value>Verify the digital signature of the appliance is valid. This option will activate only if the appliance has been digitally signed.</value>
</data>
<data name="IMPORT_SELECT_APPLIANCE_PAGE_ERROR_CORRUPT_OVA" xml:space="preserve">
<value>OVA file is corrupt or contains invalid data.</value>
</data>
<data name="IMPORT_SELECT_APPLIANCE_PAGE_ERROR_INVALID_PATH" xml:space="preserve">
<value>Path contains invalid characters.</value>
</data>
2016-07-22 09:31:58 +02:00
<data name="IMPORT_SELECT_APPLIANCE_PAGE_ERROR_INVALID_URI" xml:space="preserve">
<value>Please specify a valid URI.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="IMPORT_SELECT_APPLIANCE_PAGE_ERROR_NONE_EXIST_PATH" xml:space="preserve">
<value>Path does not exist.</value>
</data>
<data name="IMPORT_SELECT_APPLIANCE_PAGE_ERROR_NOT_SUPPORTED" xml:space="preserve">
<value>The selected file is not a valid appliance file.</value>
</data>
<data name="IMPORT_SELECT_APPLIANCE_PAGE_ERROR_SOURCE_IS_READONLY" xml:space="preserve">
<value>You do not have write permission on the location provided. Read-write access is required to import this type of file.</value>
</data>
<data name="IMPORT_SELECT_HOST_PAGE_TITLE" xml:space="preserve">
<value>Select the location where the imported VM will be placed</value>
</data>
<data name="IMPORT_SELECT_NETWORK_PAGE_NETWORK_FILTER" xml:space="preserve">
<value><?xml version="1.0" encoding="utf-16"?>
<ArrayOfString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<string>Guest installer network</string>
</ArrayOfString></value>
</data>
<data name="IMPORT_SELECT_NETWORK_PAGE_NO_AVAIL_NETWORKS" xml:space="preserve">
<value>No available networks to connect.</value>
</data>
<data name="IMPORT_SELECT_NETWORK_PAGE_TEXT" xml:space="preserve">
<value>Networking</value>
</data>
<data name="IMPORT_SELECT_NETWORK_PAGE_TITLE" xml:space="preserve">
<value>Select network to connect VM</value>
</data>
<data name="IMPORT_SELECT_STORAGE_PAGE_ERROR_NO_COMMON_SR_AVAILABLE" xml:space="preserve">
<value>No SR available with enough free space for all VMs.</value>
</data>
<data name="IMPORT_SELECT_STORAGE_PAGE_ERROR_NO_SR_AVAILABLE" xml:space="preserve">
<value>No SR available with enough free space.</value>
</data>
<data name="IMPORT_SELECT_STORAGE_PAGE_ERROR_SPACE_LIMITATION" xml:space="preserve">
<value>There is not enough available space on SR {0}. Please review your SR selections.</value>
</data>
<data name="IMPORT_SELECT_STORAGE_PAGE_ERROR_SPACE_LIMITATION_COMMON" xml:space="preserve">
<value>There is not enough available space on SR {0} for all the VMs. Please consider importing the VMs on different target SRs.</value>
</data>
<data name="IMPORT_SELECT_STORAGE_PAGE_TEXT" xml:space="preserve">
<value>Storage</value>
</data>
<data name="IMPORT_SELECT_STORAGE_PAGE_TITLE" xml:space="preserve">
<value>Select target storage</value>
</data>
<data name="IMPORT_SOURCE_PAGE_ERROR_OVF_ONLY" xml:space="preserve">
<value>Only OVF/OVA packages can be imported as vApps.</value>
</data>
<data name="IMPORT_SOURCE_PAGE_FILETYPES" xml:space="preserve">
2016-02-24 16:33:18 +01:00
<value>All import options (*.ovf;*.ova;*.ova.gz;*.vhd;*.vmdk;*.xva;ova.xml)|*.ovf;*.ova;*.ova.gz;*.vhd;*.vmdk;*.xva;ova.xml|OVF/OVA Package files (*.ovf;*.ova;*.ova.gz)|*.ovf;*.ova*;*.ova.gz|Virtual Hard Disk images (*.vhd;*.vmdk;)|*.vhd;*.vmdk;|XVA files (*.xva)|*.xva|XVA Version 1|ova.xml</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="IMPORT_SOURCE_PAGE_FILETYPES_OVF_ONLY" xml:space="preserve">
<value>OVF/OVA Package files (*.ovf;*.ova;*.ova.gz)|*.ovf;*.ova*;*.ova.gz</value>
</data>
<data name="IMPORT_SOURCE_PAGE_INTRO" xml:space="preserve">
<value>Enter the pathname of an exported VM or template, an OVF/OVA package or a virtual hard disk image file or click Browse to find the file you want.</value>
</data>
<data name="IMPORT_SOURCE_PAGE_INTRO_OVF_ONLY" xml:space="preserve">
<value>Enter the pathname of an OVF/OVA package or click Browse to find the file you want.</value>
</data>
<data name="IMPORT_SOURCE_PAGE_TEXT" xml:space="preserve">
<value>Import Source</value>
</data>
<data name="IMPORT_SOURCE_PAGE_TITLE" xml:space="preserve">
<value>Locate the file you want to import</value>
</data>
<data name="IMPORT_TEMPLATE_CONFIGURE_STORAGE" xml:space="preserve">
<value>Configure storage for the new template</value>
</data>
<data name="IMPORT_TEMPLATE_DESCRIP" xml:space="preserve">
<value>Importing Template from backup file.</value>
</data>
<data name="IMPORT_TEMPLATE_FROM" xml:space="preserve">
<value>Import template from...</value>
</data>
<data name="IMPORT_TEMPLATE_HOME_SERVER" xml:space="preserve">
<value>Select a home server for the new template</value>
</data>
<data name="IMPORT_TEMPLATE_IMPORTCOMPLETE" xml:space="preserve">
<value>Import Template complete.</value>
</data>
<data name="IMPORT_TEMPLATE_IMPORTING" xml:space="preserve">
<value>Importing Template...</value>
</data>
<data name="IMPORT_TEMPLATE_NETWORK_BLURB" xml:space="preserve">
<value>The virtual network interfaces configured for the imported template are listed below. You can add, modify or remove virtual network interfaces as required.</value>
</data>
<data name="IMPORT_TEMPLATE_SELECT_SR" xml:space="preserve">
<value>Select a storage repository where virtual disks for the new template will be stored</value>
</data>
<data name="IMPORT_TEMPLATE_UPDATING_NETWORKS" xml:space="preserve">
<value>Updating Template networking...</value>
</data>
<data name="IMPORT_TEMPLATE_UPDATING_TEMPLATE" xml:space="preserve">
<value>Updating Template...</value>
</data>
<data name="IMPORT_TEMPLATE_VIFS" xml:space="preserve">
<value>Configure virtual network interfaces for the new template</value>
</data>
<data name="IMPORT_TEMPLATE_WAITING_FOR_WIZARD" xml:space="preserve">
<value>Waiting for Import Template wizard to complete...</value>
</data>
<data name="IMPORT_THREAD_NAME" xml:space="preserve">
<value>XenAppliance.Import.Thread</value>
</data>
<data name="IMPORT_URI_NO_DESTINATION" xml:space="preserve">
<value>Import is a URI but no destination path defined.</value>
</data>
<data name="IMPORT_VM_CONFIGURE_STORAGE" xml:space="preserve">
<value>Configure storage for the new VM</value>
</data>
<data name="IMPORT_VM_FILE_DISAPPEARED" xml:space="preserve">
<value>{0} has disappeared. Please choose a valid filename.</value>
</data>
<data name="IMPORT_VM_FROM" xml:space="preserve">
<value>Import VM from...</value>
</data>
<data name="IMPORT_VM_IMPORT" xml:space="preserve">
<value>&Import ></value>
</data>
<data name="IMPORT_VM_NETWORK_BLURB" xml:space="preserve">
<value>The virtual network interfaces configured for the imported VM are listed below. You can add, modify or remove virtual network interfaces as required.</value>
</data>
<data name="IMPORT_VM_SELECT_HOME_SERVER" xml:space="preserve">
<value>Select a home server for the new VM</value>
</data>
<data name="IMPORT_VM_SELECT_SR" xml:space="preserve">
<value>Select a storage repository where virtual disks for the new VM will be stored</value>
</data>
<data name="IMPORT_VM_VIFS" xml:space="preserve">
<value>Configure virtual network interfaces for the new VM</value>
</data>
2016-10-27 17:03:16 +02:00
<data name="IMPORT_VM_WITH_VENDOR_DEVICE_WARNING_MANY" xml:space="preserve">
<value>Some or all of the VMs you are importing are able to receive updates from Windows Update. The selected location does not support this virtualization state. If you continue with the import, your VMs may not be fully, if at all, functional.</value>
</data>
<data name="IMPORT_VM_WITH_VENDOR_DEVICE_WARNING_ONE" xml:space="preserve">
<value>The VM you are importing is able to receive updates from Windows Update. The selected location does not support this virtualization state. If you continue with the import, your VM may not be fully, if at all, functional.</value>
</data>
2013-11-14 13:29:30 +01:00
<data name="IMPORT_VM_WITH_VGPU_WARNING_MANY" xml:space="preserve">
2015-03-30 17:21:46 +02:00
<value>Some or all of the VMs you are importing have virtual GPUs assigned to them. The selected location does not have the right type of GPU for all of them. If you continue with the import, their virtual GPU settings will be lost.</value>
2013-11-14 13:29:30 +01:00
</data>
<data name="IMPORT_VM_WITH_VGPU_WARNING_ONE" xml:space="preserve">
2015-03-30 17:21:46 +02:00
<value>The VM you are importing has a virtual GPU assigned to it. The selected location does not have the right type of GPU. If you continue with the import, the virtual GPU settings will be lost.</value>
2013-11-14 13:29:30 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="IMPORT_WIZARD_ALL_ON_SAME_SR_RADIO" xml:space="preserve">
<value>Place &all imported virtual disks on this target SR:</value>
</data>
<data name="IMPORT_WIZARD_DESTINATION_DESTINATION" xml:space="preserve">
<value>&Import VM(s) to:</value>
</data>
<data name="IMPORT_WIZARD_DESTINATION_INSTRUCTIONS" xml:space="preserve">
<value>Choose the pool or standalone server where you want to place the VM(s). If required, you can also specify a Home Server within the selected pool for each imported VM.</value>
</data>
<data name="IMPORT_WIZARD_DESTINATION_TABLE_INTRO" xml:space="preserve">
<value>&Assign imported VM(s) to a home server:</value>
</data>
<data name="IMPORT_WIZARD_NETWORKING_INTRO" xml:space="preserve">
<value>Map the virtual network interfaces in the VMs you are importing to networks in the destination pool or standalone server.</value>
</data>
<data name="IMPORT_WIZARD_SPECIFIC_SR_RADIO" xml:space="preserve">
<value>Place imported virtual disks onto &specified target SRs:</value>
</data>
<data name="IMPORT_WIZARD_STORAGE_INSTRUCTIONS" xml:space="preserve">
<value>Place the virtual disks in the VMs you are importing onto storage repositories (SRs) in the destination pool or standalone server.</value>
</data>
<data name="IMPORT_WIZARD_TEMPLATE_SR_HINT_TEXT" xml:space="preserve">
<value>Select the storage repository for the imported template.</value>
</data>
<data name="IMPORT_WIZARD_VM_SELECTION_INTRODUCTION" xml:space="preserve">
<value>&Virtual network interfaces in imported VMs:</value>
</data>
<data name="IMPORT_WIZARD_VM_SR_HINT_TEXT" xml:space="preserve">
<value>Select the storage repository for the imported virtual machine.</value>
</data>
2015-11-18 17:52:43 +01:00
<data name="INCOMPATIBLE_PRODUCTS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>This server version is incompatible with [XenCenter].</value>
2015-11-18 17:52:43 +01:00
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="INCOMPATIBLE_PROTOCOL_VERSION" xml:space="preserve">
<value>Incompatible protocol version</value>
</data>
<data name="INCOMPATIBLE_WRITE_CACHE_MODE" xml:space="preserve">
<value>Incompatible write cache mode</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="INCORRECT_FILE_SIZE" xml:space="preserve">
<value>Incorrect file size</value>
</data>
<data name="INCORRECT_LUN_FOR_SR" xml:space="preserve">
<value>This LUN does not contain the Storage Repository '{0}'. Please select the correct LUN.</value>
</data>
<data name="INCORRECT_OLD_PASSWORD" xml:space="preserve">
<value>Incorrect old password</value>
</data>
<data name="INFORMATION" xml:space="preserve">
<value>Information</value>
</data>
<data name="INFO_DISKMEMORY_MODE_GPU" xml:space="preserve">
<value>Disk and memory snapshots are not available for VMs with a dedicated GPU</value>
</data>
<data name="INFO_DISKMEMORY_MODE_MISC" xml:space="preserve">
<value>Disk and memory snapshots are not currently available for this VM</value>
</data>
2015-09-14 17:21:44 +02:00
<data name="INFO_DISKMEMORY_MODE_NO_IO_DRIVERS" xml:space="preserve">
<value>Disk and memory snapshots need I/O drivers to be installed</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="INFO_DISKMEMORY_MODE_NO_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Disk and memory snapshots need [XenServer product] Tools to be installed</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="INFO_DISKMEMORY_MODE_POWER_STATE" xml:space="preserve">
<value>Disk and memory snapshots need the VM to be running</value>
</data>
<data name="INFO_DISK_MODE" xml:space="preserve">
<value>Disk snapshots are not currently available for this VM</value>
</data>
<data name="INFO_QUIESCE_MODE" xml:space="preserve">
<value>Quiesced snapshots need the VSS service to be enabled on the VM</value>
</data>
2015-09-21 17:09:12 +02:00
<data name="INFO_QUIESCE_MODE_NO_MGMNT" xml:space="preserve">
<value>Quiesced snapshots need Management Agent to be installed</value>
2015-09-14 17:21:44 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="INFO_QUIESCE_MODE_NO_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Quiesced snapshots need [XenServer product] Tools to be installed</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="INFO_QUIESCE_MODE_POWER_STATE" xml:space="preserve">
<value>Quiesced snapshots need the VM to be running</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="INITIALIZED" xml:space="preserve">
<value>Initialized</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="INITIALIZE_WLB" xml:space="preserve">
<value>Initialize WLB...</value>
</data>
<data name="INITIALIZING_WLB" xml:space="preserve">
<value>Connecting to Workload Balancing server</value>
</data>
<data name="INITIALIZING_WLB_ON" xml:space="preserve">
<value>Connecting pool {0} to Workload Balancing server.</value>
</data>
<data name="INSTALLTOOLS_COULDNOTFIND_CD" xml:space="preserve">
<value>Could not find a CD drive on the selected VM.</value>
</data>
<data name="INSTALLTOOLS_COULDNOTFIND_WIN" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Could not find the [XenServer product] Tools install disc.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="INSTALLTOOLS_DONE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] Tools installation launched.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="INSTALLTOOLS_EXIST" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] Tools are already installed on this VM.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="INSTALLTOOLS_STARTING" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Launching [XenServer product] Tools installation.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="INSTALLTOOLS_TITLE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Installing [XenServer product] Tools on VM {0}</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="INSTALL_FILES_CANNOT_BE_FOUND" xml:space="preserve">
<value>Install files could not be found at specified network location</value>
</data>
<data name="INSTALL_LICENSE_KEY" xml:space="preserve">
<value>Install License Key</value>
</data>
<data name="INSTALL_PENDING_UPDATES" xml:space="preserve">
<value>Install pending &updates...</value>
</data>
<data name="INSTALL_XENSERVER_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Install [XenServer product] Tools</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="INSTALL_XENSERVER_TOOLS_DOTS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Install [XenServer product] Tools...</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="INSTALL_XS_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Install [XenServer product] Tools</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="INSTANT_VM_CREATE_DESCRIPTION" xml:space="preserve">
<value>Creating VM '{0}' from template '{1}'</value>
</data>
<data name="INSTANT_VM_CREATE_TITLE" xml:space="preserve">
<value>Instant VM create</value>
</data>
2015-02-25 14:01:03 +01:00
<data name="INTEGRATED_GPU_PASSTHROUGH_DISABLED" xml:space="preserve">
<value>This server is currently not using the integrated GPU.</value>
</data>
<data name="INTEGRATED_GPU_PASSTHROUGH_DISABLED_SHORT" xml:space="preserve">
<value>Not using the integrated GPU</value>
</data>
<data name="INTEGRATED_GPU_PASSTHROUGH_ENABLED" xml:space="preserve">
<value>This server is currently using the integrated GPU.</value>
</data>
<data name="INTEGRATED_GPU_PASSTHROUGH_ENABLED_SHORT" xml:space="preserve">
<value>Using the integrated GPU</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="INTERFACES_COUNT" xml:space="preserve">
<value>Interfaces: {0}</value>
</data>
2013-10-10 13:22:58 +02:00
<data name="INVALID_HOST" xml:space="preserve">
<value>Invalid hostname</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="INVALID_NUMBER" xml:space="preserve">
<value>Invalid number</value>
</data>
<data name="INVALID_OVF" xml:space="preserve">
<value>This does not appear to be a valid OVF file.</value>
</data>
<data name="INVALID_PARAMETER" xml:space="preserve">
<value>Invalid parameter</value>
</data>
<data name="INVALID_SESSION" xml:space="preserve">
<value>Invalid session</value>
</data>
<data name="INVALID_URL" xml:space="preserve">
<value>Invalid URL to installer files</value>
</data>
<data name="INVALID_VER" xml:space="preserve">
<value>The specified network location contains an invalid version of the installer files</value>
</data>
<data name="IN_ANY_APPLIANCE" xml:space="preserve">
<value>Is in a vApp</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="IN_POOL" xml:space="preserve">
<value>in '{0}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="IN_PROGRESS" xml:space="preserve">
<value>In progress</value>
</data>
<data name="IN_ROLLING_UPGRADE" xml:space="preserve">
<value>In rolling upgrade</value>
</data>
<data name="IP_ADDRESS" xml:space="preserve">
<value>IP Address</value>
</data>
<data name="IP_ADDRESS_LABEL" xml:space="preserve">
<value>I&P address:</value>
</data>
<data name="IP_ADDRESS_RANGE_END" xml:space="preserve">
<value>to {0}.{1}.{2}.{3}</value>
</data>
<data name="IP_ADDRESS_RANGE_LABEL" xml:space="preserve">
<value>I&P address range:</value>
</data>
<data name="IP_ADDRESS_UNKNOWN" xml:space="preserve">
<value>Unknown</value>
</data>
<data name="IQN_CHECK_EDIT" xml:space="preserve">
<value>Edit IQN</value>
</data>
<data name="IQN_CHECK_EXISTS_TEXT" xml:space="preserve">
<value>{0} has an iSCSI-IQN ({1}) which already exists on {2}. This could cause problems with iSCSI storage on this network.</value>
</data>
<data name="IQN_CHECK_EXISTS_TITLE" xml:space="preserve">
<value>iSCSI-IQN Exists</value>
</data>
<data name="IQN_CHECK_MISSING_TEXT" xml:space="preserve">
<value>{0} has no iSCSI-IQN. This could cause problems with iSCSI storage on this network.</value>
</data>
<data name="IQN_CHECK_MISSING_TITLE" xml:space="preserve">
<value>iSCSI-IQN Missing</value>
</data>
<data name="IS" xml:space="preserve">
<value>is</value>
</data>
<data name="ISCSI_DIALOG_SR_DETAILS" xml:space="preserve">
<value>SR size: {0}
SR UUID: {1}</value>
</data>
<data name="ISCSI_DIALOG_SR_DETAILS_FOR_FIBRECHANNEL" xml:space="preserve">
<value>Vendor: {0}
Serial Number: {1}
SCSI ID: {2}
Size: {3}</value>
</data>
<data name="ISCSI_FAIL" xml:space="preserve">
<value>Interrogation failed -- call succeeded!</value>
</data>
<data name="ISCSI_SHOULD_NO_BE_CREATED" xml:space="preserve">
<value>SHOULD NEVER BE CREATED</value>
</data>
<data name="ISL_SR" xml:space="preserve">
<value>StorageLink technology</value>
</data>
<data name="ISOCOMBOBOX_CD_DRIVE" xml:space="preserve">
<value>DVD drive {0} on {1}</value>
</data>
<data name="ISO_LOADED" xml:space="preserve">
<value>Loaded ISO '{0}' into the DVD Drive on VM {1}</value>
</data>
<data name="ISO_LOADING" xml:space="preserve">
<value>Loading ISO '{0}' into the DVD Drive on VM {1}</value>
</data>
<data name="ISO_UNLOADED" xml:space="preserve">
<value>Set DVD Drive on {0} as empty.</value>
</data>
<data name="ISO_UNLOADING" xml:space="preserve">
<value>Setting DVD Drive on {0} as empty.</value>
</data>
<data name="IS_EXACTLY" xml:space="preserve">
<value>is exactly</value>
</data>
<data name="IS_IN_A_POOL" xml:space="preserve">
<value>Is in a pool</value>
</data>
<data name="IS_IN_STORAGELINK_SR" xml:space="preserve">
<value>VMs on StorageLink Gateway SR</value>
</data>
<data name="IS_NOT" xml:space="preserve">
<value>is not</value>
</data>
<data name="IS_STANDALONE" xml:space="preserve">
<value>Is standalone</value>
</data>
<data name="JOINING_AD" xml:space="preserve">
2016-12-16 19:36:35 +01:00
<value>Please enter a user name and password with sufficient privileges to add servers to domain '{0}'.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="KEEP_WAITING_BUTTON_LABEL" xml:space="preserve">
<value>&Keep waiting</value>
</data>
<data name="LABEL_ATTEMPT" xml:space="preserve">
<value>Attempting to connect to {0}...</value>
</data>
<data name="LABEL_FAILED" xml:space="preserve">
<value>Canceling connection to {0}...</value>
</data>
<data name="LABEL_SYNC" xml:space="preserve">
<value>Synchronizing with {0}...</value>
</data>
2015-02-06 11:03:42 +01:00
<data name="LAST_REFRESH_FAIL" xml:space="preserve">
<value>The information is not available.</value>
</data>
<data name="LAST_REFRESH_IN_PROGRESS" xml:space="preserve">
<value>Loading...</value>
</data>
<data name="LAST_REFRESH_SUCCESS" xml:space="preserve">
<value>Last refresh: {0}</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="LAST_WEEK" xml:space="preserve">
<value>was last week</value>
</data>
<data name="LAUNCH_LICENSE_MANAGER" xml:space="preserve">
<value>License Manager</value>
</data>
<data name="LEAVING_AD" xml:space="preserve">
2016-12-16 19:36:35 +01:00
<value>Enter a user name and password with sufficient privileges to remove your machine account from AD. Authentication will be disabled even if the machine account cannot be removed.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="LEFT_ALT" xml:space="preserve">
<value>Left Alt</value>
</data>
<data name="LESS_THAN" xml:space="preserve">
<value>< {0}</value>
</data>
<data name="LICENSE_ACTIVATED" xml:space="preserve">
<value>Activated</value>
</data>
<data name="LICENSE_ERROR_1" xml:space="preserve">
<value>The licensing action for {0} failed.</value>
</data>
<data name="LICENSE_ERROR_MANY" xml:space="preserve">
<value>The licensing action failed for {0} out of {1} of the selected servers.</value>
</data>
<data name="LICENSE_ERROR_TITLE" xml:space="preserve">
<value>Licensing Error</value>
</data>
<data name="LICENSE_EXPIRED" xml:space="preserve">
<value>Unlicensed</value>
</data>
<data name="LICENSE_EXPIRED_NO_LICENSES_AVAILABLE" xml:space="preserve">
<value>No licenses available</value>
</data>
<data name="LICENSE_EXPIRED_OR_NEEDS_ACTIVATION" xml:space="preserve">
<value>A server license has expired or is in need of activation.</value>
</data>
<data name="LICENSE_EXPIRES_DAYS" xml:space="preserve">
<value>Expires in {0} days</value>
</data>
<data name="LICENSE_EXPIRES_HOURS" xml:space="preserve">
<value>Expires in {0} hours</value>
</data>
<data name="LICENSE_EXPIRES_MINUTES" xml:space="preserve">
<value>Expires in {0} minutes</value>
</data>
<data name="LICENSE_EXPIRES_ONE_MIN" xml:space="preserve">
<value>Expires in 1 minute</value>
</data>
<data name="LICENSE_EXPIRY_PURCHACE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] Online</value>
2013-06-24 13:41:48 +02:00
<comment>this text could be improved</comment>
</data>
<data name="LICENSE_EXPIRY_TITLE" xml:space="preserve">
<value>License Expired</value>
</data>
<data name="LICENSE_FIELD_DISABLED" xml:space="preserve">
<value>This field is disabled due to license restrictions on the server.</value>
</data>
<data name="LICENSE_FILE_DOES_NOT_EXIST" xml:space="preserve">
<value>The selected license file does not exist</value>
</data>
<data name="LICENSE_FILE_TOO_LARGE" xml:space="preserve">
<value>The selected file is too large to be a license</value>
</data>
<data name="LICENSE_FREE" xml:space="preserve">
<value>Free</value>
</data>
<data name="LICENSE_HOST_NOT_LIVE" xml:space="preserve">
<value>A selected host is no longer active</value>
</data>
<data name="LICENSE_LICENSED" xml:space="preserve">
<value>Licensed</value>
</data>
<data name="LICENSE_MANAGER_BUY_LICENSE_LINK_TEXT" xml:space="preserve">
<value>Buy Licenses...</value>
</data>
<data name="LICENSE_MANAGER_SUMMARY_LICENSE_EXPIRES" xml:space="preserve">
<value>License Expires:</value>
</data>
<data name="LICENSE_MANAGER_SUMMARY_LICENSE_SERVER" xml:space="preserve">
<value>License Server:</value>
</data>
<data name="LICENSE_MANAGER_SUMMARY_LICENSE_SOCKETS" xml:space="preserve">
<value>Sockets:</value>
</data>
<data name="LICENSE_MANAGER_SUMMARY_LICENSE_TYPE" xml:space="preserve">
<value>License Type:</value>
</data>
<data name="LICENSE_NEVER" xml:space="preserve">
<value>Never</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="LICENSE_NOT_ELIGIBLE_FOR_SUPPORT" xml:space="preserve">
<value>Not eligible for support</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="LICENSE_NO_HA" xml:space="preserve">
<value>The license for a host cannot be changed when HA is on</value>
</data>
<data name="LICENSE_NO_MULTISELECT_ACTIVATE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Servers must be selected one at a time when activating free [XenServer].</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="LICENSE_NO_MULTISELECT_LICENSE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Servers must be selected one at a time when licensing servers which have a version lower than [BRANDING_VERSION_5_6].</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="LICENSE_REGULAR_GRACE_TOOLTIP" xml:space="preserve">
<value>The license server {0} could not be reached. You have until {1} to reconnect to the license server.</value>
</data>
<data name="LICENSE_REQUIRES_ACTIVATION" xml:space="preserve">
<value>Expired (Requires activation)</value>
</data>
<data name="LICENSE_REQUIRES_ACTIVATION_DAYS" xml:space="preserve">
<value>Requires activation in {0} days</value>
</data>
<data name="LICENSE_REQUIRES_ACTIVATION_HOURS" xml:space="preserve">
<value>Requires activation in {0} hours</value>
</data>
<data name="LICENSE_REQUIRES_ACTIVATION_MINUTES" xml:space="preserve">
<value>Requires activation in {0} minutes</value>
</data>
<data name="LICENSE_REQUIRES_ACTIVATION_ONE_MIN" xml:space="preserve">
<value>Requires activation in 1 minute</value>
</data>
<data name="LICENSE_RESTRICTION_MESSAGE" xml:space="preserve">
<value>License Restriction: Could not connect to {0}, a server with an XE Express License already exists ({1})</value>
</data>
<data name="LICENSE_SA_EXPIRED" xml:space="preserve">
<value>Your support and maintenance has expired</value>
</data>
<data name="LICENSE_SA_EXPIRES_IN" xml:space="preserve">
<value>Your support and maintenance expires in {0}</value>
</data>
<data name="LICENSE_SERVER_COULD_NOT_OPEN_LINK" xml:space="preserve">
<value>Could not open {0}</value>
</data>
<data name="LICENSE_SERVER_PORT_FORMAT" xml:space="preserve">
<value>{0}:{1}</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="LICENSE_SERVER_WEB_CONSOLE_FORMAT" xml:space="preserve">
<value>http://{0}:{1}</value>
</data>
<data name="LICENSE_SERVER_WEB_CONSOLE_GOTO" xml:space="preserve">
<value>Go to...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="LICENSE_STATUS" xml:space="preserve">
<value>Status</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="LICENSE_SUPPORT_AND_DESKTOP_FEATURES_ENABLED" xml:space="preserve">
<value>Eligible for support
XenApp/XenDesktop features enabled</value>
</data>
<data name="LICENSE_SUPPORT_AND_DESKTOP_PLUS_FEATURES_ENABLED" xml:space="preserve">
<value>Eligible for support
XenApp/XenDesktop Platinum features enabled</value>
</data>
<data name="LICENSE_SUPPORT_AND_ENTERPRISE_FEATURES_ENABLED" xml:space="preserve">
<value>Eligible for support
Enterprise features enabled</value>
2016-02-08 11:10:01 +01:00
</data>
<data name="LICENSE_SUPPORT_AND_PREMIUM_FEATURES_ENABLED" xml:space="preserve">
<value>Eligible for support
Premium features enabled</value>
2015-01-23 11:41:54 +01:00
</data>
<data name="LICENSE_SUPPORT_AND_STANDARD_FEATURES_ENABLED" xml:space="preserve">
<value>Eligible for support
Standard features only</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="LICENSE_TOO_MANY_SERVERS_SELECTED_CAPTION" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Activation keys can only be applied to one Free [XenServer] product at a time.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="LICENSE_UNSUPPORTED" xml:space="preserve">
<value>Unsupported</value>
</data>
<data name="LICENSE_UPDATING" xml:space="preserve">
<value>Updating...</value>
</data>
<data name="LICENSE_UPDATING_LICENSES" xml:space="preserve">
<value>Updating Licenses</value>
</data>
<data name="LICENSE_UPGRADE_GRACE_TOOLTIP" xml:space="preserve">
<value>This host has been upgraded. You have until {0} to license this server.</value>
</data>
<data name="LICENSE_WILL_EXPIRE" xml:space="preserve">
<value>A server license will expire or need activation within 30 days.</value>
</data>
<data name="LICENSE_YOUR_LICENCE_EXPIRES_IN" xml:space="preserve">
<value>Your license expires in {0}</value>
</data>
<data name="LICENSE_YOUR_LICENCE_HAS_EXPIRED" xml:space="preserve">
<value>Your license has expired</value>
</data>
<data name="LICENSING_DIALOG_EXPIRED_TEXT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>One or more managed servers have expired. Either assign [XenServer] licenses, or activate Free [XenServer] products.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="LICENSING_DIALOG_EXPIRING_SOON_TEXT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>One or more managed servers will expire soon. Either assign [XenServer] licenses, or activate Free [XenServer] products.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="LICENSING_DIALOG_TEXT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Activate your free [XenServer] products or assign/release licenses for [XenServer] Advanced, Enterprise and Platinum Editions.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="LINK_STATUS" xml:space="preserve">
<value>Link Status</value>
</data>
<data name="LIST_SEPARATOR" xml:space="preserve">
<value>, </value>
</data>
2016-08-12 10:51:20 +02:00
<data name="LIVE_PATCHING" xml:space="preserve">
<value>Live Patching</value>
</data>
2016-08-19 13:11:50 +02:00
<data name="LIVE_PATCHING_FAILED_MULTI_HOST" xml:space="preserve">
<value>Live patching failed for servers {0}. To apply the patch, please put the servers into maintenance mode and reboot them.</value>
</data>
<data name="LIVE_PATCHING_FAILED_ONE_HOST" xml:space="preserve">
<value>Live patching failed for server ‘ {0}’ . To apply the patch, please put the server into maintenance mode and reboot it.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="LOADING" xml:space="preserve">
<value>Loading '{0}'...</value>
</data>
<data name="LOCAL" xml:space="preserve">
<value>Local</value>
</data>
<data name="LOCAL_SRS" xml:space="preserve">
<value>Local Storage Repositories</value>
</data>
<data name="LOCAL_STORAGE_CANNOT_BE_SEEN" xml:space="preserve">
<value>You have selected storage local to {0} that cannot be seen from this server</value>
</data>
<data name="LOCAL_TO_LOCAL_MOVE" xml:space="preserve">
<value>Cannot move virtual disks between local SRs</value>
</data>
<data name="LOCATION_LABEL" xml:space="preserve">
<value>Location:</value>
</data>
<data name="LOGGED_IN_AS" xml:space="preserve">
<value>Logged in as: {0}</value>
</data>
2013-10-10 13:22:58 +02:00
<data name="LOGGING_IN_TO_THE_ISCSI_TARGET_FAILED" xml:space="preserve">
<value>Logging in to the iSCSI target failed.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="LOG_DESTINATION" xml:space="preserve">
<value>Log Destination</value>
</data>
<data name="LUNPERVDIPICKER_IMPORT_VDI_COLUMN_TITLE" xml:space="preserve">
<value>VM - VDI (Virtual Disks)</value>
</data>
<data name="LUNPERVDIPICKER_VDI_COLUMN_TITLE" xml:space="preserve">
<value>VDI (Virtual Disks)</value>
</data>
<data name="LUNPERVDI_PAGE_NAME" xml:space="preserve">
<value>LUN-per-VDI Mapping</value>
</data>
<data name="LUNPERVDI_PAGE_TITLE" xml:space="preserve">
<value>Map virtual disks (VDIs) to individual LUNs on the target SR</value>
</data>
<data name="LVMOHBA_WARNING_DIALOG_HEADER_FOUND_EXISTING_SR" xml:space="preserve">
<value>An existing SR was found on the selected LUN</value>
</data>
<data name="LVMOHBA_WARNING_DIALOG_HEADER_NO_EXISTING_SRS" xml:space="preserve">
<value>No existing SRs were found on the selected LUN</value>
</data>
<data name="LVMOHBA_WARNING_DIALOG_LUN_DETAILS" xml:space="preserve">
<value>Vendor: {0}
Serial Number: {1}
SCSI ID: {2}
Size: {3}</value>
</data>
<data name="LVMOHBA_WARNING_DIALOG_REATTACH_LABEL_TEXT" xml:space="preserve">
<value>There is no existing SR to reattach</value>
</data>
<data name="LVMOHBA_WARNING_DIALOG_REPEAT_FOR_REMAINING_NO_SR" xml:space="preserve">
<value>&Do this for all remaining LUNs without existing SRs</value>
</data>
<data name="LVMOHBA_WARNING_DIALOG_REPEAT_FOR_REMAINING_WITH_SR" xml:space="preserve">
<value>&Do this for all remaining LUNs</value>
</data>
<data name="MAC" xml:space="preserve">
<value>MAC</value>
</data>
<data name="MAC_AUTOGENERATE" xml:space="preserve">
<value>auto-generate</value>
</data>
<data name="MAC_INVALID" xml:space="preserve">
<value>Invalid MAC address.</value>
</data>
<data name="MAINTENANCE_MODE" xml:space="preserve">
<value>Maintenance Mode</value>
</data>
<data name="MAINWINDOW_ADD_HOST" xml:space="preserve">
<value>&Add...</value>
</data>
<data name="MAINWINDOW_CONFIRM_MIGRATE" xml:space="preserve">
<value>Do you want to migrate the VM {0} to the server {1}?</value>
</data>
<data name="MAINWINDOW_CONFIRM_MIGRATE_MULTIPLE" xml:space="preserve">
<value>Do you want to migrate the selected VMs to the server {0}?</value>
</data>
<data name="MAINWINDOW_CONFIRM_MOVE_TO_POOL" xml:space="preserve">
<value>Do you want to move the server {0} into the pool {1}?</value>
</data>
<data name="MAINWINDOW_CONFIRM_MOVE_TO_POOL_MULTIPLE" xml:space="preserve">
<value>Do you want to move the selected servers into the pool {0}?</value>
</data>
<data name="MAINWINDOW_CONFIRM_REMOVE_FROM_POOL" xml:space="preserve">
<value>Do you want to remove '{0}' from pool '{1}'?
This will permanently delete and reinitialize all local storage on '{2}'. Your data will be lost, and the server will be rebooted.</value>
</data>
<data name="MAINWINDOW_CONFIRM_REMOVE_FROM_POOL_MULTIPLE" xml:space="preserve">
<value>Do you want to remove the selected servers from pool '{0}'?
This will permanently delete and reinitialize all local storage on the servers. Your data will be lost, and the servers will be rebooted.</value>
</data>
<data name="MAINWINDOW_CONFIRM_REMOVE_FROM_POOL_TITLE" xml:space="preserve">
<value>Remove From Pool</value>
</data>
<data name="MAINWINDOW_CONFIRM_REMOVE_FROM_POOL_YES_BUTTON_LABEL" xml:space="preserve">
<value>&Yes, Remove</value>
</data>
<data name="MAINWINDOW_CONNECTHOST" xml:space="preserve">
<value>&Connect</value>
</data>
<data name="MAINWINDOW_CONNECT_ALL_HOSTS" xml:space="preserve">
<value>C&onnect All</value>
</data>
<data name="MAINWINDOW_CONTEXTMENU_ADD_SERVER" xml:space="preserve">
<value>&Add Server</value>
</data>
<data name="MAINWINDOW_CONTEXT_REASON" xml:space="preserve">
<value>{0} ({1})</value>
</data>
<data name="MAINWINDOW_CONTEXT_UPDATING" xml:space="preserve">
<value>{0} (Updating...)</value>
</data>
<data name="MAINWINDOW_CONVERT_VM_TO_TEMPLATE" xml:space="preserve">
<value>Convert to &Template...</value>
</data>
<data name="MAINWINDOW_CONVERT_VM_TO_TEMPLATE_CONTEXT_MENU" xml:space="preserve">
<value>Co&nvert to Template...</value>
</data>
<data name="MAINWINDOW_COPY_TEMPLATE" xml:space="preserve">
<value>&Copy...</value>
</data>
<data name="MAINWINDOW_COPY_VM" xml:space="preserve">
<value>&Copy VM...</value>
</data>
<data name="MAINWINDOW_CTRL_B" xml:space="preserve">
<value>Ctrl+B</value>
</data>
<data name="MAINWINDOW_CTRL_E" xml:space="preserve">
<value>Ctrl+E</value>
</data>
<data name="MAINWINDOW_CTRL_N" xml:space="preserve">
<value>Ctrl+N</value>
</data>
<data name="MAINWINDOW_CTRL_R" xml:space="preserve">
<value>Ctrl+R</value>
</data>
<data name="MAINWINDOW_CTRL_S" xml:space="preserve">
<value>Ctrl+S</value>
</data>
<data name="MAINWINDOW_CTRL_Y" xml:space="preserve">
<value>Ctrl+Y</value>
</data>
<data name="MAINWINDOW_DELETE_OBJECTS" xml:space="preserve">
<value>De&lete...</value>
</data>
<data name="MAINWINDOW_DELETE_POOL" xml:space="preserve">
2014-05-15 19:47:13 +02:00
<value>Mak&e into standalone server</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MAINWINDOW_DELETE_TAG" xml:space="preserve">
<value>&Delete Tag...</value>
</data>
<data name="MAINWINDOW_DELETE_TAGS" xml:space="preserve">
<value>&Delete Tags...</value>
</data>
<data name="MAINWINDOW_DELETE_TEMPLATE" xml:space="preserve">
<value>&Delete Template...</value>
</data>
<data name="MAINWINDOW_DELETE_VM" xml:space="preserve">
<value>&Delete VM...</value>
</data>
<data name="MAINWINDOW_DESTROY_SR" xml:space="preserve">
<value>Destr&oy...</value>
</data>
<data name="MAINWINDOW_DETACH_SR" xml:space="preserve">
<value>&Detach...</value>
</data>
<data name="MAINWINDOW_DISCONNECT" xml:space="preserve">
<value>Dis&connect</value>
</data>
<data name="MAINWINDOW_DISCONNECT_ALL_HOSTS" xml:space="preserve">
<value>Di&sconnect All</value>
</data>
<data name="MAINWINDOW_DISCONNECT_CONTEXT_MENU" xml:space="preserve">
<value>&Disconnect</value>
</data>
<data name="MAINWINDOW_DISCONNECT_CONTEXT_MENU_POOL" xml:space="preserve">
<value>&Disconnect</value>
</data>
<data name="MAINWINDOW_EDIT_TAGS" xml:space="preserve">
<value>Edit Ta&gs...</value>
</data>
<data name="MAINWINDOW_EXPIRE_MESSAGE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>The [XenServer] license on '{0}' will expire in {1}.</value>
2013-06-24 13:41:48 +02:00
</data>
2014-05-12 16:40:05 +02:00
<data name="MAINWINDOW_EXPIRE_MESSAGE_TOO_LATE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>The [XenServer] license on '{0}' has expired.</value>
2014-05-12 16:40:05 +02:00
</data>
2014-07-25 09:35:18 +02:00
<data name="MAINWINDOW_EXPORT_POOL_RESOURCE_DATA" xml:space="preserve">
<value>E&xport Resource Data...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="MAINWINDOW_EXPORT_TEMPLATE" xml:space="preserve">
<value>&Export to File...</value>
</data>
<data name="MAINWINDOW_EXPORT_VM_AS_BACKUP" xml:space="preserve">
<value>Export to Fi&le...</value>
</data>
<data name="MAINWINDOW_EXPORT_VM_AS_BACKUP_TOOLTIP" xml:space="preserve">
<value>The VM must be shut down before it can be exported.</value>
</data>
<data name="MAINWINDOW_FORCE_REBOOT" xml:space="preserve">
<value>Force Re&boot</value>
</data>
<data name="MAINWINDOW_FORCE_SHUTDOWN" xml:space="preserve">
2013-11-20 09:29:11 +01:00
<value>Force Shut &Down</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MAINWINDOW_FORCE_SHUTDOWN_CONTEXT_MENU" xml:space="preserve">
2013-11-20 09:29:11 +01:00
<value>Force Shut Do&wn</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MAINWINDOW_FORGET_SAVED_PASSWORD" xml:space="preserve">
2015-11-16 17:11:40 +01:00
<value>&Forget Password</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MAINWINDOW_FORGET_SR" xml:space="preserve">
<value>&Forget</value>
</data>
<data name="MAINWINDOW_HIGH_AVAILABILITY" xml:space="preserve">
<value>&High Availability...</value>
</data>
<data name="MAINWINDOW_INSTALL_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Inst&all [XenServer product] Tools...</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MAINWINDOW_INSTANT_VM_FROM_TEMPLATE" xml:space="preserve">
<value>&Quick Create</value>
</data>
<data name="MAINWINDOW_LOG_REMOVECONNECTION" xml:space="preserve">
<value>Removed connection to {0}</value>
</data>
2015-05-27 13:17:35 +02:00
<data name="MAINWINDOW_MIGRATEVM" xml:space="preserve">
<value>&Migrate VM...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="MAINWINDOW_MIGRATE_TO_SERVER" xml:space="preserve">
<value>M&igrate to Server</value>
</data>
<data name="MAINWINDOW_MOVEVM" xml:space="preserve">
<value>&Move VM...</value>
</data>
2016-09-27 22:14:07 +02:00
<data name="MAINWINDOW_MOVE_OBJECTS" xml:space="preserve">
<value>&Move...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="MAINWINDOW_NEWPOOL" xml:space="preserve">
<value>&New Pool...</value>
</data>
<data name="MAINWINDOW_NEW_STORAGE" xml:space="preserve">
<value>&New SR...</value>
</data>
<data name="MAINWINDOW_NEW_VM" xml:space="preserve">
<value>&New VM...</value>
</data>
<data name="MAINWINDOW_NEW_VM_CONTEXT_MENU" xml:space="preserve">
<value>New V&M...</value>
</data>
<data name="MAINWINDOW_NEW_VM_FROM_TEMPLATE" xml:space="preserve">
<value>&New VM wizard...</value>
</data>
2015-02-09 17:53:29 +01:00
<data name="MAINWINDOW_PAUSE" xml:space="preserve">
<value>&Pause</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="MAINWINDOW_POWER_ON" xml:space="preserve">
<value>Power O&n</value>
</data>
<data name="MAINWINDOW_POWER_ON_CONTEXT_MENU" xml:space="preserve">
<value>Po&wer On</value>
</data>
<data name="MAINWINDOW_POWER_ON_NO_AMP" xml:space="preserve">
<value>Power On</value>
</data>
<data name="MAINWINDOW_REATTACH_SR" xml:space="preserve">
<value>R&eattach...</value>
</data>
<data name="MAINWINDOW_REBOOT" xml:space="preserve">
<value>Reb&oot</value>
</data>
<data name="MAINWINDOW_REBOOT_CONTEXT_MENU" xml:space="preserve">
<value>Reb&oot</value>
</data>
<data name="MAINWINDOW_REBOOT_HOST_CONTEXT_MENU" xml:space="preserve">
<value>Re&boot</value>
</data>
<data name="MAINWINDOW_RECONNECTAS" xml:space="preserve">
<value>Reconnec&t As...</value>
</data>
<data name="MAINWINDOW_RECOVERY_MODE" xml:space="preserve">
<value>Start in Reco&very Mode</value>
</data>
<data name="MAINWINDOW_REMOVE_HOST" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Remo&ve from [XenCenter]</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MAINWINDOW_REMOVE_HOST_CRASHDUMPS" xml:space="preserve">
2016-08-01 10:25:10 +02:00
<value>Remove Crash Dump &Files</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MAINWINDOW_REMOVE_HOST_CRASHDUMPS_CONTEXT_MENU" xml:space="preserve">
<value>Remove Crash Dump &Files</value>
</data>
<data name="MAINWINDOW_RENAME_TAG" xml:space="preserve">
<value>&Rename Tag...</value>
</data>
<data name="MAINWINDOW_REPAIR_SR" xml:space="preserve">
<value>Re&pair...</value>
</data>
<data name="MAINWINDOW_REPAIR_SR_CONTEXT_MENU" xml:space="preserve">
<value>Re&pair...</value>
</data>
2015-02-19 15:09:08 +01:00
<data name="MAINWINDOW_RESTART" xml:space="preserve">
<value>Re&start</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="MAINWINDOW_RESTART_TOOLSTACK" xml:space="preserve">
<value>Restart Toolstac&k</value>
</data>
<data name="MAINWINDOW_RESUME" xml:space="preserve">
<value>R&esume</value>
</data>
<data name="MAINWINDOW_RESUME_CONTEXT_MENU" xml:space="preserve">
<value>Re&sume</value>
</data>
<data name="MAINWINDOW_RESUME_ON_HOST" xml:space="preserve">
<value>Resume on Ser&ver</value>
</data>
<data name="MAINWINDOW_SAVE_AND_RESTORE" xml:space="preserve">
<value>Sa&ve and Restore...</value>
</data>
<data name="MAINWINDOW_SET_AS_DEFAULT_SR" xml:space="preserve">
<value>Set as Defaul&t</value>
</data>
<data name="MAINWINDOW_SHARE_SR" xml:space="preserve">
<value>&Share</value>
</data>
<data name="MAINWINDOW_SHUTDOWN" xml:space="preserve">
<value>S&hut Down</value>
</data>
2015-08-26 18:54:03 +02:00
<data name="MAINWINDOW_SR_CONVERT_TO_THIN_CONTEXT_MENU" xml:space="preserve">
2015-08-27 14:50:56 +02:00
<value>&Convert SR...</value>
2015-08-26 18:54:03 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="MAINWINDOW_START" xml:space="preserve">
<value>&Start</value>
</data>
<data name="MAINWINDOW_START_CONTEXT_MENU" xml:space="preserve">
<value>S&tart</value>
</data>
<data name="MAINWINDOW_START_ON_HOST" xml:space="preserve">
<value>Start on Ser&ver</value>
</data>
2015-02-09 17:53:29 +01:00
<data name="MAINWINDOW_STOP" xml:space="preserve">
<value>S&top</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="MAINWINDOW_SUSPEND" xml:space="preserve">
<value>S&uspend</value>
</data>
<data name="MAINWINDOW_TAKE_SNAPSHOT" xml:space="preserve">
<value>Ta&ke a Snapshot...</value>
</data>
<data name="MAINWINDOW_TOOLBAR_POWER_ON_SERVER" xml:space="preserve">
<value>Power On Server (Ctrl+B)</value>
</data>
<data name="MAINWINDOW_TOOLBAR_REBOOT" xml:space="preserve">
<value>Reboot VM (Ctrl+R)</value>
</data>
<data name="MAINWINDOW_TOOLBAR_REBOOTSERVER" xml:space="preserve">
<value>Reboot Server</value>
</data>
<data name="MAINWINDOW_TOOLBAR_RESUME" xml:space="preserve">
<value>Resume</value>
</data>
<data name="MAINWINDOW_TOOLBAR_RESUMEVM" xml:space="preserve">
<value>Resume VM (Ctrl+Y)</value>
</data>
<data name="MAINWINDOW_TOOLBAR_SHUTDOWN" xml:space="preserve">
<value>Shut Down</value>
</data>
<data name="MAINWINDOW_TOOLBAR_SHUTDOWNSERVER" xml:space="preserve">
<value>Shut Down Server</value>
</data>
<data name="MAINWINDOW_TOOLBAR_SHUTDOWNVM" xml:space="preserve">
<value>Shut Down VM (Ctrl+E)</value>
</data>
<data name="MAINWINDOW_TOOLBAR_START" xml:space="preserve">
<value>Start</value>
</data>
<data name="MAINWINDOW_TOOLBAR_STARTVM" xml:space="preserve">
<value>Start VM (Ctrl+B)</value>
</data>
<data name="MAINWINDOW_TOOLBAR_SUSPEND" xml:space="preserve">
<value>Suspend</value>
</data>
<data name="MAINWINDOW_TOOLBAR_SUSPENDVM" xml:space="preserve">
<value>Suspend VM (Ctrl+Y)</value>
</data>
2014-07-04 14:36:41 +02:00
<data name="MAINWINDOW_TRIM_SR" xml:space="preserve">
<value>Re&claim freed space</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="MAINWINDOW_XVA_BLURB" xml:space="preserve">
<value>XVA Files (*.xva)|*.xva|All Files (*.*)|*.*</value>
</data>
<data name="MAINWINDOW_XVA_TITLE" xml:space="preserve">
<value>Export to File</value>
</data>
<data name="MAKE_DEFAULT_SR" xml:space="preserve">
<value>Set as &Default</value>
</data>
<data name="MANAGEMENT" xml:space="preserve">
<value>Management</value>
</data>
<data name="MANAGEMENT_INTERFACE" xml:space="preserve">
<value>Management interface</value>
</data>
<data name="MANAGEMENT_INTERFACES" xml:space="preserve">
<value>Management Interfaces</value>
</data>
<data name="MANAGEMENT_INTERFACES_FOR" xml:space="preserve">
<value>Displayed below is a list of management interfaces for '{0}'.</value>
</data>
<data name="MANAGEMENT_NETWORK" xml:space="preserve">
<value>{0} (management)</value>
</data>
<data name="MANAGEMENT_NETWORK_WITH_POOL" xml:space="preserve">
<value>{0} (management) on {1}</value>
</data>
<data name="MANUAL_CHECK_FOR_UPDATES_PARTIAL_UNLICENSED_INFO" xml:space="preserve">
<value>Subscription Advantage required for some hosts</value>
</data>
<data name="MANUAL_CHECK_FOR_UPDATES_UNLICENSED_INFO" xml:space="preserve">
<value>Subscription Advantage required</value>
</data>
<data name="MASTER" xml:space="preserve">
<value>Master</value>
</data>
<data name="MAX" xml:space="preserve">
<value>Max</value>
</data>
<data name="MAX_BRACKETS" xml:space="preserve">
<value>(max = {0})</value>
</data>
<data name="MEMORY" xml:space="preserve">
<value>Memory</value>
</data>
<data name="MEMORY_COLON" xml:space="preserve">
<value>&Memory:</value>
</data>
<data name="MEMORY_XEN" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer]</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MEM_NOT_WHEN_SUSPENDED" xml:space="preserve">
<value>The memory cannot be changed when the VM is suspended</value>
</data>
<data name="MENU_EXPORT" xml:space="preserve">
<value>&Export...</value>
</data>
<data name="MENU_MIGRATE_TO_HOME_SERVER" xml:space="preserve">
<value>Migrate to Home Server</value>
</data>
<data name="MESSAGEBOX_ACTIVATE_VD_TITLE" xml:space="preserve">
<value>Activate Virtual Disk</value>
</data>
<data name="MESSAGEBOX_CLEAR_AFFINITY_CONFIRM" xml:space="preserve">
<value>Clear the home server for {0}? Its home will be chosen dynamically from now on.</value>
</data>
<data name="MESSAGEBOX_CLONEVM_NOSPACE" xml:space="preserve">
<value>There is not enough space available to clone the storage for this VM</value>
</data>
<data name="MESSAGEBOX_CONFIRM" xml:space="preserve">
<value>Confirm</value>
</data>
<data name="MESSAGEBOX_DEACTIVATE_VD_TITLE" xml:space="preserve">
<value>Deactivate Virtual Disk</value>
</data>
<data name="MESSAGEBOX_DELETE_CUSTOM_FIELD" xml:space="preserve">
<value>This will delete '{0}' permanently, destroying all data associated with it. Continue?</value>
</data>
<data name="MESSAGEBOX_DELETE_ISO" xml:space="preserve">
<value>This will delete {0} permanently, destroying the data on it. Continue?</value>
</data>
<data name="MESSAGEBOX_DELETE_ISO_MULTIPLE" xml:space="preserve">
<value>This will delete these ISOs permanently, destroying any data on them. Do you wish to continue?</value>
</data>
<data name="MESSAGEBOX_DELETE_ISO_TITLE" xml:space="preserve">
<value>Delete Storage</value>
</data>
<data name="MESSAGEBOX_DELETE_ISO_TITLE_MULTIPLE" xml:space="preserve">
<value>Delete Multiple Storage Items</value>
</data>
<data name="MESSAGEBOX_DELETE_SNAPSHOT" xml:space="preserve">
<value>Deleting a single snapshot disk is not allowed. This action will delete the entire snapshot, and any other disks attached. Do you wish to continue?</value>
</data>
<data name="MESSAGEBOX_DELETE_SNAPSHOTS_TITLE_MULTIPLE" xml:space="preserve">
<value>Delete Multiple Entire Snapshots</value>
</data>
<data name="MESSAGEBOX_DELETE_SNAPSHOT_MULTIPLE" xml:space="preserve">
<value>Deleting a single snapshot disk is not allowed. Deleting these snapshot disks will result in the deletion of the entire snapshot each belongs to, and any other disks attached. Do you wish to continue?</value>
</data>
<data name="MESSAGEBOX_DELETE_SNAPSHOT_TITLE" xml:space="preserve">
<value>Delete entire snapshot</value>
</data>
<data name="MESSAGEBOX_DELETE_SYS_DISK" xml:space="preserve">
<value>This will delete this system disk permanently, possibly leaving the VM unable to boot. Do you wish to continue?</value>
</data>
<data name="MESSAGEBOX_DELETE_SYS_DISK_MULTIPLE" xml:space="preserve">
<value>This will delete these system disks permanently, possibly leaving their VMs unable to boot. Do you wish to continue?</value>
</data>
<data name="MESSAGEBOX_DELETE_SYS_DISK_TITLE" xml:space="preserve">
<value>Delete System Disk</value>
</data>
<data name="MESSAGEBOX_DELETE_SYS_DISK_TITLE_MULTIPLE" xml:space="preserve">
<value>Delete Multiple System Disks</value>
</data>
<data name="MESSAGEBOX_DELETE_VD" xml:space="preserve">
<value>This will delete this virtual disk permanently, destroying the data on it. Continue?</value>
</data>
<data name="MESSAGEBOX_DELETE_VD_MULTIPLE" xml:space="preserve">
<value>This will delete these virtual disks permanently, destroying any data on them. Do you wish to continue?</value>
</data>
<data name="MESSAGEBOX_DELETE_VD_TITLE" xml:space="preserve">
<value>Delete Virtual Disk</value>
</data>
<data name="MESSAGEBOX_DELETE_VD_TITLE_MUTLIPLE" xml:space="preserve">
<value>Delete Multiple Virtual Disks</value>
</data>
<data name="MESSAGEBOX_DESTROY_SRS_CONTINUE" xml:space="preserve">
<value>Are you sure you want to destroy the selected storage repositories?
Destroying the selected storage repositories will permanently remove all associated virtual disks from the underlying storage devices.
This action is final and unrecoverable.</value>
</data>
<data name="MESSAGEBOX_DESTROY_SRS_CONTINUE_TITLE" xml:space="preserve">
<value>Destroy Multiple Storage Repositories</value>
</data>
<data name="MESSAGEBOX_DESTROY_SR_CONTINUE" xml:space="preserve">
<value>Are you sure you want to destroy '{0}'?
Destroying this storage repository will permanently remove all associated virtual disks from the underlying storage device.
This action is final and unrecoverable.</value>
</data>
<data name="MESSAGEBOX_DESTROY_SR_CONTINUE_TITLE" xml:space="preserve">
<value>Destroy Storage Repository</value>
</data>
<data name="MESSAGEBOX_DESTROY_SR_YES_BUTTON_LABEL" xml:space="preserve">
<value>&Yes, Destroy</value>
</data>
<data name="MESSAGEBOX_DETACH_SRS_CONTINUE" xml:space="preserve">
<value>Detaching the selected storage repositories will make the virtual disks that they contain inaccessible. The contents of the virtual disks themselves will remain intact.
If you subsequently reattach the storage repositories, you will need to provide the correct device configuration details.
Are you sure you want to detach the selected storage repositories?</value>
</data>
<data name="MESSAGEBOX_DETACH_SRS_CONTINUE_TITLE" xml:space="preserve">
<value>Detach Multiple Storage Repositories</value>
</data>
<data name="MESSAGEBOX_DETACH_SR_CONTINUE" xml:space="preserve">
<value>Detaching this storage repository will make the virtual disks that it contains inaccessible. The contents of the virtual disks themselves will remain intact.
If you subsequently reattach the storage repository, you will need to provide the correct device configuration details.
Are you sure you want to detach this storage repository?</value>
</data>
<data name="MESSAGEBOX_DETACH_SR_CONTINUE_TITLE" xml:space="preserve">
<value>Detach Storage Repository</value>
</data>
<data name="MESSAGEBOX_DETACH_SYSTEMVD" xml:space="preserve">
<value>This action will detach a system disk from the VM which may leave it unbootable. Would you like to continue?</value>
</data>
<data name="MESSAGEBOX_DETACH_SYSTEMVD_TITLE" xml:space="preserve">
<value>Detach system disk</value>
</data>
<data name="MESSAGEBOX_DETACH_VD" xml:space="preserve">
<value>Detaching this virtual disk will remove the association between it and the VM while preserving the disk and its data. Would you like to continue?</value>
</data>
<data name="MESSAGEBOX_DETACH_VD_TITLE" xml:space="preserve">
<value>Detach virtual disk</value>
</data>
2016-09-06 15:53:46 +02:00
<data name="MESSAGEBOX_DETACH_VD_TITLE_MUTLIPLE" xml:space="preserve">
2013-06-24 13:41:48 +02:00
<value>Detach Multiple Virtual Disks</value>
</data>
<data name="MESSAGEBOX_ERRORTEXT" xml:space="preserve">
<value>Unable to connect to server '{0}'.
{1}
{2}</value>
</data>
<data name="MESSAGEBOX_FORGET_SRS_CONTINUE" xml:space="preserve">
<value>Are you sure you want to forget the selected storage repositories?
Forgetting the selected storage repositories will permanently remove the information used to connect the virtual machines to the virtual disks in the storage repositories. The contents of the virtual disks themselves will remain intact.
This action is final and unrecoverable.</value>
</data>
<data name="MESSAGEBOX_FORGET_SRS_CONTINUE_TITLE" xml:space="preserve">
<value>Forget Multiple Storage Repositories</value>
</data>
<data name="MESSAGEBOX_FORGET_SR_CONTINUE" xml:space="preserve">
<value>Are you sure you want to forget '{0}'?
Forgetting this storage repository will permanently remove the information used to connect the virtual machines to the virtual disks in the storage repository. The contents of the virtual disks themselves will remain intact.
This action is final and unrecoverable.</value>
</data>
<data name="MESSAGEBOX_FORGET_SR_CONTINUE_TITLE" xml:space="preserve">
<value>Forget Storage Repository</value>
</data>
<data name="MESSAGEBOX_FORGET_SR_CONTINUE_YES_BUTTON_LABEL" xml:space="preserve">
<value>&Yes, Forget</value>
</data>
<data name="MESSAGEBOX_HELP_TOPICS" xml:space="preserve">
<value>Launching help topic {0} ({1}).</value>
</data>
<data name="MESSAGEBOX_HELP_TOPIC_NOT_FOUND" xml:space="preserve">
<value>Help topic {0} does not exist.</value>
</data>
<data name="MESSAGEBOX_LOAD_CORRUPTED" xml:space="preserve">
<value>Your saved settings appear to be corrupt. Revert changes to {0} or delete the file to return to default values.</value>
</data>
<data name="MESSAGEBOX_LOAD_CORRUPTED_TITLE" xml:space="preserve">
<value>Could Not Load Settings</value>
</data>
<data name="MESSAGEBOX_LOGFILE_MISSING" xml:space="preserve">
<value>Log file is missing.</value>
</data>
<data name="MESSAGEBOX_LOGS_DELETE" xml:space="preserve">
2014-08-05 17:24:56 +02:00
<value>You have applied filters to the list of events. Do you wish to dismiss all events or only the events you have chosen to view? In both cases only completed events will be removed.</value>
2013-06-24 13:41:48 +02:00
</data>
2014-07-31 10:39:16 +02:00
<data name="MESSAGEBOX_LOGS_DELETE_NO_FILTER" xml:space="preserve">
2014-08-05 17:13:48 +02:00
<value>This operation will remove all completed events. Do you wish to continue?</value>
2013-11-18 15:31:00 +01:00
</data>
2014-07-31 10:39:16 +02:00
<data name="MESSAGEBOX_LOGS_DELETE_SELECTED" xml:space="preserve">
2014-08-05 17:13:48 +02:00
<value>This operation will remove all selected completed events. Do you wish to continue?</value>
2013-06-24 13:41:48 +02:00
</data>
2013-08-10 13:29:36 +02:00
<data name="MESSAGEBOX_LOG_DELETE" xml:space="preserve">
2014-07-31 10:39:16 +02:00
<value>Are you sure you want to dismiss this event?</value>
2013-08-10 13:29:36 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="MESSAGEBOX_MOVING_VDI_TITLE" xml:space="preserve">
<value>Moving Virtual Disk</value>
</data>
<data name="MESSAGEBOX_NETWORK_DELETE" xml:space="preserve">
<value>This will delete the selected network permanently. Continue?</value>
</data>
<data name="MESSAGEBOX_NETWORK_DELETE_TITLE" xml:space="preserve">
<value>Delete Network</value>
</data>
<data name="MESSAGEBOX_PASSWORD_WRITE_FAILED" xml:space="preserve">
<value>Writing password information failed: {0}</value>
</data>
<data name="MESSAGEBOX_POOL_DELETE" xml:space="preserve">
<value>The pool Master will become a standalone server, are you sure you want to continue?</value>
</data>
<data name="MESSAGEBOX_POOL_MASTER_REMOVE" xml:space="preserve">
<value>You cannot remove the master from the pool.</value>
</data>
<data name="MESSAGEBOX_PROGRAM_UNEXPECTED" xml:space="preserve">
<value>[{0}] There has been an unexpected error. Technical details about this error have been saved to the following file. Please send this to your support representative.
{1}</value>
</data>
<data name="MESSAGEBOX_PROGRAM_UNEXPECTED_TITLE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] - Error</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MESSAGEBOX_RECONNECT_FAIL" xml:space="preserve">
<value>Unable to reconnect to {0} . Server is unavailable.</value>
</data>
<data name="MESSAGEBOX_RECONNECT_FAIL_TITLE" xml:space="preserve">
<value>Failed to Reconnect</value>
</data>
<data name="MESSAGEBOX_SAVE_CORRUPTED" xml:space="preserve">
<value>Unable to save settings. You may have insufficient disk space or your configuration file could be corrupt.
To fix a corrupt configuration file revert changes to {0} or delete the file to return to default values.</value>
</data>
<data name="MESSAGEBOX_SAVE_CORRUPTED_TITLE" xml:space="preserve">
<value>Could Not Save Settings</value>
</data>
<data name="MESSAGEBOX_SESSION_SAVE_UNABLE" xml:space="preserve">
<value>The program could not securely save your session: no session information will be stored.</value>
</data>
<data name="MESSAGEBOX_SESSION_SAVE_UNABLE_TITLE" xml:space="preserve">
<value>Could not save session</value>
</data>
<data name="MESSAGEBOX_SLAVES_EJECT" xml:space="preserve">
<value>You must eject all slaves from the pool before you can delete the pool.</value>
</data>
<data name="MESSAGEBOX_VIF_DELETE" xml:space="preserve">
<value>This will delete the selected network interface permanently. Continue?</value>
</data>
<data name="MESSAGEBOX_VIF_DELETE_TITLE" xml:space="preserve">
<value>Delete Network Interface</value>
</data>
<data name="MESSAGE_ALERT_TITLE" xml:space="preserve">
<value>{0}: {1}</value>
</data>
<data name="MIGRATE" xml:space="preserve">
<value>Migrate</value>
</data>
<data name="MIGRATE_EJECT_TOOLS_ON_UPGRADE" xml:space="preserve">
<value>Cannot migrate this VM - there may be a CD in the drive. Eject the CD and try again.</value>
</data>
<data name="MIGRATE_PLEASE_EJECT_YOUR_CD" xml:space="preserve">
<value>Please eject your CD</value>
</data>
<data name="MIGRATE_VDI_UPSELL_BLURB" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable VDI live migration. This feature enables you to migrate multiple running VDIs between SRs in the same pool with no VM downtime. </value>
2016-01-21 09:54:22 +01:00
</data>
<data name="MIGRATE_VDI_UPSELL_BLURB_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] Live VDI Migration feature or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MIGRATE_VMS_OFF_SERVER" xml:space="preserve">
<value>Migrate VMs off server '{0}'</value>
</data>
<data name="MIGRATION_NOT_ALLOWED" xml:space="preserve">
<value>This VM may not migrate at the moment</value>
</data>
2015-11-02 16:55:52 +01:00
<data name="MIGRATION_NOT_ALLOWED_CPU_FEATURES" xml:space="preserve">
<value>This VM may not migrate because the destination host does not have some of the CPU features that the VM is currently using</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="MIGRATION_NOT_ALLOWED_GPU" xml:space="preserve">
<value>This VM may not migrate because it has a dedicated GPU</value>
</data>
<data name="MIGRATION_NOT_ALLOWED_NO_SHARED_STORAGE" xml:space="preserve">
<value>This VM may not migrate; it is not on shared storage</value>
</data>
<data name="MIGRATION_NOT_ALLOWED_OUTSIDE_POOL" xml:space="preserve">
<value>A VM may not migrate outside of its pool</value>
</data>
<data name="MIN" xml:space="preserve">
<value>Min</value>
</data>
<data name="MISSING_URL" xml:space="preserve">
<value>Missing URL</value>
</data>
<data name="MIXED_POWER_ON_MODE" xml:space="preserve">
<value>Mixed</value>
</data>
<data name="MONDAY_LONG" xml:space="preserve">
<value>Monday</value>
</data>
<data name="MONDAY_SHORT" xml:space="preserve">
<value>Mon</value>
</data>
<data name="MOREONE_VM_SELECTED" xml:space="preserve">
<value>{0} VMs selected</value>
</data>
<data name="MOVED" xml:space="preserve">
<value>Moved</value>
</data>
<data name="MOVE_CANCELLED" xml:space="preserve">
2013-12-13 14:51:16 +01:00
<value>Moving {0} canceled</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MOVE_OBJECTS_TO_FOLDER" xml:space="preserve">
<value>Move selected objects to folder '{0}'...</value>
</data>
<data name="MOVE_OBJECT_TO_FOLDER" xml:space="preserve">
<value>Move object '{0}' to folder '{1}'...</value>
</data>
<data name="MOVE_VDI_CONTEXT_MENU" xml:space="preserve">
<value>&Move Virtual Disk...</value>
</data>
2015-03-17 17:35:12 +01:00
<data name="MOVE_VM_WIZARD_TITLE" xml:space="preserve">
<value>Move VM</value>
</data>
<data name="MOVE_VM_WIZARD_TITLE_AND_LOCATION" xml:space="preserve">
<value>Move VM to {0}</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="MOVING" xml:space="preserve">
<value>Moving...</value>
</data>
2014-07-25 09:35:18 +02:00
<data name="MTU" xml:space="preserve">
<value>MTU</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="MULTIPATHING" xml:space="preserve">
<value>Multipathing</value>
</data>
<data name="MULTIPATH_ACTIVE" xml:space="preserve">
<value>Active</value>
</data>
<data name="MULTIPATH_CAPABLE" xml:space="preserve">
<value>Multipath capable</value>
</data>
<data name="MULTIPATH_FAILED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>One or more paths to at least one of your storages has failed. Refer to the "[XenServer product] Administrator's Guide" for information about configuring storage multipathing.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="MULTIPATH_NOT_ACTIVE" xml:space="preserve">
<value>Not active</value>
</data>
<data name="MULTIPATH_STATUS" xml:space="preserve">
<value>{0} of {1} paths active</value>
</data>
<data name="MULTIPATH_STATUS_ISCSI_SESSIONS" xml:space="preserve">
<value> ({0} iSCSI sessions)</value>
</data>
<data name="MULTI_VDI_DELETE_INSTRUCTION" xml:space="preserve">
<value>Are you sure you wish to delete the selected items?</value>
</data>
<data name="MULTI_VDI_DELETE_WARNING" xml:space="preserve">
<value>You are about to delete multiple virtual disks. Are you sure you wish to proceed?</value>
</data>
2016-09-06 15:53:46 +02:00
<data name="MULTI_VDI_DETACH_WARNING" xml:space="preserve">
2013-06-24 13:41:48 +02:00
<value>You are about to detach multiple virtual disks, are you sure you wish to proceed?</value>
</data>
<data name="MUST_SELECT_NETWORK" xml:space="preserve">
<value>You must select a network</value>
</data>
2017-02-09 16:16:11 +01:00
<data name="MY_CITRIX_CREDENTIALS_URL" xml:space="preserve">
<value>http://www.citrix.com/welcome.html</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NAME" xml:space="preserve">
<value>Name</value>
</data>
<data name="NAME_DESCRIPTION_TAGS" xml:space="preserve">
<value>General</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="NAME_WITH_LOCATION" xml:space="preserve">
<value>{0} {1}</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NETAPP_EQUAL_PAGE_TITLE" xml:space="preserve">
<value>Select the SR to reattach or create a new SR</value>
</data>
<data name="NETWORK" xml:space="preserve">
<value>Network</value>
</data>
<data name="NETWORKING_PROPERTIES_AUX_TAB_NAME" xml:space="preserve">
<value>Storage {0}</value>
</data>
<data name="NETWORKING_PROPERTIES_BLURB_HOST" xml:space="preserve">
<value>Configure IP address settings for server management traffic (the management interface) on '{0}' here.
You can also assign IP addresses for dedicated storage or other types of network traffic (secondary interfaces).</value>
</data>
<data name="NETWORKING_PROPERTIES_BLURB_POOL" xml:space="preserve">
<value>Configure IP address settings for server management traffic (the management interface) on all of the servers in pool '{0}' here.
You can also assign IP addresses for dedicated storage or other types of network traffic (secondary interfaces) in the pool.</value>
</data>
<data name="NETWORKING_PROPERTIES_CHANGING_MANAGEMENT_CONTINUE" xml:space="preserve">
<value>&Reconfigure anyway</value>
</data>
<data name="NETWORKING_PROPERTIES_IN_USE_WARNING" xml:space="preserve">
<value>{0} is currently in use by {1}</value>
</data>
<data name="NETWORKING_PROPERTIES_IN_USE_WARNING_MANAGEMENT" xml:space="preserve">
<value>{0} is currently in use by the primary interface</value>
</data>
<data name="NETWORKING_PROPERTIES_IP_AND_DNS_SETTINGS" xml:space="preserve">
<value>IP address and DNS server settings:</value>
</data>
<data name="NETWORKING_PROPERTIES_IP_SETTINGS" xml:space="preserve">
<value>IP address settings:</value>
</data>
<data name="NETWORKING_PROPERTIES_PURPOSE_UNKNOWN" xml:space="preserve">
<value>unknown</value>
</data>
<data name="NETWORKING_PROPERTIES_REMOVE_TOOLTIP" xml:space="preserve">
<value>Remove IP Address</value>
</data>
<data name="NETWORKING_PROPERTIES_SUBTEXT" xml:space="preserve">
<value>{0}; {1}</value>
</data>
<data name="NETWORKING_PROPERTIES_TAB_TITLE_PRIMARY" xml:space="preserve">
<value>Management Interface</value>
</data>
<data name="NETWORKING_PROPERTIES_TITLE" xml:space="preserve">
<value>Configure IP Addresses - {0}</value>
</data>
<data name="NETWORKING_PROPERTIES_WARNING_CHANGING_MANAGEMENT_HOST" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>You are reconfiguring the primary management interface. If the new settings are incorrect then [XenCenter] may permanently lose the connection to the server.
2013-06-24 13:41:48 +02:00
You should only proceed if you have verified that these settings are correct.</value>
</data>
<data name="NETWORKING_PROPERTIES_WARNING_CHANGING_MANAGEMENT_POOL" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>You are reconfiguring the primary management interface. If the new settings are incorrect then [XenCenter] may permanently lose the connection to the server, or pool members may be unable to contact each other.
2013-06-24 13:41:48 +02:00
You should only proceed if you have verified that these settings are correct.</value>
</data>
<data name="NETWORKPANEL_AUTO" xml:space="preserve">
<value>Auto</value>
</data>
<data name="NETWORKPANEL_INTERNAL" xml:space="preserve">
<value><internal></value>
</data>
<data name="NETWORKPANEL_IP" xml:space="preserve">
<value>IP Address</value>
</data>
<data name="NETWORKPANEL_LIMIT" xml:space="preserve">
<value>Limit</value>
</data>
<data name="NETWORKPANEL_VLAN" xml:space="preserve">
<value>VLAN</value>
</data>
<data name="NETWORKPICKER_INTERFACE" xml:space="preserve">
<value>interface {0}</value>
</data>
<data name="NETWORKPICKER_LOG_VIF_ERROR" xml:space="preserve">
<value>Error from VIF table: {0}</value>
</data>
<data name="NETWORKS" xml:space="preserve">
<value>Networks</value>
</data>
<data name="NETWORK_ACTION_CREATING_NETWORK" xml:space="preserve">
<value>Creating network</value>
</data>
<data name="NETWORK_ACTION_CREATING_NETWORK_TITLE" xml:space="preserve">
<value>Creating network '{0}' on {1}</value>
</data>
<data name="NETWORK_ACTION_NETWORK_CREATED" xml:space="preserve">
<value>Network created</value>
</data>
<data name="NETWORK_ACTION_NETWORK_REMOVED" xml:space="preserve">
<value>Network removed</value>
</data>
<data name="NETWORK_ACTION_NETWORK_UPDATED" xml:space="preserve">
<value>Network updated</value>
</data>
<data name="NETWORK_ACTION_REMOVING_NETWORK" xml:space="preserve">
<value>Removing network</value>
</data>
<data name="NETWORK_ACTION_REMOVING_NETWORK_TITLE" xml:space="preserve">
<value>Removing network '{0}' from {1}</value>
</data>
<data name="NETWORK_ACTION_UPDATING_NETWORK" xml:space="preserve">
<value>Updating network</value>
</data>
<data name="NETWORK_ACTION_UPDATING_NETWORK_TITLE" xml:space="preserve">
<value>Updating network '{0}' on {1}</value>
</data>
<data name="NETWORK_IN_USE_BY" xml:space="preserve">
<value>{0} (in use by {1})</value>
</data>
<data name="NETWORK_NAME" xml:space="preserve">
<value>Network {0}</value>
</data>
<data name="NETWORK_RECONFIG_CONNECTION_LOST" xml:space="preserve">
<value>The connection to the server was lost. No changes have been made.</value>
</data>
<data name="NETWORK_SETTINGS" xml:space="preserve">
<value>Network Settings</value>
</data>
<data name="NETWORK_WITH_POOL" xml:space="preserve">
<value>{0} on {1}</value>
</data>
<data name="NETW_BOND_DETAILS_TEXT" xml:space="preserve">
<value>Bond Members</value>
</data>
<data name="NETW_BOND_DETAILS_TITLE" xml:space="preserve">
<value>Select members for the new bonded network</value>
</data>
<data name="NETW_CHIN_DETAILS_TITLE" xml:space="preserve">
<value>Configure the new network</value>
</data>
<data name="NETW_DETAILS_TEXT" xml:space="preserve">
<value>Network settings</value>
</data>
<data name="NETW_DETAILS_VLAN_NUMBER_IN_USE" xml:space="preserve">
<value>This VLAN number is already in use</value>
</data>
<data name="NETW_EXTERNAL_DETAILS_TITLE" xml:space="preserve">
<value>Configure the new network</value>
</data>
<data name="NETW_INTERNAL_DETAILS_TITLE" xml:space="preserve">
<value>Configure the new network</value>
</data>
<data name="NETW_NAME_TEXT" xml:space="preserve">
<value>Name</value>
</data>
<data name="NETW_NAME_TITLE" xml:space="preserve">
<value>Enter a name and description for the new network</value>
</data>
<data name="NETW_TYPE_SELECT_TEXT" xml:space="preserve">
<value>Select Type</value>
</data>
<data name="NETW_TYPE_SELECT_TITLE" xml:space="preserve">
<value>Choose the type of network to create</value>
</data>
<data name="NEVER" xml:space="preserve">
<value>Never</value>
</data>
<data name="NEWDISKWIZARD_MESSAGE" xml:space="preserve">
2016-09-12 15:34:57 +02:00
<value>You need to shutdown and then restart the VM before it can access the new disk.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEWDISKWIZARD_MESSAGE_TITLE" xml:space="preserve">
<value>Disk Created</value>
</data>
<data name="NEWER_GUI_AVAILABLE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>There is a newer version of [XenCenter] available. Please contact your support representative.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEWNETWORKWIZARD_TITLE" xml:space="preserve">
<value>New Network - {0}</value>
</data>
<data name="NEWNETWORK_NAME" xml:space="preserve">
<value>New Network</value>
</data>
<data name="NEWNETWORK_VNAME" xml:space="preserve">
<value>New Private Network</value>
</data>
<data name="NEWPOOL_DIFFERENT_NETWORK_BACKENDS" xml:space="preserve">
<value>This server's network backend is different from the master's</value>
</data>
<data name="NEWPOOL_DIFFERING_AD_CONFIG" xml:space="preserve">
<value>This server has a different Active Directory configuration to the master</value>
</data>
<data name="NEWPOOL_DIFF_HARDWARE" xml:space="preserve">
<value>This server's hardware is incompatible with the master's</value>
</data>
<data name="NEWPOOL_DIFF_SERVER" xml:space="preserve">
<value>This server is a different version to the master</value>
</data>
<data name="NEWPOOL_FREE_HOST_PAID_MASTER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>You cannot add a Free Edition [XenServer] to a pool with [XenServer] Advanced Edition or higher licenses</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEWPOOL_HAS_RUNNING_VMS" xml:space="preserve">
2017-03-10 18:05:10 +01:00
<value>This server has running VMs</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEWPOOL_HAS_SHARED_STORAGE" xml:space="preserve">
<value>This server has shared storage</value>
</data>
<data name="NEWPOOL_IS_A_POOL" xml:space="preserve">
<value>This server is master of an existing pool</value>
</data>
2013-07-03 14:05:37 +02:00
<data name="NEWPOOL_LICENSED_HOST_UNLICENSED_MASTER" xml:space="preserve">
<value>You cannot add a licensed server to an unlicensed pool</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWPOOL_LICENSEMISMATCH" xml:space="preserve">
2015-01-23 11:12:02 +01:00
<value>This server does not have the same license as the pool master</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEWPOOL_LINUXPACK" xml:space="preserve">
<value>This server's linux pack installation state differs from that of the master</value>
</data>
<data name="NEWPOOL_MASTER_CONNECTING" xml:space="preserve">
<value>The master is still connecting</value>
</data>
<data name="NEWPOOL_MASTER_DISCONNECTED" xml:space="preserve">
<value>The master is disconnected</value>
</data>
<data name="NEWPOOL_MASTER_ROLE" xml:space="preserve">
<value>Your current role on the master is not authorized to add hosts to the master's pool</value>
</data>
<data name="NEWPOOL_PAID_HOST_FREE_MASTER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>You cannot add server with a [XenServer product] Advanced Edition or higher license to a pool of Free Edition servers</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEWPOOL_POOLINGRESTRICTED" xml:space="preserve">
<value>Pooling is restricted with this server's license</value>
</data>
<data name="NEWPOOL_SLAVE_ROLE" xml:space="preserve">
<value>Your current role on the slave is not authorized to add the slave to a pool</value>
</data>
2013-07-03 14:05:37 +02:00
<data name="NEWPOOL_UNLICENSED_HOST_LICENSED_MASTER" xml:space="preserve">
<value>You cannot add an unlicensed server to a licensed pool</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWSR_ACTION" xml:space="preserve">
<value>NFS SR [{0}]</value>
</data>
2015-03-12 18:31:38 +01:00
<data name="NEWSR_CIFS_ACTION" xml:space="preserve">
2015-09-21 12:11:57 +02:00
<value>SMB SR [{0}]</value>
2015-03-12 18:31:38 +01:00
</data>
2015-03-03 16:51:56 +01:00
<data name="NEWSR_CIFS_BLURB" xml:space="preserve">
2015-09-21 12:11:57 +02:00
<value>SMB servers are a common form of Windows shared filesystem infrastructure, and can be used as a storage repository substrate for virtual disks.
2015-03-12 18:31:38 +01:00
2016-06-10 15:37:49 +02:00
As SMB storage repositories are shared, the virtual disks stored in them allow VMs to be started on any server in a resource pool and to be migrated between them using Live Migration.
2015-03-12 18:31:38 +01:00
2016-12-16 19:36:35 +01:00
When you configure a SMB storage repository, you simply provide the hostname or IP address of the SMB server, the user name, the password and the path to a directory that will be used to contain the storage repository. The SMB server must be configured to export the specified path to all servers in the pool.</value>
2015-03-03 16:51:56 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWSR_CIFS_ISO_BLURB" xml:space="preserve">
2015-09-21 12:11:57 +02:00
<value>Select this option if you have a library of VM installation ISO images available as a Windows (SMB/CIFS) share that you wish to attach to your host or pool.</value>
2013-06-24 13:41:48 +02:00
</data>
2016-11-03 14:55:46 +01:00
<data name="NEWSR_CIFS_ISO_TYPE_NAME" xml:space="preserve">
<value>Windows File Sharing (SMB/CIFS)</value>
</data>
<data name="NEWSR_CIFS_TYPE_NAME" xml:space="preserve">
<value>SMB/CIFS</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWSR_CIF_DESCRIPTION" xml:space="preserve">
2015-09-21 12:11:57 +02:00
<value>SMB ISO Library [{0}]</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEWSR_CSLG_ADAPTER_PAGE_TITLE" xml:space="preserve">
<value>Select the storage system adapter</value>
</data>
<data name="NEWSR_CSLG_AUTO" xml:space="preserve">
<value>Auto</value>
</data>
<data name="NEWSR_CSLG_BLURB" xml:space="preserve">
<value>StorageLink technology is used to connect to any of the leading storage architectures and protocols, including DAS, NAS, SAN, iSCSI and Fibre Channel.</value>
</data>
<data name="NEWSR_CSLG_DEDUPLICATION" xml:space="preserve">
<value>Deduplication</value>
</data>
<data name="NEWSR_CSLG_DEFAULT_PROVISIONING" xml:space="preserve">
<value>Default</value>
</data>
<data name="NEWSR_CSLG_FC" xml:space="preserve">
<value>Fibre Channel</value>
</data>
<data name="NEWSR_CSLG_ISCSI" xml:space="preserve">
<value>iSCSI</value>
</data>
<data name="NEWSR_CSLG_NONE" xml:space="preserve">
<value>None</value>
</data>
<data name="NEWSR_CSLG_PAGE_TITLE" xml:space="preserve">
<value>Select the storage system for your storage repository</value>
</data>
<data name="NEWSR_CSLG_SETTINGS_PAGE_TITLE" xml:space="preserve">
<value>Select the storage repository settings for use with the provisioning of new storage volumes</value>
</data>
<data name="NEWSR_CSLG_THICK_PROVISIONING" xml:space="preserve">
<value>Thick</value>
</data>
<data name="NEWSR_CSLG_THIN_PROVISIONING" xml:space="preserve">
<value>Thin</value>
</data>
2016-11-03 14:55:46 +01:00
<data name="NEWSR_CSLG_TYPE_NAME" xml:space="preserve">
<value>StorageLink technology</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWSR_EQUAL_LOGIC_BLURB" xml:space="preserve">
2016-06-10 15:37:49 +02:00
<value>Dell EqualLogic is a scalable form of high performance network attached storage, which supports the addition of capacity without downtime. You can use Dell EqualLogic shared storage to support [XenServer] features such as Live Migration and High Availability.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEWSR_EQUAL_LOGIC_DESCRIPTION" xml:space="preserve">
<value>Dell EqualLogic SR [{0} ({1})]</value>
</data>
<data name="NEWSR_EQUAL_LOGIC_FILER_ADDRESS" xml:space="preserve">
<value>Dell EqualLogic filer &address:</value>
</data>
<data name="NEWSR_EQUAL_LOGIC_FILER_DETAILS_TEXT" xml:space="preserve">
<value>EqualLogic Filer Details</value>
</data>
<data name="NEWSR_EQUAL_LOGIC_FILER_PAGE_TITLE" xml:space="preserve">
<value>Enter the Dell EqualLogic filer details</value>
</data>
2015-06-29 15:26:37 +02:00
<data name="NEWSR_FCOE_DEFAULT_NAME" xml:space="preserve">
<value>Software FCoE virtual disk storage</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWSR_HBA_DEFAULT_NAME" xml:space="preserve">
<value>Hardware HBA virtual disk storage</value>
</data>
<data name="NEWSR_ISCSI_DESCRIPTION" xml:space="preserve">
<value>iSCSI SR [{0} ({1}; {2})]</value>
</data>
<data name="NEWSR_ISCSI_FORMAT_WARNING" xml:space="preserve">
2016-01-19 02:05:08 +01:00
<value>Creating a new virtual disk on this LUN will destroy any data present. You must ensure that no other system is using the LUN, including any servers, or the virtual disk may become corrupted while in use.
2013-06-24 13:41:48 +02:00
Do you wish to format the disk?</value>
</data>
<data name="NEWSR_ISO_DESCRIPTION" xml:space="preserve">
<value>NFS ISO Library [{0}]</value>
</data>
<data name="NEWSR_LOCATION" xml:space="preserve">
<value>Location</value>
</data>
<data name="NEWSR_LUN_HAS_NO_SRS" xml:space="preserve">
<value>This LUN does not contain a Storage Repository. Please select another LUN.</value>
</data>
<data name="NEWSR_LUN_IN_USE" xml:space="preserve">
<value>This LUN is already in use.</value>
</data>
<data name="NEWSR_LUN_IN_USE_ON_POOL" xml:space="preserve">
<value>This LUN is already in use as SR {0} on pool {1}.</value>
</data>
<data name="NEWSR_LUN_IN_USE_ON_SERVER" xml:space="preserve">
<value>This LUN is already in use as SR {0} on server {1}.</value>
</data>
2015-06-29 15:26:37 +02:00
<data name="NEWSR_LVMOFCOE_BLURB" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] hosts support Software based Fibre Channel over Ethernet using supported Converged Network Adapters (CNAs) which support FCoE in this way.
2015-06-29 15:26:37 +02:00
2015-06-29 18:19:09 +02:00
All configuration required to expose a LUN to the host must be completed manually, including configuring your FCoE fabric, and allocating LUN(s) to your CNA’ s public world wide name (PWWN).
2015-06-29 15:26:37 +02:00
2015-06-29 18:19:09 +02:00
Once this configuration has been carried out, this wizard will walk you through discovering and mounting a LUN available to the hosts CNA’ s as a SCSI device. The SCSI device can then be used to access the LUN as if it were a locally attached SCSI device.</value>
2015-06-29 15:26:37 +02:00
</data>
2015-06-29 10:50:32 +02:00
<data name="NEWSR_LVMOFCOE_DESCRIPTION" xml:space="preserve">
2015-06-29 15:26:37 +02:00
<value>Software FCoE SR [{0} - {1}]</value>
2015-06-29 10:50:32 +02:00
</data>
2016-11-03 14:55:46 +01:00
<data name="NEWSR_LVMOFCOE_TYPE_NAME" xml:space="preserve">
<value>Software FCoE</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWSR_LVMOHBA_BLURB" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] hosts support Fibre Channel (FC), Fibre Channel over Ethernet (FCoE) and shared Serial Attached SCSI (SAS) storage area networks (SANs) using host bus adapters (HBAs).
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
All configuration required to expose a LUN to the host must be completed manually, including storage devices, network devices, and the HBA within the [XenServer] host.
2013-06-24 13:41:48 +02:00
Once all configuration is complete the HBA will expose a SCSI device backed by the LUN to the host. The SCSI device can then be used to access the LUN as if it were a locally attached SCSI device.</value>
</data>
<data name="NEWSR_LVMOHBA_DESCRIPTION" xml:space="preserve">
<value>Hardware HBA SR [{0} - {1}]</value>
</data>
2013-07-08 17:16:37 +02:00
<data name="NEWSR_LVMOHBA_NEXT_TEXT" xml:space="preserve">
<value>&Create</value>
</data>
2013-07-09 17:59:47 +02:00
<data name="NEWSR_LVMOHBA_SUMMARY_DETAILS_CELL_TEXT" xml:space="preserve">
<value>{0} ({1} - {2})</value>
</data>
2013-07-08 17:16:37 +02:00
<data name="NEWSR_LVMOHBA_SUMMARY_FAILURE_MULTIPLE" xml:space="preserve">
<value>Failed to create {0} SRs</value>
</data>
<data name="NEWSR_LVMOHBA_SUMMARY_FAILURE_SINGLE" xml:space="preserve">
<value>Failed to create SR</value>
</data>
<data name="NEWSR_LVMOHBA_SUMMARY_MULTIPLE_TITLE" xml:space="preserve">
<value>Summary of new Storage Repositories creation</value>
</data>
<data name="NEWSR_LVMOHBA_SUMMARY_SINGLE_TITLE" xml:space="preserve">
<value>Summary of new Storage Repository creation</value>
</data>
<data name="NEWSR_LVMOHBA_SUMMARY_SUCCESS_MULTIPLE" xml:space="preserve">
<value>{0} SRs created successfully</value>
</data>
<data name="NEWSR_LVMOHBA_SUMMARY_SUCCESS_SINGLE" xml:space="preserve">
<value>SR created successfully</value>
</data>
<data name="NEWSR_LVMOHBA_SUMMARY_TEXT" xml:space="preserve">
<value>Summary</value>
</data>
2016-11-03 14:55:46 +01:00
<data name="NEWSR_LVMOHBA_TYPE_NAME" xml:space="preserve">
<value>Hardware HBA</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWSR_LVMOISCSI_BLURB" xml:space="preserve">
2013-10-01 10:39:32 +02:00
<value>iSCSI or Fibre Channel access to a shared LUN can be configured using LVM.
2013-06-24 13:41:48 +02:00
2013-10-01 10:39:32 +02:00
Using an LVM for a shared SR provides the same performance benefits as a unshared LVM for local disk storage but also enables VM agility.</value>
2013-06-24 13:41:48 +02:00
</data>
2016-11-03 14:55:46 +01:00
<data name="NEWSR_LVMOISCSI_TYPE_NAME" xml:space="preserve">
<value>iSCSI</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWSR_MULTI_POOL_WARNING" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Warning: you must ensure that the following SR is not in use by any server not connected to [XenCenter]. Failure to do so may result in data loss.
2013-06-24 13:41:48 +02:00
SR: {0}
Do you want to reattach the SR?</value>
</data>
<data name="NEWSR_NAMEPAGE_TEXT" xml:space="preserve">
<value>Name</value>
</data>
<data name="NEWSR_NAMEPAGE_TITLE" xml:space="preserve">
<value>What do you want to call this Storage Repository?</value>
</data>
<data name="NEWSR_NETAPP_BLURB" xml:space="preserve">
<value>If you have access to a Network Appliance (NetApp) filer with sufficient disk space, running a version of Data ONTAP 7G (version 7.2 or greater), you can configure a custom NetApp Storage Repository.
The driver uses the ZAPI interface to the filer to create a group of FlexVols which correspond to an SR. VDIs are created as virtual LUNs on the filer, and attached to the host using an iSCSI data path.
VM cloning uses the snapshot and clone capabilities of the filer to provide high performance and to ensure compatibility with existing ONTAP filer management tools.</value>
</data>
<data name="NEWSR_NETAPP_DEDUP_UNAVAILABLE" xml:space="preserve">
<value>This aggregate does not support FAS deduplication</value>
</data>
<data name="NEWSR_NETAPP_DESCRIPTION" xml:space="preserve">
<value>NetApp SR [{0} ({1})]</value>
</data>
<data name="NEWSR_NETAPP_FILER_ADDRESS" xml:space="preserve">
<value>NetApp filer &address:</value>
</data>
<data name="NEWSR_NETAPP_FILER_DETAILS_TEXT" xml:space="preserve">
<value>NetApp Filer Details</value>
</data>
<data name="NEWSR_NETAPP_FILER_PAGE_TITLE" xml:space="preserve">
<value>Enter the NetApp filer details</value>
</data>
<data name="NEWSR_NFS_ISO_BLURB" xml:space="preserve">
<value>Select this option if you have a library of VM installation ISO images available as a NFS share that you wish to attach to your host or pool.</value>
</data>
2016-11-03 14:55:46 +01:00
<data name="NEWSR_NFS_ISO_TYPE_NAME" xml:space="preserve">
<value>NFS ISO</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWSR_NOWHERE_TO_CREATE" xml:space="preserve">
<value>The given filer has no existing SRs and nowhere to create a new SR.</value>
</data>
<data name="NEWSR_NO_IQNS_FOUND" xml:space="preserve">
<value>No IQNs were found on {0}.</value>
</data>
<data name="NEWSR_NO_LUNS_FOUND" xml:space="preserve">
<value>No LUNs were found on {0}.</value>
</data>
2015-03-09 16:32:07 +01:00
<data name="NEWSR_NO_SRS_FOUND" xml:space="preserve">
<value><No SRs were found></value>
</data>
2015-03-03 16:51:56 +01:00
<data name="NEWSR_PATH_CIFS" xml:space="preserve">
2015-09-21 12:11:57 +02:00
<value>Enter a path for your SMB storage</value>
2015-03-03 16:51:56 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWSR_PATH_ISCSI" xml:space="preserve">
<value>Enter a path for your iSCSI storage</value>
</data>
<data name="NEWSR_PATH_ISO" xml:space="preserve">
<value>Enter a path for your NFS ISO storage</value>
</data>
<data name="NEWSR_PATH_ISO_CIFS" xml:space="preserve">
2015-09-21 12:11:57 +02:00
<value>Enter a path for your SMB ISO storage</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEWSR_PATH_NFS" xml:space="preserve">
<value>Enter a path for your NFS storage</value>
</data>
<data name="NEWSR_SELECT_LUN" xml:space="preserve">
<value>Select the LUN to reattach or create a new SR on</value>
</data>
<data name="NEWSR_TEXT" xml:space="preserve">
<value>New Storage Repository - {0}</value>
</data>
<data name="NEWSR_TEXT_ATTACH" xml:space="preserve">
<value>Attach Storage Repository - {0}</value>
</data>
<data name="NEWSR_VHDONFS_BLURB" xml:space="preserve">
<value>NFS servers are a common form of shared filesystem infrastructure, and can be used as a storage repository substrate for virtual disks.
2016-06-10 15:37:49 +02:00
As NFS storage repositories are shared, the virtual disks stored in them allow VMs to be started on any server in a resource pool and to be migrated between them using Live Migration.
2013-06-24 13:41:48 +02:00
When you configure an NFS storage repository, you simply provide the hostname or IP address of the NFS server and the path to a directory that will be used to contain the storage repository. The NFS server must be configured to export the specified path to all servers in the pool.</value>
</data>
2016-11-03 14:55:46 +01:00
<data name="NEWSR_VHDONFS_TYPE_NAME" xml:space="preserve">
<value>NFS</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWVMAPPLIANCE_FINISHPAGE_TEXT" xml:space="preserve">
<value>Finish</value>
</data>
<data name="NEWVMAPPLIANCE_FINISHPAGE_TITLE" xml:space="preserve">
<value>Create the new vApp</value>
</data>
<data name="NEWVMAPPLIANCE_NAMEPAGE_TEXT" xml:space="preserve">
<value>Name</value>
</data>
<data name="NEWVMAPPLIANCE_NAMEPAGE_TITLE" xml:space="preserve">
<value>What do you want to call this vApp?</value>
</data>
<data name="NEWVMAPPLIANCE_VMORDERANDDELAYSPAGE_TEXT" xml:space="preserve">
<value>VM Startup Sequence</value>
</data>
<data name="NEWVMAPPLIANCE_VMORDERANDDELAYSPAGE_TITLE" xml:space="preserve">
<value>Configure the startup sequence for the VMs in this vApp</value>
</data>
<data name="NEWVMAPPLIANCE_VMSPAGE_TEXT" xml:space="preserve">
<value>Virtual Machines</value>
</data>
<data name="NEWVMAPPLIANCE_VMSPAGE_TITLE" xml:space="preserve">
<value>Choose which VMs to include in this vApp</value>
</data>
<data name="NEWVMWIZARD_CDMEDIAPAGE_INSTALLATIONSOURCE" xml:space="preserve">
<value>Installation Source</value>
</data>
<data name="NEWVMWIZARD_CDMEDIAPAGE_NAME" xml:space="preserve">
<value>Source</value>
</data>
<data name="NEWVMWIZARD_CDMEDIAPAGE_TITLE" xml:space="preserve">
<value>Locate the operating system installation media</value>
</data>
2015-02-04 18:23:51 +01:00
<data name="NEWVMWIZARD_CLOUD_CONFIG_PARAMETERS_PAGE" xml:space="preserve">
<value>Cloud-Config Parameters</value>
</data>
<data name="NEWVMWIZARD_CLOUD_CONFIG_PARAMETERS_PAGE_TITLE" xml:space="preserve">
<value>Configure Cloud-Config Parameters</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWVMWIZARD_COPY_BIOS_STRINGS_PAGE_HOST" xml:space="preserve">
<value>Copy BIOS Strings from</value>
</data>
<data name="NEWVMWIZARD_COPY_BIOS_STRINGS_PAGE_NAME" xml:space="preserve">
<value>BIOS Strings</value>
</data>
<data name="NEWVMWIZARD_COPY_BIOS_STRINGS_PAGE_TITLE" xml:space="preserve">
<value>Select the server that will provide the BIOS strings</value>
</data>
2016-09-29 13:11:37 +02:00
<data name="NEWVMWIZARD_CPUMEMPAGE_INITIAL_VCPUS" xml:space="preserve">
<value>Initial number of vCPUs</value>
</data>
<data name="NEWVMWIZARD_CPUMEMPAGE_MAX_VCPUS" xml:space="preserve">
<value>Maximum number of vCPUs</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWVMWIZARD_CPUMEMPAGE_MEMORYWARN1" xml:space="preserve">
<value>The amount of memory allocated to the new VM is greater than the amount of physical memory on any server in the pool.
Server '{0}' has {1} of physical memory in total.
You will not be able to start this VM without increasing the amount of physical memory on one of the servers in the pool.</value>
</data>
<data name="NEWVMWIZARD_CPUMEMPAGE_MEMORYWARN2" xml:space="preserve">
<value>The amount of memory allocated to the new VM is greater than the amount of physical memory available on any server in the pool.
Server '{0}' has {1} of physical memory available.
You will not be able to start this VM without freeing some space on one of the servers.</value>
</data>
<data name="NEWVMWIZARD_CPUMEMPAGE_NAME" xml:space="preserve">
<value>CPU && Memory</value>
</data>
2016-09-29 13:11:37 +02:00
<data name="NEWVMWIZARD_CPUMEMPAGE_RUBRIC" xml:space="preserve">
<value>Specify the number of virtual CPUs, their topology, and the amount of memory that will be allocated to the new virtual machine. </value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWVMWIZARD_CPUMEMPAGE_TITLE" xml:space="preserve">
<value>Allocate processor and memory resources</value>
</data>
2014-06-05 14:03:06 +02:00
<data name="NEWVMWIZARD_CPUMEMPAGE_TOPOLOGY" xml:space="preserve">
<value>Topology</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWVMWIZARD_CPUMEMPAGE_VCPUS" xml:space="preserve">
<value>vCPUs</value>
</data>
<data name="NEWVMWIZARD_CPUMEMPAGE_VCPUSWARN" xml:space="preserve">
<value>The number of vCPUs given to the new VM is greater than the number of physical CPUs on any server in the pool.
Server '{0}' has {1} physical CPUs.
Performance of this VM will be greatly reduced if it is started with this many vCPUs.</value>
</data>
<data name="NEWVMWIZARD_FINISHPAGE" xml:space="preserve">
<value>All the necessary information has been collected and the wizard is ready to provision the new virtual machine using the settings shown below.
Review these settings, then click Previous if you need to change anything. Otherwise, click Create Now to create the new VM. It may take several minutes to create the new VM.</value>
</data>
<data name="NEWVMWIZARD_FINISHPAGE_CREATE" xml:space="preserve">
<value>&Create Now</value>
</data>
<data name="NEWVMWIZARD_FINISHPAGE_NAME" xml:space="preserve">
<value>Finish</value>
</data>
<data name="NEWVMWIZARD_FINISHPAGE_TITLE" xml:space="preserve">
<value>Ready to create the new virtual machine</value>
</data>
<data name="NEWVMWIZARD_FIRSTRUNPAGE_NAME" xml:space="preserve">
<value>First Run</value>
</data>
<data name="NEWVMWIZARD_FIRSTRUNPAGE_TITLE" xml:space="preserve">
<value>Before you begin</value>
</data>
<data name="NEWVMWIZARD_HOMESERVERPAGE_HOMESERVER" xml:space="preserve">
<value>Home Server</value>
</data>
<data name="NEWVMWIZARD_HOMESERVERPAGE_NAME" xml:space="preserve">
<value>Home Server</value>
</data>
<data name="NEWVMWIZARD_HOMESERVERPAGE_TITLE" xml:space="preserve">
<value>Select a home server</value>
</data>
<data name="NEWVMWIZARD_HOMESERVER_NONE" xml:space="preserve">
<value>none</value>
</data>
<data name="NEWVMWIZARD_INSTALLATIONMEDIAPAGE_CD" xml:space="preserve">
<value>CD</value>
</data>
<data name="NEWVMWIZARD_INSTALLATIONMEDIAPAGE_INSTALLMETHOD" xml:space="preserve">
<value>Install Method</value>
</data>
<data name="NEWVMWIZARD_INSTALLATIONMEDIAPAGE_NAME" xml:space="preserve">
<value>Installation Media</value>
</data>
<data name="NEWVMWIZARD_INSTALLATIONMEDIAPAGE_NETWORK" xml:space="preserve">
<value>Network</value>
</data>
<data name="NEWVMWIZARD_INSTALLATIONMEDIAPAGE_NONE" xml:space="preserve">
<value>none</value>
</data>
<data name="NEWVMWIZARD_INSTALLATIONMEDIAPAGE_TITLE" xml:space="preserve">
<value>Locate the operating system installation media</value>
</data>
<data name="NEWVMWIZARD_INSTALLMEDIA_DVD" xml:space="preserve">
<value>&DVD drive:</value>
</data>
<data name="NEWVMWIZARD_INSTALLMEDIA_INSTALLDVD" xml:space="preserve">
<value>Install from ISO library or &DVD drive:</value>
</data>
<data name="NEWVMWIZARD_INSTALLMEDIA_INSTALLPXE" xml:space="preserve">
<value>&Boot from network</value>
</data>
<data name="NEWVMWIZARD_INSTALLMEDIA_INSTALLURL" xml:space="preserve">
<value>Install from &URL:</value>
</data>
<data name="NEWVMWIZARD_NAMEPAGE_NAME" xml:space="preserve">
<value>Name</value>
</data>
<data name="NEWVMWIZARD_NAMEPAGE_NAME2" xml:space="preserve">
<value>Name</value>
</data>
<data name="NEWVMWIZARD_NAMEPAGE_TITLE" xml:space="preserve">
<value>Name the new virtual machine</value>
</data>
<data name="NEWVMWIZARD_NETWORKINGPAGE_AUTOGEN" xml:space="preserve">
<value><autogenerated MAC></value>
</data>
<data name="NEWVMWIZARD_NETWORKINGPAGE_NAME" xml:space="preserve">
<value>Networking</value>
</data>
<data name="NEWVMWIZARD_NETWORKINGPAGE_TITLE" xml:space="preserve">
<value>Configure networking on the new VM</value>
</data>
<data name="NEWVMWIZARD_NETWORKINGPAGE_VIF" xml:space="preserve">
<value>Network Interface {0}</value>
</data>
<data name="NEWVMWIZARD_NETWORKINGPAGE_VIFSON" xml:space="preserve">
<value>Virtual network interfaces on {0}</value>
</data>
<data name="NEWVMWIZARD_NETWORKMEDIAPAGE_INSTALLATIONMETHOD" xml:space="preserve">
<value>Installation Method</value>
</data>
<data name="NEWVMWIZARD_NETWORKMEDIAPAGE_INSTALLATIONURL" xml:space="preserve">
<value>Installation URL</value>
</data>
<data name="NEWVMWIZARD_NETWORKMEDIAPAGE_NAME" xml:space="preserve">
<value>Source</value>
</data>
<data name="NEWVMWIZARD_NETWORKMEDIAPAGE_PXE" xml:space="preserve">
<value>PXE</value>
</data>
<data name="NEWVMWIZARD_NETWORKMEDIAPAGE_TITLE" xml:space="preserve">
<value>Locate the operating system installation media</value>
</data>
<data name="NEWVMWIZARD_STORAGEPAGE_DISK" xml:space="preserve">
2016-08-05 17:02:03 +02:00
<value>Disk '{0}'</value>
2013-06-24 13:41:48 +02:00
</data>
2013-09-26 14:37:27 +02:00
<data name="NEWVMWIZARD_STORAGEPAGE_DISK_DESCRIPTION" xml:space="preserve">
<value>Created by template provisioner</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWVMWIZARD_STORAGEPAGE_NAME" xml:space="preserve">
<value>Storage</value>
</data>
<data name="NEWVMWIZARD_STORAGEPAGE_NOSTORAGE" xml:space="preserve">
<value><no suitable storage></value>
</data>
<data name="NEWVMWIZARD_STORAGEPAGE_SROVERCOMMIT" xml:space="preserve">
<value>The SR '{0}' is over committed. There is only {1} of free space and the new VM requires {2}.</value>
</data>
2015-09-21 00:57:58 +02:00
<data name="NEWVMWIZARD_STORAGEPAGE_SROVERCOMMIT_THIN" xml:space="preserve">
<value>The SR '{0}' is over committed. There is only {1} of free space and the new VM requires {2} ({3} initially).</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWVMWIZARD_STORAGEPAGE_TITLE" xml:space="preserve">
<value>Configure storage for the new VM</value>
</data>
<data name="NEWVMWIZARD_STORAGEPAGE_VDINAME" xml:space="preserve">
<value>{0} {1}</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_CENTOS" xml:space="preserve">
<value>CentOS</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_CITRIX" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[Citrix]</value>
2013-06-24 13:41:48 +02:00
</data>
2015-02-04 18:23:51 +01:00
<data name="NEWVMWIZARD_TEMPLATEPAGE_COREOS" xml:space="preserve">
<value>CoreOS</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWVMWIZARD_TEMPLATEPAGE_CUSTOM" xml:space="preserve">
<value>Custom</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_DEBIAN" xml:space="preserve">
<value>Debian</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_MISC" xml:space="preserve">
<value>Misc</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_NAME" xml:space="preserve">
<value>Template</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_NOTEMPLATE" xml:space="preserve">
<value><no template selected></value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_ORACLE" xml:space="preserve">
<value>Oracle</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_REDHAT" xml:space="preserve">
<value>Red Hat</value>
</data>
2015-03-27 14:34:59 +01:00
<data name="NEWVMWIZARD_TEMPLATEPAGE_SCILINUX" xml:space="preserve">
<value>Scientific Linux</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWVMWIZARD_TEMPLATEPAGE_SNAPSHOTS" xml:space="preserve">
<value>Snapshots</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_SUSE" xml:space="preserve">
<value>SUSE</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_TEMPLATE" xml:space="preserve">
<value>Template</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_TEMPLATENAME" xml:space="preserve">
<value>Template name</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_TITLE" xml:space="preserve">
<value>Select a VM template</value>
</data>
<data name="NEWVMWIZARD_TEMPLATEPAGE_WINDOWS" xml:space="preserve">
<value>Windows</value>
</data>
2013-09-20 12:24:46 +02:00
<data name="NEWVMWIZARD_VGPUPAGE_TITLE" xml:space="preserve">
<value>Assign a virtual GPU</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEWVM_DEFAULTNAME" xml:space="preserve">
<value>{0} ({1})</value>
</data>
<data name="NEWVM_INSTALL_URL_EXAMPLE_FTP" xml:space="preserve">
<value>ftp://server/path</value>
</data>
<data name="NEWVM_INSTALL_URL_EXAMPLE_HTTP" xml:space="preserve">
<value>http://server/path</value>
</data>
<data name="NEWVM_INSTALL_URL_EXAMPLE_NFS" xml:space="preserve">
<value>nfs://server/path</value>
</data>
<data name="NEWVM_TITLE" xml:space="preserve">
<value>New VM - {0}</value>
</data>
<data name="NEWVNET_TITLE" xml:space="preserve">
<value>New Virtual Network Interface - {0}</value>
</data>
<data name="NEW_DISK_DIALOG_SR_HINT_TEXT" xml:space="preserve">
<value>Select a storage repository to create the disk on</value>
</data>
<data name="NEW_DVD_DRIVES_REQUIRED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>At least one of the VMs you wish to install [XenServer product] Tools onto has no DVD drive. Would you like to create a new DVD drive for each of the VMs that requires one?</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEW_DVD_DRIVE_CREATED" xml:space="preserve">
<value>DVD Drive Created</value>
</data>
<data name="NEW_DVD_DRIVE_CREATE_TITLE" xml:space="preserve">
<value>Creating new DVD drive on VM {0}</value>
</data>
<data name="NEW_DVD_DRIVE_CREATING" xml:space="preserve">
<value>Creating new DVD drive</value>
</data>
<data name="NEW_DVD_DRIVE_DONE" xml:space="preserve">
<value>Creating new DVD drive succeeded</value>
</data>
<data name="NEW_DVD_DRIVE_REBOOT" xml:space="preserve">
<value>You must shutdown and then restart the VM to finish the installation of the new DVD drive.</value>
</data>
<data name="NEW_DVD_DRIVE_REBOOT_TOOLS" xml:space="preserve">
<value>You must shutdown and then restart the VM to finish the installation of the new DVD drive.
2016-02-10 12:52:30 +01:00
Once the VM has restarted click the Install [XenServer product] Tools menu item once again.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEW_DVD_DRIVE_REQUIRED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>The VM you wish to install [XenServer product] Tools onto has no DVD drive, would you like to create one?</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NEW_FOLDER" xml:space="preserve">
<value>&New Folder...</value>
</data>
<data name="NEW_FOLDER_DIALOG_TITLE" xml:space="preserve">
<value>New Folder</value>
</data>
<data name="NEW_FOLDER_NAME" xml:space="preserve">
<value>&New folder name:</value>
</data>
<data name="NEW_POLICY" xml:space="preserve">
<value>&New Policy...</value>
</data>
<data name="NEW_POOL_AD_MESSAGE" xml:space="preserve">
<value>You are attempting to add the server '{0}' to a pool with a master that is configured to use AD authentication. All pool members must use the same authentication method.
Do you want to enable AD authentication on your server and join it to the same domain as the pool?</value>
</data>
<data name="NEW_POOL_AD_MESSAGE_MULTIPLE" xml:space="preserve">
<value>You are attempting to add the following servers to a pool with a master that is configured to use AD authentication:
{0}
All pool members must use the same authentication method. Do you want to enable AD authentication on these servers and join them to the same domain as the pool?</value>
</data>
<data name="NEW_POOL_CPU_MASKING_MESSAGE" xml:space="preserve">
<value>You are attempting to add the server '{0}' to a pool with a master that is using an older CPU.
2016-02-10 12:52:30 +01:00
[XenServer] can continue by rebooting the server and reducing its CPU to the level of the master. This will shut down any VMs running on the server. This feature is supported for CPU combinations listed in the [XenServer] Hardware Compatibility List.
2013-06-24 13:41:48 +02:00
Do you want to do this?</value>
</data>
<data name="NEW_POOL_CPU_MASKING_MESSAGE_MULTIPLE" xml:space="preserve">
<value>You are attempting to add the following servers to a pool with a master that is using an older CPU:
{0}
2016-02-10 12:52:30 +01:00
[XenServer] can continue by rebooting the servers and reducing their CPUs to the level of the master. This will shut down any VMs running on the servers. This feature is supported for CPU combinations listed in the [XenServer] Hardware Compatibility List.
2013-06-24 13:41:48 +02:00
Do you want to do this?</value>
</data>
<data name="NEW_POOL_LICENSE_MESSAGE" xml:space="preserve">
2015-01-23 11:12:02 +01:00
<value>You are attempting to add the server '{0}' to a licensed pool.
2013-06-24 13:41:48 +02:00
Do you want to apply the licensing from the master to this server?</value>
</data>
<data name="NEW_POOL_LICENSE_MESSAGE_MULTIPLE" xml:space="preserve">
2015-01-23 11:12:02 +01:00
<value>You are attempting to add the following servers to a licensed pool.
2013-06-24 13:41:48 +02:00
{0}
Do you want to apply the licensing from the master to these servers?</value>
</data>
<data name="NEW_POOL_SUPP_PACK" xml:space="preserve">
<value>The following supplemental pack should be installed on all servers in a pool, but currently is not:
{0}
It is strongly recommended that you Cancel and apply the latest version of the pack to all servers before creating the pool.</value>
</data>
<data name="NEW_POOL_SUPP_PACKS" xml:space="preserve">
<value>The following supplemental packs should be installed on all servers in a pool, but currently are not:
{0}
It is strongly recommended that you Cancel and apply the latest version of the packs to all servers before creating the pool.</value>
</data>
2016-02-19 06:49:24 +01:00
<data name="NEW_SCHEDULE" xml:space="preserve">
<value>&New schedule...</value>
</data>
2016-03-11 14:57:21 +01:00
<data name="NEW_SEARCH" xml:space="preserve">
<value>New Search</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEW_SR_CONNECTION_LOST" xml:space="preserve">
<value>Connection to {0} has been lost</value>
</data>
<data name="NEW_SR_DIALOG_ATTACH_NON_SHARED_DISK_HA" xml:space="preserve">
<value>The selected disk is not shared. If you add non shared disks to the VM it will became non-agile.
Do you want to continue?</value>
</data>
<data name="NEW_SR_WIZARD_FINAL_ACTION_END" xml:space="preserve">
<value>Attached SRs</value>
</data>
<data name="NEW_SR_WIZARD_FINAL_ACTION_START" xml:space="preserve">
<value>Attaching SRs</value>
</data>
<data name="NEW_SR_WIZARD_FINAL_ACTION_TITLE" xml:space="preserve">
<value>New Storage Repository</value>
</data>
<data name="NEW_TAG_LINK" xml:space="preserve">
<value>Edit tags...</value>
</data>
<data name="NEW_TEMPLATE_PROMPT" xml:space="preserve">
<value>Enter &name for new template:</value>
</data>
<data name="NEW_UPDATE_AVAILABLE" xml:space="preserve">
<value>New Update Available - {0}</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="NEW_VMPP_PAGE_TEXT" xml:space="preserve">
<value>Use this wizard to define a VM protection policy that will ensure your critical VMs are protected via automatic scheduled snapshot jobs.</value>
</data>
2016-02-19 06:49:24 +01:00
<data name="NEW_VMPP_PAGE_TEXT_MORE" xml:space="preserve">
<value>To begin, enter a name for the policy and a description (optional), then click Next.</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="NEW_VMSS_PAGE_TEXT" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Use this wizard to define a snapshot schedule that will create automatic scheduled snapshot jobs for your VMs.</value>
2016-01-29 12:34:44 +01:00
</data>
2016-02-19 06:49:24 +01:00
<data name="NEW_VMSS_PAGE_TEXT_MORE" xml:space="preserve">
<value>To begin, enter a name for the schedule and a description (optional), then click Next.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEW_VM_APPLIANCE" xml:space="preserve">
<value>&New vApp...</value>
</data>
<data name="NEW_VM_FREE_MEMORY_WARNING" xml:space="preserve">
<value>The amount of physical memory allocated to this VM is greater than the free memory of its home server</value>
</data>
<data name="NEW_VM_FROM_SNAPSHOT_MENU_ITEM" xml:space="preserve">
<value>&New VM From Snapshot...</value>
</data>
<data name="NEW_VM_TOTAL_MEMORY_WARNING" xml:space="preserve">
<value>The amount of physical memory allocated to this VM is greater than the total memory of its home server</value>
</data>
<data name="NEW_VM_WIZARD" xml:space="preserve">
<value>New VM</value>
</data>
<data name="NEW_VM_WIZARD_BIOS_STRINGS_CANNOT_BE_CHANGED" xml:space="preserve">
<value>The BIOS strings have already been set for this template and cannot be changed.</value>
</data>
<data name="NEW_VM_WIZARD_NO_SRS" xml:space="preserve">
<value>You must have some working storage to create a VM</value>
</data>
<data name="NEW_VM_WIZARD_NO_SR_OR_SRS_FULL" xml:space="preserve">
<value>Cannot find a storage repository or all your storage repositories are full.</value>
</data>
2016-10-21 19:46:38 +02:00
<data name="NEW_VM_WIZARD_TEMPLATEPAGE_NEOKYLIN" xml:space="preserve">
<value>NeoKylin</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NEW_VM_WIZARD_TEMPLATEPAGE_UBUNTU" xml:space="preserve">
<value>Ubuntu</value>
</data>
<data name="NFS_ISO_ALREADY_ATTACHED" xml:space="preserve">
<value>This NFS ISO storage is already attached to '{0}'</value>
</data>
<data name="NFS_ISO_PATH_EXAMPLE" xml:space="preserve">
<value>Example: server:/path</value>
</data>
<data name="NIC" xml:space="preserve">
<value>NIC</value>
</data>
<data name="NICPANEL_BIT_RATE" xml:space="preserve">
<value>{0} Mbit/s</value>
</data>
<data name="NICPANEL_FULL_DUPLEX" xml:space="preserve">
<value>Full</value>
</data>
<data name="NICPANEL_HALF_DUPLEX" xml:space="preserve">
<value>Half</value>
</data>
<data name="NIC_HIDDEN" xml:space="preserve">
<value>{0} (Hidden)</value>
</data>
<data name="NIC_SLAVE" xml:space="preserve">
<value>{0} (Slave)</value>
</data>
<data name="NIC_TAB_TITLE" xml:space="preserve">
<value>Network Interface Cards</value>
</data>
<data name="NIC_VLAN" xml:space="preserve">
<value>{0}, VLAN {1}</value>
</data>
<data name="NO" xml:space="preserve">
<value>No</value>
</data>
<data name="NONE" xml:space="preserve">
<value><None></value>
</data>
<data name="NONE_DEFINED" xml:space="preserve">
<value>None defined</value>
</data>
<data name="NONE_OF" xml:space="preserve">
<value>None of the following:</value>
</data>
<data name="NONE_PARENS" xml:space="preserve">
<value>(None)</value>
</data>
<data name="NOTICE_LICENCE_TITLE" xml:space="preserve">
<value>Server License</value>
</data>
2013-08-30 14:35:32 +02:00
<data name="NOTIFICATIONS_SUBMODE_ALERTS_READ" xml:space="preserve">
<value>Alerts</value>
</data>
<data name="NOTIFICATIONS_SUBMODE_ALERTS_UNREAD" xml:space="preserve">
<value>Alerts ({0})</value>
</data>
<data name="NOTIFICATIONS_SUBMODE_EVENTS_READ" xml:space="preserve">
<value>Events</value>
</data>
2013-11-19 16:42:47 +01:00
<data name="NOTIFICATIONS_SUBMODE_EVENTS_UNREAD_MANY" xml:space="preserve">
<value>Events ({0} errors)</value>
</data>
<data name="NOTIFICATIONS_SUBMODE_EVENTS_UNREAD_ONE" xml:space="preserve">
<value>Events (1 error)</value>
2013-08-30 14:35:32 +02:00
</data>
<data name="NOTIFICATIONS_SUBMODE_UPDATES_READ" xml:space="preserve">
<value>Updates</value>
</data>
<data name="NOTIFICATIONS_SUBMODE_UPDATES_UNREAD" xml:space="preserve">
<value>Updates ({0})</value>
</data>
2013-11-26 12:36:45 +01:00
<data name="NOTIFICATIONS_TOTAL" xml:space="preserve">
<value>Notifications ({0})</value>
</data>
<data name="NOTIFICATIONS_TOTAL_ZERO" xml:space="preserve">
<value>Notifications</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NOT_AGILE_NETWORK_NOT_SHARED" xml:space="preserve">
<value>The VM is not using a shared network. Restart cannot be guaranteed.</value>
</data>
<data name="NOT_AGILE_SR_NOT_SHARED" xml:space="preserve">
2013-09-26 16:48:58 +02:00
<value>The VM is using a non-shared SR. Restart cannot be guaranteed.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NOT_AGILE_UNKOWN" xml:space="preserve">
<value>The VM is not agile. Restart cannot be guaranteed.</value>
</data>
2013-11-14 12:57:28 +01:00
<data name="NOT_AGILE_VM_HAS_VGPU" xml:space="preserve">
<value>The VM has one or more virtual GPUs. Restart cannot be guaranteed.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NOT_APPLIED" xml:space="preserve">
<value>Not applied</value>
</data>
<data name="NOT_ATTACHED_TO" xml:space="preserve">
<value>not attached to</value>
</data>
<data name="NOT_CONTAINED_IN" xml:space="preserve">
<value>not contained in</value>
</data>
<data name="NOT_CONTAINS" xml:space="preserve">
<value>does not contain</value>
</data>
2015-02-12 14:11:16 +01:00
<data name="NOT_ENOUGH_SPACE_DESCRIPTION" xml:space="preserve">
<value>This host does not have enough disk space to install this update</value>
</data>
2016-08-05 16:56:55 +02:00
<data name="NOT_ENOUGH_SPACE_MESSAGE_AUTO_UPDATE" xml:space="preserve">
2016-12-12 19:12:01 +01:00
<value>There is not enough space to update '{0}' with automated updates.</value>
2016-08-05 16:56:55 +02:00
</data>
2015-02-05 18:01:14 +01:00
<data name="NOT_ENOUGH_SPACE_MESSAGE_AVAILABLE_SPACE" xml:space="preserve">
<value>Space available: {0}</value>
</data>
<data name="NOT_ENOUGH_SPACE_MESSAGE_CLEANUP" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] can free up {0} by removing residual update files. Do you wish to proceed with the cleanup?</value>
2015-02-05 18:01:14 +01:00
</data>
2015-02-12 14:11:16 +01:00
<data name="NOT_ENOUGH_SPACE_MESSAGE_INSTALL" xml:space="preserve">
2015-02-12 14:59:49 +01:00
<value>There is not enough space on '{0}' to install update '{1}'.</value>
2015-02-12 14:11:16 +01:00
</data>
2015-02-05 18:01:14 +01:00
<data name="NOT_ENOUGH_SPACE_MESSAGE_NOCLEANUP" xml:space="preserve">
2015-02-20 14:20:05 +01:00
<value>Free up some space and try again.</value>
2015-02-05 18:01:14 +01:00
</data>
<data name="NOT_ENOUGH_SPACE_MESSAGE_REQUIRED_SPACE" xml:space="preserve">
<value>Space required: {0}</value>
</data>
2015-02-12 14:11:16 +01:00
<data name="NOT_ENOUGH_SPACE_MESSAGE_UPLOAD" xml:space="preserve">
2015-02-12 14:59:49 +01:00
<value>There is not enough space on '{0}' to upload update '{1}'.</value>
2015-02-12 14:11:16 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="NOT_IN_A_FOLDER" xml:space="preserve">
<value>Not in any folder</value>
</data>
2015-06-09 18:21:50 +02:00
<data name="NOT_SAFE_TO_UPGRADE_DEFAULT_WARNING_LONG" xml:space="preserve">
2015-06-04 16:24:04 +02:00
<value>VMs on local disk will prevent disk repartitioning.
2017-01-17 16:09:36 +01:00
A new disk partitioning scheme is available in [XenServer] [BRANDING_VERSION_7_0] and above that includes larger dom0 and backup partitions, and dedicated partitions for logging, swap and UEFI.
2015-06-04 16:24:04 +02:00
2017-01-17 16:09:36 +01:00
However, there are VMs on local storage, so the current partitioning scheme will be retained. To benefit from repartitioning on upgrade to [XenServer] [BRANDING_VERSION_7_0] or above, VMs must be moved from local storage first.</value>
2015-06-04 16:24:04 +02:00
</data>
2015-06-09 18:21:50 +02:00
<data name="NOT_SAFE_TO_UPGRADE_DEFAULT_WARNING_SHORT" xml:space="preserve">
2015-06-04 16:24:04 +02:00
<value>{0}: VMs on local disk will prevent disk repartitioning.</value>
</data>
2015-06-09 18:21:50 +02:00
<data name="NOT_SAFE_TO_UPGRADE_NOT_ENOUGH_SPACE_LONG" xml:space="preserve">
<value>The disk size of the local storage prevents repartitioning.
2017-01-17 16:09:36 +01:00
A new disk partitioning scheme is available in [XenServer] [BRANDING_VERSION_7_0] and above that includes larger dom0 and backup partitions, and dedicated partitions for logging, swap and UEFI.
2015-06-09 18:21:50 +02:00
2015-06-15 17:19:52 +02:00
However, there is not enough space to perform the repartitioning, so the current partitioning scheme will be retained.</value>
2015-06-09 18:21:50 +02:00
</data>
<data name="NOT_SAFE_TO_UPGRADE_NOT_ENOUGH_SPACE_SHORT" xml:space="preserve">
<value>{0}: The disk size of the local storage prevents repartitioning.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NOT_TRUSTED" xml:space="preserve">
<value>not trusted</value>
</data>
<data name="NOT_UPGRADED" xml:space="preserve">
<value>Not Upgraded</value>
</data>
<data name="NOT_UPLOADED" xml:space="preserve">
<value>Not uploaded</value>
</data>
<data name="NOT_YET_RUN" xml:space="preserve">
<value>Not yet run</value>
</data>
<data name="NOW" xml:space="preserve">
<value>Now</value>
</data>
<data name="NO_BUTTON_CAPTION" xml:space="preserve">
<value>&No</value>
</data>
<data name="NO_DISKS" xml:space="preserve">
<value>This VM does not have any disks.</value>
</data>
<data name="NO_ELIGIBLE_MASTER" xml:space="preserve">
<value>There is no server eligible to become the master of your new pool</value>
</data>
2015-03-31 18:26:37 +02:00
<data name="NO_GPU_IN_POOL" xml:space="preserve">
<value>GPU configuration and monitoring is disabled, because there are no GPUs available in this pool.</value>
</data>
<data name="NO_GPU_ON_HOST" xml:space="preserve">
<value>GPU configuration and monitoring is disabled, because there are no GPUs available on this host.</value>
2015-01-23 11:41:54 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="NO_HALTED_VMS" xml:space="preserve">
<value>There are no halted or suspended VMs to export</value>
</data>
<data name="NO_HOME_SERVER" xml:space="preserve">
<value>Home Server is not set</value>
</data>
<data name="NO_MESSAGES_TO_DISMISS" xml:space="preserve">
<value>There are no system alerts available to dismiss.</value>
</data>
<data name="NO_MORE_USERDEVICES" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] cannot create any more disks for this VM</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NO_NAME" xml:space="preserve">
<value>(No Name)</value>
</data>
<data name="NO_SCREENSHOT" xml:space="preserve">
<value>No screenshot</value>
</data>
<data name="NO_SERVERS_NEED_ACTIVATING" xml:space="preserve">
<value>There are no servers that need activating at this time.</value>
</data>
<data name="NO_SESSION_INFO" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>No [XenServer] session information is available, cannot continue.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="NO_SNAPSHOTS" xml:space="preserve">
<value>This VM does not have any snapshots.</value>
</data>
<data name="NO_TIMELINE_INTERVALS_TEXT" xml:space="preserve">
<value>(There are currenltly no added timeline intervals)</value>
</data>
<data name="NO_VALID_DISK_LOCATION" xml:space="preserve">
<value>There are no SR locations that can support this disk</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="NO_VALUE" xml:space="preserve">
<value>-</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="NUMBER_OF_SNAPSHOTS_TO_KEEP" xml:space="preserve">
<value>Number of snapshots to keep</value>
</data>
<data name="NUMBER_OF_SOCKETS" xml:space="preserve">
<value>Number of Sockets</value>
</data>
<data name="NUMBER_SNAPSHOTS" xml:space="preserve">
<value>{0} snapshots</value>
</data>
<data name="OBJECTS_WITH_TAG" xml:space="preserve">
<value>Objects with tag '{0}'</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="OBJECT_IN_POOL" xml:space="preserve">
<value>{0} in '{1}'</value>
</data>
<data name="OBJECT_ON_SERVER" xml:space="preserve">
<value>{0} on '{1}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="OK" xml:space="preserve">
<value>OK</value>
</data>
<data name="OLDER_THAN_CURRENT_SERVER" xml:space="preserve">
<value>Older than current server</value>
</data>
<data name="OLD_CONNECTION_ALREADY_CONNECTED" xml:space="preserve">
<value>You are already connected to '{0}'</value>
</data>
<data name="ONE_VM_SELECTED" xml:space="preserve">
<value>1 VM selected</value>
</data>
<data name="ONLY_VMS_USING_STORAGELINK_SMIS" xml:space="preserve">
<value>Only VMs using StorageLink Gateway NetApp, Dell EqualLogic or SMI-S adapters can be upgraded</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="ON_SERVER" xml:space="preserve">
<value>on '{0}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="OPERATING_SYSTEM" xml:space="preserve">
<value>Operating System</value>
</data>
<data name="OPTIMIZED" xml:space="preserve">
<value>Optimized</value>
</data>
<data name="OUT_OF_DATE" xml:space="preserve">
<value>Out of date</value>
</data>
<data name="OVERALL_PROGRESS" xml:space="preserve">
<value>Overall progress: {0} of {1} servers done</value>
</data>
<data name="OVERCOMMIT" xml:space="preserve">
<value>({0}% of total memory)</value>
</data>
<data name="OVERCOMMIT_LABEL" xml:space="preserve">
<value>Overcommit:</value>
</data>
<data name="OVERVIEW_CPU_USAGE" xml:space="preserve">
<value>CPU Usage</value>
</data>
<data name="OVERVIEW_DISKS" xml:space="preserve">
<value>Disks</value>
</data>
<data name="OVERVIEW_MEMORY_USAGE" xml:space="preserve">
<value>Used Memory</value>
</data>
<data name="OVERVIEW_NAME" xml:space="preserve">
<value>Name</value>
</data>
<data name="OVERVIEW_NETWORK" xml:space="preserve">
<value>Network</value>
</data>
<data name="OVERVIEW_NO_RESULTS" xml:space="preserve">
<value>No results found</value>
</data>
<data name="OVERVIEW_UNITS" xml:space="preserve">
<value>(avg / max KBs)</value>
</data>
<data name="OVF_CREATED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Created by [XenCenter] Disk Image Import</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="OVF_DISK_CAPTION" xml:space="preserve">
<value>Virtual Disk</value>
</data>
<data name="OVF_NET_DESCRIPTION" xml:space="preserve">
<value>Virtual Network</value>
</data>
<data name="PARENT_FOLDER" xml:space="preserve">
<value>Parent folder</value>
</data>
<data name="PARTIALLY_APPLIED" xml:space="preserve">
<value>Applied on some servers</value>
</data>
<data name="PARTIALLY_CONNECTED" xml:space="preserve">
<value>Partially connected</value>
</data>
<data name="PARTIALLY_LICENSED" xml:space="preserve">
<value>Partially Licensed</value>
</data>
<data name="PASSPHRASE_STRENGTH_FAIR" xml:space="preserve">
<value>Fair</value>
</data>
<data name="PASSPHRASE_STRENGTH_GOOD" xml:space="preserve">
<value>Good</value>
</data>
<data name="PASSPHRASE_STRENGTH_LOW" xml:space="preserve">
<value>Low</value>
</data>
<data name="PASSPHRASE_STRENGTH_PROMPT" xml:space="preserve">
<value>Password strength: {0}</value>
</data>
<data name="PASSPHRASE_STRENGTH_STRONG" xml:space="preserve">
<value>Strong</value>
</data>
<data name="PASSPHRASE_STRENGTH_UNKNOWN" xml:space="preserve">
<value>Unknown</value>
</data>
<data name="PASSWORDS_DONT_MATCH" xml:space="preserve">
<value>Passwords do not match</value>
</data>
<data name="PASSWORDS_EMPTY" xml:space="preserve">
<value>Passwords cannot be empty</value>
</data>
<data name="PASSWORDS_REQUEST_ALWAYS_DISABLED_TOOLTIP_BODY" xml:space="preserve">
<value>You have set a master password, so "Give Passwords Always" is not available.</value>
</data>
<data name="PASSWORD_INCORRECT" xml:space="preserve">
<value>The password you typed was incorrect</value>
</data>
<data name="PASTE" xml:space="preserve">
<value>Paste</value>
</data>
2016-05-18 14:43:34 +02:00
<data name="PATCHINGWIZARD_AUTOUPDATINGPAGE_ERROR" xml:space="preserve">
2016-12-10 15:19:37 +01:00
<value>The automated updates process was not completed successfully.</value>
2016-05-18 14:43:34 +02:00
</data>
2016-06-22 15:43:22 +02:00
<data name="PATCHINGWIZARD_AUTOUPDATINGPAGE_ERRORS_OCCURRED" xml:space="preserve">
2016-12-10 15:19:37 +01:00
<value>The following errors occurred while automated updates were in progress:</value>
2016-05-18 14:43:34 +02:00
</data>
2016-06-22 15:43:22 +02:00
<data name="PATCHINGWIZARD_AUTOUPDATINGPAGE_ERROR_OCCURRED" xml:space="preserve">
2016-12-10 15:19:37 +01:00
<value>The following error occurred while automated updates were in progress:</value>
2016-05-18 14:43:34 +02:00
</data>
<data name="PATCHINGWIZARD_AUTOUPDATINGPAGE_FAILED" xml:space="preserve">
2016-12-10 15:19:37 +01:00
<value>The update was not completed successfully</value>
2016-05-18 14:43:34 +02:00
</data>
2016-03-16 14:22:23 +01:00
<data name="PATCHINGWIZARD_AUTOUPDATINGPAGE_TEXT" xml:space="preserve">
<value>Upload and Install</value>
</data>
<data name="PATCHINGWIZARD_AUTOUPDATINGPAGE_TITLE" xml:space="preserve">
2016-12-12 19:12:01 +01:00
<value>Uploading and installing updates</value>
2016-03-16 14:22:23 +01:00
</data>
2015-02-05 18:01:14 +01:00
<data name="PATCHINGWIZARD_CLEANUP" xml:space="preserve">
2015-02-16 12:11:30 +01:00
<value>Clean up...</value>
2015-02-05 18:01:14 +01:00
</data>
2016-06-01 14:45:21 +02:00
<data name="PATCHINGWIZARD_DOWNLOADUPDATE_ACTION_TITLE_DOWNLOADING" xml:space="preserve">
<value>Downloading update {0}...</value>
</data>
<data name="PATCHINGWIZARD_DOWNLOADUPDATE_ACTION_TITLE_SKIPPING" xml:space="preserve">
<value>Skipping download: Already downloaded update {0}...</value>
</data>
<data name="PATCHINGWIZARD_DOWNLOADUPDATE_ACTION_TITLE_WAITING" xml:space="preserve">
<value>Waiting to download update {0}...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="PATCHINGWIZARD_MODEPAGE_NOACTION" xml:space="preserve">
<value>No action required</value>
</data>
<data name="PATCHINGWIZARD_MODEPAGE_RESTARTSERVERS" xml:space="preserve">
<value>Restart these servers in this order (master always first):</value>
</data>
<data name="PATCHINGWIZARD_MODEPAGE_RESTARTVMS" xml:space="preserve">
<value>Restart these VMs:</value>
</data>
<data name="PATCHINGWIZARD_MODEPAGE_RESTARTXAPI" xml:space="preserve">
<value>Restart XAPI agent in this order (master always first):</value>
</data>
<data name="PATCHINGWIZARD_MODEPAGE_TEXT" xml:space="preserve">
<value>Update Mode</value>
</data>
<data name="PATCHINGWIZARD_MODEPAGE_TITLE" xml:space="preserve">
<value>Select the update mode</value>
</data>
<data name="PATCHINGWIZARD_MODEPAGE_UNKNOWNACTION" xml:space="preserve">
<value>Unknown</value>
</data>
2015-02-05 18:01:14 +01:00
<data name="PATCHINGWIZARD_MORE_INFO" xml:space="preserve">
2015-02-16 12:11:30 +01:00
<value>More info...</value>
2015-02-05 18:01:14 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="PATCHINGWIZARD_PATCHINGPAGE_POOL_RESOLVE" xml:space="preserve">
<value>Resolve pool problems</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_POOL_RESOLVED" xml:space="preserve">
<value>Pool problems resolved</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_POOL_RESOLVING" xml:space="preserve">
<value>Resolving pool problems...</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_POOL_REVERT" xml:space="preserve">
<value>Revert pool problems</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_POOL_REVERTED" xml:space="preserve">
<value>Pool problems reverted</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_POOL_REVERTING" xml:space="preserve">
<value>Reverting pool problems...</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_PRECHECK_REVERT" xml:space="preserve">
<value>Revert resolved prechecks</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_PRECHECK_REVERTED" xml:space="preserve">
<value>Resolved prechecks reverted</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_PRECHECK_REVERTING" xml:space="preserve">
<value>Reverting resolved prechecks...</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_SERVER_RESOLVE" xml:space="preserve">
<value>Resolve server problems</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_SERVER_RESOLVED" xml:space="preserve">
<value>Server problems resolved</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_SERVER_RESOLVING" xml:space="preserve">
<value>Resolving server problems...</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_SERVER_REVERT" xml:space="preserve">
<value>Revert server problems</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_SERVER_REVERTED" xml:space="preserve">
<value>Server problems reverted</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_SERVER_REVERTING" xml:space="preserve">
<value>Reverting server problems...</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_TEXT" xml:space="preserve">
<value>Install Update</value>
</data>
<data name="PATCHINGWIZARD_PATCHINGPAGE_TITLE" xml:space="preserve">
<value>Install the update</value>
</data>
2016-08-05 16:56:55 +02:00
<data name="PATCHINGWIZARD_PRECHECKPAGE_CHECKING_DISK_SPACE" xml:space="preserve">
<value>Checking disk space requirements</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="PATCHINGWIZARD_PRECHECKPAGE_FAILED" xml:space="preserve">
<value>Prechecks failed.</value>
</data>
<data name="PATCHINGWIZARD_PRECHECKPAGE_FIRSTLINE" xml:space="preserve">
<value>Update prechecks are performed to verify that the update "{0}" can be applied to the servers.</value>
</data>
2016-12-10 16:01:25 +01:00
<data name="PATCHINGWIZARD_PRECHECKPAGE_FIRSTLINE_AUTOMATED_UPDATES_MODE" xml:space="preserve">
2016-12-10 15:19:37 +01:00
<value>Prechecks are performed to verify that automated updates can proceed.</value>
2016-03-17 17:35:00 +01:00
</data>
2015-01-20 15:22:29 +01:00
<data name="PATCHINGWIZARD_PRECHECKPAGE_FIRSTLINE_NO_PATCH_NAME" xml:space="preserve">
<value>Update prechecks are performed to verify that the selected update can be applied to the servers.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="PATCHINGWIZARD_PRECHECKPAGE_RESOLVE" xml:space="preserve">
<value>Resolve</value>
</data>
2016-06-07 18:40:59 +02:00
<data name="PATCHINGWIZARD_PRECHECKPAGE_RESOLVING_ALL" xml:space="preserve">
<value>Resolving issues...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="PATCHINGWIZARD_PRECHECKPAGE_TEXT" xml:space="preserve">
<value>Prechecks</value>
</data>
<data name="PATCHINGWIZARD_PRECHECKPAGE_TITLE" xml:space="preserve">
<value>Perform update prechecks on selected servers</value>
</data>
2016-11-16 13:35:09 +01:00
<data name="PATCHINGWIZARD_REMOVED_UPDATES" xml:space="preserve">
<value>Deleted update installation files</value>
</data>
<data name="PATCHINGWIZARD_REMOVE_UPDATES" xml:space="preserve">
<value>Delete update installation files</value>
</data>
<data name="PATCHINGWIZARD_REMOVING_UPDATES" xml:space="preserve">
<value>Deleting update installation files</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="PATCHINGWIZARD_SELECTPATCHPAGE_CHOOSE" xml:space="preserve">
<value>Choose Update File</value>
</data>
<data name="PATCHINGWIZARD_SELECTPATCHPAGE_TEXT" xml:space="preserve">
<value>Select Update</value>
</data>
<data name="PATCHINGWIZARD_SELECTPATCHPAGE_TITLE" xml:space="preserve">
<value>Choose an existing update to install or upload a new one</value>
</data>
<data name="PATCHINGWIZARD_SELECTPATCHPAGE_UPDATESEXT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] Updates and Supplemental Packs (*.{0}, *.iso)|*.{0};*.iso</value>
2015-01-20 15:22:29 +01:00
</data>
2016-12-10 16:01:25 +01:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_AUTOMATED_UPDATES_NOT_SUPPORTED_HOST_VERSION" xml:space="preserve">
2016-12-10 15:19:37 +01:00
<value>Automated updates are not supported on this [XenServer] version</value>
2016-08-08 19:30:54 +02:00
</data>
2016-12-10 16:01:25 +01:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_AUTOMATED_UPDATES_NOT_SUPPORTED_PARTIALLY_UPGRADED" xml:space="preserve">
2016-12-10 15:19:37 +01:00
<value>Automated updates are not supported on partially upgraded [XenServer] pools</value>
2016-08-10 11:48:22 +02:00
</data>
2015-01-20 15:22:29 +01:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_CANNOT_INSTALL_SUPP_PACKS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Cannot install supplemental packs on this [XenServer] version</value>
2013-06-24 13:41:48 +02:00
</data>
2014-04-29 16:46:15 +02:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_HOST_UNLICENSED" xml:space="preserve">
<value>Subscription Advantage required</value>
</data>
2016-12-10 16:01:25 +01:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_HOST_UNLICENSED_FOR_AUTOMATED_UPDATES" xml:space="preserve">
2016-12-10 15:19:37 +01:00
<value>The server is not licensed for automated updates</value>
2016-05-04 11:27:10 +02:00
</data>
2017-01-24 18:41:35 +01:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_HOST_UNREACHABLE" xml:space="preserve">
<value>The server is unreachable</value>
</data>
2017-02-27 17:14:42 +01:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_MIXED_VERSIONS" xml:space="preserve">
<value>The same update cannot be applied to {0} and {1} versions of [XenServer]</value>
</data>
2014-04-29 16:46:15 +02:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_PATCH_ALREADY_APPLIED" xml:space="preserve">
<value>Update already applied</value>
</data>
2015-07-20 15:28:44 +02:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_PATCH_NOT_APPLICABLE" xml:space="preserve">
<value>Update not applicable</value>
</data>
2016-12-10 16:01:25 +01:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_RUBRIC_AUTOMATED_MODE" xml:space="preserve">
2017-01-18 11:59:35 +01:00
<value>Select one or more pools or standalone servers that you want to have updated.
2016-12-12 19:12:01 +01:00
Greyed out servers cannot be updated with automated updates.</value>
2016-12-10 16:01:25 +01:00
</data>
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_RUBRIC_DEFAULT" xml:space="preserve">
2017-01-18 11:59:35 +01:00
<value>Select one or more servers where you want to apply the selected update.
Servers where this update cannot be applied appear disabled in this list.</value>
</data>
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_RUBRIC_POOL_SELECTION" xml:space="preserve">
<value>Select one or more pools or standalone servers where you want to apply the selected update.
Servers where this update cannot be applied appear disabled in this list.</value>
2016-12-10 16:01:25 +01:00
</data>
2016-05-31 20:00:35 +02:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_SERVER_NOT_AUTO_UPGRADABLE" xml:space="preserve">
2016-12-12 19:12:01 +01:00
<value>This server cannot be updated with automated updates</value>
2016-05-31 20:00:35 +02:00
</data>
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_SERVER_UP_TO_DATE" xml:space="preserve">
2016-08-12 10:15:42 +02:00
<value>This server is already up-to-date</value>
2016-05-31 20:00:35 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_TEXT" xml:space="preserve">
<value>Select Servers</value>
</data>
<data name="PATCHINGWIZARD_SELECTSERVERPAGE_TITLE" xml:space="preserve">
<value>Select the servers you wish to update</value>
</data>
2016-12-10 16:01:25 +01:00
<data name="PATCHINGWIZARD_UPDATES_DONE_AUTOMATED_UPDATES_MODE" xml:space="preserve">
2016-12-10 15:19:37 +01:00
<value>Automated updates have finished.</value>
2016-03-31 16:40:23 +02:00
</data>
2015-09-07 14:37:52 +02:00
<data name="PATCHINGWIZARD_UPLOADPAGE_MESSAGE_DOWNLOAD_AND_UPLOAD" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] is now downloading your update and uploading it to the servers specified in the previous step.
2015-09-07 14:37:52 +02:00
Please wait for these operations to complete, then click Next to continue with the installation.</value>
</data>
<data name="PATCHINGWIZARD_UPLOADPAGE_MESSAGE_ONLY_UPLOAD" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] is now uploading your update to the servers specified in the previous step.
2015-09-07 14:37:52 +02:00
Please wait for this operation to complete, then click Next to continue with the installation.</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="PATCHINGWIZARD_UPLOADPAGE_TEXT" xml:space="preserve">
<value>Upload</value>
</data>
2015-09-07 14:37:52 +02:00
<data name="PATCHINGWIZARD_UPLOADPAGE_TITLE_DOWNLOAD_AND_UPLOAD" xml:space="preserve">
<value>Downloading and uploading the selected file to your servers</value>
</data>
<data name="PATCHINGWIZARD_UPLOADPAGE_TITLE_ONLY_UPLOAD" xml:space="preserve">
<value>Uploading the selected file to your servers</value>
2015-01-23 11:41:54 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="PATCHING_EJECT_CDS" xml:space="preserve">
<value>Eject any virtual CDs from your VMs</value>
</data>
<data name="PATCHING_WARNING_HA" xml:space="preserve">
<value>Disable HA until after all the hosts have been rebooted</value>
</data>
<data name="PATCHING_WIZARD_CONFIRMATION_DELETE" xml:space="preserve">
<value>The patch {0} is going to be deleted. Do you want to continue?</value>
</data>
<data name="PATCHING_WIZARD_DESC_CELL_INDENT" xml:space="preserve">
<value>{0,4}{1}</value>
</data>
<data name="PATCHING_WIZARD_ERROR" xml:space="preserve">
2015-02-27 18:00:03 +01:00
<value>{0} error.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PATCHING_WIZARD_HOST_CHECK_OK" xml:space="preserve">
<value>{0}: {1} ok.</value>
</data>
<data name="PATCHING_WIZARD_PRECHECK_STATUS" xml:space="preserve">
<value>{0} ...</value>
</data>
2016-08-12 14:15:18 +02:00
<data name="PATCHING_WIZARD_RUNNING_PRECHECKS" xml:space="preserve">
<value>Running prechecks...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="PATCHING_WIZARD_SOLVE_MANUALLY" xml:space="preserve">
<value>Unable to resolve this issue:\n{0}\n\nPlease resolve this issue manually and then click Check Again.
</value>
</data>
<data name="PATCHING_WIZARD_SOLVING_PROBLEMS" xml:space="preserve">
<value>Solving problems</value>
</data>
2015-07-09 17:59:14 +02:00
<data name="PATCHING_WIZARD_WEBPAGE_CELL" xml:space="preserve">
<value>Go to web page</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="PATCH_APPLIED" xml:space="preserve">
<value>Update '{0}' Applied to Server '{1}'</value>
</data>
2015-02-06 13:32:29 +01:00
<data name="PATCH_DESCRIPTION_AND_INSTALLATION_SIZE" xml:space="preserve">
<value>{0}
Installation size: {1}</value>
2015-02-23 15:34:35 +01:00
</data>
<data name="PATCH_DOWNLOAD_FAILED" xml:space="preserve">
<value>Failed to download {0} from '{1}'</value>
</data>
<data name="PATCH_DOWNLOAD_FAILED_MORE_INFO" xml:space="preserve">
<value>Failed to download the update {0} from '{1}'.
The update is installed on '{1}', but the update installation file may have since been deleted.
2016-02-04 11:55:18 +01:00
Upload the update from an .{2} file instead.</value>
2015-02-26 15:12:31 +01:00
</data>
<data name="PATCH_DOWNLOAD_FAILED_MORE_INFO_NOT_APPLIED" xml:space="preserve">
<value>Failed to download the update {0} from '{1}'.
The update has previously been uploaded to '{1}', but the update installation file may have since been deleted.
2016-02-04 11:55:18 +01:00
Upload the update from an .{2} file instead.</value>
2015-02-06 13:32:29 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="PATCH_EXPANDED_DESCRIPTION" xml:space="preserve">
<value>{0}
Date modified: {1}
Date created: {2}
2015-01-20 15:22:29 +01:00
Size: {3}</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PATCH_FOR_XENSERVER_VERSION" xml:space="preserve">
2016-11-25 11:45:44 +01:00
<value>{0}: This patch is for servers with version matching the regular expression '{1}'.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PATCH_NOT_FOUND" xml:space="preserve">
<value>Not found</value>
</data>
<data name="PATCH_NOT_FOUND_EXPANDED_DESCRIPTION" xml:space="preserve">
<value>{0}
File not found</value>
</data>
<data name="PATCH_UPLOADED" xml:space="preserve">
2015-01-14 15:34:12 +01:00
<value>Update uploaded to server '{0}' </value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PATHPICKER_FILETYPE" xml:space="preserve">
2016-02-24 16:33:18 +01:00
<value>XVA (*.xva)|*.xva|XVA Version 1 (ova.xml)|ova.xml</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PBDS_CHECK_DESCRIPTION" xml:space="preserve">
<value>Storage connection check</value>
</data>
<data name="PDSECTION_TITLE" xml:space="preserve">
<value>Title</value>
</data>
<data name="PERFORMANCE_TAB_TITLE" xml:space="preserve">
<value>Performance Graphs</value>
</data>
<data name="PERFORM_ALERT_EDIT_INTERVAL_WRONG_MULTIPLE" xml:space="preserve">
<value>Interval must be a multiple of 5</value>
</data>
<data name="PERFORM_ROLLING_UPGRADE_INTERACTIVE_MODE" xml:space="preserve">
<value>Perform the rolling pool upgrade (Manual Mode)</value>
</data>
<data name="PERMISSION_DENIED" xml:space="preserve">
<value>Permission Denied</value>
</data>
<data name="PERSOCKET_LICENSES_X_REQUIRED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[Citrix] [XenServer product] Per-&Socket ({0} required)</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PHYSICAL_DEVICE" xml:space="preserve">
<value>Physical device</value>
</data>
<data name="PIF_BOND" xml:space="preserve">
<value>Bond {0}</value>
</data>
<data name="PIF_DHCP" xml:space="preserve">
<value>DHCP</value>
</data>
<data name="PIF_IN_USE_BY_VMS" xml:space="preserve">
<value>in use by VMs</value>
</data>
<data name="PIF_MANAGEMENT_INTERFACES" xml:space="preserve">
<value>Management Interfaces</value>
</data>
<data name="PIF_NIC" xml:space="preserve">
<value>NIC {0}</value>
</data>
<data name="PIF_NONE" xml:space="preserve">
<value>None</value>
</data>
<data name="PIF_STATIC" xml:space="preserve">
<value>Static</value>
</data>
<data name="PIF_UNKNOWN" xml:space="preserve">
<value>Unknown</value>
</data>
<data name="PII_CUSTOMISED" xml:space="preserve">
2013-11-04 15:09:50 +01:00
<value>These files may contain personally identifiable information if customized.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PII_MAYBE" xml:space="preserve">
2013-11-04 15:09:50 +01:00
<value>These files may contain personally identifiable information.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PII_NO" xml:space="preserve">
2013-11-04 15:09:50 +01:00
<value>These files will contain no personally identifiable information.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PII_YES" xml:space="preserve">
2013-11-04 15:09:50 +01:00
<value>These files will contain personally identifiable information.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PLANACTION_VMS_MIGRATE" xml:space="preserve">
<value>Migrate VMs from Server</value>
</data>
<data name="PLANACTION_VMS_MIGRATED" xml:space="preserve">
<value>VMs migrated from Server</value>
</data>
<data name="PLANACTION_VMS_MIGRATING" xml:space="preserve">
<value>Migrating VMs off server '{0}' ... </value>
</data>
<data name="PLANACTION_VMS_REBOOT" xml:space="preserve">
<value>Reboot specified VMs</value>
</data>
<data name="PLANACTION_VMS_REBOOTED" xml:space="preserve">
<value>Rebooted specified VMs</value>
</data>
<data name="PLANACTION_VMS_REBOOTING" xml:space="preserve">
<value>Rebooting specified VMs ... </value>
</data>
<data name="PLAN_ACTION_STATUS_DISABLING_HOST_SERVER" xml:space="preserve">
<value>Disabling host server</value>
</data>
<data name="PLAN_ACTION_STATUS_HOST_UPGRADED" xml:space="preserve">
<value>Host has been upgraded</value>
</data>
<data name="PLAN_ACTION_STATUS_INSTALLING_XENSERVER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Installing [XenServer]</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PLAN_ACTION_STATUS_MIGRATING_VMS_FROM_HOST" xml:space="preserve">
<value>Migrating VMs from host</value>
</data>
<data name="PLAN_ACTION_STATUS_MIGRATING_VM_X_OF_Y" xml:space="preserve">
<value>Migrating VM {0} of {1} back to Host</value>
</data>
<data name="PLAN_ACTION_STATUS_RECONNECTING_STORAGE" xml:space="preserve">
<value>Reconnecting storage</value>
</data>
<data name="PLAN_ACTION_STATUS_REENABLING_HOST" xml:space="preserve">
<value>Re-enabling host</value>
</data>
<data name="PLEASE_RECONNECT_HOST" xml:space="preserve">
<value>{0}
Please reconnect the host and try again</value>
</data>
<data name="PLUGINS" xml:space="preserve">
<value>Plugins</value>
</data>
<data name="PLUGINS_DESC" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Adjust settings for plugins to [XenCenter]</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PLUGINS_MENU_ITEMS_ONLY_ONE_CHILD_ALLOWED" xml:space="preserve">
<value>Menu item features must only have a single command XML node as a child</value>
</data>
<data name="PLUGINS_UNRECOGNISED_XML_NODE" xml:space="preserve">
<value>Unexpected XML node '{0}' found as child of node '{1}'</value>
</data>
<data name="PLUGIN_CALLING" xml:space="preserve">
<value>Running plug-in '{0}'</value>
</data>
<data name="PLUGIN_COPYRIGHT" xml:space="preserve">
<value>Copyright</value>
</data>
<data name="PLUGIN_ENABLED_COUNT" xml:space="preserve">
<value>{0} plugins enabled</value>
</data>
2013-08-30 16:27:24 +02:00
<data name="PLUGIN_ENABLED_COUNT_ONE" xml:space="preserve">
<value>1 plugin enabled</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="PLUGIN_FEATURES" xml:space="preserve">
<value>Features</value>
</data>
<data name="PLUGIN_LINK" xml:space="preserve">
<value>Link</value>
</data>
<data name="PLUGIN_SUCCEED" xml:space="preserve">
<value>Plug-in '{0}' completed successfully.</value>
</data>
<data name="PLUGIN_TITLE" xml:space="preserve">
<value>Call plug-in '{0}'</value>
</data>
<data name="PLUGIN_VERSION" xml:space="preserve">
<value>Version</value>
</data>
<data name="PM_MODE_CUSTOM" xml:space="preserve">
<value>Custom</value>
</data>
<data name="PM_MODE_DISABLED" xml:space="preserve">
<value>Disabled</value>
</data>
<data name="PM_MODE_DRAC" xml:space="preserve">
<value>Dell DRAC</value>
</data>
<data name="PM_MODE_ILO" xml:space="preserve">
<value>iLO</value>
</data>
<data name="PM_MODE_WOL" xml:space="preserve">
<value>Wake on LAN</value>
</data>
<data name="POLICY_DOES_NOT_HAVE_ARCHIVE" xml:space="preserve">
<value>Unable to archive the selected snapshot(s).
The VM protection policy for this VM does not have automatic archiving configured. Do you want to edit the policy and configure it now?</value>
</data>
<data name="POLICY_DOES_NOT_HAVE_ARCHIVE_TITLE" xml:space="preserve">
<value>Archive Snapshot Now</value>
</data>
<data name="POLICY_NAME" xml:space="preserve">
<value>Policy Name</value>
</data>
2016-02-19 06:49:24 +01:00
<data name="POLICY_NAME_FIELD_TEXT" xml:space="preserve">
<value>Policy na&me:</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="POLICY_NAME_TITLE" xml:space="preserve">
<value>What do you want to call this policy?</value>
</data>
<data name="POLICY_SUMMARY" xml:space="preserve">
<value>Job name:\r\n {0}\r\n\r\nSelected VMs:\r\n {1}\r\n\r\nSnapshot type:\r\n {2}\r\n\r\nSchedule:\r\n {3}\r\n\r\nArchive:\r\n {4}</value>
</data>
<data name="POOL" xml:space="preserve">
<value>Pool</value>
</data>
<data name="POOLCREATE_ADDED" xml:space="preserve">
<value>Added to pool</value>
</data>
<data name="POOLCREATE_ADDING" xml:space="preserve">
<value>Adding to Pool</value>
</data>
<data name="POOLCREATE_CREATING" xml:space="preserve">
<value>Creating pool</value>
</data>
<data name="POOLCREATE_DESTROYED" xml:space="preserve">
2014-05-15 19:47:13 +02:00
<value>Made pool into standalone server</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="POOLCREATE_DESTROYING" xml:space="preserve">
2014-05-15 19:47:13 +02:00
<value>Making pool into standalone server</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="POOLCREATE_REMOVED" xml:space="preserve">
<value>Removed from pool</value>
</data>
<data name="POOLCREATE_REMOVING" xml:space="preserve">
<value>Removing from pool</value>
</data>
<data name="POOLS" xml:space="preserve">
<value>Pools</value>
</data>
<data name="POOL_COLON" xml:space="preserve">
<value>Pool:</value>
</data>
<data name="POOL_EDIT_IN_PROGRESS" xml:space="preserve">
<value>The configuration for this pool is currently being modified</value>
</data>
<data name="POOL_FAILURES_TOLERATE" xml:space="preserve">
<value>{0} failures tolerated</value>
</data>
<data name="POOL_FAILURE_TOLERATE" xml:space="preserve">
<value>{0} failure tolerated</value>
</data>
2016-12-10 16:01:25 +01:00
<data name="POOL_FORBIDS_AUTOMATED_UPDATES" xml:space="preserve">
<value>Automated updates are not supported for this server.</value>
</data>
2016-09-09 16:45:38 +02:00
<data name="POOL_FORBIDS_AUTOMATIC_RESTARTS" xml:space="preserve">
2016-09-16 14:36:03 +02:00
<value>Post-update tasks cannot be carried out automatically for all the servers to be updated.</value>
2016-09-09 16:45:38 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="POOL_GENERAL_TAB_TITLE" xml:space="preserve">
<value>Pool General Properties</value>
</data>
<data name="POOL_GONE" xml:space="preserve">
<value>Pool has disappeared!</value>
</data>
2013-08-09 18:17:24 +02:00
<data name="POOL_HAS_MIXED_LICENSES" xml:space="preserve">
<value>This pool has hosts with different types of license.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="POOL_HAS_NO_SHARED_STORAGE" xml:space="preserve">
<value>This pool has no shared storage</value>
</data>
<data name="POOL_IS_PARTIALLY_LICENSED" xml:space="preserve">
<value>The pool is partially licensed</value>
</data>
<data name="POOL_JOIN_FORBIDDEN_BY_HA" xml:space="preserve">
<value>HA is enabled on the pool</value>
</data>
<data name="POOL_JOIN_IMPOSSIBLE" xml:space="preserve">
<value>Pool join not possible</value>
</data>
2016-02-19 18:31:30 +01:00
<data name="POOL_JOIN_NOT_PHYSICAL_PIF" xml:space="preserve">
2016-03-04 14:46:06 +01:00
<value>This server must not have any bonds, VLANs or cross-server private networks</value>
2016-02-19 18:31:30 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="POOL_LICENSE" xml:space="preserve">
<value>Pool License</value>
</data>
<data name="POOL_MASTER" xml:space="preserve">
<value>Pool master</value>
</data>
<data name="POOL_NAME_EMPTY" xml:space="preserve">
<value>Pool name cannot be empty</value>
</data>
<data name="POOL_NETWORK_TAB_TITLE" xml:space="preserve">
<value>Pool Networks</value>
</data>
<data name="POOL_OR_HOST_IS_NOT_CONNECTED" xml:space="preserve">
<value>Pool or host is not connected</value>
</data>
<data name="POOL_PICKER_BLURB_NO_AFFINITY" xml:space="preserve">
<value>Select a pool or stand alone server to import this VM to. The home server setting will be taken from the template.\n\nIf this value does not correspond to a server within the selected resource pool then it will be ignored for all resourcing decisions.</value>
</data>
2013-12-13 18:35:40 +01:00
<data name="POOL_VERSIONS_LINK_TEXT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Pool partially upgraded to [XenServer] {0}</value>
2013-12-13 18:35:40 +01:00
</data>
<data name="POOL_VERSIONS_LINK_TEXT_SHORT" xml:space="preserve">
2013-12-19 13:41:07 +01:00
<value>Partially upgraded</value>
2013-12-13 18:35:40 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="POOL_X" xml:space="preserve">
<value>pool '{0}'</value>
</data>
<data name="POOL_X_READYUPGRADE" xml:space="preserve">
<value> Pool {0}</value>
</data>
<data name="POWER_ON" xml:space="preserve">
<value>Power On</value>
</data>
<data name="POWER_ON_REQUEST_FAILED" xml:space="preserve">
<value>Power on request to {0} failed. Check the network connectivity.</value>
</data>
<data name="POWER_STATE" xml:space="preserve">
<value>Power state</value>
</data>
2014-07-25 09:35:18 +02:00
<data name="POWER_USAGE" xml:space="preserve">
<value>Power usage (W)</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="PRIVACY_WARNING" xml:space="preserve">
<value>Privacy Warning</value>
</data>
<data name="PROBED_HBA" xml:space="preserve">
<value>Probing for LUNs finished</value>
</data>
<data name="PROBING_HBA" xml:space="preserve">
<value>Probing for LUNs...</value>
</data>
<data name="PROBING_HBA_TITLE" xml:space="preserve">
<value>Probing for LUNs on {0}</value>
</data>
<data name="PROBLEM_HOSTPROBLEM_TITLE" xml:space="preserve">
<value>Server '{0}'</value>
</data>
<data name="PROBLEM_MAC_ADDRESS_IS_DUPLICATE" xml:space="preserve">
<value>The MAC address entered has already been assigned to the VM: \n {1} \n\n Are you sure you wish to continue?</value>
</data>
<data name="PROBLEM_MAC_ADDRESS_IS_DUPLICATE_TITLE" xml:space="preserve">
<value>Duplicate MAC address</value>
</data>
<data name="PROBLEM_POOLPROBLEM_TITLE" xml:space="preserve">
<value>Pool '{0}'</value>
</data>
<data name="PROBLEM_SRPROBLEM_TITLE" xml:space="preserve">
<value>SR '{0}'</value>
</data>
<data name="PROBLEM_STORAGELINK_CONNECTION_FAILED" xml:space="preserve">
<value>An error has occurred while attempting to connect to Storage Link Gateway: \n\n{0}\n\nPlease review the settings for this host and reconnect.</value>
</data>
2014-05-21 14:47:51 +02:00
<data name="PROBLEM_UNSUPPORTED_STORAGELINK_SR" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>The use of StorageLink SRs was removed in [XenServer]. Remove StorageLink SRs before upgrading.</value>
2014-05-21 14:47:51 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="PROBLEM_VMAPPLIANCEPROBLEM_TITLE" xml:space="preserve">
<value>vApp {0}</value>
</data>
<data name="PROBLEM_VMPROBLEM_TITLE" xml:space="preserve">
<value>VM '{0}'</value>
</data>
<data name="PROCEED" xml:space="preserve">
<value>&Proceed</value>
</data>
<data name="PROMPT_XS_CD" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Please insert the [XenServer] CD into the physical drive on server '{0}'.
2013-06-24 13:41:48 +02:00
Press OK to continue the wizard and return to the server and follow the instructions on screen.</value>
</data>
<data name="PROPERTIES_DIALOG_TITLE" xml:space="preserve">
<value>'{0}' Properties</value>
</data>
<data name="PROPERTY_ON_OBJECT" xml:space="preserve">
<value>{0} on '{1}'</value>
</data>
<data name="PROTECTED_VMS" xml:space="preserve">
<value>Protected VMs</value>
</data>
<data name="PROTECTED_VMS_TITLE" xml:space="preserve">
<value>Select the VMs that you want to protect with this policy</value>
</data>
<data name="PROVISIONING_OPTIONS" xml:space="preserve">
<value>Provisioning Options</value>
</data>
<data name="PROVISIONING_TYPE" xml:space="preserve">
<value>Provisioning Type</value>
</data>
<data name="PROVISIONING_VM" xml:space="preserve">
<value>Provisioning VM</value>
</data>
<data name="PROXY_SERVERS_NOT_SUPPORTED" xml:space="preserve">
<value>Proxy servers are not supported.</value>
</data>
2016-09-26 18:44:17 +02:00
<data name="PVS_CACHE_CONFIG_DIALOG_TITLE" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>PVS-Accelerator configuration - '{0}'</value>
2016-09-26 18:44:17 +02:00
</data>
2016-11-11 16:00:04 +01:00
<data name="PVS_CACHE_INCOMPLETE_CONFIGURATION" xml:space="preserve">
2016-11-11 16:15:49 +01:00
<value>{0} (Incomplete PVS configuration)</value>
2016-11-11 16:00:04 +01:00
</data>
2016-07-13 14:36:49 +02:00
<data name="PVS_CACHE_MEMORY_AND_DISK" xml:space="preserve">
<value>Memory and disk</value>
</data>
<data name="PVS_CACHE_MEMORY_ONLY" xml:space="preserve">
<value>Memory only</value>
</data>
2016-11-16 13:35:09 +01:00
<data name="PVS_CACHE_MEMORY_ONLY_DISABLED" xml:space="preserve">
<value>Memory only (Not enough Control Domain memory)</value>
</data>
2016-09-26 18:44:17 +02:00
<data name="PVS_CACHE_MEMORY_SR_NAME" xml:space="preserve">
<value>MemorySR</value>
</data>
<data name="PVS_CACHE_NOT_CONFIGURED" xml:space="preserve">
<value>Not configured</value>
</data>
2016-12-07 18:45:50 +01:00
<data name="PVS_CACHE_STORAGE_CANNOT_BE_CHANGED" xml:space="preserve">
<value>This PVS cache storage cannot be changed because it is in use.</value>
</data>
2016-11-11 15:04:16 +01:00
<data name="PVS_CACHE_STORAGE_NOT_CONFIGURED" xml:space="preserve">
2016-11-11 16:15:49 +01:00
<value>{0} (Incomplete Cache Storage configuration)</value>
2016-09-26 18:44:17 +02:00
</data>
2016-10-11 14:13:50 +02:00
<data name="PVS_SITE_CANNOT_BE_REMOVED" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>This cache configuration cannot be removed because there are VMs that are streamed from this site.</value>
2016-10-11 14:13:50 +02:00
</data>
2016-08-09 13:01:59 +02:00
<data name="PVS_SITE_DIALOG_TITLE" xml:space="preserve">
2016-10-01 01:23:28 +02:00
<value>PVS Servers on site {0}'</value>
2016-07-26 16:19:18 +02:00
</data>
2016-09-26 18:44:17 +02:00
<data name="PVS_SITE_NAME" xml:space="preserve">
<value>PVS Site</value>
</data>
2016-07-13 14:36:49 +02:00
<data name="PVS_TAB_TITLE" xml:space="preserve">
2017-01-04 14:02:59 +01:00
<value>PVS-Accelerator</value>
2016-07-13 14:36:49 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="PV_DRIVERS_NOT_INSTALLED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] Tools not installed</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PV_DRIVERS_OUT_OF_DATE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] Tools out of date (version {0} installed)</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="PV_DRIVERS_OUT_OF_DATE_UNKNOWN_VERSION" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] Tools out of date</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="QOS_LIMIT_INVALID" xml:space="preserve">
<value>QoS limit must be between 1 and 2147483647 (or left empty).</value>
</data>
<data name="QUERY_DATA_AVG_MAX" xml:space="preserve">
<value>{0}/{1}</value>
</data>
<data name="QUERY_MEMORY_PERCENT" xml:space="preserve">
<value>{0}% of {1}</value>
</data>
<data name="QUERY_MEMORY_USAGE" xml:space="preserve">
<value>{0} of {1}</value>
</data>
<data name="QUERY_PERCENT_OF_CPU" xml:space="preserve">
<value>{0}% of 1 CPU</value>
</data>
<data name="QUERY_PERCENT_OF_CPUS" xml:space="preserve">
<value>{0}% of {1} CPUs</value>
</data>
<data name="QUESTION_LOGOUT_AD_USER_MANY" xml:space="preserve">
<value>You are about to log out {0} users.
Do you wish to continue?</value>
</data>
<data name="QUESTION_LOGOUT_AD_USER_ONE" xml:space="preserve">
<value>You are about to log out the user '{0}'.
Do you wish to continue?</value>
</data>
<data name="QUESTION_MARK" xml:space="preserve">
<value>?</value>
</data>
<data name="QUESTION_REMOVE_AD_USER_MANY" xml:space="preserve">
<value>You are about to remove {0} users.
Do you wish to continue?</value>
</data>
<data name="QUESTION_REMOVE_AD_USER_ONE" xml:space="preserve">
<value>You are about to remove the user '{0}'.
Do you wish to continue?</value>
</data>
<data name="QUIESCED_SNAPSHOTS" xml:space="preserve">
<value>Quiesced snapshots</value>
</data>
<data name="RAID_TYPE" xml:space="preserve">
<value>RAID type</value>
</data>
<data name="RAID_TYPES" xml:space="preserve">
<value>RAID Types</value>
</data>
<data name="RBAC_CONSOLE_WARNING_MANY" xml:space="preserve">
<value>Your current role is '{0}'.
To access this console switch to an account with one of the following roles:
{1}</value>
</data>
<data name="RBAC_CONSOLE_WARNING_ONE" xml:space="preserve">
<value>Your current role is '{0}'.
To access this console switch to an account with the following role:
{1}</value>
</data>
<data name="RBAC_CROSS_POOL_MIGRATE_VM_BLOCKED" xml:space="preserve">
<value>Current access levels do not allow migration of VMs across pools. Log in as a different user with sufficient privileges on both source and target hosts and try again.</value>
</data>
<data name="RBAC_DR_WIZARD_MESSAGE" xml:space="preserve">
<value>User {0} does not have sufficient permissions to run a Disaster Recovery wizard. Login as a different user with sufficient privileges and try again.</value>
</data>
<data name="RBAC_HA_TAB_WARNING" xml:space="preserve">
<value>Your current role is '{1}'.
To configure HA settings, switch to an account with one of the following roles:
{0}</value>
</data>
<data name="RBAC_HTTP_FAILURE" xml:space="preserve">
<value>A {0} user cannot perform this action.</value>
</data>
<data name="RBAC_NO_WIZARD_LIMITS" xml:space="preserve">
<value>Check complete, you have full access to the features in this wizard.</value>
</data>
<data name="RBAC_UPDATES_WIZARD" xml:space="preserve">
<value>User {0} does not have sufficient permissions to apply software updates to {1}. Either log in with different user credentials or deselect this server before continuing.</value>
</data>
<data name="RBAC_UPGRADE_WIZARD_MESSAGE" xml:space="preserve">
<value>User {0} does not have sufficient permissions to perform a rolling pool upgrade on {1}.
You must reconnect to {1} using an account with Pool Administrator permissions before you can upgrade it using the Rolling Pool Upgrade wizard.</value>
</data>
<data name="RBAC_WARNING_EXPORT_WIZARD_APPLIANCE" xml:space="preserve">
<value>A {0} user cannot export appliances. Login as a different user with sufficient privileges and try again.</value>
</data>
<data name="RBAC_WARNING_EXPORT_WIZARD_XVA" xml:space="preserve">
<value>A {0} user cannot export VMs. Login as a different user with sufficient privileges and try again.</value>
</data>
<data name="RBAC_WARNING_IMPORT_WIZARD_AFFINITY" xml:space="preserve">
<value>A {0} user cannot alter the Home Server setting. The value will be taken from the template, and if it relates to a server outside the resource pool then it will be ignored.</value>
</data>
<data name="RBAC_WARNING_IMPORT_WIZARD_APPLIANCE" xml:space="preserve">
<value>A {0} user cannot import appliances. Login as a different user with sufficient privileges and try again.</value>
</data>
<data name="RBAC_WARNING_IMPORT_WIZARD_IMAGE" xml:space="preserve">
<value>A {0} user cannot import virtual disk images. Login as a different user with sufficient privileges and try again.</value>
</data>
<data name="RBAC_WARNING_IMPORT_WIZARD_XVA" xml:space="preserve">
<value>A {0} user cannot import VMs. Log in as a different user with sufficient privileges and try again.</value>
</data>
<data name="RBAC_WARNING_PAGE_DESCRIPTION_SR_ATTACH" xml:space="preserve">
<value>Before you can proceed through this wizard, role-based security checks are made to ensure that you have sufficient privileges to attach storage repositories and use all the features in this wizard.</value>
</data>
<data name="RBAC_WARNING_PAGE_DESCRIPTION_SR_CREATE" xml:space="preserve">
<value>Before you can proceed through this wizard, role-based security checks are made to ensure that you have sufficient privileges to create new storage repositories and use all the features in this wizard.</value>
</data>
<data name="RBAC_WARNING_PAGE_HEADER_ROW_DESC" xml:space="preserve">
<value>Checking permissions for {0} ({1}) in '{2}' ...</value>
</data>
<data name="RBAC_WARNING_PAGE_TEXT_TITLE" xml:space="preserve">
<value>Permission Checks</value>
</data>
<data name="RBAC_WARNING_SR_WIZARD_ATTACH" xml:space="preserve">
<value>A {0} user cannot attach SRs. Log in as a different user with sufficient privileges and try again.</value>
</data>
<data name="RBAC_WARNING_SR_WIZARD_CREATE" xml:space="preserve">
<value>A {0} user cannot create new SRs. Log in as a different user with sufficient privileges and try again.</value>
</data>
<data name="RBAC_WARNING_VMPP" xml:space="preserve">
<value>A {0} user cannot create VM protection policies. Log in as a different user with sufficient privileges and try again.</value>
</data>
2016-02-09 11:58:03 +01:00
<data name="RBAC_WARNING_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>A {0} user cannot create a snapshot schedule. Log in as a different user with sufficient privileges and try again.</value>
2016-02-09 11:58:03 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="RBAC_WARNING_VM_APPLIANCE" xml:space="preserve">
<value>A {0} user cannot create vApps. Log in as a different user with sufficient privileges and try again.</value>
</data>
<data name="RBAC_WARNING_VM_WIZARD_AFFINITY" xml:space="preserve">
<value>A {0} user cannot alter the Home Server setting. Your choice of storage may be limited by the Home Server defined in the Template you select</value>
</data>
<data name="RBAC_WARNING_VM_WIZARD_BLOCK" xml:space="preserve">
<value>A {0} user cannot create VMs. Log in as a different user with sufficient privileges and try again.</value>
</data>
2013-09-20 12:24:46 +02:00
<data name="RBAC_WARNING_VM_WIZARD_GPU" xml:space="preserve">
<value>A {0} user cannot assign a virtual GPU and will be restricted to the settings on the template.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="RBAC_WARNING_VM_WIZARD_MEM" xml:space="preserve">
2013-09-20 12:24:46 +02:00
<value>A {0} user cannot alter memory values and will be restricted to the settings on the template.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="READY_UPGRADE" xml:space="preserve">
<value>Ready to Upgrade</value>
</data>
<data name="READ_ONLY" xml:space="preserve">
<value>Read Only</value>
</data>
<data name="READ_ONLY_ON_PLURAL" xml:space="preserve">
<value>You cannot perform this action because you only have Read Only access on {0}.
Disconnect from these servers, or reconnect as a more privileged user.</value>
</data>
<data name="READ_ONLY_ON_SINGULAR" xml:space="preserve">
<value>You cannot perform this action because you only have Read Only access on {0}.
Disconnect from this server, or reconnect as a more privileged user.</value>
</data>
<data name="READ_WRITE" xml:space="preserve">
<value>Read / Write</value>
</data>
<data name="REATTACH_SR" xml:space="preserve">
<value>R&eattach</value>
</data>
<data name="REBOOT" xml:space="preserve">
<value>&Reboot Now</value>
</data>
<data name="REBOOT_AGAIN_BUTTON_LABEL" xml:space="preserve">
<value>&Reboot again</value>
</data>
<data name="REBOOT_WITH_SAME_VERSION" xml:space="preserve">
<value>Rebooted with the same version</value>
</data>
<data name="RECONNECT_AS_BLURB" xml:space="preserve">
<value>You are currently logged in to '{0}' as '{1}'.
To log out of this server and log in again using a different user account, enter the account credentials below and click OK.</value>
</data>
<data name="REGION_LABLE" xml:space="preserve">
<value>&Region:</value>
</data>
<data name="REMOTE" xml:space="preserve">
<value>Remote ({0})</value>
</data>
<data name="REMOTE_SRS" xml:space="preserve">
<value>Remote Storage Repositories</value>
</data>
<data name="REMOVE" xml:space="preserve">
<value>Remove</value>
</data>
<data name="REMOVED_FROM_FOLDER" xml:space="preserve">
<value>Removed from folder</value>
</data>
<data name="REMOVED_UPDATE" xml:space="preserve">
<value>Removed Update '{0}'</value>
</data>
<data name="REMOVED_VMS_FROM_APPLIANCE" xml:space="preserve">
<value>Removed from vApp </value>
</data>
<data name="REMOVED_VMS_FROM_POLICY" xml:space="preserve">
<value>Removed from VM Protection Policy</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="REMOVED_VMS_FROM_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Removed from snapshot schedule</value>
2016-01-27 11:36:48 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="REMOVE_CRASHDUMP_FILES" xml:space="preserve">
<value>Remove Crash Dump Files</value>
</data>
<data name="REMOVE_CRASHDUMP_QUESTION" xml:space="preserve">
<value>Would you like to remove crash dump files on the selected servers?</value>
</data>
<data name="REMOVE_CRASHDUMP_WARNING" xml:space="preserve">
<value>This will permanently remove all crash dump files from {0}. It is recommended you compile these files as part of a Server Status Report before you remove them.
Click Server Status Report to open the Compile Server Status Report Wizard or click Remove Files to remove the crash dump files without compiling.
</value>
</data>
<data name="REMOVE_FROM_FOLDER" xml:space="preserve">
<value>Remove from &folder</value>
</data>
<data name="REMOVE_GROUPING" xml:space="preserve">
<value>Remove Grouping</value>
</data>
<data name="REMOVE_PATCH" xml:space="preserve">
<value>Remove Update</value>
</data>
<data name="REMOVE_SERVER" xml:space="preserve">
<value>&Remove Server...</value>
</data>
<data name="REMOVE_SERVERS" xml:space="preserve">
<value>&Remove Servers...</value>
</data>
<data name="REMOVE_SERVER_FROM_POOL_CONTEXT_MENU_ITEM_TEXT" xml:space="preserve">
<value>Remove Server from &Pool</value>
</data>
<data name="REMOVE_SNAPSHOT" xml:space="preserve">
<value>Remove Snapshot</value>
</data>
<data name="REMOVE_SNAPSHOTS_TEXT" xml:space="preserve">
<value>Are you sure you want to delete the selected snapshots? This operation cannot be undone.</value>
</data>
<data name="REMOVE_SNAPSHOT_TEXT" xml:space="preserve">
<value>Are you sure you want to delete {0}? This operation cannot be undone.</value>
</data>
<data name="REMOVE_STORAGELINK_VOLUME_ACTION_FINSH" xml:space="preserve">
<value>Removed StorageLink Volume '{0}' from '{1}'</value>
</data>
<data name="REMOVE_STORAGELINK_VOLUME_ACTION_START" xml:space="preserve">
<value>Removing StorageLink Volume '{0}' from '{1}'</value>
</data>
<data name="REMOVE_STORAGELINK_VOLUME_ACTION_TITLE" xml:space="preserve">
<value>Remove StorageLink Volume '{0}' from '{1}'</value>
</data>
<data name="REMOVE_STORAGELINK_VOLUME_MESSAGEBOX_TEXT" xml:space="preserve">
<value>Are you sure you want to remove '{0}'?</value>
</data>
<data name="REMOVE_STORAGELINK_VOLUME_MESSAGEBOX_TITLE" xml:space="preserve">
<value>Remove StorageLink Volume</value>
</data>
<data name="REMOVE_STORAGE_SYSTEM" xml:space="preserve">
<value>R&emove Storage System</value>
</data>
<data name="REMOVE_STORAGE_SYSTEMS" xml:space="preserve">
<value>R&emove Storage Systems</value>
</data>
<data name="REMOVE_VIRTUAL_DISK" xml:space="preserve">
<value>Remove Virtual Disk</value>
</data>
<data name="REMOVE_VMS_FROM_APPLIANCE" xml:space="preserve">
<value>Remove VMs from vApp '{0}'</value>
</data>
<data name="REMOVE_VMS_FROM_POLICY" xml:space="preserve">
<value>Remove VMs from VM Protection Policy '{1}'</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="REMOVE_VMS_FROM_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Remove VMs from snapshot schedule '{1}'</value>
2016-01-27 11:36:48 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="REMOVE_VM_FROM_APPLIANCE" xml:space="preserve">
<value>Remove VM '{0}' from vApp '{1}'</value>
</data>
<data name="REMOVE_VM_FROM_POLICY" xml:space="preserve">
<value>Remove VM '{0}' from VM Protection Policy '{1}'</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="REMOVE_VM_FROM_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Remove VM '{0}' from snapshot schedule '{1}'</value>
2016-01-27 11:36:48 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="REMOVING_FROM_FOLDER" xml:space="preserve">
<value>Removing from folder</value>
</data>
<data name="REMOVING_SERVERS_FROM_POOL" xml:space="preserve">
<value>Removing servers from pool</value>
</data>
<data name="REMOVING_SERVER_FROM_POOL" xml:space="preserve">
<value>Removing server '{0}' from pool '{1}'</value>
</data>
<data name="REMOVING_UPDATE" xml:space="preserve">
<value>Removing Update '{0}'...</value>
</data>
<data name="REMOVING_VMS_FROM_APPLIANCE" xml:space="preserve">
<value>Removing from vApp</value>
</data>
<data name="REMOVING_VMS_FROM_POLICY" xml:space="preserve">
<value>Removing from VM Protection Policy</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="REMOVING_VMS_FROM_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Removing from snapshot schedule</value>
2016-01-27 11:36:48 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="RENAMED" xml:space="preserve">
<value>Renamed</value>
</data>
<data name="RENAMED_BOND" xml:space="preserve">
<value>Private Network</value>
</data>
<data name="RENAMED_TAG" xml:space="preserve">
<value>Renamed tag '{0}'</value>
</data>
<data name="RENAME_FOLDER" xml:space="preserve">
<value>&Rename Folder...</value>
</data>
<data name="RENAME_TAG" xml:space="preserve">
<value>Rename tag '{0}'</value>
</data>
<data name="RENAMING" xml:space="preserve">
<value>Renaming...</value>
</data>
<data name="RENAMING_FOLDER" xml:space="preserve">
<value>Renaming folder '{0}' to '{1}'...</value>
</data>
<data name="RENAMING_TAG" xml:space="preserve">
<value>Renaming tag '{0}'</value>
</data>
<data name="REPAIRSR_SERVER" xml:space="preserve">
<value>Server</value>
</data>
<data name="REPAIR_SR" xml:space="preserve">
<value>Repair</value>
</data>
<data name="REPAIR_SR_DIALOG_CONNECTION_MISSING" xml:space="preserve">
<value>Connection Missing</value>
</data>
<data name="REPAIR_SR_DIALOG_TITLE_MULTIPLE" xml:space="preserve">
<value>Repair Storage Repositories</value>
</data>
<data name="REPAIR_SR_DIALOG_TITLE_SINGLE" xml:space="preserve">
<value>Repair Storage Repository - {0}</value>
</data>
<data name="REPAIR_SR_DIALOG_UNPLUGGED" xml:space="preserve">
<value>Unplugged</value>
</data>
<data name="REPAIR_SR_WARNING_MULTIPATHS_DOWN" xml:space="preserve">
<value>Multipaths are not fully functional</value>
</data>
<data name="REPEATED_KEY" xml:space="preserve">
<value>Repeated key</value>
</data>
<data name="REQUIRED_HOTFIX_ISNOT_INSTALLED" xml:space="preserve">
<value>{0}: The required hotfix is not installed</value>
</data>
<data name="RESOLVED_AS" xml:space="preserve">
<value>Resolved as {0}</value>
</data>
2016-08-08 15:37:47 +02:00
<data name="RESTORE_DISMISSED_UPDATES" xml:space="preserve">
<value>Restore dismissed updates</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="RESTORE_FROM_BACKUP_FINALIZE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Backup file loaded to server '{0}'. Refer to the "[XenServer product] Administrator's Guide" for instructions on how to complete the restore procedure.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="RESTORE_HOST" xml:space="preserve">
<value>Restore From Backup...</value>
</data>
2016-08-08 15:37:47 +02:00
<data name="RESTORING" xml:space="preserve">
<value>Restoring...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="RESTORING_HOST" xml:space="preserve">
<value>Restoring server '{0}'</value>
</data>
<data name="RESTRICTIONS" xml:space="preserve">
<value>Restrictions:</value>
</data>
<data name="RESUMED_SUSPENDED_VMS" xml:space="preserve">
<value>Resumed suspended VMs</value>
</data>
<data name="RESUME_ON" xml:space="preserve">
<value>Resume On</value>
</data>
<data name="RESUME_SUSPENDED_VMS" xml:space="preserve">
<value>Resume suspended VMs</value>
</data>
<data name="RESUMING_SUSPENDED_VMS" xml:space="preserve">
<value>Resuming suspended VMs</value>
</data>
<data name="RETAIL" xml:space="preserve">
<value>Retail</value>
</data>
<data name="RETRIEVING_WLB_CONFIGURATION" xml:space="preserve">
<value>Retrieving the WLB configuration.</value>
</data>
<data name="RETRIEVING_WLB_CONFIGURATION_FOR" xml:space="preserve">
<value>Retrieving the WLB configuration for pool '{0}.'</value>
</data>
<data name="RETRIEVING_WLB_DEFAULT_CONFIGURATION" xml:space="preserve">
<value>Retrieving WLB default configuration</value>
</data>
<data name="RETRY" xml:space="preserve">
<value>&Retry</value>
</data>
<data name="RETRY_BUTTON_LABEL" xml:space="preserve">
<value>&Retry</value>
</data>
<data name="REVERTED_WIZARD_CHANGES" xml:space="preserve">
<value>Reverted all changes done by this wizard</value>
</data>
<data name="REVERTING_POWER_STATE" xml:space="preserve">
<value>Reverting the power state of {0}</value>
</data>
<data name="REVERTING_RESOLVED_PRECHECKS" xml:space="preserve">
<value>Reverting resolved prechecks</value>
</data>
<data name="REVERTING_WIZARD_CHANGES" xml:space="preserve">
<value>Reverting all changes done by this wizard</value>
</data>
<data name="REVERT_POOL_STATE" xml:space="preserve">
<value> Revert pool state</value>
</data>
<data name="REVERT_PRECHECK_ACTIONS" xml:space="preserve">
<value>Revert precheck actions</value>
</data>
<data name="REVERT_WIZARD_CHANGES" xml:space="preserve">
<value>Revert all changes done by this wizard</value>
</data>
<data name="RIGHT_CTRL" xml:space="preserve">
<value>Right Ctrl</value>
</data>
<data name="ROLE" xml:space="preserve">
<value>Role</value>
</data>
<data name="ROLE_ON_CONNECTION" xml:space="preserve">
<value>{0} on '{1}'</value>
</data>
<data name="ROLLINGUPGRADE_PRECHECKS" xml:space="preserve">
<value>Upgrade prechecks are performed on all the pools you selected to ensure that all the servers can be upgraded.</value>
</data>
<data name="ROLLING_POOL_UPGRADE" xml:space="preserve">
<value>Rolling Pool Upgrade</value>
</data>
2013-12-13 18:35:40 +01:00
<data name="ROLLING_POOL_UPGRADE_ELLIPSIS" xml:space="preserve">
2016-11-17 18:07:47 +01:00
<value>Rolling Pool &Upgrade...</value>
2013-12-13 18:35:40 +01:00
</data>
2013-07-23 20:57:51 +02:00
<data name="ROLLING_UPGRADE_CAN_RESUME_UPGRADE" xml:space="preserve">
<value>This upgrade can be resumed by launching the Rolling Pool Upgrade wizard again.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="ROLLING_UPGRADE_DISCONNECTED_SERVER" xml:space="preserve">
<value>No longer connected to {0}. Please review your selection and try again.</value>
</data>
<data name="ROLLING_UPGRADE_METHOD_PAGE_TEXT" xml:space="preserve">
<value>Locate the network install files (Automatic Mode)</value>
</data>
<data name="ROLLING_UPGRADE_MODE_PAGE" xml:space="preserve">
<value>Choose the upgrade mode: Automatic or Manual</value>
</data>
<data name="ROLLING_UPGRADE_REBOOT_AGAIN_MESSAGE" xml:space="preserve">
<value>Upgrade failed. The server '{0}' has rebooted with the same version.
Check the boot order in the server and reboot again.</value>
</data>
<data name="ROLLING_UPGRADE_REBOOT_MESSAGE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>To install the [XenServer] upgrade on {0}, follow these steps:
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
1. Insert the [XenServer] installation CD-ROM in the server’ s CD/DVD drive or set up a PXE network boot.
2013-06-24 13:41:48 +02:00
2. Click the Reboot Now button below to reboot the server and begin the installation.
3. Go to the server’ s console and follow the on-screen instructions to install the upgrade.
2016-02-10 12:52:30 +01:00
To skip this server and continue to the next server in the pool, click Skip This Server. Note that running a pool with servers on different versions of [XenServer] is not supported, and so any servers that are not upgraded during this rolling pool upgrade should be upgraded as soon as possible afterwards.
2013-06-24 13:41:48 +02:00
The master must be upgraded first, so if you skip the master, the rolling pool upgrade will be canceled for this pool.
</value>
</data>
<data name="ROLLING_UPGRADE_TIMEOUT" xml:space="preserve">
<value>Still waiting for the upgrade to complete.\n\nThere maybe a problem check the server console.\n\nClick Keep Waiting if the upgrade is still running or Cancel if there was an error.</value>
</data>
<data name="ROLLING_UPGRADE_TITLE_MODE" xml:space="preserve">
<value>Upgrade Mode</value>
</data>
<data name="ROLLING_UPGRADE_UPGRADE_COMPLETED" xml:space="preserve">
<value>Rolling pool upgrade is complete.</value>
</data>
<data name="ROLLING_UPGRADE_UPGRADE_NOT_COMPLETED" xml:space="preserve">
<value>Rolling pool upgrade did not complete.</value>
</data>
<data name="RPU_WARNING_DESCRIPTION_CLEARWATER_OR_GREATER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>'{0}': New versions of [XenServer] require new licenses to be added to your license server.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="RPU_WIZARD_TAMPA_AND_OLDER_TITLE" xml:space="preserve">
<value>Checking licensing status</value>
</data>
<data name="RPU_WIZARD_VMPR_VMPP_DEPRECATION" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>'{0}': VM Protection Policies were removed in [XenServer] [BRANDING_VERSION_6_2]</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="RPU_WIZARD_WSS_DEPRECATED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>'{0}': The use of WSS servers was removed in [XenServer] [BRANDING_VERSION_6_2]</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="RUNNING_ARCHIVE" xml:space="preserve">
<value>Archiving</value>
</data>
2014-07-25 09:35:18 +02:00
<data name="RUNNING_ON" xml:space="preserve">
<value>Running on</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="RUNNING_SNAPSHOTS" xml:space="preserve">
<value>Taking snapshots</value>
</data>
<data name="RUN_POLICY" xml:space="preserve">
<value>Running policy '{0}'</value>
</data>
<data name="RUN_POLICY_STARTED" xml:space="preserve">
2016-01-29 12:34:44 +01:00
<value>Policy started</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="RUN_PRECHECKS_WITH_ACCESS_KEY" xml:space="preserve">
<value>&Run Prechecks</value>
</data>
2014-07-16 09:06:23 +02:00
<data name="RUN_REPORT" xml:space="preserve">
<value>&Run Report</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SATURDAY_LONG" xml:space="preserve">
<value>Saturday</value>
</data>
<data name="SATURDAY_SHORT" xml:space="preserve">
<value>Sat</value>
</data>
<data name="SAVE" xml:space="preserve">
<value>Save</value>
</data>
<data name="SAVECHANGES_LOCKED" xml:space="preserve">
<value>Instance is already locked</value>
</data>
<data name="SAVE_AND_RESTORE" xml:space="preserve">
<value>Save and Restore</value>
</data>
<data name="SAVE_AND_RESTORE_DESC" xml:space="preserve">
<value>Save and restore server connection state on startup</value>
</data>
<data name="SAVE_AS_TEMPLATE" xml:space="preserve">
<value>Save as a Template</value>
</data>
<data name="SAVE_CHANGES_FOR_POLICY" xml:space="preserve">
<value>Do you want to save the changes for policy '{0}'?</value>
</data>
<data name="SAVE_SEARCH" xml:space="preserve">
<value>Save Search '{0}'</value>
</data>
<data name="SAVING_FILE_X" xml:space="preserve">
<value>Saving file {0}</value>
</data>
<data name="SAVING_METADATA" xml:space="preserve">
<value>Saving metadata...</value>
</data>
<data name="SAVING_SEARCH" xml:space="preserve">
<value>Saving search '{0}'...</value>
</data>
<data name="SAVING_VMS_ACTION_DESC" xml:space="preserve">
<value>Saving configuration...</value>
</data>
<data name="SAVING_VMS_ACTION_TITLE" xml:space="preserve">
<value>Saving VM Configuration</value>
</data>
<data name="SAVING_WLB_CONFIGURATION" xml:space="preserve">
<value>Saving Workload Balancing configuration.</value>
</data>
<data name="SAVING_WLB_CONFIGURATION_FOR" xml:space="preserve">
<value>Saving Workload Balancing configuration for '{0}'.</value>
</data>
<data name="SCANNING_ADAPTERS" xml:space="preserve">
<value>Scanning adapters</value>
</data>
<data name="SCANNING_VMS" xml:space="preserve">
<value>Scanning VMs...</value>
</data>
<data name="SCAN_IN_PROGRESS_TOOLTIP" xml:space="preserve">
<value>This SR already has a scan in progress</value>
</data>
<data name="SEARCHBOX_TOOLTIP" xml:space="preserve">
<value>Find resources in the Resources Pane</value>
</data>
<data name="SEARCH_ELLIPSIS" xml:space="preserve">
<value>Search...</value>
</data>
<data name="SEARCH_TEXT_BOX_INITIAL_TEXT" xml:space="preserve">
<value>Search...</value>
</data>
<data name="SEARCH_TITLE_HOST" xml:space="preserve">
2014-09-19 14:47:04 +02:00
<value>{0}: Overview</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SEARCH_TITLE_OVERVIEW" xml:space="preserve">
2013-08-01 13:49:11 +02:00
<value>All Servers, VMs, Custom Templates & Remote SRs</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SEARCH_TITLE_POOL" xml:space="preserve">
2014-09-19 14:47:04 +02:00
<value>{0}: Overview</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SECRET_ACCESS_KEY_LABLE" xml:space="preserve">
<value>&Secret access key:</value>
</data>
<data name="SECURITY" xml:space="preserve">
<value>Security</value>
</data>
2015-08-19 09:53:15 +02:00
<data name="SECURITYEDITPAGE_RUBRIC_HOST" xml:space="preserve">
<value>Select the security protocols that can be used for communicating with this server.</value>
</data>
<data name="SECURITYEDITPAGE_SUBTEXT_SSL" xml:space="preserve">
2016-04-21 10:37:13 +02:00
<value>Backwards compatibility</value>
2015-08-19 09:53:15 +02:00
</data>
<data name="SECURITYEDITPAGE_SUBTEXT_TLS" xml:space="preserve">
<value>TLS 1.2 only</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SECURITY_CHECKS" xml:space="preserve">
<value>Security Checks</value>
</data>
<data name="SECURITY_DESC" xml:space="preserve">
<value>SSL certificate options</value>
</data>
<data name="SECURITY_GROUPS" xml:space="preserve">
<value>Security Groups</value>
</data>
<data name="SELECTED_HOST_POOL_NOT_CONNECTED" xml:space="preserve">
<value>The hosts or pools selected are not connected</value>
</data>
2014-10-28 17:42:27 +01:00
<data name="SELECTION_CANNOT_BE_MIXED_FOR_LICENSING" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Different versions of [XenServer] must be licensed separately</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SELECT_A_FILTER" xml:space="preserve">
<value>Select a filter...</value>
</data>
<data name="SELECT_DEFAULT_SR" xml:space="preserve">
<value>Select Default SR</value>
</data>
<data name="SELECT_NETWORK_TOOLTIP" xml:space="preserve">
<value>There are no networks available for this network interface</value>
</data>
<data name="SELECT_POOL" xml:space="preserve">
<value>Select Pools</value>
</data>
<data name="SELECT_STORAGE_DROPDOWN_ERROR_NOT_ENOUGH_SPACE" xml:space="preserve">
<value>{0} - not enough available space on the SR</value>
</data>
2013-10-10 13:22:58 +02:00
<data name="SELECT_TARGET_IQN" xml:space="preserve">
<value>Select target IQN</value>
</data>
<data name="SELECT_TARGET_LUN" xml:space="preserve">
<value>Select target LUN</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SELECT_VMS_TO_SUSPEND_DLOG_TITLE" xml:space="preserve">
<value>Select VMs to Suspend - server '{0}'</value>
</data>
<data name="SERVER" xml:space="preserve">
<value>Server</value>
</data>
<data name="SERVERS" xml:space="preserve">
<value>Servers</value>
</data>
<data name="SERVERS_AND_VMS" xml:space="preserve">
<value>Servers and VMs</value>
</data>
<data name="SERVERS_AND_VMS_AND_CUSTOM_TEMPLATES_AND_ALL_SRS" xml:space="preserve">
<value>Servers, VMs, Custom Templates and all SRs</value>
</data>
<data name="SERVERS_AND_VMS_AND_CUSTOM_TEMPLATES_AND_REMOTE_SRS" xml:space="preserve">
<value>Servers, VMs, Custom Templates and Remote SRs</value>
</data>
<data name="SERVER_API_INCOMPATIBLE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>This server is using an API that is incompatible with [XenCenter].</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SERVER_COLON" xml:space="preserve">
<value>Server:</value>
</data>
<data name="SERVER_FAILURE" xml:space="preserve">
<value>Server failure: {0}</value>
</data>
<data name="SERVER_LABLE" xml:space="preserve">
<value>&Server:</value>
</data>
<data name="SERVER_OUT_OF_DATE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] Out of Date</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SERVER_OUT_OF_DATE_DETAIL" xml:space="preserve">
<value>Server '{0}' is out of date and can no longer be connected to.</value>
</data>
<data name="SERVER_REQUEST_IN_PROGRESS" xml:space="preserve">
<value>A server request is in progress</value>
</data>
2016-08-05 16:56:55 +02:00
<data name="SERVER_SIDE_CHECK_AUTO_MODE_DESCRIPTION" xml:space="preserve">
<value>Disk space check</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SERVER_SIDE_CHECK_DESCRIPTION" xml:space="preserve">
<value>Server side patch check</value>
</data>
<data name="SERVER_STATUS_REPORT" xml:space="preserve">
<value>Server Status Report</value>
</data>
<data name="SERVER_STATUS_REPORT_CAPABILITIES_FAILED" xml:space="preserve">
<value>The selected servers failed when asked for their capabilities. Please select different servers.</value>
</data>
<data name="SERVER_STATUS_REPORT_GET_CAPABILITIES" xml:space="preserve">
<value>Querying server capabilities...</value>
</data>
<data name="SERVER_TIME" xml:space="preserve">
<value>The current time on the pool master is: {0}</value>
</data>
2015-10-28 19:12:31 +01:00
<data name="SERVER_TOO_OLD" xml:space="preserve">
2016-10-20 11:43:39 +02:00
<value>This version of [XenCenter] supports [XenServer] [BRANDING_VERSION_6_0] onwards.</value>
2015-10-28 19:12:31 +01:00
</data>
<data name="SERVER_TOO_OLD_SOLUTION" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Use an earlier version of [XenCenter] to manage this server.</value>
2015-10-28 19:12:31 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="SERVER_X" xml:space="preserve">
<value>server '{0}'</value>
</data>
<data name="SETTINGS" xml:space="preserve">
<value>Settings</value>
</data>
2015-08-19 09:53:15 +02:00
<data name="SETTING_SECURITY_SETTINGS" xml:space="preserve">
<value>Setting security settings</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SETTING_VM_PROPERTIES" xml:space="preserve">
<value>Setting VM properties</value>
</data>
<data name="SETTING_VM_STARTUP_OPTIONS" xml:space="preserve">
<value>Setting VM startup options</value>
</data>
<data name="SETTING_VM_STARTUP_OPTIONS_ON_X" xml:space="preserve">
<value>Setting VM startup options on {0}</value>
</data>
<data name="SET_BOND_HASHING_ALGORITHM_ACTION_END" xml:space="preserve">
<value>Bond load balancing changed</value>
</data>
<data name="SET_BOND_HASHING_ALGORITHM_ACTION_START" xml:space="preserve">
<value>Changing bond load balancing</value>
</data>
<data name="SET_BOND_HASHING_ALGORITHM_ACTION_TITLE" xml:space="preserve">
<value>Change bond load balancing</value>
</data>
<data name="SET_BOND_MODE_ACTION_END" xml:space="preserve">
<value>Bond mode changed</value>
</data>
<data name="SET_BOND_MODE_ACTION_START" xml:space="preserve">
<value>Changing bond mode</value>
</data>
<data name="SET_BOND_MODE_ACTION_TITLE" xml:space="preserve">
<value>Change bond mode</value>
</data>
2013-11-14 11:35:48 +01:00
<data name="SET_GPU_PLACEMENT_POLICY_ACTION_DESCRIPTION" xml:space="preserve">
<value>Setting GPU placement policy</value>
</data>
<data name="SET_GPU_PLACEMENT_POLICY_ACTION_DONE" xml:space="preserve">
<value>GPU placement policy set</value>
</data>
<data name="SET_GPU_PLACEMENT_POLICY_ACTION_TITLE" xml:space="preserve">
<value>Set GPU placement policy</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SET_MTU_ON_CHINS_UNDER_NETWORK" xml:space="preserve">
<value>It is highly recommended you confirm this setting matches the MTU on related network '{0}'</value>
</data>
<data name="SET_STORAGELINK_CREDS_ACTION_DESCRIPTION" xml:space="preserve">
<value>Setting StorageLink Credentials</value>
</data>
<data name="SET_STORAGELINK_CREDS_ACTION_TITLE" xml:space="preserve">
<value>Set StorageLink Credentials</value>
</data>
<data name="SET_STORAGELINK_CREDS_TO_POOL_ACTION_DESCRIPTION" xml:space="preserve">
<value>Setting StorageLink Credentials to '{0}'</value>
</data>
<data name="SET_STORAGELINK_CREDS_TO_POOL_ACTION_TITLE" xml:space="preserve">
<value>Set StorageLink Credentials to '{0}'</value>
</data>
<data name="SEVERITY" xml:space="preserve">
<value>Severity</value>
</data>
2013-07-03 14:00:24 +02:00
<data name="SEVERITY_FILTER_0" xml:space="preserve">
2013-07-11 18:47:06 +02:00
<value>&Unknown</value>
2013-07-03 14:00:24 +02:00
</data>
2014-01-06 16:48:14 +01:00
<data name="SEVERITY_FILTER_0_DETAIL" xml:space="preserve">
<value>Unknown severity</value>
</data>
2013-07-03 14:00:24 +02:00
<data name="SEVERITY_FILTER_1" xml:space="preserve">
2013-07-11 18:47:06 +02:00
<value>&Critical</value>
2013-07-03 14:00:24 +02:00
</data>
2014-01-06 16:48:14 +01:00
<data name="SEVERITY_FILTER_1_DETAIL" xml:space="preserve">
<value>Data loss imminent</value>
</data>
2013-07-03 14:00:24 +02:00
<data name="SEVERITY_FILTER_2" xml:space="preserve">
2013-07-11 18:47:06 +02:00
<value>&Major</value>
2013-07-03 14:00:24 +02:00
</data>
2014-01-06 16:48:14 +01:00
<data name="SEVERITY_FILTER_2_DETAIL" xml:space="preserve">
<value>Service loss imminent</value>
</data>
2013-07-03 14:00:24 +02:00
<data name="SEVERITY_FILTER_3" xml:space="preserve">
2013-07-11 18:47:06 +02:00
<value>&Warning</value>
2013-07-03 14:00:24 +02:00
</data>
2014-01-06 16:48:14 +01:00
<data name="SEVERITY_FILTER_3_DETAIL" xml:space="preserve">
<value>Service degraded</value>
</data>
2013-07-03 14:00:24 +02:00
<data name="SEVERITY_FILTER_4" xml:space="preserve">
2013-07-11 18:47:06 +02:00
<value>Mi&nor</value>
2013-07-03 14:00:24 +02:00
</data>
2014-01-06 16:48:14 +01:00
<data name="SEVERITY_FILTER_4_DETAIL" xml:space="preserve">
<value>Service recovered</value>
</data>
2013-07-03 14:00:24 +02:00
<data name="SEVERITY_FILTER_5" xml:space="preserve">
2013-07-11 18:47:06 +02:00
<value>&Information</value>
2013-07-03 14:00:24 +02:00
</data>
2014-01-06 16:48:14 +01:00
<data name="SEVERITY_FILTER_5_DETAIL" xml:space="preserve">
<value>Informational</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SHADOW_MEMORY_MULTIPLIER" xml:space="preserve">
<value>Shadow memory multiplier: {0}</value>
</data>
<data name="SHADOW_MEMORY_MULTIPLIER_VALUE" xml:space="preserve">
2014-06-25 13:18:24 +02:00
<value>Value should be a number greater than or equal to 1.0</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SHARED" xml:space="preserve">
<value>Shared</value>
</data>
<data name="SHARE_SR" xml:space="preserve">
<value>&Share</value>
</data>
<data name="SHOW_DETAILS" xml:space="preserve">
<value>Show Details</value>
</data>
<data name="SHOW_RUN_HISTORY" xml:space="preserve">
<value>Show Run History</value>
</data>
<data name="SHUTDOWN" xml:space="preserve">
<value>Shut down</value>
</data>
<data name="SHUTDOWN_BEFORE_EXPORT" xml:space="preserve">
<value>You need to shut down or suspend the VM before exporting it.</value>
</data>
<data name="SHUTDOWN_VM" xml:space="preserve">
<value>Shut down VM</value>
</data>
<data name="SHUTTING_DOWN_SPECIFIED_VMS" xml:space="preserve">
<value>Shutting down specified VMs</value>
</data>
<data name="SHUTTING_DOWN_VM_OUT_OF" xml:space="preserve">
<value>Shutting down VM {0} out of {1}</value>
</data>
<data name="SIGNING_APPLIANCE" xml:space="preserve">
<value>Applying digital signature to appliance...</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="SINGLE_SERVER_PRIVATE_NETWORK" xml:space="preserve">
<value>Single-server private network</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SIZE" xml:space="preserve">
<value>Size</value>
</data>
<data name="SIZE_AND_LOCATION" xml:space="preserve">
<value>Size and Location</value>
</data>
<data name="SIZE_IS" xml:space="preserve">
<value>size is</value>
</data>
<data name="SIZE_LOCATION_SUB" xml:space="preserve">
<value>{0}, {1}</value>
</data>
<data name="SIZE_NEGLIGIBLE" xml:space="preserve">
<value>Negligible</value>
</data>
<data name="SKIP_SERVER" xml:space="preserve">
<value>&Skip This Server</value>
</data>
<data name="SLACK_LABEL" xml:space="preserve">
<value>Slack:</value>
</data>
<data name="SLAVE_ALREADY_CONNECTED" xml:space="preserve">
<value>Server '{0}' is a member of pool '{1}' and is already connected.</value>
</data>
<data name="SLAVE_CONNECTION_ERROR" xml:space="preserve">
<value>Server '{0}' is in a pool. To connect to a pool, you must connect to the pool master.
Do you want to connect to the pool master '{1}'?</value>
</data>
<data name="SMALLER_THAN" xml:space="preserve">
<value>smaller than</value>
</data>
2016-12-09 16:27:22 +01:00
<data name="SMB_ISO_STORAGE_ALREADY_ATTACHED" xml:space="preserve">
2016-12-06 12:27:53 +01:00
<value>This SMB ISO storage is already attached to '{0}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SNAPSHOTS" xml:space="preserve">
<value>Snapshots</value>
</data>
<data name="SNAPSHOTS_DELETED" xml:space="preserve">
<value>Snapshots deleted.</value>
</data>
<data name="SNAPSHOTS_DELETING" xml:space="preserve">
<value>Deleting snapshots</value>
</data>
<data name="SNAPSHOTS_EMPTY" xml:space="preserve">
<value>There are currently no snapshots of this VM. To create a snapshot, click Take Snapshot.</value>
</data>
<data name="SNAPSHOTS_PAGE_TITLE" xml:space="preserve">
<value>Virtual Machine Snapshots</value>
</data>
<data name="SNAPSHOTS_SELECTED" xml:space="preserve">
<value>{0} snapshots selected</value>
</data>
<data name="SNAPSHOTTED" xml:space="preserve">
<value>Snapshot created</value>
</data>
<data name="SNAPSHOTTING" xml:space="preserve">
<value>Creating a snapshot...</value>
</data>
<data name="SNAPSHOT_BRACKETS" xml:space="preserve">
<value>{0} (snapshot)</value>
</data>
<data name="SNAPSHOT_CREATED_ON" xml:space="preserve">
<value>Created on {0}</value>
</data>
<data name="SNAPSHOT_DELETED" xml:space="preserve">
<value>Snapshot '{0}' deleted.</value>
</data>
<data name="SNAPSHOT_DELETING" xml:space="preserve">
<value>Deleting snapshots ...</value>
</data>
<data name="SNAPSHOT_FREQUENCY" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Snapshot schedule</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SNAPSHOT_FREQUENCY_TITLE" xml:space="preserve">
<value>When do you want snapshots to be taken?</value>
</data>
<data name="SNAPSHOT_GENERAL_TAB_TITLE" xml:space="preserve">
<value>Snapshot General Properties</value>
</data>
<data name="SNAPSHOT_OF" xml:space="preserve">
<value>Snapshot of</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="SNAPSHOT_OF_TITLE" xml:space="preserve">
<value>{0} (snapshot of '{1}' {2})</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SNAPSHOT_REVERT" xml:space="preserve">
<value>Snapshot revert</value>
</data>
<data name="SNAPSHOT_TAKEN_ON" xml:space="preserve">
<value>Taken on: {0}</value>
</data>
<data name="SNAPSHOT_TAKEN_ON_2" xml:space="preserve">
<value>Snapshot taken on {0}</value>
</data>
<data name="SNAPSHOT_TREE_VIEW" xml:space="preserve">
<value>Snapshot tree view</value>
</data>
<data name="SNAPSHOT_TYPE" xml:space="preserve">
<value>Snapshot Type</value>
</data>
<data name="SNAPSHOT_TYPE_TITLE" xml:space="preserve">
<value>What type of snapshot do you want to use for scheduled snapshots?</value>
</data>
<data name="SOFTWARE_VERSION_BUILD_NUMBER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] build number</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SOFTWARE_VERSION_DATE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] build date</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SOFTWARE_VERSION_PRODUCT_VERSION" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] version</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SOFTWARE_VERSION_XCP_BUILD_NUMBER" xml:space="preserve">
<value>XCP build number</value>
</data>
<data name="SOFTWARE_VERSION_XCP_DATE" xml:space="preserve">
<value>XCP build date</value>
</data>
<data name="SOFTWARE_VERSION_XCP_PLATFORM_VERSION" xml:space="preserve">
<value>XCP version</value>
</data>
<data name="SOLUTION_AUTHENTICATION" xml:space="preserve">
2016-12-16 19:36:35 +01:00
<value>Try again using a correct user name and password.</value>
2013-06-24 13:41:48 +02:00
</data>
2017-02-21 17:33:00 +01:00
<data name="SOLUTION_CHECK_PROXY" xml:space="preserve">
<value>Check that the proxy server on '{0}' is configured correctly and [XenCenter]'s connection settings are correct and try again.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SOLUTION_CHECK_XENSERVER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Check that [XenServer] is configured correctly on '{0}' and try again.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SOLUTION_HOST_STILL_BOOTING" xml:space="preserve">
<value>Please wait and then try again.</value>
</data>
<data name="SOLUTION_NOT_FOUND" xml:space="preserve">
<value>Enter a valid hostname or IP address and try again.</value>
</data>
<data name="SOLUTION_NO_PERMISSION" xml:space="preserve">
<value>Try again with a more privileged user account.</value>
</data>
<data name="SOLUTION_UNKNOWN" xml:space="preserve">
<value />
</data>
<data name="SOME_ERRORS_ENCOUNTERED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Some errors were encountered. See the [XenCenter] log for more information.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SPACED_HYPHEN" xml:space="preserve">
<value> - </value>
</data>
<data name="SPEED" xml:space="preserve">
<value>Speed</value>
</data>
<data name="SR" xml:space="preserve">
<value>Storage Repository</value>
</data>
<data name="SRPANEL_ACTIVE" xml:space="preserve">
<value>Active</value>
</data>
<data name="SRPICKER_DISK_FREE" xml:space="preserve">
<value>{0} free of {1}</value>
</data>
<data name="SRPICKER_ERROR_LOCAL_SR_MUST_BE_RESIDENT_HOSTS" xml:space="preserve">
<value>Local storage must belong to resident host</value>
</data>
<data name="SRPICKER_NETWORK_GONE" xml:space="preserve">
<value>VDI has disappeared...</value>
</data>
<data name="SRPICKER_SR_FULL" xml:space="preserve">
<value>This storage repository is full</value>
</data>
<data name="SRS_FORGOTTEN" xml:space="preserve">
<value>SRs forgotten</value>
</data>
<data name="SRWIZARD_CIFS_LIBRARY" xml:space="preserve">
2015-09-21 12:11:57 +02:00
<value>SMB ISO library</value>
2013-06-24 13:41:48 +02:00
</data>
2015-03-03 16:51:56 +01:00
<data name="SRWIZARD_CIFS_STORAGE" xml:space="preserve">
2015-09-21 12:11:57 +02:00
<value>SMB virtual storage</value>
2015-03-03 16:51:56 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="SRWIZARD_ISCSI_STORAGE" xml:space="preserve">
<value>iSCSI virtual disk storage</value>
</data>
<data name="SRWIZARD_NFS_LIBRARY" xml:space="preserve">
<value>NFS ISO library</value>
</data>
<data name="SRWIZARD_NFS_STORAGE" xml:space="preserve">
<value>NFS virtual disk storage</value>
</data>
<data name="SRWIZARD_STORAGE_NAME" xml:space="preserve">
<value>{0} virtual disk storage</value>
</data>
<data name="SR_ACTION_IN_PROGRESS" xml:space="preserve">
<value>There is currently an action in progress on this SR.</value>
</data>
<data name="SR_CANNOT_BE_DESTROYED_WITH_XC" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>This SR cannot be destroyed with [XenCenter].</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SR_CANNOT_BE_DETACHED_WITH_XC" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>This SR cannot be detached with [XenCenter].</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SR_CANNOT_BE_FORGOTTEN_WITH_XC" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>This SR cannot be forgotten with [XenCenter].</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="SR_CANNOT_BE_SEEN" xml:space="preserve">
<value>This storage repository cannot be seen from {0}</value>
</data>
<data name="SR_COULD_NOT_BE_CONTACTED" xml:space="preserve">
<value>The SR could not be contacted.</value>
</data>
<data name="SR_DETACHED" xml:space="preserve">
<value>The SR is currently detached.</value>
</data>
2015-08-21 15:16:40 +02:00
<data name="SR_DISK_SPACE_ALLOCATION" xml:space="preserve">
<value>Initial allocation: {0}
Incremental allocation: {1}</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SR_DOES_NOT_NEED_UPGRADE" xml:space="preserve">
<value>This SR does not need to be upgraded.</value>
</data>
<data name="SR_FORGOTTEN_0" xml:space="preserve">
<value>SR {0} forgotten</value>
</data>
<data name="SR_GENERAL_TAB_TITLE" xml:space="preserve">
<value>Storage General Properties</value>
</data>
<data name="SR_HAS_RUNNING_VMS" xml:space="preserve">
<value>This SR contains running VMs.</value>
</data>
<data name="SR_IS_BROKEN" xml:space="preserve">
<value>This storage repository is broken</value>
</data>
<data name="SR_IS_LOCAL" xml:space="preserve">
2016-09-09 19:52:38 +02:00
<value>VMs without a home server cannot have disks on local storage</value>
2013-06-24 13:41:48 +02:00
</data>
2015-09-18 17:33:25 +02:00
<data name="SR_PICKER_DISK_TOO_BIG" xml:space="preserve">
<value>Disk size ({0}) exceeds SR size ({1})</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SR_PICKER_INSUFFICIENT_SPACE" xml:space="preserve">
<value>{0} required when only {1} available</value>
</data>
2015-09-07 18:45:57 +02:00
<data name="SR_QUANTUM_ALLOCATION_LIMITS_INFO" xml:space="preserve">
<value>The Incremental allocation limits are as follows:
The lower limit: SR size / {0} (no lower than {1})
The upper limit: SR size / {2}</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SR_REFRESH_ACTION_DESC" xml:space="preserve">
<value>Scanning SR</value>
</data>
<data name="SR_REFRESH_ACTION_TITLE" xml:space="preserve">
<value>Scanning SR '{0}'</value>
</data>
<data name="SR_SHARE_REVERTED" xml:space="preserve">
<value>Reverting {0} to unshared completed.</value>
</data>
<data name="SR_SHARE_REVERTING" xml:space="preserve">
<value>Unable to share {0}. Reverting to original state.</value>
</data>
<data name="SR_SHARE_REVERTING2" xml:space="preserve">
<value>Reverting {0} to unshared.</value>
</data>
<data name="SR_SHARE_SETTING" xml:space="preserve">
<value>Setting {0} as shared.</value>
</data>
<data name="SR_SIZE_USED" xml:space="preserve">
<value>{0} used of {1} total ({2} allocated)</value>
</data>
2015-07-20 21:40:28 +02:00
<data name="SR_THICK_PROVISIONING" xml:space="preserve">
2015-07-28 10:23:07 +02:00
<value>Fully provisioned</value>
2015-07-20 21:40:28 +02:00
</data>
<data name="SR_THIN_PROVISIONING" xml:space="preserve">
2015-07-28 10:23:07 +02:00
<value>Thinly provisioned</value>
2015-07-20 21:40:28 +02:00
</data>
2015-09-18 17:57:31 +02:00
<data name="SR_THIN_PROVISIONING_COMMITTED" xml:space="preserve">
<value>Thinly provisioned ({0}% committed)</value>
</data>
2015-03-27 14:23:25 +01:00
<data name="SR_TRIM_NO_STORAGE_HOST_ERROR" xml:space="preserve">
<value>Cannot reclaim freed space, because the SR is detached.</value>
</data>
2013-10-10 13:22:58 +02:00
<data name="SR_UNABLE_TO_CONNECT_TO_SCSI_TARGET" xml:space="preserve">
<value>Unable to connect to iSCSI target</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SR_X_ON_Y" xml:space="preserve">
<value>SR {0} on {1}</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="STANDARD_PERSOCKET_LICENSES_X_REQUIRED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] &Standard Per-Socket ({0} required)</value>
2015-01-23 11:41:54 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="STARTED" xml:space="preserve">
<value>Started</value>
</data>
<data name="STARTED_IN_RECOVERY_MODE" xml:space="preserve">
<value>Started VM in recovery mode</value>
</data>
<data name="STARTED_SHUTDOWN_VMS" xml:space="preserve">
<value>Started shut down VMs</value>
</data>
<data name="STARTING_IN_RECOVERY_MODE" xml:space="preserve">
<value>Starting VM in recovery mode</value>
</data>
<data name="STARTING_IN_RECOVERY_MODE_TITLE" xml:space="preserve">
<value>Starting VM {0} in recovery mode</value>
</data>
<data name="STARTING_SHUTDOWN_VMS" xml:space="preserve">
<value>Starting shut down VMs</value>
</data>
<data name="STARTING_VM" xml:space="preserve">
<value>Starting VM</value>
</data>
<data name="STARTING_VMS_MESSAGEBOX_TITLE" xml:space="preserve">
<value>Starting VMs</value>
</data>
<data name="STARTING_VM_MESSAGEBOX_TITLE" xml:space="preserve">
<value>Starting VM</value>
</data>
<data name="STARTS_WITH" xml:space="preserve">
<value>starts with</value>
</data>
<data name="START_HOST" xml:space="preserve">
<value>Start host</value>
</data>
<data name="START_IN_RECOVERY_MODE" xml:space="preserve">
<value>Start in Recovery Mode</value>
</data>
<data name="START_ON" xml:space="preserve">
<value>Start On</value>
</data>
<data name="START_SHUTDOWN_VMS" xml:space="preserve">
<value>Start shut down VMs</value>
</data>
<data name="START_TIME" xml:space="preserve">
<value>Start time</value>
</data>
<data name="START_UPGRADE" xml:space="preserve">
<value>Start &Upgrade</value>
</data>
<data name="START_UP_OPTIONS" xml:space="preserve">
<value>Start Options</value>
</data>
<data name="STATIC_MAX" xml:space="preserve">
<value>Static maximum</value>
</data>
<data name="STATIC_MAX_AMP" xml:space="preserve">
<value>&Static maximum</value>
</data>
<data name="STATIC_MAX_COLON" xml:space="preserve">
<value>&Static maximum:</value>
</data>
<data name="STATUS" xml:space="preserve">
<value>Status</value>
</data>
2013-08-13 18:08:04 +02:00
<data name="STATUS_FILTER_CANCEL" xml:space="preserve">
<value>Canceled</value>
</data>
2013-07-03 14:00:24 +02:00
<data name="STATUS_FILTER_COMPLETE" xml:space="preserve">
<value>Complete</value>
</data>
<data name="STATUS_FILTER_ERROR" xml:space="preserve">
2013-08-13 18:08:04 +02:00
<value>Error</value>
2013-07-03 14:00:24 +02:00
</data>
<data name="STATUS_FILTER_IN_PROGRESS" xml:space="preserve">
<value>In progress</value>
</data>
2017-02-09 16:16:11 +01:00
<data name="STATUS_REPORT_ENTER_CREDENTIALS_MESSAGE" xml:space="preserve">
<value>Enter your MyCitrix credentials (see {0}). These credentials will only be used to authenticate with [Citrix] Insight Services once and will not be stored on this machine or on your server.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="STATUS_REPORT_ZIP_FAILED" xml:space="preserve">
<value>There was an error while packaging the server status report. Only a partial report may be available</value>
</data>
CP-16922: Implement GUI for enabling PVS read caching (#1179)
* CP-16922: UI changes to PvsPage to replace the single configure button with a separate enable and disable one, per the design doc
* CP-16922: Intermediate checkin - command + dialog implemented, but PVS page has some layout problems.
* CP-16922: Implement GUI for enabling PVS read caching and marking/unmarking VMs for prepopulation
Fix the broken layout by reverting MainWindow.resx (which shouldn't have changed) back to the previous commit. Also removed duplicate properties button code.
* CP-16922: PVS Page changes, to properly display all VMs (not just ones with proxy), only populating proxy columns if there is a proxy set.
* CP-16922: Use a CommandButton for the enable button, connected to the same command as the VM main menu button, and using the table selection as its selection manager.
* CP-16922: Delete the old enable button click behaviour (because it now has a proper command), was causing the dialog to show up twice
* CP-16922: Properly list VMs by hiding those that should be hidden (in addition to non-VMs, also hide the __gui__ prefix and others covered by Show function). Also fixes a bug in NewVMGroupVMsPage discovered when fixing this - it would show VMs that should be hidden if you used the search bar.
* CP-16922: Use ButtonText on the Command to set the text on the PVS enable button
* CP-16922: Add the disable PVS read-caching command, and its associated proxy destroy action. Both based off enable equivalents (main difference is no dialog for now). Not used yet but will be in main window menu + disable button
* CP-16922: Add disable PVS read-caching to the main window menu (under enable), with the disable command attached to it
* CP-16922: Add support for disabling PVS read-caching for selected hosts via the PVS tab page by converting the disable button into a CommandButton in the same way as the enable button, using its own command + selection manager (because Selection Managers only bind to one control)
* CP-16922: Design - adding the "read caching enabled" column from the design, so that we display both whether caching is enabled and whether the VM is currently cached. If it's disabled all other values are missing.
* CP-16922: Add the PVS site column per the design to show the site a VM's PVS Proxy is on if it has a proxy
* CP-16922: Add an event handler for VMs changing so that newly provisioned VMs immediately show up in the PVS tab page
* CP-16922: Support for properly remembering the selection when the VM list is refreshed. A new method returns the list of VMs for the selected rows, and we can then check if the VM for the row being added is in this list. If there was no previous selection then we still select the first row by default.
* CP-16922: Remove prepopulate, which is being removed from the design. The next XAPI version will remove it, so just pass False as prepopulate for now, and remove the option from the dialog and PVS tab page.
* CP-16922: Improve UI appearance for a missing Storage Repository. Per the design, if there is no SR show the message None (memory only) instead of an empty cell
* CP-16922: Improved sorting behaviour. All columns (except VM name, which always uses it) use the VM tag as a sorting fallback (since they all have duplicates). New default sort which sorts by caching enabled first (yes before no), and then VM tag as a tiebreaker. Support for remembering the current sort on refresh, ie when a value changes.
* CP-16922: Refactoring to use a VM extension method to get the PVSProxy (or null if none exists) for a VM. This was used in the PVS Page + commands which are now much simpler.
* CP-16922: Move where the SelectionChanged event handler is set when refreshing the PVS table, so that the command buttons are updated correctly.
* CP-16922: Improvements to PVS read-caching dialog. Set accept/cancel buttons properly + adjust tab values, so focus acts as expected
* CP-16922: Remove the images from the menu for Enable/Disable PVS read-caching, most commands in the menu don't have one
* CP-16922: Sorting out the strings for the actions + ParallelAction calls, and moving them into the resx. Also reverting wrong MainWindow.resx changes.
* CAR-2184: XAPI changes. I've made the minimal possible changes to PvsPage to ensure it compiles, but it's had a lot of feature work (CP-16922) that supersedes this, these small changes should keep that merge painless.
* CAR-2184 XAPI: Reverse the unrelated changes, only keep the PVS ones.
* CP-16922: Merge latest XAPI changes, notably changes to Pvs_site.create
* CP-16922: Change tab show/hide logic for PVS tab, show it even if there are no PVS sites.
* CP-16922: Implement GUI for enabling PVS read caching
Design changes - remove the storage repo column and replace it with status, which is populated with a friendly version of the pvs_proxy_status enum. Also populate site list using site.name_label
Signed-off-by: Callum McIntyre <callumiandavid.mcintyre@citrix.com>
* CP-16922: Implement GUI for enabling PVS read caching
Adjusting the CanExecute of Enable PVS read-caching command to require at least one PVS site to be created. Since the PVS tab can show up without any sites, we need this because we can't create a proxy without a site.
* CP-16922: Code review changes.
Tidied up messages, and ensured actions run async properly, and without exiting before their task.
* CP-16922: Code review changes.
Update dialog resx, wider combobox on dialog, update action descriptions before setting RelatedTask, add friendly message body for PVS error notifications.
2016-09-22 16:08:15 +02:00
<data name="STOPPED" xml:space="preserve">
<value>Stopped</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="STORAGELINK_POOL_DISK_SPACE" xml:space="preserve">
<value>{0} free of {1}</value>
</data>
<data name="STORAGELINK_SR_NEEDS_REATTACH" xml:space="preserve">
<value>There is a StorageLink Gateway SR that needs to be reattached.</value>
</data>
2014-05-21 14:47:51 +02:00
<data name="STORAGELINK_UPGRADE_TEST" xml:space="preserve">
<value>StorageLink SR status</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="STORAGEPOOLS" xml:space="preserve">
<value>Storage Pools</value>
</data>
<data name="STORAGEVOLUMES" xml:space="preserve">
<value>Storage Volumes</value>
</data>
<data name="STORAGE_ADAPTER" xml:space="preserve">
<value>Storage Adapter</value>
</data>
<data name="STORAGE_BEST" xml:space="preserve">
<value>7 (Highest)</value>
</data>
<data name="STORAGE_DEVICE_POSITION" xml:space="preserve">
<value>Device Position</value>
</data>
<data name="STORAGE_DISK" xml:space="preserve">
<value>Disk </value>
</data>
<data name="STORAGE_IN_USE" xml:space="preserve">
<value>The SR '{0}' is in use on '{1}' and cannot be introduced. You must detach the SR from '{1}' before using it again.</value>
</data>
<data name="STORAGE_PANEL_DEVICE_PATH" xml:space="preserve">
<value>Device Path</value>
</data>
<data name="STORAGE_PANEL_UNKNOWN" xml:space="preserve">
<value><unknown></value>
</data>
<data name="STORAGE_POOL" xml:space="preserve">
<value>Storage Pool</value>
</data>
<data name="STORAGE_PRIORITY" xml:space="preserve">
<value>Priority</value>
</data>
2015-06-17 10:59:21 +02:00
<data name="STORAGE_PROVISIONING_METHOD_TITLE" xml:space="preserve">
<value>Choose storage provisioning method</value>
</data>
2015-06-18 16:03:25 +02:00
<data name="STORAGE_PROVISIONING_SETTINGS" xml:space="preserve">
<value>Storage Provisioning Settings</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="STORAGE_READ_ONLY" xml:space="preserve">
<value>Read Only</value>
</data>
<data name="STORAGE_REPOSITORY_X" xml:space="preserve">
<value>storage repository '{0}'</value>
</data>
<data name="STORAGE_SR" xml:space="preserve">
<value>Storage Repository</value>
</data>
<data name="STORAGE_SYSTEM" xml:space="preserve">
<value>Storage System</value>
</data>
<data name="STORAGE_TAB_TITLE" xml:space="preserve">
<value>Storage Repositories</value>
</data>
<data name="STORAGE_TYPE" xml:space="preserve">
<value>Type</value>
</data>
<data name="STORAGE_VOLUME" xml:space="preserve">
<value>Storage Volume</value>
</data>
<data name="STORAGE_WORST" xml:space="preserve">
<value>0 (Lowest)</value>
</data>
<data name="STRINGIFY_LIST_INNERSEP" xml:space="preserve">
<value>, </value>
</data>
<data name="STRINGIFY_LIST_LASTSEP" xml:space="preserve">
<value> and </value>
</data>
<data name="STRING_SPACE_STRING" xml:space="preserve">
<value>{0} {1}</value>
</data>
<data name="SUCCEEDED" xml:space="preserve">
<value>succeeded</value>
</data>
<data name="SUNDAY_LONG" xml:space="preserve">
<value>Sunday</value>
</data>
<data name="SUNDAY_SHORT" xml:space="preserve">
<value>Sun</value>
</data>
2015-01-28 14:17:58 +01:00
<data name="SUPP_PACK_DESCTIPTION" xml:space="preserve">
<value>{0} (version {1})</value>
</data>
2015-02-27 18:00:03 +01:00
<data name="SUPP_PACK_INSTALL_FAILED" xml:space="preserve">
<value>Failed to install supplemental pack '{0}' on '{1}'.</value>
</data>
<data name="SUPP_PACK_INSTALL_FAILED_MORE_INFO" xml:space="preserve">
<value>{0}
2016-11-11 18:24:57 +01:00
Refer to the "[XenServer product] Administrator's Guide" for instructions on how to manually install a supplemental pack on a server.</value>
2015-02-27 18:00:03 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="SUPP_PACK_MISSING_ON" xml:space="preserve">
<value>{0} (not installed on {1})</value>
</data>
2015-01-20 15:22:29 +01:00
<data name="SUPP_PACK_TEMP_VDI_DESCRIPTION" xml:space="preserve">
<value>Temporary virtual disk used for the installation of Supplemental Packs</value>
</data>
<data name="SUPP_PACK_UPLOADED" xml:space="preserve">
<value>File uploaded to '{0}'</value>
</data>
<data name="SUPP_PACK_UPLOADING" xml:space="preserve">
<value>Uploading file</value>
</data>
<data name="SUPP_PACK_UPLOADING_TO" xml:space="preserve">
<value>Uploading to '{0}'</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="SUPP_PACK_VERSIONS_DIFFER" xml:space="preserve">
<value>{0} (not the same version on all hosts)</value>
</data>
<data name="SUSPEND" xml:space="preserve">
<value>Suspend</value>
</data>
<data name="SUSPENDED_SPECIFIED_VMS" xml:space="preserve">
<value>Suspended specified VMs</value>
</data>
<data name="SUSPENDING_SPECIFIED_VMS" xml:space="preserve">
<value>Suspending specified VMs</value>
</data>
<data name="SUSPENDING_VM_OUT_OF" xml:space="preserve">
<value>Suspending VM {0} out of {1}</value>
</data>
<data name="SUSPEND_SHUTDOWN_VMS_ACTION_DESC" xml:space="preserve">
<value>Preparing to suspend and shut down VMs...</value>
</data>
<data name="SUSPEND_SPECIFIED_VMS" xml:space="preserve">
<value>Suspend specified VMs</value>
</data>
<data name="SUSPEND_VM" xml:space="preserve">
<value>Suspend VM</value>
</data>
<data name="SUSPEND_VMS" xml:space="preserve">
<value>Suspend VMs</value>
</data>
<data name="SWITCH_ROLE_DESC" xml:space="preserve">
<value>Switch to an account with the required role and try again.</value>
</data>
<data name="SYNCING_DATABASE" xml:space="preserve">
<value>Performing pool database sync</value>
</data>
<data name="TAGS" xml:space="preserve">
<value>Tags</value>
</data>
<data name="TAKE_SNAPSHOT" xml:space="preserve">
<value>&Take Snapshot</value>
</data>
<data name="TAKE_SNAPSHOT_ERROR" xml:space="preserve">
<value>Take snapshot is not currently allowed.</value>
</data>
<data name="TARGET" xml:space="preserve">
<value>Target</value>
</data>
2016-08-15 15:22:18 +02:00
<data name="TARGET_SERVER" xml:space="preserve">
<value>Target Server</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="TELL_ME_MORE" xml:space="preserve">
<value>Tell me more ...</value>
</data>
2014-07-25 09:35:18 +02:00
<data name="TEMPERATURE" xml:space="preserve">
<value>Temperature (°C)</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="TEMPLATE" xml:space="preserve">
<value>Template</value>
</data>
<data name="TEMPLATE_FROM_SNAPSHOT_DEFAULT_NAME" xml:space="preserve">
<value>Template from snapshot '{0}'</value>
</data>
<data name="TEMPLATE_GENERAL_TAB_TITLE" xml:space="preserve">
<value>Template General Properties</value>
</data>
<data name="TEMPLATE_INFO_DESCRIPTION" xml:space="preserve">
<value>Description: {0}</value>
</data>
<data name="TEMPLATE_INFO_DISK" xml:space="preserve">
<value>Disk {0}: Size = {1}, SR Type = {2}</value>
</data>
<data name="TEMPLATE_INFO_MEMORY" xml:space="preserve">
<value>Memory: {0}</value>
</data>
<data name="TEMPLATE_INFO_OS" xml:space="preserve">
<value>OS: {0}</value>
</data>
<data name="TEMPLATE_INFO_TOOLSNOTPRESENT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] Tools: Not present</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="TEMPLATE_INFO_TOOLSOLD" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] Tools: Out of date (version {0}.{1} installed)</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="TEMPLATE_INFO_TOOLSUPTODATE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] Tools: Up to date</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="TEMPLATE_INFO_VCPUS" xml:space="preserve">
2013-11-14 12:58:43 +01:00
<value>vCPUs: {0}</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="TEMPLATE_LINUX_PACK_NEEDED" xml:space="preserve">
<value>You must install the Linux pack to use this template</value>
</data>
<data name="TEMPLATE_NO_DESCRIPTION" xml:space="preserve">
<value><no description></value>
</data>
<data name="TERMINATING_SESSIONS" xml:space="preserve">
<value>Terminating sessions...</value>
</data>
<data name="TERMPLATE_INFO_VIF" xml:space="preserve">
<value>Interface {0}: Network = {1}</value>
</data>
<data name="TEST_ARCHIVE_LOCATION" xml:space="preserve">
<value>Test archive target location</value>
</data>
<data name="TEXT" xml:space="preserve">
<value>Text</value>
</data>
<data name="THE_SNAPSHOT" xml:space="preserve">
<value>the snapshot '{0}'</value>
</data>
2016-02-05 08:14:39 +01:00
<data name="THIS_VM_IS_IN_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>This VM is currently part of the snapshot schedule '{0}'</value>
2016-02-05 08:14:39 +01:00
</data>
<data name="THIS_VM_IS_NOT_IN_VMSS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>This VM is not currently part of a snapshot schedule</value>
2016-02-05 08:14:39 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="THIS_VM_IS_NOT_PROTECTED" xml:space="preserve">
<value>This VM is not currently protected with a VM protection policy</value>
</data>
<data name="THIS_VM_IS_PROTECTED" xml:space="preserve">
<value>This VM is currently protected with VM protection policy '{0}'</value>
</data>
<data name="THIS_WEEK" xml:space="preserve">
<value>is this week</value>
</data>
<data name="THURSDAY_LONG" xml:space="preserve">
<value>Thursday</value>
</data>
<data name="THURSDAY_SHORT" xml:space="preserve">
<value>Thu</value>
</data>
<data name="TIMESTAMP" xml:space="preserve">
<value>TimeStamp</value>
</data>
<data name="TIME_DAY" xml:space="preserve">
<value>{0} day</value>
</data>
<data name="TIME_DAYS" xml:space="preserve">
<value>{0} days</value>
</data>
<data name="TIME_HOUR" xml:space="preserve">
<value>{0} hour</value>
</data>
<data name="TIME_HOURS" xml:space="preserve">
<value>{0} hours</value>
</data>
<data name="TIME_MINUTE" xml:space="preserve">
<value>{0} minute</value>
</data>
<data name="TIME_MINUTES" xml:space="preserve">
<value>{0} minutes</value>
</data>
<data name="TIME_MONTHS" xml:space="preserve">
<value>{0} months</value>
</data>
<data name="TIME_NEGLIGIBLE" xml:space="preserve">
<value>Negligible</value>
</data>
<data name="TIME_RANGE_MINUTES" xml:space="preserve">
<value>{0} - {1} minutes</value>
</data>
<data name="TIME_RANGE_SECONDS" xml:space="preserve">
<value>{0} - {1} seconds</value>
</data>
<data name="TIME_SECONDS" xml:space="preserve">
<value>{0} seconds</value>
</data>
<data name="TITLE" xml:space="preserve">
<value>Title</value>
</data>
<data name="TODAY" xml:space="preserve">
<value>is today</value>
</data>
<data name="TOOLS_STATUS" xml:space="preserve">
<value>Virtualization</value>
</data>
<data name="TOOLTIP_ACTIVATE_VIF_SUSPENDED" xml:space="preserve">
<value>Networks cannot be activated while the VM is suspended</value>
</data>
<data name="TOOLTIP_ACTIVATE_VIF_TOOLS" xml:space="preserve">
<value>Networks cannot be activated on a running VM without tools installed</value>
</data>
<data name="TOOLTIP_DEACTIVATE_SUSPENDED" xml:space="preserve">
<value>Disks cannot be activated or deactivated while the VM is suspended</value>
</data>
<data name="TOOLTIP_DEACTIVATE_SYSVDI" xml:space="preserve">
<value>System disks cannot be activated or deactivated while the VM is running</value>
</data>
<data name="TOOLTIP_DEACTIVATE_VDI_NEED_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Disks cannot be activated or deactivated from running VMs without [XenServer product] Tools installed</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="TOOLTIP_DEACTIVATE_VIF_SUSPENDED" xml:space="preserve">
<value>Networks cannot be deactivated while the VM is suspended</value>
</data>
<data name="TOOLTIP_DEACTIVATE_VIF_TOOLS" xml:space="preserve">
<value>Networks cannot be deactivated on a running VM without tools installed</value>
</data>
<data name="TOOLTIP_DELETE_SUSPENDED" xml:space="preserve">
<value>Disks cannot be deleted while the VM is suspended</value>
</data>
<data name="TOOLTIP_DELETE_SYSVDI" xml:space="preserve">
<value>System disks cannot be deleted while the VM is running</value>
</data>
<data name="TOOLTIP_DELETE_VDI_NEED_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Disks cannot be deleted from running VMs without [XenServer product] Tools installed</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="TOOLTIP_DETACH_SUSPENDED" xml:space="preserve">
<value>Disks cannot be removed while the VM is suspended</value>
</data>
<data name="TOOLTIP_DETACH_SYSVDI" xml:space="preserve">
<value>System disks cannot be detached while the VM is running</value>
</data>
<data name="TOOLTIP_DETACH_VDI_MUST_DEACTIVATE" xml:space="preserve">
<value>Disks must be deactivated before detaching.</value>
</data>
<data name="TOOLTIP_DETACH_VDI_NEED_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Disks cannot be removed from running VMs without [XenServer product] Tools installed</value>
2013-06-24 13:41:48 +02:00
</data>
2015-09-14 17:21:44 +02:00
<data name="TOOLTIP_EDIT_NETWORK_IO_DRIVERS" xml:space="preserve">
<value>I/O drivers must be installed to edit a network on a running VM</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="TOOLTIP_EDIT_NETWORK_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] Tools must be installed to edit a network on a running VM</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="TOOLTIP_MAX_NETWORKS_FROM_DEFAULT_TEMPLATE" xml:space="preserve">
<value>Default templates support a maximum of {0} networks at VM creation</value>
</data>
<data name="TOOLTIP_MAX_NETWORKS_FROM_TEMPLATE" xml:space="preserve">
<value>The maximum number of networks for this template has been reached.</value>
</data>
<data name="TOOLTIP_NICS_PER_BOND_LIMIT" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] only supports {0} NICs per Bond.</value>
2013-06-24 13:41:48 +02:00
</data>
2015-09-14 17:21:44 +02:00
<data name="TOOLTIP_REMOVE_NETWORK_IO_DRIVERS" xml:space="preserve">
<value>I/O drivers must be installed to remove a network on a running VM</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="TOOLTIP_REMOVE_NETWORK_SUSPENDED" xml:space="preserve">
<value>Networks cannot be removed from suspended VMs</value>
</data>
<data name="TOOLTIP_REMOVE_NETWORK_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] Tools must be installed to remove a network on a running VM</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="TOOLTIP_REMOVE_PIF" xml:space="preserve">
<value>This network cannot be removed because it is a physical device</value>
</data>
2014-07-04 14:36:41 +02:00
<data name="TOOLTIP_SR_TRIM_UNSUPPORTED" xml:space="preserve">
<value>Reclaiming freed space not supported on this SR</value>
</data>
2014-07-16 15:24:49 +02:00
<data name="TOOLTIP_SR_TRIM_UNSUPPORTED_MULTIPLE" xml:space="preserve">
<value>Reclaiming freed space not supported on these SRs</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="TREESEARCHBOX_DROPDOWN_TOOLTIP" xml:space="preserve">
<value>Views and Saved Searches</value>
</data>
<data name="TRUE" xml:space="preserve">
<value>True</value>
</data>
<data name="TRUSTED" xml:space="preserve">
<value>trusted</value>
</data>
<data name="TUESDAY_LONG" xml:space="preserve">
<value>Tuesday</value>
</data>
<data name="TUESDAY_SHORT" xml:space="preserve">
<value>Tue</value>
</data>
<data name="TURN_HA_OFF" xml:space="preserve">
<value>Turn HA off</value>
</data>
2013-09-26 15:16:44 +02:00
<data name="TVM_PAGE_DESCRIPTION_EXPORT" xml:space="preserve">
<value>Select the network on which the temporary VM (Transfer VM) used to perform the export operation will run.</value>
</data>
<data name="TVM_PAGE_DESCRIPTION_IMPORT" xml:space="preserve">
<value>Select the network on which the temporary VM (Transfer VM) used to perform the import operation will run.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="TVM_PAGE_TEXT" xml:space="preserve">
<value>Transfer VM Settings</value>
</data>
<data name="TVM_PAGE_TITLE" xml:space="preserve">
<value>Configure networking options for the Transfer VM</value>
</data>
<data name="TYPE" xml:space="preserve">
<value>Type</value>
</data>
<data name="TYPES" xml:space="preserve">
<value>Types</value>
</data>
<data name="TYPE_PAGE_DESCRIPTION_HEADER_OVF" xml:space="preserve">
<value>Import an appliance from an OVF or OVA package.</value>
</data>
<data name="TYPE_PAGE_DESCRIPTION_HEADER_VHD" xml:space="preserve">
<value />
</data>
<data name="TYPE_PAGE_DESCRIPTION_HEADER_XVA" xml:space="preserve">
<value>Import a locally stored VM, template or snapshot as a new VM.</value>
</data>
<data name="UNABLE_TO_IMPORT_SEARCH" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] was unable to import a saved search from file '{0}'.
2013-06-24 13:41:48 +02:00
2016-02-04 13:04:33 +01:00
Verify that the file is a valid {1} export.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UNCOMPRESS_APPLIANCE_DESCRIPTION" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] will uncompress the file to '{0}'. After uncompression the original file '{1}' will be deleted. Continue?</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UNINSTALL" xml:space="preserve">
<value>Delete</value>
</data>
<data name="UNKNOWN" xml:space="preserve">
<value>Unknown</value>
</data>
<data name="UNKNOWN_AD_USER" xml:space="preserve">
<value><unknown AD user></value>
</data>
<data name="UNKNOWN_OBJECT" xml:space="preserve">
<value>unknown object</value>
</data>
<data name="UNLIMITED" xml:space="preserve">
<value>Unlimited</value>
</data>
<data name="UNRECOGNISED_PLUGIN_VERSION" xml:space="preserve">
<value>Unrecognised plugin version '{0}'</value>
</data>
<data name="UNSUPPORTED_SR_TYPE" xml:space="preserve">
<value>Unsupported SR type</value>
</data>
<data name="UNTAG" xml:space="preserve">
<value>Untag Ob&ject</value>
</data>
<data name="UNTAG_OBJECTS" xml:space="preserve">
<value>Untag Ob&jects</value>
</data>
<data name="UNTIL_RESTART_X_AFTER_RESTART_Y" xml:space="preserve">
<value>Until next restart {0}; after restart {1}</value>
</data>
<data name="UPDATED_PERFMON" xml:space="preserve">
<value>Updated performance monitoring configuration</value>
</data>
<data name="UPDATED_PROPERTIES" xml:space="preserve">
<value>Updating complete.</value>
</data>
<data name="UPDATES" xml:space="preserve">
<value>Updates</value>
</data>
<data name="UPDATES_DESC" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Automatically check for [XenServer] or [XenCenter] updates</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPDATES_DIALOG_ACTION_REQUIRED" xml:space="preserve">
<value>For the update to take effect after application, the following action is required:
</value>
</data>
<data name="UPDATES_DIALOG_APPLIED" xml:space="preserve">
<value>{0} - installed ({1})</value>
</data>
<data name="UPDATES_DIALOG_FULLY_APPLIED_PROMPT" xml:space="preserve">
<value>Fully installed</value>
</data>
<data name="UPDATES_DIALOG_NOT_APPLIED" xml:space="preserve">
<value>{0} - not installed</value>
</data>
<data name="UPDATES_DIALOG_NOT_APPLIED_PROMPT" xml:space="preserve">
<value>Not applied. Click here to apply</value>
</data>
<data name="UPDATES_DIALOG_PARTIALLY_APPLIED_PROMPT" xml:space="preserve">
<value>Partially installed. Click here to re-apply</value>
</data>
<data name="UPDATES_DIALOG_PENDING_UPDATES_PROMPT" xml:space="preserve">
<value>Pending updates. Click here to apply</value>
</data>
<data name="UPDATES_DIALOG_RESTART_ALL_HOSTS" xml:space="preserve">
<value>After applying this update, all servers must be restarted.</value>
</data>
<data name="UPDATES_DIALOG_RESTART_ALL_HVM_VMS" xml:space="preserve">
<value>After installing this update, all Windows VMs must be restarted.</value>
</data>
<data name="UPDATES_DIALOG_RESTART_ALL_PV_VMS" xml:space="preserve">
<value>After applying this update, all Linux VMs must be restarted.</value>
</data>
<data name="UPDATES_DIALOG_RESTART_ALL_VMS" xml:space="preserve">
<value>After installing this update, all VMs must be restarted.</value>
</data>
<data name="UPDATES_DIALOG_RESTART_HOST" xml:space="preserve">
<value>After installing this update, server '{0}' must be restarted.</value>
</data>
<data name="UPDATES_DIALOG_RESTART_HVM_VMS_ON_HOST" xml:space="preserve">
<value>After installing this update, all Windows VMs on server '{0}' must be restarted.</value>
</data>
<data name="UPDATES_DIALOG_RESTART_PV_VMS_ON_HOST" xml:space="preserve">
<value>After installing this update, all VMs on server '{0}' must be restarted.</value>
</data>
<data name="UPDATES_DIALOG_RESTART_VMS_ON_HOST" xml:space="preserve">
<value>After installing this update, all VMs on server '{0}' must be restarted.</value>
</data>
2013-12-05 13:46:39 +01:00
<data name="UPDATES_DOWNLOAD_AND_INSTALL" xml:space="preserve">
<value>Download and Install</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPDATES_WIZARD" xml:space="preserve">
<value>Install Update</value>
</data>
<data name="UPDATES_WIZARD_ACTIONS_FOR_HOST" xml:space="preserve">
<value>Actions for server '{0}'</value>
</data>
<data name="UPDATES_WIZARD_APPLIED_UPDATE" xml:space="preserve">
<value>Installed update</value>
</data>
<data name="UPDATES_WIZARD_APPLYING_UPDATE" xml:space="preserve">
2015-03-03 15:51:44 +01:00
<value>Installing update {0} to {1}... </value>
2013-06-24 13:41:48 +02:00
</data>
2015-02-27 18:00:03 +01:00
<data name="UPDATES_WIZARD_APPLYING_UPDATE_MULTIPLE_HOSTS" xml:space="preserve">
2015-03-03 15:51:44 +01:00
<value>Installing update to {0} servers...</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPDATES_WIZARD_APPLY_FAILED" xml:space="preserve">
<value>The update failed to apply. Would you like to view the output?</value>
</data>
<data name="UPDATES_WIZARD_APPLY_UPDATE" xml:space="preserve">
<value>&Install update</value>
</data>
<data name="UPDATES_WIZARD_BROKEN_STORAGE" xml:space="preserve">
<value>The {0} storage repository is broken.</value>
</data>
<data name="UPDATES_WIZARD_CANNOT_DOWNLOAD_PATCH" xml:space="preserve">
<value>Unable to download update from '{0}': no longer connected.
Check your settings and try again.</value>
</data>
<data name="UPDATES_WIZARD_CANNOT_MIGRATE_VM" xml:space="preserve">
<value>Cannot migrate VM '{0}'</value>
</data>
2016-06-14 14:38:12 +02:00
<data name="UPDATES_WIZARD_CANNOT_MIGRATE_VM_LICENSE_REASON" xml:space="preserve">
<value>Cannot migrate VM '{0}' due to license restrictions.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPDATES_WIZARD_CANNOT_MIGRATE_VM_UNKNOWN_REASON" xml:space="preserve">
<value>Cannot migrate VM '{0}' for an unknown reason. See application logs for more details.</value>
</data>
<data name="UPDATES_WIZARD_CANNOT_SEE_NETWORK" xml:space="preserve">
<value>The VM '{0}' uses the network '{1}', which cannot be seen from all servers.</value>
</data>
<data name="UPDATES_WIZARD_CANNOT_SUSPEND_VM" xml:space="preserve">
<value>This VM cannot be suspended and will be shut down.</value>
</data>
<data name="UPDATES_WIZARD_CANNOT_SUSPEND_VM_TITLE" xml:space="preserve">
<value>Cannot suspend VM '{0}'</value>
</data>
<data name="UPDATES_WIZARD_CANNOT_UPGRADE_WITH_VM" xml:space="preserve">
<value>Cannot upgrade with VM '{0}'</value>
</data>
<data name="UPDATES_WIZARD_CONNECTION_LOST" xml:space="preserve">
<value>The connections to your selected servers have been lost. Select alternate servers or reconnect to your selected servers.</value>
</data>
<data name="UPDATES_WIZARD_DISCONNECTED_SERVER" xml:space="preserve">
<value>No longer connected to '{0}'. Please review your selection and try again.</value>
</data>
<data name="UPDATES_WIZARD_EJECT_CD" xml:space="preserve">
<value>Click here to eject CD</value>
</data>
<data name="UPDATES_WIZARD_ENTERED_MAINTENANCE_MODE" xml:space="preserve">
<value>Entered maintenance mode</value>
</data>
<data name="UPDATES_WIZARD_ENTERING_MAINTENANCE_MODE" xml:space="preserve">
<value>Entering maintenance mode...</value>
</data>
<data name="UPDATES_WIZARD_ENTER_MAINTENANCE_MODE" xml:space="preserve">
<value>Enter maintenance mode</value>
</data>
<data name="UPDATES_WIZARD_EXITED_MAINTENANCE_MODE" xml:space="preserve">
<value>Exited maintenance mode</value>
</data>
<data name="UPDATES_WIZARD_EXITING_MAINTENANCE_MODE" xml:space="preserve">
<value>Exiting {0} from maintenance mode... </value>
</data>
<data name="UPDATES_WIZARD_EXIT_MAINTENANCE_MODE" xml:space="preserve">
<value>Exit maintenance mode</value>
</data>
<data name="UPDATES_WIZARD_FILE_NOT_FOUND" xml:space="preserve">
<value>Unable to find the update file '{0}'.
Check your settings and try again.</value>
</data>
<data name="UPDATES_WIZARD_HA_ON_DESCRIPTION" xml:space="preserve">
<value>Pool '{0}' cannot have HA enabled.</value>
</data>
<data name="UPDATES_WIZARD_HA_ON_TITLE" xml:space="preserve">
<value>HA is enabled on '{0}'</value>
</data>
2014-07-14 17:00:43 +02:00
<data name="UPDATES_WIZARD_HA_ON_WARNING" xml:space="preserve">
<value>{0}: Check skipped because HA is enabled on pool {1}.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPDATES_WIZARD_HOST_EXIT_MAINTENANCE_MODE" xml:space="preserve">
<value>Click here to exit maintenance mode</value>
</data>
<data name="UPDATES_WIZARD_HOST_MAINTENANCE_MODE" xml:space="preserve">
<value>Server {0} should be put into maintenance mode when required. You must start with all servers enabled.</value>
</data>
<data name="UPDATES_WIZARD_HOST_MAINTENANCE_MODE_TITLE" xml:space="preserve">
<value>Server '{0}'</value>
</data>
<data name="UPDATES_WIZARD_HOST_NOT_LIVE" xml:space="preserve">
<value>{0}: Server is unreachable.</value>
</data>
<data name="UPDATES_WIZARD_HOST_NOT_LIVE_TITLE" xml:space="preserve">
<value>Server '{0}' unreachable</value>
</data>
2014-07-14 17:00:43 +02:00
<data name="UPDATES_WIZARD_HOST_NOT_LIVE_WARNING" xml:space="preserve">
<value>{0}: Check skipped because the server is unreachable.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPDATES_WIZARD_INSTALL_TOOLS" xml:space="preserve">
<value>Click here to install tools</value>
</data>
<data name="UPDATES_WIZARD_LOCAL_CD" xml:space="preserve">
<value>VM '{0}' has a local CD/DVD in its drive.</value>
</data>
<data name="UPDATES_WIZARD_LOCAL_STORAGE" xml:space="preserve">
<value>{0}: The VM '{1}' uses local storage and cannot be migrated.</value>
</data>
<data name="UPDATES_WIZARD_NOTVALID_EXTENSION" xml:space="preserve">
2016-02-04 11:55:18 +01:00
<value>The selected file does not have a valid extension. Valid extensions are: *.{0} and *.iso</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPDATES_WIZARD_NOT_ENOUGH_SPACE" xml:space="preserve">
<value>This storage repository does not have enough space to suspend the required VMs.</value>
</data>
<data name="UPDATES_WIZARD_NOT_ENOUGH_SPACE_TITLE" xml:space="preserve">
<value>Not enough space on default SR '{0}'</value>
</data>
<data name="UPDATES_WIZARD_NO_ACTION" xml:space="preserve">
<value>No further action is required for this update.</value>
</data>
<data name="UPDATES_WIZARD_NO_DEFAULT_SR" xml:space="preserve">
<value>There is no default SR on this pool to suspend VMs to.</value>
</data>
<data name="UPDATES_WIZARD_NO_DEFAULT_SR_TITLE" xml:space="preserve">
<value>No Default SR on Pool '{0}'</value>
</data>
<data name="UPDATES_WIZARD_NO_HOSTS" xml:space="preserve">
<value>There are no servers available to migrate the VM {0} to.</value>
</data>
<data name="UPDATES_WIZARD_NO_MEMORY" xml:space="preserve">
<value>{0}: There is not enough memory available on other servers to migrate all the VMs off this server.</value>
</data>
2016-10-19 14:10:24 +02:00
<data name="UPDATES_WIZARD_NO_REBOOT_NEEDED" xml:space="preserve">
<value>{0}: This server does not need to be rebooted.</value>
</data>
<data name="UPDATES_WIZARD_NO_REBOOT_NEEDED_LIVE_PATCH" xml:space="preserve">
<value>{0}: This server does not need to be rebooted as live patching is used.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPDATES_WIZARD_NO_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>The VM {0} does not have [XenServer product] Tools installed.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPDATES_WIZARD_OUT_OF_DATE_TOOLS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>The VM {0} cannot be suspended until it has up to date [XenServer product] Tools.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPDATES_WIZARD_PAGE1_TOPTEXT" xml:space="preserve">
<value>Select the checkboxes for each server you wish to update. Select a pool checkbox to select all the available servers in the pool.</value>
</data>
<data name="UPDATES_WIZARD_PATCH_ALREADY_APPLIED" xml:space="preserve">
<value>{0}: The update has already been applied to this server. This server will be skipped.</value>
</data>
<data name="UPDATES_WIZARD_PATCH_ALREADY_APPLIED_TITLE" xml:space="preserve">
<value>Update Already Applied to Server '{0}'</value>
</data>
<data name="UPDATES_WIZARD_PLAN_ERROR" xml:space="preserve">
<value>An error occurred trying to execute plan stage '{0}'. The error was '{1}'</value>
</data>
<data name="UPDATES_WIZARD_PRECHECK_ERROR" xml:space="preserve">
<value>An error occurred during pre-update checks. The results may not be reliable.</value>
</data>
<data name="UPDATES_WIZARD_PRECHECK_FAILED" xml:space="preserve">
<value>{0}: {1}</value>
</data>
2016-11-16 13:35:09 +01:00
<data name="UPDATES_WIZARD_PRECHECK_FAILED_CONFLICTING_UPDATE" xml:space="preserve">
2016-11-25 11:45:44 +01:00
<value>{0}: Conflicting update(s) are present: {1}</value>
2016-11-16 13:35:09 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="UPDATES_WIZARD_PRECHECK_FAILED_ON_ALL_SERVERS" xml:space="preserve">
<value>Pre-update checks failed on the selected servers. The update will not be applied.</value>
</data>
2016-11-16 13:35:09 +01:00
<data name="UPDATES_WIZARD_PRECHECK_FAILED_REQUIRED_UPDATE_MISSING" xml:space="preserve">
2016-11-25 11:45:44 +01:00
<value>{0}: Prerequisite update(s) are missing: {1}</value>
2016-11-16 13:35:09 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="UPDATES_WIZARD_PRECHECK_FAILED_TITLE" xml:space="preserve">
<value>Update precheck failed on server '{0}'</value>
</data>
<data name="UPDATES_WIZARD_REBOOT" xml:space="preserve">
<value>Reboot</value>
</data>
<data name="UPDATES_WIZARD_REBOOTED" xml:space="preserve">
<value>Rebooted</value>
</data>
<data name="UPDATES_WIZARD_REBOOTING" xml:space="preserve">
<value>Rebooting {0} ... </value>
</data>
2016-10-19 14:10:24 +02:00
<data name="UPDATES_WIZARD_REBOOT_NEEDED" xml:space="preserve">
<value>{0}: This server needs to be rebooted after the update is applied.</value>
</data>
2015-07-08 18:35:50 +02:00
<data name="UPDATES_WIZARD_REMOVING_UPDATE" xml:space="preserve">
2016-07-28 14:50:09 +02:00
<value>Deleting update installation file {0} from {1}... </value>
2015-07-08 18:35:50 +02:00
</data>
2016-03-31 16:40:23 +02:00
<data name="UPDATES_WIZARD_REMOVING_UPDATES_FROM_POOL" xml:space="preserve">
<value>Removing update files from {0}...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPDATES_WIZARD_REPAIR_SR" xml:space="preserve">
<value>Click here to repair</value>
</data>
<data name="UPDATES_WIZARD_RESTARTED_AGENT" xml:space="preserve">
<value>Restarted agent</value>
</data>
<data name="UPDATES_WIZARD_RESTARTING_AGENT" xml:space="preserve">
<value>Restarting agent in {0} ... </value>
</data>
<data name="UPDATES_WIZARD_RESTART_AGENT" xml:space="preserve">
<value>Restart agent</value>
</data>
<data name="UPDATES_WIZARD_RESTART_SERVERS" xml:space="preserve">
<value>Reboot these servers:
</value>
</data>
<data name="UPDATES_WIZARD_RESTART_VMS" xml:space="preserve">
<value>Reboot these VMs:
</value>
</data>
<data name="UPDATES_WIZARD_RESUME_VM" xml:space="preserve">
<value>Click here to resume this VM</value>
</data>
2017-02-03 18:41:23 +01:00
<data name="UPDATES_WIZARD_RUNNING_PRECHECK" xml:space="preserve">
<value>Precheck for {0} in {1}...</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPDATES_WIZARD_SR_TITLE" xml:space="preserve">
<value>Storage repository '{0}'</value>
</data>
<data name="UPDATES_WIZARD_SUSPENDED_VM" xml:space="preserve">
<value>The VM {0} is suspended with a local or Tools CD</value>
</data>
<data name="UPDATES_WIZARD_TOOLS_CD" xml:space="preserve">
<value>VM '{0}' has the tools CD in its drive.</value>
</data>
2017-02-03 18:41:23 +01:00
<data name="UPDATES_WIZARD_UPLOADING_UPDATE" xml:space="preserve">
<value>Uploading update {0} to {1}...</value>
</data>
2013-12-11 11:41:54 +01:00
<data name="UPDATES_WIZARD_VM_HAS_VGPU" xml:space="preserve">
<value>The VM '{0}' has one or more virtual GPUs.</value>
</data>
2014-07-14 17:00:43 +02:00
<data name="UPDATES_WIZARD_WLB_ON_WARNING" xml:space="preserve">
<value>{0}: Check skipped because WLB is enabled on pool {1}.</value>
</data>
2015-07-29 18:52:46 +02:00
<data name="UPDATE_DISMISS_ALL_CONTINUE" xml:space="preserve">
<value>You have applied filters to the list of updates. Do you wish to dismiss all updates from every connected server, or only the updates you have chosen to view? In both cases the dismissed updates will be removed from the servers permanently.
Note that if RBAC is enabled, only updates which you have privileges to dismiss will be affected.</value>
</data>
<data name="UPDATE_DISMISS_ALL_NO_FILTER_CONTINUE" xml:space="preserve">
<value>This operation will remove permanently all updates from every connected server. Do you wish to continue?
Note that if RBAC is enabled, only updates which you have privileges to dismiss will be affected.</value>
</data>
2015-07-23 12:48:14 +02:00
<data name="UPDATE_DISMISS_CONFIRM" xml:space="preserve">
<value>Are you sure you want to dismiss this update?</value>
</data>
2015-07-29 18:52:46 +02:00
<data name="UPDATE_DISMISS_SELECTED_CONFIRM" xml:space="preserve">
<value>This operation will remove the selected updates from the servers permanently. Do you wish to continue?
Note that if RBAC is enabled, only updates which you have privileges to dismiss will be affected.</value>
</data>
2016-11-16 13:35:09 +01:00
<data name="UPDATE_ERROR_INTRODUCE" xml:space="preserve">
<value>Failed to introduce the update.</value>
</data>
2013-12-05 13:46:39 +01:00
<data name="UPDATE_EXPORT_ALL_OR_FILTERED" xml:space="preserve">
<value>You have applied filters to the list of updates. Do you wish to export all updates from every connected server, or only the updates you have chosen to view?</value>
</data>
2016-11-11 17:02:43 +01:00
<data name="UPDATE_FOR_DIFFERENT_XENSERVER_VERSION" xml:space="preserve">
2016-11-25 11:45:44 +01:00
<value>{0}: This update is not compatible with this server version.</value>
2016-11-11 17:02:43 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="UPDATE_MANAGER_CANNOT_REMOVE_APPLIED_PATCH" xml:space="preserve">
<value>Cannot remove an update which is applied to any servers.</value>
</data>
<data name="UPDATE_PERFMON" xml:space="preserve">
<value>Update performance monitoring configuration</value>
</data>
<data name="UPDATE_PROPERTIES" xml:space="preserve">
<value>Updating '{0}'</value>
</data>
2016-11-01 16:47:13 +01:00
<data name="UPDATE_TEMP_VDI_DESCRIPTION" xml:space="preserve">
<value>Temporary virtual disk used for the installation of an update</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPDATE_WAS_NOT_COMPLETED" xml:space="preserve">
2017-02-03 18:41:23 +01:00
<value>The installation of update {0} was not completed successfully</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPDATE_WAS_SUCCESSFULLY_INSTALLED" xml:space="preserve">
<value>Update {0} was successfully installed</value>
</data>
<data name="UPDATING_PERFMON" xml:space="preserve">
<value>Updating performance monitoring configuration</value>
</data>
<data name="UPDATING_PROPERTIES" xml:space="preserve">
<value>Updating...</value>
</data>
<data name="UPGRADEWIZARD_PATCHING_TEXT" xml:space="preserve">
<value>Apply Upgrade</value>
</data>
<data name="UPGRADEWIZARD_PATCHING_TITLE" xml:space="preserve">
<value>Applying the upgrade to the pool.</value>
</data>
<data name="UPGRADEWIZARD_PRECHECK_TEXT" xml:space="preserve">
<value>Upgrade Prechecks</value>
</data>
<data name="UPGRADEWIZARD_PRECHECK_TITLE" xml:space="preserve">
<value>Problems encountered when perfoming upgrade prechecks.</value>
</data>
2016-03-30 12:37:09 +02:00
<data name="UPGRADEWIZARD_PROBLEM_INCOMPATIBLE_CPUS" xml:space="preserve">
<value>Hosts in pool '{0}' have incompatible CPUs</value>
</data>
<data name="UPGRADEWIZARD_PROBLEM_INCOMPATIBLE_CPUS_HELPMESSAGE" xml:space="preserve">
<value>Shut down all VMs</value>
</data>
2014-06-06 14:50:13 +02:00
<data name="UPGRADEWIZARD_PROBLEM_INVALID_VCPU_SETTINGS" xml:space="preserve">
<value>VM '{0}' has invalid vCPU settings.</value>
</data>
<data name="UPGRADEWIZARD_PROBLEM_INVALID_VCPU_SETTINGS_HELPMESSAGE" xml:space="preserve">
<value>Fix vCPU configuration</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPGRADEWIZARD_SELECTSERVERS_TITLE" xml:space="preserve">
<value>Select the servers you wish to upgrade.</value>
</data>
2016-03-30 12:37:09 +02:00
<data name="UPGRADEWIZARD_WARNING_INCOMPATIBLE_CPUS" xml:space="preserve">
<value>{0}: Check skipped because hosts in pool '{1}' have incompatible CPUs</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPGRADE_HOST" xml:space="preserve">
<value>Upgrade host {0}</value>
</data>
<data name="UPGRADE_MASTER" xml:space="preserve">
<value>Upgrade master {0}</value>
</data>
<data name="UPGRADE_PLAN" xml:space="preserve">
<value>Apply Upgrade</value>
</data>
<data name="UPGRADE_POOL" xml:space="preserve">
<value>Upgrade pool {0}</value>
</data>
<data name="UPGRADE_POOL_MASTER" xml:space="preserve">
<value>Upgrade pool master '{0}'</value>
</data>
<data name="UPGRADE_POOL_MASTER_X" xml:space="preserve">
<value> Upgrade pool master {0}</value>
</data>
<data name="UPGRADE_PRECHECKS_TEXT" xml:space="preserve">
<value>Prechecks</value>
</data>
<data name="UPGRADE_PRECHECKS_TITLE" xml:space="preserve">
<value>Perform upgrade prechecks on selected pools</value>
</data>
<data name="UPGRADE_SERVER" xml:space="preserve">
<value>Upgrade server '{0}</value>
</data>
<data name="UPGRADE_SERVER_X" xml:space="preserve">
<value> Upgrade server {0}</value>
</data>
<data name="UPGRADE_SLAVE" xml:space="preserve">
<value>Upgrade '{0}'</value>
</data>
<data name="UPGRADING" xml:space="preserve">
<value>Upgrading</value>
</data>
<data name="UPGRADING_SERVER" xml:space="preserve">
<value>Upgrading server '{0}' ...</value>
</data>
<data name="UPLOADING_PATCH" xml:space="preserve">
<value>Uploading Update...</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="UPLOADING_PATCH_PROGRESS" xml:space="preserve">
<value>Uploading - {0}%</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPLOADING_PATCH_TO" xml:space="preserve">
2015-01-09 13:54:12 +01:00
<value>Uploading to server '{0}'...</value>
2013-06-24 13:41:48 +02:00
</data>
2015-01-23 11:41:54 +01:00
<data name="UPLOAD_PATCH_ALREADY_UPLOADED" xml:space="preserve">
2015-02-05 18:01:14 +01:00
<value>Already uploaded</value>
2015-01-23 11:41:54 +01:00
</data>
<data name="UPLOAD_PATCH_DESCRIPTION" xml:space="preserve">
<value>Uploading...</value>
</data>
<data name="UPLOAD_PATCH_END_DESCRIPTION" xml:space="preserve">
<value>Update successfully uploaded to selected server(s)</value>
</data>
<data name="UPLOAD_PATCH_TITLE" xml:space="preserve">
2015-02-04 18:33:10 +01:00
<value>Upload</value>
</data>
2015-10-15 15:15:10 +02:00
<data name="UPLOAD_PATCH_UPLOADED" xml:space="preserve">
<value>Uploaded</value>
</data>
2016-05-20 14:01:51 +02:00
<data name="UPSELL_BLURB_AD" xml:space="preserve">
<value>Upgrade your [XenServer] license to enable Active Directory. Active Directory allows you to configure [XenServer] access control by adding named user accounts.</value>
</data>
<data name="UPSELL_BLURB_AD_MORE" xml:space="preserve">
<value>
To learn more about the [XenServer] Active Directory feature or to start a [XenServer] trial, click the button below.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UPSELL_BLURB_ALERTS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable Alerting and Reporting capabilities. Email based performance and error alerting will proactively notify administrators of error conditions or performance problems before they affect critical services.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_ALERTS_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] Alerting and Reporting feature or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_CPM" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable VM live migration. This feature enables you to migrate running VMs on shared or local storage between servers in the same pool or across pools with no VM downtime. </value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_CPM_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] Cross-Pool Migration feature or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_CPUMASKING" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable Heterogeneous Pools. Heterogeneous Pools allows hosts with different CPUs to form a resource pool, and allows virtual machines to migrate between them.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_CPUMASKING_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] Heterogeneous Pools feature or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_DMC" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable Dynamic Memory Control. Dynamic Memory Control allows [XenServer] to adjust the memory of live virtual machines, and respond dynamically to changing demands on the host server.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_DMC_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] Dynamic Memory Control feature or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_DR" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable Disaster Recovery. The Disaster Recovery feature allows you to recover your critical VMs and vApps at your DR site in the event of a disaster at your primary production site.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_DR_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] Disaster Recovery feature or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_ENHANCEDSR" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable StorageLink™ Technology. StorageLink allows [XenServer] to leverage all the power of your existing storage hardware and offload storage operations automatically. This allows for high performance and space efficient storage provisioning, cloning, and snapshot capabilities to be handled in hardware using your storage hardware's native features.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_GPU" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable GPU pass-through. The GPU pass-through feature allows you to assign a dedicated graphics processing unit to a VM for higher graphics performance.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_GPU_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] GPU pass-through feature or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_HA" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable High Availability. High Availability allows virtual machines to be automatically restarted in the event of an underlying hardware failure or individual VM failure. If the server fails the VMs will be intelligently restarted on other virtualized servers in the resource pool.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_HA_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] High Availability feature or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_PERFORMANCE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable Performance Reporting capabilities. Performance Reporting provides guidance on overall environment performance trends and enables you to accurately plan capacity as business needs change.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_PERFORMANCE_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] Performance Reporting capabilities feature or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_RBAC" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable Role Based Access Control. Using the RBAC feature, you will be able to control access to vital components in your [XenServer] resource pools, with full audit logging capabilities and seamless integration with your current Active Directory setup.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_RBAC_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] Role Based Access Control feature or to start a [XenServer] trial, click the button below.</value>
2016-01-27 11:36:48 +01:00
</data>
<data name="UPSELL_BLURB_VMSS" xml:space="preserve">
2016-02-16 10:49:39 +01:00
<value>Upgrade your [XenServer] license to enable VM Scheduled Snapshots. VM Scheduled Snapshost allows you to create automatic snapshots for your critical VMs.</value>
2016-01-27 11:36:48 +01:00
</data>
<data name="UPSELL_BLURB_VMSS_MORE" xml:space="preserve">
<value>
2016-02-16 10:49:39 +01:00
To learn more about the [XenServer] VM Scheduled Snapshots feature or to start a XenServer trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_VM_APPLIANCES" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable vApps. The vApps feature allows you to place your VMs into groups, allowing them to be started or stopped as a unit, and also allowing them to be easily recovered at your DR site in the event of a disaster at your primary production site.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_VM_APPLIANCES_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the vApps feature of [XenServer] or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_VM_PROTECTION" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable VM Protection and Recovery. VM Protection and Recovery allows you to protect your critical VMs by scheduling automatic snapshots, and optionally, archiving those snapshots to a CIFS or NFS share.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_VM_PROTECTION_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] VM Protection and Recovery feature or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPSELL_BLURB_WLB" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Upgrade your [XenServer] license to enable Dynamic Workload Balancing. Dynamic Workload Balancing continually profiles your virtual machines’ and [XenServer] hosts’ performance and will intelligently rebalance and optimally place new workloads to ensure the best use of physical server resources in your resource pool.</value>
2016-01-21 09:54:22 +01:00
</data>
<data name="UPSELL_BLURB_WLB_MORE" xml:space="preserve">
<value>
2013-06-24 13:41:48 +02:00
2016-02-10 12:52:30 +01:00
To learn more about the [XenServer] Dynamic Workload Balancing feature or to start a [XenServer] trial, click the button below.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="UPTIME" xml:space="preserve">
<value>Uptime</value>
</data>
<data name="URI_REGEX" xml:space="preserve">
<value>^(http|https|file|ftp)://*</value>
</data>
<data name="USER_AUTHORIZATION_FAILED" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] was unable to authorize the action as {0}. See the application log files for more information.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="USER_NOT_AUTHORIZED" xml:space="preserve">
<value>The user you have entered is not authorized to complete this action</value>
</data>
<data name="USES" xml:space="preserve">
<value>uses</value>
</data>
2014-07-25 09:35:18 +02:00
<data name="UTILIZATION" xml:space="preserve">
2014-08-05 05:26:00 +02:00
<value>Computer Utilization (%)</value>
2014-07-25 09:35:18 +02:00
</data>
<data name="UUID" xml:space="preserve">
<value>UUID</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="UUID_SEARCH" xml:space="preserve">
<value>Is</value>
</data>
<data name="VALUE_HYPHEN_VALUE" xml:space="preserve">
<value>{0} - {1}</value>
</data>
<data name="VAL_B" xml:space="preserve">
<value>{0} B</value>
</data>
<data name="VAL_BYTE" xml:space="preserve">
<value>B</value>
</data>
<data name="VAL_FORMAT" xml:space="preserve">
<value>{0} {1}</value>
</data>
<data name="VAL_FORMAT_SECONDS" xml:space="preserve">
<value>{0}{1}</value>
</data>
<data name="VAL_GB" xml:space="preserve">
<value>{0} GB</value>
</data>
2015-08-20 13:41:39 +02:00
<data name="VAL_GB_ONE_DECIMAL" xml:space="preserve">
<value>{0:F1} GB</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VAL_GIGB" xml:space="preserve">
<value>GB</value>
</data>
<data name="VAL_GIGRATE" xml:space="preserve">
<value>GBps</value>
</data>
<data name="VAL_KB" xml:space="preserve">
<value>{0} kB</value>
</data>
<data name="VAL_KILB" xml:space="preserve">
<value>kB</value>
</data>
2013-11-14 12:33:59 +01:00
<data name="VAL_KILOWATT" xml:space="preserve">
<value>kW</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VAL_KILRATE" xml:space="preserve">
<value>kBps</value>
</data>
<data name="VAL_MB" xml:space="preserve">
<value>{0} MB</value>
</data>
<data name="VAL_MEGB" xml:space="preserve">
<value>MB</value>
</data>
<data name="VAL_MEGRATE" xml:space="preserve">
<value>MBps</value>
</data>
<data name="VAL_MICSEC" xml:space="preserve">
<value>μs</value>
</data>
<data name="VAL_MILSEC" xml:space="preserve">
<value>ms</value>
</data>
2013-11-14 12:33:59 +01:00
<data name="VAL_MILWATT" xml:space="preserve">
<value>mW</value>
</data>
<data name="VAL_MWATT" xml:space="preserve">
<value>MW</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VAL_NANOSEC" xml:space="preserve">
<value>ns</value>
</data>
<data name="VAL_RATE" xml:space="preserve">
<value>Bps</value>
</data>
<data name="VAL_RATE_NUM_FORMAT" xml:space="preserve">
<value>0.0</value>
</data>
<data name="VAL_SEC" xml:space="preserve">
<value>s</value>
</data>
2013-11-14 12:33:59 +01:00
<data name="VAL_WATT" xml:space="preserve">
<value>W</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VAPP_SHUTDOWN_CONTEXT_MENU" xml:space="preserve">
<value>Shut Dow&n vApp</value>
</data>
<data name="VAPP_SHUT_DOWN_MENU" xml:space="preserve">
<value>Shut Dow&n vApp</value>
</data>
<data name="VAPP_START_CONTEXT_MENU" xml:space="preserve">
<value>&Start vApp</value>
</data>
<data name="VAPP_START_MENU" xml:space="preserve">
<value>S&tart vApp</value>
</data>
<data name="VBD_EDIT_CURRENTLY_ATTACHED" xml:space="preserve">
<value>The disk is attached to a VM that is not in halted state.</value>
</data>
<data name="VCPU_ONLY_WHEN_HALTED" xml:space="preserve">
2016-09-29 13:11:37 +02:00
<value>The VCPUs can only be changed when the VM is shut down.</value>
2013-06-24 13:41:48 +02:00
</data>
2014-07-25 09:35:18 +02:00
<data name="VDI" xml:space="preserve">
<value>VDI</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VDI_COPIED" xml:space="preserve">
<value>Copied disk '{0}' from SR '{1}' to SR '{2}'</value>
</data>
<data name="VDI_COPYING" xml:space="preserve">
<value>Copying disk '{0}' from SR '{1}' to SR '{2}'</value>
</data>
2015-01-23 11:41:54 +01:00
<data name="VDI_ON_SR_TITLE" xml:space="preserve">
<value>{0} on '{1}' {2}</value>
2015-02-04 18:33:10 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="VENDOR_NAME" xml:space="preserve">
<value>Vendor</value>
</data>
<data name="VERIFYING_MANIFEST" xml:space="preserve">
<value>Verifying Manifest Content...</value>
</data>
<data name="VERIFYING_MANIFEST_ERROR" xml:space="preserve">
<value>Manifest verification failed. {0}</value>
</data>
<data name="VERIFYING_SIGNATURE" xml:space="preserve">
<value>Verifying Digital Signature...</value>
</data>
<data name="VERIFYING_SIGNATURE_ERROR" xml:space="preserve">
<value>Signature verification failed. {0}</value>
</data>
<data name="VERSION_NUMBER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] version {0} (build {1}.{2}) {3}-bit</value>
2013-11-18 15:31:00 +01:00
</data>
2016-07-21 23:20:36 +02:00
<data name="VGPU_DESCRIPTION_MANY" xml:space="preserve">
2015-03-30 17:21:46 +02:00
<value>{0} virtual GPU ({1} per GPU, {2}, {3} displays)</value>
2013-06-24 13:41:48 +02:00
</data>
2016-07-21 23:20:36 +02:00
<data name="VGPU_DESCRIPTION_ONE" xml:space="preserve">
<value>{0} virtual GPU ({1} per GPU, {2}, {3} display)</value>
</data>
2017-03-07 17:13:53 +01:00
<data name="VGPU_DESCRIPTION_ZEROES" xml:space="preserve">
<value>{0} virtual GPU ({1} per GPU)</value>
</data>
2013-09-18 14:06:47 +02:00
<data name="VGPU_PASSTHRU_TOSTRING" xml:space="preserve">
<value>Pass-through whole GPU</value>
</data>
<data name="VGPU_TOSTRING" xml:space="preserve">
2015-03-30 17:21:46 +02:00
<value>{0} virtual GPU ({1} per GPU)</value>
2013-09-18 14:06:47 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="VIEW_FOLDER_MENU_OPTION" xml:space="preserve">
<value>View folder...</value>
</data>
2013-07-01 17:59:42 +02:00
<data name="VIEW_INFRASTRUCTURE" xml:space="preserve">
<value>Infrastructure</value>
</data>
<data name="VIEW_OBJECTS" xml:space="preserve">
2013-08-28 15:44:46 +02:00
<value>Objects by Type</value>
2013-07-01 17:59:42 +02:00
</data>
<data name="VIEW_ORGANIZATION" xml:space="preserve">
<value>Organization Views</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VIEW_POLICIES" xml:space="preserve">
<value>View VM Protection Policies</value>
</data>
<data name="VIEW_TAG_MENU_OPTION" xml:space="preserve">
<value>View tag...</value>
</data>
2016-02-05 08:14:39 +01:00
<data name="VIEW_VMSS_POLICIES" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>View snapshot schedules</value>
2016-02-05 08:14:39 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="VIF_HOTPLUG_FAILED_MESSAGE" xml:space="preserve">
<value>The virtual network device changes will take effect when you next restart the VM.</value>
</data>
<data name="VIF_HOTPLUG_FAILED_TITLE" xml:space="preserve">
<value>Virtual Network Device Changes</value>
</data>
<data name="VIF_LICENSE_RESTRICTION" xml:space="preserve">
<value>Upgrade your license to enable QoS settings</value>
</data>
<data name="VIF_VSWITCH_CONTROLLER" xml:space="preserve">
<value>QoS settings should be configured using the vSwitch Controller</value>
</data>
<data name="VIRTUALIZATION_OPTIMIZED" xml:space="preserve">
<value>Optimized (version {0} installed)</value>
</data>
<data name="VIRTUALIZATION_OUT_OF_DATE" xml:space="preserve">
<value>Tools out of date (version {0} installed)</value>
</data>
2015-08-13 18:41:15 +02:00
<data name="VIRTUALIZATION_STATE_VM_INSTALL_IO_DRIVERS_AND_MANAGEMENT_AGENT" xml:space="preserve">
<value>Install I/O drivers and Management Agent</value>
</data>
<data name="VIRTUALIZATION_STATE_VM_INSTALL_MANAGEMENT_AGENT" xml:space="preserve">
<value>Install Management Agent</value>
</data>
2015-09-10 15:55:04 +02:00
<data name="VIRTUALIZATION_STATE_VM_IO_DRIVERS_AND_MANAGEMENT_AGENT_INSTALLED" xml:space="preserve">
<value>I/O drivers and Management Agent installed</value>
</data>
2015-08-13 18:41:15 +02:00
<data name="VIRTUALIZATION_STATE_VM_IO_NOT_OPTIMIZED" xml:space="preserve">
2015-08-14 15:25:49 +02:00
<value>I/O not optimized</value>
2015-08-13 18:41:15 +02:00
</data>
<data name="VIRTUALIZATION_STATE_VM_IO_OPTIMIZED" xml:space="preserve">
2015-08-14 15:25:49 +02:00
<value>I/O optimized</value>
2015-08-13 18:41:15 +02:00
</data>
2015-09-29 16:39:17 +02:00
<data name="VIRTUALIZATION_STATE_VM_IO_OPTIMIZED_ONLY" xml:space="preserve">
<value>I/O optimized only</value>
</data>
2015-08-13 18:41:15 +02:00
<data name="VIRTUALIZATION_STATE_VM_MANAGEMENT_AGENT_INSTALLED" xml:space="preserve">
2015-08-14 15:25:49 +02:00
<value>Management Agent installed</value>
2015-08-13 18:41:15 +02:00
</data>
<data name="VIRTUALIZATION_STATE_VM_MANAGEMENT_AGENT_NOT_INSTALLED" xml:space="preserve">
2015-08-14 15:25:49 +02:00
<value>Management Agent not installed</value>
2015-08-13 18:41:15 +02:00
</data>
2015-09-29 16:39:17 +02:00
<data name="VIRTUALIZATION_STATE_VM_NOT_OPTIMIZED" xml:space="preserve">
<value>Not optimized</value>
</data>
2015-12-15 15:32:11 +01:00
<data name="VIRTUALIZATION_STATE_VM_NOT_RECEIVING_UPDATES" xml:space="preserve">
2016-03-16 12:06:29 +01:00
<value>Not able to receive updates from Windows Update</value>
2015-12-15 15:32:11 +01:00
</data>
2015-09-29 16:39:17 +02:00
<data name="VIRTUALIZATION_STATE_VM_OPTIMIZED" xml:space="preserve">
<value>Fully optimized</value>
</data>
2015-08-13 18:41:15 +02:00
<data name="VIRTUALIZATION_STATE_VM_RECEIVING_UPDATES" xml:space="preserve">
2016-03-16 12:06:29 +01:00
<value>Able to receive updates from Windows Update</value>
2015-08-13 18:41:15 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="VIRTUALIZATION_UNKNOWN" xml:space="preserve">
2015-02-05 15:33:44 +01:00
<value>Unknown (please wait)</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="VIRTUAL_DISK" xml:space="preserve">
<value>Virtual Disk</value>
</data>
<data name="VIRTUAL_DISKS" xml:space="preserve">
<value>Virtual Disks</value>
</data>
<data name="VIRTUAL_INTERFACE_PROPERTIES" xml:space="preserve">
<value>Virtual Interface Properties</value>
</data>
2016-10-14 14:51:51 +02:00
<data name="VIRTUAL_MACHINE" xml:space="preserve">
<value>Virtual Machine</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VIRTUAL_MACHINES" xml:space="preserve">
<value>Virtual Machines</value>
</data>
<data name="VM" xml:space="preserve">
<value>VM</value>
</data>
<data name="VMPP" xml:space="preserve">
<value>VM Protection Policy</value>
</data>
2016-02-15 05:35:26 +01:00
<data name="VMPP_DIALOG_TEXT" xml:space="preserve">
<value>Protect your critical VMs with a protection policy that takes regular scheduled snapshots and, optionally, archives the snapshots to a CIFS or NFS share.</value>
</data>
<data name="VMPP_DIALOG_TITLE" xml:space="preserve">
<value>VM Protection Policies</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="VMPP_EMAIL_CHECKBOX_TEXT" xml:space="preserve">
<value>Send &email notifications about VM protection job alerts</value>
</data>
<data name="VMPP_EMAIL_PAGE_TEXT" xml:space="preserve">
<value>XenServer can send you email notifications when alerts associated with VM protection jobs are raised, such as when a VM snapshot is created or archived, or when a snapshot or archive operation fails.</value>
</data>
<data name="VMPP_FINISH_PAGE_CHECKBOX_TEXT" xml:space="preserve">
<value>&Run the new VM protection job when I click Finish</value>
</data>
<data name="VMPP_FINISH_PAGE_TEXT" xml:space="preserve">
<value>Review the new VM protection policy below and click Previous if you want to change any settings or Finish to create the new policy.</value>
</data>
2016-02-19 06:49:24 +01:00
<data name="VMPP_FINISH_TITLE" xml:space="preserve">
<value>Create the new policy</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="VMPP_SCHEDULED_SNAPSHOTS_DEFINED_FOR_POOL" xml:space="preserve">
<value>VM protection policies defined in pool '{0}' ({1} out of {2} VMs currently protected):</value>
</data>
<data name="VMPP_SCHEDULED_SNAPSHOTS_DEFINED_FOR_SERVER" xml:space="preserve">
<value>VM protection policies defined in server '{0}' ({1} out of {2} VMs currently protected):</value>
</data>
2016-02-19 06:49:24 +01:00
<data name="VMPP_TYPE" xml:space="preserve">
<value>protection policy</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="VMPP_WIZARD_TITLE" xml:space="preserve">
<value>New VM Protection Policy</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VMS" xml:space="preserve">
<value>VMs</value>
</data>
2017-01-10 07:18:18 +01:00
<data name="VMSS_ALERT_DETAILS" xml:space="preserve">
<value>Details:</value>
</data>
<data name="VMSS_ALERT_VM_ERROR_FORMAT" xml:space="preserve">
<value>{0}. {1}: {2}</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="VMSS_CONTEXT_MENU" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Snapshot sched&ules ...</value>
2016-01-27 11:36:48 +01:00
</data>
2016-02-15 05:35:26 +01:00
<data name="VMSS_DIALOG_TEXT" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Create a snapshot schedule for your VMs.</value>
2016-02-15 05:35:26 +01:00
</data>
<data name="VMSS_DIALOG_TITLE" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Snapshot schedules</value>
2016-02-15 05:35:26 +01:00
</data>
2016-01-29 12:34:44 +01:00
<data name="VMSS_EMAIL_CHECKBOX_TEXT" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Send &email notifications about snapshot schedule job alerts</value>
2016-01-29 12:34:44 +01:00
</data>
<data name="VMSS_EMAIL_PAGE_TEXT" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>XenServer can send you email notifications when alerts associated with snapshot schedule jobs are raised, such as when a VM snapshot is created or when a snapshot operation fails.</value>
2016-01-29 12:34:44 +01:00
</data>
<data name="VMSS_FINISH_PAGE_CHECKBOX_TEXT" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>&Run the new snapshot schedule job when I click Finish</value>
2016-01-29 12:34:44 +01:00
</data>
<data name="VMSS_FINISH_PAGE_TEXT" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Review the new snapshot schedule below and click Previous if you want to change any settings or Finish to create the new schedule.</value>
2016-01-29 12:34:44 +01:00
</data>
2016-02-19 06:49:24 +01:00
<data name="VMSS_FINISH_TITLE" xml:space="preserve">
<value>Create the new schedule</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="VMSS_MAIN_MENU" xml:space="preserve">
<value>VM Snaps&hot Schedules...</value>
</data>
2016-02-19 06:49:24 +01:00
<data name="VMSS_NAME" xml:space="preserve">
<value>Schedule Name</value>
</data>
<data name="VMSS_NAME_FIELD_TEXT" xml:space="preserve">
<value>Schedule na&me:</value>
</data>
<data name="VMSS_NAME_TITLE" xml:space="preserve">
<value>What do you want to call this schedule?</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="VMSS_POLICY_SUMMARY" xml:space="preserve">
<value>Job name:\r\n {0}\r\n\r\nSelected VMs:\r\n {1}\r\n\r\nSnapshot type:\r\n {2}\r\n\r\nSchedule:\r\n {3}\r\n</value>
</data>
<data name="VMSS_SCHEDULED_SNAPSHOTS_DEFINED_FOR_POOL" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Snapshot schedules defined in pool '{0}' ({1} out of {2} VMs currently in schedule):</value>
2016-01-29 12:34:44 +01:00
</data>
<data name="VMSS_SCHEDULED_SNAPSHOTS_DEFINED_FOR_SERVER" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>Snapshot schedules defined in server '{0}' ({1} out of {2} VMs currently in schedule):</value>
2016-01-29 12:34:44 +01:00
</data>
2016-02-19 06:49:24 +01:00
<data name="VMSS_TYPE" xml:space="preserve">
<value>schedule</value>
</data>
2016-01-27 11:36:48 +01:00
<data name="VMSS_VMS" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>VMs in the snapshot schedule</value>
2016-01-27 11:36:48 +01:00
</data>
<data name="VMSS_VMS_TITLE" xml:space="preserve">
<value>Select the VMs that you want to schedule snapshots for</value>
</data>
2016-01-29 12:34:44 +01:00
<data name="VMSS_WIZARD_TITLE" xml:space="preserve">
2016-02-18 11:49:40 +01:00
<value>New snapshot schedule</value>
2016-01-29 12:34:44 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="VMS_IN_POOL" xml:space="preserve">
<value>VMs in pool '{0}':</value>
</data>
<data name="VMS_IN_SERVER" xml:space="preserve">
<value>VMs in server '{0}':</value>
</data>
2016-11-21 13:01:41 +01:00
<data name="VMS_MANY" xml:space="preserve">
<value>{0} VMs</value>
</data>
<data name="VMS_ONE" xml:space="preserve">
<value>1 VM</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VM_ALREADY_SUSPENDED" xml:space="preserve">
<value>This VM is already suspended.</value>
</data>
<data name="VM_APPLIANCE" xml:space="preserve">
<value>vApp</value>
</data>
<data name="VM_APPLIANCES" xml:space="preserve">
<value>vApps</value>
</data>
<data name="VM_APPLIANCES_DEFINED_FOR_POOL" xml:space="preserve">
<value>vApps defined in pool '{0}': </value>
</data>
<data name="VM_APPLIANCES_DEFINED_FOR_SERVER" xml:space="preserve">
<value>vApps defined in server '{0}': </value>
</data>
<data name="VM_APPLIANCES_MENU" xml:space="preserve">
<value>Manage &vApps...</value>
</data>
<data name="VM_APPLIANCES_TITLE" xml:space="preserve">
<value>Manage vApps - pool {0}</value>
</data>
<data name="VM_APPLIANCE_PROPERTIES" xml:space="preserve">
<value>vApp Properties...</value>
</data>
<data name="VM_APPLIANCE_SHUTTING_DOWN" xml:space="preserve">
<value>Shutting down vApp '{0}'</value>
</data>
<data name="VM_APPLIANCE_SHUTTING_DOWN_COMPLETED" xml:space="preserve">
<value>Shut down vApp '{0}' completed</value>
</data>
<data name="VM_APPLIANCE_SHUT_DOWN" xml:space="preserve">
<value>Shut down all VMs in vApp</value>
</data>
<data name="VM_APPLIANCE_START" xml:space="preserve">
<value>Start all VMs in vApp</value>
</data>
<data name="VM_APPLIANCE_STARTING" xml:space="preserve">
<value>Starting vApp '{0}'</value>
</data>
<data name="VM_APPLIANCE_STARTING_COMPLETED" xml:space="preserve">
<value>Start vApp '{0}' completed</value>
</data>
<data name="VM_APPLIANCE_STARTING_PAUSED" xml:space="preserve">
<value>Starting vApp '{0}' in paused mode</value>
</data>
<data name="VM_APPLIANCE_STARTING_PAUSED_COMPLETED" xml:space="preserve">
<value>Start vApp '{0}' in paused mode completed</value>
</data>
<data name="VM_APPLIANCE_START_PAUSED" xml:space="preserve">
<value>Start all VMs in vApp in paused mode</value>
</data>
<data name="VM_APPLIANCE_SUMMARY" xml:space="preserve">
<value>vApp name:\r\n {0}\r\n\r\nSelected VMs:\r\n {1}</value>
</data>
2015-02-26 15:12:16 +01:00
<data name="VM_CLOUD_CONFIG_DRIVE_CANNOT_RETRIEVE_DEFAULT" xml:space="preserve">
<value>Unable to retrieve the default cloud-config parameters.</value>
</data>
2015-02-19 15:48:52 +01:00
<data name="VM_CLOUD_CONFIG_DRIVE_INCLUDED" xml:space="preserve">
<value>Config drive included</value>
</data>
<data name="VM_CLOUD_CONFIG_DRIVE_NOT_INCLUDED" xml:space="preserve">
<value>Config drive not included</value>
</data>
2015-02-26 15:12:16 +01:00
<data name="VM_CLOUD_CONFIG_DRIVE_READONLY" xml:space="preserve">
<value>The cloud-config parameters can only be changed when the VM is shut down.</value>
</data>
<data name="VM_CLOUD_CONFIG_DRIVE_UNAVAILABLE" xml:space="preserve">
<value>The cloud-config parameters could not be retrieved.</value>
</data>
2016-09-29 13:11:37 +02:00
<data name="VM_CPUMEMPAGE_CURRENT_VCPUS_LABEL" xml:space="preserve">
<value>Current number of v&CPUs:</value>
</data>
<data name="VM_CPUMEMPAGE_CURRENT_VCPUS_READONLY" xml:space="preserve">
<value>The current number of vCPUs can only be changed when the VM is running or shut down. </value>
</data>
<data name="VM_CPUMEMPAGE_INITIAL_VCPUS_LABEL" xml:space="preserve">
<value>Initial number of v&CPUs:</value>
</data>
<data name="VM_CPUMEMPAGE_MAX_VCPUS_LABEL" xml:space="preserve">
<value>Ma&ximum number of vCPUs:</value>
</data>
<data name="VM_CPUMEMPAGE_MAX_VCPUS_READONLY" xml:space="preserve">
<value>The maximum number of vCPUs, the topology and the vCPU priority can only be changed when the VM is shut down. </value>
</data>
<data name="VM_CPUMEMPAGE_RUBRIC" xml:space="preserve">
<value>Specify the number of vCPUs, their topology, and the priority to assign them over other vCPUs. </value>
</data>
<data name="VM_CPUMEMPAGE_RUBRIC_HOTPLUG" xml:space="preserve">
<value>If the initial number of vCPUs is set lower than the maximum number, more vCPUs can be added to the virtual machine while it is running. </value>
</data>
<data name="VM_CPUMEMPAGE_VCPUS_LABEL" xml:space="preserve">
<value>Number of v&CPUs:</value>
</data>
2015-02-06 18:46:58 +01:00
<data name="VM_ENLIGHTENMENT" xml:space="preserve">
2015-02-24 11:46:11 +01:00
<value>Container Management</value>
2015-02-06 18:46:58 +01:00
</data>
2013-06-24 13:41:48 +02:00
<data name="VM_GENERAL_TAB_TITLE" xml:space="preserve">
<value>VM General Properties</value>
</data>
<data name="VM_LIVE_CHANGES_NOT_SUPPORTED_MESSAGE" xml:space="preserve">
<value>Memory and/or VCPU changes will take effect when you restart the VM.</value>
</data>
<data name="VM_LIVE_CHANGES_NOT_SUPPORTED_TITLE" xml:space="preserve">
<value>VM General Changes</value>
</data>
2015-09-09 14:56:11 +02:00
<data name="VM_MISSING_IO_DRIVERS" xml:space="preserve">
<value>I/O drivers not installed.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VM_NETWORK_TAB_ACTIVATE_BUTTON_LABEL" xml:space="preserve">
<value>A&ctivate</value>
</data>
<data name="VM_NETWORK_TAB_ADD_BUTTON_LABEL" xml:space="preserve">
<value>&Add Interface...</value>
</data>
<data name="VM_NETWORK_TAB_DEACTIVATE_BUTTON_LABEL" xml:space="preserve">
<value>Dea&ctivate</value>
</data>
<data name="VM_NETWORK_TAB_EDIT_BUTTON_LABEL" xml:space="preserve">
<value>P&roperties</value>
</data>
<data name="VM_NETWORK_TAB_REMOVE_BUTTON_LABEL" xml:space="preserve">
<value>R&emove Interface</value>
</data>
<data name="VM_NETWORK_TAB_TITLE" xml:space="preserve">
<value>Virtual Network Interfaces</value>
</data>
<data name="VM_NOT_HALTED" xml:space="preserve">
<value>{0} is not in halted or suspended state. Current state: {1}</value>
</data>
<data name="VM_NOT_SHUT_DOWN" xml:space="preserve">
<value>This VM is not shut down.</value>
</data>
<data name="VM_NOT_SUSPENDED" xml:space="preserve">
<value>This VM is not suspended.</value>
</data>
2015-06-09 13:34:13 +02:00
<data name="VM_OPERATING_MODE_HVM" xml:space="preserve">
2015-07-16 12:01:17 +02:00
<value>Hardware-assisted Virtualization (HVM)</value>
2015-06-09 13:34:13 +02:00
</data>
<data name="VM_OPERATING_MODE_PV" xml:space="preserve">
2015-07-16 12:01:17 +02:00
<value>Paravirtualization (PV)</value>
2015-06-09 13:34:13 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="VM_PAUSED" xml:space="preserve">
<value>This VM is paused.</value>
</data>
<data name="VM_PROTECTION_CONTEXT_MENU" xml:space="preserve">
<value>VM Pr&otection Policies...</value>
</data>
<data name="VM_PROTECTION_MAIN_MENU" xml:space="preserve">
<value>VM &Protection Policies...</value>
</data>
<data name="VM_PROTECTION_POLICY_FAILED" xml:space="preserve">
<value>{0} ({1} VMs failed)</value>
</data>
<data name="VM_PROTECTION_POLICY_HOST_NOT_LIVE" xml:space="preserve">
<value>Pool master unreachable</value>
</data>
<data name="VM_PROTECTION_POLICY_SUCCEEDED" xml:space="preserve">
<value>Succeeded</value>
</data>
2015-02-19 15:09:08 +01:00
<data name="VM_READ_CACHING_DISABLED" xml:space="preserve">
2015-03-16 20:54:55 +01:00
<value>This VM is not using read caching</value>
2015-02-19 15:09:08 +01:00
</data>
<data name="VM_READ_CACHING_DISABLED_REASON_LICENSE" xml:space="preserve">
2015-03-16 20:54:55 +01:00
<value>This pool is not licensed for read caching</value>
</data>
<data name="VM_READ_CACHING_DISABLED_REASON_NO_RO_IMAGE" xml:space="preserve">
<value>This VM does not have any read-only disks or disks with a read-only parent</value>
</data>
<data name="VM_READ_CACHING_DISABLED_REASON_PREV_LICENSE" xml:space="preserve">
<value>This pool was not licensed for read caching when the VM was started</value>
2015-02-19 15:09:08 +01:00
</data>
<data name="VM_READ_CACHING_DISABLED_REASON_SR_TYPE" xml:space="preserve">
2015-03-16 20:54:55 +01:00
<value>Read caching is not supported on the type of Storage Repository used by this VM</value>
2015-02-19 15:09:08 +01:00
</data>
<data name="VM_READ_CACHING_DISABLED_REASON_TURNED_OFF" xml:space="preserve">
2015-03-16 20:54:55 +01:00
<value>Read caching has been disabled on the Storage Repository used by this VM</value>
2015-02-19 15:09:08 +01:00
</data>
2015-05-27 18:40:51 +02:00
<data name="VM_READ_CACHING_DISABLED_SEARCH" xml:space="preserve">
<value>Not using read caching</value>
</data>
2015-03-09 16:32:07 +01:00
<data name="VM_READ_CACHING_ENABLED" xml:space="preserve">
2015-03-16 20:54:55 +01:00
<value>This VM is using read caching</value>
2015-03-09 16:32:07 +01:00
</data>
<data name="VM_READ_CACHING_ENABLED_SEARCH" xml:space="preserve">
<value>Using read caching</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VM_REVERTED" xml:space="preserve">
<value>VM reverted to '{0}'</value>
</data>
<data name="VM_REVERTING" xml:space="preserve">
<value>VM reverting to '{0}'</value>
</data>
<data name="VM_REVERTING_ELLIPSIS" xml:space="preserve">
<value>VM reverting...</value>
</data>
<data name="VM_RUNNING_CHECK_DESCRIPTION" xml:space="preserve">
<value>{0}: Running VM check</value>
</data>
<data name="VM_SHUT_DOWN" xml:space="preserve">
<value>This VM is shut down.</value>
</data>
2017-01-10 07:18:18 +01:00
<data name="VM_SNAPSHOT_SCHEDULE_FAILED" xml:space="preserve">
<value>{0} ({1} VMs failed)</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VM_SUCCESSFULLY_CREATED" xml:space="preserve">
<value>VM successfully created</value>
</data>
<data name="VM_SUSPENDED" xml:space="preserve">
<value>This VM is suspended.</value>
</data>
<data name="VM_USES_LOCAL_STORAGE" xml:space="preserve">
<value>This VM uses local storage</value>
</data>
2016-10-10 13:37:11 +02:00
<data name="VM_VCPU_CANNOT_UNPLUG_LIVE" xml:space="preserve">
<value>The current number of vCPUs is already {0} and cannot be decreased while the VM is running.</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VM_VCPU_CHANGES_NOT_SUPPORTED_MESSAGE" xml:space="preserve">
2013-11-14 12:58:43 +01:00
<value>vCPU changes will take effect when you restart the VM.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="VM_X" xml:space="preserve">
<value>VM '{0}'</value>
</data>
<data name="VNC_COULD_NOT_CONNECT_CONSOLE" xml:space="preserve">
<value>Could not connect to console</value>
</data>
<data name="VNC_COULD_NOT_FIND_CONSOLES" xml:space="preserve">
<value>Could not find any consoles</value>
</data>
<data name="VNC_DEFAULT_DESKTOP" xml:space="preserve">
<value>Sw&itch to Default Desktop</value>
</data>
<data name="VNC_DOCK_ALT_SHIFT_U" xml:space="preserve">
<value> (Alt+Shift+U)</value>
</data>
<data name="VNC_DOCK_F11" xml:space="preserve">
<value> (F11)</value>
</data>
<data name="VNC_FULLSCREEN_CTRL_ALT" xml:space="preserve">
<value>Fulls&creen (Ctrl+Alt)</value>
</data>
<data name="VNC_FULLSCREEN_CTRL_ALT_F" xml:space="preserve">
<value>Fulls&creen (Ctrl+Alt+F)</value>
</data>
<data name="VNC_FULLSCREEN_CTRL_ENTER" xml:space="preserve">
<value>Fulls&creen (Ctrl+Enter)</value>
</data>
<data name="VNC_FULLSCREEN_F12" xml:space="preserve">
<value>Fulls&creen (F12)</value>
</data>
<data name="VNC_FULLSCREEN_MESSAGE_CTRL_ALT" xml:space="preserve">
<value>Press Ctrl+Alt to exit full screen mode</value>
</data>
<data name="VNC_FULLSCREEN_MESSAGE_CTRL_ALT_F" xml:space="preserve">
<value>Press Ctrl+Alt+F to exit full screen mode</value>
</data>
<data name="VNC_FULLSCREEN_MESSAGE_CTRL_ENTER" xml:space="preserve">
<value>Press Ctrl+Enter to exit full screen mode</value>
</data>
<data name="VNC_FULLSCREEN_MESSAGE_F12" xml:space="preserve">
<value>Press F12 to exit full screen mode</value>
</data>
<data name="VNC_HOST_GONE" xml:space="preserve">
<value>Server has disappeared.</value>
</data>
<data name="VNC_LOOKING" xml:space="preserve">
<value>Looking for guest console...</value>
</data>
<data name="VNC_RDESKTOP" xml:space="preserve">
<value>Sw&itch to Remote Desktop</value>
</data>
2015-01-09 04:24:26 +01:00
<data name="VNC_RDESKTOP_TURN_ON" xml:space="preserve">
2014-12-04 09:35:36 +01:00
<value>Turn &on Remote Desktop</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="VNC_REDOCK" xml:space="preserve">
<value>&Redock</value>
</data>
<data name="VNC_UNDOCK" xml:space="preserve">
<value>&Undock</value>
</data>
<data name="VNC_VIRTUAL_CONSOLE" xml:space="preserve">
<value>Sw&itch to Text Console</value>
</data>
<data name="VNC_X_CONSOLE" xml:space="preserve">
<value>Sw&itch to Graphical Console</value>
</data>
<data name="VOLUMES" xml:space="preserve">
<value>Volumes</value>
</data>
<data name="WAITING" xml:space="preserve">
<value>Waiting</value>
</data>
<data name="WAITING_FOR_USER" xml:space="preserve">
<value>Waiting for user...</value>
</data>
<data name="WAKE_ON_LAN" xml:space="preserve">
<value>Wake-on-LAN</value>
</data>
<data name="WARNING" xml:space="preserve">
<value>Warning</value>
</data>
<data name="WARNING_DELETE_ISO" xml:space="preserve">
<value>This will delete this ISO permanently, destroying any data on it.</value>
</data>
<data name="WARNING_DELETE_ISO_MULTIPLE" xml:space="preserve">
<value>This will delete these ISOs permanently, destroying any data on them.</value>
</data>
<data name="WARNING_DELETE_SNAPSHOT" xml:space="preserve">
<value>Deleting a single snapshot disk is not allowed. This action will delete the entire snapshot, and any other disks attached.</value>
</data>
<data name="WARNING_DELETE_SNAPSHOT_MULTIPLE" xml:space="preserve">
<value>Deleting a single snapshot disk is not allowed. This will delete the entire snapshot each disk belongs to, and any other disks attached.</value>
</data>
<data name="WARNING_DELETE_SYS_DISK" xml:space="preserve">
<value>This will delete this system disk permanently, possibly leaving the VM unable to boot.</value>
</data>
<data name="WARNING_DELETE_SYS_DISK_MULTIPLE" xml:space="preserve">
<value>This will delete these system disks permanently, possibly leaving their VMs unable to boot.</value>
</data>
<data name="WARNING_DELETE_VD" xml:space="preserve">
<value>This will delete this virtual disk permanently, destroying any data on it.</value>
</data>
<data name="WARNING_DELETE_VD_MULTIPLE" xml:space="preserve">
<value>This will delete these virtual disks permanently, destroying any data on them.</value>
</data>
2013-12-05 13:46:39 +01:00
<data name="WEB_PAGE" xml:space="preserve">
<value>Web Page</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="WEDNESDAY_LONG" xml:space="preserve">
<value>Wednesday</value>
</data>
<data name="WEDNESDAY_SHORT" xml:space="preserve">
<value>Wed</value>
</data>
<data name="WEEKLY_SCHEDULE_FORMAT" xml:space="preserve">
<value>Weekly; at {0} every {1}</value>
</data>
2015-12-17 12:05:22 +01:00
<data name="WINDOWS_UPDATE_CAPABLE" xml:space="preserve">
<value>Windows Update capable</value>
</data>
<data name="WINDOWS_UPDATE_CAPABLE_NOT" xml:space="preserve">
<value>Not Windows Update capable</value>
</data>
2013-06-24 13:41:48 +02:00
<data name="WIZARD_BUTTON_NEXT" xml:space="preserve">
<value>&Next ></value>
</data>
<data name="WIZARD_DESC_NETWORK_SETTINGS_EXTERNAL" xml:space="preserve">
<value>Your new network will be mapped to an existing physical network interface and assigned a VLAN number to use on that interface. You can select the physical interface you would like to use below.</value>
</data>
<data name="WIZARD_DESC_NETWORK_SETTINGS_INTERNAL" xml:space="preserve">
<value>Check the box below if you would like to automatically add this network to new VMs.</value>
</data>
<data name="WIZARD_INTERNAL_ERROR" xml:space="preserve">
<value>There was an internal error completing this wizard. Please see the logs for more information.</value>
</data>
<data name="WIZARD_TEXT_IMPORT_OVF" xml:space="preserve">
<value>Import OVF/OVA Package</value>
</data>
<data name="WIZARD_TEXT_IMPORT_VHD" xml:space="preserve">
<value>Import Disk Image</value>
</data>
<data name="WIZARD_TEXT_IMPORT_XVA" xml:space="preserve">
<value>Import XVA</value>
</data>
<data name="WLB" xml:space="preserve">
<value>Workload Balancing</value>
</data>
<data name="WLBREPORT_EXPORT_SUCC" xml:space="preserve">
<value>Report exported successfully</value>
</data>
<data name="WLBREPORT_HOST_HEALTH_HISTORY" xml:space="preserve">
<value>Host Health History</value>
</data>
<data name="WLBREPORT_OPTIMIZATION_PERFORMANCE_HISTORY" xml:space="preserve">
<value>Optimization Performance History</value>
</data>
<data name="WLBREPORT_POOL_AUDIT_HISTORY" xml:space="preserve">
<value>Pool Audit Log History</value>
</data>
<data name="WLBREPORT_POOL_CONNECTION_LOST_CAPTION" xml:space="preserve">
<value>Pool Connection Lost</value>
</data>
<data name="WLBREPORT_POOL_HEALTH" xml:space="preserve">
<value>Pool Health</value>
</data>
<data name="WLBREPORT_POOL_HEALTH_HISTORY" xml:space="preserve">
<value>Pool Health History</value>
</data>
<data name="WLBREPORT_POOL_OPTIMIZATION_HISTORY" xml:space="preserve">
<value>Pool Optimization History</value>
</data>
<data name="WLBREPORT_REPORT_CONFIG_ERROR" xml:space="preserve">
<value>An error occurred when attempting to open the Workload Balancing report window. Please check the report configuration file.</value>
</data>
<data name="WLBREPORT_VM_MOTION_HISTORY" xml:space="preserve">
<value>Virtual Machine Motion History</value>
</data>
<data name="WLBREPORT_VM_MOVEMENT_HISTORY" xml:space="preserve">
<value>Virtual Machine Motion History</value>
</data>
<data name="WLBREPORT_VM_PERFORMANCE_HISTORY" xml:space="preserve">
<value>Virtual Machine Performance History</value>
</data>
<data name="WLB_ADVANCED_CONFIGURATION" xml:space="preserve">
<value>Advanced</value>
</data>
<data name="WLB_ADVANCED_CONFIGURATION_SUBTEXT" xml:space="preserve">
<value />
</data>
2014-07-16 09:06:23 +02:00
<data name="WLB_AUDIT_LOG_MAXIMUM" xml:space="preserve">
<value>Maximum</value>
</data>
2014-08-06 14:46:53 +02:00
<data name="WLB_AUDIT_LOG_MEDIUM" xml:space="preserve">
<value>Medium</value>
</data>
2014-07-16 09:06:23 +02:00
<data name="WLB_AUDIT_LOG_MINIMUM" xml:space="preserve">
<value>Minimum</value>
</data>
2014-08-06 14:46:53 +02:00
<data name="WLB_AUDIT_LOG_USER_OBJECT_ALL" xml:space="preserve">
<value>ALL</value>
2014-07-16 09:06:23 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="WLB_AUTOMATION" xml:space="preserve">
<value>Automation</value>
</data>
<data name="WLB_AUTOMATION_SUBTEXT" xml:space="preserve">
<value>Configure WLB Automation</value>
</data>
<data name="WLB_AUTO_OPT" xml:space="preserve">
<value>Automated optimizations</value>
</data>
<data name="WLB_CONFIGURATION_DIALOG" xml:space="preserve">
<value>Workload Balancing Configuration for {0}</value>
</data>
<data name="WLB_CONNECT" xml:space="preserve">
<value>&Connect...</value>
</data>
<data name="WLB_CONNECTION_ERROR_BLURB" xml:space="preserve">
<value>There was an error communicating with the Workload Balancing server.
Click Reconnect... to update the connection settings.</value>
</data>
<data name="WLB_CONNECTION_ERROR_BLURB_NO_PRIV" xml:space="preserve">
<value>There was an error communicating with the Workload Balancing server:
A {0} user cannot alter the Workload Balancing settings.</value>
</data>
<data name="WLB_CONTROLLING_HOME_SERVER" xml:space="preserve">
<value>Workload Balancing is in control of VM placement.</value>
</data>
<data name="WLB_DAY_ALL" xml:space="preserve">
<value>Every Day</value>
</data>
<data name="WLB_DAY_WEEKDAYS" xml:space="preserve">
<value>Weekdays</value>
</data>
<data name="WLB_DAY_WEEKENDS" xml:space="preserve">
<value>Weekends</value>
</data>
<data name="WLB_DISABLED" xml:space="preserve">
<value>Disabled</value>
</data>
<data name="WLB_DISABLE_QUERY" xml:space="preserve">
<value>Are you sure you want to disable Workload Balancing for pool '{0}'?</value>
</data>
<data name="WLB_ENABLED" xml:space="preserve">
<value>Enabled</value>
</data>
<data name="WLB_ENABLED_BLURB" xml:space="preserve">
<value>Workload Balancing is currently analyzing pool {0} for possible optimizations.</value>
</data>
<data name="WLB_ENABLE_WLB_BLURB" xml:space="preserve">
<value>Workload Balancing is currently paused for pool {0}.
Click Resume to continue analyzing the pool for possible optimizations.</value>
</data>
<data name="WLB_ENABLE_WLB_BLURB_NO_PRIV" xml:space="preserve">
<value>Workload Balancing is currently paused for pool {0}.
A {1} user cannot alter the Workload Balancing settings.</value>
</data>
<data name="WLB_ERROR_4000" xml:space="preserve">
<value>WLB unknown error.</value>
</data>
<data name="WLB_ERROR_4001" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>An error occurd when WLB establish a session with [XenServer].</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_ERROR_4002" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>WLB could not log into [XenServer]. It could be due to invalid credentials.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_ERROR_4003" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>WLB cannot connect to [XenServer]. It could be the [XenServer] being offline or an incorrect TCP/IP address.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_ERROR_4004" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>WLB received a null argument from [XenServer], which is not allowed.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_ERROR_4005" xml:space="preserve">
<value>WLB registry key is missing.</value>
</data>
<data name="WLB_ERROR_4007" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>WLB received an invalid argument from [XenServer].</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_ERROR_4008" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>WLB data collection service cannot retrieve [XenServer] data.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_ERROR_4009" xml:space="preserve">
<value>WLB configuration data is missing in WLB database.</value>
</data>
<data name="WLB_ERROR_4010" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>WLB received an invalid operation from [XenServer].</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_ERROR_4011" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>WLB received an out of range argument from [XenServer].</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_ERROR_4012" xml:space="preserve">
<value>WLB data collection service is not properly initialized.</value>
</data>
<data name="WLB_ERROR_4013" xml:space="preserve">
<value>WLB data collection service cannot migrate or start VMs.</value>
</data>
<data name="WLB_ERROR_4014" xml:space="preserve">
<value>WLB received an unknown execption.</value>
</data>
<data name="WLB_ERROR_4015" xml:space="preserve">
<value>WLB does not know this pool.</value>
</data>
<data name="WLB_ERROR_4016" xml:space="preserve">
<value>WLB does not have current metrics.</value>
</data>
<data name="WLB_ERROR_4017" xml:space="preserve">
<value>WLB can't find a host that has required storage repositories to place a VM. </value>
</data>
<data name="WLB_ERROR_4018" xml:space="preserve">
<value>WLB can't find required free CPUs to place a VM.</value>
</data>
<data name="WLB_ERROR_4019" xml:space="preserve">
<value>WLB can't find required free memory to place a VM.</value>
</data>
<data name="WLB_ERROR_4020" xml:space="preserve">
<value>One or more hosts in the pool do not have an appropriate license.</value>
</data>
<data name="WLB_ERROR_4021" xml:space="preserve">
2016-11-17 13:01:22 +01:00
<value>WLB could not connect to [XenServer] because the supplied credentials were invalid.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_ERROR_4022" xml:space="preserve">
<value>WLB unable to evacuate an explicitly excluded host.</value>
</data>
<data name="WLB_ERROR_4023" xml:space="preserve">
<value>WLB cannot save your configuration at this time. Verify all Workload Balancing services are running, and try reentering your configuration in a few minutes.</value>
</data>
<data name="WLB_ERROR_5" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] cannot connect to the WLB Server with the supplied WLB Server credentials.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_ERROR_6" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>The user WLB uses to connect to [XenServer] either doesn't have sufficient privileges or doesn't have access to [XenServer]. Please re-initialize WLB with an valid user.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_ERROR_SERVER_NOT_FOUND" xml:space="preserve">
<value>The specified WLB Server could not be found. Please check your settings.</value>
</data>
<data name="WLB_HOST_EXCLUSION" xml:space="preserve">
<value>Excluded Hosts</value>
</data>
<data name="WLB_HOST_SERVER" xml:space="preserve">
<value>Host Server</value>
</data>
<data name="WLB_INITIALIZE_WLB_BLURB" xml:space="preserve">
<value>This pool ({0}) is not currently connected to a Workload Balancing (WLB) server.
Click Connect... to begin using Workload Balancing to optimize your pool.</value>
</data>
<data name="WLB_INITIALIZE_WLB_BLURB_NO_PRIV" xml:space="preserve">
<value>This pool ({0}) is not currently connected to a Workload Balancing (WLB) server.
A {1} user cannot alter the Workload Balancing settings.</value>
</data>
<data name="WLB_LAST_POWERON_SUCCEEDED" xml:space="preserve">
<value>Last PowerOn Succeeded</value>
</data>
<data name="WLB_LICENSE_DISABLED" xml:space="preserve">
<value>The server does not have a license permitting Workload Balancing.</value>
</data>
<data name="WLB_METRIC_WEIGHTING" xml:space="preserve">
<value>Metric Weighting</value>
</data>
<data name="WLB_METRIC_WEIGHTING_SUBTEXT" xml:space="preserve">
<value>Adjust the weighting of WLB metrics</value>
</data>
<data name="WLB_NEXT_OPT_MODE_SCHEDULE_FORMAT" xml:space="preserve">
<value>{0} at {1}</value>
</data>
<data name="WLB_NEXT_OPT_MODE_SCHEDULE_TEXT" xml:space="preserve">
<value>Next scheduled mode change</value>
</data>
<data name="WLB_NOT_CONFIGURED" xml:space="preserve">
<value>Not configured for pool '{0}'</value>
</data>
<data name="WLB_NO_PERMISSION_BLURB" xml:space="preserve">
<value>A {0} user cannot alter the Workload Balancing settings. </value>
</data>
<data name="WLB_OPTIMIZATION_MODE" xml:space="preserve">
<value>Optimization Mode</value>
</data>
<data name="WLB_OPTIMIZATION_MODE_SUBTEXT" xml:space="preserve">
<value>Adjust the WLB optimization mode</value>
</data>
<data name="WLB_OPTIMIZING_POOL" xml:space="preserve">
<value>Optimizing pool {0}</value>
</data>
<data name="WLB_OPT_APPLY_RECOMMENDATIONS" xml:space="preserve">
<value>Apply Recommendations</value>
</data>
<data name="WLB_OPT_FAILED" xml:space="preserve">
<value>Failed</value>
</data>
<data name="WLB_OPT_HEADER_VM" xml:space="preserve">
<value>VM</value>
</data>
<data name="WLB_OPT_HEADER_VMHOST" xml:space="preserve">
<value>VM/Host</value>
</data>
<data name="WLB_OPT_LOADING_ERROR" xml:space="preserve">
<value>There was an internal error occurred loading pool optimizations. Please see the logs for more information.</value>
</data>
<data name="WLB_OPT_MENU_OPTIMAL_SERVER" xml:space="preserve">
<value>&Optimal Server</value>
</data>
<data name="WLB_OPT_MODE" xml:space="preserve">
<value>Pool optimization mode</value>
</data>
<data name="WLB_OPT_MODE_BLURB" xml:space="preserve">
<value>Specify the optimization mode to use when placing VMs in this pool.</value>
</data>
<data name="WLB_OPT_MODE_DENSITY_BLURB" xml:space="preserve">
<value>Place the largest possible number of VMs on each server </value>
</data>
<data name="WLB_OPT_MODE_MAXIMIZEDENSITY" xml:space="preserve">
<value>Maximize Density</value>
</data>
<data name="WLB_OPT_MODE_MAXIMIZEPERFORMANCE" xml:space="preserve">
<value>Maximize Performance</value>
</data>
<data name="WLB_OPT_MODE_PERF_BLURB" xml:space="preserve">
<value>Guarantee performance metrics for placed VMs </value>
</data>
<data name="WLB_OPT_OK_NOTICE_TEXT" xml:space="preserve">
<value>Optimized successfully.</value>
</data>
<data name="WLB_OPT_OPERATION_HOST_POWEROFF" xml:space="preserve">
<value>Power off</value>
</data>
<data name="WLB_OPT_OPERATION_HOST_POWERON" xml:space="preserve">
<value>Power on</value>
</data>
<data name="WLB_OPT_OPERATION_VM" xml:space="preserve">
<value>Relocate from '{0}' to '{1}'</value>
</data>
<data name="WLB_OPT_OPTIMIZING" xml:space="preserve">
<value>Optimizing ...</value>
</data>
<data name="WLB_OPT_POOL_NOT_ENOUGH_MEMORY" xml:space="preserve">
<value>There is not enough free memory available on the other servers in the pool to finish optimizing pool.</value>
</data>
<data name="WLB_OPT_POOL_NO_RECOMMENDATION" xml:space="preserve">
<value>No recommendations at this time.</value>
</data>
<data name="WLB_OPT_REASON_CONSOLIDATE" xml:space="preserve">
<value>Consolidation</value>
</data>
<data name="WLB_OPT_REASON_CPU" xml:space="preserve">
<value>CPU</value>
</data>
<data name="WLB_OPT_REASON_DISK" xml:space="preserve">
<value>Disk</value>
</data>
<data name="WLB_OPT_REASON_DISKREAD" xml:space="preserve">
<value>Disk Reads</value>
</data>
<data name="WLB_OPT_REASON_DISKWRITE" xml:space="preserve">
<value>Disk Writes</value>
</data>
<data name="WLB_OPT_REASON_LOADAVERAGE" xml:space="preserve">
<value>Load Average</value>
</data>
<data name="WLB_OPT_REASON_MEMORY" xml:space="preserve">
<value>Memory</value>
</data>
<data name="WLB_OPT_REASON_NETWORK" xml:space="preserve">
<value>Network</value>
</data>
<data name="WLB_OPT_REASON_NETWORKREAD" xml:space="preserve">
<value>Network Reads</value>
</data>
<data name="WLB_OPT_REASON_NETWORKWRITE" xml:space="preserve">
<value>Network Writes</value>
</data>
<data name="WLB_OPT_REASON_NONE" xml:space="preserve">
<value>None</value>
</data>
<data name="WLB_OPT_REASON_POWEROFF" xml:space="preserve">
<value>Release Resource</value>
</data>
<data name="WLB_OPT_REASON_POWERON" xml:space="preserve">
<value>Resource required</value>
</data>
<data name="WLB_PLEASE_WAIT" xml:space="preserve">
<value>Please wait...</value>
</data>
<data name="WLB_POWERMANAGEMENT" xml:space="preserve">
<value>Power Management</value>
</data>
<data name="WLB_POWERMANAGEMENT_SUBTEXT" xml:space="preserve">
<value>Configure WLB Power Management</value>
</data>
<data name="WLB_POWERON_MODE" xml:space="preserve">
<value>PowerOn Mode</value>
</data>
<data name="WLB_PROMPT_FOR_MODE_CHANGE_BLURB" xml:space="preserve">
<value>The Optimization Mode is scheduled to be {0}, but it currently set to {1}.
Would you like to adjust the current Optimization Mode to match the schedule?</value>
</data>
<data name="WLB_PROMPT_FOR_MODE_CHANGE_CAPTION" xml:space="preserve">
<value>Apply Optimization Mode Schedule</value>
</data>
<data name="WLB_PWR_MGT" xml:space="preserve">
<value>Power management</value>
</data>
<data name="WLB_RECONFIGURE" xml:space="preserve">
<value>Configuration Error: {0}</value>
</data>
<data name="WLB_RECONFIGURE_CREDS" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>The stored [XenServer] credentials are no longer valid. Please update the connection settings for Workload Balancing.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="WLB_RECONNECT" xml:space="preserve">
<value>Re&connect...</value>
</data>
<data name="WLB_REPORT_BACKMENUITEMTEXT" xml:space="preserve">
<value>Back to Parent Report</value>
</data>
<data name="WLB_REPORT_BACKTOPARENTREPORT" xml:space="preserve">
<value>Back to Parent Report</value>
</data>
<data name="WLB_REPORT_BIND_DATASOURCE" xml:space="preserve">
<value>An error occurred when attempting to bind report datasources: {0}</value>
</data>
<data name="WLB_REPORT_CHANGECREDENTIALSTEXT" xml:space="preserve">
<value>Change Credentials</value>
</data>
<data name="WLB_REPORT_CURRENTPAGETEXTBOXTOOLTIP" xml:space="preserve">
<value>Current Page</value>
</data>
<data name="WLB_REPORT_DATE_ORDERING_CAPTION" xml:space="preserve">
<value>Date Ordering</value>
</data>
<data name="WLB_REPORT_DATE_ORDERING_MESSAGE" xml:space="preserve">
<value>Please select an End Date that is greater than, or equal to, the Start Date</value>
</data>
<data name="WLB_REPORT_DEFINITIONS" xml:space="preserve">
<value>definitions</value>
</data>
<data name="WLB_REPORT_DELETE_SUBSCRIPTION_QUERY" xml:space="preserve">
<value>Are you sure you want to unsubscribe report '{0}'?</value>
</data>
<data name="WLB_REPORT_DELETE_SUBSCRIPTION_TITLE" xml:space="preserve">
<value>Delete Report Subscription</value>
</data>
<data name="WLB_REPORT_DOCUMENTMAP" xml:space="preserve">
<value>Show or Hide Document Map</value>
</data>
<data name="WLB_REPORT_ERROR_LOCALIZED_PARAMS" xml:space="preserve">
<value>Unable to generate localized report label parameters: {0}</value>
</data>
<data name="WLB_REPORT_EVERYDAY" xml:space="preserve">
<value>Everyday</value>
</data>
<data name="WLB_REPORT_EXPORT" xml:space="preserve">
<value>Export</value>
</data>
<data name="WLB_REPORT_EXPORTING" xml:space="preserve">
<value>Exporting to {0}</value>
</data>
<data name="WLB_REPORT_FALSEVALUETEXT" xml:space="preserve">
<value>Invalid Value</value>
</data>
<data name="WLB_REPORT_FIND" xml:space="preserve">
<value>Find</value>
</data>
<data name="WLB_REPORT_FINDNEXT" xml:space="preserve">
<value>Find Next</value>
</data>
<data name="WLB_REPORT_FIRSTPAGE" xml:space="preserve">
<value>First Page</value>
</data>
<data name="WLB_REPORT_HTTP_403" xml:space="preserve">
<value>The WLB Server was unable to process the report. Try refining your filter criteria to a smaller date range and try again.</value>
</data>
<data name="WLB_REPORT_HTTP_500" xml:space="preserve">
<value>The WLB Server did not respond to the report request.</value>
</data>
<data name="WLB_REPORT_LASTMONTH" xml:space="preserve">
<value>Last month</value>
</data>
<data name="WLB_REPORT_LASTPAGE" xml:space="preserve">
<value>Last Page</value>
</data>
<data name="WLB_REPORT_LASTWEEK" xml:space="preserve">
<value>Last week</value>
</data>
<data name="WLB_REPORT_LASTWEEKS" xml:space="preserve">
<value>Last {0} weeks</value>
</data>
<data name="WLB_REPORT_NEVER" xml:space="preserve">
<value>Never</value>
</data>
<data name="WLB_REPORT_NEXT" xml:space="preserve">
<value>Next</value>
</data>
<data name="WLB_REPORT_NEXTPAGE" xml:space="preserve">
<value>Next Page</value>
</data>
<data name="WLB_REPORT_NOMOREMATCHES" xml:space="preserve">
<value>No More Matches</value>
</data>
<data name="WLB_REPORT_PAGEOF" xml:space="preserve">
<value>of</value>
</data>
<data name="WLB_REPORT_PAGESETUP" xml:space="preserve">
<value>Page Setup</value>
</data>
<data name="WLB_REPORT_PAGEWIDTH" xml:space="preserve">
<value>Page Width</value>
</data>
<data name="WLB_REPORT_PARAMETERS" xml:space="preserve">
<value>Parameters</value>
</data>
<data name="WLB_REPORT_PASSWORDPROMPT" xml:space="preserve">
<value>Please enter your password</value>
</data>
<data name="WLB_REPORT_POOL_CONNECTION_LOST" xml:space="preserve">
<value>No longer connected to pool "{0}". Please reconnect to the pool and try again.</value>
</data>
<data name="WLB_REPORT_POOL_HEALTH" xml:space="preserve">
<value>Pool Health</value>
</data>
<data name="WLB_REPORT_PREVIOUSPAGE" xml:space="preserve">
<value>Previous Page</value>
</data>
<data name="WLB_REPORT_PRINT" xml:space="preserve">
<value>Print</value>
</data>
<data name="WLB_REPORT_PRINTLAYOUT" xml:space="preserve">
<value>Print Layout</value>
</data>
<data name="WLB_REPORT_PROCESSING" xml:space="preserve">
<value>Processing Please Wait</value>
</data>
<data name="WLB_REPORT_REFRESH" xml:space="preserve">
<value>Refresh</value>
</data>
<data name="WLB_REPORT_REMOTE_QUERY" xml:space="preserve">
<value>An error occurred when attempting to execute the remote query: {0}</value>
</data>
<data name="WLB_REPORT_SEARCH" xml:space="preserve">
<value>Search</value>
</data>
<data name="WLB_REPORT_SELECT" xml:space="preserve">
<value>Select</value>
</data>
<data name="WLB_REPORT_SELECTALL" xml:space="preserve">
<value>Select All</value>
</data>
<data name="WLB_REPORT_SET_PARAMS" xml:space="preserve">
<value>An error occurred when attempting to set report parameters: {0}</value>
</data>
<data name="WLB_REPORT_START" xml:space="preserve">
<value>Start</value>
</data>
<data name="WLB_REPORT_STOPRENDERING" xml:space="preserve">
<value>Stop Rendering</value>
</data>
<data name="WLB_REPORT_TEXTNOTFOUND" xml:space="preserve">
<value>Text not found</value>
</data>
<data name="WLB_REPORT_TOTALPAGES" xml:space="preserve">
<value>Total pages</value>
</data>
<data name="WLB_REPORT_USERNAME" xml:space="preserve">
<value>User name</value>
</data>
<data name="WLB_REPORT_VIEWREPORT" xml:space="preserve">
<value>View Report</value>
</data>
<data name="WLB_REPORT_VIEW_ALL" xml:space="preserve">
<value>View All</value>
</data>
<data name="WLB_REPORT_VIEW_BASIC" xml:space="preserve">
<value>Basic View</value>
</data>
<data name="WLB_REPORT_VIEW_CUSTOM" xml:space="preserve">
<value>Custom View</value>
</data>
<data name="WLB_REPORT_VIEW_TAG_COLUMN_HEADER" xml:space="preserve">
<value>Filter Item</value>
</data>
<data name="WLB_REPORT_VIEW_VERBOSE" xml:space="preserve">
<value>Verbose View</value>
</data>
<data name="WLB_REPORT_WHOLEPAGE" xml:space="preserve">
<value>Whole Page</value>
</data>
<data name="WLB_REPORT_ZOOM" xml:space="preserve">
<value>Zoom</value>
</data>
<data name="WLB_RETRIEVING_CONFIGURATION" xml:space="preserve">
<value>Retrieving WLB Configuration</value>
</data>
<data name="WLB_SAVING_SETTINGS" xml:space="preserve">
<value>Saving Workload Balancing settings</value>
</data>
<data name="WLB_SCHEDULED_OPT_MODE" xml:space="preserve">
<value>{0} (Scheduled)</value>
</data>
<data name="WLB_SERVER_CREDENTIALS" xml:space="preserve">
<value>Server Credentials</value>
</data>
<data name="WLB_SERVER_CREDENTIALS_SUBTEXT" xml:space="preserve">
<value>Update the credentials used for WLB communications</value>
</data>
<data name="WLB_SERVER_URL" xml:space="preserve">
<value>Workload Balancing server name</value>
</data>
<data name="WLB_SEVERITY_CRITICAL" xml:space="preserve">
<value>Critical</value>
</data>
<data name="WLB_SEVERITY_HIGH" xml:space="preserve">
<value>High</value>
</data>
<data name="WLB_SEVERITY_LOW" xml:space="preserve">
<value>Low</value>
</data>
<data name="WLB_SEVERITY_MEDIUM" xml:space="preserve">
<value>Medium</value>
</data>
<data name="WLB_SQLEXPRESS_GROOMING_BLURB" xml:space="preserve">
<value>Workload Balancing adjusts grooming history automatically for SQL Server Express databases.</value>
</data>
<data name="WLB_STATUS" xml:space="preserve">
<value>Workload Balancing status</value>
</data>
<data name="WLB_SUBSCRIPTIONS" xml:space="preserve">
<value>Subscriptions</value>
</data>
<data name="WLB_SUBSCRIPTION_BCC" xml:space="preserve">
<value>Bcc</value>
</data>
<data name="WLB_SUBSCRIPTION_CC" xml:space="preserve">
<value>Cc</value>
</data>
<data name="WLB_SUBSCRIPTION_COMMENT" xml:space="preserve">
<value>Comment</value>
</data>
<data name="WLB_SUBSCRIPTION_DATARANGE" xml:space="preserve">
<value>Data Range</value>
</data>
<data name="WLB_SUBSCRIPTION_DELIVERON" xml:space="preserve">
<value>Deliver On</value>
</data>
<data name="WLB_SUBSCRIPTION_EDITED_BY" xml:space="preserve">
<value>Edited By</value>
</data>
<data name="WLB_SUBSCRIPTION_EDITED_ON" xml:space="preserve">
<value>Edited On</value>
</data>
<data name="WLB_SUBSCRIPTION_ENDING" xml:space="preserve">
<value>Ending</value>
</data>
<data name="WLB_SUBSCRIPTION_ERROR" xml:space="preserve">
<value>An error occurred while saving subscription: {0}</value>
</data>
<data name="WLB_SUBSCRIPTION_FORMAT" xml:space="preserve">
<value>Format</value>
</data>
<data name="WLB_SUBSCRIPTION_LASTSENT" xml:space="preserve">
<value>Last Sent</value>
</data>
<data name="WLB_SUBSCRIPTION_LASTSENT_TIME" xml:space="preserve">
<value>{0} at {1}</value>
</data>
<data name="WLB_SUBSCRIPTION_REPLYTO" xml:space="preserve">
<value>Reply-To</value>
</data>
<data name="WLB_SUBSCRIPTION_RUNAT" xml:space="preserve">
<value>Run At</value>
</data>
<data name="WLB_SUBSCRIPTION_STARTING" xml:space="preserve">
<value>Starting</value>
</data>
<data name="WLB_SUBSCRIPTION_SUBJECT" xml:space="preserve">
<value>Subject</value>
</data>
<data name="WLB_SUBSCRIPTION_TO" xml:space="preserve">
<value>To</value>
</data>
<data name="WLB_TASK_SCHEDULE_CONFLICT_BLURB" xml:space="preserve">
<value>The specified schedule conflicts with an existing schedule.</value>
</data>
<data name="WLB_TASK_SCHEDULE_CONFLICT_TITLE" xml:space="preserve">
<value>Conflicting Schedule</value>
</data>
<data name="WLB_THRESHOLDS" xml:space="preserve">
<value>Critical Thresholds</value>
</data>
<data name="WLB_THRESHOLDS_SUBTEXT" xml:space="preserve">
<value>Adjust Critical thresholds for WLB metrics</value>
</data>
<data name="WLB_UNTESTED_HOST_CAPTION" xml:space="preserve">
<value>Confirm Automated Power Management</value>
</data>
<data name="WLB_UNTESTED_HOST_WARNING" xml:space="preserve">
<value>This Host has either never been remotely powered on, or failed to power on correctly in the past.
Are you sure you want to enable automated power management for this Host?</value>
</data>
<data name="WLB_WAS_DISABLED" xml:space="preserve">
<value>Workload Balancing has been paused for pool '{0}'.</value>
</data>
<data name="WORKLOAD_BALANCING" xml:space="preserve">
<value>Workload Balancing</value>
</data>
<data name="WRONG_ROLE_DESC" xml:space="preserve">
<value>You are attempting an action which requires additional privileges to those granted by your current role.</value>
</data>
<data name="XENAPPLIANCE_BAD_EXIT" xml:space="preserve">
<value>'{0}' exited with Exit Code: {1}</value>
</data>
<data name="XENAPPLIANCE_FINISHED" xml:space="preserve">
<value>'{0}' finished executing</value>
</data>
<data name="XENAPPLIANCE_FORCE_CLOSE_PROMPT" xml:space="preserve">
<value>'{0}' has not yet responded to your cancel request. Would you like to force close the process or allow it to continue to run in the background?</value>
</data>
<data name="XENAPPLIANCE_RUNNING" xml:space="preserve">
<value>Running '{0}'</value>
</data>
<data name="XENAPPLIANCE_TITLE" xml:space="preserve">
<value>Execute '{0}'</value>
</data>
<data name="XENAPPLIANCE_TOOLS" xml:space="preserve">
<value>Appliance Tools</value>
</data>
<data name="XENAPPLIANCE_WIN32" xml:space="preserve">
<value>Failed to run XenApplianceWizards executable. Please see the client log for details.</value>
</data>
<data name="XENCENTER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter]</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="XENCENTER_CONFIG_FILTER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenCenter] Settings|*.config</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="XENCENTER_NEWER_AVAILABLE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>Newer [XenCenter] Available</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="XENSEARCH_SAVED_SEARCH" xml:space="preserve">
2016-02-04 13:04:33 +01:00
<value>Saved Searches (*.{0})|*.{0}</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="XENSERVER" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer]</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="XENSERVER_6_2" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] [BRANDING_VERSION_6_2]</value>
2013-06-24 13:41:48 +02:00
</data>
2014-05-30 12:23:35 +02:00
<data name="XENSERVER_6_5" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] [BRANDING_VERSION_6_5]</value>
2014-05-30 12:23:35 +02:00
</data>
2013-06-24 13:41:48 +02:00
<data name="XENSERVER_TEMPLATES" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] Templates</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="XENSERVER_UPGRADE_REQUIRED" xml:space="preserve">
2014-05-28 17:22:31 +02:00
<value>License Upgrade Required</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="XSUPDATE" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] Update Files ({0})|{0}|All files ({1})|{1}</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="XS_BACKUP_FILES" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] Backup Files</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="XS_LICENSE_FILES" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer] License Files</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="XS_TOOLS_MESSAGE_MORE_THAN_ONE_VM" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>[XenServer product] Tools DVDs will now be inserted into the DVD drive of each of the selected VMs. Any disks currently in the drives will be ejected.
2013-06-24 13:41:48 +02:00
You will need to navigate to the Console on each of the selected VMs to complete the installation.</value>
</data>
<data name="XS_TOOLS_SR_NOT_FOUND" xml:space="preserve">
2016-02-10 12:52:30 +01:00
<value>The [XenServer product] Tools SR could not be found.</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="X_HIDDEN" xml:space="preserve">
<value>{0} (hidden)</value>
</data>
<data name="X_IS_DEPRECATED_IN_X" xml:space="preserve">
2014-05-30 12:23:35 +02:00
<value>The {0} feature was deprecated in {1} and may be unavailable in future versions</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="X_IS_REMOVED_IN_X" xml:space="preserve">
2014-05-30 12:23:35 +02:00
<value>The {0} feature is not available in {1} and later versions</value>
2013-06-24 13:41:48 +02:00
</data>
<data name="X_WITH_WARNING_X" xml:space="preserve">
<value>{0} with warning: {1}</value>
</data>
<data name="YES" xml:space="preserve">
<value>Yes</value>
</data>
<data name="YESTERDAY" xml:space="preserve">
<value>was yesterday</value>
</data>
<data name="YES_BUTTON_CAPTION" xml:space="preserve">
<value>&Yes</value>
</data>
<data name="YOU_ARE_HERE" xml:space="preserve">
2015-02-04 18:33:10 +01:00
<value>You are here</value>
</data>
2016-02-08 11:10:01 +01:00
</root>