Windows Server, IIS & Docker Container
Hi , Let say, I have 5 .NET API Containerize using Docker Container on Windows Server 2022. This 5 Container can be accessed using IP Address and Port on each My question is, What happen with my IIS on Windows Server 2022 ? Is that unused ? If unused, can I use this IIS to publish other .NET Application using Direct file deploy ? Please helpfeature Installation Error
I am facing this issue in Windows Server 2019 STD. i am also tried to solve this issue to select sources\sxs path from the OS media but still i am getting the same error. Mistakenly i have removed .Net framework from this server and after that i am facing this issue. please help me to solve this issue.
Windows Server 2025 Desktop Experience: Hyper-V cannot be installed
I have a lab with various Servers running Windows Server 2025. Some of them are installed without Desktop Experience, some with. Aside from Desktop Experience, the VMs and the operating are configured the same way using automated setup scripts. I exposed the VirtualizationExtensions for all VMs on the host using Set-VMProcessor -ExposeVirtualizationExtensions $true. Moreover, I configured all VMs to use static memory assignment. However, when I try to install Hyper-V on Windows Servers 2025 with Desktop Experience, I receive the error Hyper-V cannot be installed because virtualization support is not enabled in the BIOS. The issue occurs without any updates installed as well as with KB5050009 (2025-01 Cumulative Update for Microsoft server operating system 24H2 for x64 based Systems) installed. On machines without Desktop Experience, Hyper-V can be installed without any issues. As a side note, on VMs using Windows 11 24H2 on the same host, I can install Hyper-V without any issues.New survey - Windows Server application survey!
Happy new year everyone! With the new year, it's time to make plans and goals for the new cycle. At Microsoft, we're always planning for what's ahead, what we want to accomplish, and how can we delight our customers. That planning and the resulting prioritization is based on what we hear from our customers. So, from time to time we publish surveys to get a broader sense of what customers are thinking, how our products can help them succeed, and make sure we align our goals. Today, I'm here to ask for your input - we just released a new survey focused on understanding how customers approach Windows Server application modernization. This survey is focused on understanding how customers approach modernization of Windows Server apps, what are the challenges, how they think about the modernization process, what spins up the process, etc. This is of immeasurable value to us and will help us prioritize the work for the coming years. To answer the survey, please access: https://aka.ms/WSAppModSurvey. Feel free to share the link above with anyone and thank you in advance for your support!
What is Microsoft doing do battle the decline of Windows Server in the cloud?
What is Microsoft doing do battle the decline of Windows Server in the cloud? This is based on the news coming from the cma battle in the UK: https://www.theregister.com/2024/07/24/microsoft_cloud_cma/ This coming from someone that has invested 15+ years in learning and using Windows Server. Are there any hints as to how Microsoft might look at fixing this?
Azure VM Agent Status not ready
I have created a red hat openshift private cluster but the VMS are stuck in the state of "agent status not ready." I have followed these troubleshooting steps: Linux Virtual Machine Agent Status "Not Ready" - Microsoft Community Hub However, all of them seem to point to trying to check and see what is on the VM itself. I am unable to do this because I can't SSH into the machine. Has anyone else ran into this issue and been able to resolve it? I am deploying it via CLI as I was not able to do it via GUI for some reason. This is my script: #az login az account set --name "accountnamehidden" #az provider register -n Microsoft.RedHatOpenShift --wait #az provider register -n Microsoft.Compute --wait #az provider register -n Microsoft.Storage --wait #az provider register -n Microsoft.Authorization --wait $LOCATION= "eastus" # the location of your cluster $RESOURCEGROUP= "sample-rg" # the name of the resource group where you want to create your cluster $CLUSTER= "K8sDev1test" # the name of your cluster $arovnet= "sample-vnet" $mastersubnet = "k8sDev1-master-ue-snet" $workersubnet = "k8sDev1-worker-ue-snet" az aro create --resource-group "samplerg" --vnet-resource-group "sample-vnet-rg" --name $CLUSTER --vnet $arovnet --master-subnet "k8sDev1-master-ue-snet" --worker-subnet "k8sDev1-worker-ue-snet" --apiserver-visibility Private --ingress-visibility Private --fips true --outbound-type UserDefinedRouting --client-id hidden --client-secret hidden
