Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration 论坛
Viewing all 7008 articles
Browse latest View live

Office 365/Exchange PST Capture Tool not finding mailboxes

$
0
0

I am trying to use this utility to move the emails/contacts/etc. in some of my local PST files into an email account on Exchange Online (the cloud) through Office 365.

I have set up the "Online Connection Settings" and have connected successfully using the "check" button to my Office 365 global administrative account.

Next I added my PST file using the  "Add from Folder..." button.

The problem is that when I click on "Set mailbox..."( to direct the emails/contacts/etc. to be added to the correct email address in my company) the list never loads, it simply says "The Central Service is retrieving the mailbox data, try again in a moment".

It has been like this for several hours and shows no signs of change.

I need to be able to load .pst files from my old domain into the exchange cloud and NEVER USE THEM AGAIN. This means actually importing the emails, not just adding the .pst file to Outlook.

Please advise why the tool cannot find my company's email addresses and how to fix.

-Joe

P.S: I have already posted this in the Office 365 forums, they gave me the "not officially supported" nonsense and sent me here.




Exchange 2013 Server Migration

$
0
0

Hello,

We are in the process of migrating from an Exchange 2003 server to an Exchange 2013 SP1 server. The EXCH2003 server is in a separate domain environment than the new EXCH2013 server. We plan to export all mail from the EXCH2003 server and import to the EXCH2013 server.

At this time we are seeing an issue with the new EXCH2013 SP1 server. When we test creating a new profile in Outlook 2010 SP2 on a client machine we receive the following errors:

1) The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.

- also -

2) The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.

We are able to access OWA both internally and externally and can login under multiple user accounts. Also while logged into OWA, mail flow is working, able to send and receive.

We installed and configured a new SSL trusted certificate on the Exchange 2013 SP1 server as well.

At this time our main issue is with Outlook 2010 SP2 and Exchange 2013 SP1 not communicating with each other properly.

Please let us know what other information is needed to help resolve this issue.

Thank you,

Jason Ringholz


Regards, Jason

Migration from Exchange 2007 - Move-Request moved Mailbox to Archive Database instead of Mailbox Database

$
0
0

Dear all,

I'm in the middle of migrating from Exchange 2007 to Exchange 2013. So far everything looks good. While migrating a couple of mailboxes via Move-Request cmdlt I received an error that one particular mailbox hasn't been successfully migrated. With "Get-MoveRequest -BatchName "20140821 SBSUsers" | Get-MoveRequestStatistics" I found that error: "FailedOther" in StatusDetail.

With "Get-MoveRequest "Martin Brösamle" | fl" I had a look at its details and it showed me something strange. The contents of that mailbox seem to have been moved to the "Archive Database" instead of the supposed "Mailbox Database" though this particalur didn't even had an enabled Archive in the first place:



So I had a closer look at the details of my whole Batch: "Get-MoveRequest -BatchName "20140821 SBSUsers" | fl DisplayName,Status,TargetDatabase,Suspend,SuspendWhenReadyToComplete", and it showed several migrations being performed into the Archive Database:



I then checked whether these users now have an Archive enabled after the migration process has completed (Get-Mailbox | where {$_.ArchiveDatabase -ne $null})

But that looked normal and as expected; only users previsouly enabled with an Archive were shown here.

So why did Move-Request place the mailboxes being migrated in the Archive Database instead of the Mailbox Database and does this pose a problem?

Any help would be greatly appreciated.
Alex


Alexander Ollischer Diplom-Wirtschaftsinformatiker (FH) Citrix & Microsoft Certified Engineer (CCEA, CCEE, MCSA, MCSE, MCDBA, MCTS) Afontis IT+Services GmbH Baierbrunner Straße 15 81379 München Deutschland Telefon (089) 74 34 55-0 Fax (089) 74 34 55-55 mailto:a.ollischer@afontis.de http://www.afontis.de http://www.itganzeinfach.de Amtsgericht München, HRB 109 005 Geschäftsführer: Thomas Klimmer

Upgrade Windows Server 2012 x64 to 2012 R2 under Exchange 2013 SP1 (aka CU4)

$
0
0

Hi,

