Exchange Management Shell Cannot Find Global Catalog Servers

Hello,
I have a client with a single Exchange 2013 RU2 multi role server. Exchange works fine with no issues. However, when I open EMS and try to do anything (example get-mailbox) it returns the following error. It was working up until about a
week ago.
"Could not find any available Global Catalog in forest domain.com"
I haven't tried rebooting the server yet because Exchange is running fine, it's just PowerShell is jacked up. I have even tried Remote PowerShell from another server and same results. Has anyone ever seen this?
Thanks,
John

can you check what your nslookup returns you... are you able to connect to your DNS without any error.
the above error is generally towards network connectivity issues.
guess you have two lan cards on exchange. what is the DNS on both lan cards. i guess should b same.
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Similar Messages

Exchange 2007 with Global catalog servers

exchange 2007 connects with 2 global catalog servers
when it connects GC server A, and A is down, there is user connection error at Outlook side.
any setting to allow Exchange 2007 immediately switching to GC server B without waiting?
Thanks a lot.

Hi
As per the information and details provided by you, please follow these steps: -
If you are running a version of Exchange Server that is earlier than Exchange Server 2010, use the following steps to force Outlook to identify and use the closest global
catalog server yourself.
Click
Start, and then click Run.
In the
Open box, type regedit.exe, and then click
OK.
Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider
On the
Edit menu, click Add Value, and then add the following registry value:
Value name: Closest GC
Data Type: REG_DWORD
Radix: Hexadecimal
Value Data: 0x0000000
Quit
Registry Editor.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G

When exchange Domain Controller or Global Catalog servers?

I have a few questions want to get your help.
1,which situation exchange would contact with the Domain Controller, and which situation exchange would contact with the Global Catalog servers?what's the difference?
2,for the mailbox replication service, besides moving the mailbox ,and DAD relevant operations, which situation mailbox replication service also contact with Dc?
Please click the Mark as Answer button if a post solves your problem!

Hi,
About Question 1:
For Exchange, GC is mainly for Address Book lookups. Exchange server access to the global catalog for address information.
About DC, every domain controller contains the following three directory partitions.
1. Configuration: Contains the Configuration container, which stores configuration objects for the entire forest in cn=configuration,dc= forestRootDomain.
2. Schema: Contains the Schema container, which stores class and attribute definitions for all existing and possible Active Directory objects in cn=schema,cn=configuration,dc= forestRootDomain.
3. Domain: Contains a < domain > container, which stores users, computers, groups, and other objects for a specific domain.
For example, each Exchange Server object has the attribute Boolean messageTrackingEnabled. The Exchange server processes will turn on or off message tracking depending on the value of this attribute in the directory. This is an example of configuration data.
Configuration data is stored in the Configuration partition of Active Directory, and this partition is replicated to every DC in the Forest. Therefore Exchange can potentially go to any DC to access this information.
About Question 2:
The Mailbox Replication Service is responsible for moving mailboxes, importing and exporting .pst files, and restoring disabled and soft-deleted mailboxes. All these options need to contact with DC.
Best regards,
Belinda
Belinda Ma
TechNet Community Support
Thank you so much
Please click the Mark as Answer button if a post solves your problem!

Exchange Edge clone config import in Exchange Management shell throws error "You cannot call a method on a null-valued expression"

Hi All,
During the Coexistence of Exchange 2007 to 2010 Migration..
I have create new Edge Scubscription in Edge Server 1 and Export the Edge Configuration File from Edge Server 1.
While trying to Import Edge configuration to Edge Server 2 in Exchange Management Shell, I am getting the below Error.
I have tried importing on both Exchange 2007 and 2010 Edge Servers, getting the same error.
"Importing Edge configuration information Failed.
Reason: You cannot call a method on a null-valued expression."
Please help in resolving this issue...

