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!
Known issues
Known issues in 1912 LTSR CU9
The following known issue has been observed in Cumulative Update 9:
- If you are on Citrix Provisioning version 1912 LTSR CU9 or earlier, and upgrade your license from DaaS to Universal Hybrid Multi Cloud License (UHMC) or Platform License (UPL), then you receive an on-premises universal license file which contains PVS_CCS and PVSD_CCS licenses. To configure your new licenses, run the Configuration Wizard to change the license type from Cloud to On-premises on the License Server page. [PVS-13147]
Known issues in 1912 LTSR CU8
No new known issues have been observed in Cumulative Update 8.
Known issues in 1912 LTSR CU7
No new known issues have been observed in Cumulative Update 7.
Known issues in 1912 LTSR CU6
No new known issues have been observed in Cumulative Update 6.
Known issues in 1912 LTSR CU5
No new known issues have been observed in Cumulative Update 5.
Known issues in 1912 LTSR CU4
No new known issues have been observed in Cumulative Update 4.
Known issues in 1912 LTSR CU3
No new known issues have been observed in Cumulative Update 3.
Known issues in 1912 LTSR CU2
No new known issues have been observed in Cumulative Update 2.
Known issues in 1912 LTSR CU1
No new known issues have been observed in Cumulative Update 1.
Known issues in 1912 LTSR
The following issues are known at this release:
-
Virtual disk update schedule time cannot be applied after modifying it. It functions until you reboot the Citrix SOAP service. [PVS-4349]
-
Running
Add-PvsDeviceToDomain
without specifying a parameter adds all targets in every site to the computer’s container in Active Directory. -
When importing VHDX files that you published from App Layering to the provisioned disk store, the operation may mistakenly report that you are using an invalid disk. You can eliminate this error by changing the period (.) characters in the published file name’s date and time. A valid file name contains only one period for the .VHDX file extension. [UNI-75902]
-
When you upgrade a Provisioning Server from Version 7.15 Cumulative Update 5 to Version 1912, a warning message might appear twice. This message appears because of a dependency on the CDF installer (a separate, Citrix Virtual Apps and Desktops component) during the installation of Citrix Provisioning. The provisioning installer cannot suppress the reboot message created by the CDF installer. As a result, the reboot message appears twice. [LCM-7594]
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.