October 24, 2012 2 Comments
Easy you might think. Read more of this post
Windows Server Essentials Tips & Tricks
October 24, 2012 2 Comments
Easy you might think. Read more of this post
August 7, 2012 Leave a comment
Recently at a client of mine, we had an issue where one users Outlook would continually stop displaying new email. The inbox would show ‘last updated at..’ and would not move on from that time but, Outlook would correctly display ‘Connected’ in the bottom right corner. Read more of this post
July 11, 2012 23 Comments
Yes, you heard me right. Hopefully by now the news of the end of development, shall we say, of SBS 2011 Standard has settled in, and you are ready for how to tackle the void left in the market. I know many partners and folks are talking about alternatives, Kerio, Hosted Exchange or any number of other solutions, but i wanted to demonstrate how easy it is to setup the OnPrem (OP) integration with an Exchange server, and how it is possible to access both, using 1 single public IP address.
I have no idea how much it would actually cost to do in production though!
July 5, 2012 Leave a comment
I am certainly not the best person to ask for a reasoned business argument about why the loss of SBS Standard is good or bad thing. Read more of this post
October 27, 2011 3 Comments
I’ve noticed a lot of people are hitting my blog with search terms like SBS2011 iPhone or words to that effect. I got to thinking that maybe some people are not interested in the technical detail in my previous posts about iPhones or iPads, and maybe they just wanted to know how to add their Exchange email to their device.
If you want to know how to configure your iPhone with Office 365 look here.
If you are looking for information on the iPhone Configuration Utility, look here.
If you are looking for information on the iPhone and AutoDiscover, look here.
If you just want me to shut up and tell you what settings you need to make your iDevice work with your new Exchange Server, read on!
First from the Home screen, go to Settings.
Then go to Mail, Contacts, Calendars
Choose Add an Account.
Choose Microsoft Exchange
You are then asked for 5 pieces of information.
This is your email address
Your servers internal domain name. For example, ‘sbs.local’ could be your internal domain name. You can just enter ‘sbs’
This is the username you use when you logon to your computer in the office.
The password you use when you logon to your computer in the office.
This is just a memorable name so you can distinguish between multiple email accounts on your device.
Once you have filled out this information, click on Next. Notice the device now says ‘Verifying’
You may be presented with a warning message regarding ‘verification of the server identity’ Click on continue.
for more info on why this happens follow my link above regarding autodiscover.
In most cases you will now see a new box appear, called Server.
This is the public name for your SBS Server.
The default for SBS 2008 and SBS 2011 is ‘remote.company.com’
(where company.com is your email domain)
Type this in and click next. Again the phone will show as Verifying.
The next page will ask if you which items you want to sync to your phone.
Click on Save when you are happy with your selection.
Your items will now start to sync to your phone.
By default the iPhone will only sync the last 3 days of content, so don’t get freaked out if all of your email is ‘missing’.
You can change the behaviour in the settings of the account.
Under, Settings, Mail, Contact, Calendars, find your account by its description. Inside here you can change the sync behaviour.
June 22, 2011 18 Comments
EDIT – 28/10/2011 If you just want to know the settings required to connect your iPhone to your SBS Server, look at this post.
I use an iPhone, and i have blogged before on how to use the iPhone configuration utility in order to make deployment of the phones easier for clients.
I didn’t cover the iPhone’s ability to use ‘Autodiscover’ in that post, it didn’t occur to me at the time.
It didn’t occur to me until the other day, and then i set about confirming how it works, and in what scenarios you can use it to auto-configure a clients phone.
To follow me through this post you will need:
A Small Business Server 2011 Standard (you should have run the ‘Connect to internet’ ‘Set up your address’ ‘add a trusted certificate’ wizard)
An iPhone or iPad
Note: When i say External IP of either SBS Server or Exchange Server, i mean the address you would type if you were going to Remote Web App / Remote Web Workplace, eg. remote.domain.com = 188.8.131.52 – this applies even if you are using a third party to provide anti spam or filtering services to your email.
So, from the ‘home’ screen find ‘settings’
Find ‘mail contacts and calendars’..
Choosing Add Account.. we can then choose a Microsoft Exchange Account.
You are then faced with 5 configurable settings.
If you fill out these details with the settings relevant to you, you can then click Next. (if you click return it will automatically attempt the next stage)
You will see at the top of the screen ‘verifying..’
This is the part that has interested me, and i went to some lengths to find out what the iPhone is actually doing here.
However if i had used my brain at all i could have guessed it actually just follows the same behaviour you can see if you run the ‘Autodiscover’ tests here (at testexchangeconnectivity.com)
The iPhone will use DNS to query for your domains ‘default’ record – this is usually represented as an @ in your dns zone file.. but not something you are likely see if you are using a third party to host your DNS. Your default record like any other record translates ‘domain.com’ to an IP Address.
So for example, if you type in http://domain.com in to your browser, you MAY end up at your website, but you may end up elsewhere. It depends on the configuration of that record.
Suffice to say, it most likely does NOT point to your Exchange server. That is a problem.
If this query does return an IP address, then the iPhone will attempt the next stage of verification.
If you do not have an @ default record, for your domain, which is a valid configuration, then of course that query will fail and failover to query for ‘autodiscover.domain.com’.
At next stage of verification the iPhone will attempt an HTTPS connection to either – https://domain.com/autodiscover/autodiscover.xml or https://autodiscover.domain.com/autodiscover/autodiscover.xml
This XML file is located on your exchange server, you can see it within Windows Explorer.
You can open the file in notepad if you are interested to see the content
Please note THIS SHOULD NOT BE EDITED
You may be presented with a certificate warning if you are using a self signed – or single name certificate that is not for ‘autodiscover.domain.com’
It will attempt to login to the server with the username and password provided. If successful – your iPhone will be auto configured for your Exchange servers address.
You can then continue to finish the setup of your account.
If an HTTPS connection fails, then the process is repeated on HTTP.
If any of the above steps fail, or cannot complete – then you will be presented with a new box on your screen, and that will be for ‘Server Address’
Of course that’s fine to just enter at that stage – but it may be useful for some to know how to get this bit to work.
So to recap – to get the autodiscover feature to work:
I am making no recommendation on which option to choose, however i personally chose to delete my ‘default’ record and nothing bad has happened.
What other things will prevent a smooth auto configure? A self issued, or incorrectly named certificate.
Now most people will know with an iPhone you can simply ignore invalid certificates, BUT this is an extra prompt, and in the spirit of removing those obstacles to your users you should consider getting a UCC certificate for your SBS Server.
SBS Server will run perfectly well with a single name certificate – in fact it is designed with this in mind.
However the price difference between a single name certificate and a UCC certificate has come down considerably so now there is a good case for using a UCC instead. If the iPhone could use the DNS SRV record method for attempting autodiscovery – like Outlook clients can, then we could stick with a single name certificate.