Exchange 2013 management shell error

The problem am facing is that when I opened the Exchange management shell on my Exchange 2013 server locally it would fail to connect.The following error is receiving with Administrator account.I add another account in Organization
Management Permission it connect successfully.
following is error
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.: mail.abc.com
VERBOSE: Connecting to mail.*.*.
New-PSSession : [mail.abc.com] Connecting to remote server mail.abc.com failed with the following error message :
WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the
computer mail.abc.com. Verify that the computer exists on the network and that the name provided is spelled
correctly. 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 : NetworkPathNotFound,PSSessionOpenFailed
[PS] C:\Windows\system32>

Hi wert
Thank you for your question.
We could run Set U to make sure the logon user is domain administrator, because we use another account logon without any problems. We could check if some permissions are missing for administrator.
We could refer to the following steps to delete administrator profile to check if the issue persist:
Open up "Control Panel | System and Security | System"
In the dialog click on "Advanced system settings" (requires Admin rights)
The "System Properties" dialog will be displayed
Make sure you are in the "Advanced" register
In the "User Profiles" section click on "Settings"
The "User Profiles" dialog is displayed
Select administrator account and Delete it.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Similar Messages

Connect to Exchange 2007 Mailboxes with Exchange 2013 Management shell

Hello,
I was wondering if it is possible to use the Exchange 2013 Management Shell with the older version of Exchange 2007. When I run the console now it give me an error saying no exchange servers are available in the Active Directory site. When I use Exchange
management shell for 2007 the errors do not appear. Wondering if the management shell is backwards compatible.
Thanks,

No. your management shell MUST be the same roll-up version of exchange. I have applied updates and learned the hard way to block all updates that go beyond the server version you are
running.
http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollup-bui...
To this end, you can use the same installation media that was used to install your Exchange server "Provided you are hosting your own", just install the management console instead of the whole thing,

Exchange 2013 Management Shell - By Subject

Does anyone know a EMS command to search by subject as I cant do it from the Exchange Admin Center

Hi,
Please try the following command:
Get-ExchangeServer | Get-MessageTrackingLog -MessageSubject "test" -Start "12/12/2013 8:00AM" -End "12/19/2013 10:00AM"
In addition, the following articles for your reference:
Search Message Tracking Logs
Get-MessageTrackingLog
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 Management Tools Install Error on Win8

Hello,
I'm having some trouble installing the management tools for Exchange 2013 on Windows 8. While going through the install if I leave "Automatically install Windows Server roles and features that are required to install Exchange Server" check I get
this error...
Error:
The target of the specified cmdlet cannot be a Windows client-based operating system.
If I uncheck that option and just check the Management Tools option, the error message changes to...
Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Any help on resolving this so I can move on with the installation would be appreciated.
Thanks.

Hi,
To install the Exchange 2013 Management Tools, there are many prerequisites we need to understand before installation. And even
we must manually install some required software.
Here are some references that may be helpful to you:
Install the Exchange 2013 Management Tools
http://technet.microsoft.com/en-us/library/bb232090(v=exchg.150).aspx
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 management tools installation on windows 2012 standard edition gives error.

Exchange 2013 management tools installation on windows 2012 standard edition gives following error.
Does anyone observed this issue ?
Error:
The Exchange management tools are supported on servers running Windows Server 2012 and Windows Server 2008 R2 SP1 or later, and also on Windows 8 and Windows 7 client computers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersionForAdminTools.aspx
My Test lab is having
Exchange 2013 installed (xyz.local) domain and working fine.
Now i am installing Exchange Management tools on server which is member of (xyz.local) Domain (base OS : Windows 2012 standard edition : Windows updated)
Best Regards
sameer Prabhune

Hi Sprabhune,
It should work.
Did you install the tool by GUI or cmd?
Please select "Automatically install Windows Server roles and features that are required to install Exchange Server" to have the Setup wizard install required Windows prerequisites.
If possible, please try to install the tool on Windows 7/8 client to test.
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354.aspx
Frank Wang
TechNet Community Support

Forcefully delete user's "Deleted Items" from Exchange 2010 Management shell ?

After migration from Exchange 2003 to 2010 my organization's some user can't delete items from their deleted items folder, it generate a error message so how can I forcefully delete user's deleted items from their "Deleted Items folder" from
Exchange 2010 Management shell ? Thanks
Babu

Hi Babu ,
Based on my knowledge i have given some suggestions please have a look in to it.
1.We cannot use the search-mailbox command specifically for any folder in the mailbox.But we can use it for a whole mailbox.Below is the command which will copy the entire contents of the mailbox to the target folder called as "backup" .
Search-Mailbox -Identity "problematic mailbox name" -TargetMailbox "test mailbox" -TargetFolder "backup" -LogLevel Full -deletecontent
Note : Before executing the above command , please execute the below.
New-ManagementRoleAssignment -Name "Import Export_Enterprise Support" -SecurityGroup "Enterprise Support" -Role "Mailbox Import Export"
Once the above command is executed then you need to add your admin account to the security group "Enterprise Support" and then use the Search-Mailbox command to copy the entire items to the target mailbox and also it will delete all the copied
items from the original mailbox.
2.Another one option is to use the MFCMAPI tool to force delete the items on the deleted items folder.
Most importantly before doing all the above , please share me the error message what your users are facing while deleting the items from deleted items folder.
Thanks & Regards S.Nithyanandham

