Yes I do...
Buckle up for a Tolstoy "short story":
Would like to do this through IM7 (push out the Proliant support pack)? Or through a batch file? Either method will install or re-install what you're looking for...plus update your drivers and utilities to the appropriate version level to go along with your Insight Agents.
Since this is an IM 7 forum...let's go that route.
IM 7 has the Application Launch feature. You can refer to the help file on how to use it, but here's a quick rundown.
We can use IM7 to kick in a batch file that can push the support pack (with the web based password, IM7 trust and VCA already pre-configured). This "push" that the App.Launch can do will depend upon Microsoft credentials versus our agent trust. I'm not sure if you have agent Trust setup on your target servers (3 modes: Trust All, Trust by name, or Trust by Certificate). However this batch file calls the Proliant support pack and if the PSP has been pre-configured properly ..the net result will be a properly configured target server with the appropriate web based password, trust level and the Version Control agent - (preset), so that you won't have to go through this batch file process again.
AnyHoo...
First things first. I assume you have access to the Proliant support packs either through the HP Website or the Smartstart cd. Either way...copy the support pack for the appropriate windows os to a folder on your hard drive. Once the support pack has been copied, verify that the Read Only attribute has been removed for ALL files, especially if the files came from the Smartstart cd.
Once that's done...run setup.exe and that will open the Remote Deployment utility. You will get a popup indicating that "One or more components need configuration...".
So click ok and look over to the left and you will see the folder labeled "All Configurable Components". Open that folder and look toward the bottom where it lists the HP Insight Management Agent. Right click and configure. Check the box next to Enable SNMP sets. Type in a web based password for Administrator. If you don't specify one for Operator and User, then what you type in for Administrator will be used for the other two accounts. Personally I wouldn't use the same password for all three accounts.
Then specify your Trust level. This is where it gets a little tricky. It defaults to Trust by Certificate which is the most secure way of establishing Trust between your targets and IM 7. If you want to do Trust by Name (a little easier)...choose that option from the pull-down menu and then type in the name of the IM7 server. If you want to do Trust by Certificate...send me another reply and I can walk you through that process...
Let's assume Trust by Name to start (you can always change it to Trust by Cert later under IM7 using a Group Configuration command).
Click Save at the top left and then right click the Version Control agent that's listed right above the Insight Agent. If you see more than one Version Control Agent listed, make sure you are configuring \ choosing version 2.0.
Right click and Configure...
Put in the name of the IM7 server and the password for the WEB BASED administrator account that exists on the IM7 server. You may also have to do some redundant work here like you did with the Insight Agent (i.e. Web based password and Trust level, etc.). Click Save when you're done.
You have successfully pre-configured your Proliant Support Pack.
Back to IM7,
Go to your Tasks page and on the lower right you will see the ability to create a new Control task. Choose Application Launch.
It will give you a screen where you can input a file name. Put in a file called:
Swupdate.bat - No path needed, just the filename will do.
Below that you will see where you can put in some variables. I am going to assume you will be using a domain account as your user account to push this file...otherwise you have to provide a user account name and password (let me know...).
The two main variables that will be passed on to the swupdate.bat file are:
install_file and Repo_dir .
Let's revisit the PSP folder from earlier. Inside the PSP folder are various text files at the top. They start with BP and have three different extensions. The BP files with the .txt extensions tell you which OS this particular BP file (i.e. BP000172.txt) is for. Typically the higher the number toward the end of the file...the more recent it is.
Open up a couple of them and look at the very top...you will see the OS listed. Make a note of the one that corresponds to your particular OS.
Then back to IM 7... the first variable is Install_file and it's associated Value will be BP0001xx.XML (not the .txt...that was just for your reference.) Click "Set".
Then the variable Repo_dir will have a value of c:\PSPFolder\ In other words you need to provide the complete path to the .xml file. Click set...and then Next. Pick which target servers are going to have the PSP install applied to them and then give the overall Task a name. You have the ability to create a Query that points to the target servers. Once you pick the query that points to your target servers, schedule the task to run, and give this App.Launch task a name.
If you would rather bypass IM 7 to do all of this...let me know and I can walk you through that process. It's a little less involved.
Good luck and let me know if you have any questions.
Ed Cox
