過去的上市、上櫃公司，常常將投資人關係管理(IR：Investor Relation)視為公共關係(PR：Public Relation)的一部分，近年來，為因應投資人、尤其是投資機構對上市櫃公司營運狀況、財務報表等資訊取得的急迫性，因此，該項需求活動之頻率與負荷，已經遠遠高過原有所謂公共關係的活動程度，因此，各大上市櫃公司，陸續將投資人關係部門，獨立為專職部門，以因應此類活動之需求，以凸顯其重要性。

而投資人關係管理的好壞，將是牽動公司的投資條件的健康指標：

一、      投資人關係部門，具有反應公司之管理狀態，進而影響企業競爭力的評等。

二、      投資人關係部門，具有反應公司經營績效的任務，進而影響投資者之意願。

三、      投資人關係部門，應長期維繫與投資人之間的活動，忠實的反應與傳達投資者之權益，具有企業與資本市場間對話之任務，進而成為企業經營之策性組織之一。

基於IR部門對公司的重要性，可以歸納如下：

一、      依循公司的發展策略、經營狀況，即時、準確、完整、合於法規的披露應有之投資資訊。

二、      紀錄與企業相關之報導，維護投資者之持股與投資意願之動態。

三、      與機構投資者、證券分析師及中小投資者保持聯繫，安排與接待投資者的參訪，提高市場對公司的關注度。

四、      維繫與財經媒體的關係，適時安排企業主管接受採訪。

五、      定期或在出現重大事件時組織分析師會議、Road show等活動，與投資者進行溝通。

六、      在公司網站中設立IRM專欄，在網上披露公司資訊，方便投資者查尋和諮詢。

七、      與監管部門、公會、交易所等保持接觸，建立良好的溝通關係。

應如何善用IT技術，協助IR部門人員管理與維護以上之工作，並能做到主動安排、跟催任務執行之功能呢？ Microsoft Dynamics CRM所具備的系統彈性與物件關聯功能，為解決此一問題，提供了最佳的解答。Dynamics CRM合作夥伴，晉泰科技的CRM專業顧問團隊，以Microsoft Dynamics CRM為基礎，推出了專業的Genesis IRM^TM產品模組，並已實際的應用於上市櫃公司，本產品主要設計功能，即是針對上述IR七大項工作，其優勢歸納如下：

一、提供投資關係人基本資料維護工具，並記錄各股戶與集團之完整關聯資訊。

二、提供資訊分析工具能有效掌握投資人之持股動態、並進而發掘潛在投資者。

三、提供與投資人關係之活動行事曆功能，並與Outlook完全整合。

四、提供每次投資人相關活動之事前資料準備、事後會議記錄與跟催之完整功能。

五、具備IR專業知識庫功能，可以輕鬆地讓IR人員隨時收集、歸納市場與投資人之往來資訊。

ERP使您的企業 “跨” 出成功的第一步

許多台灣企業在選擇ERP時會呈現兩種面向：一種是選擇國外知名大廠解決方案，原因不外乎是品牌名氣大、客戶群眾多以及流程標準化；而另一種面向則是選擇國內本地解決方案，原因則是客製彈性大、流程本地化以及成本考量為首要。然而，根據我們的觀察，台灣企業在考量跨國子公司ERP解決方案時，總經常面臨到“魚與熊掌難以兼得”和“有一好就沒二好”的課題。

隨著台灣企業將觸角延伸至海外時，經常會發現原先母公司所使用的ERP系統並不適合其海外分公司的需求，整體分析下來，可將原因歸納成兩個部分：

1. 1.      母公司大型ERP經常不符合海外分公司彈性作業需求

一般來說，海外分公司的規模往往不如母公司內部組織完整，而且更著重在業務行銷等營運部門，也不需要如母公司般有複雜的營運流程，若使用與母公司同一套ERP，常常會產生系統修改過於耗時費工，不然就是系統使用所需資源配置門檻過高，產生不必要的成本和增加營運上的負擔。

1. 2.      台灣當地ERP無法符合海外當地需求

台灣當地ERP在遇到企業跨國使用時，常會遇到與當地語言、交易幣別、稅法和相關系統法令上不符而產生無法支援的窘況。就算勉強使用，也會遇到系統離開台灣後，在需要維運時變成求助無援的孤兒。

因此，我們會建議，台灣企業主在作全球跨國性布局時，務必先與公司內部團隊共同思考幾個重要的問題：

1. 1.     現階段母公司使用的ERP是否適合海外分公司規模？

一般來說，如果考量沿用母公司ERP系統建置海外分公司系統時，需要審慎評估母公司所使用的ERP是否具有符合跨國應用、高度系統彈性以及能否獲得當地顧問支援服務等條件以因應海外營運的變化。因為這與未來系統使用接受度和系統維護成本等問題息息相關。