Exchange 2013 Public Folder Error

When I try to create a Public Folder in Exchange Admin Center for Exchange Standard 2013 I get an error that says: "The process failed to get the correct properties". If I create the Public Folder from shell "New-PublicFolder -Name
"Bldg 1 & 2" -Path "\Projects\10000 to 10099"", when I browse to it from Admin Center I receive the same error.
If I try to edit the properties using Admin Center I get a popup that says "error - The process failed to get the correct properties - Click here for help..."
I have attempted this as "administrator" with membership in the following groups:
Schema Admins, Organization Management, Group Policy Creator Owners, Exchange Services, Exchange Domain Servers, Enterprise Admins, Domain Admins, Administrators.

Hi,
Did we migrate to Exchange 2013 from legacy?
We cannot starting recreating Public Folders on Exchange Server 2013 until all users have been migrated to Exchange Server 2013. For how to migrate from legacy Public Folders to Exchange Server 2013 Public Folders, see
Migrate Public Folders to Exchange 2013 From Previous Versions.
Would you like to collect event logs for the further troubleshooting?
Please contact me if there is any problem.
Thanks
Mavis
Mavis Huang
TechNet Community Support
Hi Mavis,
Yes, this was an upgrade, but all previous versions of Exchange have been uninstalled.
I'd be more then happy to send any log files in, but I'd need assistance knowing which ones you'd require.
Thanks,
Peter

Exchange 2013 SP1 Installation Errors I Cannot Resolve

Good Afternoon All -
Note: I updated this post an hour after posting. Still no solution, but please see updated info at end of this post)
I'm trying to introduce Exchange into an existing, small environment. The server I'm trying to install it onto is an SBS 2011 server (single server.) Even though SBS comes with Exchange, I found out that it's installation was corrupted and someone
had attempted to uninstall it before. Yes, it's being installed onto a server with a DC. I considered creating a Hyper-V VM on the server for Exchange, but thought it may be better to try to install directly onto server instead.
Before I started, I made sure all Exchange data had been removed. I checked for and deleted (if present) all Exchange-related objects in ADSI, ADU&C, files, and registry entries.
When I try to install Exchange 2013 SP1, I get the below errors. I know that some are easily resolved by installing pre-requisites - however - others aren't - especially the pending reboot one. I've restarted the server many times when making
changes or applying various updates and still get flagged to restart during installation. I've tried the SBS 2011 repair disc as well, but had many issues with it. In all honesty, the whole server needs to be wiped and re-installed, but
cannot do at this point.
Besides the errors below, I've zipped up the ExchangeSetupLogs folder and placed them in the link below. Also below are system specs. The only edit I made in them is a find/replace for server and domain name.
ExchangeSetupLogs Folder
System Specs
Xeon E31270 3.4Ghz
16gb RAM
Windows Server 2011 SBS x64 (Domain Controller Role Installed & Used)
C:\ - RAID 1 = 500gb
D:\ - SATA HDD = 320gb
E:\ - SATA HDD = 320GB
Should I perhaps try to install to a VM on the server or think that would use too many unnecessary resources?
Any help would be appreciated - Thanks!
Error:
This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://go.microsoft.com/fwlink/?LinkId=262359).
Without this update, the Outlook Anywhere feature may not work reliably.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then
run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
The Windows component RSAT-Clustering isn't installed on this computer and needs to be installed before Exchange Setup can begin.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringInstalled.aspx
Error:
This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from
http://go.microsoft.com/fwlink/?LinkId=260990.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
Error:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Ben K.
UPDATE
I just tried fixing a few things and tried again. Still no luck. Below is what I changed as well as the errors received. Only option was Retry. Can I just not install it onto this environment?
What I Changed
Installed Unified Comm Managed API 4.0 (Required Uninstalling Speech Analysis app before it would install)
Installed KB2619234 for Outlook Anywhere
Installed 12 updates - Server fully patched
Exchange Setup Errors
Error:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Thanks Guys -

Hi,
Agree. Windows Server 2011 SBS x64 can be the problem.
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 2007 Management shell issue: "There are multiple objects matching the identity "servername" Please specify a unique value"

I thought this would be an easy answer to an issue I'm facing, but there's a problem executing the solution.
I'm running Exchange 2007 in a clustered SCC configuration. The clustered resource is called "DENBURYMAIL." I want to give my account full mailbox access rights to all the mailboxes in this resource/database.
I believe I found the solution to this at
http://technet.microsoft.com/en-us/library/bb310792%28EXCHG.80%29.aspx (about halfway down the page) the instructions read as follows:
==============================
Q: I have a third-party messaging application that requires full access to each user's mailbox. With Exchange Server 5.5, we grant a special account the Service Account Admin permissions, and then tell the application to use this account. How
can I achieve similar functionality in Exchange 2007?
A: Exchange 2007 security works differently from that of Exchange Server 5.5. In fact, Exchange 2007 does not use a site service account. Instead, all services start as the local computer account.
If your logon account is the Administrator account, a member of the root Domain Administrators, a member of the Enterprise Administrators groups, or a member of the Exchange Organization Administrators role, you are explicitly denied access to all mailboxes
that are not your mailbox, even if you have full administrative rights over the Exchange system. All Exchange 2007 administrative tasks can be performed without having to grant an administrator sufficient rights to read other people's mail.
You can achieve the results that you want in the following ways, but do so only in accordance with your organization's security and privacy policies:
In the Exchange Management Shell, use the following command to allow access to all mailboxes on a given mailbox store:
Add-ADPermission -identity "mailbox database" -user "serviceaccount" -ExtendedRights Receive-As
=============================
But when I run the command (Add-ADPermission -identity "denburymail" -user "matthew.fazio" -ExtendedRights Receive-As) I get an error telling me that "There are multiple objects matching the identity "DENBURYMAIL." Please Specify a unique value."
I'm not sure what's causing this-- why are there "multiple objects?" Is this a problem due to operating in a clustered environment?
Any assistance would be appreciated!

