We want to clear the air on a recent announcement around the upcoming changes to MPN – specifically the retirement of the Identity and Access Competency. Last week, Microsoft announced the streamlining of our MPN competencies, which includes not just retiring a select few over the next 18 months, but also evolving competencies to put Partners in the best position to support our mutual customers. As customers increasingly look to the cloud to meet their business needs, they want to know that our partners have the expertise to help them. Identity is at the forefront of any customer’s mind when leveraging cloud services and the recent changes in MPN competencies exemplifies more than ever that Microsoft is doubling down on Identity – not sun-setting.

The recent change for the Identity and Access competency should not be seen as Microsoft retiring it, but rather expanding the solution space to include Enterprise Mobility Management. Identity and Access has been merged with mobility to better support customers with their transformation to modern end-user productivity where Identity, Mobility and Information Protection all come together.

This change is not signalling in any way the end of any Microsoft products. In fact, we have more engineers working on Identity and Access Management today (600+ across the cloud and on-premises) than we have ever had before at Microsoft. Our Enterprise Mobility Suite’s primary focus is securing a mobile enterprise led with Identity-driven security, and is on track to a billion-dollar business. Microsoft has always strived to align the key competencies to reflect the true market and business needs of our customers and partners – this transition is a great example of us continuing to do so.

While we understand any change be can a challenge, the moves are all aimed to helping our partners find greater success. You can learn more using the MPN Evolution Competency Guide or join our webinar on Thursday 28th April. If you have any questions, please use the live chat option on MPN Evolution page or contact your Microsoft contacts .

We value your partnership through this important evolution and look forward to your continued engagement in building our businesses together.

We have new updates for Surface Pro 3 devices. We also have a new tool for updating the Surface Dock on these devices. These updates are available now.

We are currently working on the MSI and ZIP files for the recent updates to Surface Pro 4 and Surface Book devices. We will let you know as soon as these are available.

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

Updates for Surface Pro 3 devices running Windows 10 The following updates will be listed as multiple updates when you check for updates in Windows, or when you view your Windows update history after installing the updates:   Microsoft driver update for Surface Dock Firmware Update Microsoft driver update for Surface Dock Integration These updates are available at http://aka.ms/drivers/surfacepro3 SurfacePro3_Win10_160420_0.zip SurfacePro3_Win10_160420_0.msi Surface Dock Integration driver update (v1.0.6.0) improves stability and compatibility with external monitors and passive video adapters. Surface Dock Firmware Update (v.1.2.6.0) improves stability and compatibility with external monitors and passive video adapters.

Updates for Surface Pro 3 devices running Windows 8.1 The following update will be listed as “Surface Firmware Update – 4/19/2016” or “Surface Hardware Update – 4/19/2016” when you view your update history after installing the updates. These updates are available at http://aka.ms/drivers/surfacepro3 SurfacePro3_Win8x_160420_0.zip SurfacePro3_Win8x_160420_0.msi Surface Dock Integration driver update (v1.0.6.0) improves stability and compatibility with external monitors and passive video adapters. Surface Dock Firmware Update (v.1.2.6.0) improves stability and compatibility with external monitors and passive video adapters.

The Surface Dock Updater When updates are available for the Surface Dock, you can use the same method to deploy them as you are using for other Surface updates. As with Surface updates, users can receive the updates via Windows Update when the dock is connected to a Surface device, or you can visit the Microsoft Download Center at to download the files directly. If you are looking for a way to update multiple docks in the least amount of time, you also have the option of downloading the Surface Dock Updater tool from the Microsoft Download Center at https://www.microsoft.com/en-us/download/details.aspx?id=46703 Surface_Dock_Updater_v1.0.8.0.msi

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

Thanks,

Surface IT Pro Marketing team

2016/4/26 更新:  このブログ記事は以前 Office 2013 更新プログラム KB3114928 の問題として公開していましたが、Outlook 2013 更新プログラム KB3114941 の問題であることが判明したため更新しました。

2016/4/6 (米国日付 2016/4/5) にリリースされた Outlook 2013 の更新プログラム KB3114941 (英語日本語機械翻訳) を適用すると Outlook 2013 と Lync 2013 (Skype for Business) 利用時にランダムにクラッシュが発生する場合がある不具合を確認しており、以下のサポート技術情報 3158521 を公開しておりますのでご確認ください。
この問題について進捗がありましたら本ブログの情報を更新いたします。

KB3158521 Lync 2013 (Skype for Business) or Outlook 2013 Crash