is it possible to upgrade Windows Server 2012 to 2012 R2 under Exchange 2013 SP1 (aka CU4) ? I want get rid of all windows servers 2012 and do not want create new host with different name.

Thanks

Exchange 2007 to 2013 Migration / GAL / Address Lists / OAB Not Updating Properly

$
0
0

Hi all,

I am in coexistence with 2007 and 2013, I just finished migrating all my mailboxes over to 2013 as well as Public Folders.

I issued the following commands to update AD Objects:

Get-EmailAddressPolicy | Set-EmailAddressPolicy

Get-GlobalAddressList | Set-GlobalAddressList

Get-AddressList | Set-AddressList

Get-DistributionGroup | Set-DistributionGroup

My address lists / GAL do not seem to be updating on the regular schedule.  When adding new users, they will show up in the All Users address list but nowhere else.

I am having to run the following three commands to manually update everything every day at this point:

Get-GlobalAddressList | UpdateGlobalAddressList

Get-AddressList | UpdateAddressList

Get-OfflineAddressBook | UpdateOfflineAddressBook

Do I need to re-create my GAL or Address Lists at this point?  

 

Error Exchange Server 2010 SP3 Upgrade - OWA Already Exists - Event ID 1002

$
0
0

Hi,

I have a problem with my Exchange 2010 SP1 deploy in Windows server 2008 R2,

I try upgrade to Exchange 2010 SP3, an error happened when step progress CAS role

Error:
The following error was generated when "$error.Clear(); 
          $InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
          new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;
          get-OwaVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController | where {$_.OwaVersion -eq "Exchange2010"} | set-OwaVirtualDirectory -WindowsAuthentication $true;
        " was run: "The virtual directory 'owa' already exists under '(Server Name)/Default Web Site'.
Parameter name: VirtualDirectoryName".

The virtual directory 'owa' already exists under '(Server Name)/Default Web Site'.
Parameter name: VirtualDirectoryName
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp

Error:
The following error was generated when "$error.Clear(); 
          $InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
          new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;
          get-OwaVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController | where {$_.OwaVersion -eq "Exchange2010"} | set-OwaVirtualDirectory -WindowsAuthentication $true;
        " was run: "The virtual directory for the mini version of Outlook Web App can't be found in the same Web site.".

The virtual directory for the mini version of Outlook Web App can't be found in the same Web site.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp


I already try delete owaVirtualDirectory from adsiedit, Exchange management console, and from IIS manager but still it say virtual directory 'owa' already exists in my server.

Can anyone help me how resolve this problem?

Thanks.

 

Best Regards,

Henry Stefanus




auto cad 2007

$
0
0
hello guys, i have installed auto cad 2007 in my computer's volume z but after that i have delete the volume Z without uninstall auto cad 2007. and then i can't install auto cad 2007 again. the computer report that error 1327. can you help me guys?

OWA calendar

$
0
0

We running exchange 2013 SP1 , and when I access owa internally and try to open calendar items I get the following error

"This action could not be completed. An error occurred on the server"

please advise.


