SCOM 2012 R2 agent with SCOM 2007 R2?

Server: SCOM 2007 R2 (now); eventual upgrade to SCOM 2012 R2
OS to monitor: Windows Server 2012
I understand SCOM 2012 agents can be installed on Windows Server 2012 and report back to SCOM 2007 R2 MGs.
I haven't been able to find documentation for or against whether SCOM 2012 R2 agents can be installed on Windows Server 2012 and can report back to SCOM 2007 R2 MGs... Is this supported?
I can't find anything on any specific CU level that might be required on SCOM 2007 R2 to support this.

Hi,
I have not found any document talking about this. The only thing I can find is SCCM 2012 r2 agent can talk with SCCM 2012 SP1.
Juke Chou
TechNet Community Support

Similar Messages

Upgrading SCOM 2012 SP1 agent to SCOM 2012 R2

Hello All
We have created a new SCOM 2012 R2 environment and now planning to upgrade our agents which are in SCOM 2012 SP1 environment . We want to keep the agents dual homed for some time . I would like to know if there is any kind of automation/script that someone
has already made to upgrade SCOM agent from SP1 to R2 ,and at the same time have it dual homed (pointing to 2 MG)

You may try
1) upgrade the SCOM agent by
msiexec /i MOMAgent.msi /qn /l*v D:\logs\AgentUpgrade.log AcceptEndUserLicenseAgreement=1
2) Add additional management group y using following vb script
Option Explicit
Dim objMSConfig
Set objMSConfig = CreateObject("AgentConfigManager.MgmtSvcCfg")
‘Add a management group
Call objMSConfig.AddManagementGroup ("MyManagementGroupToAdd", "company.sm.net",5723)
For detail, pls. refer to
http://technet.microsoft.com/en-us/library/jj899848.aspx
http://msdn.microsoft.com/en-us/library/hh329017.aspx
Roger

SCOM 2012 R2 agent upgrade fails crippling agents

