Office 2019 Commercial Preview Program

Office 2019 Commercial Preview program


Thank you for your interest in the Microsoft Office 2019 Commercial Preview program. This preview program is intended only for organizations that plan to deploy the perpetual (volume licensed) version of Office 2019 when it’s released later this year. For more information, see the Tech Community blog post.


To join the Office 2019 Commercial Preview program, you or your company must be registered with Microsoft Collaborate. If you’re not able to sign in to the Microsoft Collaborate portal, follow the instructions at Microsoft Collaborate: Documentation and guidance.

If you need support with Microsoft Collaborate, see How to get support and troubleshoot common Issues.

Join the Office 2019 Commercial Preview Program

The Preview program is available through Microsoft Collaborate, which is the only location for joining, accessing deployment packages and documentation, and providing feedback.

To join the program, follow these steps:

  1. Sign in to
  2. On the Overview page in your dashboard, select Engagements to view engagements that are available to join.
    Select Engagements
  3. Find the Office 2019 Commercial Preview engagement, select Join, accept the Terms of Use, and then select Join again.
  4. If you no longer want to participate in the Preview program, select Leave.
    Click Leave

How to download packages

  1. From the dashboard, select Packages to go to the Packages page, where you will see all packages that are associated with the engagement.
  2. Select a package to view the details and the list of files that are included in the package.
    Select package
  3. Select the download icon to download the file.

Submit feedback

To submit feedback during the program, select Feedback in the dashboard. You can view all feedback that you submitted to the Office engineering team on the Feedback page.

The value of the State column indicates the state of your feedback:

  • New – New submission.
  • Resolved – The Office team has taken appropriate action and resolved the issue.
  • Closed – The issue is closed. No more action will be taken.

To submit new feedback, follow these steps:

  1. On the All Feedback page, select Submit New Feedback.
    Submit feedback
  2. If you participate in multiple engagements, select the engagement for which you want to provide feedback.
    Select engagement
  3. On the Office 2019 Commercial Preview feedback page, complete the required fields in the feedback template. Provide as much detail as possible, including thorough reproduction steps, and then select Save.

Updates to your feedback will appear in the feedback item until the issue is resolved, such as the status is changed to “Closed.”

Cloud Adaptation and SharePoint Server Test Lab Guide for IT Professionals

Use these cloud adoption Test Lab Guides (TLGs) to set up demonstration or dev/test environments for Office 365, Enterprise Mobility + Security (EMS), Dynamics 365, and Office Server products.

TLGs help you quickly learn about Microsoft products. They’re great for situations where you need to evaluate a technology or configuration before you decide whether it’s right for you or before you roll it out to users. The “I built it out myself and it works” hands-on experience helps you understand the deployment requirements of a new product or solution so you can better plan for hosting it in production.

TLGs also create representative environments for development and testing of applications, also known as dev/test environments.

Test Lab Guides in the Microsoft Cloud

See these additional resources before diving in:

Use these articles to build your Office 365 dev/test environment:

  • Base Configuration dev/test environment

    Create a simplified intranet running in Microsoft Azure infrastructure services. This is an optional step if you want to build a simulated enterprise configuration.

  • Office 365 dev/test environment

    Create an Office 365 Enterprise E5 trial subscription, which you can do from your computer or from a simplified intranet running in Azure infrastructure services.

  • DirSync for your Office 365 dev/test environment

    Install and configure Azure AD Connect for directory synchronization with password synchronization. This is an optional step if you want to build a simulated enterprise configuration.

For your Office 365 dev/test environment, use these articles to demonstrate enterprise features of Office 365:

Create a dev/test environment for Microsoft 365 Enterprise scenarios with these articles:

Add a Dynamics 365 trial subscription and test Office 365 and Dynamics 365 integrated features and scenarios with these articles:

Create a dev/test environment that includes all of Microsoft’s cloud offerings: Office 365, Azure, EMS, and Dynamics 365. See The One Microsoft Cloud dev/test environment for the step-by-step instructions.

You can create a cross-premises dev/test environment, which includes an Azure virtual network and a simulated on-premises network, with these articles:

Here are additional cloud-based dev/test environments that you can create in Azure infrastructure services:

Join the discussion