Exchange Co-existing Migration not completing (Event ID's 1006 - Mailbox Replication, 2002 - Exchange Migration)

$
0
0

Hi Guys,

a few issues all relating to AD/Exchange Setup that have been driving me crazy for the past month, holding up our exchange 2013 upgrade and our lync implementation..

History:

1. installed new server (Server 2012 R2), installed exchange 2013 install completed properly, issues logging into ecp and owa, ssl certs werent created, created manually didnt solve. - scrapped that server deleted from adsi exchange administration servers

2. fixed ca issues, re-installed server installed exchange 2013, /preparead ,system mailboxes created migration mailbox created, create mailbox db, system mailboxes are there if checked with get-mailbox -arbitration

  • Try to migrate, migration mailbox not found in organization
  • delete all system accounts from ad, recreate with /preparead, enable them according to articles:
  1. http://technet.microsoft.com/en-us/library/gg588318%28v=exchg.150%29.aspx
  2. http://www.telnetport25.com/2013/01/quick-tiprecovering-from-a-missing-migration-mailbox-in-exchange-2013/
  3. http://social.technet.microsoft.com/wiki/contents/articles/5317.recreate-and-enable-missing-arbitration-user-accounts-and-mailboxes-in-exchange-server-2010.aspx
  4. http://social.technet.microsoft.com/wiki/contents/articles/6874.how-to-recreate-system-mailbox-federatedemail-discoverysearchmailbox-in-exchange-2010.aspx
  • get-mailbox -arbitration found all mailboxes, discovery mailbox was there too.

3. Tried migration again no errors in ecp, migration not starting, encountered above error id's

  • Error 2002 - MSExchange Migration
  • error info ('Migration.MigrationMailboxNotFoundException|The migration mailbox for the organization is either missing or invalid.
  • Error 1006 - MSExchange Mailbox Replication (ps: no dag's setup yet either)
  • -> error info ('The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
    Database: CL1-3_Main-DB
  • same error for each db on the server with different mailboxes
  • Error: Couldn't find system mailbox '6d5f301b-7323-47c1-85eb-a76a01b9b3c0' in Active Directory.')
  • Error: Couldn't find system mailbox 'f6ba51f8-c076-42e9-b00f-014a1c6b3634' in Active Directory
  • Error: Couldn't find system mailbox 'SystemMailbox{eae9aad5-0984-440d-b37c-7a399961e171}' in Active Directory.
  • Error: Couldn't find system mailbox '8c6d0335-af32-41e3-86b1-e4c15fd14a23' in Active Directory.
  • Error: Couldn't find system mailbox '8c6d0335-af32-41e3-86b1-e4c15fd14a23' in Active Directory.

SystemMailbox{eae9aad5-0984-440d-b37c-7a399961e171}' is in Active Directory and mail enabled according to above articles.

  • also received this error id 1006 - MSExchangeDiagnostics
  • error info ('The performance counter '\\CL1-3\LogicalDisk(HarddiskVolume17)\Free Megabytes' sustained a value of '207.00', for the '15' minute(s) interval starting at '8/22/2014 7:12:00 AM'. Additional information: None. Trigger Name:DatabaseDriveSpaceTrigger. Instance:harddiskvolume17')

I don't want to reinstall again as i feel that would just add wood to the fire... can anyone help diagnose this?

been trying to fix this myself for over a month.

Thanks!!

Domain controller migration in existing Exchange 2013 configuration.

$
0
0
I have the following scenario: a Windows Server 2003 SP2 DC (schema version 30, Windows Server 2003 native functional level) and an Exchange 2013 SP1 Server. I have to add a Windows Server 2012 R2 DC (upgrading to schema version 69). Could this operation affect the Exchange 2013 SP1 server functionality?

Cross Forest migration Autodiscover

$
0
0

We are attempting to move from a Windows 2008 domain to a new Windows 2012R2 domain (2008R2 forest level). Exchnage 2010 SP3 is in the 2008 domain and Exchange 2013 CU5 is in the 2012 domain.There is only one accepted email domain and it is an internet routable address (eg. com.au) whereas the AD domains are both .local

So we are trying to move mailboxes from an Exchange 2010 org in abc.local domain with amydomain.net.au email address to an Exchange 2013 org in xyz.local domain with a mydomain.net.au email address. The users only have one accepted domainmydomain.net.au, they do not have an abc.local email suffix. We are NOT moving user accounts, this is similar to moving to a hosted Exchange offering.

The problem is with Outlook autodiscover when mailboxes are migrated from Exchange 2010 to Exchange 2013.

This is what has been done:

  • Setup two way trust
  • Configure SSL certificates and get them onto the relevent Exchange servers
  • Configure the SCPs for Autodiscover in both domains
  • Configured and tested all of the DNS
  • Changed the accepted domain to an internally routed domain in Exchange 2010 and configured the same in Exchange 2013
  • Configured Send and Recieve connectors in each Exchange org
  • Used ./preparemoverequest to create new objects in 2012 domain
  • Moved mailboxes from Exchange 2010 to Exchange 2013
  • Accessed moved mailboxes with OWA successfully

Email flows between the two Exchange orgs correctly, out to the internet correctly, and in from the internet correctly. That is, if a user is in xyz.local, mail will come through the smarthost to the Exchange 2010 org, no local mailbox is found so it is sent to the Exchange 2013 org and delivered.

Outlook 2010 SP3 does not reconfigure with autodiscover. If the mailbox is moved while the user is looged on, they get a warning to restart Outlook but it doesn't connect. If the mailbox is moved when the user is not logged on, Outlook doesn't reconnect. Outlook cannot be manually configured to used the linked mailbox in the other domain.

I've read heaps of technet articles, blogs and the Exchange 2013 technet pages on Autodiscover and migration but to no avail. It is a small simple environment, all of the servers are on the same subnet so firewalls are not an issue!

This articel http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/ has been a big help but I need autodiscover after the mailbox is moved.

Thanks

Could not find any available Global Catalog in forest when running RemoteMailbox cmdlet

$
0
0

My current Exchange environment is a hybrid configuration of Office 365, Exchange 2013 hybrid, and Exchange 2007 on-premise.

I have a script responsible for enabling remote mailboxes and assigning O365 licenses to a list of users; essentially provisioning users an O365 mailbox. This script runs every hour through a defined scheduled task in the Task Scheduler.

The script is proven to work but will intermittently throw an error on some days: "Could not find any available Global Catalog in forest root.xyz.com"

Here are the nuances of the error when it does occur:

  1. It will only throw the error when the script is run via scheduled task - the script will work fine if executed from the command line
  2. The error occurs when "Enable-RemoteMailbox" or "Get-RemoteMailbox" is called.
  3. The same error will occur with ANY script that calls "Enable-RemoteMailbox" or "Get-RemoteMailbox" and is ran via scheduled task - even when the RemoteMailbox cmdlet was the only line in the script

Here is the output and error when Get-RemoteMailbox -verbose is ran:

VERBOSE: [15:49:52.474 GMT] Get-RemoteMailbox : Active Directory session
settings for 'Get-RemoteMailbox' are: View Entire Forest: 'True',
VERBOSE: [15:49:52.489 GMT] 
Get-RemoteMailbox : Runspace context: Executing
user: , 
Executing user organization: , 
Current organization: , 
RBAC-enabled:Disabled.
VERBOSE: [15:49:52.489 GMT] Get-RemoteMailbox : Beginning processing
VERBOSE: [15:49:52.521 GMT] Get-RemoteMailbox : Current ScopeSet is: {
Recipient Read Scope: {{, }}, 
Recipient Write Scopes: {{, }}, Configuration Read Scope: {{, }}, 
Configuration Write Scope(s): {{, }, }, 
Exclusive Recipient Scope(s): {}, 
Exclusive Configuration Scope(s): {} }
VERBOSE: [15:49:52.521 GMT] Get-RemoteMailbox : Resolved current organization: .
VERBOSE: [15:49:52.521 GMT] Get-RemoteMailbox : Searching objects "abose" of type "ADUser" under the root "$null".
VERBOSE: [15:49:52.536 GMT] Get-RemoteMailbox : Previous operation run on global catalog server 'evw-xyzdc-p02.ad.xyz.com'.
Get-RemoteMailbox : Could not find any available Global Catalog in forest root.xyz.com.
At C:\IDM_In\Scripts\MinimalTest.ps1:42 char:14
+ $abose = Get-RemoteMailbox 'abose' -verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-RemoteMailbox], ADTransientException
+ FullyQualifiedErrorId : E421EF0B,Microsoft.Exchange.Management.RecipientTasks.GetRemoteMailbox

VERBOSE: [15:49:52.567 GMT] Get-RemoteMailbox : Ending processing

What could be the cause of this intermittent error?

Thanks for any help

Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

$
0
0

Hi Team,

Need urgent help in resolution of following error:

Environment Details: VMware ESX

Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013

Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)

OS: Windows Server 2012 R2 - Standard (Latest Installation Media)

Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)

