What are the Steps to be taken care before decommisioning Exchange 2010

March 25, 2015, 12:16 am

≫ Next: Uninstalling Exchange 2013 SP1 failed on Step 8 Lanugage

≪ Previous: Exchange 2010 not working for 3 staff members out of 40

I migrated from exchange 2010 to 2013 with DR.

Hopefully its working fine.

Now i am planning to decommission my exchange server 2010. It was powered off 15days back.

Could you please tell me the process of decommissioning exchange server 2010.

Also what are the things need to check before decommisioning..

thanks..

↧

Uninstalling Exchange 2013 SP1 failed on Step 8 Lanugage

March 25, 2015, 3:43 am

≫ Next: Troubleshooting for Event 9646

≪ Previous: What are the Steps to be taken care before decommisioning Exchange 2010

Hello,

I am trying to uninstall Exchange 2013 SP1 but it is failing while uninstalling Language step # 8 the error is;

--------

Error:
The following error was generated when "$error.Clear();
                    $regPath='HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall';

                    $PackageGUIDRegEx = "{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}";

                    $InstallPath = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup').MsiInstallPath;

                    if(test-path ($regPath))
                    {
                        Write-ExchangeSetupLog -info ("Removing " + $RoleLanguagePackType + " Language Packs.");
                        Get-ChildItem ($regPath) | foreach{
                            if($_ -match "(?<ProductCode>$PackageGUIDRegEx)") {
                                $langPackPackageCode = $matches['ProductCode'];
                                if($langPackPackageCode -ne $null -and $langPackPackageCode.Length -ne 0) {
                                    Write-ExchangeSetupLog -info ("Removing package $langPackPackageCode");
                                    $language = $langPackPackageCode.Substring(20,4);
                                    $logFilePath = [IO.Path]::Combine($RoleLogFilePath,"Uninstall")+ '.' + $language + '.' + "Client" + "." + $RoleLogDateTime + ".msilog";
                                    uninstall-MsiPackage -ProductCode ($langPackPackageCode) -LogFile ($logFilePath);
                                };
                            };
                        };
                        Get-Childitem -Path $InstallPath -include "*.Localized.js","*.Localized.min.js" -recurse | foreach ($_) {remove-item $_.fullname};
                        Write-ExchangeSetupLog -info "Remove Language Packs completed.";
                    };

        " was run: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
--------

I am also attaching the snapshots. Please guide me how to uninstall Exchange 2013. I had some issue with Exchange Server and it need to uninstall and re-install the Exchange Server.

↧

Troubleshooting for Event 9646

March 26, 2015, 2:05 am

≫ Next: Upgrade Exchange Server 2013 SP1

≪ Previous: Uninstalling Exchange 2013 SP1 failed on Step 8 Lanugage

As an Exchange administrator, I am sure you are familiar with the kinds of the 9646 event error report in the application log. They can appear many times per day or only happen once a week. Although, it seems there is no user impact about this error, but the Boss may have concerns about the potential issues about this error.

[Symptoms]
============

[Cause]
=========
Connection and usage limits have been placed on the Exchange store to prevent a single application or a single user from using all the available connections to the Exchange store.

Item type	Registry object type	Max opened per session
ACL View	objtACLView	50
Attachment	objtAttachment	500
Attachment View	objtAttachmentView	500
Cstream	objtCStream	50
Folder	objtFolder	500
Folder View	objtFolderView	500
FX Destination Stream	objtFXDstStrm	50
FX Source Stream	objtFXSrcStrm	50
Message	objtMessage	250
Message View	objtMessageView	500
Notification	objtNotify	500,000
Rule View	objtRulesView	50
Stream	objtStream	250

[Solution]
===========
Firstly, you need to check the application log and see if the user do have the requirements to raise the store limitation for them.

For Example, some VIPs may need to keep the mailbox open on multiple clients like Outlook, OWA, Mobilities, or they have requirements to share their mailboxes to secretaries. Then you may need to raise the MaxObjsPerMapiSession value for them in order to avoid this event error report.

1.Start Registry Editor (regedit).
2.Navigate to the following registry subkey:

\\HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem

3.Right-click ParametersSystem, point to New, and then click Key. A new key is created in the console tree.
4.Rename the key MaxObjsPerMapiSession, and then press Enter.
5.Right-click MaxObjsPerMapiSession, point to New, and then click DWORD (32-bit) Value. The new value is created in the result pane.
6.Rename the key to <Object_type>, where <Object_type> is the name of the registry object type that you're modifying. For example, to modify the number of messages that can be opened, use objtMessage. Press Enter.
7.Right-click the newly created key, and then click Modify.
8.In the Value data box, type the number of objects that you want to limit this entry to, and then click OK. For example, type 350 to increase the value for the object.
9.Restart the Microsoft Exchange Information Store service.

However, for some instances, the in question user may tell you that only Outlook is in use and there is no other live MAPI sessions he know. Based on my experience, this issue can occur due to third-party add-ins on Outlook or some third-party search indexing software on the Outlook client. To verify this issue, you can run Windows in Clean Boot mode (better to temporarily remove the searching software) and run Outlook without add-ins by “Outlook /safe”.

In summary, the 9646 Event reports are just the notification about the status of each Exchange Client that connect to the mailbox store. The user impacts may not be huge and you can choose different countermeasures according to the conditions.

More details:

http://support.microsoft.com/kb/842022
https://technet.microsoft.com/en-us/library/ff477612(v=exchg.141).aspx

Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

↧

Upgrade Exchange Server 2013 SP1

March 26, 2015, 2:20 pm

≫ Next: Exchange 2013 Upgrade to CU7 from SP1 - installs successfully - Can no longer connect via ECP/OWA/Powershell/Outlook/Autodiscover

≪ Previous: Troubleshooting for Event 9646

Hello,

I have two Exchange 2013 SP1 servers with DAG configured. I want to upgrade them with CU8. Kindly advise how to do or is there any step by step document available for upgrading the DAG member server.

Thanks in advance.

↧

Exchange 2013 Upgrade to CU7 from SP1 - installs successfully - Can no longer connect via ECP/OWA/Powershell/Outlook/Autodiscover

March 20, 2015, 5:08 pm

≫ Next: Event IDs 16025 and 205

≪ Previous: Upgrade Exchange Server 2013 SP1

Hi There,
I am having massive issues with my Exchange Server.
I have 2 Nodes, one has CAS and Mailbox Roles, the other just Mailbox.

I "upgraded" the CAS server to CU7 without any errors / issues.

Once I had restarted, nothing worked any more.. I couldn't access ECP, OWA, Powershell, Autodiscover or get outlook to connect.

I managed to get Powershell working, but changing the physical directory to "C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell" from "C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\PowerShell"

But for the life of me I cannot get ECP or OWA working (haven't even tried anything else)!

I am getting a load of Events with ID 1003.

The only error I am getting is:

Server Error in '/ecp' Application.

Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.MissingMethodException: Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[MissingMethodException: Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.]
   Microsoft.Exchange.HttpProxy.ProxyModule.AllowAnonymousRequest(HttpRequest httpRequest) +0
   Microsoft.Exchange.HttpProxy.ProxyModule.OnAuthenticateInternal(HttpApplication httpApplication) +51
   Microsoft.Exchange.HttpProxy.<>c__DisplayClass5.<OnAuthenticateRequest>b__4() +447
   Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate) +40
   Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate) +408
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165

Which is almost meaningless... but maybe someone out there has some idea?

Unfortunately this is very urgent for me a these are production servers and currently there is no email for my company.

So Please please please can someone help.

I have tried many many many things from various sites, and so far nothing has worked.

Thanks,

-Tim

↧

Event IDs 16025 and 205

March 27, 2015, 12:40 am

≫ Next: Cumulative Update 8 broke Exchange 2013

≪ Previous: Exchange 2013 Upgrade to CU7 from SP1 - installs successfully - Can no longer connect via ECP/OWA/Powershell/Outlook/Autodiscover

A newly installed Exchange 2013 Server (Mailbox and Client Access roles) shows every 5 minutes the event id's 16025 and 205 in the eventlog.

Both events are shown twice at the same time. First 205 then 16025 and again 205 and 16025.

Level: Error
Id 205 - Source: MSExchange Common
Id 16025 - Source: MSExchangeFrontEndTransport

