-
Installing and configuring Provisioning Services
-
Upgrading a Provisioning Services target device vDisk using in-place upgrade
-
About SAN policies
-
-
Deploying virtual desktops to VMs using the XenDesktop Setup Wizard
Thank you for the feedback
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!
About SAN policies
PVS clients always failover to server side cache during boot when the vDisk mode is set to Cache in device RAM with overflow on hard disk.
Tip
An option has been removed from the Cache type field in the vDisk Properties window. The option Cache on device hard disk is no longer available from the drop down menu because it does not support ASLR. The replacement for this field is Cache in device RAM with overflow on hard disk. For more information, see Features removed from future releases.
Resolving failover to server side caching during boot
1. In a PVS target device booting in private vDisk mode or maintenance vDisk version, open a command prompt with administrator privileges.
2. Run the diskpart utility, using the following command:
diskpart
3. To verify the SAN policy, run the command:
Diskpart > san
The SAN policy should be Online All for PVS target devices to function correctly in while in Cache in Device RAM with Overflow on Hard Disk mode.
4. To change the SAN policy, run the command:
Diskpart > san policy=OnlineAll
5. Shutdown the PVS target device and change the vDisk mode to standard image or promote the maintenance version to test or production version.
Note
The SAN policy causes the PVS write cache drive to remain offline. During boot, the PVS target device determines that the write cache drive is ineligible for use as a write cache and therefore will failover to server side cache.
Important considerations
When creating a machine template, ensure that it has a similar hard disk drive structure and that it can boot from a vDisk in Private Image mode. For example:
- To PXE boot a VM with write cache, create a VM with 1 hard disk drive.
- To use Boot Device Manager (BDM) to boot a VM with write cache, create a VM with 2 hard disk drives.
- To use BDM to boot a VM that uses a personal vDisk and write cache, create a VM with 3 hard disk drives.
Thank you for the feedback
Share
Share
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 Do Not Agree to exit.