1. 2.     導入人員編制準備好了沒？

一般來說，海外分公司在部門分工上較母公司為精簡，經常只設立業務和財會部門。這時候，公司務必要思考，導入系統的參與人員是否已經準備好。我們會建議企業主，導入ERP的參與人員務必對公司營運流程有一定程度的了解，也千萬不要選擇讓剛加入公司的新人主導ERP導入專案。因為往往系統導入的成敗關鍵多是人為因素，而非系統本身。

1. 3.     對於新的ERP系統目標設定，公司內部是否達成共識？

我們在協助企業主導入ERP時，經常會遇到一種狀況，那就是企業主希望能夠在短時間內改善現有ERP所有做不到的事，並且還能增加許多新功能。然而當ERP專案導入範圍越大，投入所需時間、人力及預算就需要更龐大，甚至對ERP使用者來說，進入門檻過高，反而需要更多時間熟悉新的作業環境，因此徒增系統導入時的風險。

所以我們建議，公司內部對於新的ERP系統期望務必達成共識；若企業主尋求非常完整的系統導入，我們更建議能夠以階段性任務達成的方式作專案導入，好讓使用者能夠循序漸進熟悉新系統，專注於營運作業上真正所需，減少系統轉換時的衝突，或是使用初期所帶來的不適應。

Microsoft Dynamics NAV 是擁有完整的功能模組以及高度作業彈性的系統，服務的客戶規模可以從員工人數5人到500人；而其彈性的參數及系統物件設計，更能符合各種企業經營的特殊邏輯。更重要的是，Microsoft Dynamics NAV 的多公司、多幣別和多國語系支援架構，能真正符合企業跨足海外事業部的需求，讓母公司可針對不同市場子公司架構作系統規劃。而微軟全球擁有上千家ERP服務合作夥伴，能夠以最快速度提供企業主在世界各地的營運據點最即時及優質的服務。我們相信，正確的ERP全球佈局策略，絕對能幫助企業在跨足海外市場的過程中站穩成功的第一步，更是企業在全球佈局上的關鍵決勝點。

您的企業經過最近的經濟不景氣，如何贏回客戶的信賴? 是否還是透過品牌、服務，還是透過關心客戶的意見、來感動客戶人心，甚至在行銷3.0的時代，透過企業社會責任的落實，來讓客戶對您的行銷訴求有更深的感動?

行銷3.0的時代中，客戶接受到企業的行銷訴求的同時，企業傳達的訊息與準備提供給客戶的服務上，客戶很快就可判斷這是否就是他想要的服務，以及是否可以解決他的問題。行銷3.0的時代中，在企業傳達訊息與提供服務給客戶的同時，客戶就期待開始積極與企業，進行一段”價值共創的過程”，也就是企業與客戶的客戶關係管理的工作就已經展開。

在行銷3.0思維中，每個人都是行銷人！不管是第一線服務人員，還是企業決策者，不論客戶獲得有關於服務、產品與企業價值等的訊息的同時，客戶就開始進行”價值共創”。當企業的每個人把”生活態度”與”企業價值”傳達給客戶的同時，客戶更在乎企業的訊息與服務是否協助客戶共同創造了價值，作到如此才能夠打動顧客的情緒，也決定客戶在下一刻，要否願意繼續與你共舞。

(摘錄自：Marketing 3.0: From Products to Customers to the Human Spirit，作者：Philip Kotler (菲利浦．科特勒)等人)

在行銷3.0裡面，消費者是團結在一起的社群，不再像過去只是被動接受行銷，社群的消費者會主動出擊，互相分享討論。微軟Dynamics CRM 2011，在行銷3.0時代，讓企業對於經營管理、行銷、服務科學化設計具有更好的連結。微軟Dynamics CRM2011讓行銷人在思考服務設計過程中，更能夠透過與消費者社群持續溝通，在觀察社群的想法過程中，挖掘客戶需求與持續與客戶溝通，來持續設計服務、設計出行銷策略。Dynamics CRM2011也協助業務人員、客戶服務人員、公司管理者，將所有接觸到客戶的員工都視為傳遞企業價值的大使，持續傳遞企業價值給客戶，並且紀錄與客戶之間各種接觸互動的軌跡，並確實落實在每一個實踐的細節當中。在行銷 3.0時代，Dynamics CRM2011協助企業快速打動顧客的情緒。

SharePoint サポートチームの江口です。今回は、SharePoint Online/SharePoint Server 2013 (オンプレミス) で、ワークフローで HTTP Web サービスを利用する方法についてご案内します。

はじめに

