Install problem Exchange SP3 on SBS 2008

I'm unable to install Exchange SP3 on SBS 2008 running Exchange 2007 SP2. I get the following error message:
Failed to initialize the logfile: Access to the path C:\ExchangeSetupLogs\ExchangeSetup.log is denied.
Setup will not continue.
Can anybody tell me how to solve this issue?
Tom.

Hi Tom,
From your error description, I recommend you do the following steps for troubleshooting:
1. Please ensure you run the setup as a local admin at first.
2. Please disable UAC and then install Exchange 2007 SP3. We cannot install Exchange 2007 while UAC is enabled.
Hope it helps.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Similar Messages

Unrecognized certificate when Outlook 2010 tries to connect to Exchange 2007 on SBS 2008

Hi all,
I believe this is a security issue rather than a connectivity or configuration problem.
Running Outlook 2010 on Windows 7 trying to connect to Exchange 2007 on SBS 2008, I receive the following error:
"The name of the security certificate is invalid or does not match the name of the site"
When I view the certificate I see that it was issued to "zx-server" by "zx". This is NOT my domain CA nor is it a certificate I recognize. I use a self-issued certificate (i.e. issued by the SBS box). I also receive this certificate error when I browse to
the internal website (companyweb). No other computers on the network are seeing this behaviour.
I have checked the certificate stores in certmgr and I can't find any such certificate or CA. I have also searched the entire hard drive with no luck. I have run Kaspersky AV, Malwarebytes and MS Security Essentials several times but I can't find any malware.
I also recently installed Comodo Firewall (the problem began after this).
I need to find and remove the certificate and prevent it from being presented to me every time I try to connect to the server. All help, advice and suggestions appreciated.
Aide

Hi,
It’s really a common issue.
This issue occurs if the following conditions are true:
You replace the default self-signed Exchange Server 2007 or Exchange Server 2010 certificate with a different certificate.
Note The Setup program in Exchange Server 2007 or in Exchange Server 2010 creates a default self-signed certificate when Exchange Server 2007 or Exchange Server 2010 is installed.
The common name on the replacement certificate does not match the fully qualified domain name (FQDN) of the URL that is stored in the following objects:
o
The Service Connection Point object for the Autodiscover service
o
The
InternalUrl attribute of Exchange 2007 Web Service (EWS)
o
The
InternalUrl attribute of the Offline Address Book Web service
o
The
InternalUrl attribute of the Exchange unified messaging (UM) Web service
By default, the URL that is stored in these objects references the NetBIOS name of the server. For example, a URL that resembles the
following URL is stored:
https://NetBIOS_name.contoso.com/autodiscover/autodiscover.xml
This may differ from the host name that is used in the FQDN of the replacement certificate. For example, the replacement certificate
may have an FQDN that resembles the following FQDN:
mail.contoso.com
This issue causes a name mismatch error to occur. Therefore, you receive the security warning message when you try to connect Outlook
2007 to the mailbox.
For more detailed information about the procedures to fix the issue, please refer to the following KB article:
Title: Security warning when you start Outlook 2007 and then connect to a mailbox
that is hosted on a server that is running Exchange Server 2007 or Exchange Server 2010: "The name of the security certificate is invalid or does not match the name of the site"
URL:
http://support.microsoft.com/kb/940726
Regards,
James
James Xiong
TechNet Community Support

Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

I'm trying to remove Exchange 2007 from an SBS 2008 server
(Server 2008 Standard FE). My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers. We have two full blown DC's in the environment.
I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server. I can NOT seem to find a TechNet article that shows me how
to proceed in this kind of scenario. I am trying to use the TechNet article:
http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard.
When I go to Disable Mailboxes I get the following error:
Microsoft Exchange Error
Action 'Disable' could not be performed on object 'Username (edited)'.
Username (edited)
Failed
Error:
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
OK
I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010. I just want
to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
Can someone point me in the right direction?
Thanks!

Hi,
Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
On current situation, please refer to following articles and check if can help you.
Transition
from Small Business Server to Standard Windows Server
Removing SBS 2008 –
Step 1: Exchange 2007
Removing SBS 2008 – Step 2:
ADCS
Removing
SBS 2008 – Step 3: remove from domain / DCPROMO
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Hope this helps.
Best regards,
Justin Gu

Outlook 2010 Will Not Connect to Exchange 2007 on SBS 2008 Server

