Quantcast
Channel: How to recreate Powershell Virtual Directory
Viewing all 21 articles
Browse latest View live

How to recreate Powershell Virtual Directory


How to recreate Powershell Virtual Directory

$
0
0

All you need to do to re create it is connect to the server's console, open up windows powershell (Not the Exchange MGMT Shell) and run the two commands below.  This will work provided that the PowerShell virtual directory is missing on the local machine.

add-pssnapin Microsoft.Exchange.Management.PowerShell.E2010

New-PowerShellVirtualDirectory -Name "PowerShell" -InternalURL "http://YOUR_SERVER_FQDN_HERE/powershell"



How to recreate Powershell Virtual Directory

$
0
0

You've probably solved your issue by now, but I've experienced the same issue, so I post the solution so it may help others:

Edit the "applicationHost.config" file located at "C:\Windows\System32\inetsrv\config".

Look for "D:\" sting in the XML file which will be on a line starting by "Kerbauth".

Replace it by "E:\", then recyle IIS.

How to recreate Powershell Virtual Directory

How to recreate Powershell Virtual Directory

$
0
0
I would like to remove and re-create powershell virtual directory in IIS. After I changed the drive letter from D: to E: the kerbauth.dll is still pointing to D:\ path
D:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll. 

Is there any why I can edit kerbauth.dll path in Powershell Modules ? 

because of this I am not able to open EMC. 

I already tried http://msexchangeteam.com/archive/2010/02/04/453946.aspx and I found out the kerbauth.dll is still pointing to D:\ path instead of E:\

How to recreate Powershell Virtual Directory

How to recreate Powershell Virtual Directory

$
0
0

All you need to do to re create it is connect to the server's console, open up windows powershell (Not the Exchange MGMT Shell) and run the two commands below.  This will work provided that the PowerShell virtual directory is missing on the local machine.

add-pssnapin Microsoft.Exchange.Management.PowerShell.E2010

New-PowerShellVirtualDirectory -Name "PowerShell" -InternalURL "http://YOUR_SERVER_FQDN_HERE/powershell"



How to recreate Powershell Virtual Directory

$
0
0

You've probably solved your issue by now, but I've experienced the same issue, so I post the solution so it may help others:

Edit the "applicationHost.config" file located at "C:\Windows\System32\inetsrv\config".

Look for "D:\" sting in the XML file which will be on a line starting by "Kerbauth".

Replace it by "E:\", then recyle IIS.


How to recreate Powershell Virtual Directory

How to recreate Powershell Virtual Directory

$
0
0
I would like to remove and re-create powershell virtual directory in IIS. After I changed the drive letter from D: to E: the kerbauth.dll is still pointing to D:\ path
D:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll. 

Is there any why I can edit kerbauth.dll path in Powershell Modules ? 

because of this I am not able to open EMC. 

I already tried http://msexchangeteam.com/archive/2010/02/04/453946.aspx and I found out the kerbauth.dll is still pointing to D:\ path instead of E:\

How to recreate Powershell Virtual Directory

How to recreate Powershell Virtual Directory

$
0
0

All you need to do to re create it is connect to the server's console, open up windows powershell (Not the Exchange MGMT Shell) and run the two commands below.  This will work provided that the PowerShell virtual directory is missing on the local machine.

add-pssnapin Microsoft.Exchange.Management.PowerShell.E2010

New-PowerShellVirtualDirectory -Name "PowerShell" -InternalURL "http://YOUR_SERVER_FQDN_HERE/powershell"



How to recreate Powershell Virtual Directory

$
0
0

You've probably solved your issue by now, but I've experienced the same issue, so I post the solution so it may help others:

Edit the "applicationHost.config" file located at "C:\Windows\System32\inetsrv\config".

Look for "D:\" sting in the XML file which will be on a line starting by "Kerbauth".

Replace it by "E:\", then recyle IIS.

How to recreate Powershell Virtual Directory

How to recreate Powershell Virtual Directory

$
0
0
I would like to remove and re-create powershell virtual directory in IIS. After I changed the drive letter from D: to E: the kerbauth.dll is still pointing to D:\ path
D:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll. 

Is there any why I can edit kerbauth.dll path in Powershell Modules ? 

because of this I am not able to open EMC. 

I already tried http://msexchangeteam.com/archive/2010/02/04/453946.aspx and I found out the kerbauth.dll is still pointing to D:\ path instead of E:\

How to recreate Powershell Virtual Directory

How to recreate Powershell Virtual Directory

$
0
0

All you need to do to re create it is connect to the server's console, open up windows powershell (Not the Exchange MGMT Shell) and run the two commands below.  This will work provided that the PowerShell virtual directory is missing on the local machine.

add-pssnapin Microsoft.Exchange.Management.PowerShell.E2010

New-PowerShellVirtualDirectory -Name "PowerShell" -InternalURL "http://YOUR_SERVER_FQDN_HERE/powershell"



How to recreate Powershell Virtual Directory

$
0
0

You've probably solved your issue by now, but I've experienced the same issue, so I post the solution so it may help others:

Edit the "applicationHost.config" file located at "C:\Windows\System32\inetsrv\config".

Look for "D:\" sting in the XML file which will be on a line starting by "Kerbauth".

Replace it by "E:\", then recyle IIS.

How to recreate Powershell Virtual Directory

How to recreate Powershell Virtual Directory

$
0
0
I would like to remove and re-create powershell virtual directory in IIS. After I changed the drive letter from D: to E: the kerbauth.dll is still pointing to D:\ path
D:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll. 

Is there any why I can edit kerbauth.dll path in Powershell Modules ? 

because of this I am not able to open EMC. 

I already tried http://msexchangeteam.com/archive/2010/02/04/453946.aspx and I found out the kerbauth.dll is still pointing to D:\ path instead of E:\
Viewing all 21 articles
Browse latest View live