-
-
-
-
-
-
Publish layered images from template
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
Publish layered images from template
Layered images are virtual machines composited from the layers and settings specified in an image template. Using an image template, you can publish as many layered images as you need to a location in your Provisioning Service or hypervisor that you specify in the connector configuration.
When layered images are published, you can use scripts to perform important layer-specific steps. For example, you can activate Microsoft Office, which may need to be done before the virtual machine is used as a master disk for your deployment tools.
The mechanism used to run these scripts can vary, including our own kmssetup
.cmd functionality, run-once support, or even running the scripts manually. After all of the scripts run or other manual steps are taken and the virtual machine is in the desired state, a guest OS shutdown is initiated either by the scripts or manually. If you use the kmssetup.cmd
functionality, there is a documented process for initiating a shutdown after all layer scripts and other kmssetup
functionality are complete.
To publish a layered image:
- In the Images module, select one or more image templates that you want to publish.
- On the Action menu, select Publish Layered Image.
- On the Confirm and Complete page, select Publish Layered Images. For each Image Template, this starts a task called Publishing Layered Image.
-
Check the task bar, and when the disk for this image is created, click the link in the task description to advance to the next stage. Example link in task description:
The link leads you to a virtual machine whose state of creation depends upon the platform you are publishing to:
- VMware vSphere (or provisioning service on it): The virtual machine is created, powered on as the guest OS, and running any scripts specified in the connector configuration.
- Citrix Hypervisor, MS Hyper-V, Nutanix (or provisioning service on it): The virtual machine is created, but off. Log in as guest, and let the machine run any scripts specified in the connector configuration.
- Azure (or Machine creation for Azure): A window for creating a virtual machine is open, but incomplete. Enter the values required, finish creating the machine, and power it on. The machine runs any scripts specified in the connector configuration.
-
When the virtual machine is in the desired state, shut it down. The task status changes to Done.
- Use the information in the task description to navigate to the image in your environment.
Possible error message
If you receive the following error and you want to log into the published image to make changes, it must be through the local user and not a domain user.
This system was not shut down properly. Please log off immediately and contact your system administrator.
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 Do Not Agree to exit.