Video: Spludlow Framework - Windows 10 Prerequisites
Video: Spludlow Framework - Windows Server 2016 Prerequisites
Video: Update .net Version
Contents
Introduction. 1
Other Software Dependencies. 1
Enabling Windows Features. 1
Enabling Windows Features (Windows
10). 1
Enabling Windows Server Features and
Roles. 1
Configure IIS – Enable HTTPS. 1
Create SSL Certificate for HTTPS. 1
Enable HTTPS Binding. 1
IIS Basic .net Test. 1
Ensure running the correct version of
.net. 1
Database Availability (First Host
Only). 1
MSMQ Familiarity Check. 1
You should be logged into Windows using an account that
belongs to the local group Administrators. If you want to use setup for
creating users in active directory (windows domain), you need to be a member of
Domain Admins.
The following software needs to be installed:
·
7-Zip
Now it’s time to enable all the OS Features the framework
requires:
·
IIS
·
.net WCF HTTP Activation
·
.net ASP.NET
·
MSMQ
Control Panel -> Programs and Features -> Turn Windows
Features on or off -> Tick the following 3 items in this order:
- Tick “Internet Information Services” top level.
- Open up “.net Framework 4.6 Advanced Services”,
open up “WCF Services”, tick “HTTP Activation”.
- Tick “Microsoft Message Queue (MSMQ) Server” top
level. Nothing below it is required.
If you got this right your settings should match those in
the screen shot, if it looks wrong hit cancel and try it again. Note that step
2 “HTTP Activation” automatically ticks everything else required to make .net
work with IIS.
You may want to enable some other authentication methods if
you use them, for example; IIS->Security->Windows Authentication if you want
a company Intranet.
Forms authentication is a feature of ASP.NET not IIS so you
don’t need to enable it here.
Install Server pretty much the same way as Windows 10,
described above. Make sure you choose “Desktop Experience” if you want to use a
desktop with Windows.
The main difference between setting up Windows and Windows
Server is the way you switch built in operating system features on and off, for
example the web server, things that are supplied with the operating system but
you have to enable them. On Windows you click “Windows Features” within Control
Panel -> Programs and Features, you get a tree with everything available in
it and you can tick away. On Windows Server they have top level “Roles” like
web server or domain controller and then “Features” are the level below
options, for example enable .net within the web server. Anyway don’t get too
annoyed with it they are both doing the same thing just organized differently.
Within Server manager under “(2) “Add roles and features”
start the Roles and features wizard. Perform the following steps:
- Roles: “Tick Web Server (IIS)” only then click
next.
- Features: open up “.net Framework 4.6 Advanced
Services”, open up “WCF Services”, tick “HTTP Activation”. This will tick
all the other .net stuff you need.
- Features: click “Message Queuing” only “Message
Queueing Server” is required. Click next.
- Get to features for the Role IIS review
everything should all be set from previous step. Add and additional
security types.
IIS is configured using IIS Manager; go to Control Panel\All
Control Panel Items\Administrative Tools\Internet Information Services (IIS)
Manager. If IIS manager is not there, then the Windows Feature “IIS Management
Console” is not selected. Pin it to your taskbar you will be using it.
Within IIS Manager select the local server at the top level
in the left hand navigation panel.
The icons displayed on the main panel should contain “Server
Certificates” under the IIS section, double click it. You should be looking at
an empty list of server certificates.
Click the link on the right “Create Self-Signed
Certificate…” a wizard appears. Name it “SpludlowCert” with a type of
“Personal” and click OK.
You have now created a SSL certificate that IIS can use for
HTTPS.
Within IIS Manager expand the “Sites” in the left hand panel
and select “Default Web Site”.
Click the link top right “Bindings…” a list of current
bindings is shown containing the default 80.
Click “Add…” change type to HTTPS change the SSL certificate
“SpludlowCert” created previously, you can leave everything else blank.
After clicking OK, the binding 443 should appear below the
standard port 80 binding.
This is a quick and easy way check that IIS is probably
working correctly and integrating with .net.
Try browsing to the following locations (note that “fred” in
these tests is not supposed to exist):
http://localhost/ You
should see the default IIS page, currently it’s blue with hello in different
languages.
http://localhost/fred.aspx If
you don’t get “Server Error in '/' Application.” in red then ASP.NET is not
configured correctly.
http://localhost/fred.svc If
you don’t get “Server Error in '/' Application.” in red then HTTP activation is
not configured correctly
If any of these tests fail, then IIS is not configured
correctly something must have been missed when turning on Windows Features.
The test basically checks that the extension mapping for
“.aspx” and “.svc” within IIS. Make sure you interpret the error page correctly
as in this screen shot:
The version of .net running on the host must be at least
that of what the binaries where compiled for.
“ASoft .NET Version Detector”
http://www.asoft.be/prod_netver.html
The first host (Master) must have access to a database,
either local or remote. If you don’t please look at “Installing a database”.
The installer will require an initial connection string to
setup the database. This connection’s database account should have the server
role “SysAdmin” (on MS SQL) during setup so it can create the database. If you
are running setup with the same account you installed the database, then this
should already be the case.
If the database is SQL Server and runs local with integrated
security used, then the default connection strings will work.
Go to Control Panel\All Control Panel Items\Administrative
Tools\Computer Management pin this to your taskbar.
Within Computer Management under “Services and Applications”
you have “Message Queuing”, you will be using private queues, here you can
manually add, remove, and configure permissions on queues as well as managing
the messages on the queues.
If “Message Queuing” is not present, then it isn’t selected
in Windows Features.