Windows Server 2012 (6)
There is no default group policy support for Microsoft Edge browser in active directory domain Windows Server 2016. In this article, I’ll show you to install an administrative template on active directory domain Windows Server 2016 for group policies of Microsoft Edge.
Installing Administrative Template on Windows Server 2016
Download the latest administrative template (.admx) for Windows Server 2016 on your hard drive
Double-click the ‘Windows 10 and Windows Server 2016 ADMX.msi’ file where you downloaded
During security warning, click Run
On Welcome screen, click Next
Read the license terms, click I agree and then click Next
Choose for Everyone and note down the installation folder path. Click Next
During installation confirmation, click Next
Wait for the installation to finish
Click Close when an installation completes
Copying Policy Definitions to SYSVOL Folder
Copy PolicyDefinitions folder from a path where you installed administrative template
Paste the folder in %systemroot%\SYSVOL\sysvol\\Policies
Open group policy editor and you will notice the 20 policies of Microsoft Edge in Computer Configuration -> Policies -> Administrative Templates -> Windows Components -> Microsoft Edge and User Configuration -> Policies -> Administrative Templates -> Windows Components -> Microsoft Edge
Now Microsoft Edge policies have been configured in active directory domain, you can apply on AD users and computers. For Firefox and Chrome, there are administrative template files available you can use to configure their group policies support.
In previous article, we have configured a Windows Server 2016 Nano. In this post, we will extend the same topic and I’ll show you to join the nano server with an existing domain.
Joining a Nano Server with Domain
1. Run the following command on any domain controller. This will create a computer account (in an active directory) and the file you specify in the command. That file contains domain information.
Djoin.exe /provision /domain /machine /savefile .\
Open Active Directory Users and Computers console. Expand domain name, click Computers and verify the existence of computer account you just created in above step.
Go to the drive where your operating system is installed (which is normally used to be C drive). Double-click Users and then your user name. Verify the existence of file you just created.
2. Copy/paste the file (you created in above step) to C drive of nano server with the help of file explorer (type \\\c$ as shown in the following figure).
3. Execute the following command to add an IP address of nano server to the list of trusted hosts.
4. Execute the following command to create a PowerShell session with nano server.
Enter-PSSession -ComputerName -Credential \Administrator
5. Execute the following command to join the nano server with domain.
Djoin.exe /requestodj /loadfile c:\ /windowspath c:\windows /localos
6. You are done. Reboot the nano server so that changes can take effect.
Once you login, you will notice the domain name on nano server recovery console.
Q. I'm trying to perform an in-place upgrade from 2012 R2 to 2016 but it will not let me select the option to keep apps and data, why?
A. The best practice for servers is to not perform an in-place upgrade but rather perform a fresh install of the OS and migrate workloads over however if you need to perform an in-place upgrade for some roles and applications this is supported. If when performing an in-place upgrade the option to keep applications and settings is not available it is likely you entered a product key for a lower SKU than currently used, for example if you have Datacenter 2012 R2 and enter a Standard 2016 key then the option to keep applications and data will not be available. You also cannot perform an in-place upgrade if you are changing the installation mode, e.g. moving from Server Core to Server with Desktop Experience.
These days I do not need a full FTP client as much as I used to several years ago. Part of this is just because we now tend to access everything over the Internet through websites instead of downloads from FTP servers.
Remember getting some big updates from a company by downloading from their FTP server?
Anyway, while there are plenty of fully equipped FTP clients out there to download, sometimes we just need a quick connection to grab some files - in my case for my website maintenance - and need something straight forward and simple.
Well did you know that there is an FTP client built right into the Windows File Explorer?
It has actually been there through the last few versions of Windows and is very easy to setup and use for these infrequent FTP sessions.
The service is very robust and gives you the ability to easily work with files over FTP and perform functions such as uploads, downloads, deletes, renames, change file permissions (CHMOD), and even pin folders and entire sites in your File Explorer UI.
Today I want to show you this process in Windows 10 but you will find the sequence very similar in Windows 7 and 8.1.
(1) Click in the File Explorer Address Bar to highlight the field.
(2) Type in the ftp address you want to access. Note: The ftp:// element is not required at this stage but can be used.
(3) Type in your FTP username
(4) Type in your FTP password
(5) Select this check box if you are accessing this FTP server anonymously
(6) Select this check box to save your password in the Windows Credential Manager
(7) Click Log On to access the FTP server
The FTP site will open up in second instance of File Explorer and now you can access the site.
(8) You can pin a folder to the Quick Access area of File Explorer at anytime for the selected folder.
(9) By right clicking on a file or folder that is on the FTP server you can adjust the Read, Write, Execute permissions for the content. This is commonly referred to as CHMOD.
(1) If you right click on This PC you can select Map network drive to add an FTP site to this tab of File Explorer.
(11) Select the link at the bottom of this dialog to get started.
(12) Click Next to continue.
(13) After selecting the single option on this dialog, click Next to continue.
(14) Type in the FTP site address here. Note: The ftp:// element is required in this step.
(15) Select this check box for anonymous access to the FTP server.
(16) Type in your user name. Note: If you have previously accessed this FTP site in File Explorer as I showed earlier and you opted to have your password saved then you will not be prompted for the password when you access this new resource since it is already stored.
(17) You can use the full server name as shown by default or choose your own unique name for this mapped resource.
(18) If you want to immediately access this FTP server then leave this check box selected, otherwise uncheck that box.
(19) Click Finish to wrap up this process.
(20) Your newly mapped FTP server is now available when you open File Explorer and access the This PC tab.
Enjoy your quick and easy FTP access right from within File Explorer.
Q. Can I in-place upgrade to RS3?
A. An in-place upgrade from Windows Server 2016 to RS3 is not officially supported however in my limited tests it did work for a few lab instances. Note that this is only for Server Core to Server Core. This is because:
- There is no upgrade for Nano (ever, you just redeploy the container built on the new image)
- There is no RS3 of Server with Desktop Experience as Server with Desktop Experience is Long Term Servicing Channel only.
Q. I previously ran the VMM SDN Express to install the Network Controller, how can I now add the SLB MUX/Gateway?
A. The VMM SDN Express enables a single configuration file to be used to document all the desired configuration which is then used by an automated process to configure SCVMM and create the required VMs to host the various required roles such as the Network Controller, SLB MUX, Gateway. If during the initial deployment you only install the Network Controller (by setting the deployment to $false) for the other components then to add them at a later time is simply a matter of editing the file again, set the Network Controller deployment to $false (since it's already deployed) and the desired components to $true and then rerun. The process will now add the required components without reinstalling the Network Controller.