Contact us Description
What cloud adoption content do you need? We are creating content for cloud adoption that spans multiple Microsoft cloud platforms and services. Let us know what you think about our cloud adoption content, or ask for specific content by sending email to
Join the cloud adoption discussion If you are passionate about cloud-based solutions, consider joining the Cloud Adoption Advisory Board (CAAB) to connect with a larger, vibrant community of Microsoft content developers, industry professionals, and customers from around the globe. To join, add yourself as a member of the CAAB (Cloud Adoption Advisory Board) space of the Microsoft Tech Community and send us a quick email at Anyone can read community-related content on the CAAB blog. However, CAAB members get invitations to private webinars that describe new cloud adoption resources and solutions.
Get the art you see here If you want an editable copy of the art you see in this article, we’ll be glad to send it to you. Email your request, including the URL and title of the art, to

Free Step by Step SharePoint Server 2013 Lab Guides by Microsoft

This Post contains a bunch of Free Step by Step SharePoint Server 2013 Lab Guides that Microsoft gives for free on its Download Center. Usually I post them together with the other free resources that Microsoft offers, however this is a Test Lab Guide (TLG) only post, and the rest of the resources will come later in the month.

Free Step by Step SharePoint Server 2013 Lab Guides by Microsoft

Microsoft Download Center

  1. Test Lab Guide: Configure SharePoint Server 2013 in a three-tier farm
  2. Test Lab Guide: Configure intranet and team sites for SharePoint Server 2013
  3. Test Lab Guide: Demonstrate permissions with SharePoint Server 2013
  4. Test Lab Guide: Demonstrate profile synchronization for SharePoint Server 2013
  5. Test Lab Guide: Demonstrate Social Features for SharePoint Server 2013
  6. Test Lab Guide: Demonstrate SAML-based Claims Authentication with SharePoint Server 2013
  7. Test Lab Guide: Demonstrate forms-based claims authentication for SharePoint Server 2013
  8. Test Lab Guide: Configure eDiscovery for SharePoint Server 2013
  9. Test Lab Guide: Create a Business Intelligence Baseline Environment
  10. Test Lab Guide: Configure Secure Store
  11. Test Lab Guide: Configure Excel Services
  12. Test Lab Guide: Configure the Excel Services unattended service account
  13. Test Lab Guide: Configure Excel Services data refresh by using an embedded connection
  14. Test Lab Guide: Configure Excel Services data refresh by using an external connection
  15. Test Lab Guide: Configure Visio Services
  16. Test Lab Guide: Configure the Visio Services unattended service account
  17. Test Lab Guide: Configure Visio Services data refresh using an external connection
  18. Test Lab Guide: Configure PerformancePoint Services
  19. Test Lab Guide: Configure data access for PerformancePoint Services
  20. Test Lab Guide Mini-Module: Configuring a Second SharePoint Server 2013 Farm 
  21. Test Lab Guide: Configure a Highly Available SharePoint Server 2013 Search Topology
  22. Test Lab Guide: Configure an Integrated Exchange, Lync, and SharePoint Test Lab

A very nice Poster from Microsoft that resumes the above
Teched North America

  1. Configuring Office Web Applications for Microsoft SharePoint 2013 
  2. Configuring Social Features in Microsoft SharePoint 2013 
  3. Extending the Search Experience in Microsoft SharePoint 2013 
  4. Introduction to Web Content Management in Microsoft SharePoint 2013 
  5. Designing a Microsoft SharePoint 2013 Site 

SharePoint 3-tier On Premises installation

This post is a complete solution for setting up SharePoint 2016 on-premise. Most of the documents available online do not provide a complete solution/steps to install SharePoint 2016 with all of the prerequisites to be installed manually. Also, troubleshooting steps are provided for some of the most common mistakes done while installing.

The Three-Tier Architecture

This post is based on the setup on to a virtual machine based environment and will guide you how to set up the SharePoint server 2016 in your VM environment. If you are looking for the similar setup into your physical machines then please do consider checking hardware and software requirements required, supported system, storage system and finally networking.

This document is a simplified guide written to cover all aspects and scenarios encountered while setting up the prerequisites for SharePoint 2016, system requirements, errors and problems faced during set up.

In this guide we will use Windows 2k12 R2 server as an example and explain the detailed procedure.


1. A Windows 2k12 server file (Windows_server_2012_r2_with_update_x64_dvd.iso)

According to your requirement and the installation scenario use the below configurations:

Installation scenario Deployment type and scale RAM Processor Hard disk space
Single server role that uses SQL Server Development or evaluation installation of SharePoint Server 2016 with the minimum recommended services for development environments. Use the Single-Server farm role that will let you choose which service applications to provision. For additional information on Single-Server farm role, see Overview of MinRole Server Roles in SharePoint Server 2016 16 GB 64-bit, 4 cores 80 GB for system drive100 GB for second drive
Single server role that uses SQL Server Pilot or user acceptance test installation of SharePoint Server 2016 running all available services for development environments. 24 GB 64-bit, 4 cores 80 GB for system drive100 GB for second drive and additional drives
Web server or application server in a three-tier farm Development or evaluation installation of SharePoint Server 2016 with a minimum number of services. 12 GB 64-bit, 4 cores 80 GB for system drive80 GB for second drive
Web server or application server in a three-tier farm Pilot, user acceptance test, or production deployment of SharePoint Server 2016 running all available services. 16 GB 64-bit, 4 cores 80 GB for system drive80 GB for second drive and additional drives

2. Active Directory Server in the same Domain where you will be installing SharePoint 2016 Server

3. SQL Server 2014 (SQLServer2014SP2-Full-x64-ENU.iso)

4. SharePoint server 2016 with license (SharePoint_server_2016_x64_dvd_8419458.iso)

Note: Here in this lab I have used SharePoint 2016 180 days trial licenses and into windows servers I have used my MSDN licenses but in your environment you may have different types of licenses so take a brief look at its limitations as well before using them.

Install Windows 10, and Windows Server 2012 R2 update: April 2016.

All the steps are explained in detail with pictures below:

Step 1:

As we are using Windows Server 2012 R2 in our example, let’s update the server with all the latest available updates, the updates can vary depending upon the win2k12 r2 iso file you have.

It’s recommended to install all the latest available updates from Microsoft.


Once the system is updated restart the server.

Step 2:

Install the Active Directory server on Win2k12 R2 server. The step by step procedure to set it up is given here:

AD server is one of the prerequisites which needs to be installed on the same domain where the SharePoint server will be installed.

Once AD is installed properly the System is ready for step 3.

Step 3

In order to install and configure SQL server 2014 you need to install .NET framework 3.5 first, which can be installed as shown below.

* Click on Server Manager–>Manage–>Add Roles and Features–>Select Features tab as shown below.

DOTNET3.5 install * Select .NET Framework 3.5 Features and include the (.NET 2.0 and 3.0) by clicking on the check boxes and click –>Next–>Install

* The installation will take around 1 – 3 minutes.

Step 4

After installing the .NET Framework 3.5, which is a requirement for SQL2014, begin installing the SQL 2014 server on the Win2k12 Server.

  • Mount the SQLServer2014SP2-Full-x64-ENU.iso and click on “Setup” application.

Install SQL2014

  • Now a popup screen appears in which you have to select the option “Installation –>New SQL server stand alone installation or add features to an existing installation”.

Click on New

  • The next popup will ask for entering product key or Evaluation i.e. free period of 180 days, select which ever is suitable for you and click Next.

product key

  • Read and accept the License terms then Click Next.
  • Once you click on Next it will check for the prerequisites of SQL 2014, verify if all the prerequisites are met and continue by clicking Next.
  • Click on Next for all the screens till Feature selection, leaving the settings to default, ignore few warnings.
  • In Feature selection, you need to select “Database Engine Services” and “Management Tools complete” then click Next as shown below.

management tools and database engine

  • The next screen is for the configurations, leave it to default which is the Feature Rules, Click on Next.
  • In the Server Configuration section, provide the Account name as your Windows login name and set to automatic. If the credentials are correct you can go to the next screen, or it will throw an error after clicking on Next.

Server config

  • Once you move on to next screen you need to do the database configurations. We need to specify authentication mode for the Database engine which is Windows authentication mode. Select on “Add current User” to add a user under specify SQL server admin section. Click Next.

DB config

  • We are almost done for the installation, now check the summary in Ready to install Window and Click on Install.
  • The installation of SQL Server 2014 will begin, check the progress which will take 10-15 minutes.

SQL 2014installation

  • Check for the success status after installation and Click on the close button to finish the installation.
  • Now let’s do a few changes to the SQL server instance installed on the server. Go to –>SQL server management studio–>Connect using Windows Authentication, which connects to the SQL Server 2014 installed on the server.

connect to SQL studio

  • Right click on the Server Name –>Properties from the Object Explorer, as shown below.
  • Click on Security–>Logins–>Right Click on the Windows login and select server roles. Assign roles “dbcreator” and “securityadmin” check boxes and click OK.

