This is a fun little story today, but I got to see first hand how our security management pack works during a real, non-simulated attack.  I was pleasantly surprised by the results.  For the record I keep a couple of labs.  One is internal, blocked from the world, and I spend most of my time in that lab.  I recently started up a lab in Azure as Azure is a bit of an internal requirement right now given that it’s kind of a big deal in the IT world.  Because of that, I multi-purposed that lab to be a SCOM 2016 environment as well as a second test environment.  Given time constraints as well as genuine curiosity, I did not put much effort into securing the lab.  It would serve as a nice little honey pot to see if I could detect the bad guys, and as it happened, it worked.  

I posted a screenshot from this lab in this piece about a month ago.  I specifically noted the failed RDP logons and why it is a bad idea to expose RDP to the world.  My guess, as of this writing, is that this is how the attacker got in.  Our management pack lit up almost immediately:

As you can see from the screen shot, this was likely nothing more than a script kiddie, but when you leave RDP exposed to the world, you make it very easy for them to get in, and they succeeded.  In this particular case, it would be what I call a lazy attacker.  I had AppLocker audit rules configured for hash based versions of Mimikatz.  My attacker, considering him or herself clever, had simply renamed Mimikatz to “Chrome” and put it in a program files directory called “google”.  Due to this, AppLocker did its thing.  This won’t catch a pro, as they recompile their tools to have different signatures so as to avoid AV detection.  As such, I wouldn’t rely on those and call myself secure, but as you can see from the screen shot, this was not the only thing we picked up.  They also created scheduled tasks to launch their malware and started a few services on my domain controller.  These checks are a bit better, as even the pros do this.  With a good alert management process in place, a security team can confirm that the operations team was not involved in this allow for a response while the attack is occurring, potentially stopping an attacker before there is data loss.

At this point, we will be doing some forensics to see what else they did or did not do.  The Azure security team was also on top of this and stopped the attack in its tracks, so it will be interesting to see what I didn’t detect.  Hopefully, we will come away with a few more nuggets to watch.

日本マイクロソフトが 5 月 23 日 (火)～ 24 日 (水) に開催した、IT エンジニア向けイベント「de:code 2017」では、Kinect や HoloLens の父 アレックス・キップマンや、Build を機にディベロッパー エバンジェリズムから Microsoft AI & Research に転籍したスティーブ・グッケンハイマーが来日し、複合現実 (Mixed Reality、MR) と人工知能 (AI) 特に深層学習 (Deep Learning) が大きな 2 つのテーマとなりました。

de:code 2017 の Keynote では、マイクロソフトがすでに Bing や Office 365 などの製品の中にもふんだんに取り込んで利用している人工知能を、開発者が如何に使ってビジネスの世界で人工知能を利用していくかを大きく取り上げています。Build でも取り上げられた PowerPoint Translator のデモ、女子高生 Bot のりんなの新しいキャラ「りんお」で Bot の性格を変更するデモ、そして Preferred Networks との深層学習についてのグローバルな提携について触れられました。

続いて HoloLens のパートでは、22,000 人以上の開発者によって 7 万コンテンツが既に作成され、550 万時間起動されていること、そして HoloLens は世界のどこよりも日本が一番盛り上がっていることが紹介されました。事例として、医療分野で手術への応用を勧める HoloEyes 社や日本の小柳建設の例が紹介され、今後の MR の方向性やビジョンが解説されました。

より詳しい情報については、Keynote が動画として公開されていたり、関連記事が多数出ていますので、興味のあるところを掘り下げてご覧いただくことをお勧めします。

より詳細な情報

以下に主な記事やニュースをまとめました。

• 2017/5/22: STYLYがゴーグルありきのファッションを提唱！Microsoftイベント「de:code」にも出展 (PANORA)
• 2017/5/22: 『ドローンワーキンググループ』を立ち上げ— 「IoTビジネス共創ラボ」でドローン市場の活用を促進 — (ValuePress)
• 2017/5/22: Psychic VR Lab、ファッションレーベル「chloma」と共同でVR/MRが普及した近未来のためのコレクション『chloma x STYLY HMD Collection (REAL⇄MR⇄VR)』を発表 (VRInside)
• 2017/5/23: AI重視の戦略にシフトするMicrosoft。開発者向けイベント「de:code 2017」でAI活用による技術革新を訴求 (PC Watch)
• 2017/5/23: 「日本の盛り上がりにびっくり」──HoloLensの父、アレックス・キップマン来日　開発現場の光景に「鳥肌が立つ」 (IT Media)
• 2017/5/23: 「日本が最もMRに取り組んでいる」HoloLens生みの親が語る次世代のコンピューティングと来日の理由 (MoguraVR)
• 2017/5/23: 「想定数をすでに超えた」──Acer、Windows Mixed Reality対応HMDを日本で予約スタート 価格は4万円、8月出荷目指す (ORICON News)
• 2017/5/23: gumi傘下のTokyo VR Startups、マイクロソフトとの協業を発表 「Microsoft BizSpark」を導入【de:code】 (PANORA)
• 2017/5/23: Acer、Windows Mixed Reality対応の複合現実HMD。4万円で開発者向け (AV Watch)
• 2017/5/23: 速報：日本では税込4万円、エイサーが開発者用Win MRヘッドセットの予約を楽天にて開始 (Engadget Japan)
• 2017/5/24: HoloLensの父、「MRこそがコンピューターの将来」と語る – 日本マイクロソフト「de:code 2017」基調講演から (マイナビ News)
• 2017/5/24: エイサー、Windows Mixed Reality対応ヘッドマウントディスプレイの予約開始 (価格.com News)
• 2017/5/24: PFNの深層学習ソフトをMSのクラウドで、両社が戦略的協業 (日経テクノロジー)
• 2017/5/24: PFNとの提携も発表！想像を超えるマイクロソフトのAIフォーカス (ASCII.JP)
• 2017/5/25: すべてのMS製品に”知性”を組み込む–「de:code 2017」基調講演 (ZDNet Japan)
• 2017/5/25: [de:code 2017]新製品、協業も発表、Microsoftが語る今後のAI戦略は? (マイナビNews)
• 2017/5/25: de:code 2017、Web上で手軽に使える本格AIサービスが多数登場 (マイナビ News)
• 2017/5/25: データが存在する場所に“知性”を。マイクロソフトがデータベースにAIを組み込む理由 (EnterpriseZine)
• 2017/5/26: AIが新たな特異点を生む――、マイクロソフトの開発者向けイベント「de:code 2017」レポート (クラウド Watch)
• 2017/5/26: AIの時代にはクラウドにOSを委ねるのではなく、クラウドがOSになり、PCがおしゃれになる (PC Watch)
• 2017/5/26: マイクロソフト、AIでOfficeを刷新 (Nikkei IT Pro)
• 2017/5/30: 【de:code 2017 #1】Hololensのスイートスポットは1.25mから5m！「本気で始める HoloLens – プラン・設計・開発の勘どころ -」セッションレポート (VR Inside)
• 2017/5/30:【de:code 2017 #2】「HoloLens – 真のエンジニアが知るべき実装」セッションレポート (VR Inside)
• 2017/5/30:【de:code 2017 #3】「クラウドと AI の力を組み合わせたMicrosoft HoloLens のさらなる可能性」セッションレポート (VR Inside)
• 2017/5/30: NVIDIAも初出展、1年前と様変わりした「de:code」展示会場 (ASCII.jp)
• 2017/5/30: de:code 2017: PWA、WebVR、Web Assembly……ウェブ最新技術の実装でGoogle、Mozilla、Microsoftが協調 (Internet Watch)
• 2017/5/30: de:code 2017: 最新バージョン「Edge 15」が大進化、応答速度3倍、高い電力効率を実現 (Internet Watch)
• 2017/5/30: “de:code 2017”レポート: Windows 10 Fall Creators Updateの新機能は開発者もうれしい (窓の杜 News)
• 2017/5/31: “de:code 2017”レポート: HoloLensの可能性と開発時の注意点などを解説 (窓の杜 News)
• 2017/5/31: “de:code 2017”レポート: すでに始まった“声”のビジネスを支える“Cortana” (窓の杜 News)
• 2017/6/01: 【de:code 2017】MR関連セッションレポートまとめ (VR Inside)
• 2017/6/01: de:code 2017基調講演（前編）：「インテリジェンス」はシステム開発とユーザー体験をどのように変えていくのか (@IT)
• 2017/6/01: “de:code 2017”レポート: HoloLensを装着したボディガードがエスコートする未来 (窓の杜 News)
• 2017/6/02: “de:code 2017”レポート: Windows 10はプログラムを異常終了させて発症や活動を抑止する (窓の杜 News)
• 2017/6/08: マイクロソフト、ITカンファレンス“de:code 2017”の基調講演の動画を公開 (窓の杜 News)
• 2017/6/08: de:code 2017基調講演（後編）：AI、Deep Learning、「Mixed Reality」で未来のコンピューティングはどう変わるのか (@IT)

以下が日本マイクロソフトおよびパートナー様からのプレスリリースです。

• アレックス キップマンが de:code 2017 に登場
• Preferred Networks とマイクロソフト、ディープラーニングソリューション分野で戦略的協業
• 小柳建設様と「Microsoft HoloLens」を活用したプロジェクト「Holostruction」の推進で連携
• 株式会社 gumi 様の VR/AR/MR 分野でのスタートアップのインキュベーションプログラムの強化支援について

ビデオ

日本語なので安心です。英語の部分は通訳付きです。

その他のビデオ

• Microsoft de:code 2017 – Channel 9

関連記事

• Microsoft Build 2017 のまとめ
• Microsoft de:code ブログ
• de:code 2017 in Tokyo, Japan (Steve “Guggs” Guggenheimer’s Blog) (英語)

This was originally created in 2011/2012 in a series I dubbed “SQL Tips” for my team (via email and an internal blog site). I’ve decided to add these SQL Tips to my external blog. These are being posted exactly how they were written ~6 years ago…unless I found someone’s name being called out…I may have edited that to protect the innocent.

Sometimes when you write a query to find some totals by a particular category you’d also like to see the grand total. If your query is being used in a reporting services report then this is easily achieved within the report. However, if you’re just writing a T-SQL query to find this data you’ll be interested in some ‘GROUP BY’ functions. In this SQL Tip we’ll look at the CUBE & ROLLUP functions.

SELECT  sit.SMS_Assigned_Sites0 AS [Assigned Site]
       ,COUNT(sis.ResourceID)   AS [Number of Clients]
  FROM dbo.v_R_System_valid sis
       INNER JOIN dbo.v_RA_System_SMSAssignedSites sit
          ON sis.ResourceID = sit.ResourceID
 GROUP BY sit.SMS_Assigned_Sites0;
GO

SELECT  sit.SMS_Assigned_Sites0 AS [Assigned Site]
       ,COUNT(sis.ResourceID)   AS [Number of Clients]
  FROM dbo.v_R_System_valid sis
       INNER JOIN dbo.v_RA_System_SMSAssignedSites sit
          ON sis.ResourceID = sit.ResourceID
 GROUP BY CUBE (sit.SMS_Assigned_Sites0); -- In this example "ROLLUP" would work exactly the same
GO

SELECT  sit.SMS_Assigned_Sites0 AS [Assigned Site]
       ,sis.Is_Virtual_Machine0
       ,COUNT(sis.ResourceID)   AS [Number of Clients]
  FROM dbo.v_R_System_valid sis
       INNER JOIN dbo.v_RA_System_SMSAssignedSites sit
          ON sis.ResourceID = sit.ResourceID
         AND sit.SMS_Assigned_Sites0 IN (N'EU1',N'RD2') -- Add this to show fewer records for the example
 GROUP BY  sit.SMS_Assigned_Sites0
          ,sis.Is_Virtual_Machine0;
GO

SELECT  sit.SMS_Assigned_Sites0 AS [Assigned Site]
       ,sis.Is_Virtual_Machine0
       ,COUNT(sis.ResourceID)   AS [Number of Clients]
  FROM dbo.v_R_System_valid sis
       INNER JOIN dbo.v_RA_System_SMSAssignedSites sit
          ON sis.ResourceID = sit.ResourceID
         AND sit.SMS_Assigned_Sites0 IN (N'EU1',N'RD2') -- Add this to show fewer records for the example
 GROUP BY CUBE ( sit.SMS_Assigned_Sites0
                ,sis.Is_Virtual_Machine0
                );
GO

SELECT  sit.SMS_Assigned_Sites0 AS [Assigned Site]
       ,sis.Is_Virtual_Machine0
       ,COUNT(sis.ResourceID)   AS [Number of Clients]
  FROM dbo.v_R_System_valid sis
       INNER JOIN dbo.v_RA_System_SMSAssignedSites sit
          ON sis.ResourceID = sit.ResourceID
         AND sit.SMS_Assigned_Sites0 IN (N'EU1',N'RD2') -- Add this to show fewer records for the example
 GROUP BY ROLLUP ( sit.SMS_Assigned_Sites0
                  ,sis.Is_Virtual_Machine0
                  );
