IT Assistant issue

Thanks for posting!  Does the update bundle include an update for OMSA?  I have seen some recent problems with that particular update.  I suggest updating OMSA manually on your systems, then try the bundle again.

I am experiencing the same issue. and no, no OMSA is part of the bundle. Please advise.

If the bundle update doesn't work, try applying individual updates, and then you can find out which one is causing problems.  The second most likely candidate is Broadcom NIC drivers.  The fix for that is to uninstall the drivers and the Broadcom utility, then install the new drivers.  Unfortunately this is a manual procedure.

this just gets better and better <--- that was a sarcasm by the way...

i did them by hand, and still is saying the Firmware of the Brodcom card is on version 4.6 when i am sure i updated to 4.6.8. Even if y try to re-run the fimware update utility it tells me that the FW version are the same.

I even delete the whole server object from the devices list, re-scan and re-inventory....

clueless... and dissapointed.

any insights?

If you go find the firmware update for the NIC on the download site and instead of clicking Download Now, click More Download Options if available.  If there is a Hard drive or Floppy option, try that, and confirm what the readme file says the version number for the update is.

We are having this issue as well on all our PowerEdge 2950s.  There appears to be an issue with NETW_FRMW_WIN_R214709.EXE. (version 4.6.8) on our 64 bit Windows 2003 servers.  Whether it is installed via ITA or manually on the server, it always completes successfully.  IT Assistant never updates the version number when inventoried.  When we try to run it again manually on the server it says that version is already installed. 

Hi navymike ... welcome to my nightmare... lol

helloooo dell guys??? are you out there?

ok, I went thru this too, and here is the stink. ITA talks to your client system that is probably running openmanage server administrator(SA). SA runs an inventory collector called invcol.exe(IC). IC gathers all the system versions and passes that back to SA. SA then passes that back to ITA. Like this IC>SA>ITA. ITA pushes its updates in the opposite direction ITA>SA. When the updates run, the IC on the local system checks its versions and reports this back to SA and subsequently to ITA, but there are two caveats to this.
1. The IC only runs periodically, so if you run updates via ITA, then have ITA check again, you should wait at least an hour after updating to recheck the version.
2. The IC may be an older version and may not be recognizing and reporting the new version of the fw properly. This is why the update package sees you are at the right version, it also has an inventory collector in itself.

So the solution is to go get the latest version of the IC invcol.exe and put that on your SA (client) system and your ITA system just to be sure.
http://ftp.us.dell.com/cmsdk/ filename invCol_R2207005.exe (for Windows)

if you upgrade your server administrator to the latest version, your IC should be updated as well.

gnalweb, are you running  Trend Micro OfficeScan? i saw this because I'm a big Trend Micro fan. OfficeScan settings have to be changed.  ITA has a readme.txt and it says that tcp port 135 must be opened in the firewall and the temp folder for the user applying the updates has to be excluded from the real time scans. ex. C:\Documents and Settings\Administrator\Local Settings\Temp must be excluded if the user logs into the system as Administrator. i think you have to clear your temp folder of junk too because other attempts to run the updates may still be in there, and it will cause problems.