クイック実行版の Office (Office 365 ProPlusや 店頭で購入したダウンロード版など) :
・現時点では、配信停止や再リリースはされていない。
・適用されている場合は Outlook 2013 の [ファイル] タブ-[Office アカウント]-[Outlook のバージョン情報] をクリックした画面の Microsoft Outlook 2013の右側に「15.0.4815.1000」と表示される。

MSI 版の Office (ボリュームライセンスなど) :
・現時点では、配信停止や再リリースはされていない。
・適用されている場合は Outlook 2013 の [ファイル] タブ-[Office アカウント]-[Outlook のバージョン情報] をクリックした画面の Microsoft Outlook 2013の右側に「15.0.4815.1000」と表示される。。

回避方法
以下のいずれかの方法での対応をお願いいたします。

方法 1. KB3114941 をアンインストールし、以前のバージョンに戻す

クイック実行版の Office (Office 365 ProPlus や 店頭で購入したダウンロード版など)  :
・こちらのブログ  の手順に従って以前のバージョンに戻す  (参考: KB2770432 (英語日本語機械翻訳))
   (コントロール パネルの [プログラムの機能] からアンインストールすることはできない)

MSI 版の Office (ボリュームライセンスなど) :
・コントロール パネルの [プログラムと機能] から KB3114941 をアンインストールする
・WSUS で KB3114941 に対して [削除の承認] を設定してアンインストールを配信する (こちらのブログの「WSUS での配布の停止手順」を参考に設定してください)

方法 2. レジストリ MSOAuthDisabled を作成する

HKEY_CURRENT_USER\Software\Microsoft\Exchange
値の名前: MsoAuthDisabled
値の種類: 1

参考:
Outlook 2013 では、2014/9 以降の更新プログラムが適用されている場合は
従来の Windows の機能を利用した認証ではなく、Office 固有の認証システムで認証が行われます。
上記のレジストリを設定すると、Office 固有の認証システムではなく、
従来の Windows の認証システムを用いて認証を行うように動作が変更されます。

Office 固有の認証システムは以下の認証を利用するために必要であり、
これらの認証を利用している場合はレジストリで回避することができませんが、
これらの認証を利用する必要がない場合は特に影響はありません。

・多要素認証
・Azure Active Directory 認証ライブラリによる認証
・スマートカード認証

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

変更前の記事:

タイトル: 2016/4 の Office 2013 更新プログラム KB3114928 を適用すると Outlook 2013 や Lync 2013 (Skype for Business) がクラッシュする

2016/4/6 (米国日付 2016/4/5) にリリースされた Office 2013 の更新プログラム KB3114928 (英語日本語機械翻訳) を適用すると Outlook 2013 と Lync 2013 (Skype for Business) 利用時にランダムにクラッシュが発生する場合がある不具合を確認しており、以下のサポート技術情報 3158521 を公開しておりますのでご確認ください。
この問題について進捗がありましたら本ブログの情報を更新いたします。

KB3158521 Lync 2013 (Skype for Business) or Outlook 2013 Crash

クイック実行版の Office (Office 365 ProPlusや 店頭で購入したダウンロード版など) :
・現時点では、配信停止や再リリースはされていない。
・適用されている場合は Outlook 2013 の [ファイル] タブ-[Office アカウント] に
  「バージョン: 15.0.4815.1001」と表示される。

MSI 版の Office (ボリュームライセンスなど) :
・現時点では、配信停止や再リリースはされていない。
・適用されている場合は Outlook 2013 の [ファイル] タブ-[Office アカウント]-
   [Outlook のバージョン情報] をクリックした画面の MSO の右側に「15.0.4815.1000」と表示される。

回避方法
以下のいずれかの方法での対応をお願いいたします。

方法 1. KB3114928 をアンインストールし、以前のバージョンに戻す

クイック実行版の Office (Office 365 ProPlus や 店頭で購入したダウンロード版など)  :
・こちらのブログ  の手順に従って以前のバージョンに戻す  (参考: KB2770432 (英語日本語機械翻訳))
   (コントロール パネルの [プログラムの機能] からアンインストールすることはできない)

MSI 版の Office (ボリュームライセンスなど) :
・コントロール パネルの [プログラムと機能] から KB3114928 をアンインストールする
・WSUS で KB3114928 に対して [削除の承認] を設定してアンインストールを配信する (こちらのブログの「WSUS での配布の停止手順」を参考に設定してください)

方法 2. レジストリ MSOAuthDisabled を作成する

HKEY_CURRENT_USER\Software\Microsoft\Exchange
値の名前: MsoAuthDisabled
値の種類: 1

