Installation Manual Windows Storage Server 2018
The Service Management Portal and API consist of the following components:. Service Management Admin Site: - where administrators can create Web Sites clouds, Virtual Machine clouds, author plans and manage user subscriptions.
Service Management Tenant Site - where users can sign up and create web sites, virtual machines and databases. Service Management API - the API layer exposes the functionality to manage services such as web sites, virtual machines and application databases to the Admin and Tenant Sites via a unified interface. The Service Management API is comprised of 3 distinct interfaces:. Service Management Admin API – exposes functionality for completing administrative tasks from the Service Management Admin Site or through the use of PowerShell cmdlets. Note It is recommended that the Tenant API be installed on a machine or machines that are behind a firewall or otherwise inaccessible from the Internet because it provides the ability to perform critical operations like Create/Delete subscriptions and manipulation of resources across subscriptions. Service Management Tenant Public API – enables end users to manage and configure cloud services included with the Plan or Plans they subscribe to.
The Tenant Public API is designed to serve all of the needs of end users subscribing to the various services provided by a Hosting Service Provider. Web Sites Controller - enhanced version of Web Farm Framework (WFF) that provisions and manages Web Sites Roles.
Web Sites REST API - Web Sites Management API exposed via REST endpoint. Web Workers - Web Sites-specific version of IIS web server which processes client web requests. Web workers may be ‘Shared’ or ‘Reserved’. Front End - Web Sites-specific version of Application Request Routing (ARR) which accepts web requests from clients, routes requests to Web Workers and returns web worker responses to clients. Publisher - Web Sites-specific version of WebDeploy and FTP which provides transparent content publishing for WebMatrix, Visual Studio and FTP clients. File Server - Provides files services for hosting web site content.
The Service Management Portal and API and the Web Sites components are intended to run on a minimum of 7 machines (these machines may be virtual). In addition to these machines, it is expected that there will be one or more servers in the datacenter running Microsoft SQL Server and MySQL Server. The SQL Server, MySQL Server, and File Server can coexist with each other, and the Hyper-V host machine, but should not be installed in the same VMs as other Web Sites roles. Use separate SQL Server computers, or separate SQL instances, on the same SQL Server computer to isolate the Web Sites configuration databases from user/web sites databases. Naming Convention.
We recommend using descriptive computer names for each machine such as:. SvcMgmtPortal - for Express installation. SvcMgmtAdmin, SvcMgmtTenant, SvcMgtAdminAPI, SvcMgtTenantAPI, SvcMgtTenPubAPI - for distributed installation. SitesController – Web Sites Cloud Controller. SitesRESTAPI – Web Sites Cloud REST API layer.
SitesFE – Web Sites Cloud Front End. SitesPublisher – Web Sites Cloud Publisher. SitesWWS – Web Sites Cloud Shared Web Worker. SitesWWR – Web Sites Cloud Reserved Web Worker. FileServer – Web Sites Cloud File Server Memory. Configure intranet and internet access for machines running Web Sites roles as described below. Inbound access from the Internet - The following roles should be accessible from the Internet:.
Front End – to accept client requests for websites. Publisher – to accept requests from publishing tools like WebMatrix and FTP clients. Other Web sites roles do not require inbound internet access, as they do not directly service end user requests. Outbound access to the Internet - It is important that all Web Sites VMs, including Web Workers, have outbound HTTP web access to download software dependencies when installing the roles. Web Sites requires that the servers have transparent outbound Internet access.
Network Attached Storage
Web proxy only access is not sufficient. Web Sites UAC. Note If you are logged on as a user that has Administrator privileges on a remote Web Sites Cloud role machine you can disable UAC on the remote machine by running the following command from an elevated command prompt:%windir% System32 cmd.exe /k%windir% System32 reg.exe ADD HKLM SOFTWARE Microsoft Windows CurrentVersion Policies System /v EnableLUA /t REGDWORD /d 0 /f Substitute the name of the remote Web Server Cloud role machine for to disable UAC on the remote machine. Environment Requirements. By default, Web Sites are created under a default domain.
Once a website is created, users can add custom domain names to each web site. While tenant web sites can be configured to support custom domains, Web Sites does not update custom DNS records.
For a given domain such as MyCloud.com you would create the following DNS A records: Host name IP for. Front End Server(s) ftp Publishing Server(s) publish Publishing Server(s) www Service Management Tenant Portal @ (or empty) Service Management Tenant Portal This mapping scheme would allow users to login into both and to manage their sites. These two hostnames map to the portal websites that users and administrators use to manage the software. The portals are described later in this guide. In this configuration, user-created web sites are initially created using child domains such as site1.mycloud.com, site2.mycloud.com, etc. Content publishing via Web Deploy and FTP uses publish.mycloud.com and ftp.mycloud.com respectively.
Content publishing via git uses.scm.mycloud.com. If using a standalone Windows File Server, file server preparation is not required and is automated during the installation process. 2018 gmc sierra radio color guide. If, however, you are using a file server cluster or NAS device, you must create the following shares:.
Content Share – contains tenant website content. Certificate Share – contains tenant custom certificates. In addition, you will need to create users with the following permissions: User Content Share Permissions Certificate Share Permissions FileShareOwner Read/Write Read/Write FileShareUser Read/Write CertificateShareUser Read/Write. Note Web Sites makes use of a new security technology which does not depend on per web site file share permissions. This enables Web Sites to work with heterogeneous file storage implementations such as NAS devices.
On Windows file servers or clusters, install the File Services role and File Server Resource Manager role service on the File Server using the following commands:. PowerShell.exe Enable-PSRemoting –Force.%windir% system32 dism.exe /online /enable-feature /featurename:FSRM-Management /featurename:FSRM-Infrastructure Role Account Preparation. Ensure that the SQL server(s) that will be used for storing the Web Sites configuration database as well as any per-user/per-website databases are accessible remotely. Test IP connectivity and name resolution between all VMs. Ensure that the SQL Server(s) have remote access enabled. Ensure that the SQL Server(s) have mixed mode authentication enabled. Enable the TCP protocol on the SQL Server computers.
For SQL Server, follow the steps described. For SQL Server Express, use SQL Server Configuration Manager to update TCP ports.Click Start, All Programs, Microsoft SQL Server 2008 R2, Configuration Tools, SQL Server Configuration Manager to open the SQL Server Configuration Manager. Then navigate to Protocols for MSSQLSERVER and click on the TCP/IP protocol.
Ensure that the TCP/IP protocol is enabled. Navigate to the IP Addresses tab and scroll down to IPAll.
Update the TCP port to 1433 and ensure that the TCP dynamic port is disabled. Restart the SQL Server (SQLEXPRESS) service. Configure Windows Firewall for Database engine access:. Add TCP port 1433 to the Inbound rules as described. Add SqlBrowser.exe (c: Program Files (x86) Microsoft SQL Server 90 Shared sqlbrowser.exe) to the Inbound rules. Enable the SQL Server Browser service if any of your SQL Server instances are running in an instance other than the 'default' SQL Server instance.
If Sql connection strings specify a SQL Server instance in addition to the machine name (e.g. YourSqlServerMachine SqlExpress), then the SQL Server Browser service must be running.
MySQL Server preparation. Note Update password to the root password used at the time of installation.