Exchange 2010 Powershell virtual directory recreation

Nevermind Fixed.....
So apparently you have to run those commands in Powershell version 2.0, Exchange 2010 doesn't like powershell 3.0
to do that type powershell -version 2.0
then type the exchange commands.

Ok, so I opened up my IIS console today to fix a problem with Exchange and the fix was to change one of the Modules in the Powershell Virtual Directory, but when I clicked on Modules it threw an error. So I started to try an fix that, all the forums and suggestions I read said to remove the Virtual directory and recreate it...
My problem is recreating it, I get the following error, I've googled and searched a lot and can't find how to fix this.
This topic first appeared in the Spiceworks Community

Similar Messages

How to reinstall PowerShell Virtual Directory in IIS 7.5, Exchange 2010 SP1?

Hi, When reinstalling CAS role, accidently removed Powershell virtual directory in IIS and also the powershell folder under ClientAccess folder. Now EMC and EMS not working, all with Kerbrose error and WinRM error. How could I restore PowerShell virtual
directory and make it fully functional without a fully reinstall of EX2010? I tried manually add it in IIS and copy the web.config from another EX2010 server but failed. Can't access its module settings in IIS. How to recreate them? Any Powershell script(but
not the exchange one) can do the job?

Hello, thanks for your help so far!
I have a similar issue. But when hitting your 2 cmdlets in powershell, I obtain the following error:
New-PowerShellVirtualDirectory : Web object 'IIS://<FQDN Server>/W3SVC/1/ROOT' can't be found.
At line:1 char:31
+ New-PowerShellVirtualDirectory <<<< -Name "PowerShell" -InternalURL "http://<FQDN Server>/powershell"
+ CategoryInfo : NotSpecified: (0:Int32) [New-PowerShellVirtualDirectory], WebObjectNotFoundException
+ FullyQualifiedErrorId : 20F775D1,Microsoft.Exchange.Management.SystemConfigurationTasks.NewPowerShellVirtualDire
ctory
What am I doing wrong?
The IIS Default website is running. Server is W2008R2 SP1. Exchange 2010 SP3
You know you're an engineer when you have no life and can prove it mathematically

Exchange 2010 - Powershell Directory

Morning. I have googled everywhere and can't find an answer to this problem anywhere. Has anyone got an ideas??
PS C:\> New-PowerShellVirtualDirectory -Name "Powershell" -RequireSSL:$False
New-PowerShellVirtualDirectory : An error occurred while creating the IIS virtual directory
'IIS://<SVR>.<Domain>.com/W3SVC/1/ROOT/Powershell' on '<SVR>'.
At line:1 char:1
+ New-PowerShellVirtualDirectory -Name "Powershell" -RequireSSL:$False
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (<SVR>\Powershell (Default Web Site):ADObjectId) [New-PowerShellVir
   tualDirectory], InvalidOperationException
    + FullyQualifiedErrorId : 90E6376F,Microsoft.Exchange.Management.SystemConfigurationTasks.NewPowerShellVirtualDire
   ctory

Hi,
Please confirm if your Exchange Management Shell (EMS) and Exchange Admin Center (EAC) can be opened or work well in your Exchange server.
If you want to reset Windows PowerShell virtual directory for default web site in Internet Information Services (IIS), please
make sure the original PowerShell virtual directory has been deleted from the server:
1. No PowerShell listed in IIS Manager.
2. No PowerShell VD in ADSIEdit (CN=Configuration,DC=domain,DC=.com > CN=Services > CN=Microsoft Exchange > CN=Domain > CN= Administrative Groups > CN=(Groupname) > CN=Servers > CN=(ServerName) > CN=Protocols > CN=HTTP).
3. Run this command from the Elevated cmd prompt -> cscript.exe Adsutil.vbs delete w3svc/1/root/PowerShell.
If your EMS can’t be opened, then we can use Windows PowerShell Module shell to create the PowerShell virtual directory to have a try. If it doesn’t work, please collect some event logs or IIS logs in your Exchange server for further analysis.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 and Active Directory connector