参考:
Outlook 2013 では、2014/9 以降の更新プログラムが適用されている場合は
従来の Windows の機能を利用した認証ではなく、Office 固有の認証システムで認証が行われます。
上記のレジストリを設定すると、Office 固有の認証システムではなく、
従来の Windows の認証システムを用いて認証を行うように動作が変更されます。

Office 固有の認証システムは以下の認証を利用するために必要であり、
これらの認証を利用している場合はレジストリで回避することができませんが、
これらの認証を利用する必要がない場合は特に影響はありません。

・多要素認証
・Azure Active Directory 認証ライブラリによる認証
・スマートカード認証

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

Today’s Tip…

Azure App Service supports V2 (Azure Resource Manager) virtual networks. This means you can integrate your web, mobile, or API apps with your V1 or V2 virtual networks.  

To do this, go to your app > Settings > Networking blade, just as you did previously for integrating V1 virtual networks.

You can select a V1 or V2 virtual network for integration. A V1 virtual network has “(Classic)” after the name. Creating a new virtual network will create a V2 virtual network with a gateway and point to site (P2S) enabled, but it won’t set up the network with your app. 

If you have a pre-existing V2 virtual network, follow the online guidance for how to set up a gateway with P2S before it can be selected for integration.

For more information, see Integrate your app with an Azure virtual network.

The following is a list of updates for Audit and Control Management Server 2013 (ACM) and Discovery and Risk Assessment Server 2013 (DRA). The list will be updated each time a new hotfix is released for these products. You can compare the KB numbers in this list with the updates installed on your machine to make sure you have all the updates.

KB2837623 - April 8, 2014 update for ACM

https://support.microsoft.com/en-us/kb/2837623

KB2881010 - October 14, 2014 update for ACM

https://support.microsoft.com/en-us/kb/2881010

KB2899503 - May 12, 2015 update for ACM

https://support.microsoft.com/en-us/kb/2899503

KB2881006 - May 12, 2015 update for DRA

https://support.microsoft.com/en-us/kb/2881006

KB3039793 - April 5, 2016 update for ACM

https://support.microsoft.com/en-us/kb/3039793

A very short one from me today, we recently published an interactive tutorial in troubleshooting PXE. Choose to get straight down to it or go through an overview and background of PXE first:

https://support.microsoft.com/en-us/help/10082/troubleshooting-pxe-boot-issues-in-configuration-manager-2012

Rob York

Premier Field Engineer

56.     K čemu slouží styly?

57.     Jak vytvořit nový styl?

58.     Jak upravit styl?

59.     Jak najít výskyt slova v dokumentu?

 

60.     Jak nahradit slova v dokumentu?

日本マイクロソフト System Center Support Team の三輪です。先週リリースされた、System Center/Azure/Intune に関連する公開技術情報をまとめました。役に立つ手順や修正プログラムの情報など、製品をお使いいただく上で参考になる情報があるかと思います。ご参照ください。なお、ブログはすべて英語となっています。ご了承ください。

ブログ

Each year, the Microsoft Cloud and Hosting Summit provides an unparalleled opportunity for leaders across the industry to connect and share ideas on how to expand and build new services, drive innovation, and create new business opportunities.  

This year we are pleased to provide you the ability to join a LIVE virtual stream of the keynote sessions. Gather your team in your local office and watch the sessions with the theme “Empowering Digital Transformation”.

Dates: Wednesday, May 11 and Thursday May 12 - view agenda and register here: http://aka.ms/mshost16

Today’s Tip…

I read a recommended article in the Redmond Channel Partner called “Microsoft Brings Some Transparency to Windows 10 Updates”. The article included several links that I found very useful and wanted to share them with you.

Windows 10 Update History: http://windows.microsoft.com/en-us/windows-10/update-history-windows-10

This article provides additional information on the updates for Windows 10 through Windows Update. It is a summary of “important developments included in each update, with links to more detail.” You can expect this page to be updated as new information comes out. The two branches (TH1, 10240) and (TH2, 10586) are discussed in detail with a list of “quality improvements and security fixes” and the current build number (i.e. 10240.16683 and 10586.104).

Windows 10 Release Information: https://technet.microsoft.com/en-us/windows/mt679505.aspx?ocid=wc-ext-aka

This article provides great tables with the Windows 10 current versions by servicing option (servicing option: CB, CBB, LTSB, version: 1507, 1511, OS build number, availability date, and latest revision date) and the Windows 10 release history by version (OS build number, availability date, servicing option, and corresponding KB Article number and link).

New Windows as a Service Information Published: http://blogs.technet.com/b/windowsitpro/archive/2016/02/09/new-windows-as-a-service-information-published.aspx

