New Boundary Support Forum / General Discussion / Prism Patch Manager / Deploying leafs via Prism Deploy? / Latest Posts

RE: Deploying leafs via Prism Deploy?

Ved — Fri, 22 Jul 2005 08:54:00 GMT

Hi Jeff,

Bandwidth isn't a problem, its that the command isnt using the -mh switch.

The share the installer is on it open and accessable and i've no problems installing the leaf agent onto the client, only that it wont use the -mh switch to tell the agent it needs to phone home

I can use some technology we have so you can share my desktop and you'll be able to see exactly how i do it.

I'll give support a call Monday afternoon (i'm in the UK and i assume you're in the US) and we can go through the issues.

Cheers,

David

RE: Deploying leafs via Prism Deploy?

New Boundary Support — Thu, 21 Jul 2005 11:19:00 GMT

Hi Ved,

A couple easy questions:

1) Is poor bandwidth (or lack of) an issue here?

2) The "AgentInstaller" folder is copied to a share accessible by all your machines?

If you have time, please give me a call and we can figure this out.

Thanks!

Jeff Burton
New Boundary Technologies

RE: Deploying leafs via Prism Deploy?

Ved — Thu, 21 Jul 2005 08:02:00 GMT

if i run it the way suggested the install fails:

V:\>\\server\Packages$\PatchMgr\AgentInstaller\UEAgentinstaller.exe -s -h %ComputerName% -p 9968 -r myserial -mh lonppatchmgr01 -mp 9968

This fails to work.

If i use this with a -d it adds the NAME "-mh" as the name of the agent where it should just add the generic name and then move onto the -mh part of the command and add the patchmgr server to the registry so it can communicate back:

V:\>\\server\Packages$\PatchMgr\AgentInstaller\UEAgentinstaller.exe -s -h %ComputerName% -p 9968 -r myserial -d -mh lonppatchmgr01 -mp 9968

it only adds "HKEY_LOCAL_MACHINE\SOFTWARE\New Boundary Technologies\Prism Patch Manager\6.0\PMAgent\Settings\AgentMap\Agents\0\Data" which is the leaf agent on the intended client. when i did a manual installation it had another registry key which is the Master Host called HKEY_LOCAL_MACHINE\SOFTWARE\New Boundary Technologies\Prism Patch Manager\6.0\PMAgent\Settings\AgentMap\Agents\1\Data. This does not appear when running the command so it's clear that it isnt using the -mh command for some reason which I cannot understand.

if i keep the -d but add a name after it such as "leaf" it again fails to install anything.

Can you please try the command as i wrote it and see if it works?

RE: Deploying leafs via Prism Deploy?

New Boundary Support — Wed, 20 Jul 2005 12:04:00 GMT

Hi Ved,

A note on scripted installs: Currently, the Agent-Installer from the command line provides little or no feedback on an installation failure. If Leaf-Agents do not appear in the console after a reasonable amount of time has elapsed when running a script or batch file, you may want to interactively install the Leaf-Agents to see what is happening. For example, an "out of licenses" condition, or a "registration" problem between Leaf and Master may be far more evident on an interactive install than a scripted install. Running install manually will show you the problem(s) you are having with the install.

Here are a few PPM KB Articles you should check: PPM0013 and PPM0032

Remote Leaf Agent installation Example

UEAgentInstaller -s -h %ComputerName% -p 9968 -r 01-123-45678-98765-19283 -mh Server01 -mp 9968

Note: The ABSENCE of the "-l" and "-m" options implies a "remote leaf" install, rather than a "local master" install. The leaf must always point back to a master with -mh, -mp.

Important: All switch options shown in the example are required. The values can be tailored to your machines, but you cannot omit the options. This is important if you are attempting to create a script. Also make sure there are no extra spaces or extra characters.

I hope this helps!

Thanks!

RE: Deploying leafs via Prism Deploy?

Ved — Wed, 20 Jul 2005 04:54:00 GMT

I tried this as well and it fails again. i can see it starting the process in task manager to install the agent but it ends and obviously fails.

I've tried it with -l and with -r and both but it still fails. is there no logging where i can see what it's failing on? I cant remove the -s as this just puts it into manual install mode.

Thanks

David

UPDATE----

I've just tried it with a -l and -d and i'm getting closer to the issue.

It doesnt want to write in the description. as in the example below i add -d, as you need to in a local install, but it wont add a correct description. it addes the -mh as the agent name in the registry. the annoying thing is that if i add in a name after like -d "Agent" it just fails so it looks to be something to do with adding a correct description name to make it work. hopefully after it sees a correct description it'll carry on to the -mh switch and fill that in as the registry only shows the agent install not the management server.

\\server\share\UEAgentinstaller.exe -s -h %computerName% -p 9968 -l -r serialnumber -d Agent -mh myserver -mp 9968

