Kaseya Reveals Details of New IT Systems Management Product Line

Real_Wire's picture
Submitted by Real_Wire on

New Family of Products designed for Enterprise Organizations, SMEs and IT Service Providers

London, UK, February 15th 2010 — Kaseya, a leading provider of IT management software, today released details of its new products for enterprise IT departments and IT service providers, which form part of its new Kaseya 2 suite of IT systems management tools.  Kaseya 2 products specifically developed to meet the requirements of IT departments in large enterprises, smaller IT teams working in small to medium-sized enterprises (SMEs), and IT service providers working with multiple clients. 

Using the new Kaseya 2 products, IT professionals in any organization can streamline key tasks and processes, reduce complexity, and increase staff utilization and end-user satisfaction. 

Kaseya Enterprise Edition – created for IT teams looking to improve efficiency and handle increasingly complex IT estates through a proactive IT management model.  With the ability to support thousands of PCs and devices on a variety of platforms, Enterprise Edition provides complete IT systems management through a single web-based interface, with integrated IT automation.  Applications and features include:

IT automation – fully automate desktop and server tasks and procedures, including discovery, audit, monitoring, patch management, anti-virus and backup applications
Live Connect – powerful remote access functionality without interrupting the end user
ITIL-based service desk – fully-integrated incident, problem, change and knowledge base desk with full process, policy and workflow customisation
Enhanced security – granular user, multi-role and scope-based security
Reporting – centralised management reporting and messaging for enhanced communication

Top changes IT must make to survive

Bryan's picture
Submitted by Bryan on

Mary Jander of Internet Evolution takes a hard look at at what IT must do to survive the next few years of economic woes.  She has some sobering things to say, and while we might not like it, she is probably right.  For example, in her first step to IT surviving she says:

Staff levels must go down. Job cuts are now a fact of IT life. Recent announcements portend 5,000 layoffs at Microsoft; a projected 6,000 at Intel; up to 10,000 at IBM.
Cuts like these could decimate an already-pressed IT staff, unless
measures are taken to automate and virtualize more functions.

The idea of reducing costs in hardware and human resources through virtualization has been suggested before (many times). Now is the time to finally give it a try.

She also takes a look at at telecommuting, going green, Web 2.0, data management, and more.  Be sure to read her post.

ComputerWorld: Seven steps to take now for a better job in '08

Bryan's picture
Submitted by Bryan on
ComputerWorld has an article geared for IT professionals desiring another job.
Seven steps to take now for a better job in '08 - It's not the kind of thing you can cram for. If you want a better job in '08, now is the time to hone your skills, strengthen your social networks and boost your visibility in the office.
I'm personally happy with my own job and don't really plan to move anywhere.  The fact is the grass usually does appear greener on the other side then it actually is.  Though, I can  still dream.  No more IT security reports.  Lots more money.  Flexible shift hours.  A position as a CEO knowing just as much about IT as the CIO.   An organization that understands the the true value of IT in strategic planning.

Ugh...now I'm so unhappy.  Stupid IT dream...

ComputerWorld: Respect and Beyond Process Design

Bryan's picture
Submitted by Bryan on
There are a couple new articles at ComputerWorld that peaked my interest and may be something you too will be interested in reading.  The first is an opinion piece by Frank Hayes, "Frankly Speaking: Rewiring Respect for IT".
Why don’t IT people get more respect? On this Labor Day, things are actually looking better for people who work in corporate IT. Budgets aren’t quite so tight. Companies are hiring. Interesting IT projects are getting a green light. But when it comes to how our fellow employees think about us, IT work is a train wreck. Users break the rules we set up, ignore the proc­esses we develop and generally act as if we’re clueless in what we do.
On a different subject, Bruce A. Steward has written an article to remind us that supporting our customers is more than just improving the business process.

CIO Insight: IT Security, Reconsidered

