When you manualy edit a monitor or rule in the SCOM Authorin Console, maybee you have to edit the field @VariantType. The VariantType describes the type of the value that is returned.
The variant types are:
For years, when you need to define a Windows Storage as iSCSI target, you need a paid software, cause Microsoft iSCSI target software did only run on the Windows Storage Server edition.
As of April 2011, the target software is now available for free and supported in any Windows 2008 R2 edition!
You can use this for:
When you update your SCOM 2007 R2 to CU4 (Cumulative Update 4), you will have problems to load a management pack with SCOM Authoring Console.
You will receive a message, searching for management pack Microsoft.SystemCenter.Library with Version 6.1.7221.61:
Unfortunately you will found only version 6.1.7221.0 on your disk. Microsoft didn’t published the newer version as separated management pack file (*.mp).
To solve this open your management pack with a text- or xml-editor and change from:
|
1 2 3 4 5 |
<Reference Alias="SystemCenter"> <ID>Microsoft.SystemCenter.Library</ID> <Version>6.1.7221.61</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> |
to:
|
1 2 3 4 5 |
<Reference Alias="SystemCenter"> <ID>Microsoft.SystemCenter.Library</ID> <Version>6.1.7221.0</Version> <PublicKeyToken>31bf3856ad364e35</PublicKeyToken> </Reference> |
Change Version from 6.1.7221.61 to 6.1.7221.0
When you create an SNMP monitor in SCOM 2007 R2, SCOM assumes that the values are in STRING-format. So if you define, that your monitor should check an SNMP-OID to be greather than 70 and the SNMP OID gives a value of 100 back, your monitor will generate an error. To correct this, you have to tell your monitor, that it’s an INTEGER-value. Unfortunately, you can’t do this with SCOM Console.
The easiest way to do this, you have to export your management pack and open it with the SCOM Authoring Console.
To monitor SNMP devices with SCOM 2007 R2 is a litle special, as i know other products witch are more easy for monitoring SNMP devices. But SCOM has some good feature and if you have SCOM, you don’t want to have another tool only for monitoring SNMP devices.
Here is an overview for monitoring one ore more SNMP devices:
Here is a step-by-step guide to monitor one ore more SNMP devices:
Make a separated Management Pack for each device type. You will have only benefits:
Right click Network Devices under Device Management from Administration pane and select Discovery Wizard.
Did you ever searched an special email-address in your active directory? If yes, you will know, that there isn’t a special field for the email-addresses.
Go to active directory users and computers (ADUC).
Right click on the domain and choose Find.
Select Custom Search in the Find-Field and Entire Directory in the In-Field.
Select the Advanced-Register and type this LDAP query:
proxyaddresses=SMTP:user@domain.com
Press the Funktion-Key F2
Logon with your root-account.
Select Troubleshooting Options.
Select Enable Local Tech Support. After you enabled the local Tech Support, press two times the Key ESC, to exit to the Default Screen.
Press the Key-Combination ALT+F1 to enter the local Tech Support. You have to logon again on the console screen.
After you loged in, run the follow command:
|
1 |
esxcfg-scsidevs –m |
Now run this command:
|
1 |
vmkfstools –C vmfs3 –b <BLOCKSIZE> datastore <DRIVE-ID> |
| block size | maximum file-size on vmfs3 |
|---|---|
| 1 MB | 256 GB |
| 2 MB | 512 GB |
| 4 MB | 1 TB |
| 8 MB | 2 TB |
Each System-Administrator knows the problem. Every day a users loses his Notebook or his mobile device. The financial loss is one thing, but lose the the datas and the control who has access to this datas is a disaster for a lot of companies.
To secure your datas from loss some developers created solutions to backup your datas. Another important point is to encrypt your datas in a secure way, so that no one outside your organisation can access your sensitive datas.
The following things should be noted:
