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.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?
Windows Server 2019: The component store has been corrupted. Error 0x80073712
Hi all, I'm trying to install the Server Backup feature on our 2019 Server, but it results in this error: Any ideas on what may have caused this, and how to solve it? The server was installed about 5 months ago, and the installation is basically stock, not much changes made. Thanks in advance.
Error when creating task using command prompt in Windows 2019 docker container
My host is Windows 2019 standard. It contains docker image which is also based on Windows 2019 standard core (no GUI). This is the image I am using: mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2019 When I run following command on host then it works fine. But running same command in Docker container results in error. Command schtasks /create /sc minute /mo 1 /tn StudentManagementSystem /tr C:\StudentManagementSystemConsole\StudentManagementSystemConsole.exe Error The task XML contains a value which is incorrectly formatted or out of range Using following PowerShell script in Docker container also results in exact same error. $action = New-ScheduledTaskAction -Execute "node" -Argument "C:\StudentManagementSystemConsole\StudentManagementSystemConsole.exe" $now = Get-Date $interval = New-TimeSpan -Seconds 60 $forever = [System.TimeSpan]::MaxValue $trigger = New-ScheduledTaskTrigger -Once -At $now -RepetitionInterval $interval $settings = New-ScheduledTaskSettingsSet $task = New-ScheduledTask -Action $action -Trigger $trigger -Settings $settings Register-ScheduledTask -TaskName ‘Student Management System’ -InputObject $task How to fix this issue?CreateJunction inside Docker volume works on Datacenter Edition but not on Standard Edition
Hi all, I'm using a Windows Server machine to build my code with Bazel inside a Windows docker container. I want to use a docker volume to keep the Bazel cache between builds. When using Windows 10 Pro or Windows Server 2022 Standard Edition I run into this error. However, when using Windows Server 2022 Datacenter Edition everything works fine. I would understand if it wasn't working only on Windows 10 Pro as isolation modes are different (windows : hyper-v virtual machine, server: process) . From the Datacenter specification, I cannot find what justifies this difference. I know this seems like a Bazel bug but the fact that it works on the Datacenter Edition and not on the Standard Edition makes me think there is more to it. Does anyone know what causes this difference?Changing default location (OU) for domain computers
Hello All, To bring some better structure to our AD, we're looking into organizing our client domain machines in AD, under an OU hierarchy. Part of this was also (possibly) changing newly joined machines to go to a separate OU, versus inside of the default Computers container. I've found a couple of methods for doing this, however, I'm not sure if this is a supported thing to do. I'm curious what others' opinions are of this. Thanks