Good Morning,
I have a user who cannot connect to the exchange server on SBS 2008 with outlook 2010. When they start outlook, it shows disconnected and will not connect for a minimum of 20 minutes to an hour. Any suggestions on how to fix this would be appreciated.
I have rebuilt their profile, but that does not fix the issue.
Thank you,
Lee F.
Lee Feldman SMB Consultant

Hi,
Thanks for posting in the forum.
Regarding the current issue, since you have recreated the user profile without any issue, I suspect that it’s mainly caused by the network issue. At this time, please first check the TCP/IP
configurations as Larry mentioned. Then, please also refer to the article below for details about how to troubleshoot Outlook connectivity issue.
Troubleshooting Microsoft Exchange: Outlook Connectivity Issues
http://blogs.technet.com/b/mspfe/archive/2011/04/12/troubleshooting_2d00_microsoft_2d00_exchange_2d00_outlook_2d00_connectivity_2d00_issues.aspx
Hope this helps.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Andy Qi
TechNet Community Support

Problem connecting to MS Exchange 2007 on SBS 2008

I am having problems connecting to Exchange via cfexchangeconnection. Our ColdFusion environment is CF9 Enterprise on Win 2008, and the Exchange host is Win SBS 2008 (which uses IIS7).
After having worked through the documentation and following all procedures outlined at
http://help.adobe.com/en_US/ColdFusion/9.0/Developing/WSc3ff6d0ea77859461172e0811cbec14f31 -7fed.html
plus googling intensively, we have the following method to test the connection
<cfexchangeconnection action="open"
         connection="thisExchangeConnection"
         server="portal.mydomain.com"
         protocol="https"
         formBasedAuthentication="true"
         formBasedAuthenticationURL="https://portal.mydomain.com/owa/auth/owaauth.dll"
         mailboxname="myMailBox"
         username="myUsername"
         password="myPassword" />
<cfdump var="#thisExchangeConnection#">
<cfexchangeconnection action="close"
         connection="thisExchangeConnection" />
The IIS7 implementation in SBS 2008 is quite a lot different to Win 2008, so there are some question marks around some steps in the above documentation. However, we have made sure that:-
1) you can use the credentials above to login via a web browser
2) WebDav is on in IIS
3) there is no IWA and forms based authentication is on
4) certificates are installed correctly on both the CF and Exchange servers
5) the myUsernameaccount has correct permissions in iis/owa/exchange
Despite this, the net result is always
Access to the Exchange server denied.
Ensure that the user name and password are correct.
From research it seems that a lot of people have issues where the underlying problem is actually an Exchange 440 timeout error where the password in the IUSR_<servername> and IWAM_<servername> (IIS/Active Directory) is out of sync.
I was pinning my hopes on the above being the problem but now I find that in SBS 2008 there is no IWAM_<servername> server account.
All this leads me to ask is SBS 2008 actually compatible with the cfexchange tags in CF9? There is nothing in the documentation that I can find that syays that it isn't, but given the amount of time we've spent on what should be straightforward I am wondering if we are on a hiding to nothing. Anyone from Adobe care to comment?
If anyone has managed to get this to work specifically with SBS 2008, or has any advice I'd be grateful to here from you.

Hi,
As said by Sneff , I would also recommend to enable Logging to get more detailed information. Also follow
Configuration of POP/IMAP on SBS 2008 Refer to :
http://blogs.technet.com/b/sbs/archive/2008/09/19/how-to-configure-sbs-2008-to-host-pop3-imap4.aspx
http://blogs.technet.com/b/sbs/archive/2011/08/31/how-to-configure-outlook-for-pop3-imap-and-smtp-connectivity-in-sbs-2008-2011-standard.aspx
As per the error code, you need to follow
http://support.microsoft.com/kb/813514/EN-US
I would also disable AV on both Client machine and TEST , including the Filters of AV.
Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Onsite Scanner Unable To Send Documents Through Exchange 2007 Server (SBS 2008)

