Archive
#Outlook for Android released with some minor spelling mistakes :-) – #Office365, #Microsoft, #Mobility via @Office365 and @Outlook
Microsoft has now released the Outlook app from Android, it’s no longer a preview.
There has been a lot of debate around this app and how it handles your credentials etc. but I must say that from a usability point of view it’s good!
One little fun thing that I saw is that they have missed how they spelled Dropbox in the “getting started intro” of the app… 🙂
Today we are excited to announce we have removed the preview label from Outlook for Android.
In January, we released Outlook for iOS and a preview of Outlook for Android. At the time, the iOS version of Outlook was ahead of the Android version in terms of features and performance. We set a high bar for where we wanted Outlook for Android to be before we removed the preview label. Since our preview release we’ve updated Outlook for Android 17 times—that’s more than one update per week—to meet this bar. A big part of that work has been improving the performance and stability of the app along with work on localization, accessibility and other fit and finish pieces. The other part of this work was about delivering features to add new value, match the iOS version and respond to your feedback.
Along with apps like Sway, the new Office universal apps for Windows 10, OneNote and others—Outlook is an example of Office’s new development model for building mobile apps—deliver a great first version of our apps and then iterate quickly with the help and feedback of our users. This removal from preview is not a change in that plan or a statement that we are ‘done.’ We will continue our pace of updates to make the app better each week in response your feedback.
In case you haven’t been using Outlook as your primary email app yet, here are some of the end user features we have delivered in the past three months:
Improved look and feel
We’ve continued to polish the look and feel of the app. We updated our icon sets and simplified our fonts to provide a more consistent Outlook experience across operating systems and devices. But it was also important for Outlook to feel like a natural part of Android. We use common Android design principles like the Navigation Drawer to house the multiple tools offered in the app and have common actions like settings available in the App Overflow menu.
IMAP support
#XenMobile and the #Citrix Mobile Workspaces Architecture – #BYOD
This is a great blog post by Christopher Campbell and good picture to show the overall capabilities and architecture of the Citrix offering!
You’ve heard us talk about Mobile Workspaces and if you’re a techie you’re probably wondering if Citrix really has the architectural components (a complete, comprehensive and fully integrated architecture) that can deliver any app and data to any user on any device over any network?
Well let’s first identify a few of the market leading technologies that make up the Citrix Mobile Workspaces solution:
- XenApp mobilizes and secures Windows apps on any device
- XenDesktop securely delivers virtual Windows desktops and apps on any device
- XenMobile manages and secures mobile, web and SaaS apps on mobile devices
- GoToMeeting empowers people to meet and collaborate with anyone, anywhere
- ShareFile shares and syncs corporate data securely from any location
- NetScaler optimizes and secures app delivery and on any network
- CloudPlatform orchestrates and provisions apps, desktops and IT services from any cloud
OK, OK. We know you have the products but do they really integrate?
Yes. Don’t believe me? Well as they say a picture is worth a thousand words. This is what the Mobile Workspace Architecture looks like.
OK. I get it. You have the architecture but that doesn’t necessarily translate to a seamless user experience.
Still don’t believe huh? Well this is what the user experience looks like.
XenMobile is a key ingredient in delivering a mobile workspace. Along with XenApp and XenDesktop it allows organizations to deliver on giving users access to any app from any device. In fact, if you’re an existing XenApp or XenDesktop customer, XenMobile seamlessly plugs into your existing architecture.
If you’re a XenDesktop or XenApp customer this is what your environment probably looks like.
Now this is what you need to enable EMM for BYO and COPE (Corporate Owned, Personally Enabled) devices and add that MDM, MAM, Secure Email, Secure Data…
Continue reading here!
//Richard
How To: #XenMobile #MDM 8.5 Deployment Part 3: Policies – #Citrix
And here U have part 3 of Adams great blog post series!
In this 3rd part of my 7 part series on XenMobile MDM 8.5 we will focus on policies. Policies within MDM allow you to control a multitude of features on your end users mobile devices, including: WiFi, Email, VPN, Location Services, most all functionality of the device (camera, FaceTime, etc), AppStore access, etc. Most configuration variations you do to control and limit/restrict/configure your end users devices will be done from this tab. This tab is also the location where we can create some automated actions that include notifying your users when they have fallen out of compliance.
If you would like to read the other parts in this article series please go to:
- How To: XenMobile MDM 8.5 Deployment Part 1: Installation
- How To: XenMobile MDM 8.5 Deployment Part 2: Basic Configuration
In this article I was to cover a “base” set of policy configurations that will give you a feel of how the policies work in general. By no means does this cover the breadth of what you can do with MDM, but it at least gives you a glimpse.
I want to accomplish the following in this article:
- Set a passcode policy on the device
- Block iCloud from syncing documents
- Preconfigure a WiFi network on my device (so that your users could come into the office with WiFi already configured and never have been given the password)
- Blacklist Dropbox, Box, and SkyDrive applications
- Notify the user their device as Out of Compliance (OoC) if those apps are installed
- Mark the device as OoC in the dashboard
.Configure a Passcode Policy
Configuring Email-Based Account Discovery for #Citrix #Receiver
Check out this great blog post from Avinash Golusula:
Configuring Email-Based Account Discovery
1 Add DNS Service Location (SRV) record to enable email based discovery
During initial configuration, Citrix Receiver can contact Active Directory Domain Name System (DNS) servers to obtain details of the stores available for users. This means that users do not need to know the access details for their stores when they install and configure Citrix Receiver. Instead, users enter their email addresses and Citrix Receiver contacts the DNS server for the domain specified in the email address to obtain the required information.
To enable Citrix Receiver to locate available stores on the basis of users’ email addresses, configure Service Location (SRV) locator resource records for Access Gateway or StoreFront/AppController connections on your DNS server. If no SRV record is found, Citrix Receiver searches the specified domain for a machine named “discoverReceiver” to identify a StoreFront/AppController server.
You must install a valid server certificate on the Access Gateway appliance and StoreFront/AppController server to enable email-based account discovery. The full chain to the root certificate must also be valid. For the best user experience, install either a certificate with a Subject or Subject Alternative Name entry of discoverReceiver.domain, or a wildcard certificate for the domain containing your users’ email accounts.
To allow users to configure Citrix Receiver by using an email address, you need to add a SRV record to your DNS zone.
- Log in to your DNS server
- In DNS > Right-click your Forward Lookup Zone
- Click on Other New Records
- Scroll down to Service Location (SRV)
- Configuring Email-Based Account Discovery
- Choose Create Record
iOS 6.1 banned from corporate servers due to Exchange snafu – via @rspruijt
Summary: iPads and iPhones running the newest version of iOS are being blocked in some enterprises because bugs are overloading corporate Exchange servers.
One of the benefits of Apple’s iOS devices such as the iPad and iPhone is that you can upgrade to the latest version as soon as it comes out. Being on the cutting edge is usually a good thing, but sometimes it can come back to bite you. If you are connecting to an Exchange server for mail and calendar services, the latest version of iOS has an unpleasant surprise in store for you.
Reports started surfacing in late January about excessive logging on Exchange servers caused by the upgrade to 6.1. A report on Microsoft Technet states:
I had a user upgrade to 6.1 and immediately after he finished, his phone/IPAD started causing excessive logging on the exchange server.
I found the problem by using exmon and saw the CPU utilization in conjunction with high session count.
He shut down Outlook and the problem remained. He turned off his iPad and the problem went away. The only change he said he made that morning was upgrading to iOS 6.1.
This problem has been confirmed by many sources. Windows IT Pro’s Tony Redmond reports:
I’ve picked up a few other reports that cannot be publicly attributed at this point that also refer to excessive transaction log generation after iOS 6.1 devices are introduced into Exchange 2010 or Exchange 2007 environments. I assume the same is true for Exchange 2013 as the underlying cause is likely to be in Apple’s mail app code that calls ActiveSync…
Continue reading here!
//Richard