SharePoint Designer 2013 では、SharePoint 2013 プラットフォーム ワークフローを作成することができます。

SharePoint 2013 プラットフォーム ワークフローには、新しく追加された"HTTP Web サービスを呼び出す" アクションを使用することができます。

このアクションを使用することで、例えば SharePoint REST サービスのような HTTP Web サービスをワークフロー内で利用できます。

以下の手順では、例として同じ SharePoint サイト内のリストに含まれたリスト アイテムの数を取得する方法について手順を記載します。

- 目次

手順 1) SPD ワークフローの作成

手順 2) "辞書を作成 アクション" の追加

手順 3) "アクション : HTTP Web サービスを呼び出す" の追加

手順 4) "アクション : 辞書からアイテムを取得する" の追加

手順 1) SPD ワークフローの作成

1-1) SharePoint Designer 2013 を起動し、SharePoint サイトを開きます。

1-2) [リスト ワークフロー] - [<<任意のリスト>>] を選択します。

1-3) [リスト ワークフローの作成] ダイアログで以下のように設定し [OK]をクリックします。

  名前: 任意

  説明: 任意

  プラットフォームの種類: SharePoint 2013 ワークフロー

2) "辞書を作成 アクション" の追加

2-1) [アクション] - [辞書を作成] をクリックします。

  追加される文字列: "この" 辞書を作成する ("変数: 辞書"へ出力)

2-2) "この" をクリックし、"辞書の構築" ダイアログで以下の項目を追加します。

  名前 : Accept

  種類 : 文字列

  値   : application/json;odata=verbose

2-3) "変数: 辞書" をクリックし、任意の変数 (以下、RequestHeaders1 (種類:辞書)) を指定します。

手順 3) "アクション : HTTP Web サービスを呼び出す" の追加

3-1) [アクション] - [HTTP Web サービスを呼び出す] を追加します。

  追加される文字列: 次に"要求" で"この" HTTP Web サービスを呼び出す (ResponseContent は"応答" | ResponseHeaders は"応答ヘッダー" | ResponseStatusCode は"変数: 応答コード")

3-2) 追加される文字列にカーソルを合わせ、[下矢印] - [プロパティ] をクリックします。

3-3) "HTTP Web サービスを呼び出す プロパティ" ダイアログで、[RequestHeaders] に、上記手順 2-3) で指定した RequestHeaders1 を指定し [OK] をクリックします。

3-4) 追加される文字列の"この" をクリックし、"HTTP Web サービスを呼び出す" ダイアログで、以下の項目を入力します。

  HTTP Web サービスの URL を入力 : http://server/sites/site/_api/lists/getbytitle('<<リスト名>>')/ItemCount

    例 ) http://server/sites/site/_api/lists/getbytitle('ListName')/ItemCount

  HTTP メソッドの指定 : HTTP GET

3-5) "応答" をクリックし、任意の変数 (以下、ResponseContent1 (種類:辞書)) を指定します。

手順 4) "アクション : 辞書からアイテムを取得する" の追加

4-1) [アクション ] - [辞書からアイテムを取得する] を追加します。

  追加される文字列:次に"辞書" から"名前またはパスに基づいて取得したアイテム" を取得する ("アイテム" に出力)

4-2) "辞書" をクリックし、上記手順 3-5) で指定した ResponseContent1 を指定します。

4-3) "名前またはパスに基づいて取得したアイテム" をクリックし、"d/ItemCount" と入力します。

4-4) "アイテム" をクリックし、任意の変数 (以下、ItemCount1 (種類:整数)) を指定します。

上記手順で、変数 ItemCount1 に ListName のリストアイテム数が格納されます。

補足: 手順 4-3) について

上記手順で設定した"HTTP Web サービスを呼び出す" アクションの ResponseContent1 には、JSON 形式のデータが返されます。

http://server/sites/site/_api/lists/getbytitle('<<リスト名>>')/ItemCountのような HTTP 要求をした場合、以下のような形式で応答を返します。

そのため、手順 4-3) のように、JSON 形式のパスに基づき "d/ItemCount"とパスを指定して辞書からアイテムを取得します。

なお、SharePoint REST サービスでは、Accept ヘッダーに"application/json;odata=verbose" を設定することで JSON 形式で結果を取得できます。(上記手順 2) 3) で設定)

設定しない場合は以下のような Atom 形式で結果が返されます。

参考情報

SharePoint の REST サービスに関しては、以下の技術情報を合わせて参照してください。

SharePoint 2013 REST サービスの概要

[方法] SharePoint 2013 REST エンドポイントを使用して基本的な操作を完了する

"HTTP Web サービスを呼び出す" アクションについては、以下の技術情報を合わせて参照してください。