Also found the CloneLogFile as below : I masked my domain name as xxx for security reason..
Get-TransportServer -Identity:xxx | Set-TransportServer -AntispamAgentsEnabled:$true -ConnectivityLogEnabled:$false -ConnectivityLogMaxAge '30.00:00:00' -ConnectivityLogMaxDirectorySize '250MB' -ConnectivityLogMaxFileSize '10MB' -ConnectivityLogPath 'C:\Program
Files\Microsoft\Exchange Server\TransportRoles\Logs\Connectivity' -DelayNotificationTimeout '04:00:00' -ExternalDelayDsnEnabled:$true -ExternalDNSAdapterEnabled:$true -ExternalDNSAdapterGuid '00000000-0000-0000-0000-000000000000' -ExternalDNSProtocolOption
'Any' -ExternalDNSServers:$null -ExternalIPAddress:$null -ExternalDsnDefaultLanguage 'en-US' -ExternalDsnLanguageDetectionEnabled:$true -ExternalDsnMaxMessageAttachSize '10MB' -ExternalDsnSendHtml:$true -InternalDelayDsnEnabled:$true -InternalDNSAdapterEnabled:$true
-InternalDNSAdapterGuid '00000000-0000-0000-0000-000000000000' -InternalDNSProtocolOption 'Any' -InternalDNSServers:$null -InternalDsnDefaultLanguage 'en-US' -InternalDsnLanguageDetectionEnabled:$true -InternalDsnMaxMessageAttachSize '10MB' -InternalDsnSendHtml:$true
-MaxConcurrentMailboxDeliveries '7' -MaxConcurrentMailboxSubmissions '20' -MaxConnectionRatePerMinute '1200' -MaxOutboundConnections '1000' -MaxPerDomainOutboundConnections '20' -MessageExpirationTimeout '2.00:00:00' -MessageRetryInterval '00:01:00' -MessageTrackingLogEnabled:$true
-MessageTrackingLogMaxAge '30.00:00:00' -MessageTrackingLogMaxDirectorySize '1GB' -MessageTrackingLogMaxFileSize '10MB' -MessageTrackingLogPath 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\MessageTracking' -MessageTrackingLogSubjectLoggingEnabled:$true
-OutboundConnectionFailureRetryInterval '00:30:00' -IntraOrgConnectorProtocolLoggingLevel 'None' -PickupDirectoryMaxHeaderSize '64KB' -PickupDirectoryMaxMessagesPerMinute '100' -PickupDirectoryMaxRecipientsPerMessage '100' -PickupDirectoryPath 'C:\Program
Files\Microsoft\Exchange Server\TransportRoles\Pickup' -PipelineTracingEnabled:$false -ContentConversionTracingEnabled:$false -PipelineTracingPath 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\PipelineTracing' -PipelineTracingSenderAddress:$null
-PoisonMessageDetectionEnabled:$true -PoisonThreshold '2' -QueueMaxIdleTime '00:03:00' -ReceiveProtocolLogMaxAge '30.00:00:00' -ReceiveProtocolLogMaxDirectorySize '250MB' -ReceiveProtocolLogMaxFileSize '10MB' -ReceiveProtocolLogPath 'C:\Program Files\Microsoft\Exchange
Server\TransportRoles\Logs\ProtocolLog\SmtpReceive' -RecipientValidationCacheEnabled:$true -ReplayDirectoryPath 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\Replay' -RoutingTableLogMaxAge '7.00:00:00' -RoutingTableLogMaxDirectorySize '50MB' -RoutingTableLogPath
'C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\Routing' -SendProtocolLogMaxAge '30.00:00:00' -SendProtocolLogMaxDirectorySize '250MB' -SendProtocolLogMaxFileSize '10MB' -SendProtocolLogPath 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpSend'
-TransientFailureRetryCount '6' -TransientFailureRetryInterval '00:10:00'
New-AcceptedDomain -DomainName 'xxx' -DomainType 'Authoritative' -Name 'xxx'
Set-AcceptedDomain -DomainType 'Authoritative' -AddressBookEnabled:$true -Name 'xxx'
Importing Edge configuration information Failed.
Reason: You cannot call a method on a null-valued expression.

