• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3059
  • Last Modified:

Can't create PowerShell virtual directory

Hi guys,

I ran into an issue creating the virtual directory as described. I get an error stating the following:

New-PowerShellVirtualDirectory : An error occurred while creating the IIS virtual directory ‘IIS://servername.domain.local/W3SVC/1/ROOT/PowerShell’ on ‘server’.

New-PowerShellVirtualDirectory -Name PowerShell -RequireSSL:$False
CategoryInfo : InvalidOperation: (server\P…fault Web Site):ADObjectId) [New-PowerShellVirtualDirectory],

and so on.

Any suggestions?
0
Joemt
Asked:
Joemt
  • 5
1 Solution
 
Sushil SonawaneCommented:
Please check the remote registry properties service started and startup type automatic.

For more info refer below link:
http://technet.microsoft.com/en-us/library/dd159915%28EXCHG.80%29.aspx
0
 
JoemtAuthor Commented:
Remote Registry service was started and set to automatic startup. Would a screenshot or any other info aid you guys?
0
 
JoemtAuthor Commented:
Here is a screenshot of the error that is generated when attempting to create the virtual directory.
Powershell-error.jpg
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
JoemtAuthor Commented:
Ok, i have resolved my previous issue by manually creating the MSExchangePowerShellAppPool in IIS. Apparently it was missing. I then manually created the PowerShell virtual directory and matched it's settings to another server i had for comparison.

I'm now receiving and error that states:

Processing data for remote command failed with the following error message: WinRM cannot complete the operation. Verify that the specific computer name is valid, that the computer is accessible over the network, and that the firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computer within the same local subnet.
0
 
JoemtAuthor Commented:
This morning, out of morbid curiosity, I checked the Exchange Management Console. Turns out over the weekend the stars aligned just right and now it's working again. I can safely say that nothing was changed, and no reboots happened over the weekend. I can only guess that some kind of maintenance cleared the issue. Whether it was the Kerberos keychain or something else, I don't know.

If anyone has any ideas as to what could have happened, I would love to know for future reference.

Thanks all!
0
 
JoemtAuthor Commented:
Found the answer
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now