SBS 2008 to 2011 - Forgot to Remove Exchange

Argh! Following the doc for SBS 2008 to SBS 2011 migration. I guess I lost my place.... Went to demote server, I had to remove Certificate Authority first. The instructions for this were AFTER removing Exchange, so I did the Certificate
stuff, FORGOT about Exchange, and kept going....
Since my 21 days were up, I simply shut off the old server.
IN Exchange, the main mailbox, the Outlook Address Book Offline, Public Folders, etc, are all on the new server. When I run the EMC, it does list the 2nd server.
Since I am out of time, have already removed AD from the source server, how much pain do you think this can cause if we just keep the old server off, and cross our fingers?? How bad would it be to turn on the Source Server, reinstall AD services, THEN
remove Exchange, then AD? Would re-adding AD screw up everything?
Appreciate any comments (except telling me to RTFI, lol. Believe me, I wish I had).

No one? I was hoping some sort of MVP or MS Employee would at least offer an opinion as to how bad this is....

Similar Messages

How can I edit the way autodiscover.xml behaves in SBS 2008 and 2011?

I have autodiscover working correctly on a few SBS 2008 and SBS 2011 servers. But, its doing its usual misbehaving. When setting up a new Outlook profile, the user enters their email address and password. Autodiscover is successful in creating all
the account settings, but at the end of the wizard a username and password window pops up with the users full email address incorrectly filled in as the username, which is why it didn't work.
This has always been so annoying about SBS. The user then has to be told to delete their email address in the username field, then fill in "domain\username" instead. Only then is the authentication successful.
I've read lots about people adding the external domain UPN Suffix to ADD&T, then manually changing ever users login to domain.com instead of domain.local.   Then you have to mess with the owa authentication settings in exchange to accept the
UPN.   Its all too ridiculous. There must be a simpler way.
I have read about how you can control how the autodiscover.xml behaves, and there are examples of how to do it in this document:
https://docs.google.com/viewer?a=v&q=cache:0jap1FNKgV0J:https://support.quest.com/Shared/Images/SOL51188_Outlook%2520Automatic%2520Account%2520Configuration.doc+&hl=pl&gl=pl&pid=bl&srcid=ADGEESjizUeFf-JYaM7ZdfIgUCKMMXtcCl0Y3pknFbuwd64GNHIEP1K8a_mpg2YIEisP6sz5DzbtVtdW4Pc42PE0Kjd6bz-3vXz0iaQm7FKi0AnwgvFG_41ZAkBLWynaJtf8s8xyi_d2&sig=AHIEtbSie1mEHTn8el4DPquNxrpovwknUQ
The document above shows the settings we need to change. It looks like we can add the local domain using DomainName into the autodiscover.xml and this will stop autodiscover reporting that the full email address is required.  So we
should be able to get autodiscover to populate the username pop-up with with "domain\user" automatically.
OK, so my question is, how on earth do I edit these settings in SBS 2011? I can't find any articles that talk about how to edit autodiscover.
If I could just edit this one setting (that Microsoft should have correctly configured in the first place) autodiscover will work perfectly for all existing users and all future users, without having to do anything.

Just to straighten out a few things;
1) This is NOT a bug, rather by design. Not every active directory has an exchange server in place, and MS is assuming you don't want to give your internal domain name out to people (which is why it doesn't default to domain\username)
2) Going on what I said in 1), this is NOT SBS specific this is the same way with every Active Directory/Exchange install, keep in mind Microsoft did NOT specially design the software for SBS, they just bundled it into a supported configuration in a neat
little package -since the Exchange server we run on SBS is the same Exchange server powering hundreds of hosted email providers -it makes sense why autodiscover doesn't provide the domain\username (imagine what a mess that would be!)
3) I understand it's a little bit time consuming but it can actually be done for all users in a matter of seconds, select all users, right click and go to Properties, you can then choose the UPN Suffix for all users. When a new user gets created one of the
settings in the wizard is the UPN suffix and is easily changeable as long as you notate for the person creating the user to do it. (The problem here is if you're using the SBS Console instead of AD to setup the User in which case that's just an oversight
in design not a bug in the programming)
4) You can most certainly have a powershell script that changes the UPN suffix from A to B, let me know if you're interested I'll dig one up for you. That can be run on a scheduled task and will solve the remaining issues you have :)
I do see you mentioned it in number 3, I must have missed since I didn't re-read the OP before posting the article, however I just tested on several SBS 2011 machines and OWA authentication settings don't have to be changed at all, this worked immediately
for Outlook Anywhere and Outlook Web Access in my lab and two different customer production systems.
-GreenlightTech

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

Best/Safest way to P2V a SBS 2008 Server to sit on Hyper V

We have used Double Take when we did our P2V migrations to Hyper-V. We did it during office hours and didn't get any downtime.

After doing a lot of searching I managed to find that Microsoft have released an updated Version of MVMC (Microsoft Virtual Machine Converter 3.0). This new version now includes the ability to do a Live Physical to Virtual conversion.Previously they had removed this feature from SCVMM 2012 R2 and as a result I was going to do a Disk2VHD of the SBS 2008 server and then load that into Hyper V.But after doing more research I am thinking that doing a Live P2V on a SBS 2008 is risky as its got Exchange, SharePoint and other programs that change constantly.I am worried that even if I disconnect the server from the network and P2V it that something might change and I won't get a 100% carbon copy.As such I am thinking of taking an image of the Server using something like Acronis True Image Universal Restore boot CD and then restoring the image...
This topic first appeared in the Spiceworks Community

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

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.

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.

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.

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

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

Accidently removed a mailbox on the SBS 2008 server during the migration from SBS 2003

