| | | Forum Newbie
       
Group: Forum Members Last Login: 10/13/2005 6:45:00 AM Posts: 3, Visits: 1 |
| 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 !! |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 8/10/2005 9:45:00 AM Posts: 9, Visits: 1 |
| 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
___________________________ So it'll just work, right? |
| | | | 
Supreme Being
       
Group: Moderators Last Login: Yesterday @ 2:43:01 PM Posts: 657, Visits: 797 |
| 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!
New Boundary Technologies Support support@newboundary.com |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 8/10/2005 9:45:00 AM Posts: 9, Visits: 1 |
| 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?
___________________________ So it'll just work, right? |
| | | | 
Supreme Being
       
Group: Moderators Last Login: Yesterday @ 2:43:01 PM Posts: 657, Visits: 797 |
| 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
New Boundary Technologies Support support@newboundary.com |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 8/10/2005 9:45:00 AM Posts: 9, Visits: 1 |
| 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
___________________________ So it'll just work, right? |
| |
|
|