Liam
(Lurker)
2004-06-22 06:08 PM
Installing via Kix

Hey guys,

I'm new to Kix and wonder if any of you could point me in the right direction or give me a start on how I could approach what I need to do.

I would like to distribute the McAfee ePO agent package on every PC that logs onto my network, done through the login script. I would need it to check if the package is installed (could be in 2 or 3 different locations) and if not, install it. Non-Admins can run the package, as it is a non-admin install.

I guess it would be easy enough, but I've never managed to get me head round any kind of scripting.

Cheers,

Liam


Chris S.
(MM club member)
2004-06-22 06:53 PM
Re: Installing via Kix

Something like...

Code:

$epoPATH=ReadValue("HKLM\Software\Network Associates\ePolicy Orchestrator\Agent", "Installed Path")
If Not @ERROR
"ePolicy Orchestrator Agent Installed" ?
Else
"Installing ePolicy Orchestrator Agent...Please wait." ?
Copy "@SCRIPTDIR\\poaginst.exe" "%TEMP%"
Shell "%TEMP%\poaginst.exe"
Del "%TEMP%\poaginst.exe"
EndIf



Les
(KiX Master)
2004-06-22 07:04 PM
Re: Installing via Kix

I am not so sure ePO installs can be confirmed with that reg read. Seems to me ePO installs with VS 7.x but is not activated. I look for the file "C:\Documents and Settings\All Users\Application Data\Network Associates\Common Framework\LastPropsSentToServer.xml" that indicates that it is communicating with the ePO server.

Also, with ePO 3.x the executable is FrmePkg.exe


Kdyer
(KiX Supporter)
2004-06-22 09:54 PM
Re: Installing via Kix

Les is 100% correct.. Oh, and by the way, if you build your own FRAMEPKG.EXE and it uses your domain Account which expires every xx days, you will need to update the FRAMEPKG.EXE file as well.

Another thought to ponder.. We have included this in our Ghost image (I know everybody here does not do that)..

Kent


NTDOCAdministrator
(KiX Master)
2004-06-23 12:56 AM
Re: Installing via Kix

Quote:

"C:\Documents and Settings\All Users\Application Data\Network Associates\Common Framework\LastPropsSentToServer.xml"




What if my OS is installed on a different drive like D: or E:


Les
(KiX Master)
2004-06-23 01:05 AM
Re: Installing via Kix

What idiot would install the OS to D: or E:?

Richard H.Administrator
(KiX Supporter)
2004-06-23 09:50 AM
Re: Installing via Kix

Quote:

What idiot would install the OS to D: or E:?




A metaframe shop, dual-booter or hard-core masochist I guess


Liam
(Lurker)
2004-06-23 10:06 AM
Re: Installing via Kix

Quote:

Something like...

Code:

$epoPATH=ReadValue("HKLM\Software\Network Associates\ePolicy Orchestrator\Agent", "Installed Path")
If Not @ERROR
"ePolicy Orchestrator Agent Installed" ?
Else
"Installing ePolicy Orchestrator Agent...Please wait." ?
Copy "@SCRIPTDIR\\poaginst.exe" "%TEMP%"
Shell "%TEMP%\poaginst.exe"
Del "%TEMP%\poaginst.exe"
EndIf






Cool, thats a nice start, but I'm not sure what some of it means, if you have time, could you put some comments on for me please?


Quote:

I am not so sure ePO installs can be confirmed with that reg read. Seems to me ePO installs with VS 7.x but is not activated. I look for the file "C:\Documents and Settings\All Users\Application Data\Network Associates\Common Framework\LastPropsSentToServer.xml" that indicates that it is communicating with the ePO server.

Also, with ePO 3.x the executable is FrmePkg.exe




This would work in a way I guess, but what about workstations that a user has interfered with and removed the agent? The file still exists after it has been unistalled. Is there a way to check something else, perhaps a service so that the only way the agent won't be installed is if the agent is already running??

Quote:

Les is 100% correct.. Oh, and by the way, if you build your own FRAMEPKG.EXE and it uses your domain Account which expires every xx days, you will need to update the FRAMEPKG.EXE file as well.

Another thought to ponder.. We have included this in our Ghost image (I know everybody here does not do that)..

Kent





Thanks for that, but I have the package created with a dedicated epo admin account which the password doesn't get changed on regular.

We don't currently have a ghost image, thats going to be one of my next projects I think


Kdyer
(KiX Supporter)
2004-06-23 02:24 PM
Re: Installing via Kix