This blog post, written by Michael Niehaus, has links to the above two sites as well as links to the following:

• Windows 10 Servicing Options for Updates and Upgrades: https://technet.microsoft.com/en-us/library/mt598226(v=vs.85).aspx
• Preparing Your Enterprise for Windows 10 as a Service (37 min video): https://mva.microsoft.com/en-US/training-courses/preparing-your-enterprise-for-windows-10-as-a-service-11813?l=uUf1tqtQB_8505094681
• Microsoft Ignite 2016: https://ignite.microsoft.com/#fbid=Hm0pnCQv-ea

Windows 10 Servicing Options: https://technet.microsoft.com/en-us/library/mt574263%28v=vs.85%29.aspx

This TechNet article has a great deal of information, explaining the different servicing options in detail. It opens with key terminology to help users distinguish between upgrade and update, and branch and ring. It provides an overview of all three branches, and a comparison between Current Branch and Current Branch for Business. Most importantly (IMHO) is the “Switching Between Branches” table. It provides the break down from what you currently have, what you want to change to, to what you need to do.

There’s a great deal of information out there!

Hi, my name is Prachi and today I will be talking about a patch installation problem which occurs when multiple patches are installed together.

Consider the following scenario

You have a scheduled task\script that scans for updates and while it detects multiple updates, it fails when installing them. If you check the update history, you see that it failed to install any update after it tried to install a security update. The security update, then shows reboot required. 

When you open the CBS logs located in C:\windows\logs\CBS, you see the following:

2015-08-30 04:25:29, Info                  CSI    00000235 Component change list:
2015-08-30 04:25:29, Info                  CSI    00000236 Couldn't find the hash of component: Microsoft-Windows-BootEnvironment-OS-Loader.Resources, Version = 6.1.7601.23136, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the catalog [l:192{96}]"\SystemRoot\WinSxS\Catalogs\33aaa08f767a1d074889ca79e8ed861442eef084bcbaaa5379376ad63e2c87d5.cat".
2015-08-30 04:25:29, Error                 CSI    00000237@2015/8/30:04:25:29.184 (F) : Error 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] originated in function CCSDirectTransaction::AddImplicationsToCatalogsAndVerifyComponentHashes expression: (null)
[gle=0x80004005]
2015-08-30 04:26:07, Error                 CSI    00000238 (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #14706236# from CCSDirectTransaction::PrepareForCommit(...)[gle=0x90092004]
2015-08-30 04:26:07, Error                 CSI    00000239 (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #14706235# from CCSDirectTransaction::ExamineTransaction(...)[gle=0x90092004]
2015-08-30 04:26:07, Error                 CSI    0000023a (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #14706234# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0x90092004]
2015-08-30 04:26:07, Error                 CSI    0000023b (F) CRYPT_E_NOT_FOUND #14705449# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80092004]
2015-08-30 04:26:07, Error                 CSI    0000023c (F) CRYPT_E_NOT_FOUND #14534227# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 47 (0x0000002f), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x80092004]
2015-08-30 04:26:07, Error                 CSI    0000023d (F) CRYPT_E_NOT_FOUND #14534226# 42410326 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x0000002f, pSink = NULL, disp = 0)
[gle=0x80092004]
2015-08-30 04:26:07, Error                 CBS    Exec: Failed to commit CSI transaction to resolve execution chain. [HRESULT = 0x80092004 - CRYPT_E_NOT_FOUND]
2015-08-30 04:26:07, Info                  CSI    0000023e@2015/8/30:04:26:07.856 CSI Transaction @0x2feaf1b0 destroyed
2015-08-30 04:26:07, Info                  CBS    Perf: Resolve chain complete.
2015-08-30 04:26:07, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x80092004 - CRYPT_E_NOT_FOUND]
2015-08-30 04:26:07, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80092004 - CRYPT_E_NOT_FOUND]
2015-08-30 04:26:07, Info                  CBS    WER: Generating failure report for package: Package_for_KB3071756~31bf3856ad364e35~amd64~~6.1.1.2, status: 0x80092004, failure source: Resolve, start state: Absent, target state: Installed, client id: WindowsUpdateAgent

This happens because security updates usually require a reboot to commit and will fail any update that is installed after that. Please note that once you encounter a security update, it always does ask for a reboot. In addition to committing the transactions, a reboot is also responsible for committing a task called scavenging.Please note that scavenging is invoked on system startup (when TrustedInstaller starts on boot), system shutdown and idle processing.

There is another type of reboot called a non-mandatory reboot which only requires scavenging.

You can manually invoke scavenging by stopping and starting the Windows Modules Installer (TrustedInstaller) service. Please note that scavenging, as the name suggests, removes the unused components and it might help with the problem but only when the reboot required is non-mandatory.

If a third party software is being used for this, the following steps can be added to the schedule:

1. Check the patch to see if it is a security patch.
2. If it is a security patch, then install it and restart the Windows Modules Installer (TrustedInstaller) service.
3. If not, then simply install it.

NOTE: Types of RebootRequired in the Windows Update system

There are two levels of “reboot required” within the Windows Update system. There’s “mandatory reboot required”, which basically means “nothing more will happen in Windows Update until you reboot”; and there’s “non-mandatory reboot required”, which basically means “You can’t do new scans, but you can continue to install updates that you already located through previous scans”.

A non-mandatory reboot creates the key:

SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired

A mandatory reboot creates the key

 SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired\Mandatory

Prachi Gupta

Support Engineer |Microsoft Windows Core

Disclaimer : This information is provided ‘as-is’ with no warranties

With Windows Server 2016 Technical Preview 5, you can create Nano Server VMs directly in Azure, using the Nano Server image in the Azure Gallery.

Please use an elevated PowerShell console (classic or ISE) and use the instructions in the following blog to install the Azure Resource Manager cmdlets: https://msdn.microsoft.com/en-us/library/mt125356.aspx

Instructions

Download the zip file attached to this blog and unzip its contents to a local folder on your machine.

Log in to your Azure account:

Login-AzureRmAccount

Run the following commands to create a resource group and a key vault, if you haven’t already:

New-AzureRmResourceGroup -Name "MyResourceGroupName" -Location 'West US'

New-AzureRmKeyVault -VaultName "MyKeyVaultName"  -ResourceGroupName "MyResourceGroupName" -Location 'West US' -EnabledForDeployment

Make sure you use the same Resource Group Name in both cmdlets.  Select the Azure location that is best for you. I chose ‘West US’ because I’m on the West coast.

Now, it’s time to import the module that was part of the package you unzipped to a local folder:

Import-Module .\NanoServerAzureHelper.psm1 -Verbose 

You’re now ready to create a Nano Server VM (you will be prompted for the admin password):

New-NanoServerAzureVM -Location 'West US' –VMName "MyVMName" -AdminUsername "MyAdminName" -VaultName "MyKeyVaultName" -ResourceGroupName "MyResourceGroupName" -Verbose 

Let’s establish a secure PowerShell remote session to our new VM:

Get-AzureRmPublicIpAddress -ResourceGroupName "MyResourceGroupName"

Observe the output of this cmdlet and copy the FQDN string, under DnsSettings. It will look something like: "MyVMName.westus.cloudapp.com". Use it for the secure connection as follows: 

Enter-PSSession -ConnectionUri "https://MyVMName.westus.cloudapp.com:5986/WSMAN" -Credential MyAdminName

That’s it! 

Unlike previous Nano Server images in Azure, the optional roles and features are no longer in the image. Starting with TP5, they can be installed from an online repository so you have a smaller image. To add roles and features to your Nano Server VM, consult the Nano Server Getting Started Guideand refer to “Installing roles and features online”.

To access the VM securely from another machine

If you want to access the VM you created securely from another machine, you need to export the certificate from your original client to another machine. Here’s how:

1. Run certlm.msc
2. Select “Trusted Root Certification Authorities”
3. Select “Certificates”
4. Look for the certificate that is named after your VM name
5. Right-click this certificate and select “All Tasks” -> “Export” and save it to a USB drive or a shared folder.
6. On the target machine, double-click this exported certificate and click “Install Certificate”
7. Select “Current User” -> Next
8. Select “Place all certificates in the following store”, click “Browse” and select “Trusted Root Certification Authorities” -> Next -> Finish

For information on Nano Server containers and Docker, please see the following blogs:

https://msdn.microsoft.com/en-us/virtualization/windowscontainers/deployment/deployment_nano

https://msdn.microsoft.com/en-us/virtualization/windowscontainers/quick_start/manage_docker

ref@

Nano Server represents a great opportunity for applications to get the most of available resources and deliver customers an agile environment which supports a DevOps management model.  In order for applications to do this, they need to remove references to components not delivered in Nano Server (this typically means APIs which bring in the GUI or 32 bit references).

To make developing and porting apps to Nano Server easy, we added “decorations” to the Windows header files to include the right APIs, and created a Visual Studio template which leverages this header decoration work, and automates the inclusion of the right headers and libraries. You can enjoy full IntelliSense and error squiggles support.

Thanks to the Visual Studio Debugger team, the Nano Server developer experience includes full remote debugging from Visual Studio!

To automate some of the mundane tasks, we’re also including a small PowerShell module to make it easy to install the debugger binaries on the Nano Server machine, as well as start & stop the debugger.

Prerequisites

1. On your development machine, you should be running the latest version of PowerShell, i.e. Windows 10, a preview release of Windows Server 2016, or the latest version of the Windows Management Framework.
2. Make sure your development machine is running Hyper-V, if you’re going to run Nano Server in a VM.  Otherwise, make sure that your development machine has network access to your Nano Server machine.
3. Install the Update 2 version of Visual Studio 2015. Here’s a link to download the free community version of Visual Studio.  Make sure to choose “Custom” install, and under “Universal Windows App Development Tools”, ensure that “Tools (1.2) and Windows 10 SDK” is checked.
4. Download the zip file attached to this blog and unzip it:
   1. Double-click on NanoServerProjectExtensions.vsix and follow instructions to install it.
   2. Import the PowerShell module (NanoServerDebugger.psm1) by opening an elevated PowerShell or ISE session, use Import-Module and pass the full path to the .psm1 file.  Don’t close the PowerShell session! If you do, you would have to import the module every time you open the PowerShell session (unless you use a PowerShell profile of course J).
5. Follow the instructions in Getting Started with Nano Server to build your Nano Server VHD using New-NanoServerImage, and then use it to boot on a physical machine or in a VM.

Writing your First App

Now you’re ready to develop your first Nano Server app. Let’s write and debug a simple app.

1. Create a new project and, under Visual C++, choose “NanoServerApplication”.  Call your project “NanoApp1”.
2. In the debug target drop down, select x64 as the target platform
3. In the Project Properties dialog, under “General”, make sure that the “Target Platform Version” is 10 (typically 10 point something).
4. In Solution Explorer, double-click on NanoServerApplication.cpp. In _tmain, add printf(“Hello from Nano Server!\n”); Press Ctrl+F5 to make sure everything works locally.
5. From an elevated PowerShell or ISE console (import the PowerShell module again if you closed the previous console), create a session to the Nano Server machine or VM, using the following commands (for more information, consult the Nano Server Getting Started guide):
   1. $ip = “ip address to the Nano Server machine”
   2. Ensure that TrustedHosts is set to the Nano Server IP address. Otherwise: Set-Item wsman:\localhost\client\TrustedHosts “ip address to the Nano Server machine”
   3. $s = New-PSSession –ComputerName $ip –Credential ~\Administrator
   4. Install-NanoServerDebugger –session $s
6. Copy the .exe and the .pdb files from the app you just wrote to Nano Server, using the same session object:
   1. Enter-PSSession $s
   2. Md c:\NanoApp1   # for example
   3. Exit-PSSession
   4. Copy-Item –ToSession $s –path “path to the .exe and .pdb files” –Destination c:\NanoApp1. Remember to do this every time you build a new .exe! (Alternatively, you can refer to the local pdb file, but make sure to change the project properties to reflect that).
7. In the project properties dialog, under Configuration Properties \ Debugging:
   1. Change the “Debugger to launch” to: “Remote Windows Debugger”. 
   2. Remote Command = C:\NanoApp1\NanoApp1.exe (full path to the Nano app executable)
   3. Working Directory = C:\NanoApp1 (path to the Nano app executable folder)
   4. Remote Server Name = IP address of the Nano Server machine
   5. Connection = “Remote with no authentication”
8. In the open PowerShell console, start the debugger using Start-NanoServerDebugger –Session $s
9. Now you’re ready to debug your app.  Set a breakpoint and press F5 and you’re good to go! Use locals, watches … pretty much everything you’re used to using in a debugging session.
10. To stop the debugger, use: Stop-NanoServerDebugger –Session $s         

Note that the cmdlet you used (Install-NanoServerDebugger) also copied the Visual C++ runtime binaries to your Nano Server machine. If you want to run your app on another Nano Server machine, either:

• ·      Download the Visual C++ redistributable package from here, install it on your development machine, and copy the binaries over to Nano Server.

-or-

• ·      Include the required contents of the Visual C++ redistributable package that your app is dependent on as part of your app install.

Now that our simple app is working, try your hand at a WMI provider, such as this MI API sample (which also creates a PowerShell cmdlet along with the provider), or Querying a Service's Configuration.

At any rate, you’ll want to make sure that your application can participate in a DevOps management model.  This entails two things:

1. Ensure your application can be fully configured using PowerShell Desired State Configuration (DSC).  Writing a DSC provider ensures that customers can choose the DevOps deployment tool of their choice and ensure that your application will “just work”. (Note that DSC is now available on Nano Server starting with Technical Preview 4)
2. Ensure your application can be fully managed remotely via PowerShell.  You can write PowerShell cmdlets in native code using a WMI V2 provider, in managed code using .NET Core, or in PowerShell itself.

Please use the Nano Server forum to ask questions. We look forward to your feedback. 

Happy coding :)

