netman09
asked on
Exchange 2010 console error
I've introduced a new Windows 2008 R2 DC into a network having one 2003 DC w/Exchange 2003 installed on it. Everything was fine for a while but after a few reboots I can no longer use the Exchange 2010 management console.
I get: WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.
My intent was to migrate everyone to the new server and remove the old one. I've migrated all the FSMO roles and mailboxes but the old server is still in the picture as a DC.
I get: WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.
My intent was to migrate everyone to the new server and remove the old one. I've migrated all the FSMO roles and mailboxes but the old server is still in the picture as a DC.
ASKER
Also, I've already been through checking powershell in IIS. It may be note worthy that IUSR_NEWSERVER name doesn't exist. Just the IUSR_OLDSERVER name, but like I said, everything was working. Maybe an update applied during a reboot or something that made it stop working?
ASKER
The result of the winrm get winrm/config/winrs is
AllowRemoteShellAccess = true
IdleTimeout = 180000
MaxConcurrentUsers = 5
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 15
MaxMemoryPerShellMB = 150
MaxShellsPerUser = 5
I can't find any problems, I'm missing something simple I just know it.
AllowRemoteShellAccess = true
IdleTimeout = 180000
MaxConcurrentUsers = 5
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 15
MaxMemoryPerShellMB = 150
MaxShellsPerUser = 5
I can't find any problems, I'm missing something simple I just know it.
ASKER
In my original post I forgot to mention that the new server is where I installed the Exchange 2010 Enterprise server software and migrated the mailboxes to. The Exchange Shell asks for FQDN of the server and after typing it in doesn't connect.
shave you tried to create a new management console from MMC and Exchange snap int to it and try again
ASKER
Yes, but like I said, even the shell can't find the path. Outlook clients are working and the owa works fine. The system is sending and receiving emails but I can't manage the system. I'm sure this has to do with IIS in some way but I'm not seeing the problem. SO CONFUSED.
can you try to re-install winrm and re-install the administrative tool using the setup
ASKER
I'm not sure how to reinstall winrm. I've tried and I'm obviously not doing it right. I've tried finding it under features to no avail and also using winrm to delete the listener but I'm not doing that right cause it doesn't like the way I'm typing the address+transport.
Hi,
Does you have AVG installed on the server? If yes, then disbale it and try to open the Conolse.
Hope this works,
Shree
Does you have AVG installed on the server? If yes, then disbale it and try to open the Conolse.
Hope this works,
Shree
if the Exchange server is 2008 sp1 or sp2 then here is a link:
http://www.microsoft.com/downloads/details.aspx?FamilyId=d37e25cf-db05-4b23-a852-cdf865d81b82
or:
Server Manager -> Features -> Add Features -> Scroll down to the bottom -> Check off Windows PowerShell Integrated Scripting Enviornment (ISE) -> Install
http://www.microsoft.com/downloads/details.aspx?FamilyId=d37e25cf-db05-4b23-a852-cdf865d81b82
or:
Server Manager -> Features -> Add Features -> Scroll down to the bottom -> Check off Windows PowerShell Integrated Scripting Enviornment (ISE) -> Install
ASKER
I can get into the management shell and the management console by not using the FQDN but instead specifying the hostname of the server only. Does this help? Here is the 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;S A;GWGX;;;W D)
MaxConcurrentOperations = 4294967295
MaxConcurrentOperationsPer User = 15
EnumerationTimeoutms = 60000
MaxConnections = 25
MaxPacketRetrievalTimeSeco nds = 120
AllowUnencrypted = false
Auth
Basic = false
Kerberos = true
Negotiate = true
Certificate = false
CredSSP = false
CbtHardeningLevel = Relaxed
DefaultPorts
HTTP = 5985
HTTPS = 5986
IPv4Filter = *
IPv6Filter = *
EnableCompatibilityHttpLis tener = false
EnableCompatibilityHttpsLi stener = false
CertificateThumbprint
Winrs
AllowRemoteShellAccess = true
IdleTimeout = 180000
MaxConcurrentUsers = 5
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 15
MaxMemoryPerShellMB = 150
MaxShellsPerUser = 5
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
MaxConcurrentOperations = 4294967295
MaxConcurrentOperationsPer
EnumerationTimeoutms = 60000
MaxConnections = 25
MaxPacketRetrievalTimeSeco
AllowUnencrypted = false
Auth
Basic = false
Kerberos = true
Negotiate = true
Certificate = false
CredSSP = false
CbtHardeningLevel = Relaxed
DefaultPorts
HTTP = 5985
HTTPS = 5986
IPv4Filter = *
IPv6Filter = *
EnableCompatibilityHttpLis
EnableCompatibilityHttpsLi
CertificateThumbprint
Winrs
AllowRemoteShellAccess = true
IdleTimeout = 180000
MaxConcurrentUsers = 5
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 15
MaxMemoryPerShellMB = 150
MaxShellsPerUser = 5
ASKER
I've opened a Microsoft incident but won't here back from them for awhile. Being able to open the console helps though. Instead of listening for authentication at hostname.domain.com, it's listening only on the hostname. How do I fix this?
ASKER
This article has the exact error I'm seeing but I can't figure out how to fix it.
http://technet.microsoft.com/en-us/library/dd351136.aspx
Under "Connection Issues" - "Server Name Provided Doesn't Exist"
http://technet.microsoft.com/en-us/library/dd351136.aspx
Under "Connection Issues" - "Server Name Provided Doesn't Exist"
ASKER
Yea, I'm sure it's not a problem authenticating but addressing the server. Like I said, if instead of the FQDN (hostname.domain.com) I enter just the hostname it logs in just fine. It's like the FQDN is not associated with the WinRM config.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
i tried this solution, but didn't work
Had the same issue with Exchange 2010 on SBS 2011. Confirmed it was profile dependent by creating another admin profile -- it runs fine in alt admin profile. However, in SBS 2011, this path cannot be located (to try reset):c:\Users\Administra tor.domain name\AppDa ta\Roaming \Microsoft \Exchange\ RemotePowe rShell
Searched for it to no avail. Good news is that I can manage Exchange using the EMC in the alt. admin profile until it is figured out.
Searched for it to no avail. Good news is that I can manage Exchange using the EMC in the alt. admin profile until it is figured out.
Refer this:
http://blog.tiensivu.com/aaron/archives/1864-Exchange-2010-Beta-The-WS-Management-service-cannot-process-the-request.html
Hope this helps,
Shree