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
Comments
The core script you provided really helped me troubleshoot. It turned out the main issue I had was due to my own misunderstanding of how the mailbox is used in "windows" mode. I continued to try using the mailbox I named in the script which was not owned by the account under which the scheduled task was running. That will lead on to another question which I will ask at a later date if I still have other issues. Many thanks again and to all other who contribute. This connector has really saved us a pile of grief and is "the business". Ben
Question: What would be the best way to accomplish this --
I would like to have IR's created from a monitoring software that send emails alerts. For example, if an email is received indicating a drive on a server has reached 90% capacity, I would like to automatically create an IR and apply a template.
Based on different keywords in the email, maybe I could apply different templates.
In this particular use case, I'd choose SCOM and the SCOM Alert Connector above all of them. But if email is truly the only option as it sounds like this is an external monitoring system, then I think any of these 3 are viable options.
Great work on the connector!
Would it be possible to get mailbox redirection working for a mailbox with multiple smtp adresses?
Would eliminate the need to have a mailbox for each forward.
the information should be retrivable from the "TO" field in the header.
did a test today but didnt manage to get it working.
Will do a deepdive tomorrow.
I have configured it like this
but it still creates he ticket with the default ir template.
Im using ID of the template since i cant get it to work with displayname.
150+ commits.
Let's start 2019 with SMLets Exchange Connector v1.5!
Custom Work Item Prefixes: Using different Work Item prefixes than the stock IR, SR, PR, CR, etc? Whatever you've set them as, the connector now honors the most core of SCSM customizations.
Control Related Comments: The most classic of Exchange Connector "bugs". When a user who isn't the Affected or Assigned To it leaves a Comment it's left as a Null Analyst Comment. Now instead of digging through the Connector's PowerShell to change these values, they've been brought up into central configuration for easier modification. If you are considering changing these values, make sure you read the aforementioned link first.
Support for Azure AI Score Class Extensions: Using Azure Cognitive Services is one thing, but leveraging the Sentiment Scoring outside of the initial email creation in your own unique way could lead to some interesting possibilities. That's why the latest version of the connector now supports writing these returned scores from Azure to your own custom Decimal class extensions so you can further report or automate against them.
Dynamic Work Item Analyst Assignment: Analysts not picking up new Work Items? Trying to make sure things get assigned before everyone heads out to lunch? Attempting to lower your average Time to Resolution/Completion, or maybe you're @Silas_Sulser who originally indirectly raised this - the one thing that the SMlets Exchange Connector can now do is assign New Work Items out to Analysts within the Default Template's Support Group.
- Completely Random Assignment = Get all the Analysts in the Support Group and randomly assign out
- Lowest Assigned Work Item volume = Get all the Analysts in the Support Group, evaluate their currently assigned Work Items and assigns to the one with the least amount open Work Items.
- Completely Random Assignment with Exchange Out of Office = Assigning Work Items out doesn't do much good if the Analyst that got Assigned to is Out of Office. Fortunately you can leverage my latest GitHub solution for core Service Manager with SCSMOutOfOffice and prevent Work Item assignment when people are out of office. In doing so, the SMlets Exchange Connector will randomly assign Work Items out as long as the Analyst has not set their out of office.
- Lowest Work Item volume with Exchange Out of Office = Evaluate Analyst's currently assigned work item volume and assign as long as they aren't out of office using the SCSM Out of Office mp. If they are, move onto the next.
Intelligent Work Item Decisioning, Routing and Classification with Azure Machine Learning: Today we take the SCSM Data Warehouse beyond reporting. Utilizing the power of Azure Machine Learning, the connector now supports integration to Azure ML to determine if the email should become an Incident or Service Request, the Classification of that item, and finally its Support Group. Using the provided walkthrough and sample data warehouse queries included on the Wiki, you can perform an extract/upload from your DW to Microsoft and train AML on your Work Item data specific to your organization. Once trained, the connector will submit new emails to Azure in order to perform initial Work Item triage using configurable minimum confidence levels to set these fields. (e.g. Minimum Support Group Confidence must be greater than 95%). And again - tailored entirely to you, your organization and your data. This new AML integration is compatible with continued use for Azure Cognitive Services for Priority Scoring and the above new Dynamic Assignment feature...although this speaks to a future where those could be predicted as well.This feature requires an Azure subscription along with a deployed instance of Azure Machine Learning Studio. It may incur monthly costs depending on usage. Please ensure you understand the potential financial costs to your organization before enabling this feature. Here's how to find information on pricing and how you can test the service out for free via the web.
My thanks go out to @Tom_Hendricks and @Justin_Workman on this release for reviewing, raising bugs, and addressing them. You guys rock!
The introduction of Azure Machine Learning to the connector is without question the most advanced feature to date for the SMLets Exchange Connector. Apart from its listed use above, you also stand to gain improved reporting and shining a light on your less used classifications. All of this now realized through PowerShell, Azure, and the CMDB that today wakes up - your Service Manager deployment.
For some reason i cant use -Displayname i get an error "cannot find null template" something.
I changed the get-scsmobjecttemplate to
ID works fine for creating the workitem, its just not creating it with the correct template for when i send to the secondary SMTP adress.
$Mailboxes = <a rel="nofollow" href="https://community.cireson.com/profile/%7B">@{</a><div> "sysapp@skovde.se" = <a rel="nofollow" href="https://community.cireson.com/profile/%7B%22DefaultWiType%22%3D%22ir%22" title="Link: https://community.cireson.com/profile/%7B%22DefaultWiType%22%3D%22ir%22">@{"DefaultWiType"="ir"</a>;"IRTemplate"="<b>THE NAME OF MY TEMPLATE</b>";"SRTemplate"="My SR Template";"PRTemplate"="My PR Template";"CRTemplate"="My CR Template"};</div><div>}</div>If the DisplayName of your template is "THE NAME OF MY TEMPLATE" then the above code example would work for you. In an attempt to keep configuration reasonably simple, this hashtable is meant for you to provide the name here, rather than passing in an object. Further down in the script, it will look up your template by its displayname. You do not have to do this.Yes i get that.
But as i said when i run Get-SCSMObjectTemplate -DisplayName "The name of the template" i get
I have tried -ComputerName and verified that im typing the correct displayname of the template.
-ID is working
I have replaced all Get-SCSMObjectTemplate -displayname with -ID in the entire script and where-object {$_.ID -eq "$DefaultIRTemplateName"}
Shouldnt make any difference if i get the template with the guid or the displayname?
However, something else seems to be happening here. For example:
- If you run Get-ScsmObjectTemplate -DisplayName "The Wrong Template Name That Will Not Match Anything" nothing will be returned, but no exception will occur either.
- If you run Get-ScsmObjectTemplate -DisplayName "" (an empty string) then you will get all templates back at once.
- The only way to make that error occur is Get-ScsmObjectTemplate -DisplayName $null or something equivalent. In other words, you are apparently not sending a name over at all, so you should check your variable name that you are passing in, or whatever line of code is assigning a value to it.
Feel free to PM me if you are still having trouble. We can log an issue if there is something going on here with the script.when users send in comments to SRs the comment isnt added to the workitem. works for IR.
Tried to run it manually but im getting this when it tries to create the user comment
I have been trying the new dynamic assignment feature presented in 1.5 but haven't gotten it to work yet. Tried both random and volume as variables but it just keeps the assignedTo blank. The default template used has a support group mapped to it and the cireson portal does recognize the users within the group.
I am not getting any errors when the script runs. Has anyone else experienced this?
Raised and will investigate @Kenneth_McMichael
I've got a stupid question. I've downloaded 1.5 ZIP and now am looking for any Installation or Configuration documentation. Can you point me in the right direction?
Not a stupid question at all, if anything you've just given me an idea. But anyway, the Wiki on the repo covers a couple ways to setup.
https://github.com/AdhocAdam/smletsexchangeconnector/wiki/Configuration-Examples
We found that there is an issue in the way our process Completes Manual Activities. We have several MAs that go to a group of people and one MA that is used as a placeholder while an external program runs and emails Complete to the placeholder MA (basically this stops the ticket from closing until the external program does it's thing. Long story short, we have lots of MAs with no Activity Implementer.
How can we bypass the requirement that an inbound email to Complete the MA has to be from the Activity Implementer?
I figured I'd ask before weeding through code.
Bypass the requirement? Quite easily 😁
Check out the following line for the Complete/MA logic.
Certainly a scenario I never considered, but one that gives rise to an interesting path. If the person Completing is not the Implementer, then make them the Implementer when the Complete action takes place. Hrmmmm.
You read my mind and I was trying to find a way to fire a [take] command inside the If block.
Anyway, the quick fix was surprisingly simple:
1) created a var (on line 238): $BypassActivityImplementerRestriction = $true
2) on line 1481 (was 1480), I changed to: if ((($activityImplementerSMTP.TargetAddress -eq $message.From) -or $BypassActivityImplementerRestriction) -and ($commentToAdd -match "\[$completedKeyword]"))
3) did the same for the Skip, line 1489 (was 1488).
This may have been mentioned above, but I couldn't find it in the tread. I was able to use the Schedule Outlook Meeting in both Firefox and Chrome, but sadly fails for Edge and IE (IE wants to find an App to process DATA).
Don't know if this is a bug or bad settings on my end. Thanks!
This looks like it's an issue around how the browsers choose to handle the Javascript that generates the ICS file on the fly that is different in IE/Edge than Chrome/Firefox. Raised over here.
Today v1.6 arrives on GitHub!
Azure Translate: When it comes to support, why should language be a barrier? Now with integration into the Azure Cognitive Services Translator API, you can now receive emails that create Incidents or Service Requests from your Affected Users in over 60 languages and have them automatically converted to a default language for your Analysts. But if you really want to close the loop, then it's time to set the Locale on all of your SCSM User CIs and to deploy the new complimentary SCSM Translate management pack. The practical upshot of which is that employees will be able to communicate in their native languages to one another through SCSM and have translation automatically performed for them via Azure through email, portal, or console.
Enhancements: Azure Machine Learning predictions and scores can now be written to class extensions on Incidents and Service Requests so you can report, calibrate, and improve your training models.
Translation services requires an Azure subscription along with a deployed instance of Azure Translate. It may incur monthly costs depending on usage. Please ensure you understand the potential financial costs to your organization before enabling this feature. Here's how to find information on pricing.
Thanks go out to community members @Kenneth_McMichael , @Matt_Overton , and @Magnus_Lundgren1 for their attention to detail, reporting issues, and improvements to documentation.
We're on the verge of the first major upgrade that will move the connector into v2.0 territory. It's an upgrade that's been in the works for sometime now as the connector's configuration will shift out of PowerShell and into a dedicated management pack with a fully fledged UI accessible via the SCSM Console's Administration Pane. Curious to see what it looks like? You can see for yourself with v2.0 Release Candidate 2.
@Adam_Dzyacky
This new GUI version is awesome. Well done.
I have a question regarding closed SR's. I have a request from analysts to create a new IR if a user replies to an closed SR. This will mean to copy the title and description and relate the new IR and closed SR.
They wanted to re open the SR, but I said that it is not alligned with ITILL best practices. So the proposed solution are knd of meeting them halfway.
Regards
G
@Gerhard_Goossens we have that feature currently, however it's not the exact implementation you're asking for. Through the $CreateNewWorkItemWhenClosed value (true/false), if an End User replies to a Incident or Service Request that's closed it will create a new IR/SR, copy the Title/Description over, and then relate the two Work Items together. But the short version is - Closed IR creates New IR. Closed SR creates New SR.
You can see this in the Update-WorkItem function below.
And also - thank you. 😁
@Adam_Dzyacky I haven't read through all of the features of your exchange SMLets connector, but is a there way that if the connector would catch an analyst comment on an IR/SR that just arrived it would meet/ set the first response time, without needing to "acknowledge" the IR/SR?
We did a large portal upgrade (a leap , I'd say) way back in the summer. Most of our analysts have been using the console before that and not everyone has yet adapted topressing "ackonwledge" each time they want to meet the First response SLA, so they just write a normal "analyst comment" to the ticket, but this is ignored by the SLA.
Thanks!
G.