Hello,

I am a bit confused about info about requirements when migrating Exchange ActiveSync (EAS) from 2003 to 2010. Now this question is related to EAS only, forget about other services, such as OWA or Outlook Anywhere, for a while.

Basically, all migration guides state that you have to configure and setup a legacy url for legacy services for co-existence. Based on that, I have had an understanding that Exchange 2010 CAS cannot proxy EAS users that are still on Exchange 2003, but issues a redirect command to EAS client.

However, this article shows information that, based on my understanding, states that Exchange 2010 CAS DOES proxy EAS clients that are still on 2003: http://blogs.technet.com/b/exchange/archive/2009/12/08/3408985.aspx

For migration from 2007 EAS to 2010 EAS the article shows redirecting, but not with 2003.

So my question is: While talking about only EAS, do I need to configure legacy external url/namespace/name resolution or not?

Thanks for answering!

I need to send out few thousands of emails in a weekly or sometimes daily through exchange. can someone explain the best pricess to do that without getting blacklisted.

thanks

alan

Our config :
Version 14.2 (Build 247.5)

2 Mailbox servers (DAG),  2 CAS/HUB Servers using a NLB,  2 edge

my question is the following:
can i go directly to rullp 7 without installing  2,4, 5, 6 or I have to install all rollup ?
and what's the bests  practices for installing rollup ?

Hello Everyone,

In our Organisation, We already configured Windows Network Load balancing for 4 CAS Servers.

We found that among all the 4 servers, one servers (Exchange Server SP2) getting huge connections on that and rest of the other 3 servers (Exchange SP3 with 6Update RollUp) are hit very least number while compare to that server.

Kindly assist on this issue.

Hello Everyone,

we are installing Exchange server service pack 3 in our organisation. so once completed, we have to start install update rollup's.

In that, shall we install update rollup 6 directly without installing update rollup 1,2,3,...

Awaiting for your response.

Regars

Kart03

We migrated to Exchange 2013 and then shut down the old Exchange 2007 server as a test.  There was only one negative result and that was a 1 to 2 minute delay for the Outlook client to connect.  I started to uninstall Exchange 2007 and am stuck with trying to uninstall the Hub Transport service.  It fails with the error -

Unable to remove product with code 93fcff43-49e2-4ae5-9ad4-0256878ab886. The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. Error code is 1632. 

Not sure where the temp file is that is located.  The C:\temp is empty and there is 15 gb free on the C drive.

The administrator has full access and is the owner.  There are no quotas set up.  Same with the C:\Windows\Temp.

Tried to register diagnosticcomdletcontroller.dll and remove the watermark and action keys under HLKM\software\Microsoft\Exchange\v8.0\hubtransportrole but that did not help.

I have this issue decommisioning an Exchange 2007 server.

As is:

All user maibox are migrated to Exc 2013
There is a Public Folder Database on the Exch 2007 containing only system mailbox

[PS] C:\Program Files\Microsoft\Exchange Server\scripts>Get-PublicFolderStatisti
cs

Name                                     ItemCount               LastAccessTime
----                                     ---------               --------------
Default                                  0                6/11/2014 12:42:31 PM
EX:/o=Organization/ou=Exchange Administrative  169               6/11/2014 2:00:00 AM
Group (FYDIBOHF23SPDLT)
EX:/o=Organization/ou=Exchange Administrative  0                 6/11/2014 2:15:00 AM
Group (FYDIBOHF23SPDLT)
exchangeV1                               401              6/11/2014 12:42:31 PM
globalevents                             0                6/11/2014 12:42:31 PM
internal                                 0                6/11/2014 12:42:31 PM
microsoft                                0                6/11/2014 12:42:31 PM
OAB Version 2                            0                 6/11/2014 5:13:04 AM
OAB Version 3a                           32                6/11/2014 5:13:04 AM
OAB Version 4                            13                6/11/2014 5:13:04 AM
OWAScratchPad{3FFF7BEF-E55C-4CCF-A27C-CD 0                6/11/2014 12:42:31 PM
F1F89C84FF}
schema-root                              0                6/11/2014 12:42:31 PM
StoreEvents{3FFF7BEF-E55C-4CCF-A27C-CDF1 0                6/11/2014 12:42:31 PM
F89C84FF}
/o=Organization/cn=addrlists/cn=oabs/cn=Defaul 0                 6/11/2014 2:15:00 AM
t Offline Address Book

