Solved

Can't create PowerShell virtual directory

Posted on 2013-01-11
6
2,549 Views
Last Modified: 2013-05-15
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
Comment
Question by:Joemt
  • 5
6 Comments
 
LVL 18

Expert Comment

by:Sushil Sonawane
ID: 38768506
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
 

Author Comment

by:Joemt
ID: 38768519
Remote Registry service was started and set to automatic startup. Would a screenshot or any other info aid you guys?
0
 

Author Comment

by:Joemt
ID: 38768554
Here is a screenshot of the error that is generated when attempting to create the virtual directory.
Powershell-error.jpg
0
New My Cloud Pro Series - organize everything!

With space to keep virtually everything, the My Cloud Pro Series offers your team the network storage to edit, save and share production files from anywhere with an internet connection. Compatible with both Mac and PC, you're able to protect your content regardless of OS.

 

Author Comment

by:Joemt
ID: 38768998
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
 

Accepted Solution

by:
Joemt earned 0 total points
ID: 38774918
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
 

Author Closing Comment

by:Joemt
ID: 39167434
Found the answer
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Utilizing an array to gracefully append to a list of EmailAddresses
A procedure for exporting installed hotfix details of remote computers using powershell
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video discusses moving either the default database or any database to a new volume.

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now