| Author |
Message |
|
|
jbr@rtx.dk wrote:I have just been contacted by an SysAid administrator and he told me how to fix it.
You don't have to disable SSO again - it is an issue with the AJAX code.
Here is what to do:
1. Locate the serverconf.xml file (...\SysAidServer\root\WEB-INF\conf\)
2. Open it to edit.
3. In the bottom of this file, just above </serverConf> add the following line:
<disableAjax>true</disableAjax>
Now the bottom 3 lines will be like this:
<onlineHelpPageURL>http://www.ilient.com/help-page.htm</onlineHelpPageURL>
<disableAjax>true</disableAjax>
</serverConf>
4. Save the file, and you are done.
I hope this will do the trick.
Best Regards,
JBR.
I did that, and it broke SSO. Now no one can access SysAid - they are prompted for a username and password (by an HTTP password request box, not the Login.jsp screen). Even when I remove that line, I still get the prompt. I think I have to disable SSO again to get normal functionality. I will try to open my own ticket with the help desk.
|
|
|
I am having this exact same issue. We just got SSO (single sign-on) working the way we want it to. Please tell me there are options other than disabling it yet again because of some supposedly incompatible sister feature...!
Does anyone have any other resources or light to shed on this issue?
|
|
|
G. de Keijzer wrote:In search for our Kaseya replacement, i'm stuck with the following feature i want:
Scripting
I want to script common tasks on my clients machines, like:
- Reboot
- Deploy software
- Common maintenance tasks
- etc etc
I know that this is currently not available in V6.xxx . Will it be in V7?
Second question. Does anybody know of a good scripting-thingy that i can deploy at my customers and let me control that. Based on a MSP model offcourse.
Regards,
Gerwin
Your Windows domain controller can already manage most of this. Set up a Windows batch file to run at logon through Group Policy. Then just modify this file as necessary when you have new changes that can't be managed via GPO.
Example: I want every computer to reboot at 4am on Monday, Wednesday and Friday:
Search Google for other examples based on what you want to do. If you're looking to script advanced tasks, I'll echo Obelix's recommendation of AutoIt3. I use this for SQL scripting and several other advanced batch + database procedures.
|
|
|
I was in the same boat as all of these guys. It took me a minute to understand why the regulars around here were so confused and perplexed by this usage, because they've always done it the other way - using a dedicated account and having all incoming and outgoing messages recorded in the SysAid software.
It seems like there are two camps of SysAid operators - those that use the software the way I and all these others do, replying directly to users and not tracking replies to messages via SysAid and believing that this is how the software is meant to work... and those that integrated a dedicated address and have always been replying to the service account and tracking incoming and outgoing messages in SysAid.
Until recently I was solidly in the first camp - I opened up a thread back in December of 2008 complaining about this very thing when I attempted to enable integration of a help desk account in SysAid 5.6. I received much the same response from support - "why would you use it that way?" rather than any attempts to understand or fix the issue. Since the software works for pretty much everything else, we dropped the subject for a year.
When we realized that it had been disabled in 7.0, I was able to convince the other admins to make the switch to the service account scenario by adding in the Request User to the subject of the email. Since the functionality is essentially the same, it was worth making the switch.
We love the software and the company that stands behind it, just please realize that something as simple as that undocumented "bug fix" can affect a large group of your users. 
|
|
|
What sort of functionality are you holding out on? 7.0 already gives you so much more than 6.0 does. If you're waiting for a specific issue to be fixed or implemented, check the Known Issues and Feature Requests forums respectively.
Our company is about to go live with 7.0.04 but we've not had any issues during testing that would discourage us from using it.
|
|
|
Exchange Sync is enabled and the Test button says that it is working correctly.
We're not live with 7.0 yet, and I don't object that strongly to having IMAP running since it's only enabled internally. We weren't using incoming mail on 5.6, so I'm more concerned with making sure it all runs smoothly than the protocol being used.
|
|
|
I'm also wondering if the MAPI integration actually works as advertised or if it's just a placeholder cause it wasn't finished in time for 7.0 release
I really don't want to have to enable POP3/IMAP just for this one service. I haven't had any luck using the MAPI protocol for integration. Please let us know if there's anything we're missing here.
|
|
|
RICHI wrote:Where is the App? I've been checking the iPhone App store for SysAid app since Saar said its been released at the SysAid conference - Cannot find when I search for SysAid in App store -
Are we going by any other name than SysAid?
It's going through Apple's review process. The app is finished, but it's not been approved by Apple yet.
|
|
|
A tip I've found useful is to force the computer to send LM & NTLM responses via Group Policy...
Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> Network security: LAN Manager authentication level set to "Send LM & NTLM responses".
This fixed my issue with SSO not working correctly on Windows 7 Professional 32-bit / Internet Explorer 8 and SysAid 7.0.04 with tomcat, Microsoft SQL Server and the jcifs single sign-on module.
|
|
|
A tip I've found useful is to force the computer to send LM & NTLM responses via Group Policy...
Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> Network security: LAN Manager authentication level set to "Send LM & NTLM responses".
This fixed my issue with SSO not working correctly on Windows 7 Professional 32-bit / Internet Explorer 8 and SysAid 7.0.04 with tomcat, Microsoft SQL Server and the jcifs single sign-on module.
|
|
|
feda_z wrote:UP
The Русский equivalent of "bump"? 
|
|
|
LauraB wrote:That method looks a lot more effective than mine! My process involved a big art eraser and ripping up a sheet of paper into five "houses" to rearrange on the desk (I don't recommend that tactic...) After reconsidering, I created a table similar to the one above and got the answer. Don't give up, people - you can do it!
About halfway through the puzzle I drew five houses in a row in the white space and started filling in details. It helps to visualize it, especially when reading the hints about who lives next to whom. I came close to making mistakes but was able to catch myself because it didn't fit with what I could see when looking at the houses.
|
|
|
I love these! I used to solve them all the time as a kid.
For those of you who aren't familiar with this type of puzzle, here's a grid to help you get started:
Fill in all the variables in the long fields on the sides. Use checkmarks and Xs to indicate known true and known false data.
I already have a finished one with all five houses marked in order by occupant, cigar, pet, and beverage...but I won't post that yet, of course
|
|
|
Eli wrote:hey wbeers,
When you receive the email notification it will show you the requested user name who made the service request.
Best Regards,
Eli
Yes, but when the email is received on mobile devices such as our Blackberries, we can see who the email is from without having to open the request. We also can reply directly to the email from the Blackberry without having to manually input the email address each time.
This is how it currently works for us - is the behaviour I'm describing by design, or is there some way for me to enable the incoming email feature without losing my individual email addresses?
|
|
|
I recently enabled incoming emails in SysAid. I set up an email address strictly for this purpose, and now have the ability to email that address and have a new Service Request generated.
Before, however, when the administrators received the service request notification, the email would appear to be from the end user that submitted the ticket, and we would be able to see who was sending in the ticket without even opening the message. Now, however, all notifications are coming in from this new email address I created just for the email service request generation. So, if user "mike" sends a request through the end user portal, the email I get in my inbox is from "sysaid@company.com" instead of "mike@company.com". Is there a way I can revert it back to the end user's address without breaking my new functionality? Or at least have the option to switch between the two
Also, I am having another issue with assets not being automatically selected, and started a thread on it a while back: http://www.ilient.com/Sysforums/posts/list/704.page
If anyone has the time I would appreciate some more insight as to how to get that working. I am well on my way to getting the software customized to our liking, so thank you in advance!
EDIT: Resolved. Clearing the contents of the "Email address" field on the Integration page allows you to still accept incoming emails and create requests but does not cause all emails sent to administrators to be tagged with this address. Don't know if this is a bug or by design; I'm just glad it's working. If anyone has time I would still appreciate help with my other thread, linked above. Thanks
EDIT2: Inaccurate. Okay, so when I cleared the contents of the "Email address" field under Incoming Emails, I also disabled the incoming email section, effectively putting me back to square one. Trying it with Incoming Emails enabled and the blank Email address field caused all notifications to appear from the address listed under the Outgoing Emails section. Clearing that cause emails to stop coming in altogether. So yes, I still need help with this. Sorry for the flip-flop.
|
|
|