2013 Exchange, Can't connect to Exchange Management Shell. It cannot determine the content type of the HTTP response from the destination computer.

The following error occurs.
         Welcome to the Exchange Management Shell!
Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List
Tip of the day #0:
Did you know that the Identity parameter is a "positional parameter"? That means you can use:
Get-Mailbox "user" instead of: Get-Mailbox -Identity "user"
It's a neat usability shortcut!
VERBOSE: Connecting to mail1.dorothy.local.
New-PSSession : [mail1.dorothy.local] Connecting to remote server mail1.dorothy.local 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.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
Exception calling "GetComputerSite" with "0" argument(s): "The Specified directory object cannot be found."
At C:\Program Files\Microsoft\Exchange Server\V15\bin\ConnectFunctions.ps1:164 char:2
+     $localSite=[System.DirectoryServices.ActiveDirectory.ActiveDirectorySite]::GetC ...
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ActiveDirectoryObjectNotFoundException
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.: mail1.dorothy.local
VERBOSE: Connecting to mail1.dorothy.local.
New-PSSession : [mail1.dorothy.local] Connecting to remote server mail1.dorothy.local 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.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
Randy Cheek

Good Morning,
Log into the server with an account that has appropriate Exchange rights, not a local account.
Note: By default - Domain Admins don't have Exchange rights.
Dame Luthas, ITILv3, MCSE Messaging 2013, MCSA, MCITP
My Technical Blog: http://thelifestrategist.wordpress.com
Discipline is the Difference between Goals and Accomplishments
If this post is useful, please hit the green arrow on the left & if this is the answer hit "mark as answer"

Error connecting to the Exchange Management Shell - and no one can connect w/ Outlook or OWA

Whew - I'm not sure what's happening but everything blew up this morning when another admin rebooted the server...
I can't connect to the Exchange Management shell - I get this:
[<servername>.<domainname>.local] Connecting to remote server failed with the following error message : WS-Management cannot process the request. The operation failed because of an HTTP error. The HTTP error (12152) is: The server returned
an invalid or unrecognized response . For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
+ FullyQualifiedErrorId : PSSessionOpenFailed
And in digging around, re-running the sharepoint PSConfig appeard to be a fix for a related issue I was reading about, and since there didn't seemt to be any harm in running it again (I did find the technote and had manually ran it after SP1 was installed)
I ran it and this is an excerpt from the log:
09/08/2011 16:48:05 1 INF                      Entering function Farm.Clear
09/08/2011 16:48:05 1 INF                        Entering function CentralAdminServiceInstance.Reset
09/08/2011 16:48:05 1 INF                        Leaving function CentralAdminServiceInstance.Reset
09/08/2011 16:48:05 1 INF                      Leaving function Farm.Clear
09/08/2011 16:48:05 1 INF                    Leaving function Farm.TryIsJoinedToFarm
09/08/2011 16:48:05 1 ERR                    A failure has been encountered when trying to load the Farm
09/08/2011 16:48:05 1 INF                    Entering function StringResourceManager.GetResourceString
09/08/2011 16:48:05 1 INF                      Resource id to be retrieved is FarmIsJoinedFailureWhileUsingCommandLine for language English
(United States)
09/08/2011 16:48:05 1 INF                      Resource retrieved id FarmIsJoinedFailureWhileUsingCommandLine is Failed to detect if this
server is joined to a server farm. Possible reasons for this failure could be that you no longer have the appropriate permissions to the server farm, the database server hosting the server farm is unresponsive, the configuration database is inaccessible
or this server has been removed from the server farm. To diagnose this problem further, review the extended error information located at {0}. If this problem persists, run this wizard again to disconnect from the server farm. After disconnecting,
run the wizard again to create or connect to an existing server farm.
So I seem to have some massive permissions issues. Is there any kind of a technote or walkthrough that can step me through verifying what permissions should be where? The connect to Internet Wizard won't complete complaining it can't configure
the email and to run it again. That caused the Set Up your Internet Address wizard to not run, complaining you have to run the connect to Internet wizard.

