Re: Deploying MS Direct Push technology
- From: Tom <Tom@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 5 Feb 2008 11:48:02 -0800
THANKS! Great and very specific response!!!
Very much appreciated!
We'll do this when we're back in the office next week!
"William" wrote:
On 5 Feb, 14:11, Tom <T...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:.
Win2K3 SBS SP2, all updates through 2/1/2008
Exchange 2003 SP3, all updates through 2/1/2008
IIS v6 installed, all updates through 2/1/2008
We're in the process of installing MS Direct Push technology for the
Motorola Q9c.
Good plan, and looks like the server is ready.
We're a little overwhelmed at what is necessary so maybe we're just going
through the initial shock of getting Direct Push technology enabled.
It was
our impression that we 'simply' did some minor setup and vola mobility via DP
was live.
That's correct.
It appears we need to install/configure ISA2006 (which we're not familiar
with).
Not so. ISA 2006 may be a useful product, but it is not necessary for
Exchange-Activesync (aka Direct Push).
Also we currently connect via OWA to check our email. Since we initially
respond to OWA's security certificate, it's our presumption that we'll be
able to resolve this with the Q9c.
Yes - you will need to export the certificate to a DER encoded .CER
file, then copy that file to the phone, then open the certificate on
the phone to install it. This is a one-off process per phone.
In addition, you should ensure that target users are part of the
"Mobile Users" group. Then all you need to do is configure the
Activesync options on the phone (Server-name, User-name, Password, etc
plus settings for when and how to sync). The first phone will take a
little while to get right, the second and subsequent phones should
take about two minutes each.
So, where do we find ISA2006 and what are the gotch's upon
installation/setup/configuration?
You can read about ISA 2006 here:
http://www.microsoft.com/isaserver/default.mspx
but it's not necessary for this project.
Other pointers for us would certainly be appreciated as we're a small
enterprise.
a) It's often easier to attach the phone to a PC via cable for intial
setup. This lets you copy the certicate across via (Desktop)
Activesync. You can do this in "Guest" mode by selecting "Cancel" when
prompted to create a partnership, or you can create a partnership with
both the desktop and the server.
b) Use the external name of the server, not the internal name.
c) Some smartphones are locked-down by the provider, and this can make
it difficult to install the certificate. The only way to find out, is
to try.
d) If all the phones are the same, you can use cloning (or backup)
software to copy the setup from one phone to another. That way, you
just have to get one phone working the right way, clone it and then
change the user details.
See:
http://www.spritesoftware.com
I've added the microsoft.public.windows.server.sbs group, since the
people there have a lot of knowldege in this area.
--
WH
- Prev by Date: Re: "Error: unable to save the file"? Cant save pics
- Next by Date: Re: Problem accessing Comcast and another IMAP account
- Previous by thread: Re: Re: samsung sgh i620 and tomtom 6
- Next by thread: Re: Set up the Wirless Modem on Mobile 6 w/ ATT Tilt - End Data call f
- Index(es):
Relevant Pages
|
