Безопасность информационных систем является одним из основных на повестке многих компаний, которые сталкивались с утечками данных, ущербом от вымогателей-шифровальщиков, хакерскими и другими атаками. Помимо потери коммерческих данных, могут быть потеряны персональные данные физических лиц, что повлечет за собой финансовые и репутационные риски.

В серии вебинаров вы узнаете, как решения на базе Microsoft обеспечивают безопасность и соответствие международным законам по хранению и обработке персональных данных.

На вебинаре вы ознакомитесь с процессом обнаружения персональных данных. В рамках сессии будут рассмотрены способы обнаружения данных в СУБД, операционной системе Windows, электронной почте и облачных сервисах даже в случае, если данные были удалены.

В рамках данного вебинара будут рассмотрены возможности:

• Обнаружение данных через поиск. Скрытые возможности поиска Windows.
• Выход из тени с Cloud App Security.
• Обнаружение данных в Office 365.
• Поиск персональных данных в информационных системах с Office 365 Data Catalog.

Участие бесплатное, необходима регистрация

With the release of Windows Server version 1709 also come Windows Server Core and Nano Server base OS container images.

It is important to note that while older versions of the base OS container images will work on a newer host (with Hyper-V isolation), the opposite is not true. Container images based on Windows Server version 1709 will not work on a host using Windows Server 2016.  Read more about the different versions of Windows Server.

We’ve also made some changes to our tagging scheme so you can more easily specify which version of the container images you want to use.  From now on, the “latest” tag will follow the releases of the current LTSC product, Windows Server 2016. If you want to keep up with the latest patches for Windows Server 2016, you can use:

“microsoft/nanoserver”
or
“microsoft/windowsservercore”

in your dockerfiles to get the most up-to-date version of the Windows Server 2016 base OS images. You can also continue using specific versions of the Windows Server 2016 base OS container images by using the tags specifying the build, like so:

“microsoft/nanoserver:10.0.14393.1770”
or
“microsoft/windowsservercore:10.0.14393.1770”.

If you would like to use base OS container images based on Windows Server version 1709, you will have to specify that with the tag. In order to get the most up-to-date base OS container images of Windows Server version 1709, you can use the tags:

“microsoft/nanoserver:1709”
or
“microsoft/windowsservercore:1709”

And if you would like a specific version of these base OS container images, you can specify the KB number that you need on the tag, like this:

“microsoft/nanoserver:1709_KB4043961”
or
“microsoft/windowsservercore:1709_KB4043961”.

We hope that this tagging scheme will ensure that you always choose the image that you want and need for your environment. Please let us know in the comments if you have any feedback for us.

Note: We currently do not intend to use the build numbers to specify Windows Server version 1709 container images. We will only be using the KB schema specified above for the tagging of these images. Let us know if you have feedback about this as well

Regards,
Ender

Applies for Exchange 2013 and 2016

In this scenario we are migrating UM enabled users from Exchange on premises to Exchange Online. This process requires integration of your Exchange online UM with Skype for Business Server.

To deal with the migration of mailboxes from Exchange on-premises to Exchange online which are UM

enabled, we have two options.

1. You can disable UM for a user in on-premises Exchange Server and then move their mailbox to Exchange Online and enable it for UM in Exchange Online.
2. If you do not wish to disable and re-enable the user for UM and would like them to stay UM enabled while moving their mailbox, we must create the same UM Dial Plan in Exchange Online and map the online UM mailbox policy with on-premises UM mailbox policy.

When the user is moved to Exchange Online they will receive an automated email indicating that they are enabled for UM and this email will contain the new Subscriber Access number and PIN details.

Current infrastructure

• Exchange Server 2016 Hybrid
• Skype for Business Server 2015

Pre-requisites:  

1. Skype for Business Edge server: To integrate Skype for Business server with Exchange Online UM, we need a working edge server with outside access and federation enabled.

To confirm that edge server is configured correctly, sign into Skype for Business client remotely and establish an IM and audio session with a federated user.

2. Office 365 tenant: O365 should have your custom domain verified
3. O365 License: Exchange online plan 2 or above
4. Azure AD Connect: To synchronize Active Directory users to Azure Active Directory
5. Exchange Online Standalone or Exchange Online in Hybrid

Once the above-mentioned pre-requisites are met, we can either provision a mailbox directly in cloud (provided we do not have a mailbox in on premises for the same user) to enable UM in Exchange Online or we can migrate the mailboxes to Exchange Online without having on premises mailbox's UM disabled.

Steps to configure Exchange Online UM with Skype for Business Server

1. Create a UM Dial Plan in Exchange Online
2. Add a new Hosting Provider on the Edge Server
3. Create Hosted Voicemail Policy
4. Create contact objects for hosted Exchange UM in Skype for Business Server
5. Map Online UM Mailbox Policy with the On-Premises Mailbox Policy (for onboarding a mailbox)
6. Map On-Premises UM Mailbox Policy with the Online UM Mailbox Policy (for offboarding a mailbox)
7. Assign Hosted Voicemail Policy to users
8. Enable Users for Hosted Voice Mail
9. Enable users for UM in Exchange online or migrate user mailbox to Exchange online without disabling UM