Is there any update on the issue?
No. I gave up and rebuilt the server - this time inside of HyperV!
It's definetly a problem of some sort of a problem with IIS, that much is obvious. It's frustrating, because by not being able to get to the Exchange Management Shell it made recovery of the Exchange database VERY hard.
The rest of this will be a bit of a rant so feel free to stop reading here if you like :)
I'm pretty unhappy with the fragility of recovering an Exchange databas in general - there is a VERY narrow range of parameters to get mail back - and very many things that can prevent you from recovering. Had I suspected that there would have been
1/10th the pain in recovering mail, before I tried to connect the clients to the new exchange I would have made .PST files for everyone - which would have worked since they all had cached .OST files, even if the clients couldn't talk to Exchange due to the
aformentioned IIS problems. Anyway, it was a total nightmare, extremly frustrating and while many of my problems were probalby self-induced, the total lack of a coherant disaster recovery strategy has at least motivated me to be EXTREMLY diligent about
backups - and not just backups, but ensuring that the SBS backup is working and occasionally firing up a clone VM and doing a restore to ensure the one of two ways Exchange can be successfully backed up are indeed working.
With such an extreme dependence on IIS for client acces AND managemet of Exchange, there really, REALLY needs to be more documentation on how Exchange uses IIS, how to step through the registry and other low-level internals to troubleshoot and compare.
I must have read just about every technet article and literallly hundreds of blog entries on recovering Exchange - but the lack of information about Exchange's integration and dependancies on IIS were the most frustrating of all. Talk about putting all
your eggs in one basket and a huge single point of failure ticking time bomb!
And I think it was either SharePoint Express or an accidently applied SharePoint Express update that blew up IIS. A few days after that update got applied the server was restarted, and that's when everything went completly sideways. That's whats
even more frustrating - that so many applications are so dependant on a now essential layer is frustrating. I realize SBS is an exception to the rule - generally Exchange is installed on it's own server and this isn't a remote possiblity, but any update
(or installer) that messes with IIS really needs to check the environment it's going to go into, and if there is anything at all that could possibly cause a compatibility issue, the update should "fail open" and not install wtihout explicit confirmation
from the admin that he wants to isntall it. Then again, another admin either ran the installer or approved the SP Express update so that still may not have saved me - but if he saw an explicit warning he probably would not have just clicked through
it!
Oh well - thanks for reading if you went all the way through. I'm just glad that it's now over :)

Is there Exchange 2013 view Exchange Management Shell command similar to Exchange 2010

Hi,
Is there anything similar in Exchange 2013 (Please refer the image). In Exchange 2010 if you make any changes via Management console you could go to "View Exchange Management Shell Command Log" and see what shell command it ran in the background.
It was very handy to copy shell command from here and then run it from shell in case you need to make bulk changes rather than try to find out the shell command from scratch.
I was wondering if there is anything similar in Exchange 2013.
Thanks,
Raman

Probably in SP1...
Keep your finger cross ;)
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange Management Shell does not connect to server

Hi,
Can't connect to server with Exchange Management Shell.
Restart, IISRESET etc. does not help.
Method :
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri EXCHSERVER.CONTOSO.COM/PowerShell/ -Authentication Kerberos
Import-PSSession $Session
also does not work.
Error:
VERBOSE: Connecting to EXCHSERVER.CONTOSO.COM.
New-PSSession : [EXCHSERVER.CONTOSO.COM] Connecting to remote server EXCHSERVER.CONTOSO.COM failed with the following
error message : The WS-Management service cannot process the request. The load quota for the system has been exceeded.
Send future requests at a slower rate or raise the system quota. For more information, see the about_Remote_Troublesho
oting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108120,PSSessionOpenFailed
VERBOSE: Connecting to EXCHSERVER.CONTOSO.COM.
New-PSSession : [EXCHSERVER.CONTOSO.COM] Connecting to remote server EXCHSERVER.CONTOSO.COM failed with the following
error message : The WS-Management service cannot process the request. The load quota for the system has been exceeded.
Send future requests at a slower rate or raise the system quota. For more information, see the about_Remote_Troublesho
oting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108120,PSSessionOpenFailed

