Because I moved on and started working with Microsoft, I am shutting down this blog, and will be blogging on the Microsoft's System Center Operations Manager team blog.
http://blogs.technet.com/b/momteam/
I am looking forward in putting out great stuff.
look for me Lynne Taggart
Thursday, October 11, 2012
Thursday, February 23, 2012
Blog Status
I’ve been really busy with many things and many things are changing, to include this blog. I will end this blog here, and be starting up / moving to a new location. More to follow.
Thursday, February 2, 2012
Starting Snap-in from the command line
I can not take the total credit for this, a co-worker provided this list for everyone and I thought it was something good to share
You can start programs from the command line using these commands for those that need to:
Active Directory Management [admgmt.msc]
ADSI Edit snap-in [adsiedit.msc]
Application Server snap-in [appsrv.msc]
Authorization snap-in [azman.msc]
Certificates snap-in [certmgr.msc]
Certificate Authority snap-in [certsrv.msc]
Certificate Templates snap-in [certtmpl.msc]
Indexing Service snap-in [ciadv.msc]
Component Services snap-in [comexp.msc]
Computer Management snap-in [compmgmt.msc]
Default Domain Controller Security Settings snap-in [dcpol.msc]
Device Manager snap-in [devmgmt.msc]
Disk defragmenter snap-in [dfrg.msc]
Distributed File System snap-in [dfsgui.msc]
DHCP snap-in [dhcpmgmt.msc]
Disk Management snap-in [diskmgmt.msc]
DNS snap-in [dnsmgmt.msc]
Active Directory Domains and Trusts snap-in [domain.msc]
Default Domain Security Settings snap-in [dompol.msc]
Active Directory Users and Computers snap-in [dsa.msc]
Active Directory Sites and Services snap-in [dssite.msc]
Event Viewer snap-in [eventvwr.msc]
Exchange System Manager snap-in [Exchange System Manager.msc]
File Server Management snap-in [filesvr.msc]
Shared Folders snap-in [fsmgmt.msc]
Microsoft Fax Service Manager snap-in [fxsadmin.msc]
Group Policy snap-in [gpedit.msc]
Group Policy Management snap-in [gpmc.msc]
Internet Authentication Service snap-in [ias.msc]
Internet Information Services snap-in [inetsrviis.msc]
IP Address Management snap-in [ipaddrmgmt.msc]
Local Users and Groups snap-in [lusrmgr.msc]
.NET Configuration 1.1 snap-in [mscorcfg.msc]
Removable Storage snap-in [ntmsmgr.msc]
Removable Storage Operator Requests snap-in [ntmsoprq.msc]
Performance snap-in [perfmon.msc]
Enterprise PKI snap-in [pkiview.msc]
Public Key Management snap-in [pkmgmt.msc]
Routing and Remote Access snap-in [ rrasmgmt.msc]
Remote Storage snap-in [rsadmin.msc]
Resultant Set of Policy snap-in [rsop.msc]
Active Directory Schema snap-in [schmmgmt.msc]
Local Security Settings snap-in [secpol.msc]
Services snap-in [services.msc]
Sidwalk snap-in [sidwalk.msc]
Telephony snap-in [tapimgmt.msc]
Services Configuration/Connections snap-in [tscc.msc]
Remote Desktops snap-in [tsmmc.msc]
UDDI Services Console snap-in [uddi.msc]
Active Directory Users & Computers (Exch ver)snap-in [users and computers.msc]
WINS snap-in [winsmgmt.msc]
Windows Management Infrastructure (WMI) snap-in [wmimgmt.msc]
Tuesday, January 17, 2012
SCOM Zombie PSA#30: Event ID 21042
A few weeks ago someone (aka zombie) thought they were manually uninstalling a SCOM agent from a managed server. What they didn’t know was that they were NOT on the server they thought they were on but it was the Root Management Server. What comes next? They uninstalled the SCOM software from the Root Management Server. I knew this because I was on the server troubleshooting bad agents and everything closed out on me. I immediately check my event logs to see why, and the Operations Manager event log was GONE. I know, RIGHT! (aka Zombie Apocalypse)
But luck was on our side, and we were able to re-install SCOM back and apply the backup keys. everything was going good so we thought.
About 24 hours later the Root Management Server had the following alerts in the Operations Manager event log. I mean nothing but this event; it was pouring a lot of these event id every second.
There was not much out there in the world on this event id that we could find.
Event Type: Information
Event Source: OpsMgr Connector
Event Category: None
Event ID: 21042
Computer: RMS.FQDN
Description:
Operations Manager has discarded 1 item in management group <Management Group Name>, which came from $$ROOT$$. These items have been discarded because no valid route exists at this time. This can happen when devices are added to the topology but the completed topology has not been distributed yet. the discarded items will be regenerated.
Funny thing was each of the management Servers that had agents report to them were being flooded with these alerts.
Event Type: Information
Event Source: OpsMgr Connector
Event Category: None
Event ID: 20000
Computer: RMS.FQDN
Description:
A device which is not part of this management group has attempted to access this Health Service. Requesting Device Name: ServerName.FQDN
The quick fix was to “”Re-Enter”” each of the Run-As accounts back manually. Once this was done, the 21042 alert went away. However many of the event id 20000 didn’t all clear up. it took some manual process of stopping the agent service and deleting the Health Service State folder and re-starting the service again to make the some of the agents communicate back.
In my lab I was able to re-create the issue and correct it by doing this. I don’t fully understand all the details just yet but I’m working on that, if I can get some more time to it.
SCOM Zombie PSA#29: Alerts in console not showing up
This caught me off guard just now. When I opened my web console, there was a couple of alerts but when I opened my console up no alerts displayed. funny since it stated 8 active alerts.
The quick fix was that my Alert Detail tab was all the way up, so I just dragged and dropped it down to expose my alerts.
Wednesday, December 21, 2011
HAPPY “ZOMBIE” HOLIDAYS
To all the IT Zombies out there, I’ll continue posting more stuff after the New Year, but until then I want to tell everyone to enjoy this with family, friends and co-workers.
I only ask that each of you take to stop and help total strangers; in return your actions should encourage them to do the same.
Monday, December 5, 2011
SCOM Zombie PSA#28: Windows Server Operating System Management Pack v6.0.6958.0 (BUGGY)
Last week I deployed this management pack into my lab OM07, fresh system with no other management pack really on it. The odd thing was that the event logs was kicking out an event of 31565 about every ten minutes. My active alert, may or may not kick out an alert; it did generate an alert about every 6 hours or so.
Here is what I gotten in my event logs and eventfully the alert itself.
--------------------------------------------------------------------------------------------------------------------------
Description:
Failed to deploy Data Warehouse component. The operation will be retried. Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '3a49a530-26a2-c525-35fe-69df5898f150', Management Pack Version-dependent Id: 'dbf18271-9643-32ff-4849-00d79d9e2a9d'; Target: Database, Server name: 'XXXXXX', Database name: 'OperationsManagerDW'. Batch ordinal: 1; Exception: Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon.
Incorrect syntax near ','.
Incorrect syntax near ','.
Incorrect syntax near ','.
Incorrect syntax near ','.
Incorrect syntax near the keyword 'ELSE'.
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component
Instance name: xxxxx.xxxx.xxx
Instance ID: {4836F627-4378-5EDF-0DE7-97DAE0A2C939}
Management group: LAB
--------------------------------------------------------------------------------------------------------------------------
I found a couple of things on the web that suggested to do the following:
- I tried to do a repair on the for the Reporting Data Warehouse
- I restarted the services for SQL and OpsMgr
- Verified nothing new was installed on my server since I noticed the issue
- The final fix was to remove the management pack and revert to the old one.
------------------------------------------------------------------------------------------------------------------------
UPDATED INFORMATION:
There is another resolution I am told by a SCOM PFE that you can just uninstall the "Windows Server Operating System Reports" Management Pack. What this resolves is the two reports that only work on SQL 2008.
Bob Cornelissen & Marnix Wolf had blogged about this a while back and are requesting a better management pack.
But I’ve ran into another problem in a few production systems where removing the management pack was not an option. So the only option I was able to do at the time was turning this alert off via the overrides.
Subscribe to:
Posts (Atom)