Quote:

A metaframe shop




Just read the other day that MetaFrame 1.8 is coming to EOL.. MetaFrame XP does not like drive re-direction.

Kent


Kdyer
(KiX Supporter)
2004-06-23 02:30 PM
Re: Installing via Kix

There really isn't too much to explain.
Code:

$epoPATH=ReadValue("HKLM\Software\Network Associates\ePolicy Orchestrator\Agent", "Installed Path")
If Not @ERROR ; -- Check for the existence of the reg value
"ePolicy Orchestrator Agent Installed" ?
Else ; -- does not exist
"Installing ePolicy Orchestrator Agent...Please wait." ?
Copy "@SCRIPTDIR\framepkg.exe" "%TEMP%" ; -- copy the package to install ePO
Shell "%TEMP%\framepkg.exe" ; -- execute the file
Del "%TEMP%\poaginst.exe" ; -- delete the file
EndIf



Pretty simple..

If you really need to look for the ePO Server.. You should be able to readprofilestring on the siteinfo.ini. It is what I used when we migrated from one ePO server to another.

Code:

CLS
BREAK ON
:epoagent
;Version 1.1 - 6-March-2003
;Original Post 24-February-2003
;Kent Dyer (leptonator@hotmail.com)
;SYNOPSIS:
;Original idea was brought about from a Support Call to NAI as we brought on-line a new ePO Server
;Sure, we could "push" the Agent to the client, but why not have the script pick this up...
;We needed to bring on-line our Branches and leave others as originally setup.
;VERSIONS:
;Version - 1.1 6-March-2003 Bug Fix, On first RETURN, file was not closed
;Version - 1.0 24-February-2003 Original Code
$windir = READVALUE('HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion','SystemRoot')
$systemdrive = SUBSTR($windir,1,2)
$sitefile=$systemdrive+'\EPOAGENT\siteinfo.ini'
$old='OLDSERVER'
$new='NEWSERVER'
IF EXIST($sitefile)
IF READPROFILESTRING($sitefile,'Current','MasterSiteServer')=$new
RETURN
ENDIF
IF READPROFILESTRING($sitefile,'Current','MasterSiteServer')<>$new
$rc=WRITEPROFILESTRING($sitefile,'Current','MasterSiteServer',$new)
ENDIF
IF READPROFILESTRING($sitefile,'Current','Servers')<>$new
$rc=WRITEPROFILESTRING($sitefile,'Current','Servers',$new)
ENDIF
IF READPROFILESTRING($sitefile,$new,'ComputerName')<>$new
$rc=WRITEPROFILESTRING($sitefile,$new,'ComputerName',$new)
ENDIF
IF READPROFILESTRING($sitefile,$new,'DNSName')<>$new+'.DOMAIN.COMPANY.COM'
$rc=WRITEPROFILESTRING($sitefile,$new,'DNSName',$new+'.DOMAIN.COMPANY.COM')
ENDIF
IF READPROFILESTRING($sitefile,$new,'LastKnownIP')<>'1.2.3.4'
$rc=WRITEPROFILESTRING($sitefile,$new,'LastKnownIP','1.2.3.4')
ENDIF
SHELL '%COMSPEC% /C NET STOP NAIMAGENT32 > nul'
sleep 2
SHELL '%COMSPEC% /C NET START NAIMAGENT32 > nul'
RETURN
ENDIF



Do not know if this is still used for 7.x..

Kent


Les
(KiX Master)
2004-06-23 02:36 PM
Re: Installing via Kix

Quote:

but what about workstations that a user has interfered with and removed the agent?



That is what the reports in the ePO Console are for! The ePO Console is your friend.


Chris S.
(MM club member)
2004-06-23 02:42 PM
Re: Installing via Kix

Quote:

but what about workstations that a user has interfered with and removed the agent?




Plus, if you modify that code for your environment and keep it in the logon script it will reinstall the ePO client if the user removes it.


Liam
(Lurker)
2004-06-24 01:30 PM
Re: Installing via Kix

Quote:

The ePO Console is your friend.




Really??


Thanks for all the help, I think I have enough now and with a bit of time and some Kix manuals I think I could get something knocked up to get the agent installed.

Cheers guys


Kdyer
(KiX Supporter)
2004-06-24 02:09 PM
Re: Installing via Kix

One other thing if you need to deploy to a list of computers, you can import them into epo using a text list and it will push epo to each..

Kent