ref@

In Windows Server 2016 Technical Preview 4 we introduced a new installer: Windows Server App (WSA). WSA is important as it is the officially supported Server Installer going forward and is the only installer available on Nano Server.  WSA is a significant shift from the traditional MSI installer technology (for more background read the blog posted in TP4).  In particular, WSA has no Custom Actions which means that it is purely declarative.  In a recent interview, our Technical Fellow Jeffrey Snover called MSI Actions “the portal to hell” for servers. WSA’s declarative architecture enables us to meet the demanding needs of server scenarios.

To increase reliability of an application’s uninstall and upgrade, we have added support for several new APPX extensions in Technical Preview 5 (TP5).  These extensions replace the old MSI way of using custom actions for creating performance counters and ETW providers, making them first class citizens that are handled by the WSA installer. Below is the current extension support:

• NT Service – released in TP4
• WMI provider – released in TP4
• COM classes/Interfaces/AppIDs – released in TP4. However, the COM extension is subject to further breaking changes for Windows Server 2016 RTM and beyond.
• Performance counter – new in TP5
• ETW provider – new in TP5

In addition to Nano Server, WSA is now also available for the Server with Full Desktop Experience SKU.  This enables server applications to use a single, uniform WSA package regardless of which Windows Server installation option was used.

Try it out! Let us know your feedback.

