Setting up policies for mobile device using email

Non-wireless mobile devices receive the initial software and software updates through a link in an email.

The following policies must be set up on the PolicyServer in order to provision a mobile device using the email method:

• PolicyServer
  • PolicyServer > PDA set to "Yes"
  • PolicyServer > PDA > CellPhonePDA set to Yes"
  • PolicyServer > PDA > Email set to "Yes"
  • PolicyServer > PDA > SMTPServerName set to "127.0.0.1" (For email relay/lookup for Yahoo, Hotmail, or other email addresses)
  • PolicyServer > PDA > SMTPServerName set to "Company Exchange server address info"
  • For using company email addresses: PolicyServer > PDA > Source Email set to "Whomever you want to show the email is from"
• MobileSentinel
  • MobileSentinel > Common > NetworkCompliance set to "Yes"
  • MobileSentinel > Common > NetworkCompliance > ComplianceNetworkAddress set to "97.87.84.48"
  • MobileSentinel > Common > NetworkCompliance > ComplianceNetworkNetMask set to "255.255.255.255"
  • MobileSentinel > Common > NetworkCompliance > ComplianceServerAddress set to "97.87.84.48" or "SaaS.Mobile Armor.com"

At the time of this writing (immediately prior to SP6 release), the policies below apply exclusively to MobileSentinel for Pocket PC. MobileSentinel for Windows ignores the policies, with the exception of v3.0.6.

Policies->MobileSentinel->Common->NetworkCompliance->ComplianceNetworkAddress

This policy is often confused with being the address of the PolicyServer. This is not quite accurate. This policy, in connect with the ComplianceNetworkNetMask, defines a network with which a device that is out of compliance may communicate. "Out of compliance" in this case is defined as a device which has not communicated with the PolicyServer within a period of time as defined by Policies > MobileSentinel > Common > Compliance > SynchronizationTimeout. This policy is often defined as the FQDN of the server, with the NetMask set to 255.255.255.0, which would be a group of 255 computers. Specifically in the case of our SaaS offering, this address should be 97.87.84.48, and the NetMask should be 255.255.255.255. In customer deployment, this setting will vary, but in the vast majority of cases this policy should be set to either of the following:

• Network number containing the external PolicyServer address with a netmask appropriate to that network
• External address of the PolicyServer itself with a netmask of 255.255.255.255