Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/41/d94896425/htdocs/blog/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/41/d94896425/htdocs/blog/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/41/d94896425/htdocs/blog/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/41/d94896425/htdocs/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/41/d94896425/htdocs/blog/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/41/d94896425/htdocs/blog/wp-includes/http.php on line 61

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-content/plugins/wp-db-backup/wp-db-backup.php on line 106

Strict Standards: Non-static method K2::init() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-content/themes/K2/functions.php on line 31

Strict Standards: Non-static method K2::include_all() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-content/themes/K2/app/classes/k2.php on line 20

Strict Standards: Non-static method K2::include_all() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-content/themes/K2/app/classes/k2.php on line 21

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Options::init() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::init() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2::register_scripts() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-content/themes/K2/header.php on line 6
SharePoint Roundup - Sentri Panel at Boston KM Forum
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::output_header_css() should not be called statically in /homepages/41/d94896425/htdocs/blog/wp-includes/plugin.php on line 339


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/41/d94896425/htdocs/blog/wp-includes/functions.php on line 55


SharePoint Roundup - Sentri Panel

Thursday, July 19, 2012, 4:00 - 6:00 p.m., Microsoft, 201 Jones Rd., Sixth Floor, Waltham, MA 02451. Directions.

SPEAKER: Mike Gilronan, Senior VP Business Development, Sentri; Evan Riser, SharePoint Consultant at Sentri.

TOPIC: Sentri is an IT consulting and managed services Microsoft Gold Certified partner providing Business Technologies and Services to organizations in the areas of IT Infrastructure, Unified Communications, Collaboration, Contact Center, Dynamics CRM, SharePoint and Cloud Services. We will interview Mike and his colleague to learn the latest SharePoint developments, what will be coming in future releases, and how other applications and services contribute to implementation successes.

GUEST BIOGRAPHIES: Mike Gilronan was recently named Senior Vice-President of Business Development at Sentri, a Microsoft solutions partner. Mike has spent his whole career in professional services and technology, has worked in the Microsoft consulting community since 1999, previously focusing on  SharePoint solutions at KMA beginning in 2006. Mike’s financial background (“recovering” CPA) and active project manager certification (PMP) make him a bit of a “process geek,” focused on themes like measurement and ROI with key strengths in aligning business challenges with technologies. In addition to being active in Boston-area KM and SharePoint communities, Mike is a Microsoft Virtual Technology Solutions Professional, a member of the Project Management Institute Mass Bay Chapter, and a member of the Society for Information Management Boston Chapter.  Mike also has nearly a decade of experience as Board member and Treasurer for a variety of not-for-profit organizations.

Evan Riser is a SharePoint Architect for the SharePoint Practice at Sentri. Evan designs, architects and implements SharePoint solutions based on customer business needs utilizing proven best practices, delivering cost effective comprehensive solutions that bring lower TCO and higher efficiency. Evan develops implementation methodologies for complete comprehensive solutions for emerging technologies. Evan has over 6 years of experience working with SharePoint as an administrator, pre-sales engineer and architect. His SharePoint experience covers Windows SharePoint Services 2.0, Microsoft Office SharePoint Server 2007 and SharePoint Server 2010.

PLEASE PLEASE Register even if you are not certain you can attend so we have an accurate estimate of attendees for handouts. If you then make a decision not to attend, please use the registration link and note in the comments field that you will not attend.

NOTE: The registration page has changed and you will be directed to another site where the registration form resides. It is now hosted by lwmtechnology.com and is legitimate.

Registration Form for Thursday

Registration Comments (Cost, time, meeting format)

0 Responses to “SharePoint Roundup - Sentri Panel”


  1. No Comments

Leave a Reply