The good news: Advanced View Editor 2.0 for SCSM 2012 will be available at the end of this week. The bad news: will be available two different versions: free (Free Edition) and paid (Pro Edition). Get more information below.
Very short blogpost. SCOM agent of any version DOESN’T work on SCSM 2012 servers, even don’t try to install it, you can damage your SCSM installation. This is true for Beta, and, unfortunately, this is true for RTM too. So the only way to monitor SCSM servers with SCOM is a using agentless monitoring.
This is WRONG and confirmed by product team. OpsMgr agent of any versions still CAN’T coexist with SCSM 2012 RTM.
Updated 22.07.2013. Information about SCSM 2012 SP1. The SCSM 201 SP1 already contains the SCOM 2012 SP1 agent. For you this means:
- You can attach SCSM 2012 SP1 server to SCOM 2012 SP1 as manually installed. You no need to install agent on SCSM 2012 SP1 Server.
- You CAN’T update the SCSM 2012 SP1 agent to any new version of the SCOM 2012 Sp1 agent. Please don’t try to install SCOM agent’ UR on SCSM 2012 SP1 Server..
“Dear Anton Gritsenko,
Congratulations! We are pleased to present you with the 2012 Microsoft® MVP Award! This award is given to exceptional technical community leaders who actively share their high quality, real world expertise with others. We appreciate your outstanding contributions in System Center Cloud and Datacenter Management technical communities during the past year.”
Thanks everyone who participated! Special thanks to Alexey Zhuravlev who help me all time at way to MVP!
Unfortunately, AD connect doesn’t have a ability to change it schedule. For SCSM 2010 AD connector runs one per hour, for SCSM 2012 it run once per 24 hours. For small domain this is acceptable schedule but for large domains with many users it can be potential risk of overload of the SQL or SCSM servers. AD connector get from AD only objects changes since last run but even this amount of data can be large and reduce workload to SCSM management server and even more to SQL server.
Office365 is a cloud-based solution which allows you to host email and SharePoint at microsoft’s servers on the cloud. And if you already use this solution and starting using the SCSM when early or later you want to send notifications to Exchange Online mailboxes. That simple at first glance solution is not really simple. The main problem that Office365 doesn’t support Windows authentication. So the only way is send all emails through your local SMTP relay. In this post I’ll talk how to setup and configure all chain to send notifications from SCSM to Office365.
As you all know (or will know after reading of this post )) ) the SCSM 2012 have a native cmdlets which has installed during setup process of SCSM console. Some of native SCSM2012 cmdlets use different from SMLets names of the cmdlets.
Sometimes you need to know which objects contain the queue. This can be done easy with PowerShell.
When you have installed the SCSM web-portal you will have two sites: standard root site for team work and child site SMPortal with SCSM web-portal itself. If you want to use one SMportal you can move it to root level.
Some time ago Travis was publish the article about how to deploy SCSM web-parts to existing Sahrepoint server. But this instruction is very complex, and same tasks can be acomplished with much more easy way without manually copying files, editing the web.config and etc.
Microsoft try to improve performance for SCSM 2010 with different way. One of that way – use ordinal data instead of string data in console. But that change in data also make change in enum columns too: when you try to sort, group of search at enum columns the result is very strange at first look – instead of strings (like “High”, “Medium” or “Low” and so on) you see the digits. Why and how to change that?