Recently I got some emails requesting for a ACS DB sizing calculator similar to what I had published for the OpsMgr Database and Data warehouse. While I was unable to put one for the ACS DB I did find that a couple of months ago Pete Zerger one of the OpsMgr MVPs put together an Audit Collection (ACS) database sizing calculator. While we haven’t done an “official” verification of this tool I did get a chance to finally run some simulation tests on different workloads to compare it with what our customer have today and the sizing seems accurate. There are three different workloads this calculator takes into account which are workstations(smallest workload), member servers and domain controllers (largest workload). You can download the excel calculator from the link below.
Satya Vel | Program Manager | System Center |
Attachment(s): ACS DB Size Calculator.xlsx
I was asked recently to help solve a problem whereby a customer had the need to report on the availability of their servers over time. Easy you may think, run the availability report and you are done! (Well this was my first response; turns out they had a much more specific requirement!)
The customer had configured their health models for alerting accordingly and was extremely satisfied from a monitoring perspective, the problem came when they wanted to produce monthly availability figures. The needed to produce not just what health states the servers went through over time as per the health model, but they also just had a need to report on how long the server was simply up over the same period.
So the next thing I told them was to read Eugene’s blog and the article on how to do this - http://blogs.msdn.com/eugenebykov/archive/2007/09/14/linked-availability-reports.aspx.
Eugene’s blog highlights the needed process, what I have added below is steps for a specific monitor and the sample files so you can try this out yourself.
1. Identify the monitor needed, in this case the Computer Not Reachable monitor. (This monitor determines simply if the computer can be pinged or not)
1. Create a group to hold all the servers you wish to report on. The monitor in this example is targeted at the Health Service Watcher so our group needs to contain these items.
2. Now create a linked report definition. This is done by creating a new custom MP to hold this information. The sample MP already contains the required information; under the <Parameters> element in this MP the default Monitor Name is as shown below:
<Parameters>
<Parameter Name="MonitorName">
<Value>Microsoft.SystemCenter.HealthService.ComputerDown</Value>
</Parameter>
</Parameters>
3. This MP is then imported into Operations Manager.
4. Run the report and select the group created in Step 1, once rendered the Availability report is targeted solely at this monitor – Computer not Reachable.
You are able to create a linked report that uses any enabled monitor. You will need to specify the monitor system name in the MP XML, which can be found by querying the vMonitor view in the Operations Manager Data Warehouse.
Also attached to this article are 2 performance linked reports that allow you to target a specific performance counter rather than selecting the counter each time. This is particularly useful if you have for example both the Windows 2000 MP and Windows 2003 MP and cannot when running the report determine which counter to choose.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included utilities are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Daniel Savage
Program Manager | System Center Operations Manager
Attachment(s): LinkedReports.zip
The performance team had a thread discussing IOPS requirement with a customer who had some really good questions so and I thought I would share the thread with you all. For sizing the Operations Manager Database and Data warehouse I would highly recommend trying out SCCP planning tool which will give you a lot of guidance for sizing your DB’s. Below are some questions we answered to customer on IOPS requirements which I think maybe useful to you. Also one of our MVPs wrote a great article on IOPS requirements for OpsMgr based on the research he had done which can be found here: http://wchomak.spaces.live.com/blog/cns!F56EFE25599555EC!610.entry
1) Does Ops Mgr 2007 have large sprocs and / or queries that are sensitive to timely completion? Do these sprocs and / or queries run on very large data sets (if so, what's the potential range of sizes), and do they branch a lot or do other things that might generate a lot of random disk I/O?
The DB is an integral part of OpsMgr and part of the end to end operations – in that sense, there is no performance impact against OpsMgr due to sprocs and queries. For larger environments like this, one of the largest database queries will happen during a Configuration change (Importing an MP, making an override on common MP, etc). The amount of IO needed to perform this query will depend on the number of instances you are monitoring. That being said, this is not a very frequent operation, unlike say pulling the Active Alerts View in the Operations Console.
2) Do these sprocs and / or queries generally tailor better to small-block random disk I/Os (4 - 8KB), medium block random disk I/Os (16 - 32KB), or large random disk I/Os (64+KB)? Do any of the sprocs tailor better to sequential disk I/O?
SQL Server’s most basic IO happens in 8K Pages. You should see 8K random and sequential IO’s depending on the level of fragmentation of you tables and indexes. OpsMgr has daily tasks to defrag and reindex tables and indexes as needed. For more information, take a look at this document from the SQL Server 2005 Books Online: http://msdn.microsoft.com/en-us/library/ms190969.aspx One advantage of OpsMgr is that we have separated the Operational and Reporting databases. This allows the “long / expensive” queries to run outside of the Operational data, so that running reports doesn’t impact data coming in, unless the databases area on the same SQL server and physical disks).
3) Can you provide additional details about why Ops Mgr 2007 scalability is limited to 6,000 agents? We need to understand what limits Ops Mgr to 6,000 agents, whether it is OS, database, networking, threading, memory, or other limitation?
We recommend 50 UI Consoles & 6000 Agents in a single MG, as it may cause system bottleneck in RMS/DB beyond that point.
4) What is the system bottleneck in the RMS/DB that you refer to? Is it based upon the DB software, lock contention, a disk I/O shortage, something else?
The bottlenecks tend to be Memory and CPU on the RMS for the three OpsMgr services running there (mainly ConfigService), and Database IO on both the OpsDB and OpsDW. Depending on the number of Agents, Consoles, and MP’s installed, these bottlenecks maybe be a bit more or less severe, but they are the main bottlenecks for overall system scalability.
5) What I/O size (4K, 8K, 16K, etc?) must be sustained at 125 IO ops?
Since the pure number of IO’s has a much bigger impact than the size of the IOs, the size is less important. This number (125 random IOs/sec) is a rule of thumb we use, though faster disks with smaller write sizes may exceed this number, though it would be marginal.
6) How was this requirement for 125 IO ops derived (please be as specific as possible)?
This is based on a typical 10K-15K RPM SCSI disk, with completely random reading/writing. (Sequential IOs and even random/sequential IO mixes will be faster.) If it is not clear already, this number gets doubled (250 IOps) when you have a 4-disk RAID 10 array since you get two disks (and their respective mirrors) working in parallel.
7)Does this rule hold for every type of RAID (1, 5, 1+0, etc)?
For RAID 0, it gets multiplied by the number of disks you have in your array. For RAID 10, you’d multiply it by half the number of disks you have in your array (since half of your disks are used for mirroring). For RAID 1, you’d get no improvement in performance (RAID 1 only provides added redundancy – no performance benefit), so the same rule would hold true here. RAID 5 (which we don’t highly recommend, by the way, since it mostly benefits disk reads, but less so for writes), also gets some benefit, but it will be mostly for disk reads.
8) When considering a 14 drive 1+0 array, does it assume 14x125 IO ops, or 7x125 IO ops, does it assume or 14x125 for reads and 7x125 for writes?
Since RAID 1+0 (RAID 10) only uses half of the disks for performance gain (the other half are for redundancy), you would see a 7 X 125 IOps factor for both random reads and random writes. Trayce J informed me that for READS – some controllers & firmware allow the reads to take place across all the disks in the RAID 1+0 array and thus give you potentially 14x125. Other controllers only give you the 7x125.
9) Please provide detail re: how the estimates for typical support of 2,000 agents/server. If the volume of operational data were to remain the same, would the number of management packs influence the number of agents/server? What's the relationship between operational data volume and use of mgmt server resources?
An increased number of management packs puts a greater load on the RMS, but not the MS’s. So, this would not change the number of agents/MS, but may affect the number of agents that can be monitored in the deployment, due to potential bottlenecks on the RMS.
Higher operational data volume requires more management server resources.
Number of Management Packs, and more importantly the number of discovered instances impacts the Memory and CPU usage on the RMS.
Satya Vel
I wanted to drop a quick note to let you all know about something that went live a couple weeks back that I think will save many people from a ton of headaches. In addition to management pack guides being a part of the installation package for MPs, they can now be viewed from TechNet. The guides are separated into operating system technologies here (i.e. The Base OS, AD, DHCP, etc.) and all other server product here (i.e. BizTalk, SQL, Exchange, DPM, etc.). Moving forward you can expect that guides for newly released management packs will be available on TechNet within a week or so of the management pack release.
Another feature of having these guides online is that all of them are "community content-enabled", which means you can add content (tips, tricks, gotchas) directly to the online content.
I updated the Vista gadget that makes it easier to find help for System Center products. The gadget now contains more scoped searches and the new System Center branding, and it also workes better than version 1.0 did while using a slow internet connection. Use the settings in the gadget to pick the product (such as Operations Manager) that you want to find information about, and then enter a search term in the gadget to get customized search results for the specified product. For example, the gadget can filter search results so that only pages from the Operations Manager documentation on TechNet or MSDN are returned.
Here is the download link: http://gallery.live.com/LiveItemDetail.aspx?li=49e26ad0-113d-4f3d-a711-57f6530c75d9
- Chris Scoville
This is a brand new management pack for OpsMgr 2007 so if you've been waiting for MSMQ 3.0 monitoring with OpsMgr 2007, here it is! The MP was released to the MP Catalog on 6/3/2008 (version 6.0.6278.23) and it provides monitoring for MSMQ Servers, MSMQ Triggers, MSMQ Queues and Dependant Clients. Following are some relevant snippets from the document of the MP:
- All management packs (MPs) included in the download are supported on System Center Operations Manager 2007 RTM and Service Pack 1.
- The Message Queuing Management Pack for Operations Manager 2007 is designed to monitor Message Queuing version 3.0 only.
- The Message Queuing Management Pack supports the following platforms: Windows Server 2003; Windows XP
Refer to the MP's download details and the management pack guide, which is installed by the MSI file that is downloaded, for more detail.
If you are deploying Ops Mgr on machines in untrusted domains or DMZs (anywhere outside of Kerberos trust), then you are going to need to leverage PKI and set up certificates on your boxes in order for authentication to work. The process of requesting and retrieving the needed certificates can be confusing and painful, often involving a great number of steps. In this post I aim to describe how to use some standard command line tools to get certificates working in Ops Mgr.
The steps for obtaining and installing certificates for Ops Mgr are detailed at http://technet.microsoft.com/en-us/library/bb735408(TechNet.10).aspx If your CA is on a Win2K3 server, and you would prefer to carry out the certificate requesting/approving/retrieving process through the MMC certificate console snap-in and CA web UI, then these steps should work fine for you and you won't find much useful information in this post. If your CA is hosted on a Win2008 server, or you want to learn about command line alternatives, this post will be more interesting for you.
What does Win2008 have to do with it? There was a decision to change the certificate services web UI for Win2008 CAs. You can read about it at http://support.microsoft.com/kb/922706 The 2008 web UI no longer gives users the option of obtaining a Machine Certificate (previously done by checking the "Store certificate in the local computer store" box when configuring your request). Unfortunately, this setting is required for Ops Mgr-compatible certificates, so users must now explore other options.
For the purposes of this post, let's say we are setting up certificates between a Gateway and a Management Server. It is assumed we are logged in to the machines as administrators. The steps are the same for gateway, management server, or agent.
Obtaining and Installing the CA Certificate
Let's say your Gateway will be presenting the Management Server with a certiciate issued by the certificate authority CorpCA, which is hosted on cahost.contoso.com. Then your Management Server needs to trust CorpCA as a root certificate authority. If the Management Server doesn't trust the CA, then the Gateway's client cert is worthless. This is the motivation behind the CA Certificate.
To dowload the CA certificate from CorpCA and save it as CAcertificate.cer, use the following command line:
certutil -f -config "cahost.contoso.com\CorpCA" -ca.cert CAcertificate.cer
To place CACertificate.cer in the Local Computer Trusted Root Certificate Authorities store, use the following command line:
certutil -addstore Root CAcertificate.cer
More information on certutil usage can be found at http://technet2.microsoft.com/windowsserver/en/library/a3d5dbb9-1bf6-42da-a13b-2b220b11b6fe1033.mspx?mfr=true
Obtaining and Installing a Client Certificate
Now let's get a client certificate which will be presented when attempting to authenticate. There are a few steps to do this via command line.
- Create the INF configuration file
Open Notepad and make a new file named "RequestConfig.inf" Paste the following text into the file:
(If your CA is stand-alone)
[NewRequest]
Subject="CN=<Machine FQDN>"
Exportable=TRUE
KeyLength=1024
KeySpec=1
KeyUsage=0xf0
MachineKeySet=TRUE
[EnhancedKeyUsageExtension]
OID=1.3.6.1.5.5.7.3.1
OID=1.3.6.1.5.5.7.3.2
(If your CA is enterprise and has implemented a template call OpsMgrCertificate as detailed in the above-linked guide)
[NewRequest]
Subject="CN=<Machine FQDN>"
KeySpec=1
KeyUsage=0xf0
MachineKeySet=TRUE
[RequestAttributes]
CertificateTemplate="OpsMgrCertificate"
2. Convert the INF into a binary REQ file.
Run the following command line to create BinaryRequest.req from RequestConfig.inf:
certreq -new -f RequestConfig.inf BinaryRequest.req
More information on the syntax of the INF file, as well as detailed usage information for CertReq, can be found at http://technet2.microsoft.com/windowsserver/en/library/008acdeb-0650-4063-a9a2-1258b3229d4f1033.mspx?mfr=true
3. Submit the binary request to the CA and retrieve the resulting certificate.
Run the following command line to submit BinaryRequest.req to CorpCA :
certreq -submit -f -config "cahost.contoso.com\CorpCA" BinaryRequest.req
If your CA is set up to auto-approve certificate requests, you will immediately be prompted to save the resulting certificate. If you anticipate this to be the case, you can optionally skip the Save dialog by specifying the filename you want to save to (for example NewCertificate.cer) as an extra argument to the above command line.
Otherwise the RequestId of your request will be printed to the console. An admin at the CA must then choose to issue the certificate. Once the cert is issued, you can retrieve it and save the certificate as NewCertificate.cer by running the following command line:
certreq -retrieve -f -config "cahost.contoso.com\CorpCA" <RequestId> NewCertificate.cer
4. Install the certificate
To install NewCertificate.cer into the Local Computer Personal store, run the following command line:
certreq -accept NewCertificate.cer
And there you have it! You should now have the needed CA certificate and client certificate, both installed in the proper places. From here run MOMCertImport.exe (either double click it to use the GUI or run with the /SubjectName command line flag) to have Ops Mgr consume your new certificate and being authenticating with it. These steps need to be followed on both the Management Server and the Gateway.
Below is a simple batch script GetCert.cmd which ties together all of the steps above. This script is suitable for stand-alone CorpCA, set to auto-approve all requests.
if {%1} equ {/?} goto USAGE
if {%1} equ {-?} goto USAGE
if {%1} equ {?} goto USAGE
if {%1} equ {} goto USAGE
set subjectname=%1
set certpath=%systemdrive%\OMCertificates
mkdir %certpath%
rem Get the CA's cert
certutil -f -config cahost.contoso.com\CorpCA -ca.cert %certpath%\CACertificate.cer
rem Move the CA's cert to the "Trusted Root Authorities" store
certutil -f -addstore Root %certpath%\CACertificate.cer
rem Create an INF request file with the specified subjectname
del %certpath%\RequestConfig.inf
echo [NewRequest] > %certpath%\RequestConfig.inf
echo Subject="CN=%subjectname%" >> %certpath%\RequestConfig.inf
echo Exportable=TRUE >> %certpath%\RequestConfig.inf
echo KeyLength=1024 >> %certpath%\RequestConfig.inf
echo KeySpec=1 >> %certpath%\RequestConfig.inf
echo KeyUsage=0xf0 >> %certpath%\RequestConfig.inf
echo MachineKeySet=TRUE >> %certpath%\RequestConfig.inf
echo [EnhancedKeyUsageExtension] >> %certpath%\RequestConfig.inf
echo OID=1.3.6.1.5.5.7.3.1 >> %certpath%\RequestConfig.inf
echo OID=1.3.6.1.5.5.7.3.2 >> %certpath%\RequestConfig.inf
rem Create a binary request file from the INF
del %certpath%\BinaryRequest.req
CertReq -New -f %certpath%\RequestConfig.inf %certpath%\BinaryRequest.req
rem Submit the request to our CA and save the certificate
CertReq -Submit -f -config "cahost.contoso.com\CorpCA" %certpath%\BinaryRequest.req %certpath%\NewCertificate.cer
rem This step needed to import the private key. Also puts the certificate in the local computer personal store.
certreq -accept %certpath%\NewCertificate.cer
goto END
:USAGE
echo.
echo GetCert.cmd FQDN_of_machine
echo Example: GetCert.cmd Computer01.Contoso.com
echo Gets and installs a cert from CA cahost.contoso.com (CorpCA) appropriate for OMv3, and also gets and installs CA cert so this CA is trusted.
echo.
:END
Watch the attached video on how to cluster a Root Management Server and promote a Management Server to take the role of a Root Management Server
.
Starr and Myself did a talk at MMS 2008 in Las Vegas on how to build a resilient Operations Manager 2007 infrastructure. In this talk we demonstrated how to move the Operations Database, promote a management server to take the role of the Root Management Server (RMS) and detailed steps on how to cluster the Root Management Server on a 2 node Active-Passive cluster. The attached video is a recording of the session we did at MMS 2008 and I think the demo’s shown will be very valuable for anyone who is trying out MS promotion or trying to cluster the Root Management Server. The demo’s also show how to configure Management Server failover using Active Directory integration.
You can download the video from this link:http://download.yousendit.com/538FCEF51CF1ECA4
[Edit: This link is currently unavailable; stay tuned while we find a new spot for hosting.]
Enjoy the video
Satya Vel | Program Manager | System Center |
Attachment(s): http://download.yousendit.com/0409F98568765C22
Agentless Exception Monitoring (AEM) of System Center Operations Manager and System Center Desktop Error Monitoring (DEM) are identical features with the only difference being that AEM is shipped with Operations Manager 2007 and DEM is shipped with Microsoft Desktop Optimization Pack (MDOP) SKU’s. These features leverage the Microsoft Error Reporting (formerly known as Dr. Watson) or Windows Error Reporting client applications for reporting the crash or hang. These client applications are shipped with default settings to forward the Error reports to Microsoft Error Reporting Service. Using DEM, they can be configured to forward the Error reports to DEM or Operations Manager Server.
The attached document describes the steps you need to take to ensure that the Microsoft Error Reporting and Windows Error Reporting are configured correctly. I would like to thank Vishwa for spending time walking me through all the steps to troubleshoot the "DEM" thing :)
Hope this document helps PSS folks and customers.
- Satya Vel
Attachment(s): Troubleshooting AEM and DEM.docx
The Microsoft Operations Manager 2007 Security Hardening Guide is designed to provide you with essential information about how to further protect, or harden, your Operations Manager 2007 environment in conjunction with the Security Configuration Wizard (SCW). SCW is an attack-surface reduction tool for products running the Windows Server 2003 operating systems with Service Pack 1, the Windows Server 2003 operating systems with Service Pack 2, and the Windows Server 2003 R2 operating systems.
In addition to practical, hands-on configuration recommendations, this guide includes information about how to upgrade an agent that have been locked down, how to customize port numbers that have been changed from their defaults, and some examples for hardening a server and an agent. Although most server administrators can benefit from reading this guide, it is designed to produce maximum benefits for administrators responsible for Operations Manager 2007 security. The System Center Operations Manager 2007 SCW Roles and Security Hardening Guide for Windows Server 2003 is available at http://go.microsoft.com/fwlink/?LinkId=120136.
The tool linked in this article allows you to view and configure the data warehouse data retention policies configured within your Operations Manager DW.
Follow the instructions below to use.
Prerequisites
Operations Manager 2007 SP1
Operations Manager 2007 Reporting SP1
Installation
Download the attached zip file and copy the required version of the file either x86 or x64 to a local directory such as “c:\dwdatarp\”
Usage
· To view dwdatarp.exe usage instructions run:
c:\dwdatarp\dwdatarp.exe
· To view current Data Retention settings run:
c:\dwdatarp\dwdatarp.exe –s “dw servername” –d “dw databasename”
example: C:\dwdatarp>dwdatarp -s opsmgrsp1 -d OperationsManagerDW
· To set Data Retention for a particular dataset run:
c:\dwdatarp\dwdatarp.exe –s “dw servername” –d “dw databasename” – ds “dataset name” –a “aggregation name” –m “days”
example: C:\dwdatarp>dwdatarp -s opsmgrsp1 -d OperationsManagerDW – ds “Performance data set” –a “Hourly aggregations” –m 399
Notes:
1. The server with dwdatarp.exe installed must have access to the OperationsManagerDW along with the user running the tool.
2. Updates are applied with immediate effect and data will be groomed during next grooming workflow.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included utilities are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Daniel Savage
Program Manager | System Center Operations Manager
Attachment(s): dwdatarp.zip
Issue: If you try to install a secondary Management Server (MS) in a scenario with Root Management Server(RMS) and Reporting installed with Data Warehouse(DW) action account and Root Management Server action account (default action account) is the same, the secondary Management Server setup rolls back with an error in the setup log:
Error from log file:
**********************
AddRunAsProfilesCA: Error: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index,
Stack: at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at System.Collections.Generic.List`1.get_Item(Int32 index)
at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.AddRunAsProfile(String profleGuid,
MonitoringObject hostedHealthService, ManagementGroup managementGroup, String currentActionUserDomain, String currentActionUserName)
at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.AddRunAsProfiles(Session session)
Cause: In OpsMgr Service Pack 1 setup if DW Action account is same as RMS action account we do not configure DW RunAs profile. So, when you attempt to install second MS we try to configure its DW RunAs profile with DW Action account by looking at RMS DW RunAs profile which is empty. (This happens when default action account is same as DW action account and installation scenario is: RMS and Reporting is installed and then second MS is attempted to install).
Workaround:
Create a ‘Windows’ Run As Account with same domain user as that of RMS Action Account.
Associate this account to ‘Data Warehouse Account’ RunAs profile
Associate this account to ‘DW Configuration and Synchronization Reader Account’ profile (in SP1 this is called as ‘Reserved’, there would be three Reserved profiles in SP1, this one is third in the list). Re-run Management Server setup.
Needless to say this will be fixed in Service Pack 2.
-Satya
We've had a couple of queries about the ASP.NET management pack guide. It's in the process of being released, but in the meantime, use the copy attached to this post. [Edit: If you don't see the attachment at the bottom of the post, come to our blog page and click the green post title. It will take you to a page with the attachment at the bottom.]
If you're reading this post after June 2008, check the management pack for the latest guide; it's possible the guide will have changed since I posted this.
Attachment(s): OM2007_MP_ASPNET.doc
Task Status has two states Success or Fail, the way this is mapped from the 4 states that the module can return is that only Fatal Errors result in Failed tasks. Since this module is used in both rules and tasks and in the rule case we do not want to unload we only return Fatal Errors if the problem is deemed to be unrecoverable, meaning the next time the module runs there is no chance it will complete successfully.
So the trick is to make the module return Fatal Error. This is difficult at best in RTM, however in SP1 there is a reasonable way to accomplish this. On the Module there is an ‘EventPolicy’ element, this element drives when the Script and Command Executor modules create events in the event log, but it also controls how those events are reported to the engine. Which means that you as an MP author have control over how errors are reported. This element is defined as:
<xsd:complexType name="CommandExecuterEventPolicyType">
<xsd:sequence>
<xsd:element minOccurs="0" maxOccurs="1" name="Severity">
<xsd:simpleType>
<xsd:restriction base="xsd:integer">
<xsd:minInclusive value="0"/>
<xsd:maxInclusive value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" maxOccurs="1" name="StdOutMatches" type="PolicyExpression"/>
<xsd:element minOccurs="0" maxOccurs="1" name="StdErrMatches" type="PolicyExpression"/>
<xsd:element minOccurs="0" maxOccurs="1" name="ExitCodeMatches" type="PolicyExpression"/>
</xsd:sequence>
</xsd:complexType>
Basically this element contains a ‘Severity’ element, as well as a ‘StdOutMatches’, ‘StdErrMatches’, and a ‘ExitCodeMatches’ elements.
The values for Severity are as follows:
|
Warning |
0 |
Problem is expected and did not result in loss of data. |
|
Data Loss |
1 |
This is the default value, the problem resulted in data being dropped or not created. For instance an unexpected script error caused data to not be generated. |
|
Fatal Error |
2 |
This means the problem is unrecoverable and should result in the module being unloaded. |
The values for the remaining fields are all the same:
<xsd:complexType name="PolicyExpression">
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="Operator" type="PolicyOperatorType" use="optional"/>
<xsd:attribute name="CaseSensitive" type="xsd:boolean" use="optional"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:simpleType name="PolicyOperatorType">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="MatchesRegularExpression"/>
<xsd:enumeration value="DoesNotMatchRegularExpression"/>
</