It may not be specific enough for the command to understand you.
Try this:
Get-MailboxDatabase -Server <servername> | Add-ADPermission -user "matthew.fazio" -ExtendedRights Receive-As

Exchange 2013 Readiness Check Error

I have been trying to install Exchange 2013 for a while now and have continued to run into the same error during the readiness check. The readiness check stalls at 40% completed and I receive the following error:
Error:
The following error was generated when "$error.Clear();
if (Get-Service MSDTC*|?{$_.Name -eq 'MSDTC'})
Set-Service MSDTC -StartupType Automatic
Start-SetupService -ServiceName MSDTC
"was run:"The task failed because a Win32 error occurred: "Access is denied". Could not open the service "MSDTC".".
I have tried to install this both onto Windows Server 2008 R2 as well as Windows Server 2012. I have installed all of the prerequisites as noted in the Microsoft documentation. I have tried to install this as the first Exchange server in a brand
new AD environment as well as trying to install it into an AD environment where I had already installed Exchange Server 2010 with SP3. I always receive the same error message during the readiness check when it stalls at 40%.
Any help here would be very much appreciated.
Thank you.

Ok, I have figured out what was causing the problem.
It appears to be something with the order that prerequisites are installed prior to installing Exchange 2013.
I had previously following the steps listed in the following page:
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx.
I was following the section for installing Windows Server 2012 prerequisites for combined Mailbox and Client Access server roles.
I installed the required Windows components using the PowerShell script and then installed Unified Communications Managed API 4.0, Office 2010 Filter Pack, and finally Office 2010 Filter Pack SP1.
After doing this and applying updates, I tried to install Exchange 2013 CU1 and received the error that I mentioned in my initial post.
I have been able to duplicate this issue when installing Exchange 2013 CU1 into a vanilla environment with Windows Server 2012 as the AD server and Exchange 2013 onto a Windows Server 2012 box.
I also had the issue when trying to install into a coexistence environment with AD being on Server 2008 R2 and another 2008 R2 server hosting Exchange 2010 with SP3.
I decided to change the order of the prerequisite installs and after doing so, I was able to install Exchange 2013 CU1 successfully.
Here are the steps that I went through to successfully install Exchange 2013 CU1.
Installed Unified Communications Managed API 4.0
Installed Office 2010 Filter Pack
Installed Office 2010 Filter Pack SP1
Ran Powershell script to install all of the required components (the Technet article says to do this first)
Applied all outstanding updates from Microsoft Update
Installed Exchange 2013 Cumulative Update 1
By following the numbered procedure that I laid out above, I was able to successfully install Exchange 2013 CU1 into both of the lab environments that I described above without any issue.
There was a suggestion that I might have bad media.
I used the same media that I tried originally using my new procedure and it worked fine so it was not the media.
I hope this helps someone out.
Thanks for everyone’s help.

Exchange 2013 EAC shows "error Sorry, your request couldn't be completed. Try deleting the cookies from your browser, and then sign in again. If the problem continues, contact your helpdesk."

Hi,
My Exchange 2013 Hybrid environment is at CU5 level. Multiple administrators have started experiencing the error message
"error
Sorry, your request couldn't be completed. Try deleting the cookies from your browser, and then sign in again. If the problem continues, contact your helpdesk."
It only started two weeks ago and did not coincide with any infrastructure changes. The message occurs when clicking anything on the EAC GUI and it eventually allows you to perform the operation but only after the message
pops up a few times.
I have tried clearing the browser cookies, history, etc. Note that using the Office 365 EAC does not yield the same messages and it only happens in IE (IE 11).
Thanks.

Hi,
From your description, please make sure that the "Require SSL" is checked in IIS Manager -> Sites -> Exchange Back End -> ECP -> SSL Settings.
What's more, ensure that EAC site is added to the “Compatibility Mode”.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Installing Exchange 2013 management tools

I am unable to install Exchange Management Tools on other server in network. I am getting error when trying to run unattended setup "exchange server.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI
package is 'Error reading from file: C:\Users\backup-admin\Downloads\Exchange2013\RemoteScripts\ConsoleInitialize.ps1. Verify that the file exists and that you can access it". Also tried to run the setup.exe, but this option not highlighting
"Management Tools" option to select.
Mohammed Qamaruddin

Hi,
Please try the following cmdlet to solve this issue.
set-executionpolicy unrestricted
If this doesn’t work, please try to copy the
ConsoleInitialize.ps1 from a working server to this server then reinstall Exchange management Tool.
If this still doesn’t work, we should consider to re-download Exchange Server 2013 Management Pack from this
site, then try to install.
Related document:
https://technet.microsoft.com/en-us/library/bb232090%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Best Regards.

