Many of you have already seen the announcement that Configuration Manager can now be set up to sync Office 365 ProPlus updates directly.  This scenario is a direct response to requests for control of distributing these updates, and is an improvement on the past model (wherein Office 365 ProPlus updates circumvented Microsoft Update and WSUS altogether); however, there may be a nonzero cost to WSUS administrators that do not use Configuration Manager.  This post discusses how to mitigate that cost if you are affected by the change.

The Office 365 Client category now appears in the WSUS Products and Classifications pane:

If you’ve configured WSUS to sync this content, then you’ll see new updates in the console:

Deploying these updates without Configuration Manager is not supported, so the content described above is essentially useless to a WSUS standalone administrator.  Depending on your situation, we recommend that you take one of the following actions:

1. Deselect the Office 365 Client product so that WSUS does not sync this content from Microsoft Update. 

2. For those running Small Business Server or other flavors that do not allow product filtering, decline all updates for the Office 365 Client product, which can be identified by the update title.

Please let us know if there are any questions on this new content in WSUS.

BizTalk 2016 CTP 1 was released by the product group.

What is new in BizTalk 2016? :

reference : https://msdn.microsoft.com/en-us/library/mt670742

To be a part of the pre-release customer engagement program and more details of the announcement , look here : https://blogs.msdn.microsoft.com/biztalk_server_team_blog/2016/03/30/announcing-biztalk-server-2016-community-technology-preview-1/

Additionally, HIS (Host Integration Server) 2016 CTP1 was also released.

What's new with HIS 2016? https://msdn.microsoft.com/en-us/library/mt670807

Apr.

14

Script Download:  
The script is available for download from https://gallery.technet.microsoft.com/scriptcenter/How-to-create-partition-2f6147a7.

You can also use  Microsoft Script Browser for Windows PowerShell ISE to download the sample with one button click from within your scripting environment. 

This script demonstrates how to create partition table quickly in SQL Server, using the script that you will be able to generate the code needed to create a partition table.

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

Listen up educators from around Dunedin! Microsoft is coming your way!

Our Teacher Ambassadors will be in Dunedin on Wednesday 20th April 2016 at Taieri College. They will be doing a free all-day session there and all educators/teachers are welcome to come along!

In case you haven't been to a Teacher Ambassador session before I'll give you a brief overview. They provide Microsoft in the Classroom sessions that help educate you about technology and how Microsoft can benefit your classrooms & schools. These sessions are great at getting you up to speed with all the Microsoft has to offer in an educational scenario. You'll learn some great tips & tricks that could help you or you may even learn something entirely new. If you have been to these sessions before but still have questions they can help answer them! On this particular day some of the potential sessions include breakout sessions about OneNote, Office365, Class Notebook & Sway amongst others. If you would like to learn a bit more about who the Teacher Ambassadors are and what they do you can check out their website.

To RSVP to this all-day session please email: t-jegilb@microsoft.com and make sure to include your name, school, role and contact number. Get in quick so you don't miss out on this wonderful opportunity!

Don't worry other educators who are not from around Dunedin we are in the process of finalising other sessions around New Zealand so hopefully you will not miss out!

We hope you have had a wonderful first term and we look forward to seeing you all in Dunedin!

Olá Wiki Ninjas Brasil.

Sejam muito bem-vindos a mais uma Wiki Life.

Muitos dos que visitam o TechNet Wiki já devem ter se deparado com artigos que possuem em seu início uma tabela de conteúdo (recurso também conhecido como “table of contentes” ou, simplesmente, “TOC”), como indicado no exemplo a seguir:

Além de contar com atalhos que possibilitam a navegação até uma parte específica do texto, uma tabela de conteúdo permite ainda se obter uma visão rápida dos diferentes tópicos que compõem um artigo. Trata-se, portanto, de uma boa prática a adoção deste tipo de mecanismo, sobretudo considerando sua presença em outros sites baseados no conceito de Wiki.

No artigo a seguir estão os passos necessários para a correta utilização de tabelas de conteúdo em artigos:

http://social.technet.microsoft.com/wiki/pt-br/contents/articles/16675.wiki-como-inserir-uma-table-of-contents-toc.aspx

Caso ainda não seja um autor e tenha interesse em contribuir com o TechNet Wiki, reiteramos mais uma vez o convite para participar desta iniciativa. No link abaixo podem ser obtidos maiores esclarecimentos:

http://blogs.technet.com/b/wikininjasbr/archive/2016/01/06/quarta-feira-wiki-life-como-usar-o-editor-do-technet-wiki.aspx

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

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

“Why FIM/MIM MA is slow” is one of the most frequent questions we’ve got from our customers. It’s actually a board topics which has various causes. Before we dig into to the details, it is quite necessary for us to clarify below two checkpoints.

1. Which particular run profile is slow?

     As we all know, there are three type run profiles for every Management Agent and so does FIMMA. Every run profile type involves different components. And pay attention to the different interfaces leveraged by import and export profile.

2. How we define slow?

    When we mention “slow”, it could be general or slower. So it’s important to have a baseline of the FIMMA’s performance by collecting the perf counters under FIM 2010 Namespace.

Then you probably ask what kind of performance is expected? The answer is it depends on several elements like the typology, the scale, server config and sql instance config. That’s why you need setup your own baseline , the more frequent you inspect on this, the more accurate is your FIM solution’s baseline. And Microsoft Product team do publish a testing result on small profile and medium profile separately as a reference.

So next time, instead of saying “FIMMA is slow”, you shall more specific about “Which run profile of FIMMA is slow to what extend”.

Continue with the “Why FIM/MIM MA is slow?Part 1”, we will discuss the most often case “the slowness on FIMMA export”. Based on my field experience, the average performance for export on FIMMA is around 10 objects/sec.  You probably need some investigation if yours is far beyond the average or it can not meet the high-level business requirement.

You may or may not aware since FIM 2010 R2, it introduces the Composite Request to allow to export a batch changes to the FIM Service. The FIM MA export is configured by default to use an asynchronous, batch-request evaluation mode for requests created by the FIM Synchronization engine account. And we do allow you to control the behavior in the miiserver.exe.config under %FIMInstallDirectory%\2010\Synchronization Service\Bin

However the perquisite of this mode is all changes in the composite request must succeed in order for the changes to be applied.  Let’s say under the default config, all the 1000 attribute changes (aggregationThreshold) must succeed otherwise it falls back to the single mode for the batch. Below are the screenshots for the success and failed scenarios separately.

So there are below two best practices based on this mechanism which may help you improve the FIMMA export performance.

1. Try to fix these errors/bad data happened during export.

2. Tune the batch size (aggregationThreshold) to reduce the chance of failed batches.

Part of the very interesting services in Azure we have Log Analytics (used to be called Operational Insights).

In a matter of minutes (1 click) you create an A to Z infrastructure in Azure that will gather important data from all your servers (sent by an agent), store this data even if it is a big amount, and give you a very detailed analysis report via “Intelligence Packs” regarding the health in general. The solution has Packs for AD, SQL.. but also will track change management, event logs, event network traffic.

In a matter of minutes, you know the health of your internal IT, especially the gap between experts recommendations and your current configuration. This solution gives you in real time vision, gives you a clear vision of the impact for each missing recommendation, and also tells you how to fix thise problems. Once you know where the problems are, you can build an action plan, and have a better security and performance for your users, customers and businesses.

The FREE version of Log Analytics  will just keep your data 7 days and will limit to 250Mb the amount of data sent per day, but it is far sufficient to have a quick analyzis and realize how “close” or “far” you are from these recommendations. Focus on key components such as domain controllers, file servers, SQL databases.. etc.

Swith from FREE to STANDARD in one click, no more “per day limitation”, one month of log for a few euros every months. Swith to PREMIUM, you will keep your data 1 year.

Here is the portal you get after a few minutes. Each “square” is an intelligent pack (there are many others, but screen is too small to display them all ;-)

Now the goal of this post …

In the portal, you can add multiple users to the workspace, so can “delegate” the view to internal or external users, such as a partner.