ワークフロー アクション クイック リファレンス (SharePoint 2013 ワークフロー プラットフォーム)

SharePoint Designer 2013 の辞書アクションを理解する

既知の不具合として、SharePoint ワークフローから SharePoint HTTP (REST) Web サービス以外のサービスを呼び出すと、HTTP Web サービスの呼び出しが失敗する場合があることが報告されています。

問題の詳細と回避策については以下の公開情報を参照してください。

SharePoint Server 2013 の既知の問題

企業決定導入或更新ERP系統時, 總會遇到一個難題是如何選擇適用的ERP系統, 面對各顧問公司的推薦, 各家都說自己有什麼特異功能, 或是聽起來什麼問題都有最完美的解決方案. 但是, 選擇ERP系統並不是找顧問口中最完美的解決方案, 而是尋找最能夠與公司獲利完美搭配在一起的完整解決方案, 本文將告訴您, 為什麼Microsoft Dynamics ERP是能夠與公司獲利完美整合的最佳解決方案?

Microsoft Dynamics ERP的高度彈性化的系統架構, 不僅提供企業現在到未來的發展所需, 更可以和企業現有的資訊系統整合, 讓企業保有資訊系統的投資, 並且讓企業在面臨瞬息萬變的市場時, 能夠配合企業未來的變革, 迅速調整系統功能, 以因應新的契機.

兩層式ERP (Two Tier ERP)系統架構, 提供第一層完整的企業總部ERP系統解決方案, 並讓企業總部可以靈活的選擇第二層ERP系統做為子公司或獨立事業部門的ERP系統, 因為子公司或獨立事業部門的系統需求和企業總部不完全一致, 把符合企業總部使用的ERP系統導入應用, 成本不但高昂, 而且不一定適合子公司或獨立事業部門的需求.

因此, 對擁有子孫代事業體的企業總部, 需要的是一方面能夠符合子孫代事業需求的第二層ERP系統, 而且要能夠和企業總部的第一層ERP系統完全整合, 如此一來, 各項營運報表及財務報表, 都能迅速匯總各子公司或獨立事業部門的ERP系統中的資訊, 即時呈現企業整體營運指標.

兩層式ERP架構還有更多需要考慮的因素:

1. 多國語系、貨幣的資料整合, 子公司或獨立事業體可能位在世界各地不同地域或國家, 不同的語言與貨幣資料, 讓企業總部在匯集不同語系或貨幣的資料時, 正臨嚴重的資料整合問題. 而Microsoft Dynamics ERP, 因為已經考慮兩層式ERP系統的需求, 可以將第二層ERP系統中的資料, 自動與第一層ERP系統整合在一起, 以第一層ERP系統的語系及貨幣單位表現在總部各式報表中.
2. 本地端的不同稅務、法規應用, 各個國家在稅務與勞動等法規規定不同, 對第二層ERP系統而言, 這代表需要配合不同國家的法規規定製作符合該國國情的財務與營運報表. Microsoft Dynamics ERP已有符合全世界各主要國家法規規定本地化模組功能, 這些本地化模組都能考慮兩層式ERP系統的需要, 提供完善的系統整合能力, 讓企業總部能自動匯總世界各地子公司或獨立事業部門的資料, 完成集團財務與營運報表.
3. 子孫代事業體各有各的特色, 第二層ERP系統必需有靈活而彈性的系統架構, 因應各種不同行業的需求, 而快速客製能力, 能夠將第二層ERP系統在最短時間內將系統調適為子公司或獨立事業部門所需的ERP系統.

整體而言，透過兩層式ERP的導入策略設計，透過上述幾項優點的累積，對企業而言，最終便是能降低整體擁有成本(TCO)，這更是在現今詭譎多變的市場競爭環境下，最有利的投資與最長遠有效的布局。

Microsoft Dynamics ERP，是中小企業邁向全球布局與因應企業快速成長的最佳選擇。

Microsoft Dynamics ERP對中小企業導入ERP系統更是最佳選擇, 其特色反映在下面幾點優勢之上:

1. 期初建置成本, 中小企業的資金要能夠靈活調度, Microsoft Dynamics ERP低整體擁有成本的特色, 正是此一問題的最佳解答.
2. 配合未來成長需要, 中小企業很有可能在短時間內迅速成長, ERP系統必需要能配合企業成長所需, 適當調整系統功能與系統容量, 而這, 正是Microsoft Dynamics ERP的專長之一, 搭配Microsoft各種伺服器平台產品, Microsoft Dynamics ERP可伴隨中小企業成長, 不但保有各項資訊系統投資, 更將投資發揮最大經效益.
3. Microsoft Dynamics ERP與其他Microsoft產品無縫隙的整合, 更是Microsoft Dynamics ERP獨有的特色, 例如和Microsoft Office的整合功能, 讓ERP系統資料與前端Excel工作表能夠相當容易的互通, 不用任何程式設計、不用找資訊專業人員, 只要簡單的點選動作, 就能將ERP系統資料傳送到Excel工作表中, 讓工作流程更順暢的運作.
4. 快速客製能力, 在導入ERP系統時, 能夠大幅縮短ERP系統上線時程, 不用再等候冗長的系統功能客製時間, 而且, 更能在需求者印象深刻之際, 開發出需要的功能, 更貼近使用者的需求.