GO

 GROUP BY  ROLLUP (sit.SMS_Assigned_Sites0)
          ,ROLLUP (sis.Is_Virtual_Machine0);
GO

Make the Most of Microsoft Inspire with our MSP Guide

With Microsoft Inspire just around the corner, now’s the perfect time to start planning your schedule. That’s why we created the Managed Service Provider Guide to Microsoft Inspire—a curated list of sessions, meetings, events, and networking opportunities you won’t want to miss. Visit our guide to…

• Pinpoint sessions that will help you grow your portfolio of managed services
• Find out where peers from around the world will congregate after show hours
• Learn how to schedule a meeting with the Microsoft MSP team, and much more

Visit the guide >

Plan your session agenda with MySchedule, your personalized show planner

As you browse the MSP guide, add sessions and meetings you want to attend to MySchedule, your personalized show planning tool. MySchedule shows you where you need to be every hour of the day—an invaluable way to ensure you don’t miss out on events you want to attend.
It’s easy to get started. Browse the MSP guide for a session you want to attend, click the link to the official event site, sign in, and then click the ‘Add Session’ button to add it to your schedule.

Visit the MSP guide to start planning your visit, and be sure to sign-up to receive important updates leading up to the event.

Microsoft’s Docs.com service to be discontinued

Microsoft is retiring the Docs.com service on Friday, December 15, 2017 and we are hereby advising all users to move their existing Docs.com content to other file storage and sharing platforms as soon as possible, as Docs.com will no longer be available after this date.

Following Microsoft’s acquisition of LinkedIn, SlideShare has joined the Microsoft family, and represents the ideal platform for publishing your Word, PowerPoint, and PDF content with its audience of 70 million professionals, and vast content library. For custom sharing, OneDrive offers additional tools, permission settings, and security to help share and protect your data and content. With the retirement of the Docs.com service, we hope to streamline our offerings in this space and provide you with a more cohesive experience.

We appreciate your patronage of our service and apologize for any inconvenience resulting from this transition. We are happy to provide automatic backup of compatible files to OneDrive and OneDrive for Business.

Please carefully read the information in this article to learn more about your options for transferring or deleting your existing Docs.com content and account.

I’m a current Docs.com user – what does this mean for me?

The Docs.com site and existing content stored on its servers will be retired according to the following schedule:

June 9, 2017 – Creating new Docs.com accounts will no longer be supported. If you have an existing Docs.com account, you will still be able to view, edit, publish, download, and delete your existing content. If you have existing Journal and About pages, you will be able to edit them on Sway.com.

June 19, 2017 – If you are using Docs.com with a Work or School account, your Office 365 Administrator can automatically migrate all Docs.com content to OneDrive for Business on your behalf. We will update this article with specific information on this date.

August 1, 2017 – Publishing and editing content on Docs.com will no longer be supported. If you have an existing Docs.com account, you will still be able to view or download your existing content.

June 9 to December 14, 2017 – If you have an existing Docs.com account, you can sign in and choose to have your own content backed up automatically to OneDrive. As soon as your data has been transferred there, your Docs.com experience will change to read-only and links to your documents and files will redirect to the new location on OneDrive.

December 15, 2017 – The Docs.com site and all of its content will be officially discontinued. The site will no longer be accessible after this date.

May 15, 2018 – Any links to your Docs.com content that you previously shared with others and that were automatically redirected to your transferred content on OneDrive (or OneDrive for Business) will stop working after this date.

How do I move my files and content from Docs.com?

For Microsoft Accounts (Outlook.com, Hotmail.com, Live.com, etc.) and Facebook Accounts

Do the following:

1. Log in to your Docs.com profile where you can enable automatic back up of all files that are compatible with OneDrive.
2. Follow the prompts, which may include signing up for a new OneDrive account if you don’t already have one.
3. When the process is complete, you’ll find all compatible content that you had previously published to Docs.com backed up to your OneDrive folders. The original content on Docs.com will thereafter only be available for viewing or downloading.

For more detailed backup instructions, and to learn what happens after the migration of your content, please see Back up your personal Docs.com content.

For Office 365 Users with OneDrive for Business

We can automatically back up all compatible content to your OneDrive for Business account if your Administrator enables the auto-migration service for your organization (this option is available as of June 19, 2017). If you would like your school’s or company’s Administrator to initiate this process for you, please contact them and include a link to this article.

You can also choose to log in to Docs.com and follow the auto-migration prompts yourself. When the process is complete, you will find all compatible content you had previously published to Docs.com backed up to your OneDrive for Business folders. The original content on Docs.com will thereafter only be available to view, download, and delete.

For Office 365 Users without OneDrive for Business

Log in to your Docs.com profile where you can download and save your content to your device or your preferred storage and sharing platforms. You can also delete your Docs.com account and content.

What about Docs.com content not backed up to OneDrive or OneDrive for Business?

For users who have successfully completed the auto-migration process, we will save other metadata such as descriptions of your content to an Excel file, and back this up to your OneDrive or OneDrive for Business account. We will also automatically save your About and Journal pages, and any Sway content to your My Sways page on Sway.com.

For all other users and content types not covered by the above, we recommend that you manually download and save them to your preferred storage and sharing platforms.

What about content that I have already linked from Docs.com to other Web sites?

For users who have opted in to auto-migration, links to compatible content in Docs.com will redirect to OneDrive or OneDrive for Business, and continue to show up on other Web pages. If you want to remove linked content, simply delete the files from OneDrive or OneDrive for Business. On May 15, 2018, the automatic redirection to all Docs.com content will end and all links will stop working, so please make sure to manually update any links on your other Web sites before this date.

For users who did not opt in to auto-migration, all links to Docs.com content will stop working on December 15, 2017. Please make sure to manually update any links on other Web sites before this date.

What about OneNote notebooks that I distribute via Docs.com?

Because OneNote notebooks published to Docs.com already originate from OneDrive accounts, the auto-migration service will not include such notebooks. If you need to save a copy of any OneNote notebook, click the Get Notebook button, which will be available until December 15, 2017.

What if my Docs.com content exceeds my OneDrive storage limit?

If you exceed your available storage limit on OneDrive, the migration of your Docs.com content will be interrupted. Any files that were successfully transferred will remain on your OneDrive account, but any files that could not be included will not be backed up and the migration process will stop.

Content migration can be resumed after you have freed up or purchased additional storage space on your OneDrive account. To resume an interrupted migration, log back in to Docs.com and then click Start migration again.

Why can’t I back up my Docs.com content to SlideShare?

SlideShare is intended for public posting. We want its users to purposefully manage which files they want to publish publicly on the Web, and to add their own structure, titles, and descriptions to their content.

I am an Office 365 Administrator. What do I need to know?

If you are an Office 365 administrator, we will soon offer detailed information about how you can automatically back up your organization’s Docs.com content to OneDrive for Business. We will update this article after June 19, 2017 with more information.

Justin Gao

Microsoft (China)

This article is part of a series on M-Powered, an initiative undertaken by Microsoft Asia and local nonprofits in Indonesia, Malaysia, Thailand, and Vietnam to train youth and people with disabilities in IT, and improve their employability, connecting them to opportunities in the growing tech sector. 

For high school English teacher Adrianto Supardiono, one of his biggest motivations at work is watching his students mature into young, independent adults.

“Being able to share knowledge with my students and guide them in their journey towards adulthood is a blessing,” said Adrianto, who has worked at YCAB Foundation, Indonesia for close to five years. “It gives me a sense of fulfillment knowing the work I do helps shape their independence and future.”

Adrianto has been teaching English at YCAB for five years

However, Adrianto estimates that only about half of his students are successful in their job search after graduation. He observed that the key reason why many youth encounter difficulties securing employment is their lack of work readiness. This relates to the lack of confidence, teamwork and collaboration skills, and the willingness to constantly improve, among other things.

“Many of my students choose to look for work instead of pursuing further education because they feel compelled to contribute to their household,” said Adrianto. “However, many are unsuccessful because they don’t realize the importance of cultivating a work ready mindset, and honing the relevant hard skills and soft skills. My colleagues and I try our best to support them, but our resources are limited.”

And this issue is not unique to Adrianto’s students alone. While youth unemployment in Indonesia has been on the decline, the number remains higher than it was before 2000. To address the issue and enhance the employability of Indonesian youth, YCAB worked with Microsoft to develop the e-portal GenerasiBisa! as part of the M-Powered initiative in Asia.

The platform focuses on honing 21st century skills needed to answer the evolving demands of today’s increasingly digital workplace. E-learning courses on the platform are geared towards equipping young people with the hard skills and certifications needed for specific industries, while mentoring programs aim to nurture soft skills, such as teamwork and communication skills. Through the platform, youth can also keep themselves updated with the latest job opportunities, and learn about job fairs and other networking events.

With M-Powered, YCAB and Microsoft believe that they will be able to reach out to five million youth by 2020.

“The high number of young and productive people in the country shows a huge potential for Indonesia to improve the nation’s competitiveness,” said Hanif Dhakiri, Manpower Minister, Indonesia. “We hope that GenerasiBisa! platform can help improve the competence of Indonesian youth to become an independent and dignified generation that is spiritually, socially, and technically competent.”

YCAB Foundation and Microsoft pledging their efforts to enhance the employability of youth in Indonesia

For Adrianto, the online platform means that he has a readily available wealth of resources to turn to when his students come to him for career guidance. As a mentor on GenerasiBisa!, Adrianto actively encourages his students to download training courses and pursue mentorships to equip themselves with the core competencies required to meet the demands of today’s work environment.

“I’m optimistic that GenerasiBisa! will go a long way in helping young people in Indonesia in their job search,” said Adrianto. “With the opportunity to acquire and develop new skills, and connect with good role models who can provide valuable guidance, I’m sure that they will be able to create a better life for themselves and their families.”

Read the other stories in this series here.

日本マイクロソフト株式会社 (本社：東京都港区) は、Xbox One および Windows 10 PC 用レーシング ゲーム『Forza Motorsport 7』を 2017 年 10 月 3 日 (火) に、パッケージ版参考価格 6,900 円 (税抜 / Xbox One のみ)、ダウンロード版参考価格 6,436 円 (税抜) で発売、また、VIP パックなどのコンテンツを付属した『Forza Motorsport 7 デラックス エディション』を、ダウンロード版参考価格 8,426 円 (税抜) で発売します。さらに、カー パス、VIP パックなどのコンテンツを付属し、発売に先駆け先行プレイできる『Forza Motorsport 7 アルティメット エディション』を 2017 年 9 月 29 日 (金) に、パッケージ版参考価格 10,900 円 (税抜 / Xbox One のみ / 限定版*1)、ダウンロード版参考価格 10,463 円 (税抜) で発売します。
各製品は、本日より全国の Xbox One ゲーム取扱店および Microsoft ストア*2で順次予約受付を開始し、Amazon.co.jp、ビック カメラグループおよびヨドバシカメラでパッケージ版を購入された方には各販売店限定の予約購入特典を、Microsoft ストアでダウンロード版を購入された方には Microsoft ストア限定の予約購入特典をプレゼントします。
『Forza Motorsport 7』は、モータースポーツのスリルと美を極限まで感じられる Xbox One および Windows 10 PC 用のレーシングゲームです。4K UHD、HDR、60fps で描かれる驚愕のグラフィックで、リアルなレースの世界が再現され、Ferrari、Lamborghini、そして Porsche をはじめとする、Forzavista? 対応の 700 種以上のクルマが登場します。レース毎にコンディションが変化する世界屈指の 30 ものロケーションで、テクニックを磨き、経験を積んで、勝利と栄光をつかみます。『Forza Motorsport 7』は、Xbox Play Anywhere に対応し、ダウンロード版を一度購入すると追加料金無しで、Xbox One と Windows 10 PC の両デバイスでプレイすることができます。また、Xbox One と Windows 10 PC 間のクロスプレイにも対応し、かつてない規模のプレイヤーと Xbox Live を通じてレースをすることができます。

製品構成/内容

パッケージ版

『Forza Motorsport 7』(通常版)
内容: ゲーム (ディスク)

『Forza Motorsport 7 アルティメット エディション』(限定版)
内容: ゲーム (ディスク)、SteelbookR 特製ケース、アーリー アクセス (9 月 29 日 (金) からの早期購入およびプレイ)、カー パス、VIP パック*4、The Fate of the Furious カー パック

ダウンロード版

『Forza Motorsport 7 スタンダード エディション』
内容: ゲーム (ダウンロード版)

『Forza Motorsport 7 デラックス エディション』
内容: ゲーム (ダウンロード版)、VIP パック、The Fate of the Furious カー パック

