Windows-10

In our final part, we want to create the offline media to use to reimage our physical machines.

In the last SCCM Test Lab post, we looked at part 4, where we had done the basic setup, and were looking to go further into part 5.

Things have moved on since then. Microsoft has now officially released Windows Server 2016 and SCCM 2016. Windows 10 1607 was also released, with some interesting aspects about App-V and UE-V.

My focus for the last 2 months had been to plan for how we could in our organization have coexisting operating systems (Windows 7 and Windows 10) when the App-V solution was different for Windows 10 1607.

In this post I’ll be sharing some of the things I have discovered, and how you can try to make sense of all the confusion which might be out there.

This post picks up after part 1 and part 2. I suggest you read both parts first to understand what is happening here in part 3.

Anyway, this has been long overdue :-)

In this part, we will be looking at setting up some initial group policies, setting up firewall rules, installing SCCM prerequisites, and finally installing SCCM.

Well, lets get started then

If you have not read part 1 yet, I suggest you read that post first.

In part 1, we set up a basic server and nothing else. It is time to add more bits to our server and create our test lab domain. When we ended part 1, we shut down our server. Time to boot it up, and login as the local administrator.

Introduction

This post is meant to guide you through setting up a simple, DIY, for your own use, test environment. This lab will be a simple Windows domain with SCCM and 1 client machine.

Everything will be setup using virtual machines on 1 single host. The example below assumes this will be done on your own workstation, but that does not have to be the case, and you can set this up remotely somewhere else as well.