I took on the challenge of upgrading our Exchange environment to 2010. We were running an old legacy Avaya Voicemail system and was a little leery to see how the Microsoft-Cisco environment would co-exist. I was very pleased with the results. Following the documentation listed here I was able to get this up and running.
http://www.microsoft.com/downloads/details.aspx?familyid=68b43d3c-7c84-4c2f-bfd7-98754970d70e&displaylang=en
Post any questions, I am happy to help!
Thursday
The public folder couldn’t be found because there is no exchange 2010 public folder server.
After several fits with getting the public folders to work with Exchange 2010 in OWA I have finally solved this one. I was getting MSExchange ADAccess Events 2161 and 2157 in the event viewer. I had never seen the detail of these errors. After setting the event logging level for Validation to Expert I found more detailed information. Attribute: WindowsEmailAddress: Error message: Could not convert property WindowsEmailAddress to type SmtpAddress. Error while converting string *email address* to result type Microsoft.Exchange.Data.SmtpAddress: *email address* is not a valid SMTP address.
I was able to use ADSI Edit and navigated to Configuration - CN=Configuration, DC=domain, DC=co, CN=Services, CN=Microsoft Exchange, CN=exchange name, CN=Administrative Groups, CN=First Administrative Group, CN=Servers, CN=Server, CN=First Administrative Group, CN=Problematic attribute container.
I went into the properties of this and found mail attribute was the problem. I changed this and and the errors were resolved. Public folders were immediately accessible from OWA 2010.
I was able to use ADSI Edit and navigated to Configuration - CN=Configuration, DC=domain, DC=co, CN=Services, CN=Microsoft Exchange, CN=exchange name, CN=Administrative Groups, CN=First Administrative Group, CN=Servers, CN=Server, CN=First Administrative Group, CN=Problematic attribute container.
I went into the properties of this and found mail attribute was the problem. I changed this and and the errors were resolved. Public folders were immediately accessible from OWA 2010.
Tuesday
Exchange 2010
Recently upgrading Exchange 2000 to Exchange 2010. Whew! What a process. The initial upgrade to Exchange 2003 was a fairly smooth process. The install completed however I ran into a small problem getting the information store mounted after the install was complete. I started looking at the installed program list I found it was still running Exchange 2000 but with System Manager having an upgraded interface. Looking into this further there was a DC on our network which had not been completely removed. I was forced to run DCPromo/ force removal at a previous time. Removing all previous references to this domain controller and starting the Exchange 2003 in-place upgrade was successful!
I then installed Exchange 2010 on a new server running Windows 2008 Server R2, moved over a handful of mailboxes from our Exchange 2003 server and replicated the public folders between the two Exchange Servers. My big issue now is our backups. We utilize Symantec Backup Exec, problem is 12.5 does not have support for Exchange 2010 and the release for Backup Exec 2010 is first quarter of this year. ( If we are lucky) I am stuck trying to decide whether to wait to move the remaining mailboxes or to go ahead and proceed. Currently, I am using Windows Server built-in backup but I am having to manually kick these off.
I then installed Exchange 2010 on a new server running Windows 2008 Server R2, moved over a handful of mailboxes from our Exchange 2003 server and replicated the public folders between the two Exchange Servers. My big issue now is our backups. We utilize Symantec Backup Exec, problem is 12.5 does not have support for Exchange 2010 and the release for Backup Exec 2010 is first quarter of this year. ( If we are lucky) I am stuck trying to decide whether to wait to move the remaining mailboxes or to go ahead and proceed. Currently, I am using Windows Server built-in backup but I am having to manually kick these off.
Subscribe to:
Posts (Atom)