Both have exactly the same description:
No DNS servers could be retrieved from network adapter 0957d69c-9b06-4b72-aa6b-ac825435b485. Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results

Get-NetworkConnectionInfo shows the following results:
RunspaceId : e854435f-ffbe-4ccb-81d9-7e729284e26a
Name        : Microsoft Hyper-V Network Adapter
DnsServers : {10.10.32.34, 10.10.32.42}
IPAddresses : {10.10.32.45, 10.10.32.44, fe80::9cb9:ad68:c7cc:2052}
AdapterGuid : 0957d69c-9b06-4b72-aa6b-ac825435b485
MacAddress : 00:1D:D8:B7:1E:2A
Identity    : 0957d69c-9b06-4b72-aa6b-ac825435b485
IsValid     : True
ObjectState : Unchanged

Mailflow is working, I would like to get rid of these error events.

Any suggestions?

Regards
Peter

↧

Cumulative Update 8 broke Exchange 2013

March 27, 2015, 12:53 am

≫ Next: Exchange 2010 - 2013 random auth.owa error

≪ Previous: Event IDs 16025 and 205

While installing Cumulative Update 8 on our exchange 2013 server it failed with the following error during the second to last step (client access role: client access front end). Any advice on what may be causing this and how to fix?

Error:
The following error was generated when "$error.Clear();
$fe = get-ActiveSyncVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController -ErrorAction SilentlyContinue;

          if ($fe -eq $null)
          {
            new-ActiveSyncVirtualDirectory -DomainController $RoleDomainController -Role ClientAccess;
          }
          else
          {
            update-ActiveSyncVirtualDirectory $fe -DomainController $RoleDomainController -InstallIsapiFilter $true
          }
        " was run: "System.Management.Automation.ParameterBindingException: Cannot convert 'System.Object[]' to the type 'Microsoft.Exchange.Configuration.Tasks.VirtualDirectoryIdParameter' required by parameter 'Identity'. Specified method is not supported. ---> System.NotSupportedException: Specified method is not supported.
   at System.Management.Automation.ParameterBinderBase.CoerceTypeAsNeeded(CommandParameterInternal argument, String parameterName, Type toType, ParameterCollectionTypeInformation collectionTypeInfo, Object currentValue)
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
   at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".

↧

Exchange 2010 - 2013 random auth.owa error

March 27, 2015, 1:02 am

≫ Next: Users with mailboxes on exchange 2010 cant proxy to OWA on exchange 2013

≪ Previous: Cumulative Update 8 broke Exchange 2013

Hello,

I have an odd situation where we are preparing 2 exchange 2013 servers to migrate 2010 servers to

so currently:

2x Exchange 2010 (with dag)

2x Exchange 2013 (with dag).

Now it's behaving extremely odd when it comes to ECP for the 2013 servers.

randomly it works and doesn't work.

i generally try it from localhost on both 2013 servers, and individual server ip's from lets say 4 or 5 places.

all same login, and admin user is inside mailbox db DAG cluster.

now the problem:

it randomly pops up auth.owa error 500

when i say random i truly mean random, sometimes everything 100% works, i am able to login 100% from all servers.

then i check back lets say 2 hours later.. some obtain auth.owa errors while others work.

What i tried:

- I rebuild OWA (first with reset, then with remove and re-add method) on both 2013 servers.

- removed killbit file from 2013's

- rebuild exchange 2013's (just exchange it self).

- checked heartbeat monitor boxes and removed the null values.

----------------------------------

It's safe to say i am kind of lost on what to try next.

i am also mistefied why it randomly works, i know it's internally loadbalanced, but shutting down 1 of the 2013 servers did not get rid of this strange behavior.

is it possible that the exchange 2010 servers play a part in this issue?

Any ideas, any help is very much welcome!.

Regards,

Marco

Key4ce - IT professionals: www.key4ce.eu

↧

Users with mailboxes on exchange 2010 cant proxy to OWA on exchange 2013

March 26, 2015, 1:14 pm

≫ Next: Need to copy mailbox from Exchange 2010 to MS Online

≪ Previous: Exchange 2010 - 2013 random auth.owa error

