Monday, October 17, 2011 9:48 PM
I've setup Server Core with Hyper-V 2008R2 on a couple of boxes. On one of them, I was successful in my attempt to enable Server Manager Remote Management. On the other one, I get the message:
Configuring Remote Server Manager settings...
C:\Windows\System32\en-us\sconfig.vbs(968,5) (null): The system cannot find the file specified.
It looks like line 968 is calling powershell.exe and Configure-SMRemoting.ps1. I tried running powershell.exe from the command prompt and got back:
'powershell.exe' is not recognized as an internal or external command, operable program or batch file.
So I went back to sconfig and tried to enable powershell. Choosing that option returns me right to the prompt with not success or failure messages.
Next I ran DISM /Online /Get-Features and found that MicrosoftWindowsPowerShell was disabled. Great, so I ran DISM /Online /Enable-Feature /FeatureName: NetFx3-ServerCore and DISM /Online /Enable-Feature /FeatureName=MicrosoftWindowPowerShell. Now both features are enabled, but I'm still unable to run powershell from the command prompt or enable remote management.
How can I fix this? Thanks.
Tuesday, October 18, 2011 2:19 AMModerator
Configure Remote Management
1) Allow MMC Remote Management
2) Enable Windows PowerShell
3) Allow Server Manager Remote Management
4) Show Windows Firewall settings
5) Return to main menu
If you want to enable 3) Allow Server Manager Remote Management, the system will prompt to enable Windows PowerShell first.
By the way, have you tried to enable “3) Allow Server Manager Remote Management” after you enabled Windows PowerShell? Did you get the same error?
In addition, if you can’t launch PowerShell directly in command line, please navigate to C:\Windows\system32\WindowsPowerShell\v1.0 folder and launch the shell.
- Edited by Vincent HuModerator Tuesday, October 18, 2011 2:21 AM
Wednesday, October 19, 2011 2:23 AMI had already enabled PowerShell when I ran option 3. After I used DISM, I re-ran option 3 and got the same error. What gives? Thanks.
Monday, October 24, 2011 9:44 AMModerator
Please refer to the following post to see whether you can resolve the issue.
Friday, October 28, 2011 9:01 PM
I ended up reinstalling Windows.
- Marked As Answer by Vincent HuModerator Tuesday, November 08, 2011 5:12 AM
Tuesday, July 10, 2012 4:40 PMClearly 'Vincent Hu' is trying to win some stupid F'ing contest by by labeling a bunch of crap as 'answers' - this is NOT an answer you ass hole.