GSX Blog

Last week I gave an overall introduction to ITIL for Messaging and Collaboration environments. This week I will start going a little further into detail on the individual “Volumes” of the IT Infrastructure Library and how they relate to our environments. This is the second part of our series, in which I will cover Service Strategy. Each week we can expect a new article on each of the five primary components of ITIL Service Management. This will end up being a seven part series which I will make available at the end of the series as a downloadable white paper.

A few weeks back Eileen posted an article that highlights the importance of having metrics regarding the performance and availability of your messaging and collaboration environment. I’d like to expand on her article and discuss first what ITIL means to messaging and collaboration environments, then an overview of what monitoring and reporting can do for your ITIL implementation and finally how GSX Solutions can provide relief in these areas. 

More than often, we get asked questions about collaboration strategies, choices of technologies and best practices. This could feel unusual as our business is platform-agnostic and we are modest providers of complementary technology more than experts on end-users projects.

Database Availability Groups are the key component for Microsoft Exchange 2010 High Availability. As such it is critical to ensure their overall health and availability. High availability can give a false sense of security, in order to ensure an IT service is highly available the overall solution must include monitoring.

We are all preparing for Lotusphere 2012 next week in Orlando. While I am assuming that we have spoken on our projects with all of you, there is one thing I want to stress: there will be a very small amount of brochures on our booth.

The GSX Team is pleased to announce the availability of the new version of GSX Monitor & Analyzer. The new V10.1 is even more powerful, allowing managers and decision makers to:

This is the third part of a four part series that addresses database management in an Exchange 2010 environment.  It is meant to provide a good overall introduction into the maintenance and monitoring needed to ensure the health of your Exchange 2010 databases.

Last week we looked at Exchange 2010 new features and best practices, this week we’re going to look at ongoing management activities and important database statistics.

I completed my final ITIL exam today, and one of the questions was about verifying the cost of specific IT services to the business, and it reminded me of these statements:

The release of Exchange 2010 brought about some differences in the ways we need to look at database management. Gone are LCR, CCR and SCR replaced by Database Availability Groups. Exchange 2010 also introduces new user functionality and enhanced integration with other Microsoft messaging and collaboration platforms. This article will highlight the things that an administrator needs to take into consideration from a database perspective, divided into four separate posts: