Options
TERMS OF USE
AGREEMENT BETWEEN USER AND CIRESON
The Cireson Community Web Site is comprised of various web pages operated by Cireson, LLC (collectively, the web pages are referred to herein as the “Cireson Community Web Site”).
The Cireson Community Web Site is offered to you conditioned on your acceptance of the terms, conditions, and notices contained herein without modification or exception. Your use of the Cireson Community Web Site constitutes your agreement to all such terms, conditions, and notices contained in these Terms of Use.
MODIFICATION OF THESE TERMS OF USE
Cireson reserves the right to change the terms, conditions, and notices under which the Cireson Community Web Site is offered, including but not limited to the charges associated with the use of the Cireson Community Web Site upon written notice.
LINKS TO THIRD PARTY SITES
The Cireson Community Web Site may contain links to other Web Sites (“Linked Sites”). The Linked Sites are not under the control of Cireson and therefore Cireson is not responsible for the contents of any Linked Site, including, without limitation, any link contained in a Linked Site, or any changes or updates to a Linked Site. Cireson is not responsible for webcasting or any other form of transmission received from any Linked Site. Cireson is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Cireson of the site or any association with its operators.
NO UNLAWFUL OR PROHIBITED USE
As a condition of your use of the Cireson Community Web Site, you warrant to Cireson that you will not use the Cireson Community Web Site for any purpose that is prohibited by law, rule regulation or by any of these terms, conditions, and notices, including, without limitation the export of any Software or technical data to any country prohibited by law. You may not use the Cireson Community Web Site in any manner which could damage, disable, overburden, or impair the Cireson Community Web Site or interfere with any other party’s use and enjoyment of the Cireson Community Web Site. You may not obtain or attempt to obtain any materials or information through any means not intentionally made available or provided for through the Cireson Community Web Site.
USE OF COMMUNICATION SERVICES
The Cireson Community Web Site may contain bulletin board services, chat areas, news groups, forums, communities, personal web pages, calendars, and/or other message or communication facilities designed to enable you to communicate with the public at large or with a group (each a “Communication Service,” and collectively, “Communication Services”). You agree to use the Communication Services only to post, send and receive messages and material that are appropriate, proper and related to the particular Communication Service. By way of example, and not as a limitation, you agree that when using a Communication Service, you will not:
Cireson has no obligation to monitor the Communication Services. However, Cireson reserves the right to review materials posted to a Communication Service and to remove any materials in its sole discretion. Cireson reserves the right to suspend or terminate your access to any or all of the Communication Services at any time without notice for any reason whatsoever.
Cireson reserves the right at all times to disclose any information as necessary to satisfy any applicable law, rule, regulation, legal process or governmental request, or to edit, refuse to post or to remove any information or materials, in whole or in part, in Cireson’s sole discretion.
Always use caution when giving out any personally identifying information about yourself or your children in any Communication Service. Always use caution when giving out any information concerning your employer or customers, if any. Cireson does not control or endorse the content, messages or information found in any Communication Service and, therefore, Cireson specifically disclaims any liability with regard to the Communication Services and any actions resulting from your participation in any Communication Service. Managers and hosts are not authorized Cireson spokespersons, and their views do not necessarily reflect those of Cireson.
Materials uploaded to a Communication Service may be subject to posted limitations on usage, reproduction and/or dissemination. You are responsible for adhering to such limitations if you download the materials.
MATERIALS PROVIDED TO CIRESON OR POSTED ON THE CIRESON COMMUNITY WEB SITE
Cireson does not claim ownership of the materials you provide to Cireson via the Cireson Community Web Site (including feedback and suggestions) or post, upload, input or submit to the Cireson Community Web Site or its associated services (collectively “Submissions”). However, by posting, uploading, inputting, providing or submitting your Submission you are granting Cireson, its affiliated companies and sublicensees permission to use your Submission in connection with the operation of their Internet businesses including, without limitation, the rights to: copy, distribute, transmit, publicly display, publicly perform, reproduce, edit, translate and reformat your Submission; and to publish your name in connection with your Submission.
No compensation will be paid with respect to the use of your Submission, as provided herein. Cireson is under no obligation to post or use any Submission you may provide and may remove any Submission at any time in Cireson’s sole discretion.
By posting, uploading, inputting, providing or submitting your Submission you warrant and represent that you own or otherwise control all of the rights to your Submission as described in this section including, without limitation, all the rights necessary for you to provide, post, upload, input or submit the Submissions.
LIABILITY DISCLAIMER
THE INFORMATION, SOFTWARE, PRODUCTS, AND SERVICES INCLUDED IN OR AVAILABLE THROUGH THE CIRESON COMMUNITY WEB SITE MAY INCLUDE INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN. CIRESON (OR ITS SUPPLIERS) MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE CIRESON COMMUNITY WEB SITE AT ANY TIME. ADVICE RECEIVED VIA THE CIRESON COMMUNITY WEB SITE SHOULD NOT BE RELIED UPON FOR PERSONAL, MEDICAL, LEGAL OR FINANCIAL DECISIONS AND YOU SHOULD CONSULT AN APPROPRIATE PROFESSIONAL FOR SPECIFIC ADVICE TAILORED TO YOUR SITUATION.
NEITHER CIRESON NOR ANY OF ITS SUPPLIERS MAKE ANY REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, AVAILABILITY, TIMELINESS, AND ACCURACY OF THE INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS CONTAINED ON THE CIRESON COMMUNITY WEB SITE FOR ANY PURPOSE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, ALL SUCH INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS ARE PROVIDED “AS IS” WITHOUT WARRANTY OR CONDITION OF ANY KIND. CIRESON AND/OR ITS SUPPLIERS HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL CIRESON AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OR PERFORMANCE OF THE CIRESON COMMUNITY WEB SITE, WITH THE DELAY OR INABILITY TO USE THE CIRESON COMMUNITY WEB SITE OR RELATED SERVICES, THE PROVISION OF OR FAILURE TO PROVIDE SERVICES, OR FOR ANY INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS OBTAINED THROUGH THE CIRESON COMMUNITY WEB SITE, OR OTHERWISE ARISING OUT OF THE USE OF THE CIRESON COMMUNITY WEB SITE, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF CIRESON OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES. BECAUSE SOME STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU. IF YOU ARE DISSATISFIED WITH ANY PORTION OF CIRESON COMMUNITY WEB SITE, OR WITH ANY OF THESE TERMS OF USE, YOUR SOLE AND EXCLUSIVE REMEDY IS TO DISCONTINUE USING THE CIRESON COMMUNITY WEB SITE.
SERVICE CONTACT: team@cireson.com
TERMINATION/ACCESS RESTRICTION
Cireson reserves the right, in its sole discretion, to terminate your access to the Cireson Community Web Site and the related services or any portion thereof at any time, without notice.
GENERAL
To the maximum extent permitted by law, this agreement is governed by the laws of the State of California, U.S.A. and you hereby consent to the exclusive jurisdiction and venue of courts in San Diego County, California, U.S.A. in all disputes arising out of or relating to the use of the Cireson Community Web Site. Use of the Cireson Community Web Site is unauthorized in any jurisdiction that does not give effect to all provisions of these terms and conditions, including without limitation this paragraph. You agree that no joint venture, partnership, employment, or agency relationship exists between you and Cireson as a result of this agreement or use of the Cireson Community Web Site. Cireson’s performance of this agreement is subject to existing laws and legal process, and nothing contained in this agreement is in derogation of Cireson’s right to comply with governmental, court and law enforcement requests or requirements relating to your use of the Cireson Community Web Site or information provided to or gathered by Cireson with respect to such use. If any part of this agreement is determined to be invalid or unenforceable pursuant to applicable law including, but not limited to, the warranty disclaimers and liability limitations set forth above, then the invalid or unenforceable provision will be deemed superseded by a valid, enforceable provision that most closely matches the intent of the original provision and the remainder of the agreement shall continue in effect. Unless otherwise specified herein, this agreement constitutes the entire agreement between the user and Cireson with respect to the Cireson Community Web Site and it supersedes all prior or contemporaneous communications and proposals, whether electronic, oral or written, between the user and Cireson with respect to the Cireson Community Web Site. A printed version of this agreement and of any notice given in electronic form shall be admissible in judicial or administrative proceedings based upon or relating to this agreement to the same extent and subject to the same conditions as other business documents and records originally generated and maintained in printed form. It is the express wish to the parties that this agreement and all related documents be drawn up in English.
COPYRIGHT AND TRADEMARK NOTICES:
All contents of the Cireson Community Web Site are: Copyright 2016 by Cireson, LLC and/or its suppliers. All rights reserved.
TRADEMARKS
The names of actual companies and products mentioned herein and on the Cireson Community Web Site may be the trademarks of their respective owners.
The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person, or event is intended or should be inferred.
Any rights not expressly granted herein are reserved.
NOTICES AND PROCEDURE FOR MAKING CLAIMS OF COPYRIGHT INFRINGEMENT
Cireson respects the intellectual property of others and asks that users of the Cireson Community Web Site do the same. In connection with the Cireson Community Web Site, we have adopted and implemented a policy respecting copyright law that provides for the removal of any infringing materials and for the termination, in appropriate circumstances, of users of the Cireson Community Web Site who are repeat infringers of intellectual property rights, including copyrights. If you believe that one of the Cireson Community Web Site users is, through the use of the Cireson Community Web Site, unlawfully infringing the copyright(s) in a work, and wish to have the allegedly infringing material removed, the following information in the form of a written notification (pursuant to 17 U.S.C. § 512(c)) must be provided to our designated Copyright Agent:
Please note that, pursuant to 17 U.S.C. § 512(f), any misrepresentation of material fact (falsities) in a written notification automatically subjects the complaining party to liability for any damages, costs and attorney’s fees incurred by us in connection with the written notification and allegation of copyright infringement.
Designated Agent: Matthew W. Deen, Esq.
Address of Agent: 1620 Fifth Avenue, Suite 875, San Diego, CA 92101
Telephone: 619-993-8873
Fax: 888-244-8458
Email: matt.deen@cireson.com
Answers
Yes and No, depends on system. The query is only returning the failed jobs. Failed Jobs happen, the real question is are they failing all the time.
Here is a query we have (From MS) to review the internal job history.
The key is that follow up jobs completed. (You can change the top 4 to say top 10 to see more history)
-- InternalJobHistory StatusCode = 1 = SUCCESS / Completed, it is not uncommon for result to be 0 as long as it later succeeds
use ServiceManager
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_GroomSubscriptionSpecificRECLRows 55270A70-AC47-C853-C617-236B0CFF9B4C%' order by TimeStarted desc
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_GroomSubscriptionSpecificECLRows 55270A70-AC47-C853-C617-236B0CFF9B4C%' order by TimeStarted desc
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_GroomStagedChangeLogs 55270A70-AC47-C853-C617-236B0CFF9B4C%' order by TimeStarted desc
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_GroomManagedEntity A604B942-4C7B-2FB2-28DC-61DC6F465C68%' order by TimeStarted desc
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_GroomManagedEntity E6C9CF6E-D7FE-1B5D-216C-C3F5D2C7670C%' order by TimeStarted desc
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_GroomManagedEntity D02DC3B6-D709-46F8-CB72-452FA5E082B8%' order by TimeStarted desc
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_GroomManagedEntity 422AFC88-5EFF-F4C5-F8F6-E01038CDE67F%' order by TimeStarted desc
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_GroomManagedEntity 04B69835-6343-4DE2-4B19-6BE08C612989%' order by TimeStarted desc
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_GroomChangeLogs 55270A70-AC47-C853-C617-236B0CFF9B4C%' order by TimeStarted desc
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_GroomPartitionedObjects and dbo.p_Grooming%' order by TimeStarted desc
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_GroomTypeSpecificLogTables%' order by TimeStarted desc
Select top 4 * from InternalJobHistory where command like '%Exec dbo.p_DataPurging%' order by TimeStarted desc
When we had our retention policy to 2 years (in our old system) it was nearly impossible to reduce the period afterwards, as 2 or 3 days less led to all grooming jobs to fail permanently - so we had to reduce it by one day every day. Still it was not possible to reduce it to, let's say 1 year. Needless to say our database grew and grew, and the system was unstable - we had to literally restart the sql service on the sql server several times a day.
tl;dr: Set the retention policy as short as possible - Especially with the archiver feature, setting retention policies too high is not necessary imo. We now have it to 30 days for all work items except changes (which is configured to 180 days)
You don't have to wait for the nightly grooming job to run. Once it complete, if you edit the retention time, kick it off again in SQL, to you can step down say over a weekend when there is less load on the system.
Yes I know that.
We tried to manually run the groomings with the query, which microsoft provided - led to a timeout and nothing has been deleted.
Also after deleting all notification objects from our db (script was provided by microsoft), because they have not been related to the user anymore, our DB was in pending recovery status - so the system was completely broken.
Dear Brian / Simon,
I think I might have identified the issue to be with an actual AD Connector maybe. Is there a way to detect what issues are with a specific AD connector / troubleshoot it? Also at the moment the retention is set to 90 days for incidents too, if i set it to say 30 days, will this impact anything for example the datawarehouse?
Thank again.
Daniel
One way to investigate issues is the Event Viewer on your Primary Management Server. We currently have the issue, that our AD User Connector brings in AD Users, which do not exist anymore, and the funny part is, the OU in the LFXSTG.AD_User table points to a non existing OU, which got deleted months ago. I haven't had any success by reviewing the log files, as there were no errors - I ended up opening a case on Microsoft side. So detecting issues with connectors is painful imo. But maybe you are lucky.
The retention period is up to you, but a shorter retention means less data in the DB - but in the current state, people are not able to search for groomed workitems in global search. What do you mean with data warehouse impact? The data should be in the data warehouse, no matter what your retention policy is (if you set it to 0 and the warehouse jobs run after the grooming ofc not ;) ). But as we dropped our data warehouse when the archiver was released, I am no longer able to test something ;) I can just say that 30 days retention period works fine for us, but I am really looking forward to the global search update, where archived work items can be searched for as well :)
Dear Both,
Do you know if there is a limit on the amount of subscriptions SCSM can handle?
We have 37 of them.
Daniel
@CaterhamITSupport I guess it does not make much sense asking for limits specifically.
It depends on when a subscription triggers, the polling interval and the batch size - this is a pretty good explanations of how workflows in general work:
All you can do is to have a look at the workflow performance and if you are falling behind too much. If yes you can still change the polling interval and/or batch size for your custom workflows/subscriptions, but be aware that this might even cause even more trouble - so just do that if you know what to do.
In short, "hard coded" limits exist very rarely (I guess in case of exchange connectors they say 15), it depends on your environment - so asking for them will mostly get you the answer "It depends on your environment" - There are just too many factors. So all you can do is to try!
Depends on what the are connecting to. We have 27 currently. With the goal of not having two connectors attempt to update the same data.
One thing you should watch out for on the AD connector is the option to
When this was enabled it really burned out AD jobs.
If you are syncing the groups you need for the security roles. Do Not have this checked off. It runs every 24 hours on the cycle of the create time of the AD connector.
@Brian_Wiest maybe this is a misunderstanding from my side but do you mean you need this checked, if you want to use AD groups for security roles? We never checked this one and it had no impact on our security roles. But I guess you mean when there is not its own connector for the users which are members of these groups right?
If you are polling specific OU's or LDAP query for just users. And configure the SCSM Security roles via AD groups. Then you must check it.
If your Ad connector is syncing all the groups as part of the OU or LDAP DO NOT check it.
On a support ticket with MS, where our entire farm was becoming unresponsive at 3pm every day ended up being the AD connector and this check box. We pull in the entire AD tree and at 3pm it was expanding the groups for all 30K users including their membership to domain users to it just crushed our environment.
We now have one connector which brings in all users and groups from our domain via LDAP Query (|(objectclass=user)(objectClass=group)) and we don't check it.
Also when we had multiple AD Connectors with LDAP Queries behind, we never had to check this option in order for security groups to work. But I guess I am just misunderstanding what you mean :D But doesn't matter, it works fine for us so no need to discuss this further (for me) ;)