Windows Azure Pack MP for SCOM is quite easy to install and configure. Actually you just import it and it works without setting any accounts and etc. Continue reading “Quick Look at Windows Azure Pack Management Pack”
Let’s have a look Service Management Automation MP for SCOM.
Before importing the MP you need to create Run As account in SCOM and that account needs to have logon and read access to the SMA database. Continue reading “Quick Look at System Center Service Management Automation Management Pack”
The System Center 2012 Service Manager MP has some pitfalls during importing and configuration that you may stumble upon. So I will describe the steps needed to be made in case the MP guide is not clear enough.
1. First you need to install the MP so you can get the following MPs extracted:
2. After you have these 3 MPs extracted you have to import only Microsoft.SystemCenter.ServiceManager.Library
3. After the MP above is imported successfully you have to create Run As account. You can use the default action account or a separate account for tighter security. Just make sure that the account you will use has the needed permissions. You can find description of the needed permissions here on page 17. I basically make the account local administrator on Service Manager Management Servers, Service Manager DW and give db_datareader permissions to the Service Manager database and to the staging and configuration database.
4. So you create that Run As account as Windows type. Secure the account to the Service Manager Management Servers, Service Manager DW server, Service Manager database server and Service Manager DW databases servers.
5. Next you need to add the account to the Service Manager Database Account profile. Distribute it to all objects.
6. Next step is to import Microsoft.SystemCenter.ServiceManager.Discovery MP.
7. After it is imported successfully discovery of Service Manager will start. And here is the tricky part you have to wait until full discovery is performed before importing Microsoft.SystemCenter.ServiceManager.Monitoring MP. Basically you have to wait at least 24 hours to make sure discovery of Service Manager has passed fully. Trough OpsMgr console you can check if full discovery has passed.
8. Open OpsMgr console and go to Discovered Inventory view. Target it to System Center DataWarehouse 2012 Server. You should see your Service Manager DW server and if all properties are filled with values that means your Service Manager DW server is fully discovered.
9. Next Target to SCSM 2012 Management Server. You should see all your Service Manager management servers. If all properties have values for all your Service Manager Management servers that means they are fully discovered. In my case I have only one Management Server:
10. To fully verify if Service Manager was discovered you can go to Distributed Applications and open the diagram for Service Manager:
11. All Service Manager servers and database should be visible with their properties in Detail View.
12. The last step is to import Microsoft.SystemCenter.ServiceManager.Monitoring MP so the monitoring of Service Manager can start.
The software I’ve used:
- Windows Server 2012
- SCSM 2012 SP1 UR2
- SCOM 2012 SP1 UR2
- System Center 2012 Service Manager 7.5.1561.0 MP
Note: System Center 2012 Service Manager 7.5.1561.0 MP does not state that System Center 2012 Service Manager SP1 is supported but so far I haven’t discovered something that is not working properly.
Dell Management Pack for SCOM provides a lot of features but if you do not use all these features you can cut some of them. In general you can make this MP lighter. All this explained in article “Making DELL management packs lighter for your management servers” by Daniele Grandini.
Microsoft published a nice article on Partner &Customer Solutions Blog about how to take advantage of PowerShell in managing NICs. The article gives basic overview of several PowerShell commands that can be useful for getting information about NICs or configuring them. You can read the full post here.