Prerequisites: Installed

Error: Installation gives Error at Step 10 during installation of Mailbox Service

Error Details Below:

Error:

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

if ([Environment]::OSVersion.Version.Major -ge 6)

{

$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";

$reg= join-path (join-path $env:SystemRoot system32) reg.exe;

$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;

if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))

{

if ((get-service wsbexchange).Status -eq "Running")

{

Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";

}

Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";

}

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";

Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";

}

" was run: "Process execution failed with exit code 1.".

Error:

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

if ([Environment]::OSVersion.Version.Major -ge 6)

{

$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";

$reg= join-path (join-path $env:SystemRoot system32) reg.exe;

$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;

if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))

{

if ((get-service wsbexchange).Status -eq "Running")

{

Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";

}

Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";

}

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";

Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";

}

" was run: "Process execution failed with exit code 1.".

Error:

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

if ([Environment]::OSVersion.Version.Major -ge 6)

{

$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";

$reg= join-path (join-path $env:SystemRoot system32) reg.exe;

$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;

if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))

{

if ((get-service wsbexchange).Status -eq "Running")

{

Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";

}

Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";

}

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";

Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";

}

" was run: "Process execution failed with exit code 1.".

Error:

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

if ([Environment]::OSVersion.Version.Major -ge 6)

{

$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";

$reg= join-path (join-path $env:SystemRoot system32) reg.exe;

$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;

if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))

