Exchange 2010 quick q?

Django x2

Django x2

Django x2

Soldato
Joined
28 Sep 2008
Posts
14,187
Location
Britain
I have a user who has access to a Purchasing email inbox. When she sends from this account, it stores the sent message in her normal exchange sent items folder (not the purchasing sent items folder).

Is there a way around this?

Also, I'm looking to add an image as part of the signatures (or disclaimer). Can this be done through HTML?
 
Last edited:
1. You will need to use Outlook VBA to handle this as Outlook automatically saves your sent items in your sent items folder, it doesn't care if you sent the items on behalf of another mailbox or as another mailbox. Something like this would probably work but you should test it first if you can on some empty accounts or something:

http://www.excelforum.com/outlook-p...her-mailbox-in-correct-sent-items-folder.html

2. Not sure on 2010, in 2007 transport rules only allowed for plain text disclaimers. We use Exclaimer Mail Utilities at work to have HTML disclaimers (installed on the hub transport servers) but it may be that you need to use a third party tool which is similar.
 
Thanks Eulogy,

So, I know 2010 allows you to use HTML so if we can HTML the image somewhere that should be ok.

Re the 1st point. Is there a way to deploy this VBA across a userbase?
 
Lucero said:
I have a user who has access to a Purchasing email inbox. When she sends from this account, it stores the sent message in her normal exchange sent items folder (not the purchasing sent items folder).

Is there a way around this?
Click to expand...

I might be looking at this too simply, but use 2 mail profiles??
 
With Outlook 2010 you can have two exchange accounts in the same profile then you can pick which one you are sending from, might be another option.

RE: the other questions you had on my answers, pretty much gave you all the info I had to hand so you may need to investigate those yourself :)
 
Ok, how about this one Exchange gurus...

ActiveSync says it is enabled, but none of the mobile devices connect. We have to CAS role boxes behind a Barracuda NLB. Is this in some way stopping AS from working?
 
You need to ensure all the correct IIS subsites are available externally.

I'd suggest running this:
https://www.testexchangeconnectivity.com/
To diagnose.

On the transport rules, you can do HTML disclaimers, but its limited to 8196 characters long, including the powershell commands it runs in the background to do it. So probably more like 7500 characters if you have a few rules.
 
BoomAM said:
You need to ensure all the correct IIS subsites are available externally.

I'd suggest running this:
https://www.testexchangeconnectivity.com/
To diagnose.

On the transport rules, you can do HTML disclaimers, but its limited to 8196 characters long, including the powershell commands it runs in the background to do it. So probably more like 7500 characters if you have a few rules.
Click to expand...

As far as I know, they are. I've had 2010 installs work out of the box for ActiveSync. I have a feeling the NLBs are causing an issue with the autodiscover.
 
Lucero said:
As far as I know, they are. I've had 2010 installs work out of the box for ActiveSync. I have a feeling the NLBs are causing an issue with the autodiscover.
Click to expand...

What does the tester say from that link?
...although it is likely that the 'cuda is the cause tbh, as you said.
But at least the tester will help you diagnose. :)
 
It says this (for ActiveSync Autodiscover Test)