Step 1:  Create a UM Dial Plan in Exchange Online

Login to https://portal.office.com as a Global Administrator

Select Admin

Then, go to Admin centers, select Exchange from the List

Then on the following page select unified messaging

Click on ‘+’ button to create new UM dial plan and then enter name, Extension length, Dial Plan Type and Country code and save

As I have 4-digit dial plan created in my Skype for Business Server, I am using 4-digit Extension length.

Select newly created O365UMDialPlan, edit and Configure to create Subscriber Access number.

Under Outlook Voice Access add phone number in E.164 format. It should not be same as your on-premise Subscriber Access number. You can add DID if your Skype for Business Server is integrated with PSTN.

To configure Auto Attendant, select O365UMDialPlan, edit, UM Auto Attendants

Click the '+' button to create a new Auto Attendant and then enter a unique name without any space and special character.

Select “Create this auto attendant as enabled” and “Set this auto attendant to respond to voice commands” and then enter the unique phone number in E.164 format, it should not be same as on-premise auto attendant number. (If you have configured auto attendant in on-premises you can use the same auto attendant till you completely migrate to cloud).

Make a note of default UM Mailbox policy as it is required to map with the on-premises UM mailbox policy.

Step 2: Add a Hosting Provider on the Edge Server

Using the Skype for Business Server management shell, configure a hosting provider on the Edge server by running the New-CsHostingProvider cmdlet, using the parameters in the following example:

New-CsHostingProvider -Identity 'Exchange Online' -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFqdn "exap.um.outlook.com" -IsLocal $False -VerificationLevel UseSourceVerification

• Identity specifies a unique string value identifier for the hosting provider that you are creating (for example, "Exchange Online"). Values that contain spaces must be in double quotes.
• Enabled indicates whether the network connection between your domain and the hosting provider is enabled. This must be set to True.
• EnabledSharedAddressSpace indicates whether the hosting provider will be used in a shared SIP address space scenario. This must be set to True.
• HostsOCSUsers indicates whether the hosting provider is used to host Office Communications Server or Skype for Business Server. This must be set to False.
• ProxyFQDN specifies the fully qualified domain name (FQDN) for the proxy server used by the hosting provider. For Exchange Online, the FQDN is exap.um.outlook.com.
• IsLocal indicates whether the proxy server used by the hosting provider is contained within your Skype for Business Server topology. This must be set to False.
• VerificationLevel Indicates the verification level allowed for messages that are sent to and from the hosted provider. Specify UseSourceVerification, which relies on the verification level included in messages sent from the hosting provider. If this level is not specified, the message will be rejected as being unverifiable.

To ensure that a hosting provider was created successfully, run Get-CsHostingProvider. Below is the screenshot from my lab setup, your output should match as highlighted below.

Step 3: Create Hosted Voicemail Policy

Typically, only one hosted voicemail policy is required. In many cases, you can modify the global policy to meet all your needs. If you create a policy with site scope, it is assigned automatically to all users homed at the specified site. If you create a policy with per-user scope, you must explicitly assign it to users, groups, and contact objects. It is possible to deploy multiple hosted voicemail policies, but in that case the policies must be assigned on a per-user basis.

To modify global policy run below command in Skype for Business Server management shell.

Set-CsHostedVoicemailPolicy -Identity Global -Description "Global Hosted VM Policy for All Users" -Destination exap.um.outlook.com -Organization cloudtoday2016.onmicrosoft.com

• Destination specifies the fully qualified domain name (FQDN) of the hosted Exchange UM service. For Exchange Online UM this is the FQDN um.outlook.com
• Organization This parameter contains a comma-separated list of the Exchange tenants that contain Skype for Business Server users. Each tenant must be specified as an FQDN of the tenant on the hosted Exchange Service.

The Organization name is also the Default Domain name in O365.

To ensure that a Hosted Voicemail Policy was created successfully, run "Get-CsHostedVoicemailPolicy".

Your output should look like below screenshot.

To create per-user or site-level hosted voicemail policy refer: https://technet.microsoft.com/en-us/library/gg398332.aspx

Step 4: Create contact objects for hosted Exchange UM in Skype for Business (Optional)

To be able to dial in to Subscriber Access number for voicemail and Auto Attendant we must create contact objects for Auto Attendant (AA) and Subscriber Access (SA) in Skype for Business Server.

To create contact objects for AA and SA in Skype for Business server using Skype for Business management shell, refer: https://technet.microsoft.com/en-us/library/gg412765.aspx

Example:

New-CsExUmContact -SipAddress sip:O365UM@fabrikam.com -RegistrarPool RedmondPool.litwareinc.com -OU "OU=ExUmContacts,DC=litwareinc,DC=com" -DisplayNumber +1001