If I try to launch get-publifolder I get this error

[PS] C:\Program Files\Microsoft\Exchange Server\scripts>Get-PublicFolder
Get-PublicFolder : There is no existing PublicFolder that matches the following
 Identity: '\'. Please make sure that you specified the correct PublicFolder Id
entity and that you have the necessary permissions to view PublicFolder.
At line:1 char:17
+ Get-PublicFolder <<<<
    + CategoryInfo          : NotSpecified: (0:Int32) [Get-PublicFolder], Mapi
   OperationException
    + FullyQualifiedErrorId : A7F40D58,Microsoft.Exchange.Management.MapiTasks
   .GetPublicFolder

The Exchange 2007 server has cas,hub,mbx roles.

I need to delete the public folder database before uninstalling the Exchange 2007. There are no need to use the public folder database and the Exchange 2013 will become the single Exchange Server of the organization.

I thank you so much for your help and remain.

Regards,

Enrico

Cached files are local in our hosted environment. I want to migrate mailboxes to a new internal server by importing the .ost files. But that does not work with the GUI import in Outlook 2003 client. Says this is not a .pst file. Tough luck.

Any reason to think that exmerge or something else would be able to import the .ost file.

Saves me time from creating backup .pst files.

thanks

I'm installing Exchange 2007 SP3 onto Server 2008 R2. I have run this install in compatibility mode and in normal install mode with the same results. Error code 3221684346: The data area passed to a system call is too small. I am installing directly from the SP3 files, this is not an upgrade. What do I have to do to get this to work?

[2/15/2011 7:24:18 AM] [2] Interpreting line <CreateSecureKey:MSExchangeIS\ParametersPrivate> -- ID:31259 --
[2/15/2011 7:24:18 AM] [2]  CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199)
           Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Processing file 'C:\Exchange Server\Setup\data\mdb_reg.ins', at or near line 77 (CreateSecureKey:MSExchangeIS\ParametersPrivate) -- ID:31111 -- CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488)
           Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Registry file name: 'C:\Exchange Server\Setup\data\mdb_reg.ins' CRegistryManager::ScProcessFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125)
           Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Filename = 'C:\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScRunRegistryFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379)
           Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScRunRegistryFile
[2/15/2011 7:24:18 AM] [2] Filename = 'C:\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249)
           Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAddRegistryKeys
[2/15/2011 7:24:18 AM] [2]  CAtomBaseMDB::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\components\server\a_basemdb.cxx:132)
           Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CAtomBaseMDB::ScAddRegistryKeys
[2/15/2011 7:24:18 AM] [2]  CBaseAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639)
           Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAdd
[2/15/2011 7:24:18 AM] [2] Service = 'MSExchangeIS' CBaseServiceAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203)
           Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseServiceAtom(Information Store Service)::ScAdd
[2/15/2011 7:24:18 AM] [2] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535)
           Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2]  ScSetupAtom (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:897)
           Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving ScSetupAtom
[2/15/2011 7:24:18 AM] [2] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] The following 1 error(s) occurred during task execution:
[2/15/2011 7:24:18 AM] [1] 0.  ErrorRecord: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] 0.  ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] Setup is halting task execution because of one or more errors in a critical task.
[2/15/2011 7:24:18 AM] [1] Finished executing component tasks.
[2/15/2011 7:24:18 AM] [1] Ending processing.
[2/15/2011 7:42:08 AM] [0] End of Setup
[2/15/2011 7:42:08 AM] [0] **********************************************

