-
-
-
-
-
App Layering services
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!
App Layering services
The following services run on the App Layering appliance:
- Management service
- Layering service
- BITS server service
The services are displayed on the System tab.
Management service
The App Layering appliance uses the Management service to communicate with the following servers, agents, and platform software:
- Active Directory
- Windows file servers
- Network time servers
- Unix file servers
- DHCP server
- App Layering agents
- Your hypervisor and provisioning service
The firewall ports for each of the above components must be open. For details, see Firewall ports.
Layering service
The Layering service manages your layers and image templates. The appliance keeps a set of master layers on its local storage, and Elastic layers on the appliance’s File Share.
Note: Elastic layers are copies of App layers stored on the appliance’s File Share. Elastic layers are delivered upon user login, rather than as part of the layered image.
On the System module, the Layering service shows the amount of available space on each of your File Shares.
BITS Server service
The App Layering appliance copies files to and from the appliance using Microsoft’s BITS Server service and the location specified in the connector configuration.
Firewall ports for the BITS Server service
Open the firewall ports for the BITS Server service. For details, see Firewall ports.
BITS Server logs
BITS Server produces its own logs, which you can find here:
/var/log/Unidesk
The logs are based on the log4net configuration settings, which you can find in the following location:
source\BitsServer\Citrix.AppLayering.BitsServer\log4net.config
If you want to change the Uploads folder location
You can mount another volume to use for BITS uploads by configuring the path to the volume for both the BITS server and the Hyper-V connector.
-
Mount the new volume.
-
Edit the Uploads folder location for BITS Server in the following json file:
/var/aspnetcore/bits-server/appsettings.Production.json
Change default UploadFolder settings of /mnt/repository/Uploads to the new location, for example /mnt/test/Uploads.
-
Locate the connector configuration file:
/usr/local/lib/node_modules/unidesk-hyperv-connector/config.json
Change the default upload folder (called fileUploadFolderPath) from /mnt/repository/Uploads to the new location:
-
Restart both services:
systemctl restart kestrel-bits-server systemctl restart unidesk-hyperv-connector <!--NeedCopy-->
-
Update the group and permissions on the new Uploads folder:
chmod 770 /mnt/test/Uploads chmod g+s /mnt/test/Uploads chgrp apache /mnt/test/Uploads <!--NeedCopy-->
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.