『Forza Motorsport 7 アルティメット エディション』
内容: ゲーム (ダウンロード版)、アーリー アクセス (9 月 29 日 (金) からの早期プレイ)、カー パス、VIP パック、The Fate of the Furious カー パック

予約購入特典について

『Forza Motorsport 7』各製品を予約購入された方に、各販売店限定のゲーム内のドライバーが着用するスーツ「カスタム Driver Gear」をプレゼントします。また、Amazon.co.jp で『Forza Motorsport 7 アルティメット エディション』パッケージ版を予約購入された方には、1/43 スケール モデル「2018 Porsche 911 GT2 RS」 もプレゼントします。*5

対象製品/予約購入特典

Amazon.co.jp 限定特典

対象製品: Xbox One 用『Forza Motorsport 7』パッケージ版
予約購入特典: 「カスタム ドライバー ギア」2 セットご利用コード

対象製品: Xbox One 用『Forza Motorsport 7 アルティメット エディション』パッケージ版
予約購入特典: 1/43 スケール モデル「2018 Porsche 911 GT2 RS」、「カスタム ドライバー ギア」2 セットご利用コード

ビックカメラ グループ 限定特典

対象製品: Xbox One 用『Forza Motorsport 7』および『Forza Motorsport 7 アルティメット エディション』パッケージ版
予約購入特典: 「カスタム ドライバー ギア」4 セット ご利用コード

ヨドバシカメラ 限定特典

対象製品: Xbox One 用『Forza Motorsport 7』および『Forza Motorsport 7 アルティメット エディション』パッケージ版
予約購入特典: 「カスタム ドライバー ギア」4 セット ご利用コード

Microsoft ストア 限定特典

対象製品: Xbox One 用『Forza Motorsport 7』および『Forza Motorsport 7 アルティメット エディション』パッケージ版

対象製品: Xbox One および Windows 10 PC 用『Forza Motorsport 7』、『Forza Motorsport 7 デラックス エディション』および『Forza Motorsport 7 アルティメット エディション』ダウンロード版
予約購入特典: 「カスタム ドライバー ギア」2 セット ご利用コード

*1 初回のみの製造となり、数に限りがあります。
*2 各ダウンロード版の予約購入受付は、Microsoft ストアで 2017 年 6 月 14 日 (水) 2:00 から開始予定です。
*3 各デバイスでグラフィックス表現が異なります。
*4 カー パス、VIP パックの収録車種等の情報は後日発表予定です。
*5 各パッケージ版の予約購入特典は、数に限りがあります。各発売日に受け渡しとなります。ゲーム用コンテンツのアンロックには、Xbox Live への接続が必要です。

『Forza Motorsport 7』について

モータースポーツのスリルと美を極限まで感じよう。4K、HDR、60fps で描かれる驚愕のグラフィックスで、リアルなレースの世界が再現される。Ferrari、Lamborghini、そして Porsche をはじめとする、Forzavista? 対応の 700 種以上のクルマが登場。レース毎にコンディションが変化する世界屈指の 30 ものロケーションで、テクニックを磨き、経験を積んで、勝利と栄光をつかめ。

主な特徴

• 息をのむ美しさ
  • 驚愕の 4K ゲーミング: 60fps、4K、HDR で描かれる美麗グラフィックス。『Forza Motorsport 7』で、驚愕のレース体験が実現する。
  • 没入感極まる: ボディーから感じる振動を再現したカメラ シェイク、パーツの振動音で、常に危険と隣り合わせのモータースポーツの緊張が伝わる。
  • ダイナミック レース ウェザー: 強烈な雨、広がっていく水たまり、確保すら困難な視界。ラップを重ねる度に変化する環境でも恐怖心を払いのけ、極限のスピードに挑む勇気とテクニックが試される。

• 究極のクルマの世界
  • 無類のカー ラインアップ: Ferrari、Lamborghini、そして Porsche をはじめとする、Forzavista 対応の 700 車種以上のクルマが登場。
  • 変化するレース トラック コンディション: Forza 史上最大のトラック リストとなる、30 ものロケーション、200 以上のコースを攻略しよう。トラックに戻る度にレース コンディションが変わり、2 つと同じレースは存在しない。
  • 新しいキャンペーン: Forza ドライバーズ カップのプレミア レーシング チャンピオンシップにチャレンジしよう。全世界のプレイヤーの挙動を再現する何千もの Drivatar と競い、Forza ドライバーズ カップの頂点に立とう。

• すべてのドライバーのために
  • 究極のレース体験: 新たなリーグ、強化された観戦モード、ゲーム ライブ配信「Mixer」の統合、Porsche をはじめとするプレミア パートナー。『Forza Motorsport 7』は、プレイヤーにも観戦者にも究極のレース体験を提供する。
  • 思い描くレーシング ドライバーになる: レースの歴史やポップ カルチャーを網羅した、数百ものオプションを含む様々なドライバー ギア コレクションで、思い描くレーシング ドライバーになり、個性を出そう。
  • 誰もがレースを楽しめる: 『Forza Motorsport 7』は、レース ゲーム初心者からプロ級のレース ゲーム ドライバーまで、すべてのプレイヤーが好む比類のカスタマイズ機能をサポート。新たなアシスト機能や Mod 機能は、すべてのスキル レベルをサポートし、ベテラン プレイヤーが好みに応じたチューニングも可能。
  • クロスプレイ対応: Xbox One と Windows 10 PC 間でのクロスプレイに対応し、かつてない規模のプレイヤーと Xbox Live を通じてレースができる。

製品基本情報

Microsoft’s Docs.com service to be discontinued

Microsoft is retiring the Docs.com service on Friday, December 15, 2017 and we are hereby advising all users to move their existing Docs.com content to other file storage and sharing platforms as soon as possible, as Docs.com will no longer be available after this date.

Although the Docs.com site won’t be fully taken offline until December, the ability to use certain features will be scaled back over the coming weeks. If you currently have an account on Docs.com and have used it to upload and share content, please see Important information about Docs.com end of service for a timeline of specific dates on which the service will be increasingly limited in scope and features.

The information below offers details about how to back up your personal content from Docs.com to a file storage or sharing service such as OneDrive. We will update this article as more information becomes available.

What happens to my Docs.com content after it has been migrated from the site?

Content on Docs.com will be migrated to OneDrive, except for any OneNote notebooks that you may have previously published to Docs.com.

A special Docs.com folder will be created on OneDrive for you, where all of your migrated Docs.com content will be stored.

If you have been using Docs.com with a personal Microsoft Account or a Facebook account, you can back up your existing Docs.com content to any OneDrive account.

If you have been using Docs.com with a Work or School account and have chosen to automatically migrate your content, your Docs.com content will be transferred to OneDrive for that same account.

Caution: After your Docs.com content has been migrated, your Docs.com page will become read-only. You will no longer be able to update or publish content on the Docs.com site, however, you will still be able to download your content or delete your Docs.com account.

What permissions are set for Docs.com content that has been migrated to OneDrive?

When your Docs.com content has been migrated to OneDrive, it will retain the same permissions settings as previously on Docs.com. (For Work or School account users, this is only true if OneDrive for Business external sharing is enabled for your organization. Please check with your Administrator for more information.)

If external sharing is not enabled in OneDrive for Business for your organization, or if signing in to OneDrive is required to view files, or if the Docs.com sharing link has expired, then the permissions settings will default to being viewable only within your organization (or only to you).

If OneDrive’s in-org sharing is not enabled for your organization, then the permissions settings will default to being viewable only by you.

If the original Docs.com content does not have the Allow others to download your document option checked, it will inherit Only me permissions on OneDrive.

Within the Docs.com folder that is created for you on OneDrive as part of your content migration, a separate subfolder will be added to correspond to the original Docs.com visibility settings (“Public”, “Limited”, and “Organization”). Each file and document in your Docs.com content will be migrated to the corresponding subfolders based on its original visibility setting. The “Public” subfolder will contain any Docs.com content that was previously set to have “Anyone with this link” permissions.

What happens to links to my existing Docs.com content after my content has been migrated?

Even after your Docs.com content has been successfully migrated, any links pointing to existing content on Docs.com that you may have previously shared will continue to work until May 15, 2018. (For the full schedule of important dates, please see Important information about Docs.com end of service.)

Your existing links will be automatically redirected to your migrated Docs.com content on OneDrive or Sway.com, excepts for following cases:

• If Allow others to download your document was not previously enabled for the document or file.
• If OneDrive for Business external sharing is not enabled for your organization.
• If your organization did not previously opt in to the Docs.com service. (Administrators, please see Manage Docs.com use in your organization for details about how to opt in.)

What happens to any Docs.com content that I’ve embedded on other Web sites?

Any Docs.com content that you have previously embedded on other Web sites or blogs (for example, WordPress) will no longer be rendered properly. Site visitors will need to first click the Open in a new browser tab button to open and view the embedded content from its new source.

Please note that as of December 15, 2017, all previously embedded content will stop being rendered. You will need to manually change all embedded files to load from their new source locations on OneDrive or Sway.com.

How do I start backing up my content from Docs.com?

To begin your Docs.com content migration to OneDrive, please do the following:

1. Sign in to com with your Microsoft Account, your Work or School account, or your Facebook account.
2. In the yellow bar that appears near the top of your screen, click Migrate.
3. On the confirmation page that is displayed, click the Start migration button to begin the backup.

Depending on the amount and size of the content you have stored on Docs.com, the migration process may take several minutes to complete. When the migration has been completed, go to the Docs.com home page to confirm the successful migration of your content.

How can I troubleshoot any content migration failures?

If content migration failed for any of your files or documents, Docs.com will notify you in a yellow bar near the top of your screen. Please click the Check errors button for more details.

If you see an error for any of your files or documents, click the See Error Log button. This opens a list of files and their errors in a separate browser tab. Listed below are our recommendations for each type of error that you may encounter:

Justin Gao

Microsoft (China)

Обновлен дизайн OneNote для Windows 10, Mac, iOS, Android и OneNote Online в трёх ключевых областях:

• Повышение удобства для пользователей вспомогательных технологий.
• Упрощение средств навигации.
• Согласованность между устройствами.

Посмотрите видео с аудио описаниями здесь.

Повышение удобства для всех

Как сказал руководитель компании Microsoft Сатья Наделла, “Мы сфокусируемся на разработке продуктов, которые понравятся нашим заказчикам, и которые будут доступны всем и разработаны для каждого.” В этом обновлении мы выбрали целью сделать OneNote доступней для людей с ограниченными возможностями — такими как нарушение зрения и подвижности. Мы опросили сотни людей и проанализировали телеметрию продукта для понимания того, как улучшить горячие клавиши и возможности экранного диктора. Мы рады поделиться двумя значительными улучшениями в этих двух областях.

Упрощенная навигация

Мы общались с пользователями о том, как можно улучшить расположение меню навигации — особенно для больших ноутбуков. Теперь средства навигации расположены в левой области приложения. Это позволяет легко переключаться между заметками и значительно улучшает удобство использования с вспомогательными технологиями. С новым консолидированным и упрощенным дизайном, экранные дикторы могут легко осуществлять навигацию по приложению для людей с ограниченными возможностями. В дополнении, контент расположен в центральной области, что помогает обучающимся сконцентрироваться на важном и не отвлекаться на мелочи.

Согласованность между устройствами

Сегодня пользователи OneNote часто работают на нескольких устройствах. Согласованная работа на всех экранах упрощает переключение между устройствами. С этим обновлением, независимо от используемого устройства, работа будет одинакова — что позволит фиксировать мысли, делать заметки и быстрее выполнять свои задачи. Это обновление также отлично воспримется школами, где разнообразие устройств становится все более распространенным. Студенты смогут легче осуществлять переход между своими школьными и домашними устройствами, оставаясь сфокусированными на школьной работе. Стив Созин, пользователь OneNote с нарушениями зрения, подчеркивает преимущества, “Мне нравится, что это просто работает на всех устройствах, так что я могу сфокусироваться на том, чтобы делать заметки, не думая о логистике. Это действительно здорово и вдохновляюще.”

OneNote одинаково работает на всех устройствах.

Новый дизайн для OneNote разворачивается для Windows 10, Mac, iOS, Android и OneNote Online в следующие несколько недель. Проверьте эту статью для того, чтобы больше узнать об обновлении OneNote.

Чтобы бесплатно получить OneNote, оставить предложения или попросить помощи, используйте следующие ссылки:

• Получить OneNote: Mac | iOS | Android | Windows | OneNote Online
• Оставить предложение: OneNote UserVoice
• Попросить помощь: Answers.Microsoft.com

Jun.

13

Script Download:
The script is available for download from https://gallery.technet.microsoft.com/scriptcenter/How-to-add-credentials-to-90145dae.

The sample code demonstrates the VBScript sample to add credentials for specific users to access another domain automatically.

