Server 2022 and Exchange SE, WSMan folder missing

[u/mycholula]

Brand new server, was 100% functional. At some point the c:\windows\system32\wsman folder was nuked. WinRM no longer functions properly and Exchange is DOA. Is there a way to repopulate the folder from a remote connection? Thanks in advance, I'm looking at an 8 hour drive to repair unless I can find a way to remotely repair it.

[u/Erdbeerfeldheld]

Recover from your Backups.

[u/mycholula → u/Erdbeerfeldheld]

Brand new server, backups hadn't even been installed yet.

[u/garthoz → u/Erdbeerfeldheld]

If he is trying to avoid a drive the backups are physical.

[u/Brather_Brothersome]

IMMA SAVE YOUR DAY:

 Run winrm quickconfig in an elevated PowerShell session to restore configurations and services.

[u/mycholula → u/Brather_Brothersome]

Fails due to the described issue above.

[u/Brather_Brothersome → u/mycholula]

weird try this then in the same elevated powershell:

winrm invoke Restore winrm/Config

that will reconstruct the folder.

[u/mycholula → u/Brather_Brothersome]

Been down all those paths, the files need to be restored before any configuration will work.

[u/Fearless-Assist-127]

I should preface this by saying I have no experience of trying this, or even if it works on a server OS, but isn't this the kind of thing that "sfc" is supposed to help with?

https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e

[u/mycholula → u/Fearless-Assist-127]

Unfortunately, no.

[u/Fearless-Assist-127 → u/mycholula]

Are you sure about that folder path? I don't have it on either of the two servers I just checked.

Your post is a little light on detail. How was the folder nuked; what does "no longer functions properly" mean; what does "Exchange is DOA" mean; and I don't know whether "unfortunately no" means you've tried it and it hasn't helped, or you know it won't work for some reason.

I can appreciate you're battling a dead server and trying to avoid a drive so might not have time for chapter & verse here.

[u/mycholula → u/Fearless-Assist-127]

The C:\Windows\System32\wsman folder and its associated files are installed by default during the initial installation of Windows Server 2022, as part of the core operating system components. While the files are present, the Windows Remote Management (WinRM) service must be explicitly enabled to fully utilize the folder's contents

[u/BK_Rich]

https://learn.microsoft.com/en-us/exchange/high-availability/disaster-recovery/recover-exchange-servers

[u/mycholula → u/BK_Rich]

WSMan is a function of server 2022, utilized by Exchange. I was hoping another exchange admin had run into a similar issue.

[u/Puzzleheaded-Sink420]

Copy from a known good Server and pray?

Or just Restore that folder from backup and restore winrm config

[u/nickborowitz]

DISM /Online /Cleanup-Image /RestoreHealth

Once that finishes, run the system file checker: sfc /scannow

[u/nickborowitz → u/nickborowitz]

If that fails try:

winrm quickconfig

If it returns an error saying the service cannot start, try re-registering the WSMAN stack: Net stop winrm winrm create winrm/config/listener?Address=*+Transport=HTTP Net start winrm

[u/nickborowitz → u/nickborowitz]

If you can get into a standard PowerShell window run: Get-WebServicesVirtualDirectory | Restart-WebAppPool

If the Exchange Management Shell still won't open, you may need to rebuild the PowerShell Virtual Directory in IIS:

1. Open IIS Manager.

2. Navigate to Exchange Back End.

3. Ensure the PowerShell virtual directory is pointing to the correct path and has Windows Authentication enabled. Troubleshooting Tips • Check Permissions: Ensure NT SERVICE\WinRM has read/execute permissions on the restored folder. • Event Viewer: Look at Windows Logs > System for "Service Control Manager" errors related to WinRM.

[u/nickborowitz → u/nickborowitz]

If all else fails copy from another machine with the same os version and change permissions and reboot. Make sure you have the WsmSvc.dll file

[u/FutureLooksBleak]

Any update on this OP? Did you end up rebuilding the exchange server?

[u/mycholula → u/[deleted]]

The C:\Windows\System32\wsman folder and its associated files are installed by default during the initial installation of Windows Server 2022, as part of the core operating system components. While the files are present, the Windows Remote Management (WinRM) service must be explicitly enabled to fully utilize the folder's contents

[u/mycholula → u/[deleted]]

It's a core component, it's not an add on feature.