Microsoft recently announced some changes to the Microsoft Partner Network (MPN) Program that will allow better alignment with Partners who have or are moving to a Cloud practice.

With this focus on the cloud, I thought it would be appropriate to highlight some of Microsoft’s key Cloud Competencies and how you can join the successful Cloud partners drive higher margins, greater recurring revenue streams and attract more new customers with your focus on the Cloud.

If you already selling Microsoft Office, have an existing cloud practice or want one, and are interested in driving more customers to the Cloud with Office 365, then this is for you. Did you know that 80% of Fortune 500 companies are using Office 365? (Microsoft Internal Research) I’ve outlined below what competencies of the MPN Program are most suited to you, what kind of benefits you can earn, and how to get started.

There are 2 key Microsoft Competencies that are focused on Office 365 Online:

1. Small & Midmarket Cloud Solutions
2. Cloud Productivity

The one best suited to you depends on the Office 365 volumes you are driving and the number of customers you have.

Benefits of becoming a MPN Cloud Competency partner:

Ever wondered if you can get Office 365 for free? The answer is yes! When you sign up for a Cloud Competency, you will earn incremental Office 365 licenses in addition to those you get with the Core benefits. These Internal Use Rights (IURs) can be used internally or for demo purposes, but not for resale.

There are many types of Support you will be eligible for once you become an MPN Partner including Partner Advisory Hours, Product Support, Technical Pre-Sales Assistance and Cloud Signature Support, which is an exclusive technical benefit for qualified Cloud Competency partners and allows you to work directly with support engineers.

Other great benefits to having a Cloud Competency are monthly Azure credits, Pinpoint prioritization, access to offers, competency logo & a partner account manager.

How to earn a Competency:

Once you start selling Office 365, it’s only natural that you’ll want to earn benefits from Microsoft and grow your business even more with all the tools, resources, support and other benefits that are art of the Microsoft Partner Network.

What do you need to do to earn a Competency & start earning benefits?

1. Start selling Office 365

The Office 365 performance requirements start as little as 40 seats with 4 new customers in the prior 12 months, for the Silver tier of Small & Midmarket Cloud Solution competency. Already selling more than that. Consider a Gold tier or consider the Cloud Productivity competency and earn even more benefits.

In order for Microsoft to track your performance, you will need to ensure that you are listed as the Digital Partner of Record (DPOR) with your customers.

2. Pass Technical exams

There is no exam for the Silver tier of Small & Midmarket Cloud Solution competency, but others do require you to write 1 or more exams. Each exam typically costs approximately USD $150.00 and they are good for 12 months. All details on exam options and requirements are listed by competency on the MPN portal.

3. Get Customer references