You can find more All-In-One Script Framework script samples at http://aka.ms/onescriptingallery

Smartphones oder Tablets sind für Wissensarbeiter das (mobile) Office in der Hosentasche. Das spiegelt sich auch auf den jeweiligen Home-Screens wider: Sie zeigen, auf welche Anwendungen und Dienste wir am häufigsten zugreifen und welche Bedeutung diesen somit für unseren Alltag oder zumindest unsere Arbeit zukommt. In unserer Blog-Reihe möchten wir euch die Screenshots von Wissensarbeitern aus unterschiedlichen Branchen zeigen und welche Anwendungen und Apps sie immer #mitdabei haben. Stets im Mittelpunkt: mit all seinen vielfältigen Anwendungen. Dieser Beitrag ist der siebte aus der Reihe – alle weiteren Beiträge findest du hier.

Der Arbeitsplatz der Zukunft ist…vielfältig und facettenreich. Und für mich auf jeden Fall maßgeblich durch Teamwork gekennzeichnet. Das bestätigt sich auch in Gesprächen mit Kunden und Partnern. Damit wird die Prognose einiger Experten bereits jetzt Realität: Arbeit findet immer häufiger in Teams statt. Teams, die interdisziplinär und Hierarchieebenen-übergreifend für ein bestimmtes Projekt zusammenarbeiten und sich dabei nicht immer am selben Ort befinden.

Das gilt auch für meine Arbeit als Strategy Lead für die Office 365-Familie für kleine und mittelständische Unternehmen (KMU). Meine Kollegen sitzen zum Teil in unserer Deutschland-Zentrale München-Schwabing, arbeiten aber deswegen nicht unbedingt im Büro. Und viele andere Teammitglieder sind in der gleichen Rolle wie ich an den über 100 weltweiten Microsoft-Standorten tätig. Dabei ist nicht nur die räumliche Distanz, sondern beispielsweise auch die Zeitverschiebung eine große Herausforderung für Informationsfluss, Wissenstransfer und Kommunikation.

Seit der weltweiten Verfügbarkeit von Microsoft Teams nutzen wir das chatbasierte Tool als unseren virtuellen Arbeitsplatz, als eine Art digitalen Schreibtisch, an dem wir alle gemeinsam „sitzen“ – egal, wo wir uns gerade befinden. Deshalb habe ich es auch immer #mitdabei:

Besonders praktisch ist gerade für die internationalen Projekte, an denen ich mitwirke, der Aufbau des Tools als Chat mit Aktivitätsprotokoll. Das funktioniert ganz ähnlich wie bei gängigen Social Media: Im Protokoll werden alle öffentlichen Unterhaltungen, geteilten Dokumente und vieles mehr angezeigt, das ich verpasst habe seit ich das letzte Mal online war. So kann ich leicht nachvollziehen, was die Kollegen am anderen Ende der Welt erarbeitet und besprochen haben – während ich schlief.

Der Chat ist außerdem eine gute Möglichkeit für kurzfristige, schnelle Absprachen ohne den Posteingang zu verstopfen. Für komplexere Abstimmungen, oder diejenigen, die lieber telefonieren, ist Skype for Business in Teams integriert. Das Tool bündelt projektbezogen alle Informationen und Dokumente – sie liegen quasi jederzeit auf meinem Tisch, ob ich im Büro oder unterwegs bin. Aus diesem Grund hat es Microsoft Teams auch innerhalb kürzester Zeit auf meinen Homescreen geschafft und ist als mobile App (für Windwows Phone, iOS und Android) immer #mitdabei.

Wie die Homescreens meiner Kollegen und anderer Wissensarbeiter aussehen, die in ganzen anderen Bereichen arbeiten, und welche Apps für ihren Arbeitsalltag unverzichtbar sind, lest ihr in den weiteren Beiträgen unserer Serie #mitdabei.

Ein Beitrag von Marina Treude
Strategy Lead Office 365 SMB + Teams Launch Lead

みなさん、こんにちは。Windows プラットフォーム サポートの今入です。
昨年の 8 月に発表されている通り、Azure RemoteApp は、2017 年 8 月 31 日 を持ってサービスを終了します。

それに伴い、現在 Azure RemoteApp のご利用にいくつかの制限が設けられております。
これらの制限は、サービス終了に伴い、他のサービスへの円滑な移行を推奨するために設けられた制限となっております。
なお、これらの制限は、弊社サポート窓口へお問い合わせ頂いたとしても、制限を解除/緩和することはできません。ご了承頂ければ幸いでございます。

1. Azure RemoteApp の管理メニューが表示されない

2016 年 8 月 12 日の時点で、Azure RemoteApp コレクションが 1 つも所持していない場合は、旧 Azure ポータル サイトから Azure RemoteApp の管理メニューが削除されております。

表示されている場合	表示されていない場合

2. コレクション数/ユーザー数の上限を拡大できない

3. Azure RemoteApp の管理ができない

このメールに対し、2017 年 6 月 1 日までに、Azure RemoteApp サービス終了までの移行プランについてご返信、および Eric Orman から回答をもらえていない場合は、以下のように Azure RemoteApp コレクションがご利用いただけなくなっております。

4. Azure RemoteApp コレクションへのユーザー追加ができない

例 1) Standard プランで、100 ユーザーを登録していたコレクション A
コレクション A に追加できるユーザーは、あと 100 × 0.05 = 5 ユーザー追加できます。

例 2) Standard プランで、5 ユーザーを登録していたコレクション B
Standard プランの最低課金ユーザー数 20 ユーザーまで追加できるため、あと 15 ユーザー追加できます。

例 3) Premium Plus プランで、3 ユーザーを登録していたコレクション C
Premium Plus プランの最低課金ユーザー数 5 ユーザーまで追加できるため、あと 2 ユーザー追加できます。

Azure RemoteApp の移行プランの参考情報

Azure RemoteApp から移行する際の選択肢
Azure RemoteApp から Citrix XenApp Essentials に移行する方法

その他 Azure RemoteApp サービス終了に関する情報

Cumulative Update 6 (CU6) for Exchange Server 2016 will be released soon^TM, but before that happens, I wanted to make you aware of a behavior change in item recovery that is shipping in CU6.  Hopefully this information will aid you in your planning, testing, and deployment of CU6.

Item Recovery

Prior to Exchange 2010, we had the Dumpster 1.0, which was essentially a view stored per folder. Items in the dumpster stayed in the folder where they were soft-deleted (shift-delete or delete from Deleted Items) and were stamped with the ptagDeletedOnFlag flag. These items were special-cased in the store to be excluded from normal Outlook views and quotas. This design also meant that when a user wanted to recover the item, it was restored to its original folder.

With Exchange 2010, we moved away from Dumpster 1.0 and replaced it with the Recoverable Items folder. I discussed the details of that architectural shift in the article, Single Item Recovery in Exchange 2010. The Recoverable Items architecture created several benefits: deleted items moved with the mailbox, deleted items were indexable and discoverable, and facilitated both short-term and long-term data preservation scenarios.

As a reminder, the following actions can be performed by a user:

• A user can perform a soft-delete operation where the item is deleted from an Inbox folder and moved to the Deleted Items folder. The Deleted Items folder can be emptied either manually by the user, or automatically via a Retention Policy. When data is removed from the Deleted Items folder, it is placed in the Recoverable ItemsDeletions folder.
• A user can perform a hard-delete operation where the item is deleted from an Inbox folder and moved to the Recoverable ItemsDeletions folder, bypassing the Deleted Items folder entirely.
• A user can recover items stored in the Recoverable ItemsDeletions folder via recovery options in Outlook for Windows and Outlook on the web.
• However, this architecture has a drawback – items cannot be recovered to their original folders.

Many of you have voiced your concerns around this limitation in the Recoverable Items architecture, through various feedback mechanisms, like at Ignite 2015 in Chicago where we had a panel that included the Mailbox Intelligence team (those who own backup, HA, DR, search, etc.). Due to your overwhelming feedback, I am pleased to announce that beginning with Exchange 2016 CU6, items can be recovered to their original folders!

How does it work?

1. When an item is deleted (soft-delete or hard-delete) it is stamped with the LastActiveParentEntryID (LAPEID). By using the folder ID, it does not matter if the folder is moved in the mailbox’s hierarchy or renamed.
2. When the user attempts a recovery action, the LAPEID is used as the move destination endpoint.

The LAPEID stamping mechanism has been in place since Exchange 2016 Cumulative Update 1. This means that as soon as you install CU6, your users can recover items to their original folders!

Soft-Deletion:

Hard-Deletion

Are there limitations?

Yes, there are limitations.

First, to use this functionality, the user’s mailbox must be on a Mailbox server that has CU6 installed. The user must also use Outlook on the web to recover to the original folder; neither Outlook for Windows or Outlook for Mac support this functionality, today.

If an item does not have an LAPEID stamped, then the item will be recovered to its folder type origin – Inbox for mail items, Calendar for calendar items, Contacts for contact items, and Tasks for task items. How could an item not have an LAPEID? Well, if the item was deleted before CU1 was installed, it won’t have an LAPEID.

And lastly, this feature does not recover deleted folders. It only recovers items to folders that still exist within the user’s mailbox hierarchy. Once a folder is deleted, recovery will be to the folder type origin for that item.

Summary

We hope you can take advantage of this long sought-after feature. We continue to look at ways we can improve user recovery actions and minimize the need for third-party backup solutions. If you have questions, please let us know.

Ross Smith IV
Principal Program Manager
Office 365 Customer Experience

• When we see this error, generally on the mssdmn.exe process with a EventID = dm1k
  

   

  System.ArgumentException *** Message : An item with the same key has already been added.
  

   

• This means it has probably failed in the “ParseGroupCollection” method within the SiteData call for the “Site“, or SiteCollection, object
  
• In the ULS, if you were to filter where you see that error, by the ThreadID, you would see something like this:
  

  06/07/2017 09:40:56.23 mssdmn.exe (0x3124) 0x2F28 SharePoint Server Search Connectors:SharePoint ac3jn Verbose GetContent CorrelationID 393ef99d-174e-b0b4-a06f-97dc29dd8957 ObjectType SiteCollection Url https://foo/_vti_bin/sitedata.asmx Search RequestDuration 449 SPIISLatency 0 SP RequestDuration 339 57ec8c92-d753-42c2-b636-a1280b8b9e6c
  

  06/07/2017 09:40:56.37 mssdmn.exe (0x3124) 0x2F28 SharePoint Server Search Connectors:SharePoint dm1k Medium Exception Type: System.ArgumentException *** Message : An item with the same key has already been added. *** StackTrace: at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper.ParseGroupCollection(XmlReader groupReader) at Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper.InitSite(String strSiteUrl) at Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper.GetSite(String strSiteUrl, sSite3& site) 57ec8c92-d753-42c2-b636-a1280b8b9e6c
  

• We can utilize PowerShell to emulate this sitedata.asmx call on the SiteCollection Object.
  
• I suggest doing this, so we can investigate the XML andor use it for reference later.
  
• You can see in the ULS sample above that we called the “SiteCollection” object on https://foo/_vti_bin/sitedata.asmx ( if it were another SiteCollection, you would see the URL in this ULS entry )
  
• In order to get this XML, you can run this ( when prompted for creds, you want to use the Default Content Access Account credentials )
  

   

  ########################################################################################
  

  ## Set SiteData Web Service Object ### Use the Content Access Account for the $creds variable
  

  ########################################################################################
  

   

  $creds
  =
  Get-Credential
  

  $url
  =
  “https://foo”
  

  $wsUrl
  =
  $url
  +
  “/_vti_bin/sitedata.asmx?wsdl”
  

  $sitedataWS
  =
  New-WebServiceProxy
  -Uri
  $wsUrl
  -Credential
  $creds
  

   

  ########################################################################################
  

  ## SiteCollection Object – ObjectType = 2 ##
  

  ########################################################################################
  

   

  $int
  =
  [int]2
  

  $xmlinput
  =
  “<GetContent><ObjectType>2</ObjectType><ObjectId /><FolderUrl /><ItemId /><RetrieveChildItems>False</RetrieveChildItems><SecurityOnly>False</SecurityOnly><LastItemIdOnPage /><AllowRichText>False</AllowRichText><RequestLoad>100</RequestLoad><RemoveInvalidXmlChars>True</RemoveInvalidXmlChars></GetContent>”
  

  $xml
  =
  $sitedataWS.GetContentEx($int,$xmlinput)
  

  $xml
  |
  Out-File
  “C:TempSiteCollection.xml”
  

• Once you collect the XML, we can parse it through additional PowerShell
  