Run a normal powershell
Import the Exchange server 2010 snapin and get the current certificates
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010
PS C:\Users\Administrator> Get-ExchangeCertificate
Thumbprint Services Subject
084B2597D626C5361CF8002FADBEA83B9144143D IP.WS. CN=trapoist.com, OU=Domain Control Validated
76C7987A7A9C7F9917A6A1B208220CA768CE0D23 IP..S. CN=trapoist.com, OU=Domain Control Validated
Get-ExchangeCertificate | select *
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAcces
sRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {trapoist.com, www.trapoist.com, autodiscover.trapoist.com, IMAP.trapoist.com...}
CertificateRequest :
IisServices : {IIS://MAILTRAPOIST/W3SVC/1}
IsSelfSigned : False
KeyIdentifier : 36A0EC10B4503C5DBF51815A50F442D9404BE04E
RootCAType : ThirdParty
Services : IMAP, POP, IIS, SMTP
Status : Valid
SubjectKeyIdentifier : 36A0EC10B4503C5DBF51815A50F442D9404BE04E
PrivateKeyExportable : True
PublicKeySize : 2048
ServicesStringForm : IP.WS.
Archived : False
Extensions : {System.Security.Cryptography.Oid, System.Security.Cryptography.Oid, System.Security.Cryptograph
y.Oid, System.Security.Cryptography.Oid...}
FriendlyName : trapoist.com
IssuerName : System.Security.Cryptography.X509Certificates.X500DistinguishedName
NotAfter : 8/9/2015 4:06:40 PM (SE VENCERA EL 8 DE SEPTIEMBRE)
NotBefore : 8/5/2014 7:39:01 PM
HasPrivateKey : True
PrivateKey : System.Security.Cryptography.RSACryptoServiceProvider
PublicKey : System.Security.Cryptography.X509Certificates.PublicKey
RawData : {48, 130, 5, 128...}
SerialNumber : 27B309845C2696
SubjectName : System.Security.Cryptography.X509Certificates.X500DistinguishedName
SignatureAlgorithm : System.Security.Cryptography.Oid
Thumbprint : 084B2597D626C5361CF8002FADBEA83B9144143D
Version : 3
Handle : 485017248
Issuer : CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDad
dy.com, Inc.", L=Scottsdale, S=Arizona, C=US
Subject : CN=trapoist.com, OU=Domain Control Validated
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAcces
sRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {trapoist.com, www.trapoist.com, autodiscover.trapoist.com, mail.trapoist.com...}
CertificateRequest :
IisServices : {}
IsSelfSigned : False
KeyIdentifier : 54B2B188FA07098417B50DF52BDC0A41E44C9234
RootCAType : ThirdParty
Services : IMAP, POP, SMTP
Status : DateInvalid
SubjectKeyIdentifier : 54B2B188FA07098417B50DF52BDC0A41E44C9234
PrivateKeyExportable : True
PublicKeySize : 2048
ServicesStringForm : IP..S.
Archived : False
Extensions : {System.Security.Cryptography.Oid, System.Security.Cryptography.Oid, System.Security.Cryptograph
y.Oid, System.Security.Cryptography.Oid...}
FriendlyName : trapoist.com
IssuerName : System.Security.Cryptography.X509Certificates.X500DistinguishedName
NotAfter : 8/9/2014 4:06:40 PM
NotBefore : 8/12/2013 2:29:54 PM
HasPrivateKey : True
PrivateKey : System.Security.Cryptography.RSACryptoServiceProvider
PublicKey : System.Security.Cryptography.X509Certificates.PublicKey
RawData : {48, 130, 5, 161...}
SerialNumber : 042D71441FC05E
SubjectName : System.Security.Cryptography.X509Certificates.X500DistinguishedName
SignatureAlgorithm : System.Security.Cryptography.Oid
Thumbprint : 76C7987A7A9C7F9917A6A1B208220CA768CE0D23
Version : 3
Handle : 485016480
Issuer : SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godadd
y.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US
Subject : CN=trapoist.com, OU=Domain Control Validated
Renew the expired selfsigned certificate
PS C:\Users\Administrator> Get-ExchangeCertificate -Thumbprint '76C7987A7A9C7F9917A6A1B208220CA768CE0D23' | New-ExchangeCertificate
Confirm
Overwrite the existing default SMTP certificate?
Current certificate: '76C7987A7A9C7F9917A6A1B208220CA768CE0D23' (expires 8/9/2014 4:06:40 PM)
Replace it with certificate: 'C3FBFA049FE6AC1806B950EB7A7AF8286EE04880' (expires 4/13/2020 12:56:34 PM)
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): Y
Thumbprint
Services   Subject
C3FBFA049FE6AC1806B950EB7A7AF8286EE04880 IP..S.     OU=Domain Control Validated, CN=trapoist.com
PS C:\Users\Administrator> Get-ExchangeCertificate
Thumbprint                                Services   Subject
C3FBFA049FE6AC1806B950EB7A7AF8286EE04880 IP..S.     OU=Domain Control Validated, CN=trapoist.com
084B2597D626C5361CF8002FADBEA83B9144143D IP.WS.     CN=trapoist.com, OU=Domain Control Validated
76C7987A7A9C7F9917A6A1B208220CA768CE0D23 IP..S.     CN=trapoist.com, OU=Domain Control Validated
#DELETE THE OLD CERTIFICATE (EXPIRED)
PS C:\Users\Administrator> Remove-ExchangeCertificate -Thumbprint 76C7987A7A9C7F9917A6A1B208220CA768CE0D23
Confirm
Are you sure you want to perform this action?
Remove certificate with thumbprint 76C7987A7A9C7F9917A6A1B208220CA768CE0D23 from the computer's certificate store?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): Y
PS C:\Users\Administrator> Get-ExchangeCertificate
Thumbprint                                Services   Subject
C3FBFA049FE6AC1806B950EB7A7AF8286EE04880 IP..S.     OU=Domain Control Validated, CN=trapoist.com
084B2597D626C5361CF8002FADBEA83B9144143D IP.WS.     CN=trapoist.com, OU=Domain Control Validated
#CALLING CMD TO RESET THE IIS.
PS C:\Users\Administrator> cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
#RESET EL IIS
C:\Users\Administrator>iisreset
Attempting stop...
Internet services successfully stopped
Attempting start...
Internet services successfully restarted
Done