Set server roles

  • Assign the roles “dbcreator, securityadmin, and sysadmin” for “NT Authority\SYSTEM” i.e system account and the same for SQL server “NT SERVICE\MSSQLSERVER”.
  • This completes the SQL Server 2014 installation.

Step 5

Once the SQL 2104 Server is installed we are ready to start with the SharePoint Server 2014 installation.

There are some prerequisites for the SharePoint 2016 which need to be installed before directly installing SharePoint 2016. Follow the steps below which will make it easy for installing all the required components.

  • First mount the file. (SharePoint_server_2016_x64_dvd.iso)
  • There are different methods to install the prerequisites for SharePoint 2016 which may be running the ready prerequisites installer or the offline method. Normally I would prefer using the offline method because using the ready prerequisites installer will not always work fine and also not reliable. So, let’s follow the Offline method of installing the prerequisites.
  • Before proceeding with the Offline SharePoint 2016 installer, let’s try running the installer that is available with the SharePoint_server_2016_x64_dvd.iso mounted file. The prerequisiteinstaller looks like as shown in the image below.

mounted files sharepointserver2016

  • Run the installer prerequisiteinstaller application which will try to install all of the necessary components required for SharePoint 2016. The prerequisite components include the components below:

• Application Server Role, Web Server (IIS) Role
• Microsoft SQL Server 2012 Native Client
• Microsoft ODBC Driver 11 for SQL Server
• Microsoft Sync Framework Runtime v1.0 SP1 (x64)
• Windows Server AppFabric
• Microsoft Identity Extensions
• Microsoft Information Protection and Control Client 2.1
• Microsoft WCF Data Services 5.6
• Microsoft .NET Framework 4.6
• Cumulative Update Package 7 for Microsoft AppFabric 1.1 for Windows Server (KB3092423)
• Visual C++ Redistributable Package for Visual Studio 2012
• Visual C++ Redistributable Package for Visual Studio 2015

  • Click on Next in the installer and accept the License terms then proceed. Normally this fails to get installed and the error which appears as given below:

prereq error

  • Now, do not worry if this prerequisiteinstaller throws an error. Let’s start with the Offline method for installing SharePoint 2016 prerequisites.
  • There is a slight difference in the prerequisites in SharePoint 2016 when compared to SharePoint 2013.
  • let’s first download all of the prerequisites which are listed above in Step 5 and as shown in the above diagram.
  • First, let’s run the setup file from the mounted location of SharePoint 2016.iso.
  • This step will help us understand the prerequisites required to continue the installation of SharePoint 2016. The image below will give us a clear picture of what prerequisites are still required by the installer.


  • There are 6 components which need to be installed as a prerequisite before triggering the actual SharePoint 2016 installation process. Now, let’s download the required components using a PowerShell script, which will directly download from the Microsoft trusted site.
  • The Script can be downloaded from the link below. Save the file as .ps1 file. (powershell executable file)


Open PowerShell as administrator and run the command as shown in the figure below:

Run the PoweerShell script from the location where the file is saved. Ex: ” Desktop>.\Download-SP2016PreReqFiles.ps1 ”



Note: Before running the script, create a folder inside C:\ or any desired folder where you want to download the prerequisites file, once the download is completed you will see all of the files in the folder you have given. (here C:\Pre is the folder name)

download complete_prereq

The above picture shows successful completion of the prerequisites and all components downloaded into the given folder.

Note: The script does not include 2 components, they are: Microsoft WCF Data Services 5.6 and Cumulative Update Package 7 for Microsoft AppFabric1.1 Windows Server (KB3092423), which can be downloaded from the trusted Microsoft locations and respectively.

  • Download and keep all of the components in a single folder and let’s begin with the installation of the components individually.
  • Except for Windows AppFabric and its patch, all the components can be manually installed by double tapping on those applications. To install Windows AppFabric and patch, we need to run a command which will be covered below.
  • Let’s begin first by installing the MicrosoftIdentityExtensions-64 as shown below.

Microsoft identity applications

  • After Microsoft Identity Extensions installation, install the Microsoft Sync framework Runtime.

Sync framework runtime install

  • Now install the third component i.e MSIPC (Active Directory Rights Management Services)

MSIPC install

  • Reboot the Win2k12 R2 server after all of the components are installed.
  • Let’s install the forth component i.e Windows Server AppFabric using the PowerShell script as given below.
.\WindowsServerAppFabricSetup_x64.exe /i CacheClient","CachingService","CachingAdmin /gac