Code: 
Attempting the Autodiscover and Exchange ActiveSync test (if requested). 
  Testing of Autodiscover for Exchange ActiveSync failed. 
   Test Steps 
   Attempting each method of contacting the Autodiscover service. 
  The Autodiscover service couldn't be contacted successfully by any method. 
   Test Steps 
   Attempting to test potential Autodiscover URL https://mydomin.com/AutoDiscover/AutoDiscover.xml 
  Testing of this potential Autodiscover URL failed. 
   Test Steps 
   Attempting to resolve the host name mydomin.com in DNS. 
  The host name resolved successfully. 
   Additional Details 
  IP addresses returned: 88.208.xxx.xxx 
 
 Testing TCP port 443 on host mydomain.com to ensure it's listening and open. 
  The port was opened successfully. 
 Testing the SSL certificate to make sure it's valid. 
  The SSL certificate failed one or more certificate validation checks. 
   Test Steps 
   Validating the certificate name. 
  Certificate name validation failed. 
   Tell me more about this issue and how to resolve it 
   Additional Details 
  Host name mydomain.com doesn't match any name found on the server certificate CN=DSVR010308. 
 
 
 
 
 
 Attempting to test potential Autodiscover URL https://autodiscover.mydomain.com/AutoDiscover/AutoDiscover.xml 
  Testing of this potential Autodiscover URL failed. 
   Test Steps 
   Attempting to resolve the host name autodiscover.mydomain.com in DNS. 
  The host name couldn't be resolved. 
   Tell me more about this issue and how to resolve it 
   Additional Details 
  Host autodiscover.mydomain.com couldn't be resolved in DNS Exception details:
Message: The requested name is valid, but no data of the requested type was found
Type: System.Net.Sockets.SocketException
Stack trace:
at System.Net.Dns.GetAddrInfo(String name)
at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
at Microsoft.Exchange.Tools.ExRca.Tests.ResolveHostTest.PerformTestReally()
. 
 
 
 
 Attempting to contact the Autodiscover service using the HTTP redirect method. 
  The attempt to contact Autodiscover using the HTTP Redirect method failed. 
   Test Steps 
   Attempting to resolve the host name autodiscover.mydomain.com in DNS. 
  The host name couldn't be resolved. 
   Tell me more about this issue and how to resolve it 
   Additional Details 
  Host autodiscover.mydomain.com couldn't be resolved in DNS Exception details:
Message: The requested name is valid, but no data of the requested type was found
Type: System.Net.Sockets.SocketException
Stack trace:
at System.Net.Dns.GetAddrInfo(String name)
at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
at Microsoft.Exchange.Tools.ExRca.Tests.ResolveHostTest.PerformTestReally()
. 
 
 
 
 Attempting to contact the Autodiscover service using the DNS SRV redirect method. 
  ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method. 
   Test Steps 
   Attempting to locate SRV record _autodiscover._tcp.mydomin.com in DNS. 
  The Autodiscover SRV record wasn't found in DNS. 
   Tell me more about this issue and how to resolve it

Actual domain replaced with "mydomain"

However, I get exactly the same response for an Exchange 2010 domain that I know works so I don't fully know how to interpret the results
 
dunno, can you explain further? I haven't set it up before for the other Exchange 2010 company and their phones connect without issue.
 
For internal clients the SCP is used, this is stored in Active Directory.

For external clients you need to have a DNS record setup for autodiscover.yourdomain.com pointing to your CAS servers. You would also need to have autodiscover.yourdomain.com in your exchange SSL cert.

This article explains in a bit more details about the external DNS:

http://www.shudnow.net/2008/11/18/autodiscover-dns-certificates-and-what-you-need-to-know/

As I said in a previous post can you set up connections manually on the devices? All autodiscover does is retrieve settings automatically, you should be able to point a device manually at the CAS servers for ActiveSync access.

Really this almost entirely depends how people are connecting as well, as I said internally it should all function fine but if the mobiles aren't connecting to an internal wifi or similar they would be considered external devices and as such would use external autodiscover connectivity methods, which it sounds like you don't have?

Another good test is to try the autodiscover tester which is built into Outlook, with outlook open hold left ctrl and right click the small outlook icon next to the clock, you should now get an option on your menu for 'Test E-mail AutoConfiguration'

If you load this and then uncheck the two options for guesssmart you can test your autodiscover is functional by entering a user/pass, in the log it will tell you what it's testing/doing.
 
Ok, cool. I can't set up the mobile devices manually (pointing them to mail.mydomain.com, which is the same as OWA). It just says Unable to open connection to server.
 
You must log in or register to reply here.
Back
Top Bottom