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).
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
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.
The Background
Today I was reflecting on the pain install/OS testing. As we approach a new release of our windows software, we have to verify:
That it installs without issue
That it runs, given a reasonable fulfillment of dependencies
That our assumptions as to what is available on an "updated" machine are correct
On a range of architectures (32/64 bit, etc)
On a range of operating system versions (Windows XP, Windows Vista, 7, 8, etc.)
Our sad (but usual and cost effective) approach is to spin up some old boxes here on site. We either try to stuff an OS install into a VM system, or are forced to wipe the box and do a native install just to get to a "clean" install of the app. Depending on the functional approach, reverting snapshots may or may not be available.
The Idea
I realized that Windows Azure was making it very easy to spin up virtual machines these days and "pay for what you use". Mostly this appears to be focused on web hosting (Windows Server 2008 and Windows Server 8 are the only windows variants available in the "VM OS Selection" dialog). See this page for an overview.
But what if I could spin up other kinds of Windows OS images purely for testing?
I have an MSDN subscription, and access to a set of OSes that we should support. Couldn't I push these up somehow and have snapshottable, on-demand test hosts?
The Questions
Is this feasible right now with Windows Azure? (I can do this for Server 2008 and Server 8 now, it would seem...can i do this with other OS images?)
If so, how? (Can i upload a .vhd to storage in some manner as to have it show in the "my images" section?)
If not, is there a good alternative? (I get the sense you could do this with Amazon EC2? Am I barking up the wrong tree? Is this better to try and do onsite with VM software entirely?)
In the best case, I want "fresh" (recently patched) images for a set of supported Windows OSes that I can spin up on demand, pay for what I use, and then shut down again. Does this exist?
Thanks for your time and consideration...
P.S. Not entirely sure if this should be here or on serverfault...please advise.
1.Is this feasible right now with Windows Azure? (I can do this for Server 2008 and Server 8 now, it would seem...can i do this with other
OS images?)
The Windows Server is 2012, not 8. But anyway. So no. The currently supported Windows family OS'es are:
* Windows Server 2008 SP2 x64,
* Windows Server 2008 R2,
* Windows Server 2012
Note that all of them are just the 64bit versions! Frankly, I don't think Windows client OS'es will ever be supported (like XP, 7, 8)
2.If so, how? (Can i upload a .vhd to storage in some manner as to have it show in the "my images" section?)
No. so no way.
3.If not, is there a good alternative? (I get the sense you could do this with Amazon EC2? Am I barking up the wrong tree? Is this better
to try and do onsite with VM software entirely?)
Can't answer this question completely, but a quick search says that currently in Amazon EC2 you can run:
Amazon EC2 running Microsoft Windows Server® (available in 2003 R2,
2008 or 2008 R2 editions)
So far with Windows OSes.
In summary: Only Server Windows OS can be run in an Azure and Amazon.
A hint: you can't install Hyper-V on Windows server in either Azure nor Amazon (you can't virtualize what is already virtualized).
I have got the Windows Azure Platform account.
Fot he development with Windows Azure, can I use computer with Windows XP Professional.
If not what environment should i set to start working with Windows Azure, and migrating existing web projects to Windows Azure.
Regards.
Pravin.
Since azure uses Windows Server 2008 SP2/R2 as it's core OS, you will need at least Windows 7 or Windows Server 2008 to come close to mimicking the environment in Azure. If you are in a situation where you cannot upgrade your OS then you should look at utilizing a VM for development/testing purposes.
To answer your question, yes you can hack together a solution, is it pretty, no. Would I do it, no way. I also find that I like Windows 7 a lot better than XP or Vista, but I am also work for the man so I am jaded.
I've been researching EC2 over at Amazon Web Services and the website notes:
"You are also empowered to use our
bundling tools to upload your own
operating systems."
Now I've been trying to find out if the only Windows version that is supported is Windows Server 2003 or if I would be able to virtualize an older version of Windows and mash it into an AMI?
Is that possible?
Has anyone achieved it?
EC2 only allows you to bundle your own open source *nix operating systems. They won't let you run your own copy of Windows because of licensing issues.
only if you load a *nix platform with vmware then load windows onto a vm