{

if ((get-service wsbexchange).Status -eq "Running")

{

Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";

}

Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";

}

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";

Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";

}

" was run: "Process execution failed with exit code 1.".

Error:

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

if ([Environment]::OSVersion.Version.Major -ge 6)

{

$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";

$reg= join-path (join-path $env:SystemRoot system32) reg.exe;

$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;

if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))

{

if ((get-service wsbexchange).Status -eq "Running")

{

Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";

}

Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";

}

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";

Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";

}

" was run: "Process execution failed with exit code 1.".

Error:

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

if ([Environment]::OSVersion.Version.Major -ge 6)

{

$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";

$reg= join-path (join-path $env:SystemRoot system32) reg.exe;

$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;

if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))

{

if ((get-service wsbexchange).Status -eq "Running")

{

Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";

}

Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";

}

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";

Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";

}

" was run: "Process execution failed with exit code 1.".

Error:

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

if ([Environment]::OSVersion.Version.Major -ge 6)

{

$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";

$reg= join-path (join-path $env:SystemRoot system32) reg.exe;

$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;

if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))

{

if ((get-service wsbexchange).Status -eq "Running")

{

Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";

}

Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";

}

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";

Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";

}

" was run: "Process execution failed with exit code 1.".

Error:

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

if ([Environment]::OSVersion.Version.Major -ge 6)

{

$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";

$reg= join-path (join-path $env:SystemRoot system32) reg.exe;

$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;

if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))

{

if ((get-service wsbexchange).Status -eq "Running")

{

Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";

}

Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";

}

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";

Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";

}

" was run: "Process execution failed with exit code 1.".

Error:

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

if ([Environment]::OSVersion.Version.Major -ge 6)

{

$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";

$reg= join-path (join-path $env:SystemRoot system32) reg.exe;

$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;

if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))

{

if ((get-service wsbexchange).Status -eq "Running")

{

Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";

}

Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";

}

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";

Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";

}

" was run: "Process execution failed with exit code 1.".

Error:

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

if ([Environment]::OSVersion.Version.Major -ge 6)

{

$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";

$reg= join-path (join-path $env:SystemRoot system32) reg.exe;

$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;

if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))

{

if ((get-service wsbexchange).Status -eq "Running")

{

Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";

}

Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";

}

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";

Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";

}

" was run: "Process execution failed with exit code 1.".

Error:

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

if ([Environment]::OSVersion.Version.Major -ge 6)

{

$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";

$reg= join-path (join-path $env:SystemRoot system32) reg.exe;

$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;

if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))

{

if ((get-service wsbexchange).Status -eq "Running")

{

Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";

}

Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";

}

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d Exchange /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";

Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";

Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";

}

" was run: "Process execution failed with exit code 1.".

Public Folder Migration Failing

$
0
0

Trying to migrate public folders from 2010 to 2013. I keep on getting this error:

 Error: Active Directory operation failed on MCDC02.domain.org. This error is
 not retriable. Additional information: Insufficient access rights to perform the
 operation.
 Active directory response: 00002098: SecErr: DSID-03150E48, problem 4003
 (INSUFF_ACCESS_RIGHTS), data 0
  --> The user has insufficient access rights.
 8/24/2014 2:16:05 PM
 True

I have tried different administrator accounts and they have all the rights: Domain, Exchange, etc....