Your organization must submit 3-5 Microsoft Office 365 customer references from within the previous 12 months, depending if you are applying for Silver or Gold Competency tier. After a reference has been approved, it can be used toward earning or renewing a competency for up to two years.

4. Pay the fee

There are annual fees to get a Cloud Competency, but these are far outweighed by the benefits will you earn in return. Costs vary between Silver and Gold Competency. Until June 30, 2016 Microsoft is waiving the fee for Silver Small & Midmarket Cloud Solutions and Cloud Productivity Competencies. If you are already a Silver partner, you can earn your way to Gold without paying the Gold fee until your anniversary date.

Interested in moving your customers over to Office 365 but don’t know how to quickly ramp your business?

Microsoft has partnered with Skykick to provide free use of their backup and migration tools. If you haven’t used Skykick Cloud Backup before, Microsoft Action Pack and Competency Partners who have activated their Azure internal use rights can use Skykick Cloud Backup for free as a benefit of MPN Membership through June 30, 2016. Visit www.skykick.com/AzureIUR  for more info.

It has been a year since we initially released PackageManagement (a.k.a. OneGet) feature in Windows 10. PackageManagement automates software discovery, installation, and inventory (SDII), regardless of the package formats or where the packages are from.  During this past year, PackageManagement has expanded to other Windows SKUs and versions, including:

• For down-level OS (Windows Server 2012 R2, Windows Server 2012, Windows 2008 R2 SP1, Windows 8.1, and Windows 7 SP1), it is part of theWindows Management Framework (WMF) 5.0
• It has been included in Nano Server since Windows Server 2016 Technical Preview 4 (TP4)

Today I will focus on its usage and providers on Nano Server.

As you may know, Nano Server is a new deployment option of Windows Server that has a tiny footprint and runtime.  The model for Nano Server is to start small and then add only the features/components that you will use.  So PackageManagement is a core technology of Nano Server and the results are stunning:  Windows Server with a Desktop is about 10 GB, Server Core is about 5GB and Nano Server is about 440MB.

One of the ways Nano Server is so small is because it does not support the GUI stack or 32bit code.  This means that a PackageManagment provider running on Windows 10 or full server may not be able to run on Nano Server anymore, because of the API that the provider depends on is not available. You will need to port the provider first. You can leverage these two tools to analyze the code,

• the API PortabilityAnalyzer tool for managed code
• the NanoServerApiScan.exe tool for native code

Also, you will see a different set of providers available on Nano Server.  Below is a recap of the PackageManagement architecture and provider list on Nano Server.

Except for PowerShellGet provider that comes in the box, all other providers will be installed on demand. Let’s explore the cmdlets that PackageManagement provides.

For a complete usage of each cmdlet, please read the Technet doc.

Install a PackageProvider

The common steps to install a package provider are:

 You can add –force to both cmdlets to overwrite an existing provider. Use Get-PackageProvider to list providers that are installed in the local machine.

Software Discovery/Install/Inventory (SDII)

Once the provider is installed and imported, you can search, install, inventory software packages from that provider. In general, you can use the generic PackageManagement cmdlets to do so. For each provider, it may provide its own cmdlets specific to the package type, such as the PowerShellGet, ContainerImage, NanoServerPackage providers. This way, depending on your experience and usage, you can choose between the generic PackageManagement cmdlets and the specific cmdlets for that particular type of package. Here is a quick introduction for each provider available on Nano Server.

PowerShellGet

PowerShellGet manages PowerShell modules and scripts stored in an online gallery. By default, PowerShellGallery.org is the package repository.

NuGet

NuGet provider is a special provider. It is a protocol provider in the sense that it handles NuGet V2 protocol to connect to any package source (or repository) that is based on NuGet V2 server. PowerShellGallery.org is an example. Hence PowerShellGet relies on NuGet provider to connect to its gallery.   On the other hand, it is a package provider to manage NuGet packages, such as those in NuGet.org.

ContainerImage

ContainerImage provider can search, download, or install Windows container OS images from an online gallery. It is new in Windows Server 2016 Technical Preview 5 (TP5). For more information, please read the ContainerImage on GitHub for the provider, and the Container MSDN doc on how to manage Windows Containers.

NanoServerPackage

NanoServerPackage provider can search, download, or install Windows packages (feature and role) for Nano Server from an online gallery. It is new in TP5. For more information, please read the NanoServerPackage on GitHub for the provider, and Getting Started with Nano Server doc.

WSAProvider

WSA is a new installer on Nano Server.  WSAProvider wraps on top of APPX cmdlets and provides search capability for WSA packages from a local folder or network share. You can find more information on WSA here and WSAProvider on GitHub.