Exchange 2013 CU6 Update Error /PrepareAD

setup /PrepareAD /IAcceptExchangeServerLicenseTerms -- Fails
I have copied this whole folder up to the Schema FSMO role holder and and the forestprep and the domainprep and the /prepareAD will not run. I have included entries from the ExchangeSetuplog below. I only changed the Domain Name and the exchange
organization for security reasons.
Current Setup.
Originally installed Exchange 2013 SP1 on windows 2012r2 via an ISO. This server only had Exchange 2013 installed was not an upgrade. Our previous version of Exchange that was running on a different server was Exchange 2007. This server
is no longer apart of the Exchange organization.
[11/14/2014 22:00:39.0848] [1] Executing:
   install-AdministrativeGroup -DomainController $RoleDomainController
[11/14/2014 22:00:39.0864] [2] Active Directory session settings for 'Install-AdministrativeGroup' are: View Entire Forest: 'True', Configuration Domain Controller: 'DomainController', Preferred Global Catalog: 'DomainController', Preferred Domain Controllers:
'{ DomainController }'
[11/14/2014 22:00:39.0864] [2] User specified parameters: -DomainController:'DomainController'
[11/14/2014 22:00:39.0864] [2] Beginning processing install-AdministrativeGroup
[11/14/2014 22:00:39.0895] [2] Processing object "Exchange Administrative Group (FYDIBOHF23SPDLT)".
[11/14/2014 22:00:39.0926] [2] The properties changed on the object 'Exchange Administrative Group (FYDIBOHF23SPDLT)' (CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local)
are: "{ }".
[11/14/2014 22:00:39.0926] [2] Saving object "Exchange Administrative Group (FYDIBOHF23SPDLT)" of type "AdministrativeGroup" and state "Unchanged".
[11/14/2014 22:00:39.0926] [2] Previous operation run on domain controller 'DomainController'.
[11/14/2014 22:00:39.0942] [2] Reading new object "Exchange Administrative Group (FYDIBOHF23SPDLT)" of type "AdministrativeGroup".
[11/14/2014 22:00:39.0942] [2] Previous operation run on domain controller 'DomainController'.
[11/14/2014 22:00:40.0036] [2] [ERROR] Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'
already exists.
[11/14/2014 22:00:40.0036] [2] [ERROR] The object exists.
[11/14/2014 22:00:40.0083] [2] Ending processing install-AdministrativeGroup
[11/14/2014 22:00:40.0083] [1] The following 1 error(s) occurred during task execution:
[11/14/2014 22:00:40.0083] [1] 0. ErrorRecord: Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'
already exists.
[11/14/2014 22:00:40.0083] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException: Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local' already exists. ---> System.DirectoryServices.Protocols.DirectoryOperationException: The object exists.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.Deployment.InstallAdministrativeGroup.InstallConfigurationObject[TObject](ADObjectId id, Boolean force, TObject instance)
   at Microsoft.Exchange.Management.Deployment.InstallAdministrativeGroup.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[11/14/2014 22:00:40.0098] [1] [ERROR] The following error was generated when "$error.Clear();
   install-AdministrativeGroup -DomainController $RoleDomainController
" was run: "Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException: Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=local' already exists. ---> System.DirectoryServices.Protocols.DirectoryOperationException: The object exists.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.Deployment.InstallAdministrativeGroup.InstallConfigurationObject[TObject](ADObjectId id, Boolean force, TObject instance)
   at Microsoft.Exchange.Management.Deployment.InstallAdministrativeGroup.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[11/14/2014 22:00:40.0098] [1] [ERROR] Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'
already exists.
[11/14/2014 22:00:40.0098] [1] [ERROR] The object exists.
[11/14/2014 22:00:40.0098] [1] [ERROR-REFERENCE] Id=CommonGlobalConfig___48aad7b8f00942afbc699677d60bb3fe Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/14/2014 22:00:40.0098] [1] Setup is stopping now because of one or more critical errors.
[11/14/2014 22:00:40.0098] [1] Finished executing component tasks.
[11/14/2014 22:00:40.0130] [1] Ending processing Install-ExchangeOrganization
[11/14/2014 22:00:40.0130] [0] CurrentResult console.ProcessRunInternal:198: 1
[11/14/2014 22:00:40.0145] [0] CurrentResult launcherbase.maincore:90: 1
[11/14/2014 22:00:40.0145] [0] CurrentResult console.startmain:52: 1
[11/14/2014 22:00:40.0145] [0] CurrentResult SetupLauncherHelper.loadassembly:452: 1
[11/14/2014 22:00:40.0145] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[11/14/2014 22:00:40.0145] [0] CurrentResult main.run:235: 1
[11/14/2014 22:00:40.0145] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[11/14/2014 22:00:40.0145] [0] CurrentResult setupbase.maincore:396: 1
[11/14/2014 22:00:40.0145] [0] End of Setup

Hi Ryan,
From the exchange setup log information, we can find the following error :
Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local' already exists
I recommend you refer to the following article to resolve the issue :
http://www.expta.com/2013/04/active-directory-operation-failed.html
This happens when the Public Folder tree object has been manually deleted from Active Directory using a tool such as ADSI Edit. In some organizations it becomes impossible to remove Public Folders properly from a legacy Exchange org and admins resort to
using brute force to remove them. However, there are lingering attributes in AD that are still pointing to the deleted PFTree, which causes CU1 setup to fail.
Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. And the changes made in the above blog is not supported officially
by Microsoft.
Best regards,
Niko Cheng
TechNet Community Support