MCITP Exchange 2010 | MCITP Lync Server 2010 | MCTS Windows 2008

Unable to create a Migration Endpoint when migrating from SBS 2003

$
0
0

We are attempting to migrate a SBS 2003 organization and have trouble creating a migration endpoint. Outlook connectivity tests pass but the migration endpoint cannot be created due to the following error:

The identifier name  cannot be
processed due to the inability to differentiate between the following
enumerator names: Basic, Digest, Ntlm, Fba, WindowsIntegrated,
LiveIdFba, LiveIdBasic, WSSecurity, Certificate, NegoEx, OAuth, Adfs,
Kerberos, Negotiate, LiveIdNegotiate, Misconfigured. Try a more specific
identifier name.

Any help would be appreciated.


OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

$
0
0

Hi,

I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.

We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.

All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa url) also redirects me to https://legacy.domain.com/owa just fine.

HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.

Anyone any tips where to search?

Many thanks in advance.


Best regards and many thanks in advance, Eric Vegter

Exchange Server 2013: Installation fails

$
0
0

Migrating SBS 2008 to Windows Server 2012 R2 (no virtualization) and Exchange Server 2013 SP1

(1) ADprep on SBS 2008 went fine

(2) Installed necessary feature for Exchange (website “Part 1: Step-by-Step Exchange 2007 to 2013 Migration”)

A) the first time I installed Exchange 2013, the setup succeeded, however there were several ecp/WinRM errors.

B) restored Windows Server 2012 R2 to the state (2). Removed from AD (ADSI Edit)

               … CN=Services; CN=Exchange; CN=First Organization; CN=Exchange Administrator Group; CN=Servers delete new Win 2012 server

               

Run Exchange setup again:

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

         if ($RoleStartTransportService)

         {

             start-SetupService -ServiceName MSExchangeTransport -MaxWaitTimeForRunningState 0:0:40

         }

        " was run: "Service 'MSExchangeTransport' failed to reach status 'Running' on this server.".

Checked:

- IPv6 is enabled, but was setup correctly after installing ADDS role)

- Administrators (Group) is a member of the Exch. Trusted Subsystem

Probably there is an AD problem, after the restoration (B) (bare metal) of the Win 2012 server.

Please help!

Fulco

Finish migration 2010 to 2013 with two differents Microsoft nlb cas array

$
0
0

Hi,

I have outsourcing my migration from exchange 2010 to exchange 2013, but the job isn't finish and i'm alone for finish.

The 2010 environnement :

2 cas with nlb.
2 Dag serveur.

There is intergration with 2013 farm like this :

2 cas server with a news cas adresse
2 dag server.

Everythin is publish in TMG.

I can move bal from a database to an other database. The migration can take effect. The action I Don't know is to remove 2010 server after all bal migration, and change CAS NLB adresse (IP and DNS) of the news 2013 exchange serveur.

It's diffucult to apprehend the nlb adress change.

Thank for your help.

Regard

Second Exchange 2013 server in remote site

$
0
0

Just finished migrating from 2007 to 2013 and decommissioned 2007.  Exchange 2013 is running in site A with 350 mailboxes on it.  However, almost half of those users reside in site B so the plan is to introduce a second Exchange 2013 server to this site and migrating mailboxes to it.  There already exists a DC & GC in both sites.

My question is, immediately after I introduce Exchange 2013 into site B with CAS & MBX role, client computers from that site will start to receive certificate errors.  Will updating the SCP on the new exchange server to point to the SCP on the exchange server in site A be enough to mitigate that problem?  What other precautions will I need to take?  Has anybody been down this road?

Setup without "EDGE Server" option

$
0
0

Hi,

I'm setting up the Exchange Services as follow:

We have an Internal Network called "Internal.local" which running 2008r2 in all the servers and I installed Exchange 2013 on another 2008r2 server seems OK that I can send and receive mails within the network.

Now I want to setup an Edge server in the DMZ in order to allow some of the users have external email. The first problem is when I run the Exchange setup, it doesn't have the "Install EDGE Server" option. What should I do???

The second problem is if I continue with the setup, it keep asking for the AD info but I only want to install a standalone server in the DMZ. Did I do anything wrong??

Thanks. 

Viewing all 7008 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>