RE: Deploying leafs via Prism Deploy?

Pat Wilson — Wed, 13 Jul 2005 11:12:00 GMT

Ved,

Since you are running this from each client machine, don't you need to specify th '-l' parameter (after the -p, and before the -r) to specify a 'local' installation?

Good Luck !!

RE: Deploying leafs via Prism Deploy?

Ved — Wed, 13 Jul 2005 05:28:00 GMT

Doesnt look to be working. Prism Deploy says it ran ok but i get nothing installed to the clients and nothing reports back to the patch manager server. the command i'm using is as follows:

\\patchserver\share$\PatchMgr\AgentInstaller\UEAgentinstaller.exe -s -h %ComputerName% -p 9968 -r 51-2qj-vn3j7-u8k2k-2hd25 -mh lonppatchmgr01 -mp 9968

I can access the share, run the script manually and i still get nothing from it. The only way it works is if i remove the -s and just fill in the information which is obviously not what i want with 800 intended clients.

Any thoughts on how to make this work?

RE: Deploying leafs via Prism Deploy?

Ved — Fri, 08 Jul 2005 10:38:00 GMT

Excellent thanks for the assistance!

RE: Deploying leafs via Prism Deploy?

New Boundary Support — Fri, 08 Jul 2005 10:21:00 GMT

Yes, that should work as long as those domain accounts also have local admin rights on the Master Agent machine.

RE: Deploying leafs via Prism Deploy?

Ved — Fri, 08 Jul 2005 10:19:00 GMT

we have domain accounts which are local admins on the intended clients so would this not work too? The issue is that it may be hard yards getting an account with domain admin permissions unless it is totally needed.

David

RE: Deploying leafs via Prism Deploy?

New Boundary Support — Fri, 08 Jul 2005 10:02:00 GMT

Yes, use a domain admin account.

RE: Deploying leafs via Prism Deploy?

Ved — Fri, 08 Jul 2005 08:47:00 GMT

Excellent stuff

Does it have to run under a domain admin account or can it be one that is a local admin on the intended client? I'm guessing yes but just wanted to make sure.

Thanks for the superb response!

RE: Deploying leafs via Prism Deploy?

New Boundary Support — Thu, 07 Jul 2005 10:26:00 GMT

Hi David,

Yes, you can use variables within the command line.

Here are a few tips for installing Leaf Agents using Deploy:

1. Copy the folder C:\Program Files\Prism Patch Manager\AgentInstaller to a shared network location

a. Same place you store your Prism Deploy packages is always easy.

2. Create a command task in Prism Deploy and use Leaf Agent Command Line install.

b. Set the task to “run as” a domain admin account.

Sample - Leaf Agent Command Line Install (KB Article = PPM0013):

UEAgentinstaller.exe [-s] [-h machinename] [-p port] [-l] [-m] [-r serialnumber][-d description] [-mh masteragentname][-mp masteragentport][-up]

1. For “MachineName” use %ComputerName% variable.

2. For “MasterAgentName” use “%ServerName% or “LocalServerName”.

a. PPM must be installed on the servers prior to installing Leaf Agents using Prism Deploy.

Sample – New Remote Leaf Agent Install:

\\Server\Share\AgentInstaller\UEAgentinstaller.exe -s -h %ComputerName% -p 9968 -r 12-345-67890-12345-67890 -mh %PrismServerName% -mp 9968

RE: Deploying leafs via Prism Deploy?

Ved — Thu, 07 Jul 2005 08:41:00 GMT

That's great but how exactly do i configure the command line to take the client name automatically?

From the example below it has the client name written in but I would be deploying this to about 800 machines at once so obviously I dont want to do 800 individual commands

is there a way of adding a variable like %clientname% so it fills the -h part in?

UEAgentInstaller -s -h w2kp1en -p 5555 -r 01-123-45678-98765-19283 -mh Server01 -mp 9968

Hope you can help!

David

RE: Deploying leafs via Prism Deploy?

New Boundary Support — Wed, 06 Jul 2005 15:06:00 GMT

Hi David,

Yes, you can install Prism Patch Manager Leaf Agents using Prism Deploy. We recommend that to all our customers that use both products.

You simply use a Leaf Agent command line and create a Prism Deploy command task with all the correct commands and deploy the task to any machines you wish.

The command line is detailed in the PPM knowledge base article PPM0013. If you have any questions about how to set it up, please let us know.

Thank You!

New Boundary Support

Deploying leafs via Prism Deploy?

Ved — Wed, 06 Jul 2005 11:54:00 GMT

Has anyone tried deploying the leaf agents to clients via prism deploy using a package? The reason I ask is that we need to have the leaf agents on every client that already has Deploy on it.

Normally i'd be happy installing it on an AD logon script but we need to be more granular on who gets the patches so it can't be everyone at once - if you get what i mean.

Any ideas most welcome

David