---
sourceDocument: Zurich IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-service-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Prepare the reference device for the golden image

# Prepare non-persistent VDI reference device {#ariaid-title1}

* Release version: Zurich
* 
* Updated May 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Remove the registration certificate, agent identifier, cached databases, and logs from the reference device before sealing it as a golden image. This cleanup confirms that each VDI duplicated from the image registers with a
unique identity on first start.

## Before you begin

Complete the following tasks before you prepare the golden image:

* [Install Agent Client Collector on a non-persistent VDI reference device](https://www.servicenow.com/docs/mYqUI0GGgk9IN667VJG2YQ "Install Agent Client Collector (ACC) on the reference device used to create the non-persistent VDI golden image. The mid-less installation method, combined with the LOCALUSERNAME=\"SYSTEM\" parameter and a non-persistent setting in acc.yml, configures the agent to operate correctly across copied VDI sessions.")
* [Enable DEX browser extension](https://www.servicenow.com/docs/1~T2Ihny3N8FkycQLYsUwg "Activate the DEX Chrome or Edge Extension on your system to collect different operational or performance-based metrics for the web applications.")
{#prepare-np-vdi-golden-image__ul_prereq_prepare_np_vdi}

Role required: sn_dex.admin and administrator access on the reference device  
Important:  
If you skip the cleanup steps in this task, every VDI cloned from the golden image inherits the same certificate and agent identifier. Cloned VDIs cannot register correctly when this happens.

## About this task

This task removes the artifacts that the Agent Client Collector generated during installation and initial registration on the reference device. After cleanup, you set `disable-asset` to `true` in
acc.yml so that each cloned VDI generates its own asset record on first start. After you complete this task, the reference device is ready to be sealed as the golden image used to clone the VDI
pool.

## Procedure

1. Stop the Agent Client Collector service from Services.  
   Open Services as an administrator before stopping the service.
2. Set the Agent Client Collector service Startup type to Manual.  
   The cloned VDIs start the service through the logon script rather than at boot.
3. Navigate to C:\\ProgramData\\ServiceNow\\agent-client-collector\\config\\cert\\cnc\\ and delete both cnc_chain and private_key.
4. Navigate to C:\\ProgramData\\ServiceNow\\agent-client-collector\\cache\\ and delete agent_now_id.
5. Empty the contents of the databases and log folders under C:\\ProgramData\\ServiceNow\\agent-client-collector\\.
6. Open acc.yml at C:\\ProgramData\\ServiceNow\\agent-client-collector\\ and update the file as follows.
   1. Remove the line that begins with `agent-key-id`.
   2. Add the registration key again.
   3. Uncomment `disable-asset` and set its value to `true`.  

          disable-asset: true

   {#prepare-np-vdi-golden-image__substeps_prepare_acc_yml}
7. Save and close acc.yml.
{#prepare-np-vdi-golden-image__steps_prepare_np_vdi}

## Result

The reference device is ready to be sealed as a golden image. The Agent Client Collector service does not start automatically, no certificate or agent identifier carries forward, and each cloned VDI generates its own asset record on first start.

## What to do next

Configure the VDI pool to use the golden image. See [Manage logon and logoff scripts for non-persistent VDIs](https://www.servicenow.com/docs/Ivg94wrkIjeCescQMt8Ozg "Configure logon and logoff scripts in a non-persistent VDI pool to control how the MID Server starts and stops during virtual desktop sessions.").