Has anyone managed to provision an exchange 2010 mailbox with the dotnet connector bundle in the latest patch OW8.1.1.1/145769-01? ActiveDirectory.Connector-1.0.0.5143.zip and Exchange.Connector-1.0.0.5757.zip.
Provisioning the Active Directory account works fine but as soon as I add an exchange attribute I get an error: java.lang.RuntimeException: The specified directory service attribute or value does not exist. (Exception from HRESULT: 0x8007200A)
I checked everything I could think of. Either I'm missing something obvious or it does not work.
Greetings,
Marijke

Have you had any luck with this?
/hydrazine

Running Exchange 2010 PowerShell Scripts

Hello,
I have a PowerShell Script which calls PSSnapins for Exchange tools. The Exchange Management Tools are installed on the Tidal Server
The Script works fine by itself, I have executed it as the tidal users on the Tidal Server. I have also created a batch file to execute the Powershell script, which also works on the tidal server.
However when I run the job in Tidal it doesn't run correctly by that I mean it will run the none Exchange pieces. In the Output tab it shows:
Add-PSSnapin : The Windows PowerShell snap-in 'Microsoft.Exchange.Management.PowerShell.E2010' is not installed on this machine.
At E:\PowerShell\DailyChecks\Dag_daily.ps1:7 char:13
+ Add-PSSnapin <<<< Microsoft.Exchange.Management.PowerShell.E2010
    + CategoryInfo          : InvalidArgument: (Microsoft.Excha...owerShell.E2
   010:String) [Add-PSSnapin], PSArgumentException
    + FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.Ad
   dPSSnapinCommand
Add-PSSnapin : The Windows PowerShell snap-in 'Microsoft.Exchange.Management.Powershell.Support' is not installed on this machine
These Scripts also work via Windows Task Scheduler as written I would really like to get these to work in Tidal. We are Tidal 5.3.1.
Any help would be greatly appreciated.
Lee Merrill

I have struggled with a similar issue with Sharepoint snapin with performing a backup
I can give a couple of suggestions
Add snapin to default profiles
We also see a difference in 64 vs 32 bit oprerations
we had to add to both versions using a local profile.ps1 and adding a line
Add-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue
C:\Windows\System32\WindowsPowerShell\v1.0
C:\Windows\SysWOW64\WindowsPowerShell\v1.0
Execute remotely
Slightly different setup on our side
I am trying to invoke-command on the remote sharepoint server =
( you have to set up psremoting, etc)
Invoke-Command -ComputerName -scriptblock { E:\Backup\BackupSite.ps1}
Similarly I can execute the backup.ps1 with no issue on the server but can't from the tidal job.
I'll let you know if we find a fix
I am thinking double hop at this point and need to trust for delegation, etc
Marc

Add Exchange 2010 Powershell Modules with Domain Controller

Hi
We are looking for a way to run Exchange PS cmdlets from Windows 2008 R2 DC. How can we load teh Exchange PS modules with any other server
Thanks in advance
LMS

You don't need to - you can open a remote PowerShell session from the DC to the Exchange server and run the Exchange commands remotely. Use the following commands:
$PsS = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri <a href="http:///powershell">http://<serverFQDN>/powershell -Authentication Kerberos
Import-PSSession $PsS -ErrorAction SilentlyContinue

Exchange 2010 powershell calendar permissions

I want to give user01, user02, user03, and user04 reviewer rights to user05's calendar. What is the best way to do this? with a .csv file?
Please explain fully.

Dear All,
I also use this syntax:
Import-csv C:\user.csv | ForEach-Object{Add-MailboxFolderPermission -identity $_Samaccountname":\Calendar" -User "username" -AccessRights "reviewer"} , but isn't work.
csv file content:
"SamAccountName"
"testuser1"
"testuser2"
I got this error:
Add-MailboxFolderPermission : An existing permission entry was found for user: xyz.
At line:1 char:70
+ Import-csv c:\users.csv | foreach-object {Add-MailboxFolderPermission <<<< -identity $_Samaccountname":\Calendar" -User "[email protected]" -Acc
essRights "Author"}
    + CategoryInfo          : NotSpecified: (0:Int32) [Add-MailboxFolderPermission], UserAlreadyExis...nEntryException
    + FullyQualifiedErrorId : 377F77B8,Microsoft.Exchange.Management.StoreTasks.AddMailboxFolderPermission