New-CsExUmContact -SipAddress sip:O365AA@fabrikam.com -RegistrarPool RedmondPool.litwareinc.com -OU "OU=ExUmContacts,DC=litwareinc,DC=com" -DisplayNumber +1002 -AutoAttendant $True

If you have created per-user Hosted Voicemail Policy, we must assign it to all users including the SA and AA contact objects. If you have modified Global policy, by default it will be applied to all the users.

Run below commands in Skype for Business management shell to assign Hosted Voice mail policy to SA and AA contact objects.

Grant-CsHostedVoicemailPolicy -Identity "sip:O365SA@fabrikam.com" -PolicyName "Exchange Online"

Grant-CsHostedVoicemailPolicy -Identity "sip:O365AA@fabrikam.com" -PolicyName "Exchange Online" 

Where PolicyName will be the name of per-user Hosted Voicemail policy.

Step 5: Map Online UM Mailbox Policy with the On-Premises Mailbox Policy (for onboarding a mailbox)

To map online and on-premise UM Mailbox policies we must run a below command. This will allow you in migrating a mailbox without disabling its corresponding UM policy.

Set-UMMailboxPolicy -Identity "Online UM Mailbox policy" -SourceForestPolicyNames "On-prem UM mailbox policy"

• Identity is the Office 365 UM Mailbox Policy
• SourceForestPolicyNames is the On-Premises UM mailbox policy

To get the on-premises UM mailbox policy, login to Exchange Admin Center of On-Premises Exchange Server, then go to unified messaging, UM dial plan and select the dial plan, edit and make a note of UM Mailbox Policies.

Now to map online UM Mailbox Policy with the on-premises UM Mailbox Policy connect to Exchange Online PowerShell with the global administrator.

To connect to Exchange Online PowerShell, refer: https://technet.microsoft.com/en-us/library/jj984289(v=exchg.160).aspx

$cred = Get-Credential

$session = New-PSSession -ConfigurationName Microsoft.Exchange -Authentication Basic -ConnectionUri https://ps.outlook.com/powershell -AllowRedirection $true -Credential $cred

Import-PSSession $session

Once connected to Exchange Online PowerShell, run below command to map online UM policy with On-Premises UM policy.

Set-UMMailboxPolicy -Identity "O365UMDialPlan Default Policy" -SourceForestPolicyNames "UmDialPlan Default Policy"

Step 6: Map On-Premises UM Mailbox Policy with the Online UM Mailbox Policy (for offboarding a mailbox)

This step is required if in case you migrate user mailbox back to on-premises.

Run below command in on-premises Exchange Server management shell

Set-UMMailboxPolicy -Identity "UmDialPlan Default Policy" -SourceForestPolicyNames "O365UMDialPlan Default Policy"

• Identity is the On-Premises UM mailbox policy
• SourceForestPolicyNames is the Office 365 UM Mailbox Policy

Step 7: Assign Hosted Voicemail Policy to users

Assign Hosted Voicemail Policy for all the users, if you have created per-user policy. Ignore this step if you have modified the Global policy.

Grant-CSHostedVoicemailpolicy -identity “youraccount” -PolicyName “Exchange Online”

Where PolicyName will be the name of per-user Hosted Voicemail Policy

Step 8: Enable users for Hosted voicemail

We must enable users for Hosted Voicemail, by running below command.

Set-CSUser -identity “sip:username@domain.com” -HostedVoicemail $True

Step 9: Enable users for UM in Exchange online or migrate user mailbox to Exchange online without disabling UM

Once we complete all the steps mentioned above, we can migrate the mailboxes to Exchange Online without having on premises mailbox's UM disabled or we can directly enable for UM in online if user mailbox is provisioned in online.

To enable user for UM in online directly, go to Exchange online admin center, recipients, select user, Enable for UM.

Browse and select UM mailbox policy

Provide 4-digit extension and click finish.

User will receive an email with Subscriber access number and PIN details which they must reset first time they sign in.

I hope this has been informative for you, please feel free to reach out to me if you have any queries.

Thank you.

With the recent release of Windows 10 RS3 aka 1709 aka build 16299 i thought it was a good time to post some queries and collections for each Windows 10 version released so far.  Additionally i also included Queries for each OS released as far back as XP that i happened to have access to at the time of this post.

The Query itself is very simple and i like to create queries for reuse later on with collections etc. so my admins can easily reference these for reuse without unknowingly deploying to the wrong systems… “I kinda just don't trust anyone” its part of the job.  

"select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.BuildNumber = "16299""

For a full comprehensive list of Windows 10 Build history see the link below.

https://technet.microsoft.com/en-us/windows/release-info.aspx

If you would like to skip all the manual stuff you can go ahead and grab the mof files for import for collections and queries below and be on your way.

Queries-And-Collections

Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in theTerms of Use.