Part of this enrolment process, Log Analytics will send a “validation” email to the user you want to grant access. This user will click the link in the email to validate and get access to the portal.

I have noticed for now a few days, that sometimes, when you click this link to get this bad error : internal Error.

After quick investigation, it seem that “Safelink” used by Outlook to identify risky URL is causing this problem.

As a very easy work around, when you are on this error page just go to this URL : http://mms.microsoft.com.

It will finish the enrolment process, and job will be done.

I suspect that the problem will soon disappear, so here is a quick workaround.

Log Analytics is a must to see, test it now !!

At Microsoft UK we are incredibly proud of our partner ecosystem and the role you all play in helping our customers have great experiences with Microsoft products and services.

We are conducting our very first impact study which we hope will provide valuable insights into the contribution Microsoft has on the British economy alongside our partners. With a survey designed to collect valuable insights from our partners about the forces shaping the new way of doing business, the speed in which our partners are adapting, and the economic impact of promoting IP-led services and solutions in the United Kingdom.

This study not only covers the economic impact to the UK but also will provide you with a local benchmark for your organisation across sales, marketing and technical skills and may assist in discovering other areas of opportunities in the local market.

We need your help!

You may have received an email from jyap@capitalis.com.au - the agency that is conducting this study on behalf of Microsoft, inviting you to participate. If you are keen to participate and have not yet received an invitation click here to receive your personalised URL. Please click on the link and follow the instructions once you have received the invitation. The survey will take approximately 20 minutes to complete. You will need knowledge of your company’s financial records for FY15. Please forward this invite to someone else in your company if you feel they would be better placed to complete the survey. We understand the time pressures all of you are facing and, as the success of this research is heavily dependent on your input.

A report, outlining the results of the survey will provide participants with a rich source of benchmarking information and current market insight via a comparative analysis of various business elements impacting the “partner of the future”. As a gesture of appreciation, this report (valued at £250GBP) will be shared with all partners who contribute to this research.

To say thank you for your time invested we are offering those who complete the survey the chance to win, via a game of skill, one of three tickets to the Worldwide Partner Conference 2016 (WPC) valued at $1995USD per ticket.

We'd love your input to help us better shape our partner eco-system so thank you in advance for participating.

Please note: this research is being conducted on behalf of Microsoft by Capitalis, a strategic marketing consultancy, who have been partnering with Microsoft for over 10 years. The information you provide will be treated as strictly confidential by Capitalis, and personal and company-specific data will not be shared with any third party, including Microsoft. Only non-identifiable, aggregated data will be shared with Microsoft, Microsoft’s Partners and more broadly.

こんにちは、日本マイクロソフト System Center Support Team の久保です。

Data Protection Manager (DPM) の運用を行うなかで、ウイルス対策ソフトとの競合によりバックアップが失敗するという事象が発生することがございます。
事象発生の予防や、バックアップ失敗時に切り分けの一つとして、ウイルス対策ソフトの除外設定についてご紹介いたします。

一般的に、DPM がウイルス対策ソフトより受ける影響には、以下のシナリオがございます。

1. DPM エージェント (DPMRA.exe) のプロセスの動作を全て監視することで、全ファイルへアクセスのモニタリングが発生する。これにより、DPM のバックアップ パフォーマンスが悪化するとともに、余分な I/O 負荷も発生する。
2. DPM エージェントの変更点をバックアップするという動作において、保護対象側でバックアップが必要と判断したファイルを、ウイルス対策ソフトがウイルスと認識した場合に、ドライバ レベルで該当ファイルへのアクセスを拒否することで、バックアップに失敗する。
3. DPM サーバー側のレプリカ ボリュームのファイルをウイルス対策ソフトが削除してしまい、保護対象側の変更点が反映出来なくなり、バックアップに失敗する。

- 「クリーンアップ」や「検疫」について -