Add-MailboxFolderPermission : An existing permission entry was found for user: xyz.
At line:1 char:70
+ Import-csv c:\users.csv | foreach-object {Add-MailboxFolderPermission <<<< -identity $_Samaccountname":\Calendar" -User "[email protected]" -Acc
essRights "Author"}
    + CategoryInfo          : NotSpecified: (0:Int32) [Add-MailboxFolderPermission], UserAlreadyExis...nEntryException
    + FullyQualifiedErrorId : 377F77B8,Microsoft.Exchange.Management.StoreTasks.AddMailboxFolderPermission
Certainly I checked and there is no permission for xyz user on testuser1 and testuser2 Calendar.
Any help would be appreciated

Exchange 2010 SP3 Active Directory update - can I do this 2 or 3 weeks in advance of SP3 Install?

Hi,
As above really - is it OK to do the setup.exe /PrepareAD three weeks in advance of the Exchange SP3 install?
My thinking is: one less thing to do at the update and all Domain Controllers should have updated / replicated well in advance of the Service Pack install.
I only have a single Domain with two AD sites (Head office and Disaster Recovery).
Any issues with this / reasons NOT to do it?
thanks,
Adam

Hello,
Updating AD this way shouldn't cause any problems. After that operation you should verify that all modifications were successful.
Thanks, I thought so. I will do the AD update ahead of SP3 and perform the necessary checks to ensure all is OK.
Regards,
Adam

Exchange 2010 Powershell PST Export

Is there a command that will export in bulk from csv with a column of SamAccountName just the following items to PST?
All Calendar Items
All Contacts
All Tasks

Not sure about a csv, but if you paste the contents of that column into a txt file you can make a PS script starting with a get-content, followed by a For Each loop that will run the new-mailboxexportrequest with the appropriate variables.

Exchange 2010 - Virtual Directory Internal & External URL's with Wildcard Cert

Hi Guys
I am trying to determine if my Exchange 2010 server Virtual Directory URL's are setup according to best practice. I'm sure anyone with good Exchange experience will instantly be able to tell me if my Virtual Directory DNS is correct or could cause issues.
Scenario:
Hosted Exchange 2010 SP1. Multiple client mail domains hosted
2x CA, 2x HT, 2x MB, 2x DC
Wildcard *.example.co.za certificate being used on CA servers
AD domain is he.example.za.net
CA Server naming example: ca1.he.example.za.net, ca2.he.example.za.net
he.example.net DNS is done by DC servers
External name used by clients: outlook.example.co.za (For Outlook setup and OWA access)
outlook.example.co.za has two A records pointing to the CA IP's
PROBLEM/CONCERN:
We have a random OWA log out issue that we believe might be due to ambiguous DNS names being used.
If I change the Virtual Directories External URL to be the FQDN of the server, we get a Certificate Error in clients (due to the .co.za Wildcard). The external URL clients use
must be on .co.za.
So are the Virtual Directory URL's causing the CA servers to loose track of who is authenticated in where (leading to OWA disconnection)? Is it fine to load balance the CA servers with the DNS the way we are doing currently? Any other issues you see?
Current Virtual Directory settings:
Note that they are identical on CA1 and CA2
[PS] C:>Get-OabVirtualDirectory -server ca2 |fl *url
InternalUrl : https://outlook.example.co.za/OAB
ExternalUrl : https://outlook.example.co.za/OAB
[PS] C:>Get-WebServicesVirtualDirectory -Server ca2 |fl *url
InternalNLBBypassUrl : https://ca2.he.example.za.net/ews/exchange.asmx
InternalUrl          : https://outlook.example.co.za/ews/Exchange.asmx
ExternalUrl          : https://outlook.example.co.za/ews/Exchange.asmx
[PS] C:>Get-ActiveSyncVirtualDirectory -Server ca2 |fl *url
MobileClientCertificateAuthorityURL :
InternalUrl                         : https://outlook.example.co.za/Microsoft-Server-ActiveSync
ExternalUrl                         : https://outlook.example.co.za/Microsoft-Server-ActiveSync
[PS] C:>Get-EcpVirtualDirectory -Server ca2 |fl *url
InternalUrl : https://ca2.he.example.za.net/ecp
ExternalUrl : https://outlook.example.co.za/ecp
[PS] C:>Get-OwaVirtualDirectory -Server ca2 |fl *url
Url             : {}
Exchange2003Url :
FailbackUrl     :
InternalUrl     : https://ca2.he.example.za.net/owa
ExternalUrl     : https://outlook.example.co.za/owa
[PS] C:>Get-AutodiscoverVirtualDirectory |fl *url, server
InternalUrl :
ExternalUrl :
Server      : CA1
InternalUrl : https://outlook.example.co.za/
ExternalUrl : https://outlook.example.co.za/
Server      : CA2
REALLY APPRECIATE SOME EXPERT ADVISE. Thanks.

