Citrix Provisioning

Creating and configuring an SCCM update VM

December 20, 2018

Contributed by:

Create a VM and give it a name that meets DNS requirements for computer object names.
Install the operating system.
Install the Provisioning Services target device software.
Run the imaging wizard. For the same device name, use the VM name in step 1.
Reboot to image the device.
Shut down.
Add the device to the OU that SCCM is scanning. Citrix recommends dedicating an OU rather than giving SCCM free rein of the entire Active Directory.
Boot the client in private image mode.
Open the firewall ports for SCCM on both the target device and the Provisioning Server.
Make the SCCM administrator and the SCCM server a local administrator.

a. On the SCCM server, select Administration > Discovery methods. Right-click on Active Directory System Discovery and choose the option Run Full Discovery Now. By default, SCCM only scans for new clients every 8 hours.

b. Wait for the client to appear. Typically, this process takes about 10 minutes.

c. Right-click on the SCCM client and push it to the device. Wait until the SCCM client is installed and appears as active in SCCM.

d. Assign the client to a device collection in SCCM.

e. In SCCM Administration > Client Settings give the client a new setting and select the custom setting Computer Agent. Select the option Additional software manages the deployment of applications and software updates. Push this configuration to the device collection in step 4 as soon as possible.
Go to the site’s Property > vDisk Update tab and enable the automatic vDisk update option for the site.
After the SCCM client is installed and appears as active, shut down the device.
Change the vDisk to standard image mode.
Right-click on the device and choose Active Directory > Delete Machine Account.
Delete the Provisioning Services device record.
Create a host record of where the image VM is located.
Create a managed vDisk record. Note: The device name is case-sensitive.
Create a task.

Note: When pushing updates and software, always push to the SCCM device collection.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Creating and configuring an SCCM update VM

December 20, 2018

Contributed by:

December 20, 2018

Contributed by:

Creating and configuring an SCCM update VM

In this article