-
Understanding the Citrix Virtual Apps and Desktops Administration Model
-
-
-
-
-
-
-
-
-
-
Add-HypHostingUnitStorage
-
-
-
-
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Add-HypHostingUnitStorage
Adds storage locations to a hosting unit.
Syntax
Add-HypHostingUnitStorage
[-StoragePath] <String>
[-StorageType <StorageType>]
[-LiteralPath] <String>
[-LoggingId <Guid>]
[<CitrixCommonParameters>]
[<CommonParameters>]
<!--NeedCopy-->
Description
Use this command to add storage locations for storing the hard disks required by the virtual machines created by the Citrix Machine Creation Service. You cannot use this command if the connection for the hosting unit is in maintenance mode.
Examples
EXAMPLE 1
The command adds a new storage location called “newStorage.storage” to the hosting unit called “MyHostingUnit”.
Add-HypHostingUnitStorage -LiteralPath XDHyp:\HostingUnits\MyHostingUnit -StoragePath 'XDHyp:\HostingUnits\MyHostingUnits\newStorage.storage'
HostingUnitUid : bcd3d649-86d1-4aa8-8ec2-d322b6a2c457
HostingUnitName : MyHostingUnit
HypervisorConnection : MyConnection
RootPath : /
RootId :
NetworkPath : /Network 0.network
NetworkId : ab47080b-ca15-771a-c8dc-6ad9650158f1
Storage : {/Local storage.storage, /newStorage.storage}
PersonalvDiskStorage : {/newStorage.storage}
VMTaggingEnabled : True
AdditionalStorage : {TemporaryStorage}
Metadata : {}
<!--NeedCopy-->
EXAMPLE 2
The command adds a new storage location called “newStorage.storage” to the current directory. The dot (.) represents the current location (not its contents).
XDHyp:\HostingUnits\MyHostingUnit>Add-HypHostingUnitStorage -LiteralPath . -StoragePath 'XDHyp:\HostingUnits\MyHostingUnits\newStorage.storage' -StorageType OSStorage
HostingUnitUid : bcd3d649-86d1-4aa8-8ec2-d322b6a2c457
HostingUnitName : MyHostingUnit
HypervisorConnection : MyConnection
RootPath : /
RootId :
NetworkPath : /Network 0.network
NetworkId : ab47080b-ca15-771a-c8dc-6ad9650158f1
Storage : {/Local storage.storage, /newStorage.storage}
PersonalvDiskStorage : {/Local storage.storage}
VMTaggingEnabled : True
AdditionalStorage : {TemporaryStorage}
Metadata : {}
<!--NeedCopy-->
EXAMPLE 3
The command adds all of the storage that is available in the hosting unit to the specified hosting unit.
XDHyp:\HostingUnits\MyHostingUnit>dir *.storage | Add-HypHostingUnitStorage -LiteralPath XDHyp:\HostingUnits\MyHostingUnit
<!--NeedCopy-->
EXAMPLE 4
The command adds a new storage location called “newStorage.storage” to the hosting unit called “MyHostingUnit”.
Add-HypHostingUnitStorage -LiteralPath XDHyp:\HostingUnits\MyHostingUnit -StoragePath 'XDHyp:\HostingUnits\MyHostingUnits\newStorage.storage' -StorageType PersonalvDiskStorage
HostingUnitUid : bcd3d649-86d1-4aa8-8ec2-d322b6a2c457
HostingUnitName : MyHostingUnit
HypervisorConnection : MyConnection
RootPath : /
RootId :
NetworkPath : /Network 0.network
NetworkId : ab47080b-ca15-771a-c8dc-6ad9650158f1
Storage : {/Local storage.storage}
PersonalvDiskStorage : {/Local storage.storage, /newStorage.storage}
VMTaggingEnabled : True
AdditionalStorage : {TemporaryStorage}
Metadata : {}
<!--NeedCopy-->
Parameters
-LiteralPath
Specifies the path to the hosting unit to which storage will be added. The path must be in one of the following formats:
<drive>:\HostingUnits\<HostingUnitName>
or <drive>:\HostingUnits{<HostingUnit Uid>}
Type: | String |
Position: | 1 |
Default value: | None |
Required: | True |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-StoragePath
Specifies the path to the storage that will be added. The path must be in one of the following formats:
<drive>:\Connections\<ConnectionName>\MyStorage.storage
or <drive>:\Connections{<Connection Uid>}\MyStorage.storage
or <drive>:\HostingUnits\<HostingUnitName>\MyStorage.storage
or <drive>:\HostingUnits{<hostingUnit Uid>}\MyStorage.storage
Type: | String |
Position: | 2 |
Default value: | None |
Required: | True |
Accept pipeline input: | True (ByValue) |
Accept wildcard characters: | False |
-StorageType
Specifies the type of storage in StoragePath. Supported storage types are:
OSStorage
PersonalvDiskStorage
TemporaryStorage
Type: | StorageType |
Accepted values: | OSStorage, PersonalvDiskStorage, TemporaryStorage |
Position: | Named |
Default value: | OSStorage |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-LoggingId
Specifies the identifier of the high-level operation this cmdlet call forms a part of. Citrix Studio and Director typically create high-level operations. PowerShell scripts can also wrap a series of cmdlet calls in a high-level operation by way of the Start-LogHighLevelOperation and Stop-LogHighLevelOperation cmdlets.
Type: | Guid |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
CitrixCommonParameters
This cmdlet supports the common Citrix parameters: -AdminAddress, -AdminClientIP, -BearerToken, -TraceParent, -TraceState and -VirtualSiteId. For more information, see about_CitrixCommonParameters.
CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.
Inputs
String
You can pipe a string that contains a path to Add-HypHostingUnitStorage (StoragePath parameter).
Outputs
Citrix.Host.Sdk.HostingUnit
Add-HypHostingUnitStorage returns an object containing the new definition of the hosting unit.
HostingUnitUid <Guid>
Specifies the unique identifier for the hosting unit.
HostingUnitName <string>
Specifies the name of the hosting unit.
HypervisorConnection <Citrix.Host.Sdk.HypervisorConnection>
Specifies the connection that the hosting unit uses to access a hypervisor.
RootId <string>
Identifies, to the hypervisor, the root of the hosting unit.
RootPath <string>
The hosting unit provider path that represents the root of the hosting unit.
Storage <Citrix.Host.Sdk.Storage[]>
The list of storage items that the hosting unit can use.
PersonalvDiskStorage <Citrix.XDPowerShell.Storage[]>
The list of storage items that the hosting unit can use for storing personal data.
VMTaggingEnabled <Boolean>
Specifies whether or not the metadata in the hypervisor can be used to store information about the XenDesktop Machine Creation Service.
NetworkId <string>
The hypervisor’s internal identifier that represents the network specified for the hosting unit.
NetworkPath <string>
The hosting unit provider path to the network specified for the hosting unit.
AdditionalStorage
The list of additional storage items that the hosting unit can use.
Metadata <Citrix.Host.Sdk.Metadata[]>
A list of key value pairs that can store additional information about the hosting unit.
Notes
The storage path must be valid for the hosting unit. The rules that are applied are as follows:
XenServer (HypervisorConnection Type = XenServer)
NA
VMWare vSphere/ESX (HypervisorConnection Type = vCenter)
The storage path must be directly contained in the root path item of the hosting unit.
Microsoft SCVMM/Hyper-v (HypervisorConnection Type = SCVMM)
Only one storage entry for these connection types is valid, and it must reference an SMB share. Additionally, if a Hyper-V failover cluster is used the SMB share must be the top-level mount point of the cluster shared volume on one of the servers in the cluster (i.e. C:\ClusterStorage).
In the case of failure, the following errors can result.
Error Codes
HostingUnitsPathInvalid
The path provided is not to an item in a subdirectory of a hosting unit item.
HostingUnitStoragePathInvalid
The specified path is invalid.
HostingUnitStoragePathInvalid
The storage path cannot be found or is invalid. See notes above about validity.
HostingUnitStorageDuplicateObjectExists
The specified storage path is already part of the hosting unit.
HypervisorInMaintenanceMode
The hypervisor for the connection is in maintenance mode.
DatabaseError
An error occurred in the service while attempting a database operation.
DatabaseNotConfigured
The operation could not be completed because the database for the service is not configured.
DataStoreException
An error occurred in the service while attempting a database operation. Communication with the database failed for
various reasons.
CommunicationError
An error occurred while communicating with the service.
PermissionDenied
The user does not have administrative rights to perform this operation.
ExceptionThrown
An unexpected error occurred. To locate more details, see the Windows event logs on the controller being used, or examine the XenDesktop logs.
Related Links
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.