windowsserverAppfabricAfter installation, restart the Win2k12 R2 server.

  • After restarting the server, install the AppFabric update7 patch by double clicking on the application as shown below. Before installing the AppFabric application –>Right click–>Unblock the file. This is a mandatory step which needs to be done before installing a file which is downloaded from outside.

Appfabric patch update7

  • Now again restart the Win2k12 R2 server.
  • After reboot now install WCF data services by double clicking on the application directly. Before installing the WCF application –>Right click–>Unblock the file. This is a mandatory step which needs to be done before installing a file which is downloaded from outside.

WCF data services

  • After installing the components, restart the Windows2k12 R2 server and again run the Setup to confirm if all the prerequisites are met. If the screen appears as below then all the prerequisites are met.

Valid Produck Key

Note: Most of the prerequisites like sqlncli and .NET framework 4.6 will be installed when Windows update is performed, hence update is a necessary step which takes care of most of the prerequisites.

  • Enter a valid Product key and then accept the license terms. Accept and click on Continue–>Install.
  • Installation of Microsoft SharePoint Server 2016 will take 10 -15 minutes.

SharePoint2016 installation progress

  • After the installation is successful, click on Finish and a configuration wizard appears as below.

Welcome to sp config

  • Read the information and click on Next, then select Create new server farm from the next window, Click Next.
  • Specify the configuration Database settings as shown below by providing the server ip address (Database server), Database name of your choice and then username and password for database login. Then click Next.

Sharepoint config wizard

  • Once the port is configured, specify a server role, here we use Single-Server Farm, then click Next.

Sharepoint config

  • Specify the port for the web application and configure security settings as NTLM or Kerberos for authentication and then Next.

ConfigureSP central admin web app

  • Verify the configuration and click Next.

Completing the Configuration settings

    • Click on Next after verifying and the configuration will begin which will take around 10-15 minutes to finish.


Note: Troubleshooting: If the configuration fails with the following failure message as shown below, then while installing WCF data services and AppFabric you have not unblocked the files. Now unblock both the files and reinstall them. Restart the Win2k12 R2 server and begin the configuration again.

Config failed-troubleshooting

  • Once the configuration is successful, Click on Finish as shown below. After which a window appears in the browser which asks for authentication. Enter the username and password provided as authentication for database and Click OK.


  • After successful authentication, a Welcome screen appears as shown below.

Sharepoint site welcome screen

  • Start the Wizard and select “use existing managed account” and click Next. After clicking on next this will take a while to set it up. (10-15 mins)

Use existing account

  • Finally a Create Site Collection screen appears in which you can create your desired site. Then click OK.

Sitecreation window

  • This step successfully completes the Farm configuration. SharePoint 2016 installation and configuration is completed click Finish.


This is the final step for the SharePoint 2016 server setup. These steps are tested on a virtual machine environment with 100% success rate more than 10 times. So there is a maximum chance for the above provided steps to work on your environment. Also some of the troubleshooting steps are mentioned in the article which will help you to handle the problem.

Feel free to post any comments on this or if you get stuck between any steps.

You can take the following MVA courses if you are stocked at any time.

Reference links:

For High Availability you may consider looking at the below picture for system reference

This poster describes the SharePoint Online, Microsoft Azure, and SharePoint on-premises configurations that business decision makers and solutions architects need to know about.

Item Description
SharePoint Online, Azure, and SharePoint on-prem configurations

PDF file PDF  |  Visio file Visio

This poster describes four architectural models:

  • SharePoint Online (SaaS) – Consume SharePoint through a Software as a Service (SaaS) subscription model.
  • SharePoint Hybrid – Move your SharePoint sites and apps to the cloud at your own pace.
  • SharePoint in Azure (IaaS) – You extend your on-premises environment into Microsoft Azure and deploy SharePoint 2016 Servers there. (This is recommended for High Availability/Disaster Recovery and dev/test environments.)
  • SharePoint On-premises – You plan, deploy, maintain and customize your SharePoint environment in a datacenter that you maintain.

This poster shows the recommended MinRole topologies in a SharePoint on-premises environment.

Item Description
Click to view and download this poster about SharePoint Server MinRole topologies.

PDF file PDF  |  Visio file Visio

This poster shows the different recommended MinRole topologies that can be deployed in a SharePoint Server 2016 environment. It also shows the associated services that are provisioned with each role type.

This poster shows the databases that support SharePoint Server 2016.

Item Description
This is a thumbnail fo the SharePoint Server 2016 databases poster.