Running into a large amount of SCOM agents that are failing the upgrade from 2012 SP1 to R2 and would appreciate any feedback from my SCOM community colleagues. Warning this issue is not for the faint of heart.
Plan:
I am in the process of upgrading 1900 manually installed SCOM 2012 SP1 agents to R2. I am using SCCM to deliver the upgrade using the standard sanctioned upgrade parameters.
Momagent.msi /qn /l*v %SystemDrive%\SCOM2012AgentUpgrade.log AcceptEndUserLicenseAgreement=1
Problem:
I have run into a problem where on a larger group of systems, 165 servers, where the upgrade fails and leaves the agent in a crippled state. At this point the agent cannot be removed cleanly via add remove, nor can a straight install of the agent
be done. What is required is a manual removal of registry keys and then a clean install of the agent can be performed to remediate. This is no problem and I am able to do this. (Note: all other methods of agent removal did not work ie:
Cleanmom.exe utility or add remove)
Task:
Seeing that we need to do agent upgrades in the future it would be great to know why this happened so we can plan for this in the future.
Notes:
Seems like a random sample of servers (2003/2008) with different applications running on them so that doesn't help in narrowing things down.
Looking at the MSI log, I see a common issue among systems that had this problem.
******* Product: {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'DisableMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Looking for sourcelist for product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Adding {387306D9-78CE-4E0E-B952-28A50CC8B3EE}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Now checking product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media is enabled for product.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Trying source C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 2203 2: C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\MOMAgent.msi 3: -2147287037
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing net source list.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing media source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Processing URL source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Failed to resolve source
MSI (s) (7C:8C) [08:08:44:744]: Note: 1: 1714 2: Microsoft Monitoring Agent 3: 1612
CustomAction returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (7C:8C) [08:08:44:744]: Product: Microsoft Monitoring Agent -- Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Action ended 8:08:44: RemoveExistingProducts. Return value 3.
Action ended 8:08:44: INSTALL. Return value 3.
Ok so the obvious is that the installer is looking for original source installation files and not able to find them. What is surprising to me however is that the product references a 32 bit scom agent guid
387306D9-78CE-4E0E-B952-28A50CC8B3EE, however this is a 64 bit machine. Our build process dictates that a 64 bit machine only receive a 64 bit SCOM agent.
Doing a search on this product guid I realized I skipped some other references at the top of the MSI log that might offer some more explanation...
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_OM12_SP1_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Modifying OM_OM12_SP1_AGENT_FOUND property. Its current value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'. Its new value: '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_OM_AGENT_FOUND
Action ended 8:08:11: FindRelatedProducts. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_OM_AGENT_FOUND.
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_MOMV3_AGENT_FOUND
Action ended 8:08:11: _Set_OM_AGENT_FOUND. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding MOMV3_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_MOMV3_AGENT_FOUND.
Well that is interesting, seems to me that in the first line the MSI installer reads the OM_OM12_SP1_AGENT_FOUND property and identifies this with a 64 bit agent guid (8B21425D-02F3-4B80-88CE-8F79B320D330), but then appends
the 32 bit guid at the end (387306D9-78CE-4E0E-B952-28A50CC8B3EE). This is the point of my confusion and my suspicion as the cause of the problem I am having.
Concluding thoughts:
Why does the installer seems to first recognizes a 64 bit agent, but then later changes it's property to include a 32 bit agent guid.  Could a 32 bit agent have got on this 64 bit server based on the details of this log? Would this
cause my agents to fail the upgrade? I think so, but looking to bounce this over to another fellow SCOM colleague who may have wrestled with this before.
Thanks in advance if you took the time to read this and think about it. Extra points if you have any extra thoughts!
Keith

Hi,
Have you used Requirement to limit the platform when you deploy application with SCCM.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCOM 2012 R2 Agent Issue: Error 25211.Failed to install performance counters.. Error Code: -2147024809

Hi All,
I'm trying to deploy SCOM 2012 R2 agent onto a domain controller and I get the following error "Product: Microsoft Monitoring Agent -- Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.)."
I've installed the agent successfully onto 4 other domain controllers with out any issues.</p><p>The domain controllers are all VM's running on VMWare and are Windows Server 2012 R2.
I've rebuilt the Perfmon Counters based on this article: https://support.microsoft.com/en-us/kb/2554336?a=wsignin1.0
I've also enabled verbose logging on the msi installation:
InstallHSPerfCounters: Custom Action Data. C:\Program Files\Microsoft Monitoring Agent\Agent\
InstallHSPerfCounters: Installing agent perf counters.
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
Any help on this would be great.

Hi Stefan,
I've successfully installed the agent. The server needed a reboot after fixing the corrupt perfmon counters.
I know have a issue with the agent on the domain controller. It kkeeps on greying out and have used hslockdown to allow the local system access by using the following command.
HSLockdown.exe "ManagementGroupName" /A "NT AUTHORITY\Authenticated Users"
Further digging into the issue I see in the SCOM Management Server the following error "The entity servername is not heartbeating"
Written a SQL query to gather more information. SQL query I used is:
SELECT
ME.FullName,
HSO.StartDateTime AS OutageStartDateTime,
DATEDIFF (DD, hso.StartDateTime, GETDATE()) AS OutageDays,
HSO.ReasonCode,
DS.Name AS ReasonString
FROM vManagedEntity AS ME
INNER JOIN vHealthServiceOutage AS HSO ON HSO.ManagedEntityRowId = ME.ManagedEntityRowId
INNER JOIN vStringResource AS SR ON HSO.ReasonCode =
REPLACE(LEFT(SR.StringResourceSystemName, LEN(SR.StringResourceSystemName)
– CHARINDEX(‘.’, REVERSE(SR.StringResourceSystemName))), ‘System.Availability.StateData.Reasons.’, ”)
INNER JOIN vDisplayString AS DS ON DS.ElementGuid = SR.StringResourceGuid
WHERE (SR.StringResourceSystemName LIKE ‘System.Availability.StateData.Reasons.[0-9]%’)
AND DS.LanguageCode = ‘ENU’
AND ME.FullName like ‘%SERVER NAME%’ –Change name here or leave %% for ALL SERVERS
ORDER BY OutageStartDateTime
This gives me the following reason behind the failure : "The heartbeat from System Center Management Service is missing."
Have I missed anything? The agent is running fine, however SCOM is reporting that the heartbeat is missing.
Any help on this would be great.

SCOM 2012 R2 Agent Deployment - Uninstall Old and Install New

By chance anyone come up with a scripted method for removing an existing SCOM 2012 SP1 agent and installing a new 2012 R2 agent? While I've come across a few scripts I'm trying to kill a few birds with one stone. This is a cross-domain attempt where the
SCOM servers sit in one domain and the member servers are scattered across multiple domains. Member servers range from Windows Server 2003, 2008, and 2012. In most cases the servers have the 2012 SP1 agent installed and in some cases there are multiple management
groups from previous SCOM standups. In addition there's a separate DEV SCOM 2012 R2 environment to manage DEV/QA servers. Active Directory Integration is configured and I have the necessary security groups created. There is a group policy created which is
filtered to just that security group. So the plan is to simply drop the servers into the correct group and have the agent installed via group policy start up script. ADI should have DEV servers appear in DEV SCOM and PROD in PROD SCOM.
Although there are ways to facilitate agent deployment via the console I need to perform a staged migration against a ton of server so as to not impact the existing production environment. So I'd rather do this remotely to pre-selected servers. This process
should involve removing the existing agent, installing the new one, and if possible removing any existing management groups. So far I've come up with the following:
Uninstall SCOM Agent:
%WinDir%\System32\msiexec.exe /x <path>\MOMAgent.msi /qb
Install SCOM Agent:
msiexec.exe /i \\path\Directory\MOMAgent.msi /qn /l*v \logs\MOMAgent_install.log USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name> MANAGEMENT_SERVER_DNS=<MSDNSName> ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER=<AccountUser> ACTIONSDOMAIN=<AccountDomain>
ACTIONSPASSWORD=<AccountPassword>
Remove Management Group via Script
http://gallery.technet.microsoft.com/Remove-a-Management-group-336c849a/view/Discussions#content
I'm guessing this wheel has already been invented or maybe there's a better way. So I'm open to ideas or suggestions.
Any responses appreciated.

Wow! 4 days and no responses, not good Microsoft SCOM Community. So here's a status on this issue.
As stated I have Active Directory Integration configured which means:
I see the OperationsManager container in AD: dev_scom
I see the HealthService SCP and separate OU's for each of my management servers.
I have an ADI security group containing my management servers and scom action account.
I have an Agent security group which will contain servers the scom agent will be deployed via group policy.
I also have an AD LDAP query set to target the SCOM agent group.
(&(objectCategory=group)(name=DSCOM_ADI))
I finally get the script to install via the following steps:
Reference:
http://technet.microsoft.com/en-us/library/cc754995.aspx
http://technet.microsoft.com/en-us/library/cc770556.aspx
http://blog.coretech.dk/msk/install-a-scom-2012-agent-silent/
1. Launch Notepad ++ and enter the following:
msiexec /i
\\server.yourdomain.com\opsmgragent\%Processor_Architecture%\MOMAgent.msi USE_SETTINGS_FROM_AD=1 MANAGEMENT_GROUP=DEV_SCOM MANAGEMENT_SERVER_DNS=YourSCOMsrvr1.yourdomain.com ACTIONS_USE_COMPUTER_ACCOUNT=0 USE_MANUALLY_SPECIFIED_SETTINGS=0 ACTIONSUSER=svc_dscom
ACTIONSDOMAIN=yourdomain ACTIONSPASSWORD=YourPassword! AcceptEndUserLicenseAgreement=1 /qn /l*v c:\scom2012r2mmainstall.log
2. Save the script to a name of your choice. For me it's installdopsmgragent.cmd. Watch the extensions as you may end up saving it as installdopsmgragent.cmd.txt.
Note: Make note of this steps in the reference articles listed above:
"In the Add a Script dialog box, do the following:
In the Script Name box, type the path to the script, or click Browse to search for the script file in the Netlogon shared folder on the domain controller."
It's been a while since having to use a startup script so it took me a minute to figure this out. "getting too old 'fer this..."
3. Copy the script to the Netlogon folder which is located in the following directory on my Windows 2012 server: E:\SYSVOL\sysvol\yourdomain.com\scripts
4. Launch the group policy management console, create a new policy, edit it, and navigate to the following location:
Computer Configuration > Policies > Windows Settings > Scripts (Startup/Shutdown)
5. Double-click Startup to open the Startup Properties window.
6. Click Add and browse to the location of the script which you copied to the Netlogon share.
7. Click OK to close the Startup Properties window.
8. Close the Group Policy Management Editor.
9. Link the policy to an OU containing the servers.
10. Add the SCOM Agent group to the Security Filtering area of the group policy. I also remove Authenticated Users.
Note: make sure you have a few test servers in your Agent security group.
11. Drop to a command line and run gpupdate /force. You can also use gpupdate /force /sync but you will have to reboot the box you're running this from.
12. Log into one of the servers you have slated to deploy the agent to, drop to a command line, and run the same gpupdate command.
13. Follow this with a gpresult /r command to ensure that you see the policy applied in the Computer Settings area.
14. Reboot the server and you should see the startup script run.
15. Log into the server and launch the Control Panel.
16. If all went well you'll see the "Microsoft Monitoring Agent" icon.
17. Launch Event Viewer, navigate to the Operations Manager events node located under Applications and Services Logs and validate the logs.
17. If all didn't go well check the error log located, for me, on the C:\scom2012r2mmainstall.log
My issue: I don't see the management info in the Agent properties.
I installed this last night and waited until the next day still no changes. Event logs show the following:
Event ID: 2011 The Health Service did not find any policy in Active Directory
Event ID: 2003 No management groups were started. This may either be because no management groups are currently configured or a configured management group failed to start. The Health Service will wait for policy from Active Directory configuring
a management group to run.
I see the HealthService is Running in Task Manager on this server and of course I don't see anything listed in the Management Groups registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\
I don't want to manually add the management group info. Checking as I may have missed something in one of the switches.
Any responses appreciated.

Error 1723 when removing scom 2012 sp1 agent

Hi All,
I am trying to remove the scom 2012 SP1 agent from a machine and i get an error - 'Error 1723. There is a problem
with this Windows Installer package. A DLL required for this install to complete could not be run.
Any idea how can i remove the agent from the box. Let me now if any other info required to give a hint to the problem.
Durgesh Kumar

Hi,
Reinstall the agent, and the uninstall ? If possible, reboot the server and then uninstall?
Same issue here:
http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_install/get-error-1723-there-is-a-problem-with-windows/3d68fc4b-c968-4796-a270-27027a52de3f?page=2
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The problem with forecast reports in SCOM 2012 after integration with VMM 2012

Hello.
I have problem with forecast reports in SCOM 2012 after integration with VMM 2012. All other reports (not forecasting) works fine. For example, report “Host Group Forecasting” don’t work. The report is generated, but I have error: “Subreport
could not be shown”. I find only errors in SQL Server Reporting logs like this:
library!ReportServer_0-13!1758!06/26/2012-18:26:23:: i INFO: RenderForNewSession('/Microsoft.SystemCenter.VirtualMachineManager.2012.Reports/Microsoft.SystemCenter.VirtualMachineManager.2012.Report.ForecastHostGroup')
processing!ReportServer_0-13!1758!06/26/2012-18:26:28:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Не удалось выполнить
запрос для набора данных "DiskSpaceUsageForecasting". ---> Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Execution of the managed stored procedure GetTimeSeriesForecast failed with the following error: Exception has been thrown by
the target of an invocation..
Query (5, 58) Parser: The syntax for '6' is incorrect.
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteTabular(CommandBehavior behavior, ICommandContentProvider contentProvider,
AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
   at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.ReportingServices.DataExtensions.AdoMdCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeDataSet.RunEmbeddedQuery(Boolean& readerExtensionsSupported, Boolean& readerFieldProperties, List`1 queryParams, Object[] paramValues)
   --- End of inner exception stack trace ---;
The Russian string “Не удалось
выполнить запрос для набора данных "DiskSpaceUsageForecasting"” is translated to “Could not execute query for data set "DiskSpaceUsageForecasting"”.
I have clean installation SCOM 2012 RU1, VMM 2012 RU1. Integration SCOM with VMM work fine.
SQL collation for all SQL DB instances (SCOM and VMM and SCOM reporting) – “SQL_Latin1_General_CP1_CI_AS”
SQL Analysis service: SQL collation – “Latin1_General” ; language for the server – English (United States)
I think the problem in regional settings. By my opinion there are two possible mistakes:
SQL collation for all SQL DB instances. May be need use “Latin1_General_CI_AS”
as provided by
http://blogs.technet.com/b/momteam/archive/2012/05/25/clarification-on-sql-server-collation-requirements-for-system-center-2012.aspx
Need change regional setting. Question is for what (OS regional setting, SQL Analysis service settings,…) ?

Error: Subreport could not be shown
Opening a report for Client Security might result in the following error being displayed in one or more areas of the report: "Error: Subreport could not be shown."
Background
There are two possible reasons for this error:
1. Wrong location   The reporting server is pointing to the wrong computer running SQL Server or a SQL Server instance.
2. Insufficient permissions   The account configured (in SQL Server Reporting Services) to connect to the reporting database does not have appropriate permissions for the database.
Solution
To determine which reason is causing the error, attempt to directly open the subreport reporting the error, by clicking the name of the subreport.
If the reporting server is pointing to a wrong location, the report displays an error similar to the following:
Error message
An error has occurred during report processing.
Cannot create a connection to data source 'SystemCenterReporting'. Cannot open database "SystemCenterReporting" requested by the login. The login failed. Login failed for user username.
To verify the correct SQL Server computer and instance path
In Report Manager, navigate to the report generating the error and click the Properties tab.
Click Data Sources and under a Shared data source, note the path.
Open the reporting Web site. If you chose the default virtual directory for reports, the URL is: http://hostname/Reports/
If you chose to secure the viewing of reports with HTTPS, the URL is: https://hostname/Reports/
Click SCDW.
In the Connection type list, ensure that Microsoft SQL Server is selected.
In the Connection string box, ensure that the correct SQL Server computer and instance name are entered.
Note:
A period (.) denotes the local computer.
If the account has insufficient permissions, the report displays an error similar to the following:
Error message
An error has occurred during report processing. (rsProcessingAborted) Query execution failed for data set 'DSDashboardComputersTrend'. (rsErrorExecutingCommand) EXECUTE permission denied on object 'prSAS_UX_DashboardComputersTrend', database 'SystemCenterReporting',
schema 'dbo'.
To determine if you are experiencing the SQL Server permissions issue
Open the reporting Web site. If you chose the default virtual directory for reports, the URL is:http://hostname/Reportserver/
If you chose to secure the viewing of reports with HTTPS, the URL is:https://hostname/Reportserver/
Click Microsoft Operations Manager Reporting, click Microsoft Forefront Client Security, and scroll to DashboardComputersTrend.
Click DashboardComputersTrend.
If you are experiencing a SQL Server permissions issue, an error similar to the preceding error appears.
To grant permissions to the SQL Server computer
1. In Report Manager, click SCDW and note the account in the Connect using section. This is the account under which the database is contacted.
2. On the server with the System Center Reporting database, start SQL Server Management Studio.
3. In the tree, expand Security, and then expand Logins. Do one of the following:
If the user account is listed, right-click the account, click Properties, and then go to step 5.
If the user account is not listed, right-click Logins and choose New Login.
4. In the Login name box, enter the user account (domain\username).
5. In the Login Properties dialog box, click User Mapping, and then under Users mapped to this login, select the System Center Reporting check box.
6. Under Database role membership for: System Center Reporting, select the db_owner check box, and then click OK.
Thanks,
Yog Li
TechNet Community Support

How to install SCOM 2012 R2 agent on workgroup Linux machine.

Hello Experts,
Please help in installing SCOM 2012 R2 agent on WorkGroup Linux machine.
Please provide links for steps process so we can proceed easily for installation without much searching.
Thanks
Richa KM

Hi
The beauty deploying SCOM agents to Linux Systems is that it does not depend on Kerberos. If the Linux Systems is Domain joined or not does not matter. In both cases the authentication occurs using certificates which are signed by the SCOM Servers. You Need
just to make sure that:
Port 22 (SSH) and 1270 (WS-Man) are open / reachable
DNS works both ways and pointers (reverse look up) is configured.
Make sure the Linux System Name is same as DNS if not check
http://stefanroth.net/2014/02/03/scom-linux-agent-deployment-signed-certificate-verification-operation-was-not-successful/
Make sure you Setup the RunAs account properly
http://stefanroth.net/2012/03/15/scom-2012-linux-monitoring-lab-part-1-setup-suse-11-1/
If you consider these points everything should work fine...
Cheers,
Stefan
Blog: http://blog.scomfaq.ch

SCOM 2012 ACS agent Failed connecting to collector

Hi,
We are using SCOM 2012 on Windows 2012, when installing the SCOM agent with Audit Collection Services the ACS forwarder will report in as healthy until reboot, after reboot the forwarder state changes to failed to connect to collector. (XXX's are redacted
system information).
Forwarder unsuccessfully tried to connect to the following collector(s): XXXXXXXX:51909, status: 0x80090322 (TCP connect), source: registry addresses tried: XXX.XXX.XXX.XXX:51909 If the list of collectors is blank, then AdtAgent was unable to locate a collector.
Common reasons for this message are: The machine(s) listed is not online AdtServer is not running on the machine(s) listed AdtServer on the machine(s) listed is not listening on the specified port TCP connectivity to the AdtServer machine is blocked by firewall,
IPSec, or other filtering mechanism AdtServer on the machine(s) listed actively refused the connection (due to policy or current activity load) For detailed failure information, enable trace logging using the TraceFlags registry key and examine the AdtAgent.log
in the \temp subdirectory of the Windows directory.
Enabling trace logging repeats the same error, unable to connect to server. We have verified, the IP is correct, the FQDN is correct and has a forward and reverse lookup record. We have also verified via telnet that port 51909 is open in both directions.
Any help would be appreciated.

If you are 100% sure port 51909 is open at Collector's side (you don't need to open it on ACS forwarder) and there's no additional firewall somewhere at the middle use wireshark and capture what's going on.
--- Jeff (Netwrix)

SCOM 2012 Reporting Components with a shared SQL cluster

Hi, we are planning to install SCOM 2012 but i am a bit confused around the reporting components.
We have a shared SQL Enterprise cluster with multiple instances which we would like to use for our OperationsMananger and OperationsManagerDW databases. However after trying a test SCOM deployment, installing the SCOM reporting components on a VM requires
a local running copy of SQL reporting services.
Is this true? It seems ludicrous to have to purchase an additional license of SQL just to run the reporting components of SCOM. We have spent a lot of money on our SQL cluster and we would like to use it. We dont want to install the SCOM reporting components
on the shared SQL cluster.
If this is true, can you tell me which license of SQL we require? Just to run SQL reporting services on a VM should just require a standard SQL license, right?
Also if we have to purchase a SQL license for this standalone VM, would you recommend having the OperationsManagerDW database on the shared SQL cluster or on the VM where the standalone instance of SQL reporting services resides.
Surely this is something that other people have an issue with? I would have thought most people would want to use a shared SQL cluster. Any help is much appreciated.

Just to add that SQL Reporting Services isn't cluster aware so the best you could do is to install stand-alone onto a node of the cluster.
To reinforce what Scott is saying, see this screenshot of the install of SCOM reporting:
http://www.systemcentersolutions.co.uk/images/easyblog_images/42/scom/CTP2/Install/SQRS9.png
Technically you can install SCOM reporting on a shared SQL Server Reporting Services instance but as Scott (and the screenshot) state - it will overwrite any existing security settings on existing reports.
Scott is also correct that SQL Server Standard Edition is included as part of the licensing cost of System Center 2012 as long as the SQL instance only runs components of System Center.
cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
I have one SQL 2012 Server with a few instances. 1 for Scom, 1 for SCCM and 1 for Service Manager. The instance shows up as blank for reporting services on the SCOM. Do I have to install SQL on the SCOM box also? Why Can't
it see the instance on my 2012 SQL box? It is in a different instance than SCCM.

Why SCOM 2012 R2 Agent version for Service Manager servers is 6.1.7221.49, why not 7.1.10184.

Hi ,
In SCOM 2012 R2 console if i look at all of my agent managed servers have agent builds of 7.1.10184 but my two service manager servers have agent builds of 6.1.7221.49
Can anyone let me know is this known issue or how can we upgrade the agent to correct version.
Thanks in advance
Bharath

Hi,
SCOM and SCSM are built on the same structure, Management Servers and DAta Warehouse etc. This means that when you install the SCSM Management Server, the Microsoft Monitoring Agent is also installed. When
you want to monitor Service Manager and the server it´s installed on, you need to configure the SCOM parameters from the control panel at the SCSM management server.
If you were to try and install the SCOM agent at the SCSM server, it would fail and tell you that you can´t install the agent on a server where Service Manager is installed. The agent will be upgraded when
you upgrade Service Manager so this is all expected and It´s as it should be :)
Regards,
Daniel
IT Consultant at Viridis IT

SCOM 2012 SP1 Integration with Qlikview

Hi ,
can anyone help me with information on how to integrate SCOM 2012 Sp1 and Qlikview ?
Any pointers or documentation will be greatly appreciated.
Thank you,

Hi,
I recommend you go to Qlik Community to find if there have a solution.
Welcome to Qlik Community
http://community.qlik.com/welcome
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party
contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCOM 2012 R2 Integration with Lync Server 2013

Hi,
I am trying to configure SCOM 2012 R2 to work with Lync server 2013 standard edition. I have successfully installed and tested Lync Server 2013. But the problem is, I never worked on SCOM application before and I can not find any easy documents online. So
could you please help me and suggest any step by step guide for the same purpose!
BR,
Ajit

Hi,
Glad to hear that you have solved the issue. For the second question, what did you want to do with the Windows Server (anything to do with Lync Server)? As it is another question, you can also post another case on Technet forum and more engineers will help
you solve the issue.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

SCCM 2012 R2 coexist with SCCM 2007 - DPs issue

Hi all,
I have a SCCM 2012 R2 which coexists with SCCM 2007 and I'm not interested in a migration, but my question concerning the use of DPs. Is it possible for 2012 R2 clients to use a 2007 DPs, i.e. are there settings for a sort of compatibility? I've looked among
links, but most of them are related to migration.
Please advise,
Domenico

No, you can only share a distribution point during a migration between a source and destination hierarchy (see also:
http://technet.microsoft.com/en-us/library/gg712275.aspx). Without a migration that's not possible.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Deploy SCOM 2012 R2 Agents to Domain Servers on Perimeter Network using SCOM Gateway on different Domain

Hi, I have a bit odd situation on a SCOM 2012R2 deployment.
I have a MS on the internal network, and a Gateway Server on the perimeter network. Each server is connected to different Active Directory Forests and there are no trust relationships between them. I configured the communication between the two using certificates.
I have already connected some servers through the Gateway using certificates because there are on Workgroups, they are already approved on the MS and reporting their status.
However, I have some servers that are member servers of the internal AD domain but are located on the perimeter network.
So I've tried to configure one of them for testing to connect to the Gateway Server using a certificate using manual agent installation. Initially it didn't report on the SCOM, but then I ran the get-scompendingmanagement and saw that it showed there,
so I ended up approving the agent using Powershell and then it was reported on the Console as "Not Monitored"
First the agent was running as local system and then tried using a local admin account on the server, neither options have worked.
I get the following errors:
The OpsMgr Connector connected to scomgateway.externaldomain.com, but the connection was closed immediately after authentication occurred. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the
server has not received configuration. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
OpsMgr was unable to set up a communications channel to scomgateway.externaldomain.com and there are no failover hosts. Communication will resume when scomgateway.externaldomain.com is available and communication from this computer is allowed.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Is this configuration possible? Or do I need to open communication ports from the agents to the MS inside the corporate network and not use the Gateway?
Any ideas if someone else has done this are appreciated.
Thank you.
Regards.
Eduardo Rojas

I'm sorry, maybe I didn't explained myself correctly, I already have the gateway up and running with some Workgroup machines connected to it using certificates, so the Gateway is indeed working. These Workgroup machines are in fact reporting back to the
Management Server on the internal network through the Gateway.
My problem is with Domain Member machines that are on the perimeter network. This machines are joined to the Active Directory inside the corporate firewall, not the Active directory from the perimeter network (where the Gateway is joined). So my question
is, can I connect these machines through the Gateway (even if the Gateway is on a different domain) or do I need to open ports and connect them directly to the management server (which is on the same active directory domain)?
Let me know if I made myself clear.
Thank you.
Regards.
Eduardo Rojas

SCOM 2012 R2 agent with SCOM 2007 R2?

Similar Messages

Maybe you are looking for