Cool Solutions

Installing ZENworks Agent through Microsoft Deployment Toolkit (MDT)

asudheer

By:

January 13, 2017 3:46 pm

Reads:2,962

Comments:1

Score:5

Print/PDF

Download ZENworks PreAgent Tracker.zip

About Microsoft Deployment Toolkit

The Microsoft Deployment Toolkit (MDT) can help build an automated installation source for deploying Windows OS and Office. The build can also include device drivers, Windows updates, and any other software.

The ZENworks Agent is one such software that needs to be installed during deployment.

Now, let me explain the way the ZENworks agent installation is carried out in the problem statement.

About ZENworks Agent Installation

ZENworks Agent can be installed through an executable (PreAgentPkg_Agent[Complete|CompleteDotNet].exe) available on ZENworks Primary in the zone. This PreAgent package contains various individual packages that comprises the Agent. The ZENworks agent can be installed by running this PreAgent package with the following options. There are other command line parameters than listed below. Use the PreAgentPkg_Agent.exe -h option to list all the available options.

-x = suppress reboot (Manual Reboot)
-q = show no reboot prompt(quiet install)
-m = rebootless agent with limited agent

Executing PreAgent will extract the packages & create a pre agent service to track the agent installation. The PreAgent executable now exists leaving the service for tracking of individual packages required for the agent.

Problem Statement

The ZENworks PreAgent exists after the initial tasks and doesn’t wait till the installation of the individual packages. The MDT deployment will move on to the next installation in the build, thinking that the installation of ZENworks Agent is finished. This can lead to installation failure as there can be only be one installation (one instance of msiexec) is allowed in Windows at a given time.

Solution

We wrap this installer in a PowerShell script, which will be running & tracking the agent installation until it finishes.

How To

The MDT build can now be configured to run this script instead of the PreAgent package. This script will make sure that we don’t return the control to MDT while the agent installation is in progress & thus sequencing the next installations from the MDT build.

How the Script Works

This script will track the status file ZPA.status that gets created, updated with every activity of PreAgent, individual package installation and reboot behavior post installation. This is a more reliable way to track the agent installation.

The script is available ZENworks PreAgent Tracker in zip format. Please feel free to tune the script for different command options, configure script timeout, and more.

Hope this helps.

1 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 5 (1 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.
Loading...

Tags:
Categories: Cool Tools, Technical, Unified Endpoint Management, ZENworks, ZENworks Configuration Management, ZENworks Suite

Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

1 Comment

  1. By:asudheer

    I initially found this problem & a solution being described @ http://www.vaughnemiller.com/2012/09/06/installing-novell-zcm-adaptive-agent-in-mdt-2012/

    However due to limitation with the solution posted in the about post, I have come up with a different approach for better reliability.

Comment

RSS