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

Mail-enabled security groups in Office 365

Another update (11/19/2013): further evolution of Office 365 services makes creation of distribution and security groups even easier, plus there's now an option of creating a dynamic distribution group (click here for more information): Update (08/06/2012): a clear sign of Office 365 evolving along the same lines as other agile cloud services - small incremental features and minor new functionality are being delivered almost continuously and, unlike important major service updates, without much fanfare. For example, there's no need to resort to using PowerShell to setup mail-enabled security groups anymore, it can now be done at creation using management portal: Those managing Office 365 ( O365 ) tenant via the Microsoft Online Services Portal ( MOS Portal ) interface would notice that there are two distinct group entities: Security Groups: can be created via MOS Portal (main portal page>Management>Security Groups) and used for assigning

Drumbeat - Sales and Technical Resources for Office 365

Drumbeat - provides information as well as technical and sales resources for Office 365. From partnering with Microsoft, to building up your sales and technical readiness, to adopting proven methodologies for successful deployment - you will find lots of good information and many helpful links there. Here's a quick sample of topics covered: The Customer Decision Framework is Microsoft's selling methodology designed to help partners sell Office 365 to their customers. Office 365 FastTrack is Microsoft's new, 3-step pilot and deployment methodology designed so customers experience service value early in the sales cycle with a smooth path to advance from a pilot to deployment.

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 p

Technocrat

Search This Blog