Showing posts with label iPhone. Show all posts
Showing posts with label iPhone. Show all posts

Thursday, April 04, 2013

Moving to a Windows Phone–Part 3–The Move Over

As many of you will know, I engaged in a contest to get you all to click, click, and click. If enough of you clicked, the story was that Microsoft would give me a new Windows Phone. I accepted that challenge and promised that in return for the phone, I’d cease using my iPhone and use this new Windows phone for 3 months. I love my iPhone, and was somewhat nervous over the deal – but I’m willing to try it.

Well, the first part of the challenge was a success, and I duly headed over to Microsoft to pick up the new phone. It’s a Nokia Lumia 820. I arrived at Microsoft and was given the phone by Claire Smyth, our most excellent MVP Lead. We had a nice chat and I was quite excited to open the box.

First Impressions

As I opened it, the packaging was nice and very Apple like with a nicely designed box. The phone it self felt good in my hand and felt heavy enough to be real – and the battery even had nearly a full charge! Some of the newer phones I’ve held recently felt cheap and plasticy (Is that a word – all plastic like), in other words cheap and cheerful (maybe). By comparison, it was heavy enough to feel good, and could pretty instantly be used.

First impressions, thus, were good. The phone looked good, the white plastic back looked cool. It was stylish, but practical. So far so good.

Getting into the new phone

Back home, I immediately started playing. The phone booted smoothly and I was immediately able to get wireless connectivity going. My first task was to get mail working and this was surprisingly easy. I just typed in my credentials and the Exchange Server name and away it went. The Email client, at first sight looks OK, compared to the iPhone.

Getting the phone to work as a phone was also snap – I just had to find the iPhone tool to retrieve my SIM and pop it into the phone. As someone with non-existent finger nails, I did find getting into the new phone was quite difficult. As I’m not likely to have to get into the innards very often, this is probably no bad thing, but in the end, I had to get my wife, with her longer nails, to help. But once I popped the old SIM into the new phone, immediately it worked! The overall phone quality from home is sucky, but that’s O2’s issue, not the phone. But I could make calls in the UK. I’ve yet to try calls when abroad but I’ll post any issues or success that arises.

I also started playing around with the Windows Phone 8 UI – the new version Windows 8 with it’s tile based front end. And I also started searching for apps. As I posted, I have a bunch of apps I wanted and needed on the new phone so time was spent in the Store. In my last article on this topic, I set out what my needs and expectations were with regard to apps. While I knew that, at least, some the apps in a given category might be different (like they are between Android and iPhone). I can live with that to a degree.

Good stuff

Moving over to the phone for all my KEY needs has been pretty painless. Email was up in a snap, wireless and mobile data were a breeze to setup. Props to the Phone OS – when I went to setup the wireless data, rather than having to call O2 to find out the password etc., the Lumia displayed an option to just use the O2 settings and hey presto. Sweet! Mail is quick, the phone works in the local area and some of the key apps are up and working.

The Windows 8 tiles seem pretty cool. At first sight. It took me a month or two on both my last Android and iPhone to get a layout that worked and this is certainly going to be true for the Windows phone. The tiles are easy to access, easy to move around and easy to re-size. The application the tile represents can change the display – and this I find better than the iPhone’s method of displaying pushed changes.

Adding storage via a MicroSD chip is trivial and not very expensive. It was trivial to buy off the net, and a breeze to install (with the proviso that getting the back of the phone off so I could insert the chip was not easy). But after inserting it, replacing the cover and rebooting the phone - it just worked! Of course, filling it is not be a problem! I wish the iPhone had had the ability to use a MicroSD chip. Lack of on-phone memory was for me a limiting factor to the iPhone – so well done Nokia. Any chance of adding in a 2nd or 3rd slot next time – I have a lot of Grateful Deal to move onto the phone! Trying to take my 3.5TB worth of shows and fit into a mere 64GB is not easy – but that’s my problem to deal with.

Issues Arising So Far

While the initial honeymoon period was nice, it wasn’t perfect and there are a few issues I’ve noted. The first issue is the resolution of the screen. When I open an Email message, the resolution of the text is just not as crisp or as clear as on the iPhone. The iPhone is much better despite 2 year older technology. That said, I can live with it – but it feels cheap. This is a Nokia fault, really, not Windows.

The second issue, which is really quite a mild one, is the difficulty of getting into the phone’s innards. As I mentioned earlier, I don’t have adequate finger nails to pry off the cover. I suppose this is a good-news/bad-news thing – it’s difficult to get the cover off, meaning the cover won’t come off easily. And as I hopefully won’t need to pop the cover off very often, this is a minor thing.

The third issue is apps, or should I say lack thereof. After a week, I’ve not managed to duplicate the full richness of my previous iPhone environment. The Windows shop reminds me of visiting East Berlin and the USSR in the early 1980’s and going into a shop there. I’ll report more on my quest for apps in the next article.