PDF file PDF  |  Visio file Visio

This poster is a quick reference guide to the databases that support SharePoint Server 2016. Each database has the following details:

  • Size
  • Scaling guidance
  • I/O patterns
  • Requirements

The first page contains the SharePoint system databases and the service applications that have multiple databases.

The second page shows all of the service applications that have single databases.

For more information about the SharePoint Server 2016 databases, see Database types and descriptions in SharePoint Server 2016

These posters describe search architectures in SharePoint Server 2016.

Item Description
Search Architectures for SharePoint Server 2016

Poster with an overview of the search components and search databases, how they interact, and an example of a search architecture built of these components and databases.

PDF file PDF  |  Visio file Visio

This poster gives an overview of the search architecture in SharePoint Server 2016. It describes the search components and databases in the search architecture and how these interact. It also shows an example of a medium-sized search farm.
Enterprise Search Architectures for SharePoint Server 2016

Poster describing the search components and databases, three model architectures for enterprise search, hardware requirements and scaling considerations.

PDF file PDF  |  Visio file Visio

This poster gives an overview of enterprise search architecture in SharePoint Server 2016. It shows sample search architectures for small, medium, and large-sized enterprise search farms. It also gives scaling considerations and hardware requirements.
Internet Sites Search Architectures for SharePoint Server 2016

Poster describing the search components and databases, a model architecture for Internet sites search, hardware requirements, scaling considerations, and performance considerations.

PDF file PDF  |  Visio file Visio

This poster gives an overview of the search architecture for Internet sites in SharePoint Server 2016. It shows a sample search architecture for a medium-sized search farm. It also gives performance considerations and hardware requirements.

Install Windows 10 IoT Core for the Raspberry Pi

Disclaimer: This is not my original work, just a collective effort for all IoT learners support. The credit for the original writer has been included at the end of the post.

In this tutorial, I will be going through the process of installing and setting up Windows 10 IoT Core for the Raspberry Pi.

For those who don’t know Windows 10 IoT Core is a version of the Windows 10 operating system built just for IoT devices such as the Raspberry Pi. This is very useful if you plan on utilizing something like UWP to write your application, it also gives you access to Windows 10’s core, and its wide variety of features.

I very briefly go into coding and pushing applications to the device. If you need to learn more about how to do things, then I highly recommend looking at some of Microsoft’s documentation as it is very thorough.

Please note to complete this tutorial you will need either a Raspberry Pi 2 or a Raspberry Pi 3. This is unsupported on other versions of the Raspberry Pi.

Take a look at this Video Tutorial.


To be able to install Windows 10 IoT on the Raspberry Pi correctly you will need the following pieces of equipment.


Raspberry Pi 2 or 3

Micro SD Card

Ethernet Cord


Raspberry Pi Case

USB Keyboard

USB Mouse
You will also need a computer running Windows 10 to be able to complete the following process.

Installing Windows 10 IoT on your Raspberry Pi

1. To begin, we will first need to download and install the Windows 10 IoT Core Dashboard. To download this, we just need to go to the Windows 10 IoT website here.
This piece of software is what will download the correct system for our Raspberry Pi and format it.

2. Insert your SD card into the computer or laptop’s SD card reader and check the drive letter allocated to it, e.g. G:/. You will need to know this to ensure that you are formatting the correct drive, as you don’t want to be doing this to any important data.

3. Now that you have inserted your SD Card into your computer/laptop, we will need to run the “Windows 10 IoT Core Dashboard” software. If you can’t find this easily after installing it then try running a search.

With the software loaded up we need to go into the “Set up a new device” (1.) screen as shown below.

On here you will want to set your “Device name” and set the “New Administration password“. Make sure that you set the password to something you can remember easily, but is secure, as this password is what you will use to remotely connect to your Raspberry Pi (2.).

Before we continue, make sure that “Drive” is set to the correct drive, make sure that the drive letter is the same as the SD Card that your inserted in step 2.

When you have filled in your information tick the “I accept the software licence terms” and then press the “Download and install” button (3.).

Windows 10 IoT Dashboard Setup a new device

4. Once the software has finished downloading and installing Windows 10 IoT Core for the Raspberry Pi we can proceed on with this tutorial. Now safely to out your Micro SD card from your computer so you can put it into your Raspberry Pi.

Booting and setting up your Win 10 IoT device

1. Now that we have successfully downloaded and written the image to our Raspberry Pi’s Micro SD card we can insert the SD Card back into the Raspberry Pi.

