We upgraded to exchange 2010 and this broke an old java based script that connected and sent out e-mail messages. Many hours later we still can't get exchange to work like exchange 2003 did. That hope was abandoned and we decided to create a linux postfix server to forward the e-mail from the old system to exchange, eliminating exchange on the java side.
I am preparing to setup a new install of Exchange 2010 can anyone point me to a good resource to help me do this?
The reason for the install is our current exchange 2003 is 8 years old and needs to be replaced.
I have a couple of servers that I can use as a test environment, I have created a brand new domain and I want to install and configure exchange 2010 on the other, but I don't want it to i
In our organization we are running Exchange 2003 and 2010 simultaneously, with the hopes of migrating everyone to Exchange 2010 sometime within the next few months. Everyone is using Outlook 2010.
Recently, we had an issue with transaction log storage on the Exchange 2003 server.
I am setting up Evolution to access and sync to my Exchange 2010, over Ubuntu 12.04. Evolution accesses the Exchange and downloads messages from Exchange and my calender and contacts, but will not send messages. I have entered and ticked Remember Password.
Would like some advice on an exchange 2010 query.
We would like to be able to monitor the archiving activity of our new exchange 2010 ecosystem.
I have installed Exchange 2010 Standard Trial edition, into our Exchange 2003 environment. And now, for licensing, I've been provided a completely separate ISO download, volume-licensed for Exchange 2010 Enterprise.
I remember reading about how it's possible to add scripts or commandlets to Exchange 2010... in a way that as soon as Powershell imports the remote commands, your custom command is available as well.
My thought is that I'll use Exchange's roles to allow constrained / elevated access to certain functionality thought this technique.
Does anyone know the name of the thing Im thinking of?
Autodiscover on Microsoft Exchange 2010 can’t be used in my environment, due to the migration and consolidation of an email domain. As this e-mail domain is used in multiple exchange forests as an authorative e-mail domain, if we would enable autodiscover this would result in clients connecting to the newly build exchange 2010 environment prior to the users being migrated.
Is there a way to exclude the sender from delivery on distribution group emails when try are a member of that group in Exchange 2010? This was easy with a simple checkbox in Exchange 2003, but googling I can find no simple way to do this in Exchange 2010.
Email this page
