1. msi is only used for clean installs and major upgrades.
2. msp is used for minor upgrades
3. if you keep running into trouble, you many need to manually copy the package over to the managed node and run it manually. Obviously defeats the purpose of the feature, but sometimes it reveals problems outside of OME that are easier to spot (like a bad package for example).
wow after writing a nice long response the page would not allow me to post and I had to start over so lets hope I don't forget anything.
I uninstalled 6.4, restarted, and then tried to deploy 6.5 with the msi, and no flags and got the same error message. I tried more than once and still it will not install.
I had previously manually installed 6.5, then uninstalled and installed 6.4 so I could test deployment (I thought I could use the msi for upgrades and you can do manually) so I know the packages are fine.
I went and downladed the "Dell Managed Node Service Pack for Windows V2247_A016.5.0" I have another server that is a R710, and has 6.3.0 - I tried to push that our using OME and it appeared to work as there was a Green Checmark, but upon reading the details of the job it said the patch was "not applicable" I logged onto that server, we to the Dell Drivers page and using the service tag, downladed the package again and upon trying to manually upgrade it, it gave the same message that the patch is not applicable. I am just straight frustrated now.
Is there a website or document that shows which version of OSMA is compatible with which servers, instead of having to read the documentation on each? It would be nice to know what can be installed on what server, as not everyone has all new 11G servers?
Also the next version of OME should have the ability to copy the details of the Task Execution History
Downloaded that file and got the same error.... manually installing has always worked.
I will note that while trying to push out system updates I get this error message "File deploy command failed to execute with error message: Unable to access the specified share on the remote system"
I searched for this error and found some "answers" for ITA and tried them
Turn off IE ESC on USERS - as it was already disabled for Admins
Add my server to the trusted sites in IE
But nothing seems to have worked.
So it appears I can only push hardware updates to 1 server and cannot deploy or upgrade the version of OSMA for any server.... great!
And it is also numbingly annoying that I have to download 12 different versions of OSMA to install on our servers...
Interesting. It seems like you don't have permissions on the target to update or deploy. But you said you checked the permissions. I wonder if you have to reboot the target(?) I would not think you would have to. But another thread on this seemed to indicate you might.
We will update the FAQ with some locations of where to get these packages. I know it is hard to keep track.
Otherwise, I will have to see if the support team can get logs, etc., on this issue.
Opps forgot to mention this, while I still cannot push OMSA to this server, after manually installing 6.5, I was able to install BIOS through OME. So it looks like there is something preventing the OMSA install. Some of the other Driver updates don't work, but I wondering if they are the correct drivers, as the BIOS info/driver version changed after the 6.5 manual install.
Could OME and the Dell FTP catalog be messing things up?
Multiple reboots were done on both OME server and remote server, even ran CCleaner after uninstalling DiskKeeper and Symantec Endpoint to hopefully clean up the registry and alleviate any issues preventing installation.
Anyhow on a side note - and I might start a new thread for this, but if we can use the MSI to do a full install, are there any arguments to do an uninstall of an older version, so we can then push a new version? The MSP's have not worked for any server I have tried, many different versions as well - even when trying a local manual install.
There is a button to get the latest catalog. Did you download the latest using this? If the server is properly discovered and inventoried, the compliance report should show exactly what patches are needed. What driver failed? There is also a whitepaper on delltechcenter/ome for updates/patch. Not sure if that will help.
I am getting that error in RM, not OME - but my concern was that if I could not use the FTP from dell in RM, maybe the same thing was happening in OME but with out the error message. I did the download of the cab file and import that into RM, and i tried the same thing in OME but it continued to say that there were new updates, even after hitting "Get latest"
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 13th, 2012 13:00
Hi and thanks for the post.
So, just looking over your notes here....
ok, try this:
1. Be sure you are doing a 'new' OMSA install (not an upgrade. that is, the target does not have OMSA on it already.
2. do not use the /qn flag...we're looking at a problem with some of the command line options.
Let me know.
Rob
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 13th, 2012 13:00
A few other notes:
1. msi is only used for clean installs and major upgrades.
2. msp is used for minor upgrades
3. if you keep running into trouble, you many need to manually copy the package over to the managed node and run it manually. Obviously defeats the purpose of the feature, but sometimes it reveals problems outside of OME that are easier to spot (like a bad package for example).
Hope this helps.
MikeyB13
33 Posts
0
January 17th, 2012 06:00
wow after writing a nice long response the page would not allow me to post and I had to start over so lets hope I don't forget anything.
I uninstalled 6.4, restarted, and then tried to deploy 6.5 with the msi, and no flags and got the same error message. I tried more than once and still it will not install.
I had previously manually installed 6.5, then uninstalled and installed 6.4 so I could test deployment (I thought I could use the msi for upgrades and you can do manually) so I know the packages are fine.
I went and downladed the "Dell Managed Node Service Pack for Windows V2247_A016.5.0" I have another server that is a R710, and has 6.3.0 - I tried to push that our using OME and it appeared to work as there was a Green Checmark, but upon reading the details of the job it said the patch was "not applicable" I logged onto that server, we to the Dell Drivers page and using the service tag, downladed the package again and upon trying to manually upgrade it, it gave the same message that the patch is not applicable. I am just straight frustrated now.
Is there a website or document that shows which version of OSMA is compatible with which servers, instead of having to read the documentation on each? It would be nice to know what can be installed on what server, as not everyone has all new 11G servers?
Also the next version of OME should have the ability to copy the details of the Task Execution History
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 17th, 2012 08:00
I'm wondering if you are using the right file for 6.5.
Is it this one?
OM-SrvAdmin-Dell-Web-WIN-6.5.0-2247_A01.10.exe
Extract files and use Sysmgmt.msi
If that _is_ the file, then I'm not sure what the trouble could be. You could try manually installing it on the managed node just to sanity check it.
(perhaps you tried this already)
Otherwise, I may have to direct you to support (800-945-3355 ) and we may need to collect a few logs to sort it out.
Thx
Rob
MikeyB13
33 Posts
0
January 17th, 2012 10:00
Downloaded that file and got the same error.... manually installing has always worked.
I will note that while trying to push out system updates I get this error message "File deploy command failed to execute with error message: Unable to access the specified share on the remote system"
I searched for this error and found some "answers" for ITA and tried them
Turn off IE ESC on USERS - as it was already disabled for Admins
Add my server to the trusted sites in IE
But nothing seems to have worked.
So it appears I can only push hardware updates to 1 server and cannot deploy or upgrade the version of OSMA for any server.... great!
And it is also numbingly annoying that I have to download 12 different versions of OSMA to install on our servers...
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 17th, 2012 12:00
Interesting. It seems like you don't have permissions on the target to update or deploy. But you said you checked the permissions. I wonder if you have to reboot the target(?) I would not think you would have to. But another thread on this seemed to indicate you might.
We will update the FAQ with some locations of where to get these packages. I know it is hard to keep track.
Otherwise, I will have to see if the support team can get logs, etc., on this issue.
Thanks,
Rob
MikeyB13
33 Posts
0
January 17th, 2012 19:00
Opps forgot to mention this, while I still cannot push OMSA to this server, after manually installing 6.5, I was able to install BIOS through OME. So it looks like there is something preventing the OMSA install. Some of the other Driver updates don't work, but I wondering if they are the correct drivers, as the BIOS info/driver version changed after the 6.5 manual install.
Could OME and the Dell FTP catalog be messing things up?
MikeyB13
33 Posts
0
January 17th, 2012 19:00
Multiple reboots were done on both OME server and remote server, even ran CCleaner after uninstalling DiskKeeper and Symantec Endpoint to hopefully clean up the registry and alleviate any issues preventing installation.
Anyhow on a side note - and I might start a new thread for this, but if we can use the MSI to do a full install, are there any arguments to do an uninstall of an older version, so we can then push a new version? The MSP's have not worked for any server I have tried, many different versions as well - even when trying a local manual install.
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 18th, 2012 08:00
Ok...remember msp files are only used for minor upgrades.
Looks like we'll have to punt you to support so we can dig deeper into why the OMSA push is not working right for you.
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 18th, 2012 08:00
There is a button to get the latest catalog. Did you download the latest using this? If the server is properly discovered and inventoried, the compliance report should show exactly what patches are needed. What driver failed? There is also a whitepaper on delltechcenter/ome for updates/patch. Not sure if that will help.
Rob
MikeyB13
33 Posts
0
January 18th, 2012 10:00
Manage-System Update-Select Catalog Source - FTP, and it says current catalog version is the latest.
I cannot download the repository from ftp.dell.com within Repository Manger....
Error loading source repository. Digital signature verification error for 'ftp://ftp.dell.com/catalog/catalog.cab'
I was using the MSP from 6.4->6.5 or 5.4->5.5 etc
The drivers that failed were NIC driver, NIC firmware, BIOS, and iDRAC
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 18th, 2012 12:00
See this link as well.
en.community.dell.com/.../19432091.aspx
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 18th, 2012 12:00
Hi,
So you are seeing this error in RM, not OME, correct?
I noticed this post on the Sys Mgt forum. I wonder if it is related.
en.community.dell.com/.../19432471.aspx
Can you use OME to download the catalog?
Rob
MikeyB13
33 Posts
0
January 19th, 2012 08:00
I am getting that error in RM, not OME - but my concern was that if I could not use the FTP from dell in RM, maybe the same thing was happening in OME but with out the error message. I did the download of the cab file and import that into RM, and i tried the same thing in OME but it continued to say that there were new updates, even after hitting "Get latest"
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 19th, 2012 09:00
What do you see when you do View Catalog? Mine says Release ID: W6YD5, date Jan 12, 2012. that is the latest.