此外，ERP系統導入, 顧問公司往往發揮臨門一腳的重要關鍵, Microsoft嚴選配合顧問公司, 更是各型企業導入ERP系統的不二人選.

綜合以上說明，相對於其他成本過高或是缺乏彈性的ERP系統，Microsoft Dynamics ERP是企業在選擇ERP系統時的一個不一樣的選擇，甚至對台灣的集團企業第二套ERP系統以及大多數的中小企業而言，Microsoft Dynamics ERP更是企業導入ERP系統的最佳選擇。

I ran into an issue where I was replacing a competitor's search service.  I needed to provide validation that SharePoint indexed the same data and used the crawl log to get a list of all the items in SharePoint.  Here's the code:

$ssa=Get-SPEnterpriseSearchServiceApplication

$cl=New-ObjectMicrosoft.Office.Server.Search.Administration.CrawlLog$ssa

$cl.GetCrawledUrls($false,1000000,"",$false,-1,0,-1,[datetime]::minvalue,[datetime]::maxvalue) |export-csv-notypesuccesses.csv  # This will likely be huge

$cl.GetCrawledUrls($false,1000000,"",$false,-1,1,-1,[datetime]::minvalue,[datetime]::maxvalue) |export-csv-notypewarnings.csv

$cl.GetCrawledUrls($false,1000000,"",$false,-1,2,-1,[datetime]::minvalue,[datetime]::maxvalue) |export-csv-notypeerrors.csv

Then just a quick ETL to SQL for SP's index, a full outer join and done.

Hello and welcome!

Today, I want to share the candidates list of the MTPC (Microsoft Technical Persian Contributors) award with you. This is the first time that we are going to announce the winner of this award, so we consider all the articles were published in last two years. For our next awards, we only judge the articles in the last 6 months. The judgement has two separate parts:

• The articles will be judged by Ed and me.
• Persian community can announce their favorite article in the comments section.

Based on the outputs of the two processes, we will announce the award winner.

Here are the articles based on the alphabetical (author name) order:

• Mohammad Ganji
  • http://social.technet.microsoft.com/wiki/contents/articles/13843.split-zone-dns-fa-ir.aspx
• Fatemeh Keshtkar
  • http://social.technet.microsoft.com/wiki/contents/articles/15317.fa-ir.aspx
• Omid Koushki
  • http://social.technet.microsoft.com/wiki/contents/articles/15629.dhcp-server-2003-2008-fa-ir.aspx
• Farid Nasiri
  • http://social.technet.microsoft.com/wiki/contents/articles/22171.audit-collection-services-scom-fa-ir.aspx
• Patris Soltanpour
  • http://social.technet.microsoft.com/wiki/contents/articles/6733.active-directory-attributes-in-the-aduc-gui-tool-fa-ir.aspx
• Erfan Taheri
  • http://social.technet.microsoft.com/wiki/contents/articles/18488.fa-ir.aspx
• Yahya Zahedi
  • http://social.technet.microsoft.com/wiki/contents/articles/18400.hyper-v-fa-ir.aspx

Please join me to congratulate and judge the articles!

For companies that have low account lockout thresholds, adding an AD FS proxy to their DMZ (which is required for Exchange Online) exposes a Denial of Service method.  Many companies have their email addresses set as their UPN and executive emails are well known.  This gives an attacker a method to lock executives out of their accounts at any time and as often as they would like.

In 2012 R2, AD FS adds the ability to soft lockout an account.  The administrator can set a threshold that is lower than the domain's account lockout threshold so that any additional password attempts that go through the proxy are never attempted, keeping the user's account active.  Enabling this feature and setting the threshold is easy through Windows PowerShell

ExtranetLockoutEnabled - enables or disables soft lockout

ExtranetLockoutThreshold - number of bad attempts allowed before soft lockout

ExtranetObservationWindow - lockout time frame

Upgrading to a new version of SharePoint provide tons of value because at Microsoft we have many engineers building new things for each release. The majority of SharePoint deployments are on a version of SharePoint that is nearly 5 years old now. How old is your cell phone, tablet, or laptop?

