SCOM 2012 Powershell command to remove agent

Hello,
Has anyone had any luck removing agents via Powershell to mimic the delete agent from the console?
Blogs don't turn up anything useful for this task.
The 2012 Powershell covers how to approve agents, add proxy flag, and uninstall agent, but nothing to remove.  Used the SQL stored procedure previously in 2007R2 (and same procedure exists in 2012 SP1. 
Anyone aware of Powershell automate agent removal?
Thanks!
SCOM Power Shell to add SCOM 2012 agent
Get-SCOMPendingManagement | where {$_.AgentName -eq "ServernameFQDN"} | Approve-SCOMPendingManagement
Enable Proxy on newly added agent
Get-ScomAgent | where-object {$_.DisplayName -like "okcnmo*"} | where-object {$_.ProxyingEnabled.Value -eq $False} | Enable-SCOMAgentProxy
SQL Query to remove
http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/e413c030-509b-45e4-bcd4-b4ae1a649c73
Uninstall Agent
http://technet.microsoft.com/library/hh545186.aspx
Remove Unix agents
http://social.technet.microsoft.com/Forums/en-US/operationsmanagerunixandlinux/thread/081f2801-7dfa-4db9-8c78-6adbc487a031/

We actually have used the stored procedure for 2007 and 2012
OperationsManager.dbo.p_TypedManagedEntityDelete
If you want to use Invoke-Sqlcmd to run the query.
Another way from SQL which can be put in PowerShell
--Grab GUID for that health service
select * from BaseManagedEntity
where FullName like '%<servername>%'
and IsDeleted = 1
Look for FullName with Microsoft.SystemCenter.HealthService:servername
-- Use this to test the entity delete for the healthservice GUID
DECLARE @EntityId uniqueidentifier;
DECLARE @TimeGenerated datetime;
-- change "GUID" to the ID of the invalid entity
SET @EntityId = '<GUID here>';
SET @TimeGenerated = getutcdate();
BEGIN TRANSACTION
EXEC dbo.p_TypedManagedEntityDelete @EntityId, @TimeGenerated;
COMMIT TRANSACTION
--Check what is in deleted
select * from BaseManagedEntity
where IsDeleted = 1

Similar Messages

  • Scom 2012 R2 Convert Manually installed Agents to Remotely managed

    Hi
    Need to convert manually installed agents to remotely managed.
    Found this post :
    http://damatisystemcenter.com/2013/01/25/convert-manually-installed-agents-to-remotely-managed/
    The last Query converts one agent to remotely managed
    How do I do if I want ALL my agents to be converted to remotely ?

    Hi,
    Setting Agents as Remotely Manageable in SCOM 2012 R2
    http://daxsnippets.wordpress.com/2014/04/08/setting-agents-as-remotely-manageable-in-scom-2012-r2/
    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.

  • Scom 2012 r2 command line install

    I want to pass the username and password as variable in the below command for datareader and datawriter accounts . The installation stops as its not able to validate the creds. Can some please help me correcting the script . If I hardcode the username and
    password in the below script it works
    $user = 'dpmain\me
    $pass = 'passw'
    Start-Process -FilePath C:\SCOM2012R2\setup.exe -ArgumentList '/install /InstallPath:"C:\Program Files\Microsoft System Center 2012 R2\Operations Manager" /components:OMServer,OMConsole /ManagementGroupName:OM2012SandBox /SqlServerInstance:. /DatabaseName:OperationsManager
    /DWSqlServerInstance:. /DWDatabaseName:OperationsManagerDW /UseLocalSystemActionAccount /UseLocalSystemDASAccount /DatareaderUser: '$user' /DatareaderPasswod:'$pass' /DataWriterUser:'$user' /DatareadePassword:'$pass' /EnableErrorReporting:Never /SendCEIPReports:0
    /UseMicrosoftUpdate:0 /AcceptEndUserLicenseAgreement:1 /silent'

    The line below is taking care of the installation of you first management server. Change the parameters to first to your needs.
    Start-Process-FilePathE:\setup.exe
    -ArgumentList'/install /InstallPath:"C:\Program Files\Microsoft System Center 2012 R2\Operations Manager" /components:OMServer,OMConsole /ManagementGroupName:SCOMMgmt /SqlServerInstance:SQLSERVER\Instance /DatabaseName:OperationsManager
    /DWSqlServerInstance:SQLSERVER\Instance /DWDatabaseName:OperationsManagerDW /ActionAccountUser:Contoso\Administrator /ActionAccountPassword:'XXXX' /DASAccountUser:contoso\Administrator /DASAccountPassword:'XXXX'
    /DatareaderUser:domhome\Administrator /DatareaderPassword:'XXXX' /DataWriterUser:domhome\Administrator /DataWriterPassword:'XXXX' /EnableErrorReporting:Never /SendCEIPReports:0 /UseMicrosoftUpdate:0 /AcceptEndUserLicenseAgreement:1
    /silent'
    Also check below links
    http://scug.be/christopher/2014/03/10/scom-2012-r2-unattended-installation-command-line/
    http://technet.microsoft.com/en-us/library/hh416216.aspx
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • Executing DPM Powershell Commands

    Hi All,
             I am trying to execute DPM 2012 Powershell commands from a console application in c#, but at the time of Invoke it is giving me the following error.
    {"Could not load file or assembly 'ACM, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.":"ACM, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"}
    Below is my code.
    var runspace = PShell.GetRunSpace();
                if (runspace.RunspaceStateInfo.State == RunspaceState.BeforeOpen)
                    runspace.Open();
                var pipeline = runspace.CreatePipeline();
                pipeline.Commands.AddScript("$installPath = (Get-ItemProperty \"HKLM:\\SOFTWARE\\Microsoft\\Microsoft Data Protection Manager\\Setup\" \"UIInstallPath\").UIInstallPath");
                pipeline.Commands.AddScript("$dpmModuleFullPath = $installPath + \"Modules\\DataProtectionManager\\DataProtectionManager.psd1\"");
                pipeline.Commands.AddScript("Import-Module $dpmModuleFullPath");
                pipeline.Commands.AddScript("$pg=get-protectiongroup -dpmserver dpm-2012-01");
                pipeline.Commands.AddScript("$pg");
                try
                    System.Collections.ObjectModel.Collection<PSObject> result = pipeline.Invoke();
                    foreach (PSObject obj in result)
                        var name = obj.Properties["FriendlyName"].Name;
                catch (Exception e)
    ilyas

    Hi All,
             I am trying to execute DPM 2012 Powershell commands from a console application in c#, but at the time of Invoke it is giving me the following error.
    {"Could not load file or assembly 'ACM, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.":"ACM, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"}
    Below is my code.
    var runspace = PShell.GetRunSpace();
                if (runspace.RunspaceStateInfo.State == RunspaceState.BeforeOpen)
                    runspace.Open();
                var pipeline = runspace.CreatePipeline();
                pipeline.Commands.AddScript("$installPath = (Get-ItemProperty \"HKLM:\\SOFTWARE\\Microsoft\\Microsoft Data Protection Manager\\Setup\" \"UIInstallPath\").UIInstallPath");
                pipeline.Commands.AddScript("$dpmModuleFullPath = $installPath + \"Modules\\DataProtectionManager\\DataProtectionManager.psd1\"");
                pipeline.Commands.AddScript("Import-Module $dpmModuleFullPath");
                pipeline.Commands.AddScript("$pg=get-protectiongroup -dpmserver dpm-2012-01");
                pipeline.Commands.AddScript("$pg");
                try
                    System.Collections.ObjectModel.Collection<PSObject> result = pipeline.Invoke();
                    foreach (PSObject obj in result)
                        var name = obj.Properties["FriendlyName"].Name;
                catch (Exception e)
    ilyas
    I have the very same issue, only I am running the script from within PowerGui (www.powergui.org). Was a resolution ever found for this issue?
    http://blog.aggregatedIntelligence.com/

  • 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.

  • How to remove network devices through powershell? (scom 2012)

    Hi
    Could anyone says how to delete network device in SCOM 2012 through powershell?
    In 2007 we have Get-RemotelyManagedDevice.
    I have a big number network device in monitoring and now need delete some of them with specific filter, all switches.
    How to do it?
    Thanks
    Alex

    The devices were discovered by an old Management Server that was reinstalled.
    I finally got those devices out of my SCOM environment using this SQL query (just replace networkdevicename):
    UPDATE
    BaseManagedEntity
    SET
    isdeleted=1
    from
    BaseManagedEntity where
    BaseManagedEntityId in
    (select
    BaseManagedEntityId from
    BaseManagedEntity where
    displayname like
    '%networkdevicename%')

  • Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

    I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
    We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
    installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
    I have to remove the management installation first. And that's not gonna happen.
    I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
    In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
    Control Panel. And this can NOT be the most healthy way of getting through the setup.
    I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
    Any of you have tips as to how I can get rid of the agents more gracefully?

    Hi
    Thanks for the replay guys!
    None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
    I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
    days.
    Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
    agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
    So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
    but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

  • SCOM 2012 R2 # Windows Server agents remain in pending management

    Hi,
    First I installed one SCOM 2012 R2 Ops Manager. On same SCOM ops manager I added 3 windows server agents to monitor as below..
    one 2008 R2 AD server
    one Lync 2013 FE server
    one Exchange server 2013
    Now due to some technical issues later I had to completely remove/uninstall SCOM 2012 R2 setup. But I forgot to uninstall/remove 3 agents first before uninstalling SCOM 2012 R2 ops manager :( However I did manual uninstall of Microsoft monitoring agent setup
    from all 3 monitored agent servers.
    Now I setup new SCOM 2012 R2 ops manager once again. FQDN of new SCOM has been changed now, though server is in same domain as old one. Problem I am facing here is " I cannot able to add those 3 agents back into new SCOM ops manager. When I install
    agent back onto those 3 servers (by agent discovery or manual setup) , servers remains in pending management. I used power shell command to approve all 3 but even after approval servers are not being monitored. Health status always showing not monitored. A
    blank green circle.
    I think I didn't properly removed old agent setup, & somehow those 3 agents still bound to old SCOM ops manager.
    Could you please help me how I can remove remaining components of old agent setup from windows agent servers and monitor them with new SCOM?
    BR,
    Ajit

    Ensure that the following registry keys are deleted:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService
    Reboot the agent machine (if possible)
    Delete the agent from Agent Managed in the OpsMgr console.
    Then try to discovery and push agent from console if failed. Try to install it manual and then from pending management click approved.
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • 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.

  • Automatic windows agent fail over in SCOM 2012 / 2012 R2

    Hi All,
    I have a question with respect to SCOM 2012 / 2012 R2 windows agent fail over.
    For example i have only 400 windows agents and i have 2 MS in my environment. So 200 windows agents are managed by MS1 and the rest 200 are managed by the MS2.
    What i want to know is if either of the MS (MS1 or MS2) Shutdown / restart or any thing happens to them, Do the agents automatically fail over to the other MS ? As i have not configured ant thing for this as i don't know.
    So is there any configuration to be done for the above to happen after the deployment of both the management servers is done before discovering the agents or does it automatically understand take the rest 200 agents thinking that the other MS is down ?
    Gautam.75801

    Hi All,
    I have a question with respect to SCOM 2012 / 2012 R2 windows agent fail over.
    For example i have only 400 windows agents and i have 2 MS in my environment. So 200 windows agents are managed by MS1 and the rest 200 are managed by the MS2.
    What i want to know is if either of the MS (MS1 or MS2) Shutdown / restart or any thing happens to them, Do the agents automatically fail over to the other MS ? As i have not configured ant thing for this as i don't know.
    So is there any configuration to be done for the above to happen after the deployment of both the management servers is done before discovering the agents or does it automatically understand take the rest 200 agents thinking that the other MS is down ?
    Gautam.75801
    This happens automagically for Windows agents within a domain that are assigned to a Management Server.  For other scenarios, such as Gateways, the Gateways should be configured for failover between Management Servers, and the agents attached to those
    Gateways should be configured to failover between the Gateways.  Cross platform agents report to a resource pool, so that happens automagically as well.
    To confirm your scenario, simply run the Get-SCOMAgent cmdlet.
    To test you can do the following, assuming first agent in the array isn't a Management Server/Gateway :)
    $SCOMAgents = get-scomagent
    $SCOMAgents[0].PrimaryManagementServerName
    $SCOMAgents[0].GetFailoverManagementServers()
    Supporting article:
    http://blogs.technet.com/b/jimmyharper/archive/2010/07/23/powershell-commands-to-configure-gateway-server-agent-failover.aspx

  • SCOM 2012 UR2 - Flush health service state causes infinite agent resets

    Appearing on several of our 2008R2 servers from our SCOM 2012 UR2 environment, set up with several management servers:
    If I select a monitored servers agent in the Operator Console and click the task
    Flush health service state and cache, the selected agent will restart as intended.
    However, it will restart again every 2-3 minutes forever ever after, unless  you stop the agent service and delete the health service cache folder on the monitored server.
    This is visible via the eventlog:
    event 103, Healthservice. A task to reset the health service store has been submitted.  The service store will be deleted and re-created.
    This was never the case with our SCOM2007R2 setup and started appearing with 2012.
    Have anyone seen this before? Any ideas?
    Regards / Jon

    Might save someone some time....
    Stopping the agent, removing the "Health Service State" directory + restarting doesn't appear to help.  I did this *and* deleted some agents from the console (then re-added them.  We turned auto approve off)  and it appears
    it might have fixed it.  I'll know more in the morning if this actually does the trick besides doing a full uninstall/reinstall of the agent.
    If you don't know what agents are constantly restarting, search all management servers for *many* file transfers (Event ID 2110 in Ops manager event log) all to the same Instance/GUID. Execute this powershell on a managemnt server: "get-SCOMClassInstance
    -Id <GUID>" to get the affected agent. Alternatively, make a SCOM rule to catch event 103 and look for many repeats from the same server/agent:
    Event Type: Warning
    Event Source: HealthService
    Event Category: Health Service
    Event ID: 103
    Description:
    A task to reset the health service store has been submitted.  The service store will be deleted and re-created.

  • SCOM 2012 Test-Mailflow command received an NDR from SystemMailbox

    I installed and configured the Exchange Server 2010 Management Pack in System Center Operations Manager (SCOM) 2012. Everything is working fine except one monitor:
    "KHI: One or more unexpected NDRs have been received in response to Test-MailFlow cross-premises test messages."
    This monitor shows a critical error.
    Every 10 minutes, SCOM runs the following PowerShell command:
    Test-Mailflow -CrossPremises:$true
    The command sends an e-mail to the FederatedEmail system mailbox ([email protected]), but an NDR is generated because the mailbox has a 1MB storage quota and it quickly filled up with test
    messages.
    How is this supposed to work? Should I just raise the quota on the FederatedEmail mailbox, or is there something else that's supposed to be done? I've consulted TechNet and the Management Pack documentation and I can't find much information about the Test-Mailflow
    synthetic transaction or how it's supposed to work. 
    We also have a hybrid deployment between Exchange 2010 and Office 365, so I would love it if this Test-Mailflow command could actually test mailflow between our Exchange environment and Office 365. That would be really helpful information to alert
    on.
    Any help or recommendations would be greatly appreciated. Thank you!
    Here is the full text of the error:
    Test-Mailflow command received an NDR from
    SystemMailbox{GUID}@domain.com in response to a
    test message sent to
    [email protected].
    Delivery has failed to these recipients or groups:
    SystemMailbox{GUID}
    ([email protected])
    <mailto:[email protected]>
    The recipient's mailbox is full and can't accept messages now. Please try
    resending this message later, or contact the recipient directly. Diagnostic
    information for administrators: Generating server: SERVER.domain.com
    [email protected] #554-5.2.2
    mailbox full 554 5.2.2
    STOREDRV.Deliver.Exception:QuotaExceededException.MapiExceptionShutoffQuotaExceeded;
    Failed to process message due to a permanent exception with message Cannot open
    mailbox /o=First Organization/ou=Exchange Administrative Group/cn=Configuration/cn=Servers/cn=SERVER/cn=Microsoft System
    Attendant.

    Our SCOM 2012 environment is doing the same thing. This test-mailflow is generated by the managment pack and therefore should belong in this forum.
    Otherwise, you should remove the support statement in the Management Pack Guide (June 2012)
    Cross-premises mail flow monitoring and reporting   The Management Pack includes new mail
    flow monitoring and reporting capabilities for customers who use our hosted service.
    Error:
    Test-Mailflow command received an NDR from SystemMailbox{dfd5527a-b3bb-473a-b7d3-1257984884}@customer.com in response to a test message sent to [email protected]mer.com. Delivery has failed to these recipients
    or groups: SystemMailbox{dfd5527a-b3bb-473a-b7d3-a2743d86cdda} ([email protected]) The recipient's mailbox is full and can't accept messages now. Please try resending this message later, or contact the recipient
    directly. Diagnostic information for administrators: Generating server: MAIL-01.customer.com [email protected] #554-5.2.2 mailbox full 554 5.2.2 STOREDRV.Deliver.Exception:QuotaExceededException.MapiExceptionShutoffQuotaExceeded;
    Failed to process message due to a permanent exception with message Cannot open mailbox <snip>

  • 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:&nbsp;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 Agent - Best Practices with Base Images

    I've read through the
    SCOM 2012 agent installation methods technet article, as well as how to
    install the SCOM 2012 agent via command line, but don't see any best practices in regards to how to include the SCOM 2012 agent in a base workstation image. My understanding is that the SCOM agent's unique identifier is created at the time of client installation,
    is this correct? I need to ensure that this is a supported configuration before I can recommend it. 
    If it is supported, and it does work the way I think it does, I'm trying to find out a way to strip out the unique information so that a new client GUID will be created after the machine is sysprepped, similar to how the SCCM client should be stripped of
    unique data when preparing a base image. 
    Has anyone successfully included a SCOM 2012 (or 2007 for that matter) agent in their base image?
    Thanks, 
    Joe

    Hi
    It is fine to build the agent into a base image but you then need to have a way to assign the agent to a management group. SCOM does this via AD Integration:
    http://technet.microsoft.com/en-us/library/cc950514.aspx
    http://blogs.msdn.com/b/steverac/archive/2008/03/20/opsmgr-ad-integration-how-it-works.aspx
    http://blogs.technet.com/b/jonathanalmquist/archive/2010/06/14/ad-integration-considerations.aspx
    http://thoughtsonopsmgr.blogspot.co.uk/2010/07/active-directory-ad-integration-when-to.html
    http://technet.microsoft.com/en-us/library/hh212922.aspx
    http://blogs.technet.com/b/momteam/archive/2008/01/02/understanding-how-active-directory-integration-feature-works-in-opsmgr-2007.aspx
    You have to be careful in environments with multiple forests if no trust exists.
    http://blogs.technet.com/b/smsandmom/archive/2008/05/21/opsmgr-2007-how-to-enable-ad-integration-for-an-untrusted-domain.aspx
    http://rburri.wordpress.com/2008/12/03/untrusted-ad-integration-suppress-misleading-runas-alerts/
    You might also want to consider group policy or SCCM as methods for installing agents.
    Cheers
    Graham
    Regards Graham New System Center 2012 Blog! -
    http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at
    http://systemcentersolutions.wordpress.com/

Maybe you are looking for

  • VPN (PPTP) problem

    Hi I have a weird VPN problem on my macbook. I'm trying to connect to a Windows 2000 Server though VPN dialup (PPTP), it connects, seems like I'm getting an IP, but I cannot access anything on the network. VPN dialup works fine from my iMac, so I kno

  • How to check how many adobe forms are in use cross systems or locally

    Hello, we want to check that we are not using to many adobe forms within our SAP system. Is there an easy way to get this information out of sap ? please guide. (TC or  Report)   thanks JR

  • Adobe Livecycle Designer ES 2 - how to repeat page layout in the form?

    How would you repeat page layout design randomly in a form, means how the same page layout can be repeated on non-consecutive pages of an LC Form? For e.g. I want to repeat Page1 layout on Page 5 and Page 6 of an LC Form. How to do that. Please reply

  • How can i download yahoo mail contacts to my mini ipad

    how can i download yahoo mail contacts to my mini ipad?

  • KKBC_ORD for all orders in a plant

    Hi, Is there any report in CO-PC which would give me the information I can get in KKBC_ORD but for all orders in the plant at one run? My problem is that, I require to see the actual, target and plan activity quantities for particular production cost