上記シナリオ 2 や 3 につきまして、「クリーンアップ」や「検疫」といったウイルス対策ソフト固有の、ファイル削除以外の方法による安全なファイル保持方法を使用した場合には、ファイルは存在するものの、ファイルへのアクセスはブロックする、といった処理がウイルス対策ソフトのフィルタ ドライバ レベルで行われる場合がございます。
DPM は同期を行う際に、保護対象においてどのファイルがいつ変更されたのかというリスト (変更ジャーナル) を参照し、全てのファイルの変更点をバックアップしております。しかし、このようなウイルス対策ソフトによる一部のファイルに対するブロックが行われた場合には、同期処理に異常が発生し、バックアップを行う事は出来ません。
同期においては、前回の同期や整合性チェック以降、保護対象においてどのような変更が発生したのかをブロック単位で監視しているため、上記 シナリオ 2 や 3 のシナリオが発生した場合には、レプリカボリュームと保護対象の差分の監視の結果に不整合が発生し、同期は行えず、整合性エラーが検知されることとなります。
また、整合性エラー発生にともなう整合性 チェックを実施した際に、バックアップすべきファイルがウイルス対策ソフトからブロックされた場合、整合性チェックは失敗します。

- 「隔離」処理について -

「隔離」処理の実装に依存いたしますが、DPM のバックアップ対象外のボリュームに対してファイルを隔離し、DPM のバックアップ対象のボリュームからは削除する場合には上記のようなバックアップの問題は起きないものと考えられます。
一方で、DPM のバックアップ対象のボリュームに、隔離されたファイルが残されておりドライバ レベルでのアクセスが排他処理されてしまうケースではバックアップに失敗します。

以上の内容を踏まえた上で、以下の設定を実施して下さい。

- ウイルス対策ソフトの設定について -

以下のプロセスとパスについて、ウイルス対策ソフトより除外する必要がございます。
詳細な設定手順についてはウイルス対策ソフトにより様々ですので、ウイルス対策ソフトのヘルプをご確認いただくか、作成元に手順をご確認ください。

A. DPM 関連プロセス・フォルダ のリアルタイム監視除外
B. csc.exe の除外
C. レプリカ の パスの除外
D. ウイルスと判断されたファイルの「削除」設定

※ このブログ上で"<DPM のインストール パス>" と記載されているパスは、バージョンやインストール方法によって異なります。既定では以下の通りです。

DPM 2007   : C:\Program Files\Microsoft DPM\
DPM 2010   : C:\Program Files\Microsoft DPM\
DPM 2012   : C:\Program Files\Microsoft System Center 2012\DPM\
DPM 2012 R2: C:\Program Files\Microsoft System Center 2012 R2\DPM\

A. DPM 関連プロセス・フォルダの リアルタイム監視除外
==========================================

DPM サーバー、および DPM の保護対象にてウイルス対策ソフトを導入する場合は DPMRA.exe のリアルタイム モニタリングを無効にします。
また、保護されたすべてのデータ ソースのレプリカに対するリアルタイム モニタリングを無効にします。

DPMRA.exe のパスをご確認の上、除外設定を行ってください。
なお、既定では DPMRA.exe は以下のパスに配置されます。

● DPM サーバー上
-------------------------------

　<DPM のインストール パス>\DPM\bin\DPMRA.exe

● 保護対象サーバー上
-------------------------------

　C:\Program Files\Microsoft Data Protection Manager\DPM\bin\DPMRA.exe 

また、DPM 2010 以降のバージョン (DPM 2010 / 2012 / 2012 R2) におきましては、以下のパス配下もリアルタイム監視から除外いただくことを推奨いたします。

※ DPM サーバーおよび保護対象サーバー上の両方にて設定を行ってください。 

<DPM のインストール パス>\DPM\XSD
<DPM のインストール パス>\DPM\Temp\MTA

~ 参考資料 ~

> You receive job status failure messages in Data Protection Manager
http://support.microsoft.com/kb/928840/en-us

B. csc.exe について
==========================================

DPM サーバーにおいて、DPM 管理者コンソールの使用中にパフォーマンスが低下するといった場合に備え、C# コンパイラである csc.exeプロセスが生成するファイルを、ウイルス対策ソフトがスキャンしないよう csc.exe プロセスのリアルタイム モニタリングを無効にします。
DPMRA.exe 同様に、csc.exe のパスをご確認の上、除外設定を行ってください。なお、既定では csc.exe は以下のパスに配置されます。

