serverfault.com

I want to use Hyper-V on a Windows Server 2025 hosted via Hyper-V. ExposeVirtualizationExtensions is true in PowerShell for the guest system. Server Manager shows the Hyper-V role installed, but searching for Hyper-V in the Windows search bar produces no results. There is a Hyper-V section in Server Manager that shows that Hyper-V is installed and running (vmms). There is also no Hyper-V shortcut at C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools. and virtmgmt.msc does not exist in the system32 folder. How can I access Hyper-V Manager now?

I am seeking help here looking for something which can do what the title suggests. FTP is a terrible protocol, but many very expensive legacy devices that I'm dealing with still require it for remote support. The legacy devices cannot be upgraded to SFTP or equivalent due to both technical and non-technical reasons. I'm trying to find an existing product or a daemon "protocol proxy" that can just be deployed on a small device, docker, or VM and left alone. Preferably on something like an Intel NUC right next to the legacy device, so that the insecure FTP protocol is not ever going over the intranet. Tunneling over SSH is also not viable due to the random ports used by active/passive mode data connection. There are some 'managed file transfer' tools out there which are like pulling out a nail with a jackhammer... looking for something less 'enterprisey' in that regard. I have created a protocol proxy daemon like this using Java with some Ap

I'm trying to set up Nginx to proxy_pass the location / to an external host. I want the redirect to be masked so it looks like it's served from the old host. So I can't use return 301 <new_host> And I only want to redirect the / endpoint, not /api This is my default.conf for nginx: server { # catch all request listen 80; server_name _; location /api/ { proxy_pass http://apiserver:8080/api/; proxy_redirect default; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location / { proxy_pass http://<new_host>/frontend/index.html; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

I have 2 Windows 11 Pro boxes. Machine A has 2 screens, Machine B has 3. The problem is that after I connect (not using use multimon) From A to B, all the applications running on B move from Display 1 (as identified by the Display Settings GUI) to Display 3. mstsc.exe /l on Machine B shows three displays, 0:, 1: and 2:. 0: corresponds to Display 3 from the GUI (i.e., not the one I want), 1: corresponds to Display 1 from the GUI (i.e, the one I want.) I suspect that the incoming connection is routed to "0:" by default. The selectmonitors parameter allows me to control which monitor on Machine A is used, but I want to control which monitor on Machine B is used. Is there a way to configure RDP on either host to connect to display 1 (or "1:") on Machine B?

We have a 2 proxy, 4 MYSQL server setup, all in one percona cluster. Our data guys do not want their oozie database on Percona. We left it as is for years. The proxy is a floating ip address (xx.xx.xx.60) which passes through to xx.xx.xx.61 and xx.xx.xx.62. One in one datacentre and one in the other. 2 database hosts in one datacentre (dc1-db1, dc1-db2) and 2 in the other (dc2-db1, dc2-db2). Last year I moved it over from the single server it currently sits on, and kept an eye on the tables. After I saw records being written real time I left it in place. A day later I got a message stating data was missing. It transpires that some transaction data was not being written but it appears that the transaction may have been started. I moved the DB back to a single host. I reviewed the percona setup and the proxy. The parameters seem to fall into line with what examples I could see out there. Client and server timeouts are 60 minutes and the proxy balance is

I am attempting to implement block-level remote disk access between two Windows systems: System B (Target): Hosts a physical disk (e.g., \.\PhysicalDrive0) System A (Initiator): Connects over iSCSI and mounts the disk as a local block device Current Approach: Using Windows iSCSI Target Server, which requires virtual disks backed by VHD/VHDX files. Issue: Creating a VHDX for a physical disk results in full-size allocation (e.g., a 400 GB disk requires ~400 GB storage) This introduces: Significant storage overhead Delay in provisioning It prevents instant exposure of the physical disk over the network Requirements: Export a raw physical disk directly (no intermediate full-size VHDX) Enable immediate / near-instant provisioning Maintain read-only access on the initiator side Ensure no additional storage footprint (no disk duplication) Preferably using Windows-native mechanism

In the Azure AD ecosystem, what tools or functionality can be used to query and log user activity statuses at regular intervals? In my prior job the IT team had an Azure/AD "view" (or equivalent) that allowed Reporting Analysts to pull down user activity. The data was in 5 minute intervals, and would tell us if a PC was active, idle, or locked in that period. The idle status was based on the lack of keyboard and mouse activity. The company was fairly invested in the Azure environment, I remember them using Intune and Endpoint Manager, and am sure there were other Microsoft products but cannot recall sorry.

In our Windows Server 2016/2019 Active Directory Environment, We are getting Directory Service 1988 events. We tried through MS GUI tool but unable to process, received failed to remove lingering object and operation failed. We tried removing manually from domain controller. Follow the this Format repadmin /removelingeringobjects Authserver 04dc247f-cb35-43ac-8856-23f4603076b0 CN=configuration, DC=rootcon, DC=local /advisory_mode Removal of lingering objects was successful on authserver, but still showing. How should lingering objects be removed?

I am researching the possibility of overcommitting memory on a host where many Windows servers are running. The virtual machines are QEMU/KVM backed and managed by Libvirt. My current observation is that as soon as the Windows Server boots, the QEMU process will occupy the same amount of RSS memory as defined in -m option. On the other hand, a Linux guest does not behave the same way, as it will gradually consume more memory as the virtual machine runs. One solution to over commit memory is to enable KSM. But the drawback of this soluti

I created several Azure OpenAI resources in my Azure account. I deployed GPT models in each of the Azure OpenAI resources. I access them via the Azure OpenAI Playground. How can I configure each Azure OpenAI resource so that one cannot spend more than 50 USD monthly on it? I tried adding a budget, but I couldn't find an option to put a hard limit on the expenses.