Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Install Altiris Agent on ESX

Updated: 07 Jul 2009 | 7 comments
ziggy's picture
+14 14 Votes
Login to vote

We all know how much money is saved with going virtual where possible. And with the advances in virtual technologies, this area is growing faster every year. With that said, you have probably figured out that I strongly believe Virtual Environments are the way of the future, just like wireless, grid, and cloud computing.

As stated before, we are a TMS client, and install our Altiris Agents exclusively on our servers. Needless to say, we have many *NIX servers (over 11,000) and all with an Altiris agent on them. The ESX platform being one of them. With over 600 ESX servers (mostly 3.0.1) they have a slightly different OS configuration that a standard Altiris agent installation procedure will not work out of the box.

With the help of my ESX guru, we have developed a script that will install the Altiris agent on the node that the script is ran from. Depending on your environment, specifically firewall and security configurations, this script may work as-is, or with minor tweaks:

#!/bin/bash
mkdir /tmp/altirisagent
cd /tmp/altirisagent
chkconfig firewall --level 2345 off
/usr/sbin/esxcfg-firewall --AllowIncoming
/usr/sbin/esxcfg-firewall --AllowOutgoing
ftp -n <
user anonymous rdp
cd /path/to/your/AltirisAgent
binary
prompt
mget aex-agent-install-config.xml
mget aex-bootstrap.gz
quit
EOF2
cd /tmp/altirisagent
mv aex-agent-install-config.xml .aex-agent-install-config.xml
#chmod u+x
gunzip aex-bootstrap.gz
chmod u+x aex-bootstrap
./aex-bootstrap http://yourNS.serverhere.com
/usr/sbin/esxcfg-firewall --BlockIncoming
/usr/sbin/esxcfg-firewall --BlockOutgoing 
esxcfg-firewall --openPort 52028,tcp,in,AltirisAgent
esxcfg-firewall --openPort 52029,udp,in,AltirisAgent
esxcfg-firewall --openPort 80,tcp,out,AltirisAgent
esxcfg-firewall --openPort 80,udp,out,AltirisAgent  

If you place the above lines in a file on one of your ESX 3.x servers, give it execute permissions with this command:

chmod 755 

and then run it as root. One minute later you will have an awesome Altiris Agent up and running on your ESX host.

Thank you.

Comments

dougj's picture
26
Mar
2009
3 Votes +3
Login to vote

Great article, Ziggy!

Nice to get your insights into this, Ziggy. Thanks for sharing this with us. 

Eshwar's picture
04
Apr
2009
1 Vote +1
Login to vote

Thanks for sharing...

 

Thanks,
Eshwar

rpoag's picture
02
Jun
2009
0 Votes 0
Login to vote

Firewall

Thanks for the script.  We added tcp port 1011 inbound and outbound to get monitor solution working.

Ryan Poag
Campbell & Company, Inc.
If your question has been resolved, please be sure to "Mark as Solution"! Thank you.

Tom Gool's picture
01
Nov
2009
0 Votes 0
Login to vote

Very cool

This is a very cool way for managing my ESX hosts from within DS

markfreeman's picture
22
Feb
2011
0 Votes 0
Login to vote

Great article, got my ESX 3

Great article, got my ESX 3 servers installed pain free (once I had this script!). Has anyone had success with ESX 4?

ziggy's picture
22
Feb
2011
0 Votes 0
Login to vote

We did not use this on ESX

We did not use this on ESX 4.  Actually, there are some fundamental issues with how Altiris handles ESX 4 servers.  We are on the latest 6.x version (with rollup) and found that for all our ESX 4 servers, they were being identified as Linux servers (probally due to how it is determined via wich kernal is found).  That means that they were falling into the 'All Linux servers' collection instead of the 'All ESX servers' collections.  I opened a ticket and after much back and forth, they agreed to place a fix for it in the next rollup.  I had to clone and modify the collections to build a new 'All Linux servers' and 'All ESX servers' collection, and then change all the policies (inventory and other jobs) to point to those new collections so that we didn't get any bad cross-mojination.  All that needs to be done is run 'vmware -v' to see what version an ESX server is.  That could easily be integrated into the agent.  I am looking forward to 7.1 next month, so we will see how it is handled there as well.  Good luck!

markfreeman's picture
24
Feb
2011
0 Votes 0
Login to vote

Thanks for that Ziggy, I'm

Thanks for that Ziggy, I'm rolling out on 7.0 so I guess we will see what 7.1 brings.