I have an SBS 2008 server complete with Exchange 2007 in house and have configured Exchange 2007 to use the Exchange Online Protection (EOP) to process mail for malware, etc. This setup has worked great for the last year or so with no issues.
However, all of a sudden in the last couple of weeks our onsite copier can no longer send documents through email to anyone within the organization. The copier is a Kyocera TaskAlfa 3050CI and exists with the same network. The copier can scan
to a network folder without issue.
If I change the SMTP settings to use a gmail account instead of a local account I can send mail to outside email address. Even with this changed though I still can't send to our domain addresses.
I tried running a message trace from the Exchange Management Console but it doesn't find anything for hte given subject or date/time when I scanned the document.
I am not exactly sure what I should be checking or what piece of the puzzle is causing the problem here. Any ideas on what might be happening or how to correct it?
Thanks so much!

Hi,
Any update? Would you please let us confirm some questions as Howtodo mentioned. Please feel free to let us
know.
Based on your description, it seems that only the copier can’t send documents via emails. On your SBS 2008
environment, please check if some user accounts encounter the similar issue. In other words, did users also can’t send emails attached with documents? If the email was attached with a small size document, will the same result?
In addition, can find any relevant error or events?
Hope this helps.
Best regards,
Justin Gu

Removing Exchange 2007 from SBS 2008 after Migrating to Office 365 Mid Sized with DirSync and SSO

We have recently completed off a Migration of Exchange 2007 to Office 365 Mid Sized platform.
I now need to decomission the old SBS 2008 server as they have moved to a Windows Server 2012 R2 server setup for DC, File and print and application servers.
I need to know what are the ramifications of removing the Exchange 2007 server from the SBS 2008 server and will this remove the LegacyDN details from AD and cause any issues with internal emails between users using Outlook linked through to Office365.
I understand that after removing Exchange 2007 there will be no friendly GUI to update and maintain proxyAddress, targetAddress and LegacyDN addresses, I am comfortable doing this in ADSI edit or with a script.
Will this remove the x500 addresses relating to the on premise Exchange Orgainisation and just leave behind the x500 addresses for Exchange Labs which I assume is the x500 addresses for the Azure AD intergration for Office365.

Hi ,
Thank you for posting your issue in the forum.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

IIS SMTP instead of Exchange 2007 on SBS 2008

We have recently moved a client from Exchange 2007 on a 2008 Small Business Server over to Office 365. We would like to disable Exchange 2007 altogether in order to free up resources on an already overworked server. However, we have a couple of multifunction
devices that require an unauthenticated SMTP relay for email. I believe the easiest solution available to us is to enable SMTP in IIS and limit the relay to certain internal IPs. Assuming Exchange is fully disabled, would this be a viable solution? Given that
we are still running IIS internally, I would see this as a net gain in terms of system resources.

It is not possible.

Upgrade exchange 2007 to exchange 2013 on SBS 2008

Hi,
I need to upgrade EX07 to EX13 on small business server 2008, So I am looking for the documents or steps which will help in Implementation.
Thanks in advance!
-av

Hi,
Any update about the issue?
In-place upgrade is not possible. According to the MS article:
When you're upgrading your existing Exchange 2007 organization to Exchange 2013, there's a period of time when Exchange 2007 and Exchange 2013 servers will coexist within your organization. You can maintain this mode for an indefinite period of time, or
you can immediately complete the upgrade to Exchange 2013 by moving all resources from Exchange 2007 to Exchange 2013, and then decommissioning the Exchange 2007 servers. You have a coexistence scenario if the following conditions are true:
Exchange 2013 is deployed in an existing Exchange organization.
More than one version of Microsoft Exchange provides messaging services to the organization
Upgrade from Exchange 2007 to Exchange 2013
https://technet.microsoft.com/en-us/library/jj898581%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

SBS 2008 & Forefront Exchange 2010

Uninstalled the Forefront for Exchange that ships with SBS 2008 and installed the new Forefront 2010 for Exchange. Everything works great but I have a problem with the SBS Console alert. In Forefront Exchange 2010, the Forefront engine takes over the anti-SPAM function from Exchange and that is a good thing, but now the inherent SBS 2008 console has an error message under SECURITY for "Spam protection for E-Mail" as CRITICAL. I know what the problem is but I do not know how to disable the alert. Now that Excahnge is no longer handling anti-SPAM, the SBS server sees the function inactive and issues an alert sice it is unaware that that role is now filled by the Forefront 2010 anti-spam engine. Is there a method do disable the SBS Consoel alert on the SECURITY tab? Everything is working great with Forefront Exchange 2010 on SBS 2008 other than this little alert that is bugging me.
Thanks to anyone out there that has any insight on this...

