kdegraa Absent Member.
Absent Member.
1694 views

Deploying Zenworks agent 11.3 with Windows 7

Hi,

we currently build Windows 7 images with the Zen agent installed before sys prepping the master computer and then taking the image. This has worked fine up till the 11.3 agent that is currently being issued by our zcm server. Windows computers now do not automatically join the local Active Directory domain after imaging. They need to be manually joined. This because the script we use sitting in the C:\Windows\Setup\Scripts folder does not fully work. It gets so far and then goes no further.

After looking online it is becoming clear installing the Zen agent prior to the sysprep is not the best way to do it. Reading on this forum indicates most people use a process to install the Zen agent as part of the sysprep process with the installer starting from a command in the unattend.xml file.

I've had a fairly long search of this forum, going down into 20 pages or so but can't find any instructions on how to kick off the Zen agent.

If anyone can give instructions on the syntax of the command to install in unattend.xml and also any other files it would be greatly appreciated.

Thanks.
Labels (2)
0 Likes
4 Replies
Knowledge Partner
Knowledge Partner

Re: Deploying Zenworks agent 11.3 with Windows 7

kdegraa;2398453 wrote:
Hi,

we currently build Windows 7 images with the Zen agent installed before sys prepping the master computer and then taking the image. This has worked fine up till the 11.3 agent that is currently being issued by our zcm server. Windows computers now do not automatically join the local Active Directory domain after imaging. They need to be manually joined. This because the script we use sitting in the C:\Windows\Setup\Scripts folder does not fully work. It gets so far and then goes no further.

After looking online it is becoming clear installing the Zen agent prior to the sysprep is not the best way to do it. Reading on this forum indicates most people use a process to install the Zen agent as part of the sysprep process with the installer starting from a command in the unattend.xml file.

I've had a fairly long search of this forum, going down into 20 pages or so but can't find any instructions on how to kick off the Zen agent.

If anyone can give instructions on the syntax of the command to install in unattend.xml and also any other files it would be greatly appreciated.

Thanks.


See here: https://www.novell.com/communities/coolsolutions/windows-7-automated-imaging-and-zcm-registration/

Thomas
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Deploying Zenworks agent 11.3 with Windows 7

If you just run the Agent installer from the command line with the /? switch, it will give you a bunch of parameters including automation.

The simplest way to install the agent on the image is to run the install, shutdown, and take the image before rebooting when the agent actually registers.
There are other methods too
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
Knowledge Partner
Knowledge Partner

Re: Deploying Zenworks agent 11.3 with Windows 7

kdegraa;2398453 wrote:
Hi,

we currently build Windows 7 images with the Zen agent installed before sys prepping the master computer and then taking the image. This has worked fine up till the 11.3 agent that is currently being issued by our zcm server. Windows computers now do not automatically join the local Active Directory domain after imaging. They need to be manually joined. This because the script we use sitting in the C:\Windows\Setup\Scripts folder does not fully work. It gets so far and then goes no further.

After looking online it is becoming clear installing the Zen agent prior to the sysprep is not the best way to do it. Reading on this forum indicates most people use a process to install the Zen agent as part of the sysprep process with the installer starting from a command in the unattend.xml file.

I've had a fairly long search of this forum, going down into 20 pages or so but can't find any instructions on how to kick off the Zen agent.

If anyone can give instructions on the syntax of the command to install in unattend.xml and also any other files it would be greatly appreciated.

Thanks.


We install the agent on the "base" image, get what we need and then remove the agent.
Prior to creating the sysprep, we copy the actual preagentcomplete.exe onto the hard drive

In the unattend.xml file we have the machine the join the domain, and then after the machine reboots/comes up the first time, the user logs in and then we execute the .exe install for the ZCM agent (okay technically we run a batch file that runs ziswin.exe /c just to make sure the ISD is whacked and THEN run the install).

Seems to work OK.

However, it should also be noted that our AD GPO temporarily grants users "admin" rights for a few days after the machine is inserted in the domain to run the install and any other odd programs they may need.

But there are many other ways to do this.

We liked it this way because if there was a ZCM agent update, we didn't have to build an entirely new image, we just opened it with Ghost Explorer and plopped in the new .EXE and that was it.
0 Likes
gerwil1478
New Member.

Re: Deploying Zenworks agent 11.3 with Windows 7

Hi
I find that the ZAA is best installed after the workstation has had its unique name applied. Else duplicate entries and scripts will fail.

Part of my unattended.xml :-
.
.
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>C:\Install-Win\ZAA-Win7-64bit-9010.exe /q</CommandLine>
<Description>Install ZCM agent</Description>
<Order>2</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>C:\Windows\wsname.exe /N:LAW-$SERIALNUM</CommandLine>
<Description>Change the computer name</Description>
<Order>1</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>

So rename first. Install the agent and "/q" to reboot. Also, when a new ZAA turns up, it is just a matter of coping it to the local drive, sysprep without changing anything and reimage.

Cheers
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.