• Some time back, we created some PowerShell that would try to mimic this “ParseGroupCollection” and try to identify duplicate “Groups” within the returned XML.
  

   

  #the attributes that are in the group element/node
  

  $attributes
  =
  “ID”,“Name”,“OwnerID”,“OwnerIsUser”,“Description”
  

   

  #the object array of custom objects we will use to return data
  

  $results
  = @()
  

   

  #setup the xml reader and get the data
  

  $xmlReader
  =
  [System.Xml.XmlReader]::Create(‘C:TempSiteCollection.xml’)
  

   

  #read dat data
  

  while($xmlReader.Read())
  

  {
  

  
  #Set things we want to check ahead of the compare operation
  

  
  $isElementNodeType
  =
  $xmlReader.NodeType -eq
  [System.Xml.XmlNodeType]::Element
  

  
  $isGroupNode
  =
  $xmlReader.Name -eq
  ‘Group’
  

   

  
  #Compare ALL THE THINGS!
  

  
  if($isElementNodeType
  -and
  $xmlReader.HasAttributes -and $isGroupNode)
  

  {
  

  
  #create object to store the current group element
  

  
  $currentGroup
  =
  “”
  |
  Select
  “ID”,“Name”,“OwnerID”,“OwnerIsUser”,“Description”
  

   

  
  #loop through attribute array set above.
  

  
  foreach($attribute
  in
  $attributes)
  

  {
  

  
  #start populating data in $currentGroup by reading that attribute from current point in reader
  

  
  $currentGroup.$attribute = $xmlReader.GetAttribute($attribute)
  

  }
  

   

  
  #add current group to results
  

  
  $results
  +=
  $currentGroup
  

   

  }
  

   

  }
  

   

  $resultcount
  =
  $results.Count
  

  Write-Host
  “There are $resultcount group elements”
  

   

  ##see the items easily
  

  #$results | Select Id, Name | Out-GridView
  

   

  #group items and then look for items when
  

  $results
  |
  group
  -Property
  name
  |
  ? {$_.count -gt
  1} |
  select
  count, name
  

  $results
  |
  group
  -Property
  Id
  |
  ? {$_.count -gt
  1} |
  select
  count, name
  

   

• If there are any Duplicates, on the Name or ID, we would dump out the Name or ID with a count and the Name of the duplicate Group
  
• If you get any returns on these, where count > 1, then you can go find those groups in the Site Permissions of your Site and remove one of the Groups.
  
• There are times that parsing through this XML doesn’t yield any Duplicate NamesIDs so what do you do in that case?
  
• This is where a Process Dump would be handy
  
• We have a pre-created rule that willshould dump on the following:
  

   

  tag_dm1k AND message contains “An item with the same key has already been added.”
  

   

   

  • Download “Debug Diag 2.0” from here:
    

     

    https://www.microsoft.com/en-us/download/details.aspx?id=49924
    

     

  • Install it on your Crawl Server(s)
    
  • Once you install it, open “DebugDiag 2.0 Collection”
    
  • When the crashhang wizard comes up, click on “Close” or Cancel
    
  • Then in the Lower right corner, click on the “Import” button
    
  • Select that “tag_dm1k_partial.ddconfig” file you saved to your Crawl Server(s)
    
  • Click OK
    
  • Once the rule loads up, right click the Rule > Activate Rule
    
  • Trigger a crawl..
    

• This should monitor mssdmn.exe process and capture a DMP file when that EventId = dm1k is thrown, with that message in the ULS
  

• looking at the DMP file.
  

   

• i see this
  

  0:106> !threads
  

  ThreadCount: 143
  

  UnstartedThread: 0
  

  BackgroundThread: 143
  

  PendingThread: 0
  

  DeadThread: 0
  

  Hosted Runtime: no
  

  Lock
  

  ID OSID ThreadOBJ State GC Mode GC Alloc Context Domain Count Apt Exception
  

  0 1 1a60 000000338a9306f0 20220 Preemptive 0000000000000000:0000000000000000 000000338a923120 0 MTA
  

  4 2 3138 000000338a93b3e0 2b220 Preemptive 0000000000000000:0000000000000000 000000338a923120 0 MTA (Finalizer)
  

  9 3 3628 00000033a48469a0 20220 Preemptive 0000000000000000:0000000000000000 000000338a923120 0 MTA
  

  13 4 24ec 00000033ad63a0e0 28220 Preemptive 0000000000000000:0000000000000000 000000338a923120 0 MTA
  

  18 5 1be8 00000033ad63e890 28220 Preemptive 0000000000000000:0000000000000000 000000338a923120 0 MTA
  

   

  <truncated>
  

   

  12 71 24a4 00000033b02fa880 20220 Preemptive 0000000000000000:0000000000000000 000000338a923120 0 MTA
  

  104 72 8cc 00000033b7c2b8b0 20220 Preemptive 0000000000000000:0000000000000000 000000338a923120 0 MTA
  

  106 73 188c 00000033b0336fd0 20220 Preemptive 000000338DE59980:000000338DE5AFC0 000000338a923120 0 MTA System.ArgumentException 000000338de50b08
  

• next i dumped the Stack out
  

0:106> ~k

# Child-SP RetAddr Call Site

00 00000033`ab3f5ef8 00007ff7`e637d4f7 Microsoft_Office_Server_Native!ULSSendFormattedTrace [n:srcutilulsapinativetrace.cpp @ 404]

01 00000033`ab3f5f00 00007ff7`e637c265 ConnectorPH!DomainBoundILStubClass.IL_STUB_PInvoke(UInt32, UInt32, Microsoft.Office.Server.Diagnostics.ULSTraceLevel, System.String, Boolean)+0x157

02 00000033`ab3f6020 00007ff7`e637b095 Microsoft_Office_Server!Microsoft.Office.Server.Diagnostics.ULS.SendTraceImpl(UInt32, Microsoft.Office.Server.Diagnostics.ULSCatBase, Microsoft.Office.Server.Diagnostics.ULSTraceLevel, System.String, System.Object[])+0x125 [n:srcotoolsincosrvDiagnosticsULS.cs @ 2334]

03 00000033`ab3f6080 00007ff7`e7392bd1 Microsoft_Office_Server!Microsoft.Office.Server.Diagnostics.ULS.SendTraceTag(UInt32, Microsoft.Office.Server.Diagnostics.ULSCatBase, Microsoft.Office.Server.Diagnostics.ULSTraceLevel, System.String, System.Object[])+0x155 [n:srcotoolsincosrvDiagnosticsULS.cs @ 2303]

04 00000033`ab3f6120 00007ff7`e737627e Microsoft_Office_Server_Search!Microsoft.Office.Server.Search.Internal.Protocols.CProtocolHelper.HandleException(System.Exception, UInt32)+0xf1 [n:srcsearchmanagedlibOMProtocolsutil.cs @ 545]

05 00000033`ab3f61b0 00007ff8`45ac59c5 Microsoft_Office_Server_Search!Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper.GetSite(System.String, Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.sSite3 ByRef)+0x42e [n:srcsearchmanagedlibOMProtocolsstsv3ph.cs @ 2732]

06 00000033`ab3f6220 00007ff8`45ac58c3 clr!ExceptionTracker::CallHandler+0xc5 [f:ddndpclrsrcvmexceptionhandling.cpp @ 3341]

07 00000033`ab3f62c0 00007ff8`45ac42af clr!ExceptionTracker::CallCatchHandler+0x7f [f:ddndpclrsrcvmexceptionhandling.cpp @ 535]

08 00000033`ab3f6350 00007ff8`4e53347d clr!ProcessCLRException+0x2e6 [f:ddndpclrsrcvmexceptionhandling.cpp @ 1067]

09 00000033`ab3f6430 00007ff8`4e4f5405 ntdll!RtlpExecuteHandlerForUnwind+0xd [d:blueminkernelntosrtlamd64xcptmisc.asm @ 252]

0a 00000033`ab3f6460 00007ff8`45ac4348 ntdll!RtlUnwindEx+0x385 [d:blueminkernelntosrtlamd64exdsptch.c @ 1006]

0b 00000033`ab3f6b40 00007ff8`45ac4304 clr!ClrUnwindEx+0x40 [f:ddndpclrsrcvmexceptionhandling.cpp @ 4328]

0c 00000033`ab3f7060 00007ff8`4e5333fd clr!ProcessCLRException+0x2b2 [f:ddndpclrsrcvmexceptionhandling.cpp @ 1032]

0d 00000033`ab3f7140 00007ff8`4e4f4847 ntdll!RtlpExecuteHandlerForException+0xd [d:blueminkernelntosrtlamd64xcptmisc.asm @ 131]

0e 00000033`ab3f7170 00007ff8`4e53258a ntdll!RtlDispatchException+0x197 [d:blueminkernelntosrtlamd64exdsptch.c @ 535]

0f 00000033`ab3f7840 00007ff8`4b6b871c ntdll!KiUserExceptionDispatch+0x3a [d:blueminkernelntosrtlamd64trampoln.asm @ 715]

10 00000033`ab3f7f50 00007ff8`45ac5294 KERNELBASE!RaiseException+0x68 [d:blueminkernelkernelbasexcpt.c @ 828]

11 00000033`ab3f8030 00007ff8`45ac508e clr!RaiseTheExceptionInternalOnly+0x2fe [f:ddndpclrsrcvmexcep.cpp @ 3134]

12 00000033`ab3f8130 00007ff8`453daacf clr!IL_Throw+0x11b [f:ddndpclrsrcvmjithelpers.cpp @ 5017]

13 00000033`ab3f8300 00007ff7`e737cdc2 mscorlib_ni!System.Collections.Generic.Dictionary`2[[System.__Canon, mscorlib],[System.__Canon, mscorlib]].Insert(System.__Canon, System.__Canon, Boolean)+0xdd274f [f:ddndpclrsrcBCLSystemCollectionsGenericDictionary.cs @ 314]

14 00000033`ab3f8390 00007ff7`e737660e Microsoft_Office_Server_Search!Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper.ParseGroupCollection(System.Xml.XmlReader)+0x192 [n:srcsearchmanagedlibOMProtocolsstsv3ph.cs @ 2642]

15 00000033`ab3f8410 00007ff7`e7375ef2 Microsoft_Office_Server_Search!Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper.InitSite(System.String)+0x2ae [n:srcsearchmanagedlibOMProtocolsstsv3ph.cs @ 2628]

16 00000033`ab3f84b0 00007ff7`e7375af9 Microsoft_Office_Server_Search!Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper.GetSite(System.String, Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.sSite3 ByRef)+0xa2 [n:srcsearchmanagedlibOMProtocolsstsv3ph.cs @ 2704]

<truncated>

• We can see our function in here…
  

ParseGroupCollection(System.Xml.XmlReader)

• the line above is the hashtablecollection
  
• so i dumped that Stack Object out:
  

   

  0:106> !dso 00000033`ab3f8300
  

  OS Thread Id: 0x188c (106)
  

  RSP/REG Object Name
  

  rbx 000000338de594e8 System.String Exception Type: System.ArgumentException *** Message : An item with the same key has already been added.
  *** StackTrace: at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
  

  at Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper.ParseGroupCollection(XmlReader groupReader)
  

  at Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper.InitSite(String strSiteUrl)
  

  at Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper.GetSite(String strSiteUrl, sSite3& site)
  

  r12 000000338c634130 Microsoft.Office.Server.Diagnostics.ULSCat
  

  r13 000000338c73add8 System.String Exception Type: {0} *** Message : {1} *** StackTrace: {2}
  

  r14 000000338de50e08 System.Object[] (System.Object[])
  

  00000033AB3F8300 000000338d241d58 System.Collections.Generic.Dictionary`2[[System.String, mscorlib],[Microsoft.Office.Server.Search.Internal.Protocols.sSecurityUser[], Microsoft.Office.Server.Search]]
  

  00000033AB3F8320 000000338d241d58 System.Collections.Generic.Dictionary`2[[System.String, mscorlib],[Microsoft.Office.Server.Search.Internal.Protocols.sSecurityUser[], Microsoft.Office.Server.Search]]
  

  00000033AB3F8330 000000338de50970 Microsoft.Office.Server.Search.Internal.Protocols.sSecurityUser[]
  

  00000033AB3F8338 000000338de11038 System.String 1031479 Precision breeding for piglet survival PhD studentship Owners
  

  00000033AB3F8358 000000338d242000 System.String https://foo
  

  00000033AB3F8370 000000338c7694c0 System.Xml.XmlSubtreeReader
  

  00000033AB3F8378 000000338d241cd0 Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper
  

  00000033AB3F8380 000000338de4fe80 System.Xml.XmlSubtreeReader
  

  00000033AB3F8390 000000338de4fe80 System.Xml.XmlSubtreeReader
  

  00000033AB3F8398 000000338be97090 System.Globalization.CultureInfo
  

  00000033AB3F83B0 000000338de4fdb0 System.String 1031479 Precision breeding for piglet survival PhD studentship Owners
  

  00000033AB3F83B8 000000338de4fe58 System.String 10058
  

  00000033AB3F83C8 000000338de50970 Microsoft.Office.Server.Search.Internal.Protocols.sSecurityUser[]
  

  00000033AB3F83D0 000000338de4fdb0 System.String 1031479 Precision breeding for piglet survival PhD studentship Owners
  

  00000033AB3F83D8 000000338de4fe58 System.String 10058
  

  00000033AB3F83E8 000000338c7660a8 System.Xml.XmlTextReaderImpl
  

  00000033AB3F83F8 000000338d241cd0 Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper
  

  00000033AB3F8400 000000338c7694c0 System.Xml.XmlSubtreeReader
  

  00000033AB3F8548 000000338de50b08 System.ArgumentException
  

  00000033AB3F85B0 000000338d241cd0 Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper
  

  00000033AB3F85B8 000000338d242000 System.String https://foo
  

  00000033AB3F85E0 000000338d242000 System.String https://foo
  

  00000033AB3F8780 000000338d241cd0 Microsoft.Office.Server.Search.Internal.Protocols.SharePoint2006.CSTS3Helper
  

  00000033AB3F96B0 000000338be91420 System.String
  

  00000033AB3F96C0 000000338be91420 System.String
  

  00000033AB3F9740 000000338be91420 System.String
  

  00000033AB3F9770 000000338be91420 System.String
  

  00000033AB3F9780 000000338be91420 System.String
  

  00000033AB3F9810 000000338be91420 System.String
  

  00000033AB3F9820 000000338be91420 System.String
  

  00000033AB3F9848 000000338be91420 System.String
  

  00000033AB3F9878 000000338be91420 System.String
  

  00000033AB3F9880 000000338be91420 System.String
  

  00000033AB3F9890 000000338be91420 System.String
  