GaryD9, on this thread:
http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/67eea70a-5ed8-49ae-ba06-6abb2673f38e
posted a detailed answer which worked for me, as far as the Console alert goes. It doesn't fix the emailed reports. I'll copy it here incase that thread becomes unavailable:
the CAUSE of the error is that the MS Exchange "content filter" is turned off in favor of the forefront content filter when forefront is installed. The SBS console is still looking at the Exchange filter status (which is now off) and is generating an
error. On my SBS 2011 server, the cause of this is a file named "E12AntiSpam.xml" in the "C:\Program Files\Windows Small Business Server\Data\SHExtensions" directory. Within that file, there is probably a line such as
$(Get-TransportAgent "Content Filter Agent").Enabled
The fix can be as simple as changing the line to:
$(Get-TransportAgent "FSE Content Filter Agent").Enabled
(just inserting "FSE " in the front of the agent name)
It should be noted that you can't edit this file unless you open it from Notepad after right clicking
on the shortcut for Notepad and selecting "Run as Administrator". Also, you won't see any changes until you close and re-open the Windows SBS Console.
I'm a little concerned that removing the FSE.XML file (as proposed on the SBS forum) may stop ALL error
reporting rather than just changing the source from the regular content filter to the Forefront version. This solution of editing the E12AntiSpam.XML file seems a safer bet.

SBS 2008 to Exchange 2013 - "Create legacy Exchange host name"... Single External IP?

Migrating a customer to Exchange 2013 from SBS 2008.
Once of the Pre-reqs is to setup an external A record for legacy.customer.com for the external IP address of the old Exchange server.
The customer only has a single external IP address...
So what do I do for this external DNS of legacy.customer.com?