2. Before we power back on the device, make sure that you plug in a HDMI cable and a mouse and keyboard, we will need all 3 of these if you intend on utilizing Wi-Fi on your Raspberry Pi Windows 10 IoT device.

Once done you can plug your Raspberry Pi back into power and allow it to start booting up.

3. Now is the long wait for your Raspberry Pi to start up, when I did this it took a fair while for the Raspberry Pi to start up on boot, don’t be afraid if you think it may have frozen it just takes some serious time to do the initial setup and startup.

4. Once it has finished starting up, you should be greeted with a screen like below. Now to setup a WiFi connection, we need to click the cog in the top right-hand corner.

Windows 10 IoT on the Raspberry Pi

5. Now in the next menu we need to go to “WiFi and Network” and select the WiFi access point you want to connect to, you will receive a prompt asking you to enter your network password.

Once you have connected to your WiFi network you can return to the main screen to grab your Raspberry Pi’s IP Address, as we will need this further along in the tutorial.

Raspberry Pi Windows 10 IoT Set WiFi

Connecting to Your Device

Now there are 3 ways you’re able to connect to your Raspberry Pi Windows 10 IoT device. I will quickly mention each method now.

Web Browser

First off is utilizing your web browser to talk with the Raspberry Pi, it is probably the easiest out of the 3 main ways to deal with. Basically, all you simply need to do is point your Web Browser to your Raspberry Pi’s IP Address on port 8080.

For example, my Raspberry Pi’s local IP address is, so in my favorite web browser i would type in

You can also use the “Windows 10 IoT Core Dashboard” tool to be able to click to get to the devices web page as well. Simply load up the application, go to the “My Devices” (1.) tab in the left sidebar, right click (2.) on the device you want to connect to and click “Open in Device Portal” (3.).

Windows 10 IoT My Devices Screen

Upon either going to your Raspberry Pi’s IP Address or using the Windows 10 IoT Core Dashboard tool you will be first asked to login. Make sure you use administrator as the username, and the password you set at the beginning of this tutorial as the password.

Upon successfully logging in you should be greeted with the screen below. We recommend exploring around as the web tool does offer a fair bit of access and incite to your device. You can debug and see real time performance through this interface which is incredibly helpful to see what you Raspberry Pi is doing.

Raspberry Pi Windows 10 IoT Website


PowerShell is not a tool that many will be too familiar with, but it is Microsoft’s more advanced version of command prompt giving you access to a wealth of tools including the ability to administer remote systems, a feature we will be making use of shortly.

PowerShell makes it rather simple to interact with your Raspberry Pi Windows 10 IoT device as we will show shortly. There is two ways of connecting to your device through PowerShell. The easier way relies on the “Windows 10 IoT Core Dashboard” tool (Steps 1a+), the other way is utilizing PowerShell to do everything (Steps 1b+).

1a. First off, we will explain the simple way, first load up the “Windows 10 IoT Core Dashboard” tool. With the application open, go to the “My Devices” (1.) tab in the sidebar, right click (2.) on the device you want to connect to and click “Launch PowerShell” (3.).

Raspberry Pi Windows 10 IoT Dashboard Launch Powershell

2a. This will launch a PowerShell session that will automatically begin to connect to your Raspberry Pi. When prompted enter the password we set at the start of this tutorial. You should be greeted with a PowerShell window like shown below when you have been successfully connected.

1b. The second way of connecting to your Raspberry Pi is slightly more complicated and utilizes PowerShell completely. To open PowerShell on Windows 10, right click the windows Icon and select “Windows Powershell (Admin)“.

2b. In here we want to type in the following command, this adds our Raspberry Pi as a trusted device for PowerShell to connect to. Make sure you replace [YOUR _PI_IP_ADDRESS] with your Raspberry Pi’s local IP address.

Set-Item WSMan:\localhost\Client\TrustedHosts -Value [YOUR _PI_IP_ADDRESS]

3b. With that done, we can now start a PowerShell session with our Raspberry Pi Windows 10 IoT device. To do this enter the command below into PowerShell, making sure you replace [YOUR _PI_IP_ADDRESS] with your Raspberry Pi’s local IP address.

Enter-PSSession -ComputerName [YOUR _PI_IP_ADDRESS] -Credential [YOUR _PI_IP_ADDRESS]\Administrator

4b. You will be asked to enter the password you set earlier in this tutorial. Enter that to continue.