• this group is of interest to me:
  

   

  1031479 Precision breeding for piglet survival PhD studentship Owners
  

  10058
  

   

• so i went back to my SiteCollection.xml we had collected..
  
• i changed the PS a bit to dump the $results object from the Previous PS
  

$results
|
Select
Id, Name
|
Out-GridView

• and then I filtered where Name contains “Precision”
  
• i see these entries here:
  

   

• those with IDs = 9972, 9973, 9974 appear to be the Culprit here. ( somehow these entries made it into the Groups table with that funky encoded value )
  
• so we used the following PowerShell “SiteGroups” removed:
  

   

  $ids
  =
  “9972”, “9973”, “9974”
  

  $w
  =
  Get-SPWeb
  https://foo
  

  foreach($sg
  in
  $w.SiteGroups |
  ?{$_.Name -match
  “Precision breeding for piglet survival PhD Student”})
  

  {
  

  
  foreach($id
  in
  $ids)
  

  {
  

  
  if($sg.Id -eq $id)
  

  {
  

  
  “Removing Group “
  +
  $sg.Name +
  ” With ID: “
  + $sg.Id
  

  
  $w.SiteGroups.RemoveByID($id)
  

  }
  

  }
  

  }
  

   

• this should get these groups out and allow the site to be crawled..

We wanted to post a quick note to call out that our friends in .NET are releasing .NET Framework 4.7 to Windows Update for client and server operating systems it supports.

At this time, .NET Framework 4.7 is not supported by Exchange Server. Please resist installing it on any of your systems after its release to Windows Update.

We will be sure to release additional information and update the Exchange supportability matrix when .NET Framework 4.7 becomes a supported version of .NET Framework with Exchange Server. We are working with the .NET team to ensure that Exchange customers have a smooth transition to .NET Framework 4.7, but in the meantime, delay this particular .NET update on your Exchange servers. Information on how this block can be accomplished can be found in article 4024204, How to temporarily block the installation of the .NET Framework 4.7.

It’s too late, I installed it. What do I do now?

If .NET Framework 4.7 was already installed and you need to roll back to .NET Framework 4.6.2, here are the steps:

Note: These instructions assume you are running the latest Exchange 2016 Cumulative Update or the latest Exchange 2013 Cumulative Update as well as .NET Framework 4.6.2 prior to the upgrade to .NET Framework 4.7 at the time this article was drafted. If you were running a version of .NET Framework other than 4.6.2 or an older version of Exchange prior to the upgrade of .NET Framework 4.7, then please refer to the Exchange Supportability Matrix to validate what version of .NET Framework you need to roll back to and update the steps below accordingly. This may mean using different offline/web installers or looking for different names in Windows Update based on the version of .NET Framework you are attempting to roll back to if it is something other than .NET Framework 4.6.2.

1. If the server has already updated to .NET Framework 4.7 and has not rebooted yet, then reboot now to allow the installation to complete.

2. Stop all running services related to Exchange.  You can run the following cmdlet from Exchange Management Shell to accomplish this: 

(Test-ServiceHealth).ServicesRunning | %{Stop-Service $_ -Force}

3. Depending on your operating system you may be looking for slightly different package names to uninstall .NET Framework 4.7.  Uninstall the appropriate update.  Reboot when prompted.

• On Windows 7 SP1 / Windows Server 2008 R2 SP1, you will see the Microsoft .NET Framework 4.7 as an installed product under Programs and Features in Control Panel.
• On Windows Server 2012 you can find this as Update for Microsoft Windows (KB3186505) under Installed Updates in Control Panel.
• On Windows 8.1 / Windows Server 2012 R2 you can find this as Update for Microsoft Windows (KB3186539) under Installed Updates in Control Panel.
• On Windows 10 Anniversary Update and Windows Server 2016 you can find this as Update for Microsoft Windows (KB3186568) under Installed Updates in Control Panel.

4. After rebooting check the version of the .NET Framework and verify that it is again showing version 4.6.2.  You may use this method to determine what version of .NET Framework is installed on a machine. If it shows a version prior to 4.6.2 go to Windows Update, check for updates, and install .NET Framework 4.6.2.  If .NET Framework 4.6.2 is no longer being offered via Windows Update, then you may need to use the Offline Installer or the Web Installer. Reboot when prompted.  If the machine does show .NET Framework 4.6.2 proceed to step 5.

• .NET Framework 4.6.2 offline installer.
• .NET Framework 4.6.2 web installer.

5. After confirming .NET Framework 4.6.2 is again installed, stop Exchange services using the command from step 2.  Then, run a repair of .NET 4.6.2 by downloading the offline installer, running setup, and choosing the repair option.  Reboot when setup is complete.

6. Apply any security updates specifically for .NET 4.6.2 by going to Windows update, checking for updates, and installing any security updates found.  Reboot after installation.

7. After reboot verify that the .NET Framework version is 4.6.2 and that all security updates are installed.

8. Follow the steps here to block future automatic installations of .NET Framework 4.7.

The Exchange Team

Ever need to disable a specific monitor?

I know I get tired of clicking through the console, maybe you do too?
Do you know the Monitor name and class?
If yes, then you can enable/disable monitors from PowerShell

So let’s get started.

From your management server, you can run SCOM commands as your ID (assuming your ID is set up in SCOM)

This example has 2 purposes:

1. SQL2016 SP1 does NOT populate the proper fields, and will be fixed in SP2 per the SQL Engineering blog (Look at comments section – blog here)
2. Tired of the warning alerts in my SCOM console

Find the monitors

$Monitor = get-scommonitor | where { $_.DisplayName -like “Service Pack Compliance” } | where { $_.Name -like “*Microsoft.SQLServer.2016.DBEngine*” }

Let’s focus for a second on some differences, and how you can interchange the two depending on what information you know

DisplayName attribute is what you see in the console (note the spaces)

Name attribute typically has dots for the spaces

Override a class

Disable-SCOMMonitor -Class $Class -ManagementPack $MP -Monitor $Monitor

Just in case you need to undo the override

Enable-SCOMMonitor -Class $Class -ManagementPack $MP -Monitor $Monitor

Override a group

$Group = (Get-SCOMGroup -DisplayName “Group*”)

# Enable the group

Enable-SCOMMonitor -Group $Group -ManagementPack $MP -Monitor $Monitor

# Disable the group

Disable-SCOMMonitor -Group $Group -ManagementPack $MP -Monitor $Monitor

Reference Links

Disable-SCOMMonitor https://docs.microsoft.com/en-us/powershell/systemcenter/systemcenter2016/operationsmanager/vlatest/disable-scommonitor

Enable-SCOMMonitor https://docs.microsoft.com/en-us/powershell/systemcenter/systemcenter2016/OperationsManager/vlatest/Enable-SCOMMonitor

Por: Kamal Hathi, Gerente General.

Durante Microsoft Data Insights Summit, James Phillips, Vicepresidente Corporativo de Aplicaciones, Plataforma e Inteligencia (BAPI) en Microsoft, anunció la disponibilidad general de Power BI Premium.

Power BI Premium fue anunciado primero el 3 de mayo de 2017 como el siguiente paso en nuestro compromiso para impulsar a la gente y las organizaciones con acceso a inteligencia crítica. La oferta habilita la distribución de reportes de manera amplia a través de una empresa y a nivel externo, sin requerir que los recipientes tengan licencia de manera individual. Y ya que Power BI Premium consiste en la capacidad en el servicio de Power BI dedicado en exclusiva a una organización, la oferta brinda la flexibilidad de personalizar el desempeño basado en las necesidades de un equipo, departamento u organización.

Power BI Premium está disponible en un rango de tamaños de capacidad, cada uno con diferentes números de núcleos virtuales y tamaños de memoria que pueden escalar conforme cambien los requerimientos, lean el documento técnico de Power BI para más información y exploren la calculadora para ayudarles con la planeación de la implementación de Power BI Premium. Visiten la documentación para detalles de compra.

Power BI Premium incluye la implementación en sitio y la distribución de reportes interactivos de Power BI y reportes paginados tradicionales con Power BI Report Server. Power BI Premium permite el mismo número de núcleos virtuales que una organización dispone en la nube para que también sean implementados en las instalaciones sin la necesidad de dividir la capacidad. Elijan Power BI en la nube o mantengan reportes en sitio con Power BI Report Server y muévanse a la nube a su propio ritmo.

Power BI Report Server ahora está disponible a nivel general como parte de Power BI Premium. Los clientes de SQL Server Enterprise Edition con Software Assurance (SA) activo, tienen los derechos para implementar Power BI Report Server a través de la habilitación de SA. ¡Descarguen hoy la edición de evaluación de Power BI Report Server gratis! Conozcan más sobre las características de Power BI Report Server, regístrense para asistir a nuestro webinar el 28 de junio de 2017 y exploren documentos para más información sobre cómo arrancar.

Adicional a esto, Power BI Premium evoluciona la manera en la que el contenido Power BI es integrado en aplicaciones a través de la convergencia de Power BI Embedded con el servicio de Power BI. Los clientes, socios y la amplia comunidad de desarrolladores pueden aprovechar una superficie de API, un conjunto consistente de capacidades y acceso a las más recientes características con Power BI Premium.

El precio para integrar con Power BI Premium arranca con 625 dólares por mes. Lean más para una lista de SKU y su disponibilidad, así como ayuda para comenzar.

Por último, para mantener el ritmo con la rápida innovación de Power BI, docenas de nuevas características fueron anunciadas durante la conferencia de James, disponible bajo demanda. Visiten los blogs de servicio de Power BI, Power BI Desktop y Power Mobile para conocer más sobre ellos.

Los visuales personalizados de Visio para Power BI estarán disponibles a partir de julio de 2017 en la tienda de visuales personalizados, pero ya están disponibles como versión previa.

Y ofrecimos un vistazo al futuro de Power BI al demostrar las capacidades que llegarán pronto, que incluyen reportes más poderosos que cuentan con páginas personalizadas a través de simulacros, botones de navegación, parámetros con escenarios de supuesto, y marcadores. Más aún, para ayudar a cerrar el ciclo al cambiar información de valor directo a una acción, también mostramos cómo podrán utilizar PowerApps dentro de Power BI para habilitar de manera continua, escritura directo en los reportes de Power BI. Y por último, mostramos cómo Quick Insights tanto en Power BI Desktop como en Q&A ponen IA avanzada en las manos de todos, desde analistas a usuarios finales que hacen preguntas en dispositivos móviles. Como siempre, planeamos mantenernos al día con el increíble ritmo de mejoras y nuevas características por las que es conocido Power BI.

Si no pudieron asistir a Microsoft Data Insights Summit, vean las conferencias y las sesiones especiales bajo demanda para más información sobre Power BI Premium y otros anuncios que se realizaron.

I august 2017 er Danmark vært for det første UNLEASH – Innovation Lab. Microsoft er stolt partner på initiativet, det samler 1000 af de klogeste, unge mennesker i 9 dage Danmark. Projektet går ud på finde holdbare løsninger til 7 af FN’s 17 klimamål og selve setuppet er helt vildt ambitiøst og har fået over 200 partnere til at kaste sig ind i kampen. Indtil 2030 vil der hvert år afholdes en konference i et nyt land med et nyt fokus. Og hver gang er meningen, at der skal komme rigtige løsninger på rigtige problemer ud af det.

