Alex Le
asked on
Cannot re-create PowerShellVirtualDirectory Exchange 2010 after deletion
I had this question after viewing Exchange Server 2010 - Error to recreate Powershell Virtual Directory.
I got the same problem, I followed the guidance in that topic but I cannot see the web.config created in the folder C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Po werShell. Then I checked by run the Get-PowerShellVirtualDirec tory to make sure this folder can be recognized by system but it seemed that it wasn't. Please see the pic attached.
Capture.PNG
I got the same problem, I followed the guidance in that topic but I cannot see the web.config created in the folder C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Po
Capture.PNG
Please try to run this command via Exchange Management Shell and share the output. Please run EMS as administrator
ASKER
Hi Gaurav,
Thank for your help. I have followed your guidance but whenever I open EMS, it could not connect to server (see the pic attached). I had got this problem some weeks ago before I deleted Power Shell Virtual Directory to troubleshoot the case.
I tried go on typing the command Get-PowerShellVirtualDirec tory and it came up with the error like the pic attached shows.
Error1.PNG
error2.PNG
Thank for your help. I have followed your guidance but whenever I open EMS, it could not connect to server (see the pic attached). I had got this problem some weeks ago before I deleted Power Shell Virtual Directory to troubleshoot the case.
I tried go on typing the command Get-PowerShellVirtualDirec
Error1.PNG
error2.PNG
Do you have the correct RBAC on the exchange? from the screenshot, I can see that your exchange environment is having issues.
ASKER
Hi Gaurav,
I am not sure about the RBAC correct or not, but I am logging in as Administrator to carry out the commands, do you have any advice more?
I am not sure about the RBAC correct or not, but I am logging in as Administrator to carry out the commands, do you have any advice more?
Can you check the Active Directory for the permissions for the account you logged and you can share the screen shot of the membership of the administrator account. I tried to connect you via Session sharing feature of EE.
ASKER
Hi,
I am logging with Administrator account as pics.
I have seen the session Sharing feature on my portal anywhere.
Capture1.PNG
Capture2.PNG
I am logging with Administrator account as pics.
I have seen the session Sharing feature on my portal anywhere.
Capture1.PNG
Capture2.PNG
ASKER
Hi ITGuy565,
Thank for you response. I had followed the link you sent before I raised the question here. After removing the PowerShell Directory , I coud not re-create it, and that's why I was here for the topic.
Thank for you response. I had followed the link you sent before I raised the question here. After removing the PowerShell Directory , I coud not re-create it, and that's why I was here for the topic.
Try this:
1. Open IIS console
2. For Default Web Site, Add a new Virtual Directory.
a) Alias: PowerShell
b) Path: C:\Program files\Microsoft\V14\Exchan ge Server\ClientAccess\PowerS hell.
3. Open Basic Settings of new Virt Dir and make sure the Application Pool is set to: MSExchangePowerShellAppPoo l.
4. If PowerShell-Proxy is missing as well then add another Virtual Directory.
a) Alias: PowerShell-Proxy
b) Path: C:\Program files\Microsoft\V14\Exchan ge Server\ClientAccess\PowerS hell-Proxy .
5. Open Basic Settings of new Virt Dir and make sure the Application Pool is set to: MSExchangePowerShellProxyA ppPool.
6. Turn off requirement for SSL.
1. Open IIS console
2. For Default Web Site, Add a new Virtual Directory.
a) Alias: PowerShell
b) Path: C:\Program files\Microsoft\V14\Exchan
3. Open Basic Settings of new Virt Dir and make sure the Application Pool is set to: MSExchangePowerShellAppPoo
4. If PowerShell-Proxy is missing as well then add another Virtual Directory.
a) Alias: PowerShell-Proxy
b) Path: C:\Program files\Microsoft\V14\Exchan
5. Open Basic Settings of new Virt Dir and make sure the Application Pool is set to: MSExchangePowerShellProxyA
6. Turn off requirement for SSL.
ASKER
Hi Peter,
Thank for your support.
I did follow that way and I got the error as the file shown.
Let me describe the nature of system briefly.
- It is Hybrid Exchange, mailboxes has been migrated to O365 for long time ago.
- We would often use EMC to set control on mailboxes, EMC is used to have 2 sections of on-premise and O365 on that.
- One day, the On-premised initialized fail and I tried to connect again by doing some troubleshooting.
- I have been following the way of re-creating Powershell Directory and have been stuck on here.
Let me know if you need more info to have more advice for the next step.
Alex Le
error.docx
Thank for your support.
I did follow that way and I got the error as the file shown.
Let me describe the nature of system briefly.
- It is Hybrid Exchange, mailboxes has been migrated to O365 for long time ago.
- We would often use EMC to set control on mailboxes, EMC is used to have 2 sections of on-premise and O365 on that.
- One day, the On-premised initialized fail and I tried to connect again by doing some troubleshooting.
- I have been following the way of re-creating Powershell Directory and have been stuck on here.
Let me know if you need more info to have more advice for the next step.
Alex Le
error.docx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Peter,
I did run the command. It said there's already the folded. However, I can not see anything from Get- .. command. Please see the pic attached.
Capture.PNG
I did run the command. It said there's already the folded. However, I can not see anything from Get- .. command. Please see the pic attached.
Capture.PNG
ASKER
Hi Peter,
I have just remove the folder by manually on IIS and re-created but it appeared an error like pic shown
Capture.PNG
I have just remove the folder by manually on IIS and re-created but it appeared an error like pic shown
Capture.PNG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Well, this is a simple way to do it...
go to the server
Open powershell console as Administrator and then run:
go to the server
Open powershell console as Administrator and then run:
#To enable exchange server commands on the server so you can actually run the New Psv...
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010;
New-PowershellVirtualDirectory -Name Powershell -InternalUrl "https://www.res.local/powershell"