Here are a few upgrade strategies you can consider so no matter what challenges you are struggling with, you can start getting value from the latest version.

Microsoft has published its security guidance and baselines for Windows 8.1, Windows Server 2012 R2 and Internet Explorer 11.  If you have been reluctant to evaluate or deploy these technologies in the absence of specific USGCB guidance, NIST essentially says, "Use the vendor's guidance."  Here is the vendor's guidance.  Please see these three new blog posts:

Security baselines for Windows 8.1, Windows Server 2012 R2 and Internet Explorer 11 – FINAL– This post includes a zipped download containing documentation, GPO backups, scripts for installing GPOs locally, custom ADMX/ADML for new settings, and WMI filters for use with AD group policy.  Note that corresponding CAB files for the Security Compliance Manager (SCM) will be published before the end of the month.

Configuring Account Lockout– the baseline settings for account lockout changed since the beta (and since previous baselines). This post explains why and the tradeoffs organizations need to consider to determine the right account lockout policy for them.

Changes in the Security Guidance for Windows 8.1, Server 2012 R2 and IE11 since the beta– This post describes the rest of the changes that were made between the beta and the final.

Aquí está una cópia de la presentación de los boletines de seguridad de Microsoft de Agosto de 2014.

Regístrese para el webcast de septiembre:

https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032575643

A copia da apresentação pode ser encontrada neste posting.

O webcast pode se encontrado aqui: https://www.livemeeting.com/cc/_XML/MSEvents/view?id=1032575587&role=view&pw=FE86D5E2

Back - by popular demand!

An old acquaintance, Mr. Rupert Torquil-Smythe Esq., has emailed (several times) to ask that the Mr. Norris wallpaper I found on the interweb be republished.

And, so, here's Chuck in all his resplendent omnipotence:

As a bonus, I've also included my current desktop wallpaper. Two for the price of one!

The PoSh Chap is the chap that just keeps on giving...

One can convert a seven day performance model to a 26 week model without a lot of trouble. I chose 182 days, because it won't impact the Power View reports I created very much. I will change the Perf query to use daily aggregated data instead of hourly aggregated data. As of this writing, the line charts in Power View support 1,000 data points. A line for one week of hourly data equates to 168 data points. A line for 26 weeks of daily data equates to 182 data points. For the chart of statistics with five lines both time periods stay below 1,000 data points.

The seven day model is the one I built then modified in my previous two posts:

http://blogs.technet.com/b/drewfs/archive/2014/08/12/scom-performance-data-and-power-view.aspx

http://blogs.technet.com/b/drewfs/archive/2014/08/14/scom-performance-model-with-configuration-data.aspx

I find long term data provides insights into trends and patterns which may not plainly appear within a week. One might identify behavior tied to a fiscal calendar or seasonal events. Also, the visualizations in Power View may help build a case for capacity changes. Overall, the reports help with data-driven analysis.

I should note that configuration changes become more apparent over time, too. That's why I used to store snapshots of server configuration in an operational database. Sudden changes in performance provoke questions about what happened and why.

Overview

A. Modify SQL Queries in the Performance Data Model

B. Refresh the Data and Review Reports

Step by step

1. Open Perf 7d Model in Excel
2. Save the workbook as Perf 182d Model
3. Select Manage from the Data Model section of the POWERPIVOT menu 

4. Select the Perf dataset tab
5. Select Table Properties from the ribbon in the Design menu 

6. Enter a new query (Perf.vPerfHourlyàPerf.vPerfDaily; 7à182) 

   /*Perf*/

   SELECT     PERF.ManagedEntityRowId

   ,PERF.PerformanceRuleInstanceRowId

   ,PERF.DateTime

   ,PERF.AverageValue

   ,PERF.MinValue

   ,PERF.MaxValue

   ,PERF.SampleCount

   FROM Perf.vPerfDaily PERF

   INNERJOIN vPerformanceRuleInstance PRI ON PRI.PerformanceRuleInstanceRowId = PERF.PerformanceRuleInstanceRowId

   INNERJOIN vPerformanceRule PR ON PR.RuleRowId = PRI.RuleRowId

   WHERE PERF.DateTime>(GETUTCDATE()- 182)

   ORDERBY PERF.DateTime

    

