Skip to main content

Exoprise CloudReady Monitor for Office 365

Basic value proposition - supplements Office 365 dashboard capabilities by providing near real-time performance and point-of-access monitoring (includes alerting capabilities via email or SMS when custom defined thresholds are exceeded).

Office 365 Health Dashboard:

Exoprise Sensor Dashboard (sample):
Crowdsourcing feature is pretty interesting - Exoprise service collects (anonymously) performance data across the entire community of users (all sensors that report back to the system), trends, and lets you compare your stats against calculated crowd averages. This may highlight performance problems that are common across the entire O365 Service or something that is not O365 related at all (e.g. local ISP issue). Seems like a very useful feature.

The way performance data is collected - small (<12MB) agent in installed on a workstation (or server, or VM) at the customer's site. The agent performs synthetic transactions (like sending and receiving email, etc.) and measures response times, etc. Thus the agent will need to be configured with a valid O365 account/license (not a big deal, but potentially a small additional expense for the customer) + need to make sure the account's password is set to not expire and least privilege is configured (to avoid any inadvertent information leaks, though the agent itself is only supposed to collect performance data).

The way the service is priced is by sensor, currently the following sensors are available or planned:
  • Exchange Online
  • AD
  • ADFS
  • Azure (beta)
  • SharePoint Online (planned)
The sensor monitors one service (from the list above) at one location (agent installed). For example, if customer has 2 locations (1 main, 1 satellite) and wants to monitor Exchange Online from both, but AD and ADFS only from the main one - 4 sensors would need to be licensed.

For more information visit http://www.exoprise.com/

Comments

Popular posts from this blog

Skype for Business and VTC Interoperability

Skype for Business (SfB) has a very, very strong potential, I have written about it in my previous post. I can't think of any other platform that shows as much promise in terms of bridging personal and business communications as well as unifying different modes and mediums. And all of this may have started with a strategic acquisition of Skype by Microsoft in 2011.

That said, the road ahead is not without challenges. For example, interoperability with other platforms. Making SfB work with existing Video TeleConferencing (VTC) systems, many of which represent significant capital investments in organizations' infrastructure, could be of a particular importance.

After reading statements like Skype for Business is based on Session Initiation Protocol (SIP) standards and supports H.264 (MPEG-4 video coding standard) one can come to a quick conclusion that integration and/or interoperability with other VTC solutions is easy or nearly automatic. Unfortunately, the industry is not qui…

PoSh Disable and Move AD Users

A quick and easy way to disable user accounts and move them into designated OU:

Import-Csv "C:\TEMP\users.csv" | ForEach-Object { `      $u=$_."sAMAccountName"; $l="Disabling and moving: " +$u; write-output $l; `      Get-ADUser -Identity $u | `      Disable-ADAccount -PassThru | `      Move-ADObject -TargetPath "OU=Disabled Users,OU=Organization,DC=domain,DC=local"
Input is provided via a CSV file:
users.csv (username) sAMAccountName  jdoe1  jdoe2  jdoe3  jdoe4  jdoe5  

To generate input file run something like this, review and edit as necessary:
Search-ADAccount –UsersOnly –AccountInactive –TimeSpan 180.00:00:00 | `      where {$_.enabled} | `      Get-ADUser | `      select sAMAccountName | `      Export-Csv -Path "C:\TEMP\users.csv"

WordPress displays weird characters

Sometimes after a database conversion (e.g. from MySQL to MariaDB) or due to encoding issues a situation might arise when WordPress is showing weird characters. A quick way of remedying the situation would involve examining the pages to discover a pattern (what characters are being substituted, in the example below the apostrophe was replaced by â€™) then running an queries against the database to reverse the effect. Here's a quick example (common tables that store content):



UPDATE wp_posts SET post_content = REPLACE(post_content, 'Â', '')     UPDATE wp_posts SET post_content = REPLACE(post_content, '’', "'")     UPDATE wp_postmeta SET meta_value = REPLACE(meta_value, 'Â', '')     UPDATE wp_postmeta SET meta_value = REPLACE(meta_value, '’', "'")     
Please, keep in mind that to permanently resolve the issue you would need to get to the root of the problem and may need to adjust encoding, run a databas…