Hi Kane,
Why did not you use cas array to load balance client connectivity?
If you create a CAS array, you can assign an virtual IP (VIP) for the CAS array FQDN (e.g CASarray.example.za.net), and then point all the Virtual Directories internal URL to CAS array fqdn;
For external, you can point outlook.example.co.za to VIP which had been assigned to CAS array.
I recommend you refer to the following article to understand CAS array:
http://technet.microsoft.com/en-us/library/ee332317(v=exchg.141).aspx#CASarray
http://blogs.technet.com/b/ucedsg/archive/2009/12/06/how-to-setup-an-exchange-2010-cas-array-to-load-balance-mapi.aspx
http://blogs.technet.com/b/exchange/archive/2012/03/23/demystifying-the-cas-array-object-part-1.aspx
Best regards,
Niko Cheng
TechNet Community Support

Files associated with user's mailbox database and reverent directory path (exchange 2010)

Hi,
I want to know all the files and other associated types of log files with particular user's mailbox database in exchange 2010 & its reverent directory path . Please suggest
Aditya Mediratta

Hi,
If you want to view the database file path and associated log file path, you can use the following command.
Get-MailboxDatabase "Mailbox Database" | fl *path
Default path is C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2010 is suddenly unmanageable

Hi --
On a SBS 2011 box running Exchange 2010 SP2, Exchange has suddenly become unmanageable. I have no idea what happened overnight to cause this. But I've been trying to get this fixed for two hours already, with no luck.
Nobody can open OWA. From anywhere. Including from the server itself. IE network diagnostics reveal that "The device or resource (whatever) is not set up to accept connections on port "https".
The Exchange Management Console won't open. I get the error "The attempt to connect to http://server/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: The WinRM client cannot process the
request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication
mechanisms supported by the server. To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the computer name as the remote destination,
specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic."
Opening an Exchange Management Shell results in the error:
>>>>>>>>>>>>>>>>>>>>>>>>
VERBOSE: Connecting to server.domain.local
[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
ooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to server.domain.local
[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
ooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to server.domain.local
[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
ooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
<<<<<<<<<<<<<<<<<<<<<<<<
I have checked and double-checked bindings, Kerberos settings, and a slew of other things. I have reset IIS and rebooted the server multiple times. I can't get past this. Everything referenced in the following articles was checked and verified to be as the
articles said they should be:
http://blogs.technet.com/b/bshukla/archive/2012/05/04/exchange-management-shell-error-500-internal-server-error.aspx
http://technet.microsoft.com/en-us/library/ff607221%28v=EXCHG.80%29.aspx
http://support.microsoft.com/kb/2028305
I installed and ran the EMTshooter script referenced in http://blogs.technet.com/b/exchange/archive/2010/12/07/resolving-winrm-errors-and-exchange-2010-management-tools-startup-failures.aspx. This it what it reported:
>>>>>>>>>>>>>>>>>>>>>>>>
Welcome to the Exchange Management Troubleshooter!
We recommend that you run the troubleshooter after making changes to
IIS to ensure that connectivity to Exchange Powershell is unaffected.
Checking IIS Service...
Checking the Exchange Install Path variable...
Checking the Powershell Virtual Directory...
Checking the Powershell vdir SSL setting...
Checking the Powershell vdir path setting...
Checking HTTP Port 80...
Checking HTTP Port 80 Host Name...
Testing for errors...
VERBOSE: Connecting to server.domain.local
[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a r
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep
    + FullyQualifiedErrorId : PSSessionOpenFailed
The Exchange Management Troubleshooter successfully completed connecting to:
server.domain.local
Failed to connect to any Exchange Server in the current site.
Problem found:
Looking for error...
These are the possible causes for this error:
1. The default http binding has been removed from the Default Web Site. Exchange Powershell needs http to be configured
so that the IP Address is "All Unassigned", the Port is "80", and the Host Name is "". A common scenario for changing t
his is if you are running multiple web sites, and attempting to set up a redirect to https://mail.company.com/owa by req
uiring SSL on the Default Web Site, and creating another web site to do the redirect back to the SSL-enabled website. Re
mote PowerShell requires port 80 to be available on the Default Web Site for all Internet Addresses. If you want to set
up an automatic redirect to /owa and redirect http requests to https, you should follow the instructions located at:
http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx
and follow the directions under the section:
"For a Configuration in Which SSL is required on the Default Web Site or on the OWA Virtual Directory in IIS 7.0."
2. The http binding on the Default Web Site has been modified, and the Hostname field configured. To correct this issue,
you need to clear out the Hostname field under the port 80 bindings on the Default Web Site.
After each error is resolved, close this window and re-run the tool to check for additional problems.
<<<<<<<<<<<<<<<<<<<<<<<<
However, the bindings on the Default Web site are correct (I've checked them multiple times).
And the server's System, Security and Application logs are devoid of anything that could even begin to explain what is going on.
And this was all working yesterday ...
I have automatic replies to modify/remove and have no way to get to them. Outlook on the PCs won't pull up Automatic Replies, claiming that the server is unavailable. On the other hand, email is coming and going fine ...
I need to get this fixed _now_. Does anybody know how to get to the bottom of this -- and what could have possibly happened to cause this in the first place?
Thanks
CL

Hi --
C:\Users\Administrator>winrm quickconfig
WinRM already is set up to receive requests on this machine.
WinRM already is set up for remote management on this machine.
C:\Users\Administrator>winrm invoke Restore winrm/Config
Restore_OUTPUT
C:\Users\Administrator>winrm get winrm/config
Config
    MaxEnvelopeSizekb = 150
    MaxTimeoutms = 60000
    MaxBatchItems = 32000
    MaxProviderRequests = 4294967295
    Client
        NetworkDelayms = 5000
        URLPrefix = wsman
        AllowUnencrypted = false
        Auth
            Basic = true
            Digest = true
            Kerberos = true
            Negotiate = true
            Certificate = true
            CredSSP = false
        DefaultPorts
            HTTP = 5985
            HTTPS = 5986
        TrustedHosts
    Service
        RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD)
        MaxConcurrentOperations = 4294967295
        MaxConcurrentOperationsPerUser = 15
        EnumerationTimeoutms = 60000
        MaxConnections = 25
        MaxPacketRetrievalTimeSeconds = 120
        AllowUnencrypted = false
        Auth
            Basic = false
            Kerberos = true
            Negotiate = true
            Certificate = false
            CredSSP = false
            CbtHardeningLevel = Relaxed
        DefaultPorts
            HTTP = 5985
            HTTPS = 5986
        IPv4Filter = *
        IPv6Filter = *
        EnableCompatibilityHttpListener = false
        EnableCompatibilityHttpsListener = false
        CertificateThumbprint
    Winrs
        AllowRemoteShellAccess = true
        IdleTimeout = 180000
        MaxConcurrentUsers = 5
        MaxShellRunTime = 2147483647
        MaxProcessesPerShell = 15
        MaxMemoryPerShellMB = 150
        MaxShellsPerUser = 5
C:\Users\Administrator>winrm enumerate winrm/config/listener
C:\Users\Administrator>netstat -aon | find ":80"
TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
TCP    0.0.0.0:808            0.0.0.0:0              LISTENING       4856
TCP    192.168.214.20:80      192.168.214.20:15979   ESTABLISHED     4
TCP    192.168.214.20:15979   192.168.214.20:80      ESTABLISHED     6336
TCP    192.168.214.20:15980   192.168.214.20:80      TIME_WAIT       0
TCP    192.168.214.20:15997   192.168.214.20:8014    SYN_SENT        8528
TCP    [::]:80                [::]:0                 LISTENING
4
TCP    [::]:808               [::]:0                 LISTENING
4856
TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80 [fe80::adee:f7f8:e6f6:1f35%13]:15926
TIME_WAIT       0
TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80 [fe80::adee:f7f8:e6f6:1f35%13]:15973
TIME_WAIT       0
TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80 [fe80::adee:f7f8:e6f6:1f35%13]:15978
TIME_WAIT       0
TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80 [fe80::adee:f7f8:e6f6:1f35%13]:15982
TIME_WAIT       0
TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80 [fe80::adee:f7f8:e6f6:1f35%13]:15984
TIME_WAIT       0
TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80 [fe80::adee:f7f8:e6f6:1f35%13]:15989
TIME_WAIT       0
TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80 [fe80::adee:f7f8:e6f6:1f35%13]:15990
TIME_WAIT       0
C:\Users\Administrator>
PID 4 is c:\Windows\system32\ntoskrnl.exe
PID 6336 is DataCollectorSvc.exe
I'm still getting all the same errors.

Virtual directory misconfigured

Exchange server path to kerbauth.dll is wrong / Powershell virtual directory is misconfigured. How to re-created virtual directory for Powershell on affected server.
Thanks for ypour replies.
Treat as urgent.

Hi,
Please run the following commands one by one to recreate PowerShell virtual directory.
Get-PowerShellVirtualDirectory -Server <AffectedServer> | Remove-PowerShellVirtualDirectory
New-PowerShellVirtualDirectory -Server <AffectedServer> -Name PowerShell
Get-PowerShellVirtualDirectory -Server <AffectedServer> | Set-PowerShellVirtualDirectory -BasicAuthentication:$false
IISReset
After PowerShell virtual directory re-creation, please check its modules in IIS and made sure that Kerberos module is native and the path to its DLL is correct.
Best Regards.

Exchange 2010 Management Console "Initialization failed" troubleshooting

This error:
The following error occurred when searching for On-Premises Exchange Server:
[server#.Domain] Connecting to the remote server failed with the following error message:
The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting help topic
I've seen errors similar to this in these forums, but I haven't had any luck with the steps used to correct other's problems. The most recent steps I've taken are:
uninstalled and reinstalled IIS, then uninstalled and reinstalled CAS, along with various other fixes to no avail.
After installing Exchange and CAS the console was working for a couple of weeks, it died with this error after two things we can remember, although various other things may have been the cause:
1. installed a lengthy list of windows updates
2. installed the URL rewrite module: http://www.iis.net/expand/URLRewrite and set it up to rewrite http://domain to https://domain/owa, this has since been reverted and uninstalled, it still doesn't work.

Thank you for Your Post
The First Error on this Blog is the error that you are facing
http://msexchangeteam.com/archive/2010/02/04/453946.aspx
Issue:
Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
Possible causes:
1. Remote PowerShell uses Kerberos to authenticate the user connecting. IIS implements this Kerberos authentication method via a native module. In IIS Manager, if you go to the PowerShell Virtual Directory and then look at the Modules, you should see Kerbauth listed as a Native Module, with the dll location pointing to C:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll. If the Kerbauth module shows up as a Managed module instead of Native, or if the Kerbauth module has been loaded on the Default Web Site level (instead of, or in addition to, the PowerShell virtual directory), you can experience this issue. To correct this, make sure that the Kerbauth module is not enabled on the Default Web Site, but is only enabled on the PowerShell virtual directory. The entry type of "Local" indicates that the Kerbauth module was enabled directly on this level, and not inherited from a parent.
2. If the WSMan module entry is missing from the global modules section of the C:\Windows\System32\Inetsrv\config\ApplicationHost.config file, as follows:
<globalModules>
<add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />
This will result in the WSMan module displaying as a Managed module on the PowerShell virtual directory.
To correct this, make sure that the WSMan module has been registered (but not enabled) at the Server level, and has been enabled on the PowerShell virtual directory.
3. If the user that is attempting to connect is not Remote PowerShell enabled. To check if a user is enabled for Remote PowerShell, you need to open the Exchange Management Shell with an account that has been enabled, and run the following query.
(Get-User <username>).RemotePowershellEnabled
This will return a True or False. If the output shows False, the user is not enabled for Remote PowerShell. To enable the user, run the following command.
Set-User <username> -RemotePowerShellEnabled $True

Branch office Exchange 2010 Role base administration control for branch site administrator

Dear sir,
   Customer has a Exchange 2010 Main and Branch office environment:
- Main office Exchange 2010 CAS x2 +HTS & Mailbox x2 (Server1,2 & Server 3,4)
  (Main office administrator:domain1\administrator) - DAG1
- Branch office Exchange 2010 CAS+HTS x2 & Mailbox with DAG x2 (Server5,6 & Server7,8
   (Branch Administrator: domain1\badmin) - DAG2
   Customer would like to know what is the role which permission should grant / delegate for ID: badmin in order to manage Exchange server 5,6,7,8 ? (with manage user account and performance in DAG2 failover & branch exchange server)
Regards,
Joe Tam

Dear Brian,
   I have try in my lab to scale down into 2 x Server in 1 AD Single Domain And Single Forest. It still have many unexpected behaviour, can you please suggest whether it is a design or bug of Exchagne 2010 SP1?
Procedure:
============================================================================
Exchange 2010 Role Delegation Problem: (Single AD, Single Site)
Environment:
Server: Windows 2008 R2 AD x1 + (CAS+HTS+Mailbox) Server x1
AD Server: AD1
Exchange2010 Server : EX2010 (with SP1) – Member Server Joined to testdomain1.net
Domain Name: testdomain1.net (NETBIOS: TESTDOMAIN1)
In AD,
Login as domain administrator: Testdomain1\administrator
1. Create an Organization Unit OU1.
2. Create User User1 under OU1
3. Delegate User1 to allow create user in OU1
Select all item in “Delegate the following common tasks:
In Exchange 2010 Server,
Login as domain administrator: Testdomain1\administrator
1. Rename existing database name to HKDB1
2. Create a new database AUDB1 in EX2010 Server:
AUDB1 Create Done.
Assign testdomain1\User1 as Exchange 2010 local administrators group.
Logoff Testdomain1\administrator and Login Testdomain1\User1
Open Exchange EMC: (Failed, because no user management roles is grant).
Logoff Testdomain1\User1, Login Testdomain1\Administrator
Open Exchange 2010 PowerShell:
Delegate User1 to allow perform recipient management in HKDB1 only:
====================================================================
New-ManagementScope "HKDBSCOPE" -DatabaseRestrictionFilter {Name -Eq 'HKDB*' }
$RoleGroup = Get-RoleGroup "Recipient Management"
New-RoleGroup "HKDBRecipientManagement" -Roles $RoleGroup.Roles -CustomConfigWriteScope "HKDBSCOPE"
Add-RoleGroupMember “HKDBRecipientMANAGEMENT” -Member User1
====================================================================
Result:
In Exchange 2010 Server, logon as domain user: Testdomain1\User1
Open Exchange Management Console: (User1 able to open EMC now)
Perform Create User User2 in OU1 with Mailbox located in HKDB1
Mailbox Creation Failed because it cannot match the Database name = HKDB*
Logoff Testdomain1\User1, Login Testdomain1\Administrator
In Exchange Management Shell, enter:
Set-ManagementScope "HKDBSCOPE" -DatabaseRestrictionFilter {Name -Like 'HKDB*' }
Logoff Testdomain1\administrator, Login Testdomain1\User1
Open Exchange Mangement Shell and Create User2 again.
Create user successfully.
Perform create User User3 in OU1 with Mailbox located in AUDB1
User3 Creation Failed because it is not meet the Database restriction of User1 – Like HKDB*
Logoff Testdomain1\User1, Login Testdomain1\Administrator
Open Exchange Management Console, create User3 in AUDB1
Create User3 in Users Container, by administrator ID.
Logoff Testdomain1\administrator, Login Testdomain1\User1
Perform mailbox remove of User2
User2 mailbox remove successfully.
Perform deletion of User3
Mailbox User3 Remove Successfully.
Why User3 is allowed to deleted mailbox which is located in by using delegated of User1?
Moreover, it found that User3 properties can also be changed by using User1. Why?
Does it mean delegation cannot handle delete operation?
In Active Directory User and Computer: User2 is deleted successfully by using User1 ID.
In Active Directory User and Computer: User3 is also deleted successfully by using User1 ID.

Exchange 2010 Powershell virtual directory recreation

Similar Messages

Maybe you are looking for