| Author |
Message |
|
|
SLA has little thing to do with size.
It has EVERYTHING to do with the culture... and since culture means people it won't matter be it in a garage shop or multibillion integalactic corporates.
The main drive of SLA is that parties are "motivated" to do their job by mapping the competency into the legal domain. SLA means shit in spots with "challenged" government (read:law enforcement).
Scale it down...
SLA means shit in corporates with "challenged" management.
|
|
|
For those who had too many wars and long for peace and good will towards hardwares and softwares... they will shift more and more toward preventive initiatives. The way I see it... it's what all the bells and whistles build into sysaid is for in the first place anyway.
Instead of working on SR, we should beat the trend by monitoring and maintenance.
Now if monitoring got all the attention (and STILL no charts !) why, in the name of ELVIS, maintenance have to stuck in the back seat ?
I think it should be in it's own menu with complete set of what an average IT Joe would need like :
1. Tab to list todolist and or checklist.
2. Tab to embed portable softwares.
3. Tab to log/copy paste things which should be easily transform into a pdf report.
4. Tab to fire message/task or sort to order spare part, inquire warranty, fire an SR to vendors...
you got the picture.
No ?
|
|
|
Areas that would directly benefit from this are asset mgmt and monitoring.
Depending on how macho the dev elves I can see potential in project and the ITIL thingy.
|
|
|
OMG.... Robert Redford...
*smitten*
|
|
|
Strange.. my sysaid server just consumed 2Gig of the memory... causing anxiety among the users...
And when I checked, java.exe is the culprit.
Coincidence ?
|
|
|
I got one that's not even a history yet...
"I want to keep EVERYTHING on the server FOREVER. You will not delete ANYTHING !."
The file server quit like two weeks ago because it's too full (yess... I've warned and threat and all...) instead of forging a document management policy, we're looking to upsize the SAN and implement mail archiver (I discovered a 4 gig pst file !).
Aligning IT with business ?
Yeah right.
|
|
|
|
computer freeze is caused either by cpu and or memory load...
|
|
|
Bigmac...
When I was having problem we too only use one browser (firefox) at the time. The problem with coexisting browser still happen because :
1. IE is installed by default.
2. Autoupdate windows upgraded IE.
And the weirdest part is :
3. Browsers seems to share programs with each other.
Firefox seems to depend on some capability of IE, Chrome seems to use some of firefox's module...
So heads up.
|
|
|
The SQL won't be a problem...
Although you won't have them both in production... but you do need them both running so the problem would be more on the DNS which I think related to license.
Fire a formal sr to ilient even though it's just consulting.
*smile*
|
|
|
Those different flavour of browsers better not exist in the same machine.
I have issued having firefox and ie co-exist. I solved it by downgrading one of them.
|
|
|
Ouch...
Exchange mail protocol (MAPI) only supported recently by the release of the newest version (ver. 7). Before that only pop would work.
The way I see it... you got two option :
Upgrade to version 7
Or...
You setup mailbox outside the organization that support smtp only scheme.
|
|
|
By default sysaid will mail user when status is change.
If you haven't change this then using escalation is correct but use it to change the status of the sr instead of firing e-mail.
Let sysaid do the rest.
|
|
|
*smile*
Slick...
We just have a building expansion... I'll see if the force is with me on this one.
Most grateful for the cool tips
*slight nod wider smile*
|
|
|
Prolly just miss a step of this
|
|
|
|
Try this..
|
|
|