Unable to connect to local Exchange 2013 server when opening Exchange Management shell

Hi Everyone
Yesterday evenything was working fine, and then this morning, I`m unable to establish a connection with the Exchange shell. I receive the following errors. Any help is appreciated.
         Welcome to the Exchange Management Shell!
Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List
Tip of the day #55:
Want to view the mounted status of all mailbox databases? Type:
Get-MailboxDatabase -Status | Format-Table Name, Server, Mounted
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
VERBOSE: Connecting to .
New-PSSession : Cannot bind parameter 'ConnectionUri'. Cannot convert value
"http:///powershell?serializationLevel=Full;ExchClientVer=15.0.516.32;clientApplication=ManagementShell;TargetServer="
to type "System.Uri". Error: "Invalid URI: The hostname could not be parsed."
At line:1 char:30
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+                              ~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [New-PSSession], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.NewPSSessionCommand
[PS] C:\Windows\system32>
Ernie Prescott
Updated information.
I can succussfully connect to the exchange powershell from a remote computer, using this method.
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
http://<FQDN of Exchange 2013 Client Access server>/PowerShell/ -Authentication Kerberos
Import-PSSession $Session
So the problem is localised on the server.
Regards

Hi
Try the steps for Error 1 on this link
http://www.petenetlive.com/KB/Article/0000477.htm
Hope it will help
Cheers
If you have any feedback on our support, please click
here
Zi Feng
TechNet Community Support

Recovery data using Exchange Management Shell From Recovery Database

Recently Some of our employees had been requesting a restore of some deleted emails from earlier in the year. Through our Backup Exec 2012 the recovery of the emails were not working. After 2 weeks on the phone with Symantec we determined that theyre Granular
Recovery Technology was not functioning properly for whatever reasons. As a last resort we recovered the backup set to a recovery database and now need to use the management shell in Exchange in order to recover the emails. I am having trouble with the
syntax and wanted to see if anyone out there could help me with the necessary commands in order to recover emails. forgive me if i have left out any required information. i am still a student trying to learn

If you are interested in 3rd party products check out Lucid8's DigiScope
http://www.lucid8.com/product/digiscope.asp
which will allow you to open any offline Exchange Database within a familiar Outlook type GUI. Once opened you can Browse, Search, Export Mailboxes, Folders and Individual Items to PST & MSG or Recover data directly to any Production Exchange
server or mailbox.
Regarding the RDB commands, here is a good article
http://technet.microsoft.com/en-us/library/ee332351.aspx and also here are a couple of Examples
NOTE: The examples below assume that you have recovered the DB in question to the RDB and that a copy of the mailbox belonging to John_Doe is within the Recovery Database.
A: The command below will recover the mailbox called John_Doe from the Recovery Database called
RecoveryDatabase1 to the John_Doe mailbox in the live database. NOTE: This method relies on the original mailbox still being intact on the Production Server.
Use the Exchange Management Shell and run the following command:
Restore-Mailbox -Identity John_Doe -Recovery Database RecoveryDatabase1
B: You can also recover the John_Doe mailbox from the Recovery Database and place it into
a folder called "John_Doe Recovery" within a mailbox called BobTheManager.
Use the Exchange Management Shell and run the following command:
Restore-Mailbox -Identity BobTheManager -RecoveryDatabase RecoveryDatabase1 -RecoveryMailbox John_Doe -TargetFolder “John_Doe Recovery"
C: There is also the ability to search the mailbox content for keywords. In this example we
search for any messages containing the word “SecretStuff” and restore those items to a folder called “John_Doe recovery with SuperSecret text” within a mailbox called JaneSupervisor.
Use the Exchange Management Shell and run the following command:
Restore-Mailbox -Identity JaneSupervisor -RecoveryDatabase RecoveryDatabase1 -RecoveryMailbox John_Doe -SubjectKeywords "SecretStuff"
–TargetFolder “John_Doe recovery with SecretStuff"
Troy Werelius
www.Lucid8.com
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers with Lucid8's DigiScope

Export Public Folder contacts to CSV File using Exchange management Shell

Hi All
Is there a command i can run in the exchange management shell to export all public folder contacts (which are in many sub folders) to a CSV file?
Any help on this appreciated.
Ben Weinberg
Prime-Networks
www.prime-networks.co.uk
Please post the resolution to your issue so that everyone can benefit
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello Ben,
Per my knowledge, you cannot use Exchange Management Shell to export the contacts in public folder to csv file.
If you want to export contacts in public folder to a csv file, you can follow this way to do that:
Open Outlook and create a Temp Contact Folder
Move all the contacts to the Temp Contact Folder
Use Outlook export contacts to csv file .
Thanks,
Evan Liu
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
[email protected]

SBS2011: Starting Exchange Management shell failed with the following Error 7BF3678A-829B-4F11-884C-4D 49060D84E6

SBS2011: Starting Exchange Management shell failed with the following Error 7BF3678A-829B-4F11-884C-4D 49060D84E6
This is not a REMOTE Exchange 2010 server, I'm launching it from the SBS2011 Console with the Domain Admin.
It looks like a permissions error, because when I use "RUN AS ADMINISTRATOR" on the exchange management tool, it launches with no errors and no issues...
I searched and I couldn't find anything that fits this exact error.
Thanks
Russ

Hi,
Any update?
Just checking in to see if the suggestions were helpful. Please let us know if you would like further assistance.
Best Regards,
Andy Qi
TechNet
Subscriber Support
If you are TechNet
Subscription user and have any feedback on our support quality, please send your feedbackhere.
Andy Qi
TechNet Community Support

How to: Get a list of mail users by using the Exchange Management Shell

Hello every one, quick question: When I run this code below for VB, how will I see the results of the program? Is there anyway I can make the results appear in a message box?
Function GetUsersUsingBasicAuth( _
    ByVal LiveIDConnectionUri
As String, ByVal ScehmaUri
As String, _
    ByVal Credentials
As PSCredential, ByVal
Count As Integer)
As Collection(Of PSObject)
    Dim ConnectionInfo
As WSManConnectionInfo = _
        New WSManConnectionInfo(New Uri(LiveIDConnectionUri), ScehmaUri, Credentials)
    ConnectionInfo.AuthenticationMechanism = AuthenticationMechanism.Basic
    Dim RemoteRunspace
As Runspace
    RemoteRunspace = RunspaceFactory.CreateRunspace(ConnectionInfo)
    Return GetUserInformation(Count, RemoteRunspace)
End Function
Function GetUserInformation(ByVal
Count As
Integer, ByVal RemoteRunspace
As Runspace) As Collection(Of PSObject)
    Dim RemotePowerShell
As PowerShell = PowerShell.Create
    RemotePowerShell.AddCommand("Get-Users")
    RemotePowerShell.AddParameter("ResultSize",
Count)
    ' Open the remote runspace on the server.
    RemoteRunspace.Open()
    ' Associate the runspace with the Exchange Management Shell.
    RemotePowerShell.Runspace = RemoteRunspace
    ' Invoke the Exchange Management Shell to run the command.
    Return RemotePowerShell.Invoke
End Function

All you need to do is enumerate through the Collection returned eg
Dim commandResults As Collection(Of PSObject)
commandResults = RemotePowerShell.Invoke()
For Each obj As PSObject In commandResults
MessageBox.Show(obj.Properties("DisplayName").Value.ToString())
Next
Cheers
Glen

Is it possible to install Exchange Management Shell on a workstation to manage my Exchange 2013 server?

I don't want to log into my Exchange 2013 every time when I need the Exchange Management Shell. Is that possible I can just install it on my workstation and then remote access to it? Thanks.
Lawrence Fung

Correct - it is in the article Amy references, but is in the bulleted section at the top
The computer you install the management tools on must have a supported operating system (such as Windows Server 2012 or Windows 8), have enough disk space, be a member of an Active Directory domain, and satisfy other requirements. For information about system
requirements, see
Exchange 2013 System Requirements.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

After fresh installation of exchange 2013 I am not seeing Exchange Management shell EMS and EAC is redirecting to OWA

I am trying to upgrade my Exchange 2010 environment to exchange 2013. I was able to install exchange 2013 on a VM running windows 2012 R2 without any errors, however after installation I am not able to login to Exchange admin center as it keeps redirecting
to OWA and I am not seeing Exchange management shell.

Hi,
What’s the version of your Exchange 2013 Server. Try updating it to the latest version first.
If you were using an account which is still on the Exchange 2010 MBX server, this could be an issue. Try creating a new admin account on the Exchange 2013 and check if the issue still happens
to it.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange Management Shell Cannot Find Global Catalog Servers

Similar Messages

Maybe you are looking for