7. Click Save
8. Select the Entity dataset tab
9. Select Table Properties from the ribbon in the Design menu
10. Enter a new query (7à182)

    /*Entity*/

    selectdistinct

    ME.ManagedEntityRowId

    ,MET.ManagedEntityTypeDefaultName as METype

    ,TLMET.ManagedEntityTypeDefaultName as TLMEType

    ,ME.TopLevelHostManagedEntityRowId

    ,ME.ManagementGroupRowId

    ,ME.Name

    ,ME.DisplayName

    ,ME.Path

    ,ME.ManagedEntityTypeRowId

    from Perf.vPerfDaily PERF

    innerjoin vManagedEntity ME on ME.ManagedEntityRowId = PERF.ManagedEntityRowId

    innerjoin vManagedEntityType MET on MET.ManagedEntityTypeRowId = ME.ManagedEntityTypeRowId

    innerjoin vManagedEntity TLME on TLME.ManagedEntityRowId = ME.TopLevelHostManagedEntityRowId

    innerjoin vManagedEntityType TLMET on TLMET.ManagedEntityTypeRowId = TLME.ManagedEntityTypeRowId

    where PERF.DateTime>(GETUTCDATE()- 182)

    orderby ME.ManagedEntityTypeRowId

     

11. Click Save

1. Select Refresh All from the Refresh pulldown in the ribbon in the Home menu 

2. Click Close when the refresh is complete
3. Close the Power Pivot window
4. Click OK in the Power View dialog window 

5. Select Austin from the Themes pulldown in the Themes section of the ribbon of the POWER VIEW menu to distinguish the reports from the seven day model 

6. Review the reports to make sure they are still presentable 

7. Save the workbook

I just dropped my van off for some maintenance at the dealership and am currently waiting for a shuttle to take me to the office. As I sit here I’m thinking about EOP and PowerShell and have come up with a great idea for this week’s article. I don’t always think about EOP outside of work, but when I do, watch out! Already, let's dive in.

In my role I work with customers that are brand new to Exchange Online Protection and assist them in implementing and troubleshooting the service. Typically customers come from a 3rd party spam filtering service and have existing safe and block lists in place which they want to migrate over to EOP. If these lists are long, the process of adding them to EOP through the online portal can be very agonizing. Luckily, there’s an easier and quicker way to do this, PowerShell to the rescue! This article is going to focus on lists that are comprised of sender domains, but this script can easily be modified for specific senders.

Example

We have a list of domains we want to safe list in EOP. We may have an existing rule that we would like to append domains to, or we may need to create a new rule from scratch.

First off, create a .csv file containing all of the domains (one per line) that should be added to the safe list. Here’s what mine looks like.

Once this is created we can jump into PowerShell.

1. If there isn’t an existing transport rule then we’ll need to create one. Since we’re talking about PowerShell let’s use a cmdlet to accomplish this. If you already have a safe list transport rule then go straight to step #2.
   
   New-TransportRule –name SafeDomains –SetSCL -1
   
   The above will set the SCL to -1 (Bypass spam filtering) for messages that trigger this rule.
   
   
2. Now we need to add the domains that we want to safe list to this rule. The following script will work both for brand new rules and for existing rules. If you have an existing safe list rule, this script will append the new entries to those that already exist in the rule.
   
   $csvImport=Import-Csv .\SafeDomains.csv -header domains
   $rule = Get-TransportRule SafeDomains
   
   #create safeDomains as an array
   $safeDomains = @()
   
   if ($rule.SenderDomainIs -ne $null)
   {
   $safeDomains = $rule.SenderDomainIs
   }
   
   foreach($v in $csvImport.domains)
   {
   $safedomains += $v
   }
   
   set-TransportRule SafeDomains -SenderDomainIs $safeDomains

That’s it! Here’s how my rule looks in the portal.

 
To create a block list, change the action above to how you would like EOP to handle messages that are received from the blocked domains (ex. delete message, move to quarantine, set a high SCL, etc…).

Connecting to PowerShell is quite easy, but often people need just a little push in the right direction with a sample script to get really moving on their own. It reminds me of this saying.

Give a person a fish and you feed them for a day. Teach a person to fish and you feed them for a lifetime.

Happy scripting!

Resources

Exchange Online PowerShell
Exchange Online Protection PowerShell

Note: If you have Exchange Online licenses (which include EOP), use the first link. If you have Exchange Online Protection licenses, use the second link.

Posted by Richard Harper

Given erroneous press reports about our research, as the lead for a Microsoft Research project called WindUp, I want to clarify our project’s objectives. We released WindUp into the Windows Phone Store last week as part of our ongoing research.  Our goal is to learn how people create, share and converse about content online.

WindUp is a mobile application for research purposes only that enables users to share images, videos, text, and audio snippets for a finite period of time, or for a designated number of views, before the content in question is deleted permanently. The application is designed to enable me and my team to explore patterns of content creation and exchange.  It isn’t meant to compete with anyone else’s service, and it isn’t meant for commercial purposes.

At Microsoft Research, part of our work from time to time involves building prototypes that let us explore some basic research questions. We hope that people give WindUp a test and share their experiences with us, and we look forward to the feedback and the insights we’ll gain.

On August 26, 2014, we will hold the fourth of our bi-monthly Solutions Advisory Board (SAB) webinars. SAB webinars are one hour and consist of brief presentations followed by time for open feedback.

Here is the agenda for the August 2014 webinar:

• Introductions and logistics – Chris Fox or Joe Davies
• Enterprise cloud architecture – Brenda Carter
  • Visual representation of IT architecture across Microsoft Cloud offerings by IT discipline — identity, storage, networking, security, high availability (HA) and disaster recovery (DR), and mobility.
  • Q&A
• An automated file collection system that supports e-Discovery – Chris Fox
  • Overview of an automated method to collect, sort, and store editable content and .PST files that are stored on local drives for eDiscovery.
  • Q&A
• Using Hyper-v replica in conjunction with DFS and Exchange DAG to provide close-to-fail-safe HA –SAB MEMBER Steve Rubin
  • The challenge and its solution.
  • Q&A
• Azure solutions – Joe Davies
  • SharePoint Server Farm feature of the Azure Preview Portal.
  • Azure solutions content for SQL Server, Desktop Hosting, Windows Server Essentials.
  • Q&A
• Hybrid Cloud Base Configuration Test Lab Guide (TLG) [if time permits]
  • Give feedback early on this new configuration for hybrid-based test/dev and PoC environments.
  • Q&A
• Resources and wrap-up – Chris Fox or Joe Davies

This Webinar is extra-special because Steve Rubin, an SAB member, will be presenting his own solution. This fulfills our original and ongoing promise to promote our members' own solution ideas within the rest of the SAB community. Thanks so much for stepping up, Steve!

To prepare for this webinar, please look over the following resources:

• For enterprise cloud architecture, see the existing posters at http://aka.ms/azposters and http://aka.ms/moda.
• For eDiscovery, see the eDiscovery flow poster.
• For Azure solutions content, see the Solutions node in the Windows Azure Technical Documentation Library
• For Test Lab Guides in Azure, see the Azure Test Lab portal page in the TechNet Wiki.

We are anxious to hear your feedback on these topics to help us refine our content efforts going forward.

We will have two sessions at different times on August 26 to accommodate all our members worldwide. We have sent every SAB member Lync meeting invitations for both meetings so you can accept the one the best fits your schedule.

Thanks and see you on the 26th!

Note: By participating in this webinar you agree that Microsoft may record and use this session for internal purposes only.

To receive an invitation to an SAB Webinar, you must be an SAB member. To join the SAB, send an email-based request to SAB@microsoft.com. Please feel free to include any information you want about your experience in creating solutions with Microsoft products or areas of interest.

Microsoft recently announced Windows Apportals, Windows 8.1 apps that can integrate a customer’s entire line of business (LOB) stack into a single, modern, touch-based experience. Windows Apportals were built in response to numerous customer requests to create an “on-the-glass” integration for the wide variety of LOB apps that exist in their organizations today, including legacy Windows 7 desktop applications; newer, modern Windows 8 apps, and web-based applications. Apportals can be generated by vertical, by industry, or by role, and allow custom branding with customer-specific logos.

On August 26, 27, and 28, I will be hosting one-hour calls to talk to partners interested in the opportunity to add Apportals as a service offering to their business. I’ll demonstrate how quickly and easily you can build an Apportal with the Apportal Prototype Generator, and share information about the advantages an Apportal provides customers.

Register for one of these one-hour calls:

• Tuesday, August 26 at 12:00PM Eastern Time / 9:00AM Pacific Time

• Wednesday, August 27 at 1:00PM Eastern Time / 10:00AM Pacific Time 

• Thursday, August 28 at 3:00PM Eastern Time / 12:00PM Pacific Time

We will record one of the above sessions for on-demand viewing.

Prior to attending the call, download these Apportal resources. For access, you will need to sign in with your Microsoft account associated to your MPN membership.

• Guide to building a Windows Apportal

• Apportal Prototype Generator

 Here are some of the benefits for partners that build and implement Windows Apportals for customers:

• Easy to sell – you have the opportunity to create value-based pricing models which solve business needs and take advantage of existing legacy infrastructure and non-Microsoft applications

• Increased margin opportunity

• Pricing power – there is greater perceived value

• Cost margin – re-usable code sets, no licensing

• Organizational architecture – end-to-end workflow requirement drives visibility into more of the customer’s organization, enabling a broader solution sell 

• CMO/CIO engagement – pitch to Business Decision Makers, but have IT on your side because Apportals provide a fully managed solution

I hope you'll join me to learn about this new partner opportunity. Register today.