Bryan's picture
Submitted by Bryan on
An excellent article at CIO Insight in their "Expert Voices" column concerning IT security.  The article is titled, "IT Security, Reconsidered":
Business people know risk and return are opposite sides of the same coin; you can't have return without risk. So successful companies learn to analyze, accept and manage risk…most kinds of risk, anyway. When it comes to IT risk, organizations tend to focus on avoiding risk instead of managing it, by preventing intrusions and preparing to respond to catastrophic events. But instead of protecting companies, this approach to risk has blindsided IT to a long stream of IT disasters, from system meltdowns (Comair, Jet Blue) and stolen credit card data (TJX, CardSystems Solutions) to pilfered laptops (Veterans' Administration) and stolen data (U.S. Department of Transportation). Putting IT security back in the context of risk management has been the focus of George Westerman's work.
This year at work I have spent close to half my time dealing with a lot of IT security.  I have not only been kept busy with locking down the network but  also with way too much paperwork certifying that our machines are secure.  When you spend so much time making the paper pushers happy that you're following the latest policies it hard to actually really identify the true risks that don't show up on paper.  More importantly, spending so much time on IT security not only locks out the would-be hackers but also locks your IT staff out from adding potential IT value to the operations.  There has to be a balance somewhere...

Getting more work done through less innovation

Bryan's picture
Submitted by Bryan on
The biggest reward I get from working on IT projects is the opportunity to take new ideas and new strategies and piece them together into something that has never been done before.  Even when I'm not the one originating the new idea, I like helping other innovative people bring their ideas to the table.  I have ideas, dreams, and aspirations to help take my workplace to the next level of where it should be via innovative use of what I know best, information technology.  How could innovation and all these wonderful ideas I have in my head not be anything but a good thing for my organization?  A recent article in the Wall Street Journal answers just that question by saying that there are negatives for an organization that innovates too much.

In "How Innovation Can Be Too Much of a Good Thing", George Anders writes about how companies and business consultants are rediscovering that less innovation can produce better business results.  Companies that used to push the limit in efficiency are finding that they're "jamming too many new ideas into a product pipeline, without enough slack time to ensure that critical tasks stayed on schedule".

Similar insights have been standard wisdom on the manufacturing floor for decades. Factory managers learn about bottlenecks through the formal discipline of queuing theory. That teaches them to keep a little slack in the system to handle the unpredictable -- but inevitable -- crunch times.

Collaboration Loop: Collaboration, where have you been all my life?

Bryan's picture
Submitted by Bryan on

"After all, why is collaboration any more important now than it’s ever been? One argument is that now more than ever, businesses are all about their people. (Yeah, OK, that’s an inelegant twist on Microsoft’s “People-Ready Business” slogan.) But that’s not true—successful businesses have always leveraged the skills of their employees, and the so-called knowledge economy has been around seemingly forever, or at least several decades. So what’s new here?"

Complete Story

Identifying Open Source Winners and Losers

Bryan's picture
Submitted by Bryan on
Very interesting article from InformationWeek, How to Tell the Open Source Winners from the Losers.
There are 139,834 open source projects under way on SourceForge, the popular open source hosting site. Five years from now, only a handful of those projects will be remembered for making lasting contributions--most will remain in niches, unnoticed by the rest of the world. For every Linux, Apache, or MySQL, dozens of other open source efforts fizzle out.

That's a dilemma for the many companies that are expanding their use of open source. Corporate developers and other IT professionals must get better at divining the winners and ignoring the losers. The wrong picks can lead companies down a rat hole of support problems and obsolete software.
Not sure if I agree with everything in the article.  For example, the 9-point checklist  of what is required for a successful open source project is surely up for debate.  However, the article is a very good starting point for companies and their IT managers to identify the more successful projects.   According to the article, some of the up-and-comers in open source include Alfresco (CMS), Subversion (version control), and Hyperic (system management).

It's funny though, I remember visiting SourceForge quite a bit years ago.  These days though, I seem to find the project directory through "word of mouth" via the blogs.  Amazing how blogging continues to change the IT landscape.

CIO Insight: How to Manage Application Enhancements

Bryan's picture
Submitted by Bryan on

"One of the endless challenges for a large corporate software engineering organization is to develop an effective process for handling the steady stream of small changes, fixes and enhancements that seem to accumulate around installed software, both custom developed and Commercial of the Shelf (COTS)—no matter how good it is initially. Typically, these changes can be handled by a single engineer, don't require much resource or elapsed time and are generally pretty well defined. Users know that they are not asking for much, and don't, therefore, expect to have to wait very long to get their change request implemented."

Complete Story

Pages