10-18-2017 Updated to include Windows 10 Language Packs

By now you probably have seen that Windows 10 RS3 released yesterday 10/17/2017.  Its available via MSDN, MVLS and any other channels you may use.

Additionally you might find the following links useful if you are planning on creating a reference image, doing OS Deployment or simply managing the latest Windows 10 release in your environment.

Windows 10 RS3:

Download via MSDN or MVLS

Windows 10 RS3 ADK:

https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit

Windows 10 RS3 Administrative Templates:

https://www.microsoft.com/en-gb/download/details.aspx?id=56121

Windows 10 RS3 Security Baseline:

https://blogs.technet.microsoft.com/secguide/2017/10/18/security-baseline-for-windows-10-fall-creators-update-v1709-final/

Windows 10 RS3 Language Packs:

https://blogs.technet.microsoft.com/mniehaus/2017/04/26/finding-windows-10-language-packs/

As additional items become available ill continue to update this post with more resources.  A couple of items to consider if you are a ConfigMgr customer.  ConfigMgr 1706 supports Deployment and Management of Windows 10 RS3 currently.  At the moment i do not believe we have “support” for Windows 10 ADK 1709 so i would wait for an official stance on this before implementing in your environment.  I would suspect that this would come with the next release of ConfigMgr if not sooner but proceed with caution before upgrading to this release of the ADK until you get confirmation that it is officially support and with what release its supported on.

Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in the Terms of Use.

Microsoft Tech Summit 2017 スペシャル トラックでは加藤一二三氏が登壇し、日本マイクロソフトのエバンジェリスト西脇資哲と人工知能について対談します。

▼ スペシャル トラックの詳細はこちらから

またスポンサー各社様のソリューションをはじめ、さまざまなコンテンツをご用意し、皆様に最新のテクロノジをより深く体験いただくと共に、他では得られない最新情報をお届けします。

お申し込み受け付けは 10/27 (金) までです。今すぐお申し込みください!

▼ Microsoft Tech Summit 2017 のお申込みはこちらから

微軟 Ignite 2017 已於 9/25-9/29 舉行，總共有超過1537個會談，在這裡我想跟你們分享關於 Azure 安全性及操作管理的部分， 若想知道最新訊息，也可以追蹤twitter：@MS_Ignite!!

注意：點擊各個會議連結就可以直接連到微軟 Ignite 官網。

必看基礎會議：

• 資料中心移轉－平台、流程與人員的路線圖 (Jefferey Snover)
• 針對混合雲環境的 Azure 安全性及管理 (Jeremy Winter)
• 對您的 Azure 資源執行安全且管理優良的策略 (Scott Woodgate)

安全性相關會議：

• 利用微軟 Azure 安全中心簡化混合雲保護方式 (Sarah Fender)
• 利用下一代安全性操作及調查，快速回應安全性威脅 (Meir Mendelovich)
• 描述雲端攻擊：微軟獨特的洞察分析如何幫助您防範攻擊 (Tom Teller)
• 利用微軟 Azure 安全中心保護 Azure IaaS 部署 (Sarah Fender)
• 防範暗黑(雲)藝術：深入 Azure 安全性分析 (And Malone)

監控相關會議：

• 獲得您 IT 混合環境全面的洞察分析，並採用 Azure 解決方案 (A.S. Sivakumar)
• 快照 debug 和微軟 Azure 診斷功能 (Nikhil Joglekar 和 Dan Taylor)
• 利用 Azure Application Insights 在您的 DevOps 工作流程中分析和 degbug 應用程式
• 利用 Azure 的網路監控解決方案，了解網路性能和可用性 (Abhishek Pathak)
• 用四個新的 Azure 管理體驗來運行您的業務關鍵應用程式 (Jan Kalis)
• 用 Azure 網際網路監控、診斷，和 debug (Abhishek Pathak 和 Vijay Tinnanur)
• 更新的 Azure Log Analytics: 一個利用機器學習及更多技術的強大查詢語言 (Ketan Ghelani)

備份和災難修復：

• 您業務在 IaaS 運行之業務持續性 (Vishal Mehrotra)
• 優化 Azure 以進行災難復原 (John Savill)
• 透過 Azure Site Recovery 的 Application-aware 災難復原功能支援 VMware、Hyper-V，和 Azure IaaS VMs (Abhishek Hemrajani)  
• 利用微軟 Azure Backup 保護您的資料 (Vijay Tandra Sistla)

治理：

• 在政策管理的基礎上，大力實行 Azure (Joseph Chan)
• 利用 Cloudyn 來監控、分配，和優化您的雲端花費，使 Azure 發揮其最大功效 (Robert Reynolds)

系統中心 (System Center)：

• 現代資料中心的系統中心：先來看看今年升級的地方 (Bala Rajagopalan)
• 微軟 System center 2016 正夯：客戶現在利用案例來進行管理 (Mahesh Narayanan)

PowerShell、配置和自動化與可延展性：