Summary after a Week

Overall, it’s a nice phone. The display quality is somewhat disappointing – I expected iPhone 4 quality and better. The OS is solid, and the core apps I’m using so far all work OK. But several apps are still unfound and some don’t yet work for me. I’ll return in a week or two with further commentary.

Tuesday, December 13, 2011

Microsoft Begins Shipping the Lync Mobile Client

For those of us in the Lync world, the release of a Lync client for mobile phones has been long awaited. Although Microsoft released Lync 2010 to the market over a year ago, there has been no mobile client up till now. The lack of a mobile client has been a point some Microsoft competitors have been quick to jump on. But starting earlier this week, the client is slowly rolling out on 5 key platforms (Windows phone, iPhone, iPad, Android and Nokia Symbian).  Thus far, Microsoft has only released Lync for the Windows Phone – the others are shown as ‘coming soon’ on the Mobile Clients for Microsoft Lync web page.

Microsoft cites 4 key features of the new Lync mobile client:

  • Join conferences with a single touch - no access code or pin number is required.
  • Stay connected, while controlling your availability – you can see who's available at a glance and connect over IM, email or a call. You can also set your own status and notification settings so you can stay in touch while protecting your "off-work" time.
  • Communicate with others using a single, consistent identity. The Call-via-work feature allows outbound calls using your Enterprise Voice number, making it easier for others to recognize calls from the Lync mobile client.
  • Connect with confidence through channel encryption, transport layer security (TLS) support, and perimeter/internal network protection that help safeguard your communications.

To the dismay of some, there is no VOIP client – all phone calls to/from the device have to be made over the cellular network, but Call from work and One Number reach do make that a little less expensive.  It appears that the Call via Work feature will not be shipped with Android.

Like so many things Microsoft, the client is not something you can just load from the relevant store and have it work – you do need some work on your Lync implementation and need to install the latest cumulative updates (CU4 in particular) to get the necessary services up and running that support the motile client.

These requirements are spelt out in yet another TechNet article: http://technet.microsoft.com/en-us/library/hh690988.aspx. You will need to do some work against your DNS servers to ensure automatic discovery and sign-in works properly. Although this is pretty straightforward, it is work that needs to be planned for and carried out. If you are an Office 365 user and Microsoft is managing your DNS, the work appears to be already done. I host DNS externally to Office 365 but it took me just a few minutes to adjust my DNS settings as needed. You also have to install and configure the mobility service (in CU4), and update your voice policy to support use of the mobile client.

One important gotcha that might be easy to overlook: You need to include certain (new and additional) SAN entries on your key servers. In particular you need to adjust SAN entries on the certificates in your Director pool, your Front End Pool and the reverse proxy. If you use public certificates for any of these systems, you may have to buy an updated certificate for the RP system. 

In closing, it’s worth noting that the mobile client does NOT provide 100% of the features of the Lync desktop client.  You can see a good comparison of the various clients at: http://technet.microsoft.com/en-us/library/hh691004.aspx. Some features that are NOT provided by the mobile client (as documented in TechNet) include:

  • Caching multiple users account information on the same device
  • Modify Contacts List
  • Tag contacts for status change alerts
  • Control privacy relationships
  • Log IM conversations in Exchange/Outlook
  • Use dial-in audio conferencing
  • Transfer a call
  • Call a response group
  • Support E911
  • Client side IM archiving and client side recording

I can’t wait to get my hands on the client and to use it against my Office 365 account (tfl@reskit.onmicrosoft.com). From all I’ve heard from those who have the client – it does what it says it does and thus far appears stable and resilient. I look forward to using the client - As an iPhone user, I will have to patient. After all – I’ve been waiting 14 months or so for this client a few more days wait is not the end of the world! It will make a nice Christmas present!

Friday, February 18, 2011

PowerShell on my iPhone

I recently got a new iPhone 4 16GB, courtesy of American Express (a long story!) and have been slowly making the transition from my HTC Desire Android (a nice phone) to the iPhone. There are some observations I’ll leave for another day – but let’s just say that the iPhone is not perfect and the Desire/Android is worth competitor.

One neat thing I have found in my search for applications for the new phone is iPowerShell V2, built by Sapien. iPowerShell is neat reference tool for users of Microsoft’s PowerShell, for use on the iPhone or iPod Touch. It contains full descriptions of all the core PowerShell Version 2 cmdlets, their syntax, parameters and examples of proper usage. It also contains the complete set of “about item” help topics as well as provider and alias help.

I’ve not yet found a way to extend it (i.e. to add or modify the contents, but I find it useful to dip into and out of. I particularly like browsing the about_* files using iPowerShell.

Here’s a screen shot of the application:

image