Hi Allister -
You shouldn't need an EXTERNAL dns entry for legacy. Here's how it works:
Client from outside -> External IP to Exchange 2013 (now here's where the interesting thing happens)
Exchange auto-magically proxies mailboxes on the old environment. Reason being: New Exchange Servers always know how to get to old servers. You just change all the internal URLs to legacy. (or you can even do oldmail., whatever you like) and since this information
is inside AD, Ex2013 will find it.
These are the URLs you need to change in 2007/2010
ClientAccessServer
webservicesvirtualdirectory
oabvirtualdirectory
owavirtualdirectory
ecpvirtualdirectory
ActiveSyncVirtualDirectory
AutodiscoverVirtualDirectory You can read more on how to set these here:
http://social.technet.microsoft.com/wiki/contents/articles/5163.managing-exchange-2010-externalinternal-url-s-via-powershell.aspx
Here's the Million dollar question though: being SBS 2008, does this have exchange 2007 or 2010 on it? If it's 2010, you don't need the legacy namespace anymore. 2007, you do. Connect to https://ex2013server/owa and log into a mailbox on the 2010 environment.
If you can get there (you'll know cause it flipped over to a 2010 interface) then it's working.
A wise man is a fool, with a good memory.

Can two servers running windows sbs 2008 be on the same network

I have two HP proliant dl360 servers. We are trying to set up one as a file server. Can we install a copy of Windows sbs 2008 on both machines (we have the license) in the same network

Hi
Every one is quite right you can not install SBS2008 on both machines. Only 1 server on a network can have SBS on it.
However all you need for the second file only server is Server 2008 (it doesn't need to be SBS)
Things to investigate
1. If you have a license for SBS2008 you may run Server 2008 on other servers with no additional client licenses (if you install server 2008R2 or higher on a second or more servers, you will need both SBS2008 and Server 2008R2 client licenses for each user)
So client licenses are sorted
2. If you already have 2 copies of SBS2008 for install, you may find you can downgrade SBS2008 to server 2008 (you will need to double check this, but generally means you can install Server 2008 without having to spend the extra money as you already have
paid for the SBS2008)
3. You may find a old retail copy of Server 2008 on ebay you can buy
Generally the solution to this is, SBS2008 goes on the most powerful server, and is set up as the domain controller, exchange etc.... then on the second server you just install Server 2008 and join it to the domain to be controlled by SBS2008 server, you
don't need to worry about extra CALS, as long as you stay Server 2008 or under
You then set up this second server independently with backups, shadowcopies and shared folders
Group policies for both are configured on the SBS box so you can set up predefined mapping etc
The difficulty you will have is obtaining the old software
If you uses SBS2011 you can use Server 2008R2 and before with no additional CALS
CALS relate to the core OS used, in SBS2008 it is 2008 in SBS 2011 it is 2008R2
Hope this helps
Tris

Indexing on SBS 2008

I have a client that is having some very odd issues with indexing on SBS 2008.
The primary concern is when they perform a search from a Windows 7 machine, all data being searched is in a network share on the sbs 2008 box, only some of the results are being shown. However if we manually navigate to the same directory the file
searched is clearly there. They have also noted that there are occasions where the search will say no results found - in this case we can also manually browse to the file with no issues.
At this time my leading theory is the size of the index is just too big for this sbs box to handle. So I would like to help them trim down the items being indexed. So the question is:
Will there be any adverse effects if we remove the exchange directory from the index? If so what are they potentially going to be?

Hi,
Regarding the current issue, please let me know if you have installed Windows Search service on SBS 2008? In addition, have you installed the Index Service on it? For details, please refer
to the following articles.
Find Items Faster with Windows Search and Libraries
https://blogs.technet.com/b/sbs/archive/2010/04/05/find-items-faster-with-windows-search-and-libraries.aspx
How to install and configure the Indexing Service on a Windows Server 2008-based computer
http://support.microsoft.com/kb/954822/en-us
Hope this helps.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

SQL Server 2014 on SBS 2008

Hi
Is it OK to install SQL Server 2014 on SBS 2008 which is the only domain controller on the network and will not be demoted in normal circumstances?
Thanks
Regards

Hi Y a h y a,
SQL Server Setup will not block installation on a computer that is a domain controller.
However, for security reasons, we recommend that you do not install SQL Server 2014 on a domain controller. There are some limitations as follows:
• You cannot run SQL Server services on a domain controller under a local service account.
• After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the host computer to a domain controller.
• After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member.
• SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.
• SQL Server Setup cannot create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup will fail.
Reference:
Hardware and Software Requirements for Installing SQL Server 2014
Using SQL Server in Windows Small Business Server 2008 Premium Edition
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

Exchange server 2007 Service Pack problems SBS 2008

I am Running Exchange server 2007 on Small Business server 2008 (SBS 2008). I tried to install SP2 but it fails both windows update and manually. Can anyone first advise me what version I'm currently running?
Help / about form Exchange Management Console displays:
Version 08.01.0436.000
And running repair on Exchange server from programs and features displays 2007 SP1 setup. So I believe SP2 to be next I have also ran SP3 but this fails.
Here is the end lines from a log:
[03/05/2014 08:54:13] [0] Setup will run the task 'uninstall-msipackage'
[03/05/2014 08:54:13] [1] Setup launched task 'uninstall-msipackage -logfile 'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode '24b2c164-de66-44fe-b468-a46d9d5e6b31' -PropertyValues 'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU''
[03/05/2014 08:54:13] [1] Beginning processing.
[03/05/2014 08:54:13] [1] Property 'PackageName' is 'EXCHANGESERVER.msi'.
[03/05/2014 08:54:13] [1] Removing MSI package with code '24b2c164-de66-44fe-b468-a46d9d5e6b31'.
[03/05/2014 09:09:01] [1] [ERROR] Unexpected Error
[03/05/2014 09:09:01] [1] [ERROR] Unable to remove product with code 24b2c164-de66-44fe-b468-a46d9d5e6b31. Fatal error during installation. Error code is 1603. Last error reported by the .msi package is 'Could not open key: UNKNOWN\Components\7ABFE44842C12B390AF18C3B9B1A1EE8\461C2B4266EDEF444B864AD6D9E5B613.
Verify that you have sufficient access to that key, or contact your support personnel. '.
[03/05/2014 09:09:01] [1] [ERROR] Fatal error during installation
[03/05/2014 09:09:01] [1] Ending processing.
[07/05/2014 19:45:17] [0] End of Setup
There is a registry key to match this and The administrator account used for setup has access to it i believe??? What does this log mean?

Hi,
This error indicated that your account missed registry permissions on: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\ 7ABFE44842C12B390AF18C3B9B1A1EE8\461C2B4266EDEF444B864AD6D9E5B613
Please check whether you have permission. You can also check whether the key have permissions inherited from the Parent Key or not.
After changing the permission, please run the setup again.
Best Regards.

Install problem Exchange SP3 on SBS 2008

Similar Messages

Maybe you are looking for