Is Azure AD application proxy on Windows Server core? - azure

Is it possible to install and configure an Azure application proxy connector on windows server 2016 (Core), or does it only work on full (UI) server install?

It's possible. The Document states:
To use Application Proxy, you need a Windows server running Windows
Server 2012 R2 or later. You'll install the Application Proxy
connector on the server.
It seems you only need a windows server 2012 R2 or above. You can try to install the Application Proxy connector with commands.
Here is a tutorial for server core: Install & Register Azure AD Application Proxy Connector on Windows Server 1709
More references:
What is the Server Core installation option in Windows Server?
Create an unattended installation script for the Azure AD Application Proxy connector

Related

Deploy website to IIS from VS - options aren't present?

I am trying to get web deployment working, but following Microsoft: Publish to IIS
Prerequisites:
Must have VS2019 [yes]
Server is running Windows 2019 DataCenter
Running IIS 10
ASP 2.0, 3.0 and 4.7 installed
Web Deploy 3.6 for Hosting Server installed
Web Account Manager Service running
Web Deployment Agent Service running
Web Management Service Running
IIS Management Scripts and Tools installed
With the above installed, the instruction say to restart the IIS Console and chose Deploy > Configure Web Deploy Publishing from the Default website, but it's not showing (on the Default Site, or my App Services site)
To resolve the close iis manager if it is open.
Go to the "programs and feature".
Select web deploy -> click change.
Enable IIS Manager UI Module, IIS Deployment Handler, and Remote Agent Service.
Click next -> change -> finish.

ERROR_SMO_NEEDED_FOR_SQL_PROVIDER when I'm trying to Web Deploy

When I try to publish project from Visual Studio 2019 to remote IIS server, I'm getting an error:
"The SQL provider cannot run because of a missing dependency. Please make sure that Microsoft SQL Server Management Objects (Version 10 or higher) is installed. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_SMO_NEEDED_FOR_SQL_PROVIDER".
This is the first time I installing software to server, so here is what I did, following instructions on the web:
Added features: Windows Deployment Services (with Deployment Server and Transport Server), IIS Management Console, IIS Management Scripts and Tools, Management Service, Logging Tools.
Installed SQL Server Management Objects (version 13.0.1601.5), Microsoft Web Deploy 3.6 (because of version 4.0 won't offer me to install IIS Deployment Handler and won't show me Deploy menu in the IIS).
Tried to configure Web Deploy Publishing for existing user from Active Directory with defining connection string to SQL server.
Allowed users in IIS Manager Permissions.
Some important information:
Server is in domain, connection to internet restricted. Application works in intranet.
Using Web Platform Installer permitted because of item 1. Any programs should be installed offline only.
Server haven't been used for Web Deploy before.
Before installing Microsoft Web Deploy 3.6, I was unable to check connection from Visual Studio and even hadn't current error.
I guess that error happens because of incorrect connnection strings (Enter SQL Server/MySQL connection string to be used for publishing).

How to create publishing profile for azure virtual machine?

How to create publishing profile for a website running on azure virtual machine?
I know how to do it for Azure Web Site, but can this be done if I have IIS running on a VM in azure?
I also have a console application running using task scheduler on this VM, it would be nice to automate that deployment too.
( After working with Rails and Php frameworks, I miss the common config file used by the website and CronJob to connect to the DB)
You need to set up Webdeploy in the azure VM. it is same as an on-premises server.
Web Deploy Installation.. You need to install prerequisites - .net framework.
Configuring IIS 7 with webdeploy / Or with IIS8
Set up endpoints on azure vm to do webdeploy. Port 8172 for Webdeploy.
Then you can create a publish profile in Visual Studio 2012/13 to deploy to this endpoint.
http://msdn.microsoft.com/en-us/library/dd465337(v=vs.110).aspx
or You can do it using Powershell scripts.
sample-
http://gallery.technet.microsoft.com/scriptcenter/Deploy-a-Web-App-to-Two-99f1a3bc

Windows Server App Fabric Environment setup on SharePoint 2010

I have One SQL Database server, two WFE and one APP server. I have planned to install windows app fabric server for caching mechanism. What is the best approach to install app fabric servers for my environment?
should it install on all WFE or only on APP server ?
The Intention of having App Fabric Cache server installation is to increase the performance and the response time of the application or the service. SO, I would recommend to have it installed separately.

Disparity in options available in Web Deploy 2.0 on two matching servers

IIS 7.5 is installed on two servers (both Windows Server 2008 R2) with Web Deploy 2.0 installed (to enable me to Publish from Visual Studio 2010.) Publishing straight from VS requires the Web Management Service be running on the server. I've been publishing to the first server for months, no problem. The second server has just been spun up (not by me) but as far as I can tell has all the same versions of components (OS, IIS, Web Deploy). However, on the second server the Web Management Service isn't installed. There's a key difference:
Web Deploy 2.0 options available on the first server:
Web Deploy 2.0 options available on the second server:
Why is there a difference between the two?
(Follow-up: I tried the Web Deploy 3.0 installer and encountered the exact same dialog as the second server, above, except that it said "3.0" instead of "2.0".)
Verify the proper IIS roles are installed on your new server. In the Server Manager console, under Web Server (IIS), verify the following roles are installed:
Management Tools
IIS Management Console
IIS Management Scripts and Tools
Management Service
Then try re-running your Web Deploy installer. I think you'll find you get the options you desire.

Resources