Oh yeah, and DCs don't have local security groups right?  That's a bit of a problem I think.

thx

Rob

Thanks for taking the time to post and provide feedback.

I will send your post off to the OME marketing team now so they can discuss with the engineers to see what can be done.   But as you note, at the moment, this is not supported.  Not sure if installing in a VM is an option for you.

I certainly understand the resource constraints of smaller shops.  And remember, even if we support a DC, memory and core requirements (see readme :-) ) come into play as well.  Even with SQL Express (since it is CPU limited), the box can get pretty busy.

Thanks again,

Rob

Thanks for the quick response!

Correct, they don't have local security groups, but they can use groups on the domain.  For instance, for some programs that try to create local groups as part of the installation (e.g. SQL 2005), these groups are created on the domain instead and work fine.  I imagine it depends on what calls the application is making to create the groups/accounts as to if this automatically allows for creating on the domain when on a DC, or if this has to be coded separately.  I would think it could always be an option to have the user create the required security manually on the domain and tell OME which ones to use.

In the past with ITA, performance has never really been an issue for us.  We mainly use it for hardware alerting and not for deploying packages as with the smaller environments its quicker just to deploy what we want manually.  ITA has always worked great as a SNMP Trap alerter (more cost-effective and works better with Dell hardware than most everything else I've tried), except for the fact that you couldn't really import third-party MIBs.  I've been looking forward to OME and the advancements in this area.

A VM is an option in some cases, but not really ideal for us when we have another physical server.  The idea is if the critical server that runs the VMs goes down or has a major issue we can still be alerted to that via the monitoring software on the second server.  If it was running in a VM on the main server, without a cluster to failover the VM it would go down with the server without sending an alert.

It's fine that OME is designed for multi-server installations, but why then is the ProSupport Active Server Monitoring being moved to OME from December? Is Dell now saying they are not interested in SMBs? Will all our customers get a refund for the service that they cannot longer use?

Poynter,

Thanks for taking the time to post your feedback and concerns around the ProSupport Monitoring.

Can you please contact the following email address directly so that they can ensure your concerns are understood?

PSM_Scheduler@Dell.com 

Best regards,
Rob

Thanks for your feedback. We'll definitely review the requirement for OME to install on DCs for the future release.

Regards

Abhijit

I am in the same boat at the moment.  I have a single-server client that wishes to continue using Proactive Systems Management, which is being deprecated in favor of a plugin for OME.  Since OME doesn't currently run on DCs and the current iteration of PSM will apparently be killed off at the end of the year, I would like to know what Dell's proposed solution is here.  If PSM can continue without OME that'd be my preference since I have no interest in installing a replacement for IT Assistant to support a single-server environment, but if there won't be an alternative, OME really needs to support domain controllers before this cutover.  We're just over 2 months out, and especially considering that the holidays are coming up, there isn't much time to get this together.

I will be seriously disappointed with Dell if they kill off PSM without providing a viable migration option for SMBs that have no need or to run additional servers or VMs just to support OME.

So for us (in the support forum), we try to be definitive in our technical answers, but we don't have as much detail as to future features or roadmaps.

We _do_ however send this type of feedback to the appropriate marketing teams so they get to see your concerns first-hand.

Thanks,

Rob

That's a very non-committal response.  Can we expect that release in time to ensure uninterrupted proactive monitoring support on DCs in single-server environments?

It's been over two weeks since the last update on this, and there's less than a month before the holiday season begins, after which support for the current Proactive Systems Management infrastructure will be discontinued.  Is there any information at all yet on how single-server DC environments will be supported?  I don't really think marketing teams are the proper party to be forwarding these concerns to (perhaps software engineering?), but any word at all would be better than telling us that a solution we're using is going away in short order with no viable replacement options at the moment.

Hi there.

Marketing == Product Owner.  The terminology varies from company to company.  Not software eng for sure, since they build out products based on business requirements. :-)

I think the team tried to reach out to you a while back and provide some more background and detail.  Let me know if you don't hear back.

Rob

Hi and thanks for the post.

OME is our 1 to many console and, when installed on a server, it will monitor multiple "managed nodes" (e.g., servers, storage, switches, etc.).

As indicated, we have passed along the feedback on DC and it is being reviewed and considered as a feature in a future release.

Some folks will run OME in a VM.  Others, if they just have a _single_ server to manage will use Dell Server Administrator (OMSA) which is our 1 to 1 management software.  And depending on if you have an iDrac, there are options there as well.

Thanks and regards,

Rob

en.community.dell.com/.../1760.openmanage-server-administrator-omsa.aspx

Who can get in contact with to arrange a refund on the ProSupport that our customers can no longer use?

I think folks have been using the PSM email address from earlier in the thread to get some more specifics as to the PSM support window.    Can you see if that gets you some more details on the EOL schedule for PSM?

thanks,

Rob