Professor i nanoteknologi og formand for Carlsberg Fonden, Flemming Besenbacher, har startet UNLEASH – læs mere om ham her…

Nedenfor er lille snip af, hvad deltagerne skal igennem under de 9 dage i Danmark – læs selv mere på https://unleash.org

“The talents go through a facilitated process of innovation, uniquely tailored by UNLEASH. They form teams to explore real-life challenges within the 7 themes from multiple angles, before defining specific problems and coming up with preliminary solutions. These are tested with leading experts and company partners, then refined, and ultimately presented to peers and panels of judges and mentors.
The SDG Innovation Challenge takes place at 10 Folk High Schools, unique learning institutions located in the Danish countryside. Folk High Schools focus on personal development, open collaboration, and hands-on learning, and these approaches inform the SDG problem-solving to unlock new perspectives.
At the end of this rapid-fire innovation process, each team of Talents have a draft SDG solution, implementation plan, and presentation – getting them ready for the final stage in Aarhus!”

В версии 3.0 файловой системы ReFS, заявленной в Windows Server 2016, появилась функция Block Cloning, оперирующая клонированием файлов на уровне метаданных. Так как ReFS позволяет нескольким файлам использовать одни и те же логические кластеры, то операции по копированию файлов превращаются из перемещения данных на уровне физических кластеров в перемещение данных на уровне логическом.

Коллега Сергей Груздов использовал эту возможность для разработки скриптового решения, практически мгновенно клонирующего файл, размещённый на томе, размеченном в файловой системе ReFS 3.0.

Hi guys, this is Justin from APAC escalation team, in this short article I am going to share a small trick on how to figure out the services hosted in svchost.exe in kernel memory dump.

– Debugger outputs the dump type when we open the dump file.

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

– List all the svchost.exe process in the system.

kd> !process 0 0 svchost.exe
…
PROCESS ffffc0033fe4b780
SessionId: 0  Cid: 1c28    Peb: 5b10682000  ParentCid: 02ec
DirBase: 96c38000  ObjectTable: ffff8607051552c0  HandleCount: <Data Not Accessible>
Image: svchost.exe
…

– Output more information about the svchost.exe we want to check.

kd> !process ffffc0033fe4b780 1
PROCESS ffffc0033fe4b780
SessionId: 0  Cid: 1c28    Peb: 5b10682000  ParentCid: 02ec
DirBase: 96c38000  ObjectTable: ffff8607051552c0  HandleCount: <Data Not Accessible>
Image: svchost.exe
VadRoot ffffc0033fe58620 Vads 241 Clone 0 Private 4527. Modified 5484. Locked 169.
DeviceMap ffff8606fe946fb0
Token                             ffff860706b91060
ElapsedTime                       02:00:58.188
UserTime                          00:00:00.062
KernelTime                        00:00:00.078
QuotaPoolUsage[PagedPool]         141256
QuotaPoolUsage[NonPagedPool]      40560
Working Set Sizes (now,min,max)  (1573, 50, 345) (6292KB, 200KB, 1380KB)
PeakWorkingSetSize                8712
VirtualSize                       2097352 Mb
PeakVirtualSize                   2097352 Mb
PageFaultCount                    17047
MemoryPriority                    BACKGROUND
BasePriority                      8
CommitCharge                      16033

– Here we use the address of VadRoot. VAD is  short for Virtual Address Descriptor. It is a data structure used to describe a section of virtual memory in Windows kernel. We can use !vad command to output all the VADs in a specific process. There are 241 VADs allocated for this process. Because the VADs are organized into a AVL tree, so we can see some extra information about VADs like levels. To figure out the services hosted in this process, the important information here are the mapped dlls. In this process there is a mapped dll named PeerDistHttpTrans.dll and this is a dll for PeerDistSvc service in Windows 10.

