Exchange 2010: Outlook Anywhere enabled after some accounts were connected via outlook
I had inadvertently left Outlook Anywhere disabled an my first Exchange 2010 install. I had setup 3 users in Outlook 2010 before I realized it. Now I have gone back to Exchange 2010 and enabled it. Still waiting on 15 minute period for it to be done, but the question is: 1) Will I have to do anything with the first 3 clients to get the Outlook Anywhere settings added... will they they pick it up from Exchange automatically or will I have to do something manual? 2) And do future Outlook clients automatically pick it up? 3) I chose NTLM as our users will go nuts keying credentials all the time. Do most of you use NTLM. 4) Do the phones / ipads / androids use outlook anywhere or do they use activesync? Just want to make sure NTLM setting will not screw up remote devices like that from working. Greg --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Exchange 2010: Outlook Anywhere enabled after some accounts were connected via outlook
It looks like the outlook anywhere settings did make it to the existing clients, BUT... I don't know if this is a problem or not, but feel like I cannot move forward without verification. - The existing outlook users I had setup seems to be getting the Outlook Anywhere settings. They all still show SERVERNAME.AD.MYDOMAIN.COM in the server. Even the newly setup Outlook Clients after Outlook Anywhere was successfully enabled on server have the same value. BUT I thought they would all show OWA.MYDOMAIN.COM. I am nervous about continuing if it is showing up WRONG. I checked the settings at another site and it doesn't use server name it, but uses MAIL.THEIRDOMAIN.COM. So I would have expected this site to show OWA.MYDOMAIN.COM instead of SERVERNAME.AD.MYDOMAIN.COM in the server field. - I noticed under client access / owa (Default Web Site) properites it has internal URL https://servername.ad.mydomain.com/owa set and that represents the wrong internal name. I mean yes it is a valid url, but we have a pinpoint dns for owa.mydomain.com and autodiscover.mydomain.comso the internal should be https://owa.mydomain.com/owa. Since we did pinpoint dns that should be same as external right. I checked the other site and it should be the same. It shows the same for internal on the other tabs for ECP, EAS, OAB. I changed them hoping it may fix what was showing up in server for exchange client, but no joy... doesn't seem to make a difference. Need feedback on this. - I did an internet test on autodiscover from Outlook by doing CTRL-RIGHTCLICK on outlook symbol in system tray. I then did the Test Email Autoconfiguration. I can provide the link of results if someone is willing to look at it. Greg On Fri, Jan 25, 2013 at 5:42 PM, Greg Saunders gsaund...@myitanalyst.comwrote: I had inadvertently left Outlook Anywhere disabled an my first Exchange 2010 install. I had setup 3 users in Outlook 2010 before I realized it. Now I have gone back to Exchange 2010 and enabled it. Still waiting on 15 minute period for it to be done, but the question is: 1) Will I have to do anything with the first 3 clients to get the Outlook Anywhere settings added... will they they pick it up from Exchange automatically or will I have to do something manual? 2) And do future Outlook clients automatically pick it up? 3) I chose NTLM as our users will go nuts keying credentials all the time. Do most of you use NTLM. 4) Do the phones / ipads / androids use outlook anywhere or do they use activesync? Just want to make sure NTLM setting will not screw up remote devices like that from working. Greg --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Exchange 2010: Outlook Anywhere enabled after some accounts were connected via outlook
Maybe another way of asking this: Our internal domain is ad.mydomain.com and our external is mydomain.com. Our CAS has been configures so internal and external url is owa.mydomain.com We are using pinpoint dns internally for owa.mydomain.com and autodiscover.mydomain.com since the internal domains differ. All of the tests at https://www.testexchangeconnectivity.com looking the way they should as an external test. I also test internally by using CTRL-RIGHTCLICK on Outlook icon in system tray and choose Test Email Autoconfiguration. This all passes as well. The ONLY thing I think might be an issue is the value for server under RPC is pulling in our actual exchange server FQDN: exchange.ad.mydomain.cominstead of owa.mydomain.com. The test for HTTP has server as owa.mydomain.com. But I believe I should be seeing the same value for RPC. For the life of me I cannot figure out why. I looked at another company/site that I help where they have same configuration and it DOES pull in the same owa.mydomain.com for both RPC and HTTP. So why is mine NOT? Where is it getting the server value for RPC? What am I missing? Thanks in advance! On Fri, Jan 25, 2013 at 8:33 PM, Greg Saunders gsaund...@myitanalyst.comwrote: It looks like the outlook anywhere settings did make it to the existing clients, BUT... I don't know if this is a problem or not, but feel like I cannot move forward without verification. - The existing outlook users I had setup seems to be getting the Outlook Anywhere settings. They all still show SERVERNAME.AD.MYDOMAIN.COM in the server. Even the newly setup Outlook Clients after Outlook Anywhere was successfully enabled on server have the same value. BUT I thought they would all show OWA.MYDOMAIN.COM. I am nervous about continuing if it is showing up WRONG. I checked the settings at another site and it doesn't use server name it, but uses MAIL.THEIRDOMAIN.COM. So I would have expected this site to show OWA.MYDOMAIN.COM instead of SERVERNAME.AD.MYDOMAIN.COM in the server field. - I noticed under client access / owa (Default Web Site) properites it has internal URL https://servername.ad.mydomain.com/owa set and that represents the wrong internal name. I mean yes it is a valid url, but we have a pinpoint dns for owa.mydomain.com and autodiscover.mydomain.comso the internal should be https://owa.mydomain.com/owa. Since we did pinpoint dns that should be same as external right. I checked the other site and it should be the same. It shows the same for internal on the other tabs for ECP, EAS, OAB. I changed them hoping it may fix what was showing up in server for exchange client, but no joy... doesn't seem to make a difference. Need feedback on this. - I did an internet test on autodiscover from Outlook by doing CTRL-RIGHTCLICK on outlook symbol in system tray. I then did the Test Email Autoconfiguration. I can provide the link of results if someone is willing to look at it. Greg On Fri, Jan 25, 2013 at 5:42 PM, Greg Saunders gsaund...@myitanalyst.comwrote: I had inadvertently left Outlook Anywhere disabled an my first Exchange 2010 install. I had setup 3 users in Outlook 2010 before I realized it. Now I have gone back to Exchange 2010 and enabled it. Still waiting on 15 minute period for it to be done, but the question is: 1) Will I have to do anything with the first 3 clients to get the Outlook Anywhere settings added... will they they pick it up from Exchange automatically or will I have to do something manual? 2) And do future Outlook clients automatically pick it up? 3) I chose NTLM as our users will go nuts keying credentials all the time. Do most of you use NTLM. 4) Do the phones / ipads / androids use outlook anywhere or do they use activesync? Just want to make sure NTLM setting will not screw up remote devices like that from working. Greg --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Exchange 2010: Outlook Anywhere enabled after some accounts were connected via outlook
Well... there is one difference between the two sites I was comparing... the site that showed the same server for RPC and HTTP has a CAS ARRAY (3 CAS) and that may be the difference. Have I been chasing a problem that doesn't exist? Should I expect the RPC server name to be the actual internal server name and HTTP server name be the external. And when the client takes their notebook on the road it will switch over to what is in the client connections where it does have owa.mydomain.com??? On Fri, Jan 25, 2013 at 9:44 PM, Greg Saunders gsaund...@myitanalyst.comwrote: Maybe another way of asking this: Our internal domain is ad.mydomain.com and our external is mydomain.com. Our CAS has been configures so internal and external url is owa.mydomain.com We are using pinpoint dns internally for owa.mydomain.com and autodiscover.mydomain.com since the internal domains differ. All of the tests at https://www.testexchangeconnectivity.com looking the way they should as an external test. I also test internally by using CTRL-RIGHTCLICK on Outlook icon in system tray and choose Test Email Autoconfiguration. This all passes as well. The ONLY thing I think might be an issue is the value for server under RPC is pulling in our actual exchange server FQDN: exchange.ad.mydomain.cominstead of owa.mydomain.com. The test for HTTP has server as owa.mydomain.com. But I believe I should be seeing the same value for RPC. For the life of me I cannot figure out why. I looked at another company/site that I help where they have same configuration and it DOES pull in the same owa.mydomain.com for both RPC and HTTP. So why is mine NOT? Where is it getting the server value for RPC? What am I missing? Thanks in advance! On Fri, Jan 25, 2013 at 8:33 PM, Greg Saunders gsaund...@myitanalyst.comwrote: It looks like the outlook anywhere settings did make it to the existing clients, BUT... I don't know if this is a problem or not, but feel like I cannot move forward without verification. - The existing outlook users I had setup seems to be getting the Outlook Anywhere settings. They all still show SERVERNAME.AD.MYDOMAIN.COM in the server. Even the newly setup Outlook Clients after Outlook Anywhere was successfully enabled on server have the same value. BUT I thought they would all show OWA.MYDOMAIN.COM. I am nervous about continuing if it is showing up WRONG. I checked the settings at another site and it doesn't use server name it, but uses MAIL.THEIRDOMAIN.COM. So I would have expected this site to show OWA.MYDOMAIN.COM instead of SERVERNAME.AD.MYDOMAIN.COM in the server field. - I noticed under client access / owa (Default Web Site) properites it has internal URL https://servername.ad.mydomain.com/owa set and that represents the wrong internal name. I mean yes it is a valid url, but we have a pinpoint dns for owa.mydomain.com and autodiscover.mydomain.com so the internal should be https://owa.mydomain.com/owa. Since we did pinpoint dns that should be same as external right. I checked the other site and it should be the same. It shows the same for internal on the other tabs for ECP, EAS, OAB. I changed them hoping it may fix what was showing up in server for exchange client, but no joy... doesn't seem to make a difference. Need feedback on this. - I did an internet test on autodiscover from Outlook by doing CTRL-RIGHTCLICK on outlook symbol in system tray. I then did the Test Email Autoconfiguration. I can provide the link of results if someone is willing to look at it. Greg On Fri, Jan 25, 2013 at 5:42 PM, Greg Saunders gsaund...@myitanalyst.com wrote: I had inadvertently left Outlook Anywhere disabled an my first Exchange 2010 install. I had setup 3 users in Outlook 2010 before I realized it. Now I have gone back to Exchange 2010 and enabled it. Still waiting on 15 minute period for it to be done, but the question is: 1) Will I have to do anything with the first 3 clients to get the Outlook Anywhere settings added... will they they pick it up from Exchange automatically or will I have to do something manual? 2) And do future Outlook clients automatically pick it up? 3) I chose NTLM as our users will go nuts keying credentials all the time. Do most of you use NTLM. 4) Do the phones / ipads / androids use outlook anywhere or do they use activesync? Just want to make sure NTLM setting will not screw up remote devices like that from working. Greg --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
