You can’t install Windows on a USB flash drive using Setup

Q: “You can’t install Windows on a USB flash drive using Setup.”

When trying to install Windows 10 from Windows Update the install fails and I get a screen that tells me:

“You can’t install Windows on a USB flash drive using Setup.”

I’m not trying to install it on a USB and i’m just trying to install it onto my computer which runs Windows 8.1 currently.

A:

Had the same problem and found this from google.

The second method is what fixed it for me.

2] The other fix few users reported as being helpful, was to change a registry value. Please be careful while working in the registry. Make sure you create a backup of Registry before you proceed.

  • From the Desktop screen press Win + R
  • Type in Regedit
  • Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  • Change the value PortableOperatingSystem to “0” from 1.

Once you change the registry value please reboot the system and try to update again from Windows Store.

Original article:

https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/you-cant-install-windows-on-a-usb-flash-drive/003a982e-aa32-49ad-8bf5-e7e83d488c63?auth=1

Installing Exchange Server 2016 on Windows Server 2016

On October 1st, Microsoft Exchange Team released the new Exchange Server 2016. Microsoft has been testing and improving on millions of mailboxes in their Office365 environment before releasing the product on-premises. I will describe in this article a step-by-step guide for the installation of Microsoft Exchange Server 2016. The installation considers:

  • a single server deployment of Exchange Server 2016 with the Mailbox role on a new Windows Server 2016
  • Windows Server 2016 forest functional level
  • Exchange Server 2016 with the latest Cumulative Update 4

Because Windows PowerShell is a powerful tool that every sysadmin would know, I will use PowerShell to perform the installation. But If you prefer the graphical interface, you can use it!

Step 1: Requirements

Before installing Exchange Server 2016, you must review the following requirements:

Forest Functional Level for Exchange 2016
  • Windows Server 2008 or higher
Minimum Operation System
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
Minimum Memory Requirement (RAM)
  • Mailbox Server 8GB minimum
  • Edge Transport Server 4GB minimum

To check your Active Directory Forest Functional Level, you can run the “Get-ADForest” cmdlet:

PowerShell script

Important:

  1. Note that Microsoft doesn’t support the installation of Exchange 2016 on a computer that’s running Windows Server Core or Nano Server. The Windows Server Desktop Experience feature needs to be installed.
  2. Client Access Role is removed in Exchange Server 2016 which simplify the Exchange architecture.

If you need further information about what you need to have in your environment before installing Exchange 2016, please visit the following link: https://technet.microsoft.com/en-US/library/aa996719(v=exchg.160).aspx

Step 2: Installing Pre-Requisites

Open Windows PowerShell as Administrator, and run the sconfig utility to install the latest Windows Updates. Exchange Server 2016 requires the update described in Microsoft Knowledge Base article KB3206632. Without this update, Exchange Server 2016 will not work reliably on Windows Server 2016. Choose the number 6 to download and install Updates:

Open Windows PowerShell as Administrator

Next, run the following command to install the Remote Tools Administration Pack:

PowerShell script

Now, we will install the required roles. The prerequisites for Exchange Server 2016 varies if you run a Windows Server 2012 or 2016. So be careful, and use the following for Windows Server 2016:

Windows indicates that no reboot is required but I advise you to restart the server.

PowerShell script

The .Net Framework 4.5 and higher is required, so to check .Net version on Windows Server 2016:

If it’s above “394747” then it means that you have .NET Framework 4.6.2 or later installed.

PowerShell script

To finish with pre-requisites, you must download and install Unified Communications Managed API 4.0 Runtime: http://www.microsoft.com/en-us/download/details.aspx?id=34992

Unified Communications Managed API 4.0 Runtime

Click next and finish to install Microsoft UCMA component:

Unified Communications Managed API 4.0 Runtime

Step 3: Preparing Schema and Active Directory

After you’ve prepared a Windows Server with the Exchange Server 2016 pre-requisites you can proceed with the schema update. To apply only the schema update:

First, mount the Exchange Server 2016 installation media, open a PowerShell console and navigate to the setup files. Then type the following command:

Windows PowerShell

Extending schema status must be “Completed”. After applying the schema update we can prepare our Active Directory with the PrepareAD parameter:

Windows PowerShell

The final step to get Active Directory ready for Exchange is to prepare each of the Active Directory domains where Exchange will be installed.

Windows PowerShell

If you have more than one domain, you can replace the PrepareDomain parameter with PrepareAllDomains parameter.

Step 4: Installing the Mailbox Server Role

The Mailbox server role contains all of the components required to run an Exchange Server 2016 server. If you need an Edge Server, you can still install it in Exchange 2016 but that is not a mandatory role. At this step, it’s up to you. To install the Mailbox Role, there are two ways you can do this:

  • Using the graphical interface. Run the exe, choose Next, Accept the agreement, select the Mailbox Role, specify the path for the Exchange Server installation and choose Install.
  • Or you can try to install Exchange with Windows PowerShell.

Below are the available parameters to customize your installation:

In my opinion, it’s never a good idea to install the Exchange Database and the log folder on the root partition.

The setup process will collect some information needed for installation, check the prerequisites and configure your Exchange Server. Just wait …

Windows PowerShell

When it’s done, open Internet Explorer and go to https://<FQDN of Mailbox Server>/owa to validate your Exchange installation.

Exchange installation validation

You have successfully installed your Exchange Server 2016 on Windows Server 2016. The idea of this article was to illustrate how PowerShell can allow us to simplify and automate our daily tasks.

Thanks for reading!

 

Original article:

Installing Exchange Server 2016 on Windows Server 2016

Windows 10 1803 downloaden voor 30 april

Je kunt nu al updaten naar deze versie, met de Media Creation tool via de volgende stappen:

1) download de Media Creation tool:
https://download.microsof…0B1/MediaCreationTool.exe

2) download deze CAB file: https://drive.google.com/…5Q3HaYPaF682SKuWwSHe/view

3) sla de .exe en de .cab in dezelfde folder op.

4) Start de Media Creation tool via de commandline met: MediaCreationTool.exe /selfhost

5) upgrade direct, of bouw eerst een ISO (up to you). En je zit op 17134. :)

 

Original article:

https://tweakers.net/nieuws/137967/windows-10-april-update-verschijnt-maandag-30-april.html

How to Configure NTP Server on Windows Server 2016

 

In this article, I will show you how to configure NTP Server on Windows Server 2016 in just a few steps.

We will use PowerShell to change the NTP Server and we will validate if it worked afterward.

 

Type the following commands

  • w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:MANUAL
  • Stop-Service w32time
  • Start-Service w32time

Of course, you can take any NTP Server that you want.

Now verify if the time-server was set correctly on your Server 2016 by typing:

  • w32tm /query /status

You should get a reply like this:

Now we will go ahead and verify if our clients sync properly.

 

Verifying if the Time Server was correctly set on our Clients

On a client computer open a PowerShell with right-click and Run as Administrator….

Type:

  • w32tm /query /status

Check the time-server and type:

  • w32tm /resync
  • w32tm /query /status

Then you are able to see that the time-server actually changed like in the example below.

And that’s it! Easy, right?

Always make sure that you use the same time-server in your network and that all your clients are syncing with it. If you have time differences inside of your Active Directory Domain you will run into major issues.

 

Original article:

How to Configure NTP Server on Windows Server 2016