{"id":1898,"date":"2018-07-10T12:48:00","date_gmt":"2018-07-10T16:48:00","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/?p=1898"},"modified":"2018-07-10T12:50:09","modified_gmt":"2018-07-10T16:50:09","slug":"announcing-new-network-operations-center-noc-look","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2018\/07\/announcing-new-network-operations-center-noc-look\/","title":{"rendered":"Announcing New Network Operations Center (NOC) Look"},"content":{"rendered":"<p>ExchangeDefender is proud to announce the new look for our Network Operations Center (NOC) which includes new status pages, new blog, new look and yes \u2013 even more information you can pass on to your clients. The idea behind the redesign was to give end users and our non-IT partners a way to get an <a href=\"http:\/\/www.exchangedefender.com\/noc.php\">assessment of the network at a glance<\/a>, a <a href=\"http:\/\/www.exchangedefender.com\/noc\/\">deep dive into technical issues<\/a>, and to provide recent and historical service issues so that IT personnel in charge of our services can match up service problems with times that we had an issue or maintenance window.<\/p>\n<h3><strong>\u00a0 \u00a0Is there a problem?<\/strong><\/h3>\n<p>This is generally the first question that a user will ask when they contact our partners for a service issue. And unless you <a href=\"http:\/\/www.twitter.com\/xdnoc\">follow us on Twitter @xdnoc<\/a>, you probably need to check our NOC page. Here is the new look:<\/p>\n<p><a href=\"http:\/\/www.exchangedefender.com\/blog\/wp-content\/uploads\/2018\/07\/image2.png\"><img loading=\"lazy\" decoding=\"async\" style=\"display: inline; background-image: none;\" title=\"image2\" src=\"http:\/\/www.exchangedefender.com\/blog\/wp-content\/uploads\/2018\/07\/image2_thumb.png\" alt=\"image2\" width=\"504\" height=\"210\" border=\"0\" \/><\/a><\/p>\n<p>Our users will be able to look at the <a href=\"http:\/\/www.exchangedefender.com\/noc.php\">NOC page<\/a> and immediately see the issue and take the next step.<\/p>\n<h3><strong>\u00a0 \u00a0What is the problem?<\/strong><\/h3>\n<p>By the time there is an issue or the maintenance window is concluded, service notices are closed and aren\u2019t visible to partners anymore. We had a lot of reasons for this but needless to say that it\u2019s been one of the top complaints from our partners for years and it took us a while to figure out how to do this discretely and in a way that would be beneficial for everyone. Since support folks tend to either follow us on <a href=\"http:\/\/www.twitter.com\/xdnoc\">twitter (@xdnoc)<\/a> or are living in our portal at <a href=\"https:\/\/support.ownwebnow.com\">support.ownwebnow.com<\/a>, we wanted to put it in a location that would make it most actionable. You will notice quite a few changes to our support portal:<\/p>\n<p><a href=\"http:\/\/www.exchangedefender.com\/blog\/wp-content\/uploads\/2018\/07\/image-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" style=\"display: inline; background-image: none;\" title=\"image (1)\" src=\"http:\/\/www.exchangedefender.com\/blog\/wp-content\/uploads\/2018\/07\/image-1_thumb.png\" alt=\"image (1)\" width=\"534\" height=\"428\" border=\"0\" \/><\/a><\/p>\n<p>Now this screen will continue to change \u2013 but the idea is the same \u2013 if you resell or manage our products, I want you to know immediately upon logging in what the issue was and how it was resolved. You can then match up the timeline and work from there but you will get all the information in one, secure, compliant and process driven environment.<\/p>\n<p>The point is \u2013 if you\u2019re a lurker or just wondering, I want you to see if there is an issue at all. If you work with us, I want to arm you with all the information you can ever need and I want a support tech on my side to be available to you immediately to advise what to do.<\/p>\n<p>Afterwards, you can read about the details on the NOC blog at <a href=\"http:\/\/www.exchangedefender.com\/noc\">www.exchangedefender.com\/noc<\/a> where we write up longer technical articles that nobody will ever read, but our partners find them extremely valuable because they aren\u2019t written in technical jargon \u2013 they are meant to explain to your clients what happened, what we did, and what we\u2019ll do next to make sure that issue doesn\u2019t repeat.<\/p>\n","protected":false},"excerpt":{"rendered":"<p> [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1898","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/1898","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=1898"}],"version-history":[{"count":4,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/1898\/revisions"}],"predecessor-version":[{"id":1903,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/1898\/revisions\/1903"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=1898"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=1898"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=1898"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}