※ 保護対象においては当該設定は不要です。
C:\Windows\Microsoft.net\Framework\v2.0.50727\csc.exe 

~ 参考資料 ~

> Data Protection Manager 2007 の展開計画
http://download.microsoft.com/download/7/B/5/7B570775-83A6-45F9-88AA-B81527B6EE42/DPMv2Planning.doc
#「ウイルスのリアルタイム モニタリングの構成」(P.66) をご参考下さい。なお、本内容は、DPM 2010 および DPM 2012 R2 についても同様でございます。

C. レプリカのパスについて
==========================================

保護された全てのデータソースのレプリカのパスは以下の手順で確認します。
ウイルス対策ソフトで除外設定をする場合は、以下の手順にてパスを確認し、設定くださいますようお願いいたします。

● レプリカのパスの確認方法
-------------------------------

1. DPM 管理者コンソールを起動します。
2. ナビゲーション バーで、[保護] をクリックします。
3. 保護対象のデータソースを選択すると画面下の [詳細] の項に [レプリカのパス ： クリックすると詳細が表示されます。] と表示されますので、クリックします。 

例: 以下のようにレプリカ ボリュームのパスがございます。
(マウント ポイントを使用して“<DPM のインストール パス>\DPM\Volumes\Replica\" 配下にマウントされております。)

c:\Program Files\Microsoft DPM\DPM\Volumes\Replica\MOSSDB.contoso.local\File System\E-9af215e2-ead8-11dd-a8ea-00155dd94c04\677656bd-580b-4fa8-8dd4-0c6a046ace88\Full\ 

4. 表示された [レプリカのパスの詳細] ダイアログボックスに表示されたパスをウイルス対策ソフトウェアのリアルタイム モニタリング除外対象として登録します。

D. ウイルスと判断されたファイルの「削除」設定
==========================================

ウイルス対策ソフトウェアによりウイルスと判断されたファイルについては、削除するよう設定して下さい。
※ DPM 側からは一般的にこういったウイルス対策ソフトの影響が考えられる場合は「隔離」オプションを「削除」に変更していただく必要がございます。

※ 今回ご紹介する設定を実施していただいても、ウイルス対策ソフトの影響を完全に除外することができない可能性もございます。

上記設定を実施していただいても事象が改善しない場合で、ウイルス対策ソフトのドライバ レベルでの影響が考えられる場合には、切り分けとしてウイルス対策ソフトのサービスを停止してただいたうえで、様子をご確認ください。本切り分けにて事象が改善された場合には、ウイルス対策ソフトのアンインストールの実施をお願い致します。

なお、この場合にはウイルス対策ソフトのアンインストール以外による対処方法はございませんので、あらかじめご承知くださいますようお願い申し上げます。

> DPM サーバーでのウイルス対策ソフトウェアの実行
https://technet.microsoft.com/ja-jp/library/hh757911(v=sc.12).aspx

Nous avons récemment annoncé 2 informations qui me paraissent pertinentes sur Windows 10, je me permets donc de vous les partager.

1. Un lien https://www.microsoft.com/en-us/WindowsForBusiness/windows-roadmapintitulé « Roadmap Windows 10» est maintenant disponible afin de vous permettre de savoir ce qui a été récemment ajoutés, ce qui est en cours de développement et les fonctionnalités qui aurait pu être annulée.

2. La mise à disposition de la build 1511 dans le ring CBB.

La build 1511 qui était déjà disponible pour les PC configurés en Current Branch depuis Novembre est maintenant disponible pour les PC configurés en Current Branch for Business.

Pour rappel, la CBB n’est pas une branche différente mais uniquement un niveau de maturité qui apparait suffisant à Microsoft pour un déploiement généralisé en entreprise.

Nous vous recommandons de commercer à tester cette version si cela n’est pas déjà fait.

https://technet.microsoft.com/fr-fr/windows/mt679505.aspx?ocid=wc-ext-aka

Un nouvel ISO Windows 10 1511 sera prochainement disponible incluant la mise à jour de Mars 2016 (KB 3140768), cependant vous pouvez arriver au même résultat en injectant manuellement la mise à jour de mars dans votre processus de déploiement.

Si vous êtes intéressés par ce type d’information, n’hésiter à pas à me suivre sur Twitter

N’hésitez pas à revenir vers votre TAM si vous souhaitez un complément d’information.

Today’s Tip…

To disable ActiveSync for users by using Exchange Online PowerShell, follow these steps:

1. Connect to Exchange Online by using remote PowerShell. For more information about how to do this, go to the following Microsoft website:
   Connect to Exchange Online using remote PowerShell
2. Do one of the following:

• To disable ActiveSync connectivity for a single user, run the following command:
  Set-CASMailbox -Identity <Mailbox ID> -ActiveSyncEnabled $False
• To disable ActiveSync connectivity for a group of users, use the Get-User cmdlet to change the scope of the command.
  For example, to disable ActiveSync for all the users in the Sales department, run the following command:
  Get-User -RecipientTypeDetailsUserMailbox | where {$_.Department -eq "Sales"} | Set-CASMailbox -ActiveSyncEnabled $False
• To disable ActiveSync for all users in an organization, run the following command:
  Get-Mailbox | Set-CasMailbox -ActiveSyncEnabled $False

Exchange Admin Center

To disable ActiveSync for users in Office 365 by using the Exchange admin center, follow these steps:

• Sign in to the Office 365 portal (https://portal.office.com) as a global admin.
• Click Admin, and then click Exchange.
• In the left navigation pane, click recipients, and then click mailboxes.
• Select the user mailbox that you want to change, and then click Edit
• Click mailbox features, and then click Disable Exchange ActiveSync.

• Click OK.

Embora muitos de nossos colaboradores da comunidade percebam que não exista integração entre fórum e wiki, saibam que ela existe sim e é bem comum. Apenas para destacar um ponto importante, o conselho da comunidade trata esse tópico como uma das áreas de conhecimento dos Wiki Ninjas. As áreas de conhecimento tem a função de direcionar, ou seja, dar um norte a todas as atividades que ocorrem dentro da comunidade. Todas as áreas de conhecimento e seus responsáveis podem ser localizadas acessando o artigo - "Conselho da comunidade TechNet Wiki: Áreas de Foco" pelo endereço:

Dentro deste espaço - "TechNet Wiki Discussion" o nosso objetivo é receber os feedbacks dos membros da comunidade, tratar problemas, propor melhorias, moderar questões sobre o tema e responder a dúvidas pertinentes ao Wiki. Todas essas ações, são possíveis mediante as questões observadas por nossa comunidade. O local onde buscamos essas informações para justamente sempre melhorar o nosso Wiki é o fórum exclusivo criado especificamente para tratar toda esta gama de assuntos. Ele está disponível para acesso no link:

O acesso é aberto a todos os membros, independente do seu nível de contribuição (medalhas, pontos e tempo de contribuição na comunidade) ou títulos. Todos os membros podem participar e, a parte boa é a interação que os membros da comunidade podem ter com os líderes comunitários de todas as partes do mundo. Eles estarão lá para ajudar a esclarecer todas as dúvidas, fique a vontade para participar.

Por fim queremos agradecer a todas as contribuições da comunidade e destacar que este fórum é público, gratuito e específico para o Wiki. É super importante que a comunidade participe, pois é com base nessas informações que conseguimos mapear todas as necessidade e assim as tratar em todos os níveis da comunidade.

Obrigado.

Wiki Ninja Hezequias Vasconcelos @++

Within this space - "TechNet Wiki Discussion" the goal is to receive feedback from community members, address issues, propose improvements, moderate questions about various topics and answer questions relevant to the Wiki.
These actions are possible through the issues observed by our community. The place where we seek this information to always improve our Wiki is the exclusive forum created specifically to address the entire spectrum of subjects. It is available to access the link:

Access is open to all members, regardless of their level of contribution (medals, points and contribution of time in the community) or titles. All members can participate, and the good part is the interaction that community members may have with community leaders from all over the world. They will be there to help clarify any questions, feel free to participate.

Finally we want to thank all the community contributions and noted that this forum is public, free and specific to the Wiki. It's super important that the community participates, because it is based on this information we can map all the needs and thus treat in all levels of the community.

Hi all - 

I wanted to let you know that this Friday, April 15th the Skype for Business product team will be delivering a broadcast.

Details:

• What: Learn about the Skype for Business Cloud Connector
• Who: Skype for Business group
• When: April 15h at 9:00 am PST
• Where: Skype Meeting Broadcast - http://aka.ms/SfBcast
• Will this be recorded: Yes, it will take a couple of weeks and then it will posted on the Skype channel

Regards,
Bea

A wonderful week of news and new technology advances from Build this week have filled our minds with new possiblilities!

So much to play with!

Can you help us document some of the new features coming out over the next year?

Do you have a good grasp on how we should now be doing that thing that we do?

Did you find a knowledge gap in the web for the new features now available?

This is a great chance to jump into the TechNet Guru competition and stamp your authority on your favoutrite subject.

All you have to do is add an article to TechNet Wiki from your own specialist field. Something that fits into one of the categories listed on the submissions page. Copy in your own blog posts, a forum solution, a white paper, or just something you had to solve for your own day's work today.

Drop us some nifty knowledge, or superb snippets, and become MICROSOFT TECHNOLOGY GURU OF THE MONTH!

This is an official Microsoft TechNet recognition, where people such as yourselves can truly get noticed!

HOW TO WIN

1) Please copy over your Microsoft technical solutions and revelations to TechNet Wiki.

2) Add a link to it on THIS WIKI COMPETITION PAGE (so we know you've contributed)

3) Every month, we will highlight your contributions, and select a "Guru of the Month" in each technology.

If you win, we will sing your praises in blogs and forums, similar to the weekly contributor awards. Once "on our radar" and making your mark, you will probably be interviewed for your greatness, and maybe eventually even invited into other inner TechNet/MSDN circles!

Winning this award in your favoured technology will help us learn the active members in each community.

Below are February's mighty winners and contenders. We should have March's winners by about mid month.

BizTalk Technical Guru - February 2016

Forefront Identity Manager Technical Guru - February 2016

Microsoft Azure Technical Guru - February 2016

Miscellaneous Technical Guru - February 2016

SharePoint 2010 / 2013 Technical Guru - February 2016

Small Basic Technical Guru - February 2016

SQL BI and Power BI Technical Guru - February 2016

SQL Server General and Database Engine Technical Guru - February 2016

System Center Technical Guru - February 2016

Transact-SQL Technical Guru - February 2016

Universal Windows Apps Technical Guru - February 2016

Visual Basic Technical Guru - February 2016

Visual C# Technical Guru - February 2016

Wiki and Portals Technical Guru - February 2016

Windows PowerShell Technical Guru - February 2016

Windows Presentation Foundation (WPF) Technical Guru - February 2016

Windows Server Technical Guru - February 2016

Good luck! 
Pete Laker 

& Ninja Ed

ATENÇÃO: Este artigo ainda está sendo revisado !!

Existe uma série de combinações de ambiente suportados para conectar Exchange On-Premise com Exchange Online montando um ambiente híbrido.

A versão mínima de Exchange Server que permite a conexão com o Exchange Online (Office 365) é Exchange 2010, logo, não está sendo considerado cenários com Exchange 2007. Cenário com Exchange 2007 precisam pelo menos um servidor Exchange 2010 ou superior (conhecido como Hydrid Server)

Segue a tabela de possíveis cenários suportados:

(1) Exchange 2013 system requirements
 https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx 

(2) Exchange 2016 system requirements
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.160).aspx

De forma geral, a conexão entre os ambientes Exchange é configurada com a execução do HCW, mas existem uma série de configuração adicionais requeridas para o perfeito funcionamento do fluxo de mensagens entre o Exchange OnPremise e o Exchange Online. Lembrando que o cenário que foi testado utilizou o Standalone Hybrid Configuration Wizard disponível em: http://aka.ms/HybridWizard.

Segue abaixo o detalhamento de todas as configurações adicionais que devem ser ajustadas nos Conectores do Exchange para cada cenário:

Cenários 1, 5 e 9:

Rodar o HCW sem necessidade de qualquer alteração nos conectores.

Cenário 2:

Rodar HCW e fazer os seguintes ajustes::

1. No Exchange Manangement, em cada um dos servidores Hub Transport remover o Receive Connector “Inbound from Office 365”
2. No Exchange Manangement, remover os servidores Hub Transport do Send Connector “Outbound to Office 365” e adicionar os servidores Edge (necessário digitar o nome dos Edges)
3. No Exchange Manangement Shell, configurar o Receive Connector default da Internet em cada servidor Edge usando o comando PowerShell abaixo:

Set-ReceiveConnector –Identity "<ServerName>\Default internal receive connector <ServerName>" -TlsDomainCapabilities mail.protection.outlook.com:AcceptOorgProtocol –Fqdn <FQDN_publico_do Edge>

Cenários 3 e 4:

Rodar HCW e fazer os seguintes ajustes::

1. No ADSIEdit.msc, no caminho CN=Outbound to Office 365,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<Org>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain>,DC=<domain> alterar o atributo msExchSmtpSendFlags de 64 para 131136 (ver mais infos sobre esse atributo ao final do post).
2. Force a execução do EdgeSync via PowerShell usando Start-EdgeSubscription
3. No Exchange Manangement, em cada um dos servidores Hub Transport remover o Receive Connector “Inbound from Office 365”
4. No Exchange Manangement, remover os servidores Hub Transport do Send Connector “Outbound to Office 365” e adicionar os servidores Edge (necessário digitar o nome dos Edges)
5. No Exchange Manangement Shell, configurar o Receive Connector default da Internet em cada servidorEdge usando o comando PowerShell abaixo:

Set-ReceiveConnector –Identity "<ServerName>\Default internal receive connector <ServerName>" -TlsDomainCapabilities mail.protection.outlook.com:AcceptOorgProtocol –Fqdn <FQDN_publico_do Edge>

Cenários 6, 7, 8, 10, 11 e 12:

Rodar HCW e fazer os seguintes ajustes::

1. No Exchange Manangement Shell, configurar o Receive Connector default da Internet em cada servidor Edge usando o comando PowerShell abaixo:

Set-ReceiveConnector –Identity "<ServerName>\Default internal receive connector <ServerName>" -TlsDomainCapabilities mail.protection.outlook.com:AcceptOorgProtocol –Fqdn <FQDN_publico_do Edge>

Informações sobre o atributo  msExchSmtpSendFlags:

O atributo msExchSmtpSendFlags ajustado via ADSIEdit.msc nos cenários 3 e 4 representa o atributo CloudServicesMailEnableddo SendConnector via PowerShell. Como este parâmetro foi introduzido no Exchange 2013, não é possível alterar o atributo via PowerShell no Exchange 2010, logo, é necessário modificar via ADSIEdit.msc. No ADSIEdit.msc  o valor 16 representa o valor $False do PowerShell e o valor 131136 representa o valor $True.

Esse atributo precisa ser alterado no cenário de Exchange 2010 com Edge 2013/2016, pois o Send Connector é criado pelo HCW nos servidores Hub Transport (Exchange 2010), mas é executado nos servidores Edge (Exchange 2013), por isso, é necessário ter o atributo com valor $True (ou 131136).

Este valor deve ser $True (ou 131136) para preserver o cabeçalho entre os ambientes Exchange OnPremise e Exchange Online, dessa forma a mensagem é “marcada” como internal. Isso pode ser visto no cabeçalho das mensagens no atributo X-MS-Exchange-Organization-AuthAs. Se este atributo estiver com valor Anonymous é muito provável que este atributo esteja com valor $False (ou 16).

* * Contribuição do PFE Rafael Mantovani.