Hi, here is a problem I have been bashing my head with for about a week. I am transitioning to Exchange 2010 from 2003. I have two DC's running Windows Server 2003 Sp2, one of which is the Exchange 2003 server. I have just brought online a windows 2008R2 member server, which I am attempting to install exchange 2010 on. I get the following error message during installation.

Organization Preparation
Failed

Error:
The following error was generated when "$error.Clear(); install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema1.ldf")" was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema1.ldf'. The error code is: 8224. More details can be found in the error file: 'C:\Users\administrator.CFN\AppData\Local\Temp\2\ldif.err'".

There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema1.ldf'. The error code is: 8224. More details can be found in the error file: 'C:\Users\administrator.CFN\AppData\Local\Temp\2\ldif.err'

Elapsed Time: 00:00:22

And from the ldif.err:

The connection cannot be established

The error code is 8224

------

Now I have checked dns, all is good. I can resolve the DC without issue.

I have done dcdiag and netdiag and passes all tests. I have even written a hosts file, all this to no avail.

Any help would be appreciated.

Thanks

B

Hello,

Sorry if this is a repeat question, but anything I have found already is from 2009 and doesn't appear to be a solution.

I updated the server and now I get errors when opening Exchange Powershell (and EMC) on the server.  I've tried to uninstall the updates and backing up the state of the server.  This is a 2008 Server with Exchange 2010.  The DC is a 2003 Windows Server.  Any help is appreciated.

It also takes the server 20-40 minutes or more to reboot and login.

The error:

VERBOSE: Connecting to 2008SERV.ServicesInc.local

[2008serv.servicesinc.local] Connecting to remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.

    + CategoryInfo         : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException

    + FullyQualifiedErrorId : PSSessionOpenFailed

Exception calling "GetComputerDomain" with "0" argument(s): "The local computer is not joined to a domain or the domain

 cannot be contacted."

At D:\Exchange 2010\v14\bin\ConnectFunctions.ps1:204 char:70

+     [System.DirectoryServices.ActiveDirectory.Domain]::GetComputerDomain <<<< ().Forest.Name

    + CategoryInfo         : NotSpecified: (:) [], MethodInvocationException

    + FullyQualifiedErrorId : DotNetMethodException

Exception calling "GetComputerSite" with "0" argument(s): "The specified domain either does not exist or could not be contacted.

"

At D:\Exchange 2010\v14\bin\ConnectFunctions.ps1:164 char:92

+     $localSite=[System.DirectoryServices.ActiveDirectory.ActiveDirectorySite]::GetComputerSite <<<< ()

    + CategoryInfo         : NotSpecified: (:) [], MethodInvocationException

    + FullyQualifiedErrorId : DotNetMethodException

Exception calling "FindAll" with "0" argument(s): "Unknown error (0x80005000)"

At D:\Exchange 2010\v14\bin\ConnectFunctions.ps1:253 char:17

+     $search.FindAll <<<< ()

    + CategoryInfo         : NotSpecified: (:) [], MethodInvocationException

    + FullyQualifiedErrorId : DotNetMethodException

You cannot call a method on a null-valued expression.

At D:\Exchange 2010\v14\bin\ConnectFunctions.ps1:146 char:33

+                 $siteName = $siteDN.ToString <<<< ().SubString(3).Split(",")[0]

    + CategoryInfo         : InvalidOperation: (ToString:String) [], RuntimeException

    + FullyQualifiedErrorId : InvokeMethodOnNull

WARNING: No Exchange servers are available in the Active Directory site . Connecting to an Exchange server in another

Active Directory site.

Failed to connect to an Exchange server in the current site.

Enter the server FQDN where you want to connect.:

This rollup, 2936871, when installed on a server having Forefront Protection for Exchange Server integrated with Exchange services, causing Information Store not starting. For this we have to disable the integration and start the services. When again you try to integrate and start the services, Exchange services will not start. So you should not integrate Forefront with Exchange services at all, finally.