Exchange 2013 SP1 prerequ errors

Current installation. 4 Exchange 2013 machines on Server 2008 R2 platform (VM with Hyper-V), all have CAS and mailbox role installed. DAG across all for servers. 2 servers
reside in main datacenter and 2 on a DR site.
The Exchange installation is at CU 2 and working.<o:p></o:p>
We have 2 domain controllers in the main datacenter (win 2008 R2) and 2 domain controllers in the DR site (Win 2012 R2).<o:p></o:p>
DCDIAG checks out fine on all. Network is fine for all.
Running SP1 installation on the Exchange servers in the DR site results in prerequisites in a bunch of errors which all stem from one root issue: <o:p></o:p>
Error:
Either Active Directory doesn't exist, or it can't be contacted.<o:p></o:p>
Running the same on the main site (DC= Win 2008 R2) completes prereq for SP1 with no errors.
So the difference is that the 2 Exchange servers on the DR site have Win 2012 R2 for their domain controllers and fail.<o:p></o:p>
Any advise?<o:p></o:p>
Gerhard Waterkamp ACSLA Inc.

No, I am not done.
The situation is that on the DR site SP1 on 2 Exchange 2013 servers (on 2008 R2) using Windows 2012 R2 Domain controllers does not install.
Error messages: ( a whole bunch more, but all related to this)
Error:
Either Active Directory doesn't exist, or it can't be contacted.
It is not resolved but still open.
Gerhard Waterkamp ACSLA Inc.

Lync 2013 to Exchange 2013 Oauth problem - Error:[OAuthTokenBuilder:GetAppToken] unable to continue building token; no locally configured issuer