2: kd> !vad ffffc0033fe58620
VAD           Level     Start       End Commit
ffffc0033fd73180  7     7ffe0     7ffef     -1 Private      READONLY
ffffc0033fdc0010  6   5b10600   5b107ff     39 Private      READWRITE
ffffc0033db93b30  7   5b10800   5b1087f     12 Private      READWRITE
ffffc0033f9f07e0  5   5b10a80   5b10b7f     11 Private      READWRITE
ffffc0033f577980  7   5b10b80   5b10c7f     11 Private      READWRITE
ffffc0033f62bae0  6   5b10c80   5b10d7f     11 Private      READWRITE
ffffc0033fa22650  7   5b10d80   5b10e7f     11 Private      READWRITE
ffffc0033fc599b0  4   5b10e80   5b10f7f     11 Private      READWRITE
ffffc0033fadb7a0  6   5b10f80   5b1107f     11 Private      READWRITE
ffffc0033fe5d1e0  5   5b11280   5b1137f     11 Private      READWRITE
ffffc0033f7a7fc0  3   5b11480   5b1157f     11 Private      READWRITE
ffffc0033f9f1ee0  7   5b11580   5b115ff     19 Private      READWRITE
ffffc0033fe323d0  6   5b11600   5b1167f     19 Private      READWRITE
ffffc0033f49e1c0  7   5b11680   5b116ff     19 Private      READWRITE
ffffc0033eac72b0  5   5b11780   5b1187f     11 Private      READWRITE
ffffc0033b81b670  6   5b12780   5b127ff     11 Private      READWRITE
ffffc00340cfe720  4   5b12800   5b1287f     11 Private      READWRITE
ffffc003400d42f0  7   5b12880   5b128ff     11 Private      READWRITE
ffffc0034414bdf0  6   5b12900   5b1297f     11 Private      READWRITE
ffffc0033efb5350  7   5b12980   5b129ff     11 Private      READWRITE
ffffc0033b5f34d0  8   5b12a00   5b12a7f     11 Private      READWRITE
ffffc0033fe42610  5  212d92b0  212d92bf      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033d228280  6  212d92c0  212d92c1      0 Mapped       READONLY           Pagefile section, shared commit 0x2
ffffc0033fe38850  7  212d92d0  212d92e5      0 Mapped       READONLY           Pagefile section, shared commit 0x16
ffffc0033fe454a0  2  212d92f0  212d92f3      0 Mapped       READONLY           Pagefile section, shared commit 0x4
ffffc0033fe45290  7  212d9300  212d9300      0 Mapped       READONLY           Pagefile section, shared commit 0x1
ffffc0033fe3f050  6  212d9310  212d9311      2 Private      READWRITE
ffffc0033f7badf0  7  212d9320  212d93e0      0 Mapped       READONLY           WindowsSystem32locale.nls
ffffc0033fc93e70  5  212d93f0  212d93f0      0 Mapped       READWRITE          Pagefile section, shared commit 0x1
ffffc0033f64e0e0  6  212d9400  212d9400      1 Private      READWRITE
ffffc0033fdf2a80  4  212d9410  212d9410      1 Private      READWRITE
ffffc0033f9cd710  6  212d9420  212d9420      0 Mapped       READONLY           Pagefile section, shared commit 0x1
ffffc0033fd00680  5  212d9430  212d9430      0 Mapped       READONLY           Pagefile section, shared commit 0x1
ffffc0033fb1a280  7  212d9440  212d9445      0 Mapped       READONLY           WindowsRegistrationR00000000000d.clb
ffffc0033dcf1a70  6  212d9450  212d945f      1 Private      NO_ACCESS
ffffc0033fe619f0  7  212d9460  212d9460      1 Private      READWRITE
ffffc0033fe6f160  3  212d9470  212d947c      3 Private      READWRITE
ffffc0033fe88520  6  212d9480  212d948f      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033fa7d6c0  5  212d9490  212d949f      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033e9ef190  6  212d94a0  212d94af      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033f85ec40  4  212d94b0  212d94bf      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033fe354b0  6  212d94c0  212d94cf      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033feaef70  5  212d94d0  212d94df      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033fe83d50  6  212d94e0  212d94e0      0 Mapped       READWRITE          Pagefile section, shared commit 0x1
ffffc0033fa3be40  7  212d94f0  212d94f7      8 Private      READWRITE
ffffc0033fdf1e50  1  212d9500  212d95ff    247 Private      READWRITE
ffffc0033fe45040  5  212d9600  212d96bf      0 Mapped       READONLY           Pagefile section, shared commit 0x7
ffffc0033fe362e0  6  212d96c0  212d96cf     16 Private      READWRITE
ffffc0033fe74160  4  212d96d0  212d96dc      2 Private      READWRITE
ffffc0033fadbd90  6  212d96e0  212d96ef      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033f67b7f0  5  212d96f0  212d96ff      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033faebf70  6  212d9700  212d970f      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033dcbd900  3  212d9710  212d971f      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033e1988a0  6  212d9720  212d972f      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033fb2a700  5  212d9730  212d973f      0 Mapped       READWRITE          Pagefile section, shared commit 0x10
ffffc0033d396a40  6  212d9740  212d978e      0 Mapped       READWRITE          Pagefile section, shared commit 0x4f
ffffc0033fe75160  4  212d9790  212d979c      1 Private      READWRITE
ffffc0033feaed40  7  212d97a0  212d97ee     79 Private      READWRITE
ffffc0033f7a2e70  6  212d97f0  212d97ff     16 Private      READWRITE
ffffc0033fe76160  7  212d9800  212d98ff      7 Private      READWRITE
ffffc0033fe3cc60  5  212d9900  212d99ff    241 Private      READWRITE
ffffc0033fe383b0  6  212d9a00  212d9b87      0 Mapped       READONLY           Pagefile section, shared commit 0x7
ffffc0033fded530  2  212d9b90  212d9d10      0 Mapped       READONLY           Pagefile section, shared commit 0x181
ffffc0033fd91740  7  212d9d20  212da118      0 Mapped       READONLY           Pagefile section, shared commit 0x3f9
ffffc0033fdf1330  6  212da120  212da21f      4 Private      READWRITE
ffffc0033fdff490  7  212da220  212da556      0 Mapped       READONLY           WindowsGlobalizationSortingSortDefault.nls
ffffc0033fe77530  5  212da560  212dc561   8193 Private      READWRITE
ffffc0033fe7b770  7  212dc570  212dc66f      1 Private      READWRITE
ffffc0033fe7c880  6  212dc670  212dc771    257 Private      READWRITE
ffffc0033fb0cdc0  7  212dc780  212dc7b5      1 Private      READWRITE
ffffc0033fa8f690  4  212dc7c0  212dc7c0      1 Private      READWRITE
ffffc0033f97e4a0  6  212dc7d0  212dc7d0      1 Private      READWRITE
ffffc0033feb12a0  5  212dc7e0  212dc7e1      2 Private      READWRITE
ffffc0033fe579f0  7  212dc7f0  212dc7f0      1 Private      READWRITE
ffffc0033fda99f0  6  212dc800  212dc8ff    157 Private      READWRITE
ffffc0033fe6d280  3  212dc900  212dc9ff     76 Private      READWRITE
ffffc0033fdff7a0  7  212dca00  212dcb11    274 Private      READWRITE
ffffc0033fe4e420  6  212dcb20  212dcc1f    256 Private      READWRITE
ffffc0033fe83c10  7  212dcc20  212dcd1f    256 Private      READWRITE
ffffc0033d3968a0  5  212dcd20  212dce1f    256 Private      READWRITE
ffffc0033fea3aa0  7  212dce20  212dcf1f    256 Private      READWRITE
ffffc0033dcf4790  6  212dcf20  212dcf2f     16 Private      READWRITE
ffffc0033f9e5870  7  212dcf30  212dcf37      8 Private      READWRITE
ffffc0033f8aa260  4  212dcf40  212dcf41      2 Private      READWRITE
ffffc0033f923470  7  212dcf50  212dcfaf      0 Private      READWRITE
ffffc0033eb14300  6  212dcfb0  212dcfb1      2 Private      READWRITE
ffffc0033be8fcc0  7  212dcfc0  212dcfc0      1 Private      READWRITE
ffffc0033feaff70  5  212dcfd0  212dcfdf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fe09c30  6  212dcfe0  212dcfef      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fec3490  7  212dcff0  212dcfff      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fe58620  0  212dd000  212dd0ff    233 Private      READWRITE
ffffc0033daa28d0  7  212dd100  212e10ff   3027 Private      READWRITE
ffffc0033eb2a270  6  212e1100  212e1293    404 Private      READWRITE
ffffc0033e198800  7  212e12a0  212e13f3      0 Mapped       READONLY           Pagefile section, shared commit 0x154
ffffc0033f9d3b90  5  212e1400  212e14ff      1 Private      READWRITE
ffffc0033fb135b0  7  212e1500  212e1a0f      2 Private      READWRITE
ffffc0033fec28f0  6  212e1a10  212e1a1f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fe57f70  7  212e1a20  212e1a2f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fe57ed0  4  212e1a30  212e1a3f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fe57e30  7  212e1a40  212e1a4f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fad7f70  6  212e1a50  212e1a5f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fad7ed0  7  212e1a60  212e1a6f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fad7e30  5  212e1a70  212e1a7f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fad7d90  7  212e1a80  212e1a8f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033a890010  6  212e1a90  212e1a9f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033a890200  7  212e1aa0  212e1aaf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033a890160  3  212e1ab0  212e1abf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033a8900c0  7  212e1ac0  212e1acf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033feb4010  6  212e1ad0  212e1adf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fc368c0  7  212e1ae0  212e1aef     16 Private      READWRITE
ffffc0033feafa90  5  212e1af0  212e1aff     16 Private      READWRITE
ffffc0033fad7c20  7  212e1b00  212e1b0f     16 Private      READWRITE
ffffc0033feb40e0  6  212e1b10  212e1b1f     16 Private      READWRITE
ffffc0033fec57a0  7  212e1b20  212e1b2f     16 Private      READWRITE
ffffc0033f71bd40  4  212e1b30  212e1b37      8 Private      READWRITE
ffffc0033f71bca0  7  212e1b40  212e1b4f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fecdcf0  6  212e1b50  212e1b5f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fecdca0  7  212e1b60  212e1b6f     16 Private      READWRITE
ffffc0033fec57f0  5  212e1b70  212e1b7f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fecf8f0  7  212e1b80  212e1b87      8 Private      READWRITE
ffffc0033fecce00  6  212e1b90  212e1b97      8 Private      READWRITE
ffffc0033fa92b30  7  212e1ba0  212e1baf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fa655a0  2  212e1bb0  212e1bbf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033f8e2660  7  212e1bc0  212e1bcf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fee4a10  6  212e1bd0  212e1bdf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033feb4d30  7  212e1be0  212e1bef      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033feb4bb0  5  212e1bf0  212e1bff      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fed34f0  7  212e1c00  212e1c0f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistRepubPeerDistRepubStoreCatalog.pds
ffffc0033fb0b3c0  6  212e1c10  212e1c10      1 Private      READWRITE
ffffc0033faa11d0  7  212e1c20  212e1c20      1 Private      READWRITE
ffffc0033fb3b640  4  212e1c30  212e1dc3    404 Private      READWRITE
ffffc0033f9481d0  7  212e1dd0  212e1dd1      2 Private      READWRITE
ffffc0033eac29c0  6  212e1de0  212e1de0      1 Private      READWRITE
ffffc0033e7fe2a0  7  212e1df0  212e22ff      1 Private      READWRITE
ffffc0033fec7c80  5  212e2300  212e2307      8 Private      READWRITE
ffffc0033d341560  7  212e2310  212e2311      2 Private      READWRITE
ffffc0033fed29d0  6  212e2320  212e237f      0 Private      READWRITE
ffffc0033f97a550  7  212e2380  212e2381      2 Private      READWRITE
ffffc0033fab8bc0  3  212e2390  212e2390      1 Private      READWRITE
ffffc0033fee74e0  7  212e23a0  212e23af      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033febdf70  6  212e23b0  212e23bf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033fec33f0  7  212e23c0  212e23cf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033e9ef0f0  5  212e23d0  212e23df      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033fec7eb0  7  212e23e0  212e23ef      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033fee6760  6  212e23f0  212e23ff      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033fee45e0  7  212e2400  212e240f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033feeb890  4  212e2410  212e241f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033feba450  8  212e2420  212e242f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033feb7cc0  7  212e2430  212e243f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033feb7c20  8  212e2440  212e244f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033feb7b80  6  212e2450  212e245f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033fee6010  8  212e2460  212e246f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033fee61d0  7  212e2470  212e247f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033fee6130  8  212e2480  212e248f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033feeceb0  5  212e2490  212e249f      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033feece10  8  212e24a0  212e24af      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033feecd70  7  212e24b0  212e24bf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033feeccd0  8  212e24c0  212e24cf      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033fed9970  6  212e24d0  212e24df      8 Mapped       READONLY           WindowsServiceProfilesNetworkServiceAppDataLocalPeerDistPubPeerDistPubCatalog.pds
ffffc0033fd2dc20  7  212e2500  212e25ff     51 Private      READWRITE
ffffc0033fe38990  1 7df5ff0b0 7ff5ff0af      1 Mapped       NO_ACCESS          Pagefile section, shared commit 0
ffffc0033fde53d0  8 7ff69d760 7ff69d85f      0 Mapped       READONLY           Pagefile section, shared commit 0x5
ffffc0033fe388f0  7 7ff69d860 7ff69d882      0 Mapped       READONLY           Pagefile section, shared commit 0x23
ffffc0033fde56e0  6 7ff69da60 7ff69da6d      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32svchost.exe
ffffc0034435b210  8 7ff8ecca0 7ff8ecce1      6 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32adsldp.dll
ffffc0033fe56a90  7 7ff8ed080 7ff8ed094      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32OnDemandConnRouteHelper.dll
ffffc0033dd1e400  8 7ff8ee920 7ff8eec11     13 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32esent.dll
ffffc0033fe750c0  5 7ff8f1120 7ff8f112c      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32httpapi.dll
ffffc0033fdff260  7 7ff8f7910 7ff8f7951      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32adsldpc.dll
ffffc0033fb0c870  8 7ff8f8830 7ff8f8841      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32PeerDistHttpTrans.dll
ffffc0033fe8c3d0  6 7ff8f8ac0 7ff8f8b69      7 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32WSDApi.dll
ffffc0033fcb0290  8 7ff8f8b70 7ff8f8ba1      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32PeerDistWSDDiscoProv.dll
ffffc0033faebc50  7 7ff8f8bb0 7ff8f8bd6      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32ddptrace.dll
ffffc0033faebcf0  8 7ff8f8be0 7ff8f8c1c      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32ddpchunk.dll
ffffc0033fe83a80  4 7ff8f8c20 7ff8f8e00      5 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32PeerDistSvc.dll
ffffc0033fe70260  6 7ff8f99c0 7ff8f9a04      7 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32activeds.dll
ffffc0033feab6a0  7 7ff8fcc20 7ff8fcc2d      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32npmproxy.dll
ffffc0033fe6ac30  5 7ff8fd570 7ff8fd5a6      8 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32fwpolicyiomgr.dll
ffffc0033fc42180  7 7ff8fd5d0 7ff8fd605      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32netprofm.dll
ffffc00340a763c0  8 7ff8fd7c0 7ff8fd7c9      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32rasadhlp.dll
ffffc0033fdfed30  6 7ff8fddc0 7ff8fddd7      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32netapi32.dll
ffffc00343920be0  8 7ff8fe350 7ff8fe35c      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32dsparse.dll
ffffc0033dd56cd0  7 7ff8fe8b0 7ff8fe8bd      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32PeerDistAD.dll
ffffc0033de49800  8 7ff8fea30 7ff8fea65      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32xmllite.dll
ffffc0033fded410  3 7ff901310 7ff90131a      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32ktmw32.dll
ffffc0033fcb86e0  7 7ff901a80 7ff901a99      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32dhcpcsvc.dll
ffffc0033fde5d80  6 7ff901c10 7ff901c25      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32dhcpcsvc6.dll
ffffc0033e9ef730  8 7ff902410 7ff9024dc      5 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32winhttp.dll
ffffc0033b006250  7 7ff902f30 7ff902f99      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32FWPUCLNT.DLL
ffffc0033ebe1910  8 7ff9032d0 7ff9032da      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32winnsi.dll
ffffc0033fe694f0  5 7ff9032e0 7ff90331d      5 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32logoncli.dll
ffffc0033fe8a940  6 7ff9036d0 7ff903731      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32wevtapi.dll
ffffc0033fe68d60  7 7ff904680 7ff9046a6      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32sppc.dll
ffffc0033f9e4430  4 7ff9046b0 7ff9046d5      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32slc.dll
ffffc0033d33b350  7 7ff9049c0 7ff9049ea      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32fwbase.dll
ffffc0033d2cee10  6 7ff904c40 7ff904cc5      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32FirewallAPI.dll
ffffc0033fe6c420  5 7ff904ed0 7ff904ef2      5 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32gpapi.dll
ffffc0033fe29f70  6 7ff905100 7ff905113      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32wldp.dll
ffffc0033fe6f3f0  2 7ff9051a0 7ff9051e9      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32authz.dll
ffffc0033fe7e260  8 7ff905330 7ff90533b      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32secur32.dll
ffffc0033fb56930  7 7ff905450 7ff905482      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32rsaenh.dll
ffffc0033dd0ceb0  8 7ff905610 7ff905760      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32webservices.dll
ffffc0033fe70d20  6 7ff9058f0 7ff905927      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32IPHLPAPI.DLL
ffffc00340dc8920  8 7ff905930 7ff9059d0      5 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32dnsapi.dll
ffffc0033fe69590  7 7ff9059e0 7ff9059ec      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32netutils.dll
ffffc0033fe75010  8 7ff9059f0 7ff905a0e      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32userenv.dll
ffffc0033fcba9e0  5 7ff905b60 7ff905bbb      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32mswsock.dll
ffffc0033b480750  7 7ff905bc0 7ff905caf     12 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32kerberos.dll
ffffc0033fdfe760  6 7ff905d20 7ff905d2a      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32cryptbase.dll
ffffc0033fe42310  4 7ff905d40 7ff905d56      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32cryptsp.dll
ffffc00343bcf230  8 7ff905d60 7ff905d74      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32cryptdll.dll
ffffc0033fe6f350  7 7ff905e60 7ff905e8a      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32bcrypt.dll
ffffc0033fca04c0  6 7ff905f80 7ff905fab      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32sspicli.dll
ffffc0033b4ab520  7 7ff906150 7ff9061e7      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32sxs.dll
ffffc0033fe75bf0  5 7ff906280 7ff906293      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32profapi.dll
ffffc0033fb0e6d0  8 7ff9062a0 7ff9062ae      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32kernel.appcore.dll
ffffc0033fde5590  7 7ff9062b0 7ff9062bf      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32msasn1.dll
ffffc0033fe8f6c0  6 7ff9062c0 7ff90630b      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32powrprof.dll
ffffc0033faaa9c0  7 7ff906310 7ff906491      8 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32gdi32full.dll
ffffc0033fe4e1d0  3 7ff9064a0 7ff906594      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32ucrtbase.dll
ffffc0033fe2fcf0  8 7ff9065a0 7ff9065f4      3 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32wintrust.dll
ffffc0033faa14a0  7 7ff906650 7ff9066b9      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32bcryptprimitives.dll
ffffc0033fe3c8b0  6 7ff906770 7ff90698c      8 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32KernelBase.dll
ffffc0033fe32500  7 7ff906990 7ff906b58     10 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32crypt32.dll
ffffc0033f980380  8 7ff906b60 7ff906bfb      6 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32msvcp_win.dll
ffffc0033fe75c90  5 7ff906cb0 7ff906ccd      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32win32u.dll
ffffc0033faaa920  8 7ff9073b0 7ff907514      6 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32user32.dll
ffffc0033fe66d20  7 7ff907520 7ff907589      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32ws2_32.dll
ffffc0033fe71260  8 7ff907590 7ff9075eb      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32Wldap32.dll
ffffc0033f9e2f10  6 7ff907610 7ff9076ce      6 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32oleaut32.dll
ffffc0033fb0d200  7 7ff9077d0 7ff90786e      9 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32clbcatq.dll
ffffc0033f4f3280  4 7ff907870 7ff90791a      5 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32kernel32.dll
ffffc0033fde5990  7 7ff909080 7ff9090d8      5 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32sechost.dll
ffffc0033fe4a160  8 7ff9090e0 7ff9090e7      2 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32nsi.dll
ffffc0033fe88350  6 7ff909290 7ff909331      9 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32advapi32.dll
ffffc0033fe81a80  7 7ff909370 7ff9094a6      6 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32ole32.dll
ffffc0033fe426c0  5 7ff9094b0 7ff90954d     10 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32msvcrt.dll
ffffc0033faa1400  8 7ff909550 7ff909583      4 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32gdi32.dll
ffffc0033fe37590  7 7ff909590 7ff909857      9 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32combase.dll
ffffc0033fe8a350  6 7ff909cf0 7ff909e10      5 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32rpcrt4.dll
ffffc0033fde5640  7 7ff909e20 7ff909ff0     14 Mapped  Exe  EXECUTE_WRITECOPY  WindowsSystem32ntdll.dll
Total VADs: 241, average level: 7, maximum depth: 8
Total private commit: 0x3e1c pages (63600 KB)
Total shared commit:  0x7a3 pages (7820 KB)

-Justin