Trying to upgrade a CCR cluster to Exchange 2007 Service Pack 2 in my lab and running into an issue. All cluster resources have been failed to one node, firewall has been started, Remote Registry service restarted... From Exchange Management Shell I type: setup.com /m:upgrade. The only thing returned are the following three lines. "Welcome to Microsoft Exchange Server 2007 Unattended Setup Preparing Exchange Setup Exchange Server setup encountered an error" There is nothing in the event logs and no Exchangesetup.log file is being created. The three lines above are all three displayed almost immediately and returned to prompt. I have searched online but everything I find has some component that failed when they see an error. Any ideas? Thank you.

Hello Dcook, Are we talking about Service Pack 1 for Exchange Server 2007, right? Can you validate the log files created during this process installation? Which are the messages appearing at the end of the logfile located at <system drive>\ExchangeSetupLogs\ExchangeSetup.log?

Anderson, Originally I had the ExchangeSetup.log file in the ExchangeSetupLogs folder from the original install of Exchange but when I ran "setup.com /m:upgrade" I was not getting any new information appended to the log. I then moved all the files out of the ExchangeSetupLogs folder to see if it would create new logs and it does not create logs. I have done a search on the server for ExchangeSetup.log in hopes it was creating it some place else but there is nothing. It seems like the setup is not even attempting to start. I have tried different media in hopes is was the media but that does not appear to be the case. One of the DVDs is the same one used to upgrade my CAS. Any other ideas?

Hi, I did find under the release notes of Exchange 2007 SP1 the following - http://download.microsoft.com/download/5/e/6/5e672458-592a-44a2-b489-11cec19d3c82/RelNotes.htm Streaming Backups Are Disabled By Default in SP1 As part of the continuing Microsoft security initiatives,Exchange2007SP1 introduces a behavior change that is designed to reduce the attack surface on yourExchangemessaging system. This change directly affects remote streaming backups. In the RTM version of Exchange2007, remote streaming backup was enabled by default. This default configuration is less secure because it allows anyone in the domain who hassufficient backup rights to backup an Exchange server. Moreover, data that is backed up remotely is not encrypted, and backups are frequently performed over a public,client-accessible network. In compliance with the Microsoft "Secure by Default" initiative, in Exchange2007SP1the remote streaming functionality is disabled by default. A manual override in the form of the following registry value must be enabled to restore this functionality: Caution: Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem Name: Enable Remote Streaming Backup Type: DWORD Value: 0 = default behavior (remote backup disabled); 1 = remote backup enabled There are two cases in which enabling remote streaming backups is required, as follows: Cluster continuous replication (CCR) environments require remote streaming backup for seed operations, for example, when you use the Update-StorageGroupCopy cmdlet. Third-party applications may require remote streaming backup functionality. Contact your application vendor to determine whether the application requires remote streaming backup capabilities. Not sure if this will help, but we are trying it. Topher

I figured out my issue. I was running the command from within PowerShell rather than in a command prompt. The documentation said command prompt but I was thinking powershell. Would be nice if the setup checked to see if powershell was running and give an error about that if it is rather than just saying it encountered an error.