Hi,
I am having a problem getting OAuth to work from Exchange 2013 to Lync 2013.
I have read and following the instructions online and cannot see what I am doing wrong.
On the Exchange 2013 server, I get the following error when I run:
Test-OAuthConnectivity -Service EWS -TargetUri
https://exchserver2.domainname.local/ews/ -Mailbox "Jack"
RunspaceId : 920118a3-6ab2-45dc-9b68-de68133de95e
Task : Checking EWS API Call Under Oauth
Detail : The configuration was last successfully loaded at 01/01/0001 00:00:00 UTC. This was 1059263714 minutes
ago.
The token cache is being cleared because "use cached token" was set to false.
Exchange Outbound Oauth Log:
Client request ID: 19ad80f6-7751-429f-aac5-e802105fbbc6
Information:[OAuthCredentials:Authenticate] entering
Information:[OAuthCredentials:Authenticate] challenge from
'https://exchserver2.domainname.local/ews/Exchange.asmx' received: Bearer
client_id="00000002-0000-0ff1-ce00-000000000000",
trusted_issuers="[email protected]",Negotiate,NTLM
Information:[OAuthCredentials:GetToken] client-id: '00000002-0000-0ff1-ce00-000000000000', realm: '',
trusted_issuer: '[email protected]'
Information:[OAuthCredentials:GetToken] start building a token for the user domain 'domainname.co.uk'
Information:[OAuthTokenBuilder:GetAppToken] start building the apptoken
Information:[OAuthTokenBuilder:GetAppToken] checking enabled auth servers
Error:[OAuthTokenBuilder:GetAppToken] unable to continue building token; no locally configured issuer
was in the trusted_issuer list, realm from challenge was also empty. trust_issuers was
[email protected]
Error:The trusted issuers contained the following entries
'[email protected]'. None of them are configured locally.
Exchange Response Details:
HTTP response message:
Exception:
System.Net.WebException: The request was aborted: The request was canceled. --->
Microsoft.Exchange.Security.OAuth.OAuthTokenRequestFailedException: The trusted issuers contained the
following entries '[email protected]'. None of them are
configured locally.
at Microsoft.Exchange.Security.OAuth.OAuthTokenBuilder.GetAppToken(String applicationId, String
destinationHost, String realmFromChallenge, IssuerMetadata[] trustedIssuersFromChallenge, String
userDomain)
at Microsoft.Exchange.Security.OAuth.OAuthTokenBuilder.GetAppWithUserToken(String applicationId,
String destinationHost, String realmFromChallenge, IssuerMetadata[] trustedIssuersFromChallenge, String
userDomain, ClaimProvider claimProvider)
at Microsoft.Exchange.Security.OAuth.OAuthCredentials.GetToken(WebRequest webRequest,
HttpAuthenticationChallenge challengeObject)
at Microsoft.Exchange.Security.OAuth.OAuthCredentials.Authenticate(String challengeString, WebRequest
webRequest, Boolean preAuthenticate)
at Microsoft.Exchange.Security.OAuth.OAuthCredentials.OAuthAuthenticationModule.Authenticate(String
challenge, WebRequest request, ICredentials credentials)
at System.Net.AuthenticationManager.Authenticate(String challenge, WebRequest request, ICredentials
credentials)
at System.Net.AuthenticationState.AttemptAuthenticate(HttpWebRequest httpWebRequest, ICredentials
authInfo)
at System.Net.HttpWebRequest.CheckResubmitForAuth()
at System.Net.HttpWebRequest.CheckResubmit(Exception& e, Boolean& disableUpload)
at System.Net.HttpWebRequest.DoSubmitRequestProcessing(Exception& exception)
at System.Net.HttpWebRequest.ProcessResponse()
at System.Net.HttpWebRequest.SetResponse(CoreResponseData coreResponseData)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.Monitoring.TestOAuthConnectivityHelper.SendExchangeOAuthRequest(ADUser user,
String orgDomain, Uri targetUri, String& diagnosticMessage, Boolean appOnly, Boolean useCachedToken,
Boolean reloadConfig)
ResultType : Error
Identity : Microsoft.Exchange.Security.OAuth.ValidationResultNodeId
IsValid : True
ObjectState : New
It appears to work fine from Lync 2013 to Exchange 2013.
When I run: Test-CsExStorageConnectivity -sipuri [email protected] -Binding Nettcp -Verbose in Lync 2013 I get a successful outcome:
VERBOSE: Successfully opened a connection to storage service at localhost using
binding: NetNamedPipe.
VERBOSE: Create message.
VERBOSE: Execute Exchange Storage Command.
VERBOSE: Processing web storage response for ExCreateItem Success.,
result=Success, activityId=0bbdc565-4a05-4b57-bf95-0c75488a1ef6, reason=.
VERBOSE: Activity tracing:
2015/01/02 19:15:55.616 Autodiscover, send GetUserSettings request,
[email protected], Autodiscover
Uri=https://exchserver2.domainname.local/autodiscover/autodiscover.svc, Web
Proxy=<NULL>
2015/01/02 19:15:55.616 Autodiscover.EWSMA trace,
type=AutodiscoverRequestHttpHeaders, message=<Trace
Tag="AutodiscoverRequestHttpHeaders" Tid="30" Time="2015-01-02 19:15:55Z">
POST /autodiscover/autodiscover.svc HTTP/1.1
Content-Type: text/xml; charset=utf-8
Accept: text/xml
User-Agent: ExchangeServicesClient/15.00.0516.004
</Trace>
2015/01/02 19:15:55.624 Autodiscover.EWSMA trace, type=AutodiscoverRequest,
message=<Trace Tag="AutodiscoverRequest" Tid="30" Time="2015-01-02 19:15:55Z"
Version="15.00.0516.004">
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope
xmlns:a="http://schemas.microsoft.com/exchange/2010/Autodiscover"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<a:RequestedServerVersion>Exchange2013</a:RequestedServerVersion>
<wsa:Action>http://schemas.microsoft.com/exchange/2010/Autodiscover/Autodiscove
r/GetUserSettings</wsa:Action>
<wsa:To>https://exchserver2.domainname.local/autodiscover/autodiscover.svc</
wsa:To>
</soap:Header>
<soap:Body>
<a:GetUserSettingsRequestMessage
xmlns:a="http://schemas.microsoft.com/exchange/2010/Autodiscover">
<a:Request>
<a:Users>
<a:User>
<a:Mailbox>[email protected]</a:Mailbox>
</a:User>
</a:Users>
<a:RequestedSettings>
<a:Setting>InternalEwsUrl</a:Setting>
<a:Setting>ExternalEwsUrl</a:Setting>
<a:Setting>ExternalEwsVersion</a:Setting>
</a:RequestedSettings>
</a:Request>
</a:GetUserSettingsRequestMessage>
</soap:Body>
</soap:Envelope>
</Trace>
2015/01/02 19:15:55.704 Autodiscover.EWSMA trace,
type=AutodiscoverResponseHttpHeaders, message=<Trace
Tag="AutodiscoverResponseHttpHeaders" Tid="30" Time="2015-01-02 19:15:55Z">
HTTP/1.1 200 OK
Transfer-Encoding: chunked
request-id: 5917d246-64b0-48e2-ad79-f9b6cffb5bea
X-CalculatedBETarget: exchserver2.domainname.local
X-DiagInfo: EXCHSERVER2
X-BEServer: EXCHSERVER2
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Set-Cookie: ClientId=FTFXWUQWWRJVBMNBG; expires=Sat, 02-Jan-2016 19:15:55 GMT;
path=/;
HttpOnly,X-BackEndCookie=actas1(sid:S-1-5-21-3691024758-535552880-811174816-113
5|smtp:[email protected]|upn:[email protected])=u56Lnp2ejJqBx8jIn
sqbxpvSz8rHx9LLzp7O0sbOzcnSzcqcmZqem8aempmcgYHNz87K0s/N0s/Oq87Gxc7KxcrK;
expires=Sun, 01-Feb-2015 19:15:55 GMT; path=/autodiscover; secure; HttpOnly
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: EXCHSERVER2
Date: Fri, 02 Jan 2015 19:15:55 GMT
</Trace>
2015/01/02 19:15:55.704 Autodiscover.EWSMA trace, type=AutodiscoverResponse,
message=<Trace Tag="AutodiscoverResponse" Tid="30" Time="2015-01-02 19:15:55Z"
Version="15.00.0516.004">
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action
s:mustUnderstand="1">http://schemas.microsoft.com/exchange/2010/Autodiscover/Au
todiscover/GetUserSettingsResponse</a:Action>
<h:ServerVersionInfo
xmlns:h="http://schemas.microsoft.com/exchange/2010/Autodiscover"
xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<h:MajorVersion>15</h:MajorVersion>
<h:MinorVersion>0</h:MinorVersion>
<h:MajorBuildNumber>1044</h:MajorBuildNumber>
<h:MinorBuildNumber>21</h:MinorBuildNumber>
<h:Version>Exchange2013_SP1</h:Version>
</h:ServerVersionInfo>
</s:Header>
<s:Body>
<GetUserSettingsResponseMessage
xmlns="http://schemas.microsoft.com/exchange/2010/Autodiscover">
<Response xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<ErrorCode>NoError</ErrorCode>
<ErrorMessage />
<UserResponses>
<UserResponse>
<ErrorCode>NoError</ErrorCode>
<ErrorMessage>No error.</ErrorMessage>
<RedirectTarget i:nil="true" />
<UserSettingErrors />
<UserSettings>
<UserSetting i:type="StringSetting">
<Name>InternalEwsUrl</Name>
<Value>https://exchserver2.domainname.local/EWS/Exchange.asmx</Value>
</UserSetting>
<UserSetting i:type="StringSetting">
<Name>ExternalEwsUrl</Name>
<Value>https://exchserver2.domainname.co.uk/EWS/Exchange.asmx</Value>
</UserSetting>
<UserSetting i:type="StringSetting">
<Name>ExternalEwsVersion</Name>
<Value>15.00.1044.000</Value>
</UserSetting>
</UserSettings>
</UserResponse>
</UserResponses>
</Response>
</GetUserSettingsResponseMessage>
</s:Body>
</s:Envelope>
</Trace>
2015/01/02 19:15:55.704 Autodiscover, received GetUserSettings response,
duration Ms=88, response=NoError
2015/01/02 19:15:55.706 Lookup user details,
sipUri=sip:[email protected], [email protected],
sid=S-1-5-21-3691024758-535552880-811174816-1135, [email protected],
tenantId=00000000-0000-0000-0000-000000000000
VERBOSE: Items choice type: CreateItemResponseMessage.
VERBOSE: Response message, class: Success, code: NoError.
VERBOSE: Item: Microsoft.Rtc.Internal.Storage.Exchange.Ews.MessageType, Id:
AAMkADAwNWZkZWI0LWM5NGYtNDUxNy05Nzk3LWZhZjRiY2Y4MTU4NwBGAAAAAADLP1MgTEXdQ7zQSlb
qPl++BwBauhRZTfLbTYZ+hBWtK784ANcdmUYqAACSqIurRqgYSZwMhT/IBw89AACnT6G9AAA=,
change key: CQAAABYAAACSqIurRqgYSZwMhT/IBw89AACnip6b, subject: , body: .
VERBOSE: Is command successful: True.
Test passed.
All my certificates on the Exchange 2013 and Lync 2013 servers are from my local CA.
I use APP with the public certificates as my reverse proxy for people connecting from outside the network.
In Lync, the OAuthTokenIssuer certificate created through the Lync deployment wizard is issued to domainname.local (my primary sip domain) and the Subject Alternative names include domainname.co.uk
I then exported this certificate to the Exchange Server and use the Set-AuthConfig to use this certificate for OAuth.
from what I read this was what I was supposed to do.
is this correct?
I have tried so many things I don't know what do to next.
Should the OAuth certificate in exchange be the one exported from Lync?
In Lync, should the OAuthTokenIssuer certificate include the servername or lyncserver.domainname.local or just be domainname.local like it is at the moment?
thank-you
jack