I accidently removed a legacy mailbox from the SBS 2008 server while still doing the migration from SBS 2003. I meant to click on the Move Mailbox like the instructions said but clicked on the Remove option, then clicked the 'X' to close the box since
I figured that would cancel what I did however it removed the mailbox from the SBS 2008 list.
Please tell me that I can get it back. It still shows up in the old SBS Exchange System Manager but now when an email is sent, it sends back a no delivery message. It's like the account doesn't exist any more.
Can it be recovered and if so, how?
thanks,
Jeff

Hi Jeff,
Would you please let us know current situation of this issue? Just check if above suggestions can help you.
If any update, please feel free to let us know.
In addition, please also refer to following article and thread, and then check if can help you.
How
to use a Recovery Storage Group in SBS 2008
How
to recover a deleted user and mailbox on SBS 2008
Hope this helps.
Best regards,
Justin Gu

Migrate SBS 2008 with exchange 2007 to office365

Hi, we have a sbs 2008 with exchange 2007 the boss got the idea to move the E-mail to office 365, i have done some research but still have some questions, now i am not an expert on exchange, could some one tell me if this is a straight operation going from
exchange 2007 to office 365, is it supported or do we have to move to exchange 2010 and then to office 365?
Thank you very much in advanced.

Yes, going from Exchange 2007 to Office 365 is supported. You want to run a Migration.
Check out this link for exact instructions on what to do for the migration:
http://help.outlook.com/en-US/140/ms.exch.ecp.emailmigrationwizardexchangelearnmore.aspx
Then, when you are ready to setup Outlook with Office 365, check out this link to make Outlook use the public Autodiscover rather than SBS Autodiscover:
http://www.mcbsys.com/techblog/2011/08/using-office-365-in-an-sbs-2008-environment-take-2/
I just did a cutover migration from SBS 2008 to Office 365 using both these websites and it went off very nicely.
Good luck on your migration.
Oh, and if you only use Office 365 for email, it is $4 a month per user.

Migration from exchange SBS 2008 to Microsoft exchange 20013

i have started an upgrade of an SBS 2008 to an exchange 2013
i installed the 2 server in coexistence and moved all mailboxes as well as all public folders
what should i do next to be able to decommission the SBS and turn it off completely
PS: our company does use third party certificate as all the users are local users on TS server
much appreciate it

Please follow the Microsoft Exchange Server Deployment Assistant
which is web-based tool that asks you a few questions about your current environment and then generates a custom step-by-step checklist that will help you deploy different versions of Exchange Server for different types of scenarios.
http://technet.microsoft.com/en-in/exchange/jj657516.aspx
Exchange Queries

I have a serious contacts redundancy problem. First I have multiple email account formats, e.g., 2011 MacOutlook, 2008 Entourage, 2007 Window Outlook, iPhone Exchange and these are all connected to the same account. The problem is I had up to 15 contact

I have a serious contacts redundancy problem.
First I have multiple email account formats,e.g., 2011 MacOutlook, 2008 Entourage, 2007 Window Outlook, iPhone Exchange and these are all connected to the same account. The problem is I had up to 15 contacts for the same person.
I deleted the Entourage contacts as that seemed to be the program that was causing the problems. When I synced this morning, now all my contacts are gone from every where.
How can I restore to my last back? If I restore, it will ask to restore to the back that was just made… which has no contacts?
Help would be greatly appreciated !!

I have a serious contacts redundancy problem.
First I have multiple email account formats,e.g., 2011 MacOutlook, 2008 Entourage, 2007 Window Outlook, iPhone Exchange and these are all connected to the same account. The problem is I had up to 15 contacts for the same person.
I deleted the Entourage contacts as that seemed to be the program that was causing the problems. When I synced this morning, now all my contacts are gone from every where.
How can I restore to my last back? If I restore, it will ask to restore to the back that was just made… which has no contacts?
Help would be greatly appreciated !!

Revoked Certificate on Outlook 2010/Exchange 2007/SBS 2008

Hi All,
I have an issue that has been frustrating me for quite some time now.
Our setup is SBS 2008 with Exchange 2007. 2 Weeks ago we had to renew our certificate for remote.xxxxxxx.com. This was done through the SBS consoles > Network > Fix my Network and followed the wizard. and this worked fine.
I have however got one user who has a problem and he informs me that this is been an issue since before the cert was renewed.
He is a remote laptop user who visits the office maybe 5 times a month. When launching Outlook 2010 on his machine (Win 7 x64) it comes up with the error: Security Alert, Information you exchange with this site cannot be viewed or changed by others. However,
there is a problem with the Site's security certificate. (Red X) The security certificate for this site has been revoked. This site should not be trusted. Then OK and View Certificate buttons.
I have tried to use the View Certificate to install the certificate to the correct store but no luck. Also tried exporting the cert from the server and installing manually into Trusted Root CA, via MMC Certificates Snap-In and no luck.
I'd like to mention that If i log into a different user, on the same domain, on the same laptop, the issue is gone. So it's local to his profile on the laptop.
Plus, he cannot access the OWA on his laptop either, but again a different user - same laptop can. I have verified that the OWA is still working from another machine in the business, that is using the same certificate. I cannot understand why the
subject machine thinks the certificate has been revoked when I don't believe it has.
Can anybody please shed some light on this situation for me - any avenues to explore would be hugely appreciated.
Many thanks
Nicky

I hope this helps
http://www.msexchange.org/articles-tutorials/exchange-server-2007/management-administration/managing-exchange-certificates-part2.html
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

SBS 2008 to 2011 - Forgot to Remove Exchange

Similar Messages

Maybe you are looking for