OMSA Task to update from Openmanage Essentials

Hey there...

So I was thinking for 7.3 to 7.4 you use the msp file for upgrade?  Is that what you are doing?  

I have not looked at this in a while but I'm thinking folks use msp for minor OMSA upgrades or they run a OME task to uninstall (see sample task in OME) and then push it a-new.  But msp should work.

Does that help at all?

Thanks!

Rob

I'm not sure what you mean by msp, I've never successfully pushed an OMSA install, uninstall or upgrade from OME as of yet.  I am just beginning to play with it, I read the document on it and thought I followed the instructions but it didn't work.

I cannot seem to the find the msp (patch) version of OMSA v7.4 OME usually needs the msp version in order to do an upgrade.

Do you have the option to manually uninstall OMSA on your target server(s) and then try a fresh install? Try a single target first and see the result. I am not sure if your problem is with credentials or netwoork configuration, or something else.

To try a fresh install of OMSA, do unzip the downloaded executable and point to the msi for the task creation process. Do ensure that  you have entered the right credentials, and check other options (like 64-bit) if applicable.

- PPrabhu

Yeah, sorry, my mistake.  7.4 is an exe and the smaller point releases like 7.3.0.1 are msp files.  You can find them located at support.dell.com.  Just pick some sort of PowerEdge server model and go to drivers and downloads.

Try the test like PPrabhu suggests.  We are trying to see if there is some sort of permissions issue you are facing.

thx!

Rob

Ok uninstalling it and rebooting then pushing 7.4 which is the exe I have it pointed to in the task installs 7.3 which was on it prior.

That confuses me.

Hey,

Can you check what is the OMSA package present in your temp folder on the server where you are trying to deploy OMSA through OME? If there is already an OMSA package present, then it might have resulted in updating the older OMSA from the temp folder. Just to cross verify, if there is any package present under temp folder, i would request you to delete that from the temp folder and then perform an omsa deploy using OME. Let us know if that goes well.

I don't see any sysmgmt file in c\users\name\appdata\local\temp or in c\windows\temp.

I pointed it to the desktop of the server I'm using to deploy OMSA and specified the 64 bit version of OMSA.

The job references this location but on the deploying server or the target server I do not see this path as there is no s43K folder.

PackageCode 0
PackageFileName C:\Users\$TRScott\AppData\Local\Temp\s43k\SysMgmt.msi
PackageReleaseId Not Available
PackageState complete
PackageStatus 2
TotalStatusMessage Software update complete.

Hi Scott,

I have seen this happening when an unfinished task made the packages stay in the temp folder and System Update>> Packages folder but once everything is cleared, it works fine. 

Can you try this? Launch %temp% from your run prompt and clear if any preinstaller zip package or any OMSA related package is there. Clear the package from the system update >> packages folder as well.

Now create a new OMSA  deploy task. Make sure OMSA 7.4 package is selected. Let us know if this works.

Just a random thought, it doesnt make a lot of sense but sometimes we do miss these small small things. Can you check that the package you are using is an actual 7.4 package? If you install it manually, does it install 7.3 or 7.4. I know its the most chance but just to check.

Just one more thing which comes in my mind is: Do you have already have OMSA 7.3 installed on your server? And then when you try to install 7.4, you still see 7.3, is that the case? I am just trying to understand whether OME is actually deploying the new package or not. You can be sure about this by uninstalling the older OMSA from the server and then creating a OMSA deploy task. It should help us root cause. 

Also, are you able to see BAUpdate.XML getting created under windows/temp folder when you trigger an OMSA deploy task? 

It is definitely 7.4, I've manually installed it and it shows as 7.4.

The server did have 7.3 on it but before installing 7.4 I removed it and rebooted the server then pushed 7.4 install and it puts on 7.3, which server am I going to see that xml file on, the deployment server where OME is installed or the target server where I'm installed OMSA?

Nope no preinstaller is there and I've cleared out the packages folder and it still seems to install 7.3 only.

Okay. So, you will see that XML file on the target server. But it stay only as long as the task is executing. That can give you some insight on what is going wrong. I am running out of suggestions, you may want to log a trouble ticket if this also doesn't work

Never see a .xml file of the name you say I should, I do see a folder with a sysmgmt.msi in it while it is installing then it disappears when done.  And again it installed 7.3.  I'll have to open a case with Dell later this week once I'm back from a business trip.