We are in the process of migrating from 2010 to 2013. Users with mailboxes on exchange 2010 can't proxy to the owa on Exchange 2013 - there is no error - just receiving a message "Still working on it"

alex serdyukov

↧

Need to copy mailbox from Exchange 2010 to MS Online

March 26, 2015, 6:48 am

≫ Next: Error Preparing Schema for Exchange 2013

≪ Previous: Users with mailboxes on exchange 2010 cant proxy to OWA on exchange 2013

I perform the Hybrid Configuration from that site:

https://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-FQAIAAAAQAAAAA8AKFQAQAA~&f=255&MSPPError=-2147217396

When I try to do the moving step, I have those errors;

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:06

Test
Failed

Error:
Deserialization fails due to one SerializationException: System.Runtime.Serialization.SerializationException: Unable to find assembly 'Microsoft.Exchange.MailboxReplicationService.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
at System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name)
at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, IMethodCallMessage methodCallMessage)
at Microsoft.Exchange.Data.SerializationTypeConverter.<>c__DisplayClass3.<DeserializeObject>b__0()

Unable to find assembly 'Microsoft.Exchange.MailboxReplicationService.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Exchange Management Shell command attempted:
'50038459-45a0-4cf4-bc46-42d9d7158752' | New-MoveRequest -Remote -RemoteHostName 'mail.sqliaison.com' -RemoteCredential 'System.Management.Automation.PSCredential' -TargetDeliveryDomain 'inedge.mail.onmicrosoft.com'

Elapsed Time: 00:00:06

The user is in the cloud synchronized with my local DC and I have assigned a license to it.

Any help would be appreciated/

↧

Error Preparing Schema for Exchange 2013

April 9, 2014, 10:44 am

≫ Next: Exchange CA recovery

≪ Previous: Need to copy mailbox from Exchange 2010 to MS Online

I recive this error when running the preparing AD for exchange 2013 on a 2012 r2 server.

Error:

The following error was generated when "$error.Clear();

# O15# 2844081 - Create PartnerApplication "Exchange Online" in DC and On-Premise

$exch = [Microsoft.Exchange.Data.Directory.SystemConfiguration.WellknownPartnerApplicationIdentifiers]::Exchange;

$exchApp = Get-PartnerApplication $exch -ErrorAction SilentlyContinue -DomainController $RoleDomainController | Where { $_.UseAuthServer };

if ($exchApp -eq $null)

{

$exchAppName = "Exchange Online";

$exchApp = New-PartnerApplication -Name $exchAppName -ApplicationIdentifier $exch -Enabled $RoleIsDatacenter -AcceptSecurityIdentifierInformation $false -DomainController $RoleDomainController;

}

# Create application account for Exchange

$appAccountName = $exchApp.Name + "-ApplicationAccount";

$appAccount = Get-LinkedUser -Identity $appAccountName -ErrorAction SilentlyContinue -DomainController $RoleDomainController;

if ($appAccount -eq $null)

{

$appAccountUpn = $appAccountName.Replace(" ", "_") + "@" + $RoleFullyQualifiedDomainName;

$appAccount = New-LinkedUser -Name $appAccountName -UserPrincipalName $appAccountUpn -DomainController $RoleDomainController;

New-ManagementRoleAssignment -Role "UserApplication" -User $appAccount.Identity -DomainController $RoleDomainController;

New-ManagementRoleAssignment -Role "ArchiveApplication" -User $appAccount.Identity -DomainController $RoleDomainController;

New-ManagementRoleAssignment -Role "LegalHoldApplication" -User $appAccount.Identity -DomainController $RoleDomainController;

New-ManagementRoleAssignment -Role "Mailbox Search" -User $appAccount.Identity -DomainController $RoleDomainController;

New-ManagementRoleAssignment -Role "TeamMailboxLifecycleApplication" -User $appAccount.Identity -DomainController $RoleDomainController;

New-ManagementRoleAssignment -Role "MailboxSearchApplication" -User $appAccount.Identity -DomainController $RoleDomainController;

Set-PartnerApplication -Identity $exchApp.Identity -LinkedAccount $appAccount.Identity -DomainController $RoleDomainController;;

}

" was run: "Couldn't find a user with the identity "ESL.LOC/Users/Exchange Online-ApplicationAccount".".