-
-
Deploying virtual desktops to VMs using the XenDesktop Setup Wizard
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!
Using UNC names
A Universal Naming Convention (UNC) format name defines the location of files and other resources that exist on a network. UNC provides a format so that each shared resource can be identified with a unique address. UNC is supported by Windows and many network operating systems (NOSs).
With Provisioning Services, UNC format names can be used to specify the location of the OS Streaming database for all Provisioning Servers, and to specify the location of a particular vDisk.
Syntax
UNC names must conform to the \\SERVERNAME\SHARENAME syntax, where SERVERNAME is the name of the Provisioning Server and SHARENAME is the name of the shared resource.
UNC names of directories or files can also include the directory path under the share name, with the following syntax:
\\SERVERNAME\SHARENAME\DIRECTORY\FILENAME
For example, to define the folder that contains your configuration database file in the following directory:
C:\Program Files\Citrix\Provisioning Services
On the shared Provisioning Server (server1), enter:
\\server1\Provisioning Services
Note: UNC names do not require that a resource be a network share. UNC can also be used to specify a local storage for use by only a local machine.
Accessing a Remote Network Share
To access a remote network share using a UNC format name, the Stream Service must have a user account name and password on the remote system.
To use a UNC name to access a remote network share:
- On the Provisioning Server, create a user account under which the Stream Service will run. This account must have a password assigned, otherwise the Stream Service will not be able to log in correctly. Your Stream Service can share the same user account and password, or separate user accounts and passwords can be set up for each service.
- Share the vDisk and configuration database folders. In Windows Explorer, right-click on the folder, then select Properties. Click the Sharing tab, then select the Share this folder radio button. Enter or select a Share name.
- Make sure permissions are set to allow full control of all files in the vDisk folder and database folder. Click the Permissions button on the Sharing tab, or click the Security tab, then set the correct permissions.
- For the Stream Service:
- Go to Control Panel>Computer Management>Component Services, right click on the Stream Service, and select Properties.
- Click the Log On tab. Change the Log on as: setting to This Account, and set up the service to login to the user and password configured in Step 1.
- Verify that all Stream Services are restarted. The Configuration Wizard does this automatically. Stream Services can also be started from the Console or from the Control Panel.
Note: Do not use a mapped drive letter to represent the vDisk or database location directories when configuring Stream Services. The Stream Service cannot access folders using a mapped drive letter for the directory, because the mapped drives do not exist when the services start at boot time.
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.