We are busy migrating our application from a classic Cloud Service to a new App Service model.
We've done this before, but are now stumbling to something strange and I'm suspecting it might have something to do with the underlying operating system.
The Cloud Service is running on a VM with the Windows Server 2016 family installed (OS Version: 10.0.14393 according to this link: https://www.gaijin.at/en/lstwinver.php)
From what I can tell, the App Service Plan has a much older operating system installed, because Kudu is giving me the following OS information
OS version: Microsoft Windows NT 6.2.9200.0
Which apparently is Windows Server 2012.
In order to test my hypothesis I want to upgrade the OS version of the App Service Plan, but I can't figure out how to do this or even if this is possible.
Yes, currently, web app is hosted on Windows Server 2012.
In order to test my hypothesis I want to upgrade the OS version of the
App Service Plan, but I can't figure out how to do this or even if
this is possible.
Currently, it is not possible. Now Azure Web app is not supported on Windows Server 2016. Based on my experience, it will supported in the future.
Related
Hello im new on this type of software i had serch on Google about MQ but all what i find is that it can be install on linux windows xp ...
so this may be stupid but is there any way to install MQ on windows server
is there any way to install MQ on windows server
Yes. If you have purchased it you should be able to download it for production use via IBM Passport Advantage, all the details can be seen here:
https://www-01.ibm.com/support/docview.wss?uid=swg24043697
If you only want to use it for personal developer use, you can use the free developer edition, which can be found here:
https://developer.ibm.com/messaging/mq-downloads/
So for clarity, 9.1 is the latest LTS (long term service) release, 9.1.1 is the latest CD (continuous delivery) release. Which is more useful depends on what you are trying to use. It is supported on a range of operating systems, including Windows.
From the 9.1 SOE (System requirements), this is supported in windows server 2016 and windows server 2012r2 (that's the server o/s's as well Windows 10 and 8.1 for desktops). If you need older operating system support, you need to look at older MQ releases, such as 9.0*, 8.0* etc.
MQ windows drivers can be installed on any windows machine, depending upon the system requirement for particular MQ, it is not restricted to Windows XP only
System Requirements for MQ 9.1
https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=B560B760819A11E6B5854315721876AE&osPlatforms=Windows
System Requirements for MQ 9.0
https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=8360DD50895F11E5816C133BBD3A3812&osPlatforms=Windows
System Requirements for MQ 8.0
https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Windows
Do we have an option to upgrade Windows OS in Azure?
I'm looking for a solution to upgrade my WINDOWS OS in Azure. I didn't find any answer.
Is there any alternative way to do this?
As per the following KB
Microsoft does not support an upgrade of the operating system of a Microsoft Azure virtual machine"
To work around this issue, create an Azure VM that's running a supported version of an operating system, and then migrate the workload (Method 1, preferred), or download and upgrade the VHD of the VM (Method 2).
Hi I have a console app which I need to start up when Windows Server 2012 starts and without needing to login. I've done a bit of research and people advise a windows service is the correct approach, however the links are quite old and I wanted to confirm this is still the case, or indeed correct at all. Cheers.
Yes, Windows Service is still the most popular way to write and run servers and or a 'daemon' in Windows OS.
Depending on what your application is doing, you might have other options though, e.g. hosting an application in IIS (Microsoft's Web server application in Windows Server).
More recently, Microsoft has been working with Docker to also allow the use of containerized application deployments, which is available in new versions of Windows Server (Windows Server 2016).
Here are a few resources for more reading:
For .NET developers: Walkthrough: Creating a Windows Service Application in the Component Designer
Not just for .NET developers: Quick Start: Windows Containers on Windows Server
Why is there a specific version of MongoDb for windows azure? The normal windows version seems to work just fine? What's the difference between those two?
This seems to be the case for a lot of applications, including memcached which someone have made a windows azure port of.
Why would I use a windows azure version of any application? What do I gain?
Why is there a specific version of MongoDb for windows azure? The normal windows version seems to work just fine? What's the difference between those two?
The normal MongoDB install requires an existing Windows environment.
The MongoDB Installer for Windows on Azure includes the provisioning of Azure VMs as well as installation of MongoDB. Provisioning options can also include selecting an Azure data centre location and creating multiple VMs for a replica set.
There is also a package to deploy MongoDB Worker Roles using Azure's Platform-as-a-Service instances.
Why would I use a windows azure version of any application? What do I gain?
If you use the normal Windows installer, you have to create the Azure instances yourself and then download & install MongoDB. If you are creating a replica set you will have to repeat this for each node and add the configuration manually.
The Azure installer simplifies the number of manual steps needed to get your deployment up and running.
I am trying to get the Azure SDK up and running on my dev PC and have been having some issues.
I have installed the SDK, tools for VS and am trying to run the samples. Every time I try to run the samples the Development Storage service starts and then the Developer Fabric tries to start. This is where is stops. The Developer Fabric cannot run any websites for whatever reason.
I have followed their checklist for setting up the system and there is not Event messages. I am running under Vista Home Premium with IIS 7 installed.
If you have any suggestions I would love to hear them.
It turns out my problem is a little deeper than simply Azure not working on my computer.
In order to natively debug IIS apps using windows vista (configured under the project settings) you need to have windows authentication enabled for IIS. This feature cannot be installed let alone enabled under Vista Home Premium under the guise of what home user would want such a feature.
For the average VS 2005 user this is okay there is a hotfix but for me and my fancy VS 2008 SP1 there is no solution.
After becoming supremely frustrated with this issue I posted it as the following Microsoft Connect issue.