Has anybody already in this soup?

Whether Microsoft has checked this? Any solution?

The error events are the below two:

Log Name:      Application
Source:        MSExchangeIS
Event ID:      9581
Task Category: Virus Scanning
Level:         Error
Keywords:      Classic
Description:
Error code 1 returned from virus scanner initialization routine. Virus scanner was not loaded. 

Log Name:      Application
Source:        MSExchangeIS
Event ID:      9564
Task Category: General
Level:         Error
Keywords:      Classic
Description:
Error 0x1 starting the Microsoft Exchange Information Store.
Failed to start virus scan.

My Environment is as follows:

Production

Server 1 -  CAS, Hub Transport (DAG witness server)

Server 2 -  Mailbox (3 databases - DAG with Server 3) - Currently at SP1

Server 3 -  Mailbox, Hub Transport

Migrating mailboxes from Exchange 2000/2003 To Exchange 2007 in a different forest.

This of course all takes place in the new Exchange Management shell which so far seems like a huge step backward in technology.

This wasnt easy to figure out.  Hope this info helps, it is without warranty or gaurantee and I suppose you could completely delete the entire world if you follow them (limiting my liability if you screw up).  This process gets a list of mailboxes and supplies them to the move-mailbox command so you dont have to enter them one at a time.

First credentials need to be set in the source domain (the Ex2000/2003 domain)
The command below will pop up a gui to enter domain\usernam and password and stores these in the variable $c which will be called later.

$c = Get-Credential

Getting the mailbox list

Default Get-Mailbox command - there are many more options for this but here is what I used.

Get-Mailbox -Credential $c -Database "Exch2003Server1\DB1" -DomainController server.domain.com -ResultSize Unlimited

-Database is your old EX2000 or Ex2003 server and must be "servername\Mailbox Store" The "Mailbox Store" must be the exact name as it appears in ESM under the First Storage Group.

-DomainController specifies a DC in the source or old EX2000/2003 domain.

-TargetDatabase is your new Ex2007 server and must be "servername\Mailbox Database"  The "Mailbox Database" is the default name and should work unless it was changed.

-ResultSize Unlimited tells the Get-Mailbox command to list all the mailboxes in your org, unfiltered.

Run the Get-Credential and Get-Mailbox commands above (customized for your setup) to confirm that it works before proceeding.

save your working Get-Mailbox command.

Next a Move-Mailbox command must be built.

The default command looks like:

Move-Mailbox -TargetDatabase "Ex2007servername\Mailbox Database" -SourceForestGlobalCatalog server.domain.com -SourceForestCredential $c

-TargetDatabase is the Exchange server you are moving to.
-SourceForestGlobalCatalog is a 2003 Global Catalog server FQDN. !!YES IT MUST BE 2003!! I had to install one in my 2000 domain to get this to work but first had to deall with forestprep and domainprep issues.
-SourceForestCredential is another call to your $c variable which is your EX2000/2003 domain admin account.

Now the Get-Mailbox command needs to be piped into the Move-Mailbox command and, Presto! Mailboxes migrate.

Get-Mailbox -Credential $c -Database "Exch2003Server1\DB1" -DomainController server.domain.com -ResultSize Unlimited | Move-Mailbox -TargetDatabase "Ex2007servername\Mailbox Database" -SourceForestGlobalCatalog server.domain.com -SourceForestCredential $c

HI ,

I have migrated windows 2003 to windows 2008.Its successfully migrated.

Second phase i have a plan to migrate exchange 2003 to exchange 2010.

My current setup

windows 2008 64bit (DC)

exchange 2003 sp2

This  is my plan to migrate.But  i have a doubt in installing exchange 2010 in this scenario.

Is it necessary to use Setup.com /PrepareLegacyExchangePermissions,

Please help me what excactly i have to do