5b. After about 30 seconds, PowerShell should have now successfully made the connection and you should see a screen like below.

Raspberry Pi Windows 10 IoT Core Powershell connection


The third main way of interacting with your Raspberry Pi Windows 10 IoT device is to utilize SSH. The main advantage of this is that it is a widely available protocol and is something most users of the Raspberry Pi will be thoroughly familiar with.

You can also follow the SSH instructions below in order to use SSH to connect to your device.

1. To start off make sure you have a SSH client installed, on Windows I highly recommend using either Putty or MobaXterm.

2. Now in your SSH Client connect to your Raspberry Pi’s IP Address on port 22 (The default SSH port).

3. When asked to enter the username you want to login with, make sure you use administrator, as this is the default login username for Windows 10 IoT Core.

4. You will now be asked to enter the password associated with the account, the password you want to use is the one you would of set within the Windows 10 IoT Core Dashboard at the start of this tutorial.

5. You should now be successfully logged into your Raspberry Pi Windows 10 IoT Core device and should be greeted with a screen like what is shown below.

Raspberry Pi Windows 10 IoT SSH

If you want to learn more about utilizing SSH and some of the commands you can use within the session then make sure you take a look at Micrsoft’s own IoT documentation here.

Setting up Visual Studio for Windows 10 IOT Core

Lastly you are most likely going to want to setup Visual Studio Community. The reason for this is so that you are able to start developing your own applications for Windows 10 IoT Core.


1. First, we must download and install Visual Studio Community, luckily this is easily available on Microsoft’s website, you can find Visual Studio Community by going to the visual studio community.

Be warned that the download and installation of Visual Studio Community can take some time especially on slow internet connections.

2. Once the installation process has completed you can continue this with tutorial. Start by launching up Visual Studio Community. It will ask you to do some configuration, it should be fine to just use the default settings.

3. You will notice that there isn’t any IoT templates in the default installation. Click on the here link next to install Windows 10 IOT core project templates back on the page linked back.

4. Now one of the things you will find that is currently missing is any project templates for Windows 10 IoT Core. We can grab and install these by going to the Visual Studio marketplace.

5. Once you have downloaded and installed the templates, close and re-open Visual Studio, you need to do this for Visual Studio to load them in.

6. Upon creating the new project, you will be prompted to activate developer mode on your Windows 10 device. Simply follow the prompts provided to activate it.

7. Everything should now be ready for you to code your new application. You can find documentation on certain features of Windows 10 IoT Core by going to their documentation page. You can also find a document that explains how to utilize the GPIO pins from within Windows 10 IoT by going to their GPIO documentation.

Pushing code to the device

1. Once you have your new application in a state in which you want to deploy it to your Raspberry Pi Windows 10 IoT device, go up to the tab that has a green arrow in it.

2. Click the black drop down arrow, and select remote machine.

3. Now in here you should be able to select your Raspberry Pi underneath automatic configuration, however in some cases this will not function correctly and you will have to manually enter the IP of your Raspberry Pi.

4. You should now be able to push code / applications to your Windows 10 IoT Raspberry Pi.

I hope you now have learn how to install Windows 10 IoT core for the Raspberry Pi. If I have missed anything, or if you are having troubles or anything else you would like to share then be sure to drop a comment below.

All credit goes to PyMyLifeUp

Windows 10 IoTCore


This project’s goal is to demonstrate guidelines for creating a Windows 10 IoTCore based product and walk through the creation of an IoT device, from implementation to final deployment.

The project has two applications:

  • One background application to receive sensor data and send it to the Azure cloud. Receiving sensor data and analyzing it are important tasks in IoT and a device will often operate in “headless” mode for monitoring; thus, we separate these tasks in an independent app. It also receives application keys securely and saves user settings to Azure.
  • One foreground application for user interaction. This application shows local weather (read by the background app), information from the internet (news and regional weather) and interacts with the user (playing media or showing a slideshow). A settings page is also available to change settings.

App communication

The applications are written using Universal Windows Platform (UWP); thus, the same foreground app can be run on both IoT and Desktop.


Steps from implementation of apps to deployment are documented with an end-to-end solution. Each tutorial shows small code snippets and then links to the code running in the walkthrough project.


  1. About the project
  2. Background application
  3. Foreground application
  4. Inter-application communication
  5. Connecting to the Azure cloud
  6. Integration with third-party services
  7. Preparing for deployment
  8. Deployment
    • Creating a retail OEM image

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.