Thomas,
thanks for giving this the time. I have run the Configure-EnterpriseApplication.ps1 script following by remove-PartnerApplication so many times that I was wondering if there are other setting that
Configure-EnterpriseApplication.ps1 creates that aer not removed when you run
remove-PartnerApplication.
is there a way to completely remove everything that is confirmed when you run
Configure-EnterpriseApplication.ps1 so I can run Configure-EnterpriseApplication.ps1 without there being any configurations left from when I previously run that command?
thanks
jack
[PS] C:\Windows\system32>Get-PartnerApplication |fl
RunspaceId : cb2fb328-769d-4b32-8b7b-1fa35e2994f5
Enabled : True
ApplicationIdentifier : 00000004-0000-0ff1-ce00-000000000000
CertificateStrings : {MIIGcDCCBVigAwIBAgITPgAAARIHL+ig32UAAQAAAAABEjANBgkqhkiG9w0BAQUFADBcMRUwEwYKCZIm
iZPyLGQBGRYFbG9jYWwxHTAbBgoJkiaJk/IsZAEZFg1HdWlkZUNsb3RoaW5nMSQwIgYDVQQDExtHdWlkZ
UNsb3RoaW5nLUFQUFNFUlZFUjEtQ0EwHhcNMTUwMTEwMTIxODIzWhcNMTcwMTA5MTIxODIzWjB7MQswCQ
YDVQQGEwJHQjEPMA0GA1UECBMGTG9uZG9uMQ8wDQYDVQQHEwZMb25kb24xHzAdBgNVBAoTFkd1aWRlIEN
sb3RoaW5nIExpbWl0ZWQxCzAJBgNVBAsTAkhRMRwwGgYDVQQDExNHdWlkZUNsb3RoaW5nLmNvLnVrMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyzDzaLsjJfktsbwIJ998ihsZM/0rKGdIt8rIx00oc
HA7w0uVyz2UqnP9a8uRi6HkA7djbynlmGG0hKSUUQngXxz7q2dY6q9rcY5Rw2mJOMeppounx44FFp4+4e
5HQKviLTYo+3DBGIR0mYDqxanKPS00d0f7HDLvmVb90hjdrbE372JBdcNNHs2OHRqg37bN2fAbwd22c9x
2kvi0rESFnr+KcIGECVInCTHLJ7fwVqvi4hvRqtz7KLZsMXprpgeVDs45EMMRtwJ5Hw8uZR4CFz4dHSlo
dIVgDPn8Ns2vGhcUK0JU4WkDbjnqo1SJzHlqtNjiu//wGcn77PAiM0yhyQIDAQABo4IDCjCCAwYwCwYDV
R0PBAQDAgWgMCEGCSsGAQQBgjcUAgQUHhIAVwBlAGIAUwBlAHIAdgBlAHIwEwYDVR0lBAwwCgYIKwYBBQ
UHAwEwHQYDVR0OBBYEFOY3whPicRAXNsTDSIg3FexpaCKdMHUGA1UdEQRuMGyCH0x5bmNTZXJ2ZXIyLkd
1aWRlQ2xvdGhpbmcuY28udWuCH0x5bmNTZXJ2ZXIyLkd1aWRlQ2xvdGhpbmcubG9jYWyCE0d1aWRlQ2xv
dGhpbmcuY28udWuCE0d1aWRlQ2xvdGhpbmcubG9jYWwwHwYDVR0jBBgwFoAUDHst3gUSMGwvkiNTPavmi
UEWgtQwggEuBgNVHR8EggElMIIBITCCAR2gggEZoIIBFYaBzWxkYXA6Ly8vQ049R3VpZGVDbG90aGluZy
1BUFBTRVJWRVIxLUNBLENOPURvbVNlcnZlcjIsQ049Q0RQLENOPVB1YmxpYyUyMEtleSUyMFNlcnZpY2V
zLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9R3VpZGVDbG90aGluZyxEQz1sb2NhbD9jZXJ0
aWZpY2F0ZVJldm9jYXRpb25MaXN0P2Jhc2U/b2JqZWN0Q2xhc3M9Y1JMRGlzdHJpYnV0aW9uUG9pbnSGQ
2h0dHA6Ly9jcmwuZ3VpZGVjbG90aGluZy5sb2NhbC9jcmxkL0d1aWRlQ2xvdGhpbmctQVBQU0VSVkVSMS
1DQS5jcmwwgdUGCCsGAQUFBwEBBIHIMIHFMIHCBggrBgEFBQcwAoaBtWxkYXA6Ly8vQ049R3VpZGVDbG9
0aGluZy1BUFBTRVJWRVIxLUNBLENOPUFJQSxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2
aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPUd1aWRlQ2xvdGhpbmcsREM9bG9jYWw/Y0FDZXJ0aWZpY2F0Z
T9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwDQYJKoZIhvcNAQEFBQADggEBAD
87GUPi02czEMO2Op0CeKBBpGwsfjYR9+RlC2uKAoH8PbWAxYNP3Ke6BtPeFy+95GGAJd5Z0+6LpO/AagA
+zeY/tocZQjy0pYaU4/TPZgD+ZB/8sU982msu+8waO316ipBcf/87n9ZW3Jjk5DcVbtwrZErrGRe9DEn8
QArN0jroLfaRtbDumse1Lp76+dxFuVhlLWcUXtIKaxm+UU9DS94EwJMtN54lDm3EG6hVdiGUR7TYqZU0K
HGm7HciIhuO+2rhAazOBiIAAW6wZRUpFKZONSVD6bKrQCzL12LvynQ7XC6Itgr4JGzNCmoN43dXwVCkWo
amTDdZY4h+QBqUvvY=}
AuthMetadataUrl : https://lyncserver2.domainname.local/metadata/json/1
Realm : domainname.local
UseAuthServer : False
AcceptSecurityIdentifierInformation : True
LinkedAccount : domainname.local/Users/LyncEnterprise-ApplicationAccount
IssuerIdentifier :
AppOnlyPermissions :
ActAsPermissions :
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : LyncEnterprise-786f61476b634278a3c9b9e4ec08b660
DistinguishedName : CN=LyncEnterprise-786f61476b634278a3c9b9e4ec08b660,CN=Partner
Applications,CN=Auth Configuration,CN=domainname,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domainname,DC=local
Identity : LyncEnterprise-786f61476b634278a3c9b9e4ec08b660
Guid : 07495125-ccd4-4443-82d9-74fc3b955cdf
ObjectCategory : domainname.local/Configuration/Schema/ms-Exch-Auth-Partner-Application
ObjectClass : {top, msExchAuthPartnerApplication}
WhenChanged : 10/01/2015 17:14:55
WhenCreated : 10/01/2015 17:14:55
WhenChangedUTC : 10/01/2015 17:14:55
WhenCreatedUTC : 10/01/2015 17:14:55
OrganizationId :
Id : LyncEnterprise-786f61476b634278a3c9b9e4ec08b660
OriginatingServer : DomServer2.domainname.local
IsValid : True
ObjectState : Unchanged

Exchange 2013 management shell error

Similar Messages

Maybe you are looking for