• 和 Jeffrey Snover (PowerShell 發明者) 與 Don Jones 一起攻克 PowerShell (Jeffrey Snover)
• 利用 Azure Management 管理組織配置並更新/補強 Windows 和 Linux 伺服器 (Ravi Kiran Chintalapudi)
• 利用 PowerShell 和 Azure Automation 管理混合雲並改變您的工作空間 (Eamon O'Reilly)
• Azure Management 技術框架：用於協助合作夥伴擴展 (Evan Hissey)

こんにちは、Azureサポートチームの三國です。
今回は管理ディスクを用いたLinuxのOSディスクを他の仮想マシンのデータディスクとして接続する方法についてご案内致します。
非管理対象ディスクの手順についてはLinux OS が起動しない時のトラブル シューティングについて (ARM編)にて記載がありますのでそちらをご参照下さい。

本情報の内容（添付文書、リンク先などを含む）は、作成日時点でのものであり、予告なく変更される場合があります。

はじめに

利用シーン・概要・注意事項・補足・FAQについては Linux OS が起動しない時のトラブル シューティングについて (ARM編) をご参照ください。

手順

それでは手順をご案内します。

2. ディスクの情報を確認します(名前、リソースID)

3. 仮想マシンを削除します。

4. データディスクとして他のVMにアタッチします。

5. データディスクをマウントして復旧作業を行います

例) $ sudo grep SCSI /var/log/messages

例) $ sudo mkdir /datadrive

例）$ sudo mount /dev/sdc1 /datadrive

例）$ sudo umount /datadrive

みなさま、いつも Device & Mobility Team Blog をご覧いただきありがとうございます。セキュリティ製品 担当の鈴木です。

本日は2017 年11月に実施されるIntuneのコンプライアンスポリシーの仕様変更について説明します。
Azure Active Directoryで条件付きアクセスのデバイスコンプライアンスの準拠をチェックしている場合影響を受ける可能性があります。影響のある可能性がある環境は次になります。

• Azure Active Directoryで条件付きアクセスを設定し、準拠デバイスにアクセス許可を与えており、コンプライアンスチェックの対象になってない端末がある場合
• SCCMとIntuneのハイブリッド構成で条件付きアクセスを上記と同様に設定している場合
• Office 365のモバイルデバイス管理を利用していて「デバイスがポリシーの要件を満たしていなくてもアクセスできるようにする」というポリシーを利用している場合

Intuneのデバイスコンプライアンスは、デバイスが管理者の指定した設定をクリアしているか確認することができる機能で、デバイスの安全性を確認することができる機能の一つです。

MDM管理されたデバイスはコンプライアンスポリシーをチェックして適合していれば「準拠デバイス」としてAzureADに登録されます。Azure ADの条件付きアクセスで適合済みのデバイスのみのアクセスを許可することでクラウドサービスの安全性を高めることができます。

いままでデバイスコンプライアンスポリシーの対象となっていない端末はすべて「準拠」と認識されていました。これがセキュリティ強化のため、2017年11月のIntuneのアップデートの後は「準拠していない」に変更されます。この変更に伴い、いままで問題なくアクセスできていた端末がアクセスをブロックされる可能性があります。

この問題が発生するかどうかを確認するにはIntuneの管理ポリシーから確認できます。


ここに新しくコンプライアンスポリシーが適用されてない端末の数が表示された場合影響がある可能性があります。この機能は2017年10月のアップデートで提供される予定です。その場合は条件付きアクセスの内容を確認して条件にデバイスコンプライアンスの準拠が設定されている場合はアクセスできない端末が発生しないか確認してください。

もしコンプライアンスポリシーのチェックを行わず登録済みデバイスにアクセスできるようにするには、何も設定されていないブランクのコンプライアンスポリシーを作成してユーザに割り当てるようにします。またこの件に対応できる設定が11月のアップデートとともに提供される予定です。
詳細の方法についてはこちらの記事をご確認ください。
Upcoming Security Enhancements in the Intune Service – your action is required!

Earlier today, I was asked to make an update to my script to wipe Exchange Online mailboxes to include Archive Mailboxes.  Fortunately, it ended up being much easier than I anticipated:

When I enumerated the mailbox originally, I used:

$Root = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service, [Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Root)

In order to access the Archive folder, I just had to change the WellKnownFolderName from Root to ArchiveRoot, after examining the list available at https://msdn.microsoft.com/en-us/library/microsoft.exchange.webservices.data.wellknownfoldername(v=exchg.80).aspx.

$Root = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service, [Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::ArchiveRoot)

But, not being able to leave well enough alone, I wanted to provide some additional options, such as wiping only the mailbox, only the archive, or both, or being able to specify more than one user on the command line.  You can pick up the new and improved version at the TechNet Gallery: https://gallery.technet.microsoft.com/Wipe-Exchange-Online-331ab4f4

Windows 10 Fall Creators Update sürümünün Active Directory ortamında yönetilmesini sağlayan Yönetimsel GPO Şablonlarına buradan ulaşılabilir.

Last week I attended OpenHack Amsterdam, and this post is my thoughts about that great event.

The event was focused on Containers and Microservices – on a high level the goal was migrating on-premise Linux and Windows workloads to Microsoft Azure cloud through Kubernetes on Azure Container Service and Azure Service Fabric. Regarding to both technologies the event hosted two special guests from engineering teams in Redmond: Mark Fussell (@mfussell) - Lead PM for Service Fabric and Gabe Monroy (@gabrtv) - Lead PM for Containers on Azure. Besides, there were many Expert Proctors from engineering teams to help attendees.

The event took place from 9th to 11th of October 2017 in Amsterdam, Netherlands in fascinating venue – De Hallen.

What is OpenHack?

This is something new in my opinion, a new quality of wide-opened events. I will start with what OpenHack is not.

So, OpenHack is not:

• proctored labs like Hands-On Labs training or workshop;
• product tech marketing sessions (presentation format);
• sales engagement;
• limited to a specific developer segment;
• exclusively project-based end customer focused engagement;
• a traditional Microsoft "event" like conference;
• design and architecture workshop;
• hackathon like competition.

And now, what is OpenHack? The OpenHack experience brings together a sizeable group of diverse Developers to learn how to implement a given scenario through immersive, structured, hands-on, FUN, challenge-based hacking. OpenHack is targeted to Developers inside and outside Microsoft ecosystem, and the activities are geared towards hands-on code-with experiences vs. formal session presentation.

Microsoft Extended Family pre-day

On Sunday, October 8th was a pre-day event designed for Microsoft employees and "extended family" like partners, MVPs, and RDs where engineering leads did technical drill down into what we'll be focused on over the next few days.

In most cases, we know each other only from electronic communication. The event gave us an opportunity to network and socialized as well.

Hacking Teams

The whole event was split into two technologies: Service Fabric and Kubernetes. Depends on the survey on registration, attendees were assigned to teams their selected technology. Each team has four to five members, with a mix of Microsoft employees, partners, and customers and one Expert Proctor from the engineering team. At the end proportion of teams were ~25% for Service Fabric and 75% for Kubernetes. I was the member of Service Fabric team (Greetings for Team 3 ).

Challenge-based Hacking

During a three-day intensive event, each team has directly engaged in the challenge-based hacking activity through the same increasing difficulty challenges to accomplish. There were not any step-by-step guides, etc. – the goal was to use existing knowledge source like docs.microsft.com and examples on GitHub to find right solutions for the Challenge. After each resolved Challenge, Proctor validated it and unblocked next Challenge, so, you cannot go further without accomplished Challenge.

For the whole OpenHack were five challenges in total: three main challenges, and two extra challenges to chosen when first three has done. On high-level challenges are:

1. Run application using Docker on local machine and VM in Microsoft Azure cloud.
2. Run legacy application (Minecraft in this case) on Service Fabric or Kubernetes cluster in Microsoft Azure, create monitoring solution and create persistent state solution for that application.
3. Write REST API application and Web Application that utilize API, deploy both to the cluster.
4. Challenge 4. was split between two paths:
   1. Create a solution for the global workload.
   2. Create an auto-up solution for cluster based on a specified threshold.
5. Based on the previous decision, Challenge 5. was split between two paths:
   1. To be added soon...
   2. Create a full auto-scale solution with scale-up and scale-down for cluster based on a specified threshold.

Gamification

That was not a typical contest like hackathon to win something using know technology to accomplish a task. You had to use the specific technology, even if you did not know it. The whole event had gamification model to add more "spicy" at the end Teams progress was displayed on a big screen, so everyone can saw where his or her team is and where the other teams are.

Extra stuff like Expert Talk and Code-with Pod

During event was two special activities in the agenda like Expert Talks and Code-with Pods.

Both activates driven Engineering leads, for Export Talks attendees used post-it notes (with their topic idea), and engineering leads picked popular topics and did informal talk.

Code-with Pods attendees could bring workplace project ideas to hacked with Microsoft expert. Each slot has 2 hours, and idea for this activity was first-come, first served.

Community Meetups

After the first and second day of the OpenHack were community Meetups.

First was Dutch Azure Meetup where Mark Fussell (Lead PM of Service Fabric, Microsoft) was speaking about Service Fabric, and Brian Randell (Visual Studio ALM MVP) was speaking about PowerShell for Developers.

The second was Software Circus Meetup where Gabe Monroy (Lead PM of Containers on Azure, Microsoft) was speaking about Kubernetes and the Open Service Broker API, and Pini Reznik (CTO, Container Solutions) was speaking about Adoption of Cloud Native infrastructure.

Polish presence

I am very happy because there were several people from our customers and partners (about 10) from my native country. In addition, I am proud of team No. 17 in which there were as many as 3 Poles. Why? Because this team won OpenHack! Congrats to:

• Maciej Misztal
• Wiktor Zasowski
• Krzysiek Biernat

Testimonial from Wiktor Zasowski (Systems Administrator, Viessmann)

I have fallen in love with the OpenHack formula. Clear learning path, entertaining challenges together with a little bit of gamification, and most crucial factor was gathering of great engineers and proctors eager to answer all problematic questions we have stumbled across.

Summary

I totally agree with Wiktor's testimonial. I have fallen in love with the OpenHack formula too. New learning experience which I LOVE – a combination of challenge-based hacking, gamification, sharing experiences with an unknown before teammates, no step-by-step guides gave me an incredible engagement and focused on learning new things. I want more OpenHacks!

Have a look at after movie

Appendix

Below you can find several links to technical stuff related to OpenHack technologies.

• Azure General
  • Azure CLI reference
  • Azure resource naming best practices
    
• Docker and Containers
  • Dockerfile reference
  • Docker CLI reference
  • Azure docker extension on Linux VMs
  • Windows Containers Documentation
• Azure Service Fabric
  • Service Fabric Containers Overview
    
• Kubernetes on Azure
  • Azure Container Service with Kubernetes
  • Kubectl overview

Over the past few days we've released updated drivers and firmware for Surface Pro, Surface Laptop, Surface Book, and Surface Pro 3 devices.

Surface Pro

For Surface Pro devices (Model 1796) running the Windows 10 Fall Creators Update, these new driver updates provide support for Windows Mixed Reality features and improve battery life by disabling touch while the Type Cover lid is closed. The updates include new drivers for Intel(R) Display Audio, Intel(R) HD Graphics, Intel(R) Precise Touch Device, Marvell AVASTAR Bluetooth Radio Adapter, and Marvell AVASTAR Wireless - AC Network Controller.

These updates are available in MSI format from the Surface Pro Drivers and Firmware Page in the Microsoft Download Center. Click Download to download the following file:

• SurfacePro_Win10_16299_1710007_0.msi

For your reference, here is a full list of the driver versions that are updated in this release and the improvements they provide:

• Intel(R) Display Audio v10.22.1.100 is required to support Windows Mixed Reality features.
• Intel(R) HD Graphics 620 v22.20.16.4749 is required to support Windows Mixed Reality features.
• Intel(R) Precise Touch Device v1.2.0.92 improves battery life by disabling touch while the Type Cover lid is closed.
• Marvell AVASTAR Bluetooth Radio Adapter v15.68.9120.47 is required to support Windows Mixed Reality features.
• Marvell AVASTAR Wireless - AC Network Controller v15.68.9120.47 is required to support Windows Mixed Reality features.

Surface Laptop

For Surface Laptop devices running the Windows 10 Fall Creators Update, these new driver updates provide support for Windows Mixed Reality features, improve Surface Dock stability, update installation, and DisplayPort stability, and improve keyboard safe-mode stability, two-finger scrolling, and system stability. The updates include new drivers for Intel(R) Display Audio, Intel(R) HD Graphics, Marvell AVASTAR Bluetooth Radio Adapter, Marvell AVASTAR Wireless - AC Network Controller, Surface Dock Firmware Update, Surface Dock Integration, Surface Integration, Surface Integration Service Device, Surface Keyboard, Surface Storage Firmware Update, Surface System Aggregator, Surface Trackpad, and Surface UEFI.

These updates are available in MSI format from the Surface Laptop Drivers and Firmware Page in the Microsoft Download Center. Click Download to download the following file:

• SurfaceLaptop_Win10_16299_1704008_0.msi

For your reference, here is a full list of the driver versions that are updated in this release and the improvements they provide:

• Intel(R) Display Audio v10.22.1.100 required to support Windows Mixed Reality features.
• Intel(R) HD Graphics 620 v22.20.16.4749 required to support Windows Mixed Reality features.
• Marvell AVASTAR Bluetooth Radio Adapter v15.68.9120.47 required to support Windows Mixed Reality features.
• Marvell AVASTAR Wireless - AC Network Controller v15.68.9120.47 required to support Windows Mixed Reality features.
• Surface Dock Firmware Update v1.2.6.0 Improves Surface Dock update installation and DisplayPort stability.
• Surface Dock Integration v1.0.6.0 Improves Surface Dock stability.
• Surface Integration v2.0.535.0 improves keyboard safe-mode experience.
• Surface Integration Service Device v1.0.801.0 improves system stability.
• Surface Keyboard v135.1713.0.0 improves keyboard safe-mode experience.
• Surface Storage Firmware Update v1.1.1199.0 improves system stability.
• Surface System Aggregator v135.1704.1.0 improves system stability.
• Surface Trackpad v2.122.2683.0.0 Improves two-finger scrolling.
• Surface UEFI v136.1736.769.0 improves system stability.

Surface Book

For Surface Book devices running the Windows 10 Fall Creators Update, this new driver update enables the Power Slider feature that improves both battery life and the adaptive brightness feature. The update includes a new driver for Surface Integration.

These updates are available in MSI format from the Surface Book Drivers and Firmware Page in the Microsoft Download Center. Click Download to download the following file:

• SurfaceBook_Win10_16299_1705000_1.msi

For your reference, here is a full list of the driver versions that are updated in this release and the improvements they provide:

• Surface Integration v1.1.333.0 enables the Power Slider feature that improves both battery life and the adaptive brightness feature.

Surface Pro 3

For Surface Pro 3 devices running Windows 10 Creators Update or above, these new driver updates improve battery life while the device is in Connected Standby. The updates include new drivers for Realtek High Definition Audio and Realtek USB 3.0 Card Reader.

These updates are available in MSI and ZIP format from the Surface Pro 3 Drivers and Firmware Page in the Microsoft Download Center. Click Download to download the following files:

• SurfacePro3_Win10_15063_1704002_0.msi
• SurfacePro3_Win10_15063_1704002_1.zip

For your reference, here is a full list of the driver versions that are updated in this release and the improvements they provide:

• Realtek High Definition Audio v6.0.1.8125 improves battery life while the device is in Connected Standby.
• Realtek USB 3.0 Card Reader v10.0.15063.31236 improves battery life while the device is in Connected Standby.

Last September during my presentation with Meir at Ignite, we talked about how powerful the new search capability in Azure Security Center is, the integration with Log Analytics gives you total control, and flexibility to find what you really need.  But how to really use this? First step is to read our core documentation regarding Search in Security Center. Now that you know the basics, let's go over the following scenario.

Problem

As a security investigator, you identify the following Alert in Security Center:

Based on this alert, you noticed that abbybecker was the user that executed this process. Now you want to find out if there are more alerts raised by abbybecker.

Solution

Now is the time to use the advanced Search. If you use this article, you will have the core steps to access the Search capability. In the Log Search page, click Advanced Analytics, and when you get there click in the + sign to create a new query. Here it is the query that you can use for that:

After typing the query, click Go, and you will see the result in the table right below the search field, as shown below:

The results are shown in a table, which makes very easy to read it. Cool, isn't it? Question now is: how did you find this SecurityDetection field to search for? Easy, on the left pane, under SCHEMA, type secur and you will see all fields that contains security and you can search for.

As you can see, there are plenty of fields that you can use to gather the data that you need. Now go ahead and have some fun creating queries!

Good news - those of you wanting to test out Windows 10 Enterprise version 1709 capabilities can download these now from the Evaluation Center.

Here are the full details from the Evaluation Center

Over on the Windows for IT Pros blog my long time trans-Tasman friend has made a lengthy post What's new for IT pros in Windows 10, version 1709. I won't rehash what Nathan has typed, but here are the categories he has covered in detail, with lots of links to investigate.

• Deployment
• Servicing
• Security
• Management
• Networking
• Proactive Insights
• General Improvements

Check out what Nathan has posted, and if you are heading to the Tech Summit in Sydney, Nathan will be there along with other members of the Windows team, ready to answer your questions and take your feedback.

Now that Windows 10, version 1709 has been released you can download the latest version of the Windows ADK. If you still need earlier versions they are available via the same link.

However, I usually recommend to choose the option to download it so that I can install it onto a multiple PCs.

Notice that the downloaded version is compressed, and you can then install at local disk or network speeds when needed.

Over on the Windows Analytics blog they posted the general availability of Windows Analytics: Update Compliance.  For those of you unfamiliar with Windows Analytics, it is one of Microsoft's Operations Management Suite offerings. This solution collects system data including update installation status, Windows Update for Business configuration data, Windows Defender status data and sends that data to be analysed. To start learning more and set up a free trial, head on over to the Windows Analytics page.

Update Compliance provides the following:

• Dedicated drill-downs for devices that might need attention
• An inventory of devices, including the version of Windows they are running and their update status
• The ability to track protection and threat status for Windows Defender Antivirus-enabled devices
• An overview of WUfB deferral configurations (Windows 10 Anniversary Update [1607] and later)
• Powerful built-in log analytics to create useful custom queries
• Cloud-connected access utilizing Windows 10 telemetry means no need for new complex, customized infrastructure

More Windows 10, version 17o9 news... the ADMX templates are available for download.

Details

ISSUE:

User receives message "We couldn't sync this library. This library can no longer be synced using this application. To sync these files, use the latest OneDrive application", when trying to sync using OneDrive for Business (Groove) client.

RESOLUTION:

- In the search box on the taskbar, type regedit

- Select the top result, regedit Run command

- Update to registry key - HKEY_Current_UserSoftwareMicrosoftCommonGrooveDisablemysitesync from 1 to 0.

NOTE: If you continue to receive message, also check the same registry location for SPOTenantSyncClientRestriction key and change that key as well from 1 to 0.