Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

martinasher

6 Posts

6134

September 19th, 2007 09:00

Landesk and OMSA software conflicts

We have 500 + Dell poweredge servers from X6XX models to X9XX.
We use the Current Dell OM installation disks to build our servers we also install OMSA.
 
The business has decided and has implemented a full Landesk installation.
Once the Landesk agent is installed the "Hardware Log" tab is missing from OMSA, also missing are various "config" links from within OMSA.
On occasions the hardware log tab will be visible, I think this is due to which services start first, generally the OMSA implementation is affected.
Reinstallation of OMSA sometimes rectifies the issue for a reboot or two, the OMSA version is also irrelevant.
We do not get hardware monitoring via IT Assistant with the hardware log disabled we have to monitor the system event logs or resort to checking the lights on the servers.
Has anyone come across this and rectified the issues?
We have a fault logged with Landesk, they have not been successful in rectifying it yet, the latest client gets rid of the "WDTRESET" error but does not correct the clash with OMSA.
 

GeorgeBC

68 Posts

September 24th, 2007 21:00

Thank you for posting. Unfortunately if OMSA is conflicting with another product, there most likely will not be a fix provided by Dell Software Engineers. The best action to take is what you have already done, and contact LanDesk. They may be able to contact our Software Team to discuss the conflict.
 
Additionally, find out if LanDesk is using port 1311. OMSA uses port 1311, so there could be a port conflict. Most likely the conflict is the way LanDesk and OMSA communicate with the Dell hardware, and they are just butting heads. Thank you.

martinasher

6 Posts

September 25th, 2007 08:00

Very little help from Dell, I raised a support call a couple of months ago but due to workload I was unable to concentrate on it, wound up closing the call.
 
Landesk keep promising that the next agent will fix it, it never does!
 
It looks like we have fixed it.
If the landesk agent starts after OMSA the systems work correctly, we created a dependency for the landesk services to start after the OMSA services that seems to have cured it, just got to get the changes rolled out to all of the other servers now. Just got to make sure that earlier versions of OMSA use the same services.
 

Was this post helpful?

View All

No Events found!

Top