Now that VSAE is available for recent versions of Visual Studio we are missing a 64bit version of the extensions. MP Simulator (32bit) won't work when run on a 64bit OS with a 64bit SCOM agent installed.
In the past Microsoft had made available versions for both architectures.54 votes
VSAE 64 bit is released now.
Why should we not being able to vote for all ideas/feedback if we'd like to support them?
With the current limitation (and the fact that I near to never received votes back) the platform is not useful to me and I don't feel participation makes sense.
Here is the feedback from UserVoice itself:
"Hi Patrick - voting limitations is a feature imposed by the site administrator. If you wish for them to disable this feature, I recommend creating an idea on their web portal requesting them to remove this functionality."
Please disable it.
Patrick2 votescompleted · AdminAakash Basavaraj[MSFT] (Program Manager, Microsoft System Center Operations Manager) responded
We have increased the number of Votes from 10 to 20. Urge all users to vote on highly impactful / important ideas.
Any idea when is RHEL 8 going to be supported? My customers are already deploying servers in RHEL8 and we cannot provide monitoring for them.135 votes
VSAE should support Visual Studio 2019 and System Center 2019108 votes
When rolling out SSRS 2017, once you add the SCOM Report Server role to it, the Reports page only gives a 500 error. Reports work in the console, but can no longer get to the web interface.110 votes
We need support in SCOM 2019 for agents that are running Server 2012. And, really, for 2008R2 agents. I understand that 2008 is EOL in January, but it is now March (we also have plenty of 2008 in production) At this point we cannot upgrade to SCOM 2019 without at least 2012 support, and preferably 2008R2.113 votescompleted · AdminAditya Goda (Product Manager, Microsoft System Center Operations Manager) responded
SCOM 2019 now supports monitoring of Windows Server 2012. SCOM 2019 systems requirement documentation has been updated to reflect the same.
Current design for node location property is to show the last known value. For example a device is added and has a location this location is shown. If the location field is made empty the property in SCOM is not updated. This behavior is a deviation from the normal behavior for object properties as they do reflect the current effecitve data. Please remove this deviation and always show the current effective value, if we want to know a historical value we do have a data warehouse and reporting capabilities.32 votes
SCOM 2019 UR1 has the fix. Thanks
With SCOM Always On sql architecture. Whenever a maintenance schedule is created it is not replicated to secondary DB. This requires manual effort with DB permissions to replicate the SQL agent job. The schedule is not effective until its replicated which eliminates the self service feature for end users. Not every one has DB permissions.50 votescompleted · AdminAditya Goda (Product Manager, Microsoft System Center Operations Manager) responded
This has been fixed with SCOM 2019.
There is a S2D management pack for SCOM2016 but it doesn't appear to be working the same in SCOM2019. Any plans to monitor S2D in SCOM2019 with management packs?1 vote
Monitoring of Azure Metric Alerts hasn't been working since early this year. Objects are discovered fine, but whenever an Azure Metric Alert fires, the change is not comming down to the SCOM environment objects, and thus no SCOM alert is generated.3 votes
Please try out the latest version https://www.microsoft.com/en-us/download/details.aspx?id=50013
There are a whole ton of great SCOM blogs out there. There are also a whole great number of blogs for other products like config manager on techblogs but nothing for SCOM. Could we start a blog? https://techcommunity.microsoft.com/t5/custom/page/page-id/Blogs8 votes
Monitoring of SLES 15 systems is currently not possible with SCOM 2016. Please provide an agent and management pack to monitor SLES 15 systems with SCOM 2016 at the same level as SLES 11 and 12.28 votes
We have installed & imported Azure SCOM Management Pack 184.108.40.206 everything seems to be fine post installation. We were able to integrate subscription as per suggested steps with required permission. But once we start configuring metrics for CPU, Memory, Disk Utilization that's where things started to look strange. we were not able to figured it out what should be our next course of action to address this challenge. Even we could not find any fruitful information after doing some research and then we decided to raise a case (119031923002943) specific to this challenge and post our conversation with Engineer we came to know that this is product limitation instead of a issue. I would request concern people\team to take this as a feedback and enhance the Management Pack capabilities to increase SCOM's scope in terms of Azure subscription monitoring through SCOM 2016. Because we as customer investing some much money and we don't value for our money then it is satisficing from customer point of view.
We have installed & imported Azure SCOM Management Pack 220.127.116.11 everything seems to be fine post installation. We were able to integrate subscription as per suggested steps with required permission. But once we start configuring metrics for CPU, Memory, Disk Utilization that's where things started to look strange. we were not able to figured it out what should be our next course of action to address this challenge. Even we could not find any fruitful information after doing some research and then we decided to raise a case (119031923002943) specific to this challenge and post our conversation with Engineer we…4 votes
Azure MP supports metrics collection as CPU, Disk utilization etc. Latest version is available here
Correct the fact that all UNIX/Linux-based monitor health states are reset when a Management Server (or Gateway) is rebooted.
When a Management Server (or Gateway) is rebooted, all UNIX/Linux-based monitor health states are reset, resulting in the subsequent re-generation of a slew of alerts for all related x-plat agents118 votes
In SCOM 2019 no new alerts will be created during failover for Unix/Linux agents. We have documented this new feature in What’s New in SCOM 2019. Please go through the details there.
Many Enterprise organisations are still reliant on File Services such as DFS-R and need to effectively monitor it. With no new release of the DFS Replication Management pack to support Windows Server 2016 and 2019, Organisations are failing to monitor key parts of their infrastructure, with failures affecting hundreds of users.
Please provide further support for DFS-R Monitoring33 votes
These two management packs break each other when deployed together. BOTH management packs require workarounds to fix an issue with Microsoft.IdentityModel.Clients.ActiveDirectory, and they are each dependent upon 2 different versions of that assembly, so it is impossible to configure both at the same time without continuously swapping out these .dlls. Additionally, both management packs come up with many missing assemblies, which have to be copied from other locations to get them to work at all. Where is the quality control?2 votes
We have fixed this, Apology for this bad bug.
To exclude an instance or database from discovery, you have to either specify the full name or use * to exclude everything. It would be much more use to be able to exclude '_clone' or 'test*'.114 votescompleted · AdminAakash Basavaraj[MSFT] (Program Manager, Microsoft System Center Operations Manager) responded
SQL Server MP (for 2012 and up) is the successor of SQL Server 2017+ MP and has this feature from its first version – 18.104.22.168, April 2019.
Originally, this feature was presented in June 2018 within the last RTM release of SQL Server 2017+ MP (v.22.214.171.124).
The APM component (regardless of APM being enabled) frequently breaks .NET applications. Re-installing agent with NOAPM=1 means we cannot leverage the SCOM console to deploy agents. Request155 votescompleted · AdminAditya Goda (Product Manager, Microsoft System Center Operations Manager) responded
This ask has been shipped with SCOM 1807, which enables you to disable the APM component when you deploy the Operations Manager agent from Discovery Wizard in the console, when performing a repair of the agent from the Operations console, and similarly controlling behavior when using the PowerShell cmdlets Install-SCOMAgent and Repair-SCOMAgent.
This feature ask will also be shipped in SCOM 2019.
Issues related to APM, crashing the IIS application pools has been fixed and shipped with SCOM 2016 UR6: https://support.microsoft.com/en-us/help/4459897/update-rollup-6-for-system-center-2016-operations-manager#enable
Fix to these issues, will also be available in SCOM 2019.
This was semi-dormant as a ticket on Developer Community for two months before it was very recently closed: https://developercommunity.visualstudio.com/content/problem/318019/visual-studio-crashes-using-scom-vsae.html
It is basically impossible to with with MP projects in VS 15.8.3 and later.
I need to be able to use the later versions of Visual Studio 2017 AND VSAE together, and I cannot really have a bunch of versions installed side-by-side. (Already running VS2015 besides VS2017).3 votes
Thanks for reporting. This is fixed now.
I have just updated to this latest version of the 'Management Pack Recommendations MP' via the Updates and Recommendations feature in SCOM2016. I now have a couple of hundred powershell failed to run warnings from a large number of servers for 'Lightweight non server roles discovery' filling my alerts pane. Previously zero script errors.
So far been unsuccessful in resolving this issue.15 votes
- Don't see your idea?