Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

Resources for IT Professionals

older | 1 | .... | 829 | 830 | (Page 831) | 832 | 833 | .... | 889 | newer

    0 0

    Hello Wiki Ninjas and much valued TechNet and MSDN members !!!

    After watching several times "a movie" and gave all my money to Lucas ...ops... to Mickey...

    I'm back !!!

     

    Wiki Ninja Belt

    The Ninja Belt Calculator has just been run, and the list of Ninja Belts have been updated in the following TechNet WIki article:

     

    Wiki Ninja Belt Status: Who Has What Belt Ranking

     

    The calculator has been run monthly, due to the constant work done of everyone involved to make Wiki Ninja Belts a reality.

    It recognizing their work to sharing knowledge in Technical articles to Developers and IT Professionals.

    You don't know what to do get your TNWiki Ninja Belt?

    Well... anyone who "comes onto our radar" (either by winning a Weekly Top Contributor Award, winning a TechNet Technical Guru Award, being interviewed or having a Featured Article) gets added to our database.

    We then track your progress and achievements, and award Ninja Belts - depending on your progress.

    Ninja belt ranks include your TechNet / MSDN Profile stats, so we have to import them too.

    Altogether, this is crunched through our Ninja Belt Calculator, based on the rules defined here.

    See below is a list of those Community members who are being promoted to Ninja Belt levels:

     

    Calculator Belt Upgrades (January, 29th)

    User Name Ninja Belt
    Ken Cenerelli Blue Belt
    Erdem SELÇUK Green Belt

      

    Congratulations to all these Wiki Ninjas for gaining ranks in January, 2016 !!!


    And don't forget to review your next steps to Ninja Belt Ranks:

    Read more about the Wiki Ninja Belts and the Ranking System.

     

      

      

    See a full list of who has what ranking.

    This really was a special month to our Community. 

    So join us in sharing knowledge and stand out among other professionals.

    We have excellence to share effective solutions, because we have talented authors.

     

    See you soon here !

    Brazilian Wiki Ninja Durval


    0 0

    Olá amigos da comunidade.

    Sejam bem-vindos a nossa Atualização Internacional.

    O destaque da semana vem dos Estados Unidos da América.




    Falamos de Naomi N.



    Contribuições:

    Ela faz parte da comunidade desde 2007.

    Ganhadora de vários prêmios como TechNet Guru e MCC.

    Destaque em diversas publicações internacionais na área de desenvolvimento de software.

    Membro do conselho e como autora ela escreveu diversos artigos no Wiki.


    Esses são alguns dos seus artigos:


    T-SQL: Relational Division

    SQL Server: Searching All Columns in a Table for a String

    T-SQL: Applying APPLY Operator

    TechNet Guru Contributions

    How SQL Server Determines Type of the Constant

    TechNet Guru Contributions - Transact SQL

    Visual FoxPro: How to Have Two Related Comboboxes in a Grid Control

    T-SQL: Split String with a Twist

    Fixing Missing Data Based on Prior Row Information

    T-SQL: Group by Time Interval

    Patindex Case Sensitive Search

    T-SQL: How to Find Rows with Bad Characters

    T-SQL: Gaps and Islands Problem

    T-SQL: Random Equal Distribution

    T-SQL: Date-Related Queries

    T-SQL: Date-Related Queries

    T-SQL: Create Report for Last 10 Years of Data



    É muito bom ver a comunidade internacional em ação.

    Convido a comunidade a dar os parabéns a ela pela excelente contribuição na comunidade.

    Agradecemos a atenção.



    Wiki Ninja @Hezequias Vasconcelos ++

    0 0

    撰文者:數位時代 發表日期:2016/01/27

    電子競技(e-Sports)是數位世代的新體育,隨著網路與電腦技術成熟,電競遊戲的玩家與觀眾不斷在成長,尤其是台灣,根據Twitch全球最大遊戲影音串流平台統計,台灣是全球觀賞流量排名第五的國家,而台北市是Twitch全球城市排名中,流量最多的城市。

    如此龐大的電競觀眾,賦予台灣電競內容很大的成長空間,前電競國手黃智仁在2013年成立方舟數位(4Gamers),從電競賽事的規劃執行、行銷到現場直播,提供完整內容端的解決方案,希望打破電競賽事依附在遊戲公司下的現況,讓電競賽事不只是比賽,更是娛樂觀光產業的一環。

    方舟數位成立短短3年間就成效斐然,不只公司人數突破20人,2014年所執行的電競賽事更高達40多場,其中以「IEM英特爾全球世界大賽」成效最為驚人,3天累積不重覆瀏覽量高達35萬人,最多有5萬人同時在線。

    搶攻電競內容 提供完整賽事方案

    由於方舟數位提供的是完整電競賽事解決方案,因此內部有各式各樣的提案簡報,滿足不同客戶需求,目前,國內甲組電競賽事的社群操作,有一半以上的主導權在方舟數位身上。

    此外,方舟數位還有一項秘密武器,就是黃智仁自己研發的電競賽事系統,這套系統可以在半小時內安排參賽選手的對戰組合和賽程,還能記錄前一場比賽對伍的戰績,甚至還會為選手們建立檔案,留下選手詳細的爭戰紀錄,讓參賽選手和隊伍都能藉此找到贊助廠商。

    方舟數位IMC專家陳韋博表示,過往要到客戶處提案時,必須先用辦公室電腦的Office軟體製作提案簡報,再將簡報存在隨身碟裡,然後帶著隨身碟與筆電去客戶端提案,倘若遇到客戶有不同意見或要做會議記錄的情況,都只能寫在紙上,等回到辦公室再修改檔案。

    但是現在陳韋博將筆電改成Surface Pro 4、Office軟體換成軟體換成訂閱Office 365雲端服務,拜訪客戶時不再需要一堆設備,只要一台Surface Pro 4和網路,就能隨時存取及編輯提案簡報,省去許多檔案傳送的步驟,同時也節省電腦空間。

    「Office 365整合OneDrive雲端儲存功能,我認為這是最方便的地方,」陳韋博滿意地說,他進一步指出,自從改用Office 365,提案簡報製作完成後,檔案都直接上傳到OneDrive雲端儲存,到客戶端再開啟手機4G網路分享的功能,如果客戶有什麼需要修改的地方,或會議中有需要記錄的事情,也可以直接在檔案裡修正,修正完的檔案直接上傳至雲端,省一道寫在紙上的工夫,也不必擔心檔案存來存去可能會有的版本問題。

    第6代Intel® Core™處理器 讓國際級直播活動順暢到底

    目前方舟數位除了電競賽事直播外,也承辦各種不同活動(如:研討會、記者會)的現場直播業務。

    在現場直播的分工上,導播是靈魂人物,導播機和控盤則是主要的兩個設備,導播機負責接收各路訊號,導播則經由控盤決定目前要呈現哪一路訊號要在主螢幕上,但只有在攝影棚內拍攝的時候才能這麼做,如果遇到外出辦活動時,由於設備繁多,為求精簡體積,方舟數位多半以筆電取代控盤,讓導播用滑鼠操作筆電內的控盤模擬軟體。

    然而,實體控盤為按鍵式設計,筆電卻得用滑鼠操作,在使用上難免會令人感到不方便,再者有時活動主辦單位受限於空間,只能提供一張折疊會議桌,光是放置直播所需用到的機台設備便已稍嫌不足,再加上用來取代控盤的筆電,更是占空間,如何精簡設備與善用空間,是方舟數位出外景時最頭痛的問題,而Surface Pro 4的輕便與觸控功能,成為解決這個問題的最佳答案。

    陳韋博認為,Surface Pro 4比筆電更適合取代實體控盤,因其為觸控式設計不僅直覺,也比較貼近實體控盤的操作方式,而且它體積非常輕巧、可以直立式擺放不占桌面空間,更適合外出辦活動使用。

    此外,Surface Pro 4在硬體上採用第6代Intel® Core™處理器,不僅運算效能強,可以穩定迅速地運作控盤模擬軟體,甚至還能多工進行其他的任務,例如:畫面監看,因為Surface Pro 4螢幕解析度較前一代升級為2,763×1,824畫素,畫素密度則是267ppi,可以清楚地呈現攝影機所錄到的現場畫面,再加上杜比音效立體聲喇叭的配置,讓導演更能精確掌握現場收音狀況。

    總結來看,Surface Pro 4直覺性觸控、軟硬體完美結合的設計,讓方舟數位在客戶提案、現場直播更方便,期待未來在Surface Pro 4與Office 365助力下,讓方舟數位能夠為台灣電競圈,甚至世界電競圈產出更豐富的內容。

    (本文為台灣微軟與《數位時代》整合行銷部共同企劃。)


    0 0

    (Alternative title: "Help, I synched Upgrades before installing the patch!" 

    This applies to anyone who missed KB 3095113 when it was offered as a hotfix, and subsequently enabled synching of Upgrades in their environment.  The upgrades that were downloaded happen to be from the Windows 10 1511 feature upgrade, but these steps could be modified to suit a similar purpose for a different set of content.)

    In this scenario, WSUS has downloaded content that it cannot use.  Because parsing only happens once, and WSUS does not know what “Upgrades” are without having installed KB 3095113, it incorrectly identifies the upgrade as a regular update and saves it to the SUSDB as such.  In order to remedy this, you must perform the following sequence of steps on the WSUS servers as specified in the table below (where "USS" represents "upstream server"):

    Action

    Where to perform

    1.       Disable the “Upgrades” classification

    USS or Standalone WSUS

    2.       Delete the previously synched upgrades

    All WSUS (start with topmost server)

    3.       Enable the “Upgrades” classification

    USS or Standalone WSUS

    4.       Perform full sync

    USS or Standalone WSUS

    Some workarounds propose that you delete these entries from the SUSDB via SQL queries, but we do not recommend directly modifying database content.  The supported way to remove update content is with PowerShell commands [from an elevated session] as described below.  Again, be sure that you perform the deletion step on the WSUS server that is highest in your hierarchy first, and then work your way down; otherwise, your deletions may be replaced by the USS on the next sync attempt. 

    // disable Upgrades classification on local WSUS server

    Get-WsusClassification | Where-Object -FilterScript {$_.Classification.Title -Eq “Upgrades”} | Set-WsusClassification -Disable  

    // delete all update content on the current server belonging to the 1511 release

    $s = Get-WsusServer

    $s.SearchUpdates(“version 1511, 10586”) | foreach { $s.DeleteUpdate($_.Id.UpdateId) } 

    // enable Upgrades classification

    Get-WsusClassification | Where-Object -FilterScript {$_.Classification.Title -Eq “Upgrades”} | Set-WsusClassification 

    // perform full sync

    $sub = $s.GetSubscription()

    $sub.StartSynchronization()


    0 0

    こんにちは。日本マイクロソフトの松岡でございます。

    本日は、クラスター環境の IP アドレス変更手順についてご紹介いたします。

     

    クラスター環境の移行をおこなう場合など、クラスターを構成している各ノードの物理 IP アドレスと、クラスター上で稼働しているアプリケーションに紐づく仮想 IP アドレスを変更する必要がある場合があります。その際、クラスター環境の IP アドレス変更については、以下の 3 種類の IP アドレスの変更を検討していただく必要があります。

     

    物理 IP アドレス:

    ・クラスター構成ノード (物理サーバー) IP アドレス


    仮想 IP アドレス:

    ・クラスター管理用 (クラスターコアリソース) の仮想 IP アドレス

    ・クラスター化されたアプリケーションの仮想 IP アドレス

     

    今回は上記 3 つの IP アドレスの変更の順番と、変更方法についてご案内したいと思います。

     

    ※注意点※

    クラスター環境構成後はドメイン移行、物理ホスト名の変更はサポートしておりません。

    変更が必要となる場合には、一度クラスターを解除する必要があります。

     

    仮想 IP の変更を行う場合、クラスター化されたアプリケーションの設定も変更が必要な場合があります。

    詳細につきましてはご利用のアプリケーションの提供元様にご確認ください。

     

     設定手順

    ===========

    Blog では Windows Server 2012 R2 における IP アドレスの変更手順についてご案内します。

     

    設定手順は以下の順番で行います。

     

    1) クラスターサービスの停止

    2) クラスター構成ノード (物理サーバー) IP アドレス変更

    3) クラスター管理用 (クラスターコアリソース) IP アドレス変更

    4) クラスター化されたアプリケーションの IP アドレス変更

     

    1) クラスターサービスの停止方法

    --------------------------------

    クラスターの IP アドレスを変更するには、[クラスター コア リソース] と、クラスター上で稼働している各種アプリケーションを停止した上で、クラスターサービスを停止する必要があります。

     [クラスター コア リソース] と、クラスター上で稼働している各種アプリケーションを停止する理由は、不要なクラスター リソースの失敗やエラーの検知を避けて、変更が完了したものから順番に起動することで、正常にオンラインになるかを確認する為です。

     

    1-1.

    [フェールオーバークラスターマネージャー] を開きます。

     

    1-2.

    左側のウィンドウから [クラスター名] を選択した後、中央ウィンドウの [クラスターコアリソース] を展開します。[サーバー名] を展開し、[IP アドレス: XXX.XXX.XXX.XXX] を右クリックし、[オフラインに移行] を選択します。

     

     

    1-3.

    左側のウィンドウから [役割] を展開し、登録されているグループを、右クリックし、[役割の停止] を選択します。

    ※この手順で、役割に登録されている全てのグループを停止してください。

     

      

    1-4.

    左側のウィンドウから [クラスター名] を 右クリックし、[他のアクション] より [クラスターのシャットダウン] を選択し、クラスターを停止させます。

     

      

    以上で、クラスター サービスの停止は完了です。

     

    2) クラスター構成ノード (物理サーバー) IP アドレス変更手順

    -------------------------------------------------------------

    IP アドレスを変更するノード (物理サーバー) にログインし、以下の手順を各ノード上で実施します。

     

    2-1.

    [ネットワークと共有センター] を開き、[アダプタ―の設定の変更] から [ネットワーク接続] の画面に進みます。

    IP アドレスを変更するネットワークアダプタを右クリックし、表示されたメニューから [プロパティ] を選択します。

      

    2-2.

    中央の"この接続は次の項目を使用します" の一覧から、変更する IP [TCP/IPv4] または [TCP/IPv]6 を選択し、[プロパティ] をクリックします。

    2-3.

    [次の IP アドレスを使う] または [次の IPv6 アドレスを使う] がチェックされた状態で、IP アドレスを設定し [OK] をクリックします。

     

     

    以上で、クラスター構成ノード (物理サーバー) IP アドレス変更は完了です。

     

    - 補足 ------

    なお、本手順によってセグメントの変更されると、クラスターに登録されているネットワーク名が、規定の「クラスター ネットワーク 1 」などに変更され、ネットワークのオプションが「クラスターのみ」となる場合がございます。その際は、ネットワークのサブネットをご確認の上、適切なネットワークの設定を再度おこなってください

    <参考> フェールオーバークラスターのネットワーク設定を変更する

    https://technet.microsoft.com/ja-jp/library/cc725775.aspx

    また、変更したネットワークがフェールオーバー クラスター マネージャー上から見えていない場合には、上記手順 2-1. から変更したネットワークを右クリックし、 [無効] にしていただき、再度 [有効] を選択してください。同時に、一度フェールオーバー クラスター マネージャーを閉じていただき、再度開いていただくことで最新の情報が反映されます。

    -------------

     

    3) クラスター管理用 (クラスターコアリソース) IP アドレス変更手順

    ---------------------------------------------------------------------

    物理 IP アドレスの変更後に、[フェールオーバー クラスター マネージャー] から仮想 IP アドレスの変更を実施します。

     

    3-1.

    [フェールオーバークラスターマネージャー] の左側のウィンドウから [クラスター名] を右クリックし、[クラスターの起動] を選択し、クラスターサービスを起動します。

    ※もし [クラスター名] が表示されていない場合は、中央ウィンドウの"管理" から [クラスターに接続する] を選択し [OK] を押すと、クラスターに接続を開始します。接続完了後、左側のウィンドウに [クラスター名] が表示されます。

      

     

    3-2.

    左側のウィンドウから [クラスター名] を選択した後、中央ウィンドウの [クラスターコアリソース] を展開します。[サーバー名] を展開し、[IP アドレス: XXX.XXX.XXX.XXX] を右クリックし、[プロパティ] を選択します。

     

     

    3-3.

    [全般] タブから [ネットワーク] のリストから使用するサブネットを選択し、[静的 IP アドレス] の項目から使用する IP アドレスを設定し、[適用] を選択した後、[OK] を選択します。

     

      

    3-4.

    中央ウィンドウの [クラスタコアリソース] 内の [サーバー名] を右クリックし、[オンラインにする] を選択し、変更した IP アドレスリソースが正常にオンラインになることを確認します。

     

     

    以上で、クラスター管理用 (クラスターコアリソース) IP アドレス変更は完了です。

     

    4) クラスター化されたアプリケーションの IP アドレス変更手順 

    -----------------------------------------------------------

    上記、クラスター コア リソースの IP アドレス変更手順と同じ手順で、変更が必要な全てのアプリケーションの仮想 IP アドレスの変更を実施します。

     

    4-1.

    [フェールオーバークラスターマネージャー] の左側のウィンドウから [役割] を選択し、登録されているグループを選択します。下の [リソース] タブを選択し、変更したい [IP アドレス: XXX.XXX.XXX.XXX] をダブルクリックします。

     

    4-2.

    [全般] タブから [ネットワーク] のリストから使用するサブネットを選択し、[静的 IP アドレス] の項目から使用する IP アドレスを設定し、[適用] を選択した後、[OK] を選択します。

     

    4-3.

    変更した IP アドレスリソースが紐づくアプリケーションを右クリックし、[オンラインにする] を選択します。登録されているアプリケーションが正常にオンラインになることをご確認ください。

     

    上記変更方法を参考に、変更が必要な全てのアプリケーションの仮想 IP アドレスの変更を実施してください。

    以上の手順でクラスターの IP アドレスの変更の全てが完了です。

      

    - クラスター構成の確認

    -----------------------

    以上の手順を実施した後、変更を行った IP アドレスリソースが正常にオンラインになっているかをご確認いただき、通信に問題はないか、またイベント ログにエラーが出ていないかをご確認ください。

    ※アドレスの変更に伴って、IP アドレスのエラー (FailoverClustering ID:1069) や通信の切断を示す (FailoverClustering ID:1123) などが発生する可能性があります。IP アドレスに関するエラーについても、作業完了後に発生したエラーでなければ問題は無いので、ご安心ください。

     

    また、クラスター構成を変更した後は構成の検証を行いクラスターが正常に動作しているかご確認ください。クラスターの検証については、左側ウィンドウの [クラスター名] を右クリックし、[クラスターの検証] から実施することが出来ます。

     

    <参考> フェールオーバークラスター構成の検証

    https://technet.microsoft.com/ja-jp/library/cc772055.aspx

     

    このブログが皆様のお役に立てれば幸いです。


    0 0

    Summary: Windows PowerShell MVP, Teresa Wilson, shares her roundup of Windows PowerShell activities for the coming months.

    Hello scripters,

    Teresa Wilson here. I hope you had a marvelous weekend and are ready to tackle this week. Ed is finally getting back to normal and we have a few trips coming up—all Windows PowerShell related.

    Arizona PowerShell User Group March 1 in Phoenix

    First of all, we will be in Phoenix, AZ on March 1, 2016 for the Arizona PowerShell User Group (AZPOSH) meeting. I also heard from a little birdie that my good friend Jason Helmick will be there. The signup is not available yet (they are still promoting their February meeting) but as soon as it is, I will tweet it and put it on the Scripting Guys Facebook page. I might even try to talk Ed into posting another short blog about it with signup information.

    PowerShell Saturday #010 March 19 in Tampa

    Next is PowerShell Saturday #010 in Tampa, Florida at the University of South Florida (USF) on March 19, 2016. We have an amazing lineup of speakers and sessions. There will be something for everyone—no matter what your skill level. We have five MVPs, six Microsoftees, and two user group leaders confirmed. Here is a link to information about the PowerShell Saturday #010 speakers. This will be a day loaded with PowerShell goodness.

    I am not going to write about the sessions in this post. For more information, please read the Session synopses. We will be adding a few more sessions in the upcoming days. There will be four tracks with five sessions in each track. This means roughly five hours of training for you.

    We are not doing this to make money. We are charging a small fee to cover the cost of the food, and if we have any leftover, we will buy more swag to give away.

    Our sponsors are on board to help us with the expenses that go along with an event. We could not put on a day of training like this without the sponsors. And we also want to recognize the speakers who pay their own travel expenses and the companies that pay the travel for their employees to attend. We have speakers coming from Canada, Wisconsin, Utah, Tennessee, Ohio, Georgia, and all over Florida.

    I would be remiss if I did not mention Ed and my cohost for this day. Microsoft evangelist, Blain Barton (@blainbar on Twitter), has been amazing in getting this show on the road. Our other partner in crime is Will Anderson, our webmaster. Will is an MVP and Honorary Scripting Guy  (@GamerLivingWill on Twitter).

    With all this knowledge and PowerShell goodness just waiting to unfold, what are you waiting for? Sign up today: Register: PowerShell Saturday #010.

    ~Teresa

    I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at scripter@microsoft.com, or post your questions on the Official Scripting Guys Forum. Also check out my Microsoft Operations Management Suite Blog. See you tomorrow. Until then, peace.

    Ed Wilson, Microsoft Scripting Guy


    0 0
  • 02/01/16--01:00: Azure Point-to-Site VPN
  • Point-to-Site VPN umožňuje připojení koncového zařízení odkudkoliv do vytvořené virtuální sítě. Pro připojení se používá VPN klient, který je součástí Windows. Součástí konfigurace je instalace certifikátu a balíku konfigurace VPN klienta, který obsahuje veškerá nastavení pro připojení. Podporovanými operačními systémy...(read more)

    0 0

    Monitoring services in windows computers is available out of box in SCOM through Service Monitoring Template. But in a large enterprise with over 1000s of windows computers and 100s of applications, it is difficult to list out all services that needs to be monitored in each computer and create monitoring using template. Consider monitoring on average 30 services in 1000 computers would result on 30,000 instances added to SCOM DB. This will create numerous classes, discoveries and cause bloating of instance space which will make SCOM less responsive.

    Also, we cannot create a monitor for each service and target it across all computers as each service may be present on bunch of computers and not on others. Thus targeting unanimously will result in false alarms and again, we may need 30+ windows service monitors targeted to all windows computers which will create overhead on agents and thus on the computers running the agent.

    So, What is the solution?

    Optimal solution would be creating a single rule to monitor all automatic services in each computer and alert on those which are not running. This can be accomplished using Powershell script with property bag output.

    The rule runs on each computer at specific time interval, creates property bags for each service which is set to automatic but not running and an alert is generated for each property bag.

    A catch to note in this monitoring scenario is not to alert on services that are stopped only for a moment. To overcome the issue, we will use consolidator condition. So only if the service is failed for ‘n’ consecutive samples, we will alert.

    This solution, though optimal pose another challenge – What if we do not want to monitor a service which is set to automatic in one or few of computers.

    This can be handled using a centrally located file with details of service and the computers to be excluded from monitoring.

    We will see how to construct the Management Pack XML to accomplish this. You can also create MP using Visual Studio, MP Studio or Authoring Console.

    Step 1:

    Add references to the Management pack.

    1<ManagementPack ContentReadable="true" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> 2<Manifest> 3<Identity> 4<ID>GKLab.Windows.Automatic.Service.Monitoring</ID> 5<Version>1.0.0.0</Version> 6</Identity> 7<Name>GKLab Windows Automatic Service Monitoring</Name> 8<References> 9<Reference Alias="SC">10<ID>Microsoft.SystemCenter.Library</ID>11<Version>6.1.7221.0</Version>12<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>13</Reference>14<Reference Alias="Windows">15<ID>Microsoft.Windows.Library</ID>16<Version>6.1.7221.0</Version>17<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>18</Reference>19<Reference Alias="Health">20<ID>System.Health.Library</ID>21<Version>6.1.7221.0</Version>22<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>23</Reference>24<Reference Alias="System">25<ID>System.Library</ID>26<Version>6.1.7221.0</Version>27<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>28</Reference>29<Reference Alias="Performance">30<ID>System.Performance.Library</ID>31<Version>6.1.7221.0</Version>32<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>33</Reference>34</References>35</Manifest>

    Step 2:

    Now create a Powershell property bag probe script. The Powershell script fetches list for all services that are set to start automatic and checks for the current status. For each service that are set to Automatic but not running, a property bag is created.

    To exclude some services from being monitored, a centrally located CSV file is used and the path of file is passed as parameter to the script. The script reads list of services to be excluded from monitoring from CSV file and compares it with the list of services in the target computer. The property bag for excludes services are not created.

    1param ( 2 [string] $excludeservicelist 3) 4if (test-path $excludeservicelist) { 5write-eventlog -logname "Operations Manager"-Source "Health Service Script"-EventID 776-Message "WindowsAutomaticServiceMonitoring.ps1 - Accessing Exclusion List CSV"-EntryType Information 6$contents= Import-Csv $excludeservicelist 7} 8$TargetComputer= hostname 9$api= New-Object -comObject 'MOM.ScriptAPI'10$auto_services= Get-WmiObject -Class Win32_Service -Filter"StartMode='Auto'"11foreach ($servicein$auto_services)12{13$isExcluded=014$state=$service.state15$name=$service.DisplayName16If ($Contents){17$contents|ForEach-Object{18$ExcludeServiceDisplayName=$_.ServiceToExclude19$ExcludeComputerName=$_.ComputersToExclude20if (($name-match$ExcludeServiceDisplayName) -and (($TargetComputer-match$ExcludeComputerName) -or ($ExcludeComputerName-match"ALL_COMPUTERS"))){21$isExcluded=122#write-eventlog -logname "Operations Manager" -Source "Health Service Script" -EventID 777 -Message "WindowsAutomaticServiceMonitoring.ps1 - Excluded Service Name - $ExcludeServiceDisplayName, Excluded Computer Name - $ExcludeComputerName" -EntryType Information23 }24 }25 }26if (($isExcluded-eq0) -and ($state-eq"Stopped")){27#write-eventlog -logname "Operations Manager" -Source "Health Service Script" -EventID 778 -Message "WindowsAutomaticServiceMonitoring.ps1 - Windows Service set to Automatic but Not Running - $name" -EntryType Information28$bag=$api.CreatePropertyBag() 29$bag.AddValue("ServiceName", $name)30$bag.AddValue("Status", $state)31$bag32 }33}
    Step 3:

    Create a data source module incorporating the above written Powershell script. We will use consolidator condition as discussed in solution part to alert only on valid service failures.

    1<TypeDefinitions> 2<ModuleTypes> 3<DataSourceModuleType ID="GKLab.Windows.Auto.Service.Monitoring.DataSource" Accessibility="Internal" Batching="false"> 4<Configuration> 5<xsd:element minOccurs="1" name="ExcludeServiceList" type="xsd:string"/> 6<xsd:element minOccurs="1" name="IntervalSeconds" type="xsd:integer"/> 7<xsd:element minOccurs="1" name="ConsolidationInterval" type="xsd:integer"/> 8<xsd:element minOccurs="1" name="Count" type="xsd:integer"/> 9</Configuration>10<OverrideableParameters>11<OverrideableParameter ID="IntervalSeconds" Selector="$Config/IntervalSeconds$" ParameterType="int"/>12<OverrideableParameter ID="Count" Selector="$Config/Count$" ParameterType="int"/>13<OverrideableParameter ID="ConsolidationInterval" Selector="$Config/ConsolidationInterval$" ParameterType="int"/>14</OverrideableParameters>15<ModuleImplementation Isolation="Any">16<Composite>17<MemberModules>18<DataSource ID="Trigger" TypeID="System!System.SimpleScheduler">19<IntervalSeconds>$Config/IntervalSeconds$</IntervalSeconds>20<SyncTime>00:00</SyncTime>21</DataSource>22<ProbeAction ID="Probe" TypeID="Windows!Microsoft.Windows.PowerShellPropertyBagProbe">23<ScriptName>WindowsAutomaticServicesMonitoring.ps1</ScriptName>24<ScriptBody><![CDATA[25param (26 [string] $excludeservicelist27)28if (test-path $excludeservicelist) {29write-eventlog -logname "Operations Manager" -Source "Health Service Script" -EventID 776 -Message "WindowsAutomaticServiceMonitoring.ps1 - Accessing Exclusion List CSV" -EntryType Information30 $contents = Import-Csv $excludeservicelist31}32$TargetComputer = hostname33$api = New-Object -comObject 'MOM.ScriptAPI'34$auto_services = Get-WmiObject -Class Win32_Service -Filter "StartMode='Auto'"35foreach ($service in $auto_services)36{37 $isExcluded = 038 $state = $service.state39 $name = $service.DisplayName40 If ($Contents){41 $contents | ForEach-Object{42 $ExcludeServiceDisplayName = $_.ServiceToExclude43 $ExcludeComputerName = $_.ComputersToExclude44 if (($name -match $ExcludeServiceDisplayName) -and (($TargetComputer -match $ExcludeComputerName) -or ($ExcludeComputerName -match "ALL_COMPUTERS"))){45 $isExcluded = 146 write-eventlog -logname "Operations Manager" -Source "Health Service Script" -EventID 777 -Message "WindowsAutomaticServiceMonitoring.ps1 - Excluded Service Name - $ExcludeServiceDisplayName, Excluded Computer Name - $ExcludeComputerName" -EntryType Information47 }48 }49 }50 if (($isExcluded -eq 0) -and ($state -eq "Stopped")){51 write-eventlog -logname "Operations Manager" -Source "Health Service Script" -EventID 778 -Message "WindowsAutomaticServiceMonitoring.ps1 - Windows Service set to Automatic but Not Running - $name" -EntryType Information52 $bag = $api.CreatePropertyBag() 53 $bag.AddValue("ServiceName", $name)54 $bag.AddValue("Status", $state)55 $bag56 }57}58]]></ScriptBody>59<Parameters>60<Parameter>61<Name>ExcludeServiceList</Name>62<Value>$Config/ExcludeServiceList$</Value>63</Parameter>64</Parameters>65<TimeoutSeconds>300</TimeoutSeconds>66</ProbeAction>67<ConditionDetection ID="Consolidator" TypeID="System!System.ConsolidatorCondition">68<Consolidator>69<ConsolidationProperties>70<PropertyXPathQuery>$Target/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</PropertyXPathQuery>71<PropertyXPathQuery>Property[@Name='ServiceName']</PropertyXPathQuery>72</ConsolidationProperties>73<TimeControl>74<WithinTimeSchedule>75<Interval>$Config/ConsolidationInterval$</Interval>76</WithinTimeSchedule>77</TimeControl>78<CountingCondition>79<Count>$Config/Count$</Count>80<CountMode>OnNewItemTestOutputRestart_OnTimerSlideByOne</CountMode>81</CountingCondition>82</Consolidator>83</ConditionDetection>84</MemberModules>85<Composition>86<Node ID="Consolidator">87<Node ID="Probe">88<Node ID="Trigger"/>89</Node>90</Node>91</Composition>92</Composite>93</ModuleImplementation>94<OutputType>System!System.ConsolidatorData</OutputType>95</DataSourceModuleType>96</ModuleTypes>97</TypeDefinitions>

    Step 4:

    Next we will create a rule using the data source. Below configuration needs to be customized according to the need.

    ExcludeServiceList – the UNC path for the excluded services list file (in CSV format). Sample CSV provided below.

    CSV has two headers- “ServiceToExclude” which is display name of service.

    ComputersToExclude – NetBIOS Name of computer. If two or more computers, it can be specified as individual entry or using regular expression syntax. If need to exclude in all computers, the value should be “ALL_Computers”

    1ServiceToExclude,ComputersToExclude2Distributed Transaction Coordinator,SCOM2012R23Windows Audio,Win2k12-DC4Remote Registry,ALL_Computers5Software Protection,SCOM2012R2|Win2k12-DC

    IntervalSeconds – Polling Interval in Seconds

    Count – Number of polls, the service should fail to alert. (Minimum 2)

    ConsolidationInterval – The interval time within which the service status fails ‘n’ number of times to generate alert.  (Minimum value = (n-1) * IntervalSeconds where n = count)

    1<Monitoring> 2<Rules> 3<Rule ID="GKLab.Windows.AutomaticService.Monitoring.Rule" Enabled="true" Target="Windows!Microsoft.Windows.Computer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100"> 4<Category>Alert</Category> 5<DataSources> 6<DataSource ID="DS" TypeID="GKLab.Windows.Auto.Service.Monitoring.DataSource"> 7<ExcludeServiceList>\\SCOM2012R2\Configs\WindowsAutomaticServiceMonitoringExclusionList.csv</ExcludeServiceList> 8<IntervalSeconds>300</IntervalSeconds> 9<ConsolidationInterval>600</ConsolidationInterval>10<Count>2</Count>11</DataSource>12</DataSources>13<WriteActions>14<WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">15<Priority>1</Priority>16<Severity>2</Severity>17<AlertMessageId>$MPElement[Name="GKLab.Windows.AutomaticService.Monitoring.Rule.AlertMessage"]$</AlertMessageId>18<AlertParameters>19<AlertParameter1>$Data/Context/DataItem/Property[@Name='ServiceName']$</AlertParameter1>20</AlertParameters>21<Suppression>22<SuppressionValue>$Target/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</SuppressionValue>23<SuppressionValue>$Data/Context/DataItem/Property[@Name='ServiceName']$</SuppressionValue>24</Suppression>25</WriteAction>26</WriteActions>27</Rule>28</Rules>29</Monitoring>

    Step 5:

    Final step is to construct XML for presentation and language packs. Ensure the close the <ManagementPack> tag.

    1<Presentation> 2<StringResources> 3<StringResource ID="GKLab.Windows.AutomaticService.Monitoring.Rule.AlertMessage"/> 4</StringResources> 5</Presentation> 6<LanguagePacks> 7<LanguagePack ID="ENU" IsDefault="true"> 8<DisplayStrings> 9<DisplayString ElementID="GKLab.Windows.Automatic.Service.Monitoring">10<Name>GKLab Windows Automatic Service Monitoring</Name>11<Description>GKLab Windows Automatic Service Monitoring Management Pack</Description>12</DisplayString>13<DisplayString ElementID="GKLab.Windows.Auto.Service.Monitoring.DataSource">14<Name>GKLab Windows Automatic Service Monitoring Data Source</Name>15<Description>GKLab Windows Automatic Service Monitoring Data Source</Description>16</DisplayString>17<DisplayString ElementID="GKLab.Windows.AutomaticService.Monitoring.Rule">18<Name>Windows Automatic Services Monitoring Rule</Name>19<Description>Windows Automatic Services Monitoring Rule</Description>20</DisplayString>21<DisplayString ElementID="GKLab.Windows.AutomaticService.Monitoring.Rule" SubElementID="Alert">22<Name>Alert</Name>23</DisplayString>24<DisplayString ElementID="GKLab.Windows.AutomaticService.Monitoring.Rule" SubElementID="DS">25<Name>GKLab Windows Automatic Service Monitoring Data Source</Name>26</DisplayString>27<DisplayString ElementID="GKLab.Windows.AutomaticService.Monitoring.Rule.AlertMessage">28<Name>Windows Automatic Services Monitoring Alert</Name>29<Description>Windows Service {0} is set to auto-start but is currently not running.</Description>30</DisplayString>31</DisplayStrings>32</LanguagePack>33</LanguagePacks>34</ManagementPack>

    Step 7:

    Deploy the MP in lab and check for alerts.

    image

     

    I have attached copy of XML which you can import in to any authoring tool. Customize as per your needs and have fun.

    Happy SCOMing…


    0 0

    Monitoring services in windows computers is available out of box in SCOM through Service Monitoring Template. But in a large enterprise with over 1000s of windows computers and 100s of applications, it is difficult to list out all services that needs to be monitored in each computer and create monitoring using template. Consider monitoring on average 30 services in 1000 computers would result on 30,000 instances added to SCOM DB. This will create numerous classes, discoveries and cause bloating of instance space which will make SCOM less responsive.

    Also, we cannot create a monitor for each service and target it across all computers as each service may be present on bunch of computers and not on others. Thus targeting unanimously will result in false alarms and again, we may need 30+ windows service monitors targeted to all windows computers which will create overhead on agents and thus on the computers running the agent.

    So, What is the solution?

    Optimal solution would be creating a single rule to monitor all automatic services in each computer and alert on those which are not running. This can be accomplished using Powershell script with property bag output.

    The rule runs on each computer at specific time interval, creates property bags for each service which is set to automatic but not running and an alert is generated for each property bag.

    A catch to note in this monitoring scenario is not to alert on services that are stopped only for a moment. To overcome the issue, we will use consolidator condition. So only if the service is failed for ‘n’ consecutive samples, we will alert.

    This solution, though optimal pose another challenge – What if we do not want to monitor a service which is set to automatic in one or few of computers.

    This can be handled using a centrally located file with details of service and the computers to be excluded from monitoring.

    We will see how to construct the Management Pack XML to accomplish this. You can also create MP using Visual Studio, MP Studio or Authoring Console.

    Step 1:

    Add references to the Management pack.

    1<ManagementPack ContentReadable="true" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> 2<Manifest> 3<Identity> 4<ID>GKLab.Windows.Automatic.Service.Monitoring</ID> 5<Version>1.0.0.0</Version> 6</Identity> 7<Name>GKLab Windows Automatic Service Monitoring</Name> 8<References> 9<Reference Alias="SC">10<ID>Microsoft.SystemCenter.Library</ID>11<Version>6.1.7221.0</Version>12<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>13</Reference>14<Reference Alias="Windows">15<ID>Microsoft.Windows.Library</ID>16<Version>6.1.7221.0</Version>17<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>18</Reference>19<Reference Alias="Health">20<ID>System.Health.Library</ID>21<Version>6.1.7221.0</Version>22<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>23</Reference>24<Reference Alias="System">25<ID>System.Library</ID>26<Version>6.1.7221.0</Version>27<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>28</Reference>29<Reference Alias="Performance">30<ID>System.Performance.Library</ID>31<Version>6.1.7221.0</Version>32<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>33</Reference>34</References>35</Manifest>

    Step 2:

    Now create a Powershell property bag probe script. The Powershell script fetches list for all services that are set to start automatic and checks for the current status. For each service that are set to Automatic but not running, a property bag is created.

    To exclude some services from being monitored, a centrally located CSV file is used and the path of file is passed as parameter to the script. The script reads list of services to be excluded from monitoring from CSV file and compares it with the list of services in the target computer. The property bag for excludes services are not created.

    1param ( 2 [string] $excludeservicelist 3) 4if (test-path $excludeservicelist) { 5write-eventlog -logname "Operations Manager"-Source "Health Service Script"-EventID 776-Message "WindowsAutomaticServiceMonitoring.ps1 - Accessing Exclusion List CSV"-EntryType Information 6$contents= Import-Csv $excludeservicelist 7} 8$TargetComputer= hostname 9$api= New-Object -comObject 'MOM.ScriptAPI'10$auto_services= Get-WmiObject -Class Win32_Service -Filter"StartMode='Auto'"11foreach ($servicein$auto_services)12{13$isExcluded=014$state=$service.state15$name=$service.DisplayName16If ($Contents){17$contents|ForEach-Object{18$ExcludeServiceDisplayName=$_.ServiceToExclude19$ExcludeComputerName=$_.ComputersToExclude20if (($name-match$ExcludeServiceDisplayName) -and (($TargetComputer-match$ExcludeComputerName) -or ($ExcludeComputerName-match"ALL_COMPUTERS"))){21$isExcluded=122#write-eventlog -logname "Operations Manager" -Source "Health Service Script" -EventID 777 -Message "WindowsAutomaticServiceMonitoring.ps1 - Excluded Service Name - $ExcludeServiceDisplayName, Excluded Computer Name - $ExcludeComputerName" -EntryType Information23 }24 }25 }26if (($isExcluded-eq0) -and ($state-eq"Stopped")){27#write-eventlog -logname "Operations Manager" -Source "Health Service Script" -EventID 778 -Message "WindowsAutomaticServiceMonitoring.ps1 - Windows Service set to Automatic but Not Running - $name" -EntryType Information28$bag=$api.CreatePropertyBag() 29$bag.AddValue("ServiceName", $name)30$bag.AddValue("Status", $state)31$bag32 }33}
    Step 3:

    Create a data source module incorporating the above written Powershell script. We will use consolidator condition as discussed in solution part to alert only on valid service failures.

    1<TypeDefinitions> 2<ModuleTypes> 3<DataSourceModuleType ID="GKLab.Windows.Auto.Service.Monitoring.DataSource" Accessibility="Internal" Batching="false"> 4<Configuration> 5<xsd:element minOccurs="1" name="ExcludeServiceList" type="xsd:string"/> 6<xsd:element minOccurs="1" name="IntervalSeconds" type="xsd:integer"/> 7<xsd:element minOccurs="1" name="ConsolidationInterval" type="xsd:integer"/> 8<xsd:element minOccurs="1" name="Count" type="xsd:integer"/> 9</Configuration>10<OverrideableParameters>11<OverrideableParameter ID="IntervalSeconds" Selector="$Config/IntervalSeconds$" ParameterType="int"/>12<OverrideableParameter ID="Count" Selector="$Config/Count$" ParameterType="int"/>13<OverrideableParameter ID="ConsolidationInterval" Selector="$Config/ConsolidationInterval$" ParameterType="int"/>14</OverrideableParameters>15<ModuleImplementation Isolation="Any">16<Composite>17<MemberModules>18<DataSource ID="Trigger" TypeID="System!System.SimpleScheduler">19<IntervalSeconds>$Config/IntervalSeconds$</IntervalSeconds>20<SyncTime>00:00</SyncTime>21</DataSource>22<ProbeAction ID="Probe" TypeID="Windows!Microsoft.Windows.PowerShellPropertyBagProbe">23<ScriptName>WindowsAutomaticServicesMonitoring.ps1</ScriptName>24<ScriptBody><![CDATA[25param (26 [string] $excludeservicelist27)28if (test-path $excludeservicelist) {29write-eventlog -logname "Operations Manager" -Source "Health Service Script" -EventID 776 -Message "WindowsAutomaticServiceMonitoring.ps1 - Accessing Exclusion List CSV" -EntryType Information30 $contents = Import-Csv $excludeservicelist31}32$TargetComputer = hostname33$api = New-Object -comObject 'MOM.ScriptAPI'34$auto_services = Get-WmiObject -Class Win32_Service -Filter "StartMode='Auto'"35foreach ($service in $auto_services)36{37 $isExcluded = 038 $state = $service.state39 $name = $service.DisplayName40 If ($Contents){41 $contents | ForEach-Object{42 $ExcludeServiceDisplayName = $_.ServiceToExclude43 $ExcludeComputerName = $_.ComputersToExclude44 if (($name -match $ExcludeServiceDisplayName) -and (($TargetComputer -match $ExcludeComputerName) -or ($ExcludeComputerName -match "ALL_COMPUTERS"))){45 $isExcluded = 146 write-eventlog -logname "Operations Manager" -Source "Health Service Script" -EventID 777 -Message "WindowsAutomaticServiceMonitoring.ps1 - Excluded Service Name - $ExcludeServiceDisplayName, Excluded Computer Name - $ExcludeComputerName" -EntryType Information47 }48 }49 }50 if (($isExcluded -eq 0) -and ($state -eq "Stopped")){51 write-eventlog -logname "Operations Manager" -Source "Health Service Script" -EventID 778 -Message "WindowsAutomaticServiceMonitoring.ps1 - Windows Service set to Automatic but Not Running - $name" -EntryType Information52 $bag = $api.CreatePropertyBag() 53 $bag.AddValue("ServiceName", $name)54 $bag.AddValue("Status", $state)55 $bag56 }57}58]]></ScriptBody>59<Parameters>60<Parameter>61<Name>ExcludeServiceList</Name>62<Value>$Config/ExcludeServiceList$</Value>63</Parameter>64</Parameters>65<TimeoutSeconds>300</TimeoutSeconds>66</ProbeAction>67<ConditionDetection ID="Consolidator" TypeID="System!System.ConsolidatorCondition">68<Consolidator>69<ConsolidationProperties>70<PropertyXPathQuery>$Target/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</PropertyXPathQuery>71<PropertyXPathQuery>Property[@Name='ServiceName']</PropertyXPathQuery>72</ConsolidationProperties>73<TimeControl>74<WithinTimeSchedule>75<Interval>$Config/ConsolidationInterval$</Interval>76</WithinTimeSchedule>77</TimeControl>78<CountingCondition>79<Count>$Config/Count$</Count>80<CountMode>OnNewItemTestOutputRestart_OnTimerSlideByOne</CountMode>81</CountingCondition>82</Consolidator>83</ConditionDetection>84</MemberModules>85<Composition>86<Node ID="Consolidator">87<Node ID="Probe">88<Node ID="Trigger"/>89</Node>90</Node>91</Composition>92</Composite>93</ModuleImplementation>94<OutputType>System!System.ConsolidatorData</OutputType>95</DataSourceModuleType>96</ModuleTypes>97</TypeDefinitions>

    Step 4:

    Next we will create a rule using the data source. Below configuration needs to be customized according to the need.

    ExcludeServiceList – the UNC path for the excluded services list file (in CSV format). Sample CSV provided below.

    CSV has two headers- “ServiceToExclude” which is display name of service.

    ComputersToExclude – NetBIOS Name of computer. If two or more computers, it can be specified as individual entry or using regular expression syntax. If need to exclude in all computers, the value should be “ALL_Computers”

    1ServiceToExclude,ComputersToExclude2Distributed Transaction Coordinator,SCOM2012R23Windows Audio,Win2k12-DC4Remote Registry,ALL_Computers5Software Protection,SCOM2012R2|Win2k12-DC

    IntervalSeconds – Polling Interval in Seconds

    Count – Number of polls, the service should fail to alert. (Minimum 2)

    ConsolidationInterval – The interval time within which the service status fails ‘n’ number of times to generate alert.  (Minimum value = (n-1) * IntervalSeconds where n = count)

    1<Monitoring> 2<Rules> 3<Rule ID="GKLab.Windows.AutomaticService.Monitoring.Rule" Enabled="true" Target="Windows!Microsoft.Windows.Computer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100"> 4<Category>Alert</Category> 5<DataSources> 6<DataSource ID="DS" TypeID="GKLab.Windows.Auto.Service.Monitoring.DataSource"> 7<ExcludeServiceList>\\SCOM2012R2\Configs\WindowsAutomaticServiceMonitoringExclusionList.csv</ExcludeServiceList> 8<IntervalSeconds>300</IntervalSeconds> 9<ConsolidationInterval>600</ConsolidationInterval>10<Count>2</Count>11</DataSource>12</DataSources>13<WriteActions>14<WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">15<Priority>1</Priority>16<Severity>2</Severity>17<AlertMessageId>$MPElement[Name="GKLab.Windows.AutomaticService.Monitoring.Rule.AlertMessage"]$</AlertMessageId>18<AlertParameters>19<AlertParameter1>$Data/Context/DataItem/Property[@Name='ServiceName']$</AlertParameter1>20</AlertParameters>21<Suppression>22<SuppressionValue>$Target/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</SuppressionValue>23<SuppressionValue>$Data/Context/DataItem/Property[@Name='ServiceName']$</SuppressionValue>24</Suppression>25</WriteAction>26</WriteActions>27</Rule>28</Rules>29</Monitoring>

    Step 5:

    Final step is to construct XML for presentation and language packs. Ensure the close the <ManagementPack> tag.

    1<Presentation> 2<StringResources> 3<StringResource ID="GKLab.Windows.AutomaticService.Monitoring.Rule.AlertMessage"/> 4</StringResources> 5</Presentation> 6<LanguagePacks> 7<LanguagePack ID="ENU" IsDefault="true"> 8<DisplayStrings> 9<DisplayString ElementID="GKLab.Windows.Automatic.Service.Monitoring">10<Name>GKLab Windows Automatic Service Monitoring</Name>11<Description>GKLab Windows Automatic Service Monitoring Management Pack</Description>12</DisplayString>13<DisplayString ElementID="GKLab.Windows.Auto.Service.Monitoring.DataSource">14<Name>GKLab Windows Automatic Service Monitoring Data Source</Name>15<Description>GKLab Windows Automatic Service Monitoring Data Source</Description>16</DisplayString>17<DisplayString ElementID="GKLab.Windows.AutomaticService.Monitoring.Rule">18<Name>Windows Automatic Services Monitoring Rule</Name>19<Description>Windows Automatic Services Monitoring Rule</Description>20</DisplayString>21<DisplayString ElementID="GKLab.Windows.AutomaticService.Monitoring.Rule" SubElementID="Alert">22<Name>Alert</Name>23</DisplayString>24<DisplayString ElementID="GKLab.Windows.AutomaticService.Monitoring.Rule" SubElementID="DS">25<Name>GKLab Windows Automatic Service Monitoring Data Source</Name>26</DisplayString>27<DisplayString ElementID="GKLab.Windows.AutomaticService.Monitoring.Rule.AlertMessage">28<Name>Windows Automatic Services Monitoring Alert</Name>29<Description>Windows Service {0} is set to auto-start but is currently not running.</Description>30</DisplayString>31</DisplayStrings>32</LanguagePack>33</LanguagePacks>34</ManagementPack>

    Step 7:

    Deploy the MP in lab and check for alerts.

    image

     

    I have attached copy of XML which you can import in to any authoring tool. Customize as per your needs and have fun.

    Happy SCOMing…


    0 0
  • 02/01/16--03:18: COSN Platform Best Practices
  • I've already shared some high-level best practices regarding Cloud OS Network Platform in my previous posts. Today I'll continue sharing my knowledge about building IaaS cloud services based on Hyper-V, System Center and Azure Pack for hosting service providers and big enterprises. Here are my best practices regarding IaaS for Cloud OS Network Platform.

    Common best practices

    1. Don't forget to configure automatic Windows Server activation. I've already shared some best practices in a previous post.
    2. Use the same Update Rollup version for all COSN Platform components. Using different versions of URs for VMM, SPF and WAP is not supported and will cause a lot of troubles. Don't forget to update SCOM agents to the newest UR.
    3. Use high-availability deployment options for all COSN Platform components. Eliminate single point of failure.
    4. Change HTTPS services port from service default to 443. As example, SPF service uses 8090 port by default, Azure Pack components also use non-standard HTTPS ports after installation.
    5. Use Enterprise CA certificates for internal services and Public CA issued certificates for services, accessible by tenants. Don't use self-signed certificates.
    6. Use dedicated VM with all Windows Server and System Center consoles installed to manage COSN Platform. Enable remote management for IIS across COSN Platform components.
    7. Add #WAPWiki to your favorites. This is a very useful resource.

    Management Active Directory

    1. Use naming conventions for user accounts, service account and computer accounts.
    2. Provide full descriptions for service accounts
    3. Don't add users to Domain Admins if it is absolutely unnecessary. Use rights delegations of local admin rights instead.
    4. Create separate security groups for service access. Configure service to assign access to groups instead of users.
    5. Use Group Managed Service Accounts (gMSAs) instead of traditional user accounts for services. It will increase security by automatically leveraging password management for service account. But be sure that the service itslef supports gMSAs. As example, SQL Server 2014 supports them.
    6. If you run domain controller with PDC role inside a Hyper-V VM, disable "Time Synchronization" in Integration Services tab in the VM settings. Otherwise hosts will try to get time from PDC, and your PDC will try to get time from the underlying host. You'll go into chicken and egg problem and time will not be actual across the whole management domain.
    7. Always configure time synchronization with an external source on a domain controller with PDC role. As example, just run this command on DC with PDC role and restart the server:
      w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:MANUAL
      Stop-Service w32time
      Start-Service w32time

    Hyper-V Hosts and Clusters

    1. Don't enable NUMA Spanning in Hyper-V Settings of the host unless it is unnecessary. NUMA Spanning can potentially increase the VM density, but it decreases the CPU performance.
    2. Don't use checkpoints for management VMs unless unnecessary. Checkpoint decrease virtual disk performance and consume more storage.
    3. Use the same version of network adapter drivers across Hyper-V cluster.
    4. Don't enable CPU compatibility mode for VMs if you use hosts with the same CPU family in the cluster. CPU Compatibility can potentially decrease CPU performance because not all available CPU instructions will be used. Details are available here.
    5. Run cluster validation tests every month and check the results.
    6. Check the consistency of software updates every month.
    7. No need to use a dedicated network adapter for Live Migration traffic. You can use Cluster network for this.
    8. Exclude unneeded and unstable network adapters from cluster use.
    9. To achieve high availability, use multiple similar network adapters and use NIC Teaming in "Dynamic" mode.
    10. Separate hosts which run NVGRE Gateways and hosts that run VMs, which use NVGRE Network Virtualization. Collocation of them is not supported.
    11. Tune VMQ properly.
    12. If you use 10GbE network, check that Live Migration don't uses "Compression" mode.
    13. Install all available hotfixes for failover clustering from this article.
    14. Install all available hotfixes from this article if you use NVGRE.

    Storage

    1. Hyper-V host must be able to see only that LUNs, that they will use for CSV. Configure zoning and masking properly.
    2. Connect one LUN to several hosts only if they are connected into the same cluster. Otherwise there will be no write master, hosts will try to write simultaneously and file system will corrupted very soon.
    3. Prefer formatting disks in GPT instead of MBR.
    4. Use 64k cluster size.
    5. Prefer vendor MPIO DSM instead of Microsoft default DSM.
    6. Use storage classification functionality for storage disks, clouds and VM Images.
    7. If you are using SMB to store VMs, specify FQDN instead of flat name in share URL. \\fs01.contoso.com\VMs instead of \\fs01\VMs. VMM doesn't like flat names for network shares.
    8. Install all available hotfixes for File Services on SOFSs and VMM Library Servers from this article.
    9. If you use Storage Spaces:
      1. Read this post
      2. Apply the recommended registry changes
      3. Disable TRIM and Physical Disk cache
      4. Specify "-UseLargeFRS" option when formatting drives.
      5. Use "Least Blocks" MPIO Global policy and "Round Robin" MPIO policy for SSDs.

    Virtual Machine Manager

    1. VMM Service is very important for COSN Platform. Use at least 2 VMM instances in a cluster.
    2. Add all used networks as Logical Networks. Define subnets and IP pools for every network.
    3. Use proper isolation types for Logical Networks. All management logical networks should use "One Connected Network" isolation. NVGRE-based Logical networks for tenants must use "Hyper-V Network Virtualization Isolation". If you use traditional VLANs for tenants instead, create new sites with different VLANs in the same Logical Network with "VLAN-based Isolation". Details are here.
    4. On every Hyper-V host check in host's Hardware Settings that every physical network adapter is mapped to a proper Logical Network.
    5. On every Hyper-V host check in in host's Hardware Settings that local system drives are not available for new VM placement (uncheck "Available for Placement" checkmark).
    6. If you use NVGRE, then consider using at least /22 IP Pool for PA Network. Otherwise you will be out of available PA IP addresses very soon.
    7. Always add file shares and libraries using FQDN instead of flat names.
    8. Check that all shares have correct permissions. Should be no errors in VMM.
    9. Use traditional clustered File Server for highly available VMM Library. SOFS is not recommended for this.
    10. Scope Libraries to proper Host Groups, Networks and Clouds.
    11. Store HNV Gateway Service template in the VMM Library. You will need to create additional network services.
    12. Use Availability Sets for VMs with guest clustering and NLB. This will create anti-affinity rules for you and place VMs with guest clustering on different hosts.
    13. Use different RunAs Accounts for different purposes. Assign only needed rights to these accounts.
    14. In some conditions host refresher goes into Legacy Mode (instead of default "Event Based" mode). Check refresher mode periodically and revert refresher mode back to Event Based mode.
    15. Configure Bare Metal Deployment  to reinstall faulty hosts and add new hosts quickly.
    16. Deploy different HNV gateways from the same service template.
    17. Don’t miss important parameters in network service connection string (BackendSwitch, MpDiscovery and MpDiscoveryIpAddress).

    SQL Server

    1. Don't use Dynamic Memory for VMs with SQL Server. Here is a good explanation.
    2. COSN Platform supports SQL Server 2012 and SQL Server 2014. You can use any of them, but don't forget to install latest cumulative updates.
    3. Never install SQL Server in a standalone mode. SQL Server is a core, VMM and WAP won't work without SQL Server connection. Use AlwaysOn Failover Clustering or AlwaysOn Availability Groups for high availability. Or both.
    4. Don't collocate all DBs in the same instance. Use a dedicated VM for SCOM DW at least.
    5. Use separate domain service accounts for SQL Server service and SQL Server agent.
    6. Use gMSA if you use SQL Server 2014 or newer.
    7. Use separate disks for system, database files and log files.

    Azure Pack

    1. Don't collocate all Azure Pack components in the same VM. Use Minimal distributed deployment or Scaled distributed deployment architecture, explained here.
    2. Don’t forget to update Azure Pack database to the same UR version after all Azure Pack components update.
    3. Reconfigure portal names and ports like described here. Use port 443 for HTTPS instead of defaults.
    4. If Microsoft NLB doesn't suit your needs, you can use virtual network load balancers instead.  KEMP VLM and Citrix NetScaler VPX work OK with Azure Pack services.
    5. By default, Azure Pack sends user password in clear text after password change initiated by the tenant. It's a good idea to delete this field in Notification Settings in Azure Pack admin portal - password should not be stored in users inbox.

    VM Templates

    1. Update Hyper-V integration services for Windows and Linux to the latest available version.
    2. Use this manual for CentOS VM template creation.
    3. Don't use Dynamic Memory for templates. You can't predict which workloads tenants will install into their VMs, that will be deployed using these templates. Some workloads like Exchange or SQL Server Standard don't support Dynamic Memory.
    4. Tenants sometimes confused because they need to hit CTRL+ALT+END instead of CTRL+ALT+DEL when connect via console to their Windows Server based them. To eliminate this confusion, disable CTRL+ALT+DEL requirement on the logon screen.
    5. You can't disable Secure Boot option for Generation 2 VM Roles. Linux distros don't support Secure Boot on Hyper-V 2012 R2. So don't use Generation 2 VM Roles if you need Linux. But there is no such issue with Standalone VMs - you can disable Secure Boot manually in VM template settings in VMM.

    But remember - all these recommendations are not official statements by Microsoft. I share these best practices based on my personal experience, achieved in 10+ deployments of COSN Platform in different service providers from different countries. So no warranties :)


    0 0

    В феврале 2015 года мы анонсировалипартнерскую программу Cloud Storage (CSPP) и предоставили поставщикам облачных хранилищ возможность подключать свои сервисы к Office Online и Office для iOS. Сегодня  Office стал еще проще в использовании благодаря добавлению соавторства в реальном времени над документами Office Online, хранящимися на партнерских облачных сервисах, расширении интеграции Office для iOS на всех партнеров CSPP, а также предоставлении возможности интеграции Outlook.com с такими провайдерам облачных хранилищ как Dropbox и Box.

    ...(read more)

    0 0

    V předchozím článcích o produktu Power BI jsem se věnoval, vymezení produktu a jeho využití na analýzu dat z Facebookového účtu. V dnešním článku chci ukázat, že tento nástroj lze využít i mimo počítačové předměty a to konkrétně ve veřejné správě téma demografie.

                    Ukázka byla vytvořena za pomoci studentů 1. ročníku zaměření informatika a reálně používaná při výuce v oboru veřejná správa. Cílem analýza počtu obyvatel v závislosti na místě bydliště za rok 2014 v okrese Klatovy.

    Veškerá data jsme čerpali z Českého statistického úřadu, část databáze demografických údajů za obce ČR https://www.czso.cz/csu/czso/databaze-demografickych-udaju-za-obce-cr

    Jsou zde dvě sekce Územní změny, počty obyvatel, narození, zemřelí, stěhování (1971-2014) a Sňatky, rozvody, potraty (1991-2014). Žákyně se setkaly poprvé s tak velkými objemy dat a musely se s nimi „poprat“. Když jsme příslušné tabulky stáhli a porovnali, bylo jasné, že data sobě přímo neodpovídají a bude třeba provést redukci dat. Další problém, před kterým tým stál, byly GPS souřadnice obcí v ČR; nakonec se po několika pokusech podařilo i tyto údaje najít. Celkem byly k dispozici 3 tabulky, které bylo nutné sloučit, aby byla data adekvátní.

    Pro zpracování dat byl použit nový nástroj od firmy Microsoft pro analýzu dat, a to PowerBi ve verzi Desktop a posléze verze On-line. Aplikace PowerBi nám velice usnadnila práci se zpracováním vkládaných údajů. Z relačního modelu je patrné, že spojovacím klíčem mezi tabulkami byl kód obce, který byl jednoznačným identifikátorem.

    Celý model je tvořen již zmíněnými třemi tabulkami, a to List1 (zde jsou právě GPS souřadnice obcí), CZ0322 (údaje za sňatky, rozvody, potraty) a CZ0322(2) (za územní změny, počty obyvatel, narození, zemřelí, stěhování).

    V aplikaci  PowerBI Desktop v části sestava byla po naimportování dat, jejich vyčištění a přípravě vytvořena sestava výstupních dat včetně vizualizace.

    Data jsme vizuálně rozdělili do tří provázaných částí, a to mapa, tabulka a celkový graf. Princip je takový, že na mapě vyberete vámi požadovanou obec a v pravé části se vám k dané obci zobrazí příslušná data. Pokud jsou data dostatečně objemná, je jejich počet vidět i v celkovém grafu. Například u obce Klatovy, viz obrázek. Pokud se žádná obec na mapě nevybere, jsou vidět data za celý okres Klatovy v roce 2014.

     

     

     

    Poté, co jsme tyto výstupy připravili v desktopové verzi, bylo potřeba je importovat do cloudového prostředí a sdílet. Zde jsme narazili na problém. Vzhledem k tomu, že jde o novou aplikaci, která se stále  vyvíjí, není možné publikovat data veřejně, ale pouze v rámci organizace. Data jsou přístupná na adrese https://app.powerbi.com/groups/me/dashboards/4f246413-9e70-4b40-b0df-6e96f12feb12 uživatel soutez@sszpkt.cz heslo Opendata2015.

    Karel Rejthar - MIE Expert

     


    0 0

    Sejam muito bem-vindos a mais um Domingo Surpresa.

    O uso de Containers é uma tendência crescente, com soluções como Docker ganhando mais espaço a cada dia. Utilizando de maneira mais racional recursos de infraestrutura, este tipo de tecnologia procura oferecer uma alternativa leve, segura e que torne mais simples o processo de deployment dos mais variados tipos de aplicações.



    Do ponto de vista prático, um Container nada mais é do que uma unidade isolada com todo o conteúdo necessário para a execução de uma aplicação. Uma das vantagens no uso deste tipo de estrutura é evitar todo o trabalho de instalação de sistemas operacionais e outros softwares para vários ambientes. Assim, múltiplos Containers podem ser executados em uma única máquina, compartilhando recursos do mesmo sistema operacional.

    Para saber mais sobre o uso de Containers e da tecnologia Docker acesse os links:

    Instalação do Docker-Engine em uma Máquina Virtual Ubuntu

    Windows Containers Quick Start – Docker

    Docker and Microsoft

    E por hoje é isso... Até a próxima!

       

    Wiki Ninja Renato Groffe (Wiki, Facebook, LinkedIn, MSDN)


    0 0

    Salut les amis Wiki Ninja Français communautaires.



    Bienvenue au lundi interviews.

    Parlons du processus d'entrevues.

    Le processus d'entrevue est un blog qui a lieu tous les lundis.

    L'objectif est d'être une façon de remercier et de récompenser nos meilleurs contributeurs à la communauté TechNet Wiki.

    La communauté française a un site qui centralise toutes les interviews communautaires.

    Visitez:

    Interview avec un 'Wiki Ninja' (fr-FR)


    Si vous souhaitez être interviewé ou référez quelqu'un visiter ce site très intéressant et laisser un commentaire.

    L'équipe communautaire sera surveille l'TechNet et si vous êtes sélectionné vous contactera.

    Nous remercions tous les répondants et des employés de la communauté française.

    Nous attendons les commentaires inquiets et nous aimerions connaître les nouveaux membres.

    Merci.


    Wiki Ninja @Hezequias Vasconcelos ++


    0 0

    We have new updates for Surface Pro 4 devices.

    Click the heading below to go to the specific location on the Download Center. At the Download Center, click Details then click + More to see all available downloads for the device. For all devices you can follow the similar deployment process that is used for Surface Pro 3 described at Surface TechCenter.

    DOWNLOAD

    Surface Pro 4

    SurfacePro4_Win10_160128_0.msi
    SurfacePro4_Win10_160128_0.zip

    Updates for Surface Pro 4 devices

    For Surface Pro 4 devices, updates will be posted at http://aka.ms/drivers/surfacepro4

    The following update will be listed as “System Firmware Update – 1/27/2016” when you view your update history.

    Note that Surface Pro 4 devices can only run Windows 10 operating system.

    Surface Embedded Controller Firmware (v103.899.256.0)

    • Adds battery charging enhancements and thermal tuning

    Surface Fingerprint Sensor driver update (v2.2.10.6)

    • Improves accuracy

    Wireless Network Controller and Bluetooth driver update (v15.68.9037.59)

    • Improves access point compatibility and throughput on 5GHz networks

    As always, these updates may also be made available via the Windows Update service. When Surface updates are provided via the Windows Update service, they are delivered in stages to Surface customers. As a result, not every Surface will receive the update at the same time, but the update will be delivered to all devices.

    Thanks,

    Surface IT Pro Marketing team


    0 0

    Hi folks, it's me, Heyko and I'm a Premier Field Engineer for Virtualization in Germany. A few days ago a customer asked me if it is possible to pre-seed a Hyper-V VM Backup in Data Protection Manager 2012 R2.

    First of all a few words about Data Protection Manager. System Center Data Protection Manager or short SCDPM or just DPM is Microsoft's Enterprise grade backup solution. It enables you to backup several enterprise workloads such as SQL Server, SharePoint, Exchange, Hyper-V and a lot more.

    One of the key differences between DPM and other backup solutions is that there is only one initial full backup and than DPM keeps this backup in sync and creates snapshots aka recovery points to allow you to restore data from a selected date/time. This allows you to create backups from servers in branch offices connected with a weak WAN link only.

    It might be helpful or necessary to think about a manual synchronization/offline transportation instead of an initial replication via a weak WAN link, because the initial backup via a weak WAN link could take days or weeks to complete.

    Today I'll show you a way how to transfer a Hyper-V VM e.g. with an external harddisk.

     

    The first step is to create a new Protection Group or add a new VM to this Protection Group

    clip_image002

     

    On page "Choose replica creation method" you choose "Manually".

    clip_image004

     

    After successful creation you can see the VM with Protection Status "Manual replica creation pending"

    clip_image006

     

    Now you select "Click to view details" to see the Destination Path for the VM Data on the DPM Machine and select the Destination Path and copy it to a notepad or something else.

    clip_image008

    The copied path should look like the following:

    c:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VSS Writer\vol_fec96cc7-9308-47da-95ac-efb18e44e96e\e3d3a7e8-b88c-4b04-bb40-9f7a2dbc8d8b\Full\C-Vol\

    The GUIDs can differ in each case. The last part in my case C-Vol determines that C:\ is the volume where the VM-Files are. It could be C-Vol\ClusterStorage or other Volumes, too.

    Now you switch to the backup target and copy the VM related files from there to an external harddisk or something else. The VM should be powered off first. You can copy all VM files but in most cases it's enough to take the VHD or VHDX files because these are the biggest ones.

     

    The next step is to copy the data from the backup target into the Volume on the DPM machine. For the following steps you should log in with the local Administrator Account on the DPM Server.

    You can join the target directory on the DPM Server with an elevated Command Prompt or the Windows Explorer:

    clip_image010

    clip_image012

    It’s important to keep the current folder structure.

    In my case i need the following directories and files:

    · C:\Hyper-V\  >>  ...\Full\C-Vol\Hyper-V\..

    · C:\VMMDisks\  >>  ...\Full\C-Vol\VMMDisks\..

    On the left is the path on the backup source and the right hand side shows the path on the DPM server.

     

    The next and final step is starting the Consistency Check on the DPM Machine:

    clip_image014

    Some seconds/minutes later the Consistency Check is finished and you can check the VHDX file:

    clip_image016

    And you'll see that the VHDX File hasn't been touched. If the VM is up and running during the transportation there will be an update of this file.


    0 0

    Друзья, мы хотим познакомить вас с полезным решением нашего партнера, компании inCOMa, которое позволяет добавлять в Project готовые настроенные блоки работ.

    ...(read more)

    0 0

    By Richard Smith
    General Manager, Microsoft World Wide Licensing & Pricing (WWLP)

    Today, we’re announcing another significant step in the transformation of Microsoft volume licensing to make it easier for customers and partners to do business with us.

    Beginning on July 1, 2016, the minimum Enterprise Agreement (EA) commitment for commercial customers signing new Enterprise Enrollments or Enterprise Subscription Enrollments will increase from 250 users or devices to 500. Along with this change, we are guiding new commercial customers within the 250 to 499 user or device range to our modern volume licensing solutions: the Microsoft Product and Services Agreement (MPSA) and the Cloud Solutions Provider (CSP).

    Together, these announcements reflect the underlying transformation in what customers buy and how they buy it. First, customers are increasingly harnessing our cloud and hybrid solutions, and second, our modern programs of MPSA and CSP, purpose-built for these developments, are rapidly being embraced because they deliver the simpler, more flexible licensing our customers and partners tell us they want.

    Microsoft Products and Services Agreement (MPSA).MPSA is the fastest and most flexible way to buy all the software and cloud services you need through one simplified agreement.

      • You can create a purchasing structure that reflects your organization’s structure, yet optimize pricing across your MPSA.

      • One-, two-, and three-year durations for many online services deliver budget predictability and the flexibility to purchase what you need when you need it. We’ll also soon add short-term subscription durations (one to 11 months) to help you address seasonal and project-based needs.

      • There are no minimum requirements to start buying cloud services. You can begin with exactly as much as you need for your organization, and you’ll get price protection on any incremental purchases you buy during the term of the subscription.

    Cloud Solution Provider (CSP). For customers seeking to fully outsource management of their cloud services, CSP offers an easy way to license what you need in combination with the value-added services offered by your systems integrator, hoster, or born-in-the-cloud reseller partner.

      • There are thousands of CSP partners worldwide with the technical expertise to help you take full advantage of Microsoft cloud technologies — even if you have no in-house IT department.

      • You can fully leverage these partners to handle ordering, provisioning, management, and support for Microsoft cloud services.

      • For Office 365 and Microsoft Dynamics Online, your partner can purchase a subscription and add and modify seats mid-term. For Azure, you pay for what you use, in arrears. There are no minimum requirements to start buying cloud services.

    At the expiration of their current EA term, existing commercial customers with fewer than 500 users or devices can choose to transition to MPSA or CSP, or they can renew their EA by extending it for one additional 36-month period. The extension option is recommended for customers whose unique needs are not yet supported by MPSA or CSP, as well as for customers who simply prefer to continue with the EA.

    Please note that the change to the minimum commitment does not impact EA customers with greater than 500 users or devices, Public Sector customers, or the Server and Cloud Enrollment (SCE).

    Start preparing for the change today

    While changes do not go into effect until July 1, 2016, customers can start planning ahead today. Commercial EA customers with fewer than 500 users or devices should contact their partner or sales executive to learn more, and visit our online resources for EA, MPSA, and CSP. For updates, real-time information and direct engagement, please follow us on Twitter.

    Today’s announcement is an important milestone in how we are bringing a faster, more flexible licensing experience to our customers. Stay tuned to this blog for more updates as we continue our journey toward transforming licensing at Microsoft.


     


    0 0

    Politics. Hockey. The economy. Weather. Flagging trends in the coming year is always a fun thing to do and it gives us a chance to a step back from the day-to-day grind to consider the all-important big picture. So, let’s take five minutes to talk business tech in Canada with an eye to identifying some of the milestones that may influence our industry in 2016.

    1. Digital security sparks more cloud interest

    Trend: Cyber threats and hacks will likely continue to make big headlines in 2016 and cause even more concern amongst Canadian business owners. This concern should prompt more stories, interest, inquiries and conversations about how the cloud can help safeguard businesses.

    Consider: Getting cloud-focused. Offer your existing customers a cloud migration strategy focused on safeguarding their business. Create crisp presentations, scripts and other assets about digital security to empower your team to speak authoritatively on this subject.

    2. Mobile adoption reaches the tipping point

    Trend: In 2016, mobile devices will probably account for over half of Canada’s web time. The steady adoption of mobile devices in Canada will continue, people will spend more time on their phones and tablets than they do on PCs and they’ll use phones to make more purchases, too.

    Consider: Mobilizing! If you lack mobile expertise and competencies, get some training, partner or hire to fill the gap. And make sure your website is responsive – meaning, that it looks good and works properly on any device, including mainstream phones and tablets.

    3. Canadian businesses look to cut costs

    Trend: Faced with economic uncertainty and a weak dollar, many Canadian business owners will likely look to cut costs in 2016. As they zero in operations, they may second-guess the value of in-house IT staff (if they have any), licenses and even tech vendor relationships.

    Consider: Positioning the cloud as a cost-cutter? Instead of maintaining (or worse, defending) out-of-date tech, why not propose upgrades that help your customers reduce costs by taking advantage of the cloud? They may be more receptive to modernizing if it can save them money.

     4. Bigger, smarter data demands

    Trend: As our economy continues to digitize, the sheer volume of data we create and a desire to make sense of it all will grow. In 2016, you will likely hear more leaders in our private and public sector talk about big data analysis as a solution for everything from traffic to terrorism.

    Consider: Strengthening your analytics capacity through training and certification, partnership or hiring. Buffing up your technical depth will enable you to provide higher-value, innovative solutions in advanced workloads, like IoT, advanced analytics and machine learning.

    5. The rise of Windows 10

    Trend: As the free upgrade offers draws to a close in the summer of 2016, more Canadian organizations and consumers will seize the opportunity to make the leap to Windows 10. By the end of the year, Windows 10 may be installed hundreds of millions of devices worldwide.

    Consider: Adopting and evangelizing Windows 10. If you have not yet upgraded internally, go for it! Consider developing Windows 10 app-building capabilities to capitalize on this growth. And, above all, encourage your customers to migrate before the offer ends.

    So, what do you think? Do you agree, disagree or have some trends of your own to share? I’d love to hear them! Feel free to share your thoughts in the comments below.

    Happy New Year!

    Jason

    Channel Chief @ Microsoft Canada

    @jbrommet


    0 0

    Today’s Tip…

    In-Memory OLTP with extended T-SQL surface area is now in public preview in Azure SQL Database. With In-Memory OLTP, a significantly larger number of applications are able to improve transaction performance and go up to 30 times faster, plus benefit from increased concurrency. To complement these enhancements, we’ve also introduced our in-memory columnstore that delivers queries up to 100 times faster, for real-time operational analytics on top of the accelerated transaction performance provided by In-Memory OLTP. For more information, please visit the In-Memory in Azure SQL Database documentation webpage.


older | 1 | .... | 829 | 830 | (Page 831) | 832 | 833 | .... | 889 | newer