Interlink Cloud Blog

Interlink Cloud Blog

Welcome to the Interlink Cloud Blog

All content provided on this blog is for informational purposes only. The owner of this blog makes no representations or warranties regarding the information from our partners or other external sources.
Matt Scherocman

Skype for Business Mobile: Cloud and On Premise

Microsoft finally released the mobile client for Windows 7 Phones, Androids, iPhones/iPADs, and the Symbian devices.  Finally, we can now use Lync anywhere and those of you out there that have enabled Enterprise Voice have a host of options from dialing out your PSTN connection from anywhere, to auto-joining conferences with a tap on your phone.

The clients have been an average experience for me to this point.  I use the iPhone and, like many, I was anticipating the release of the Lync client to be able to use on my iPAD and iPhone.  Conferencing is the biggest dissappointment to me.  Not being able to connect using the iPad to a conference to see whiteboarding and screen sharing is, to say the least, disappointing.  Especially on the iPad where you would expect a more rich experience.  However, it is classified as mobile and has the same limitations as the other mobile clients.

As for deployment, if you are using Lync online, it couldn't get any easier!  A CNAME change is required for the Lync mobile client to connect, point to online.lync.com. It's as simple as the push notifications provider you have to use anyway!  In discussion with Kevin Peters, MVP and MCM in Lync Voice and Enterprise Messaging, he didn't make any changes; with a single vanity domain, Lync mobile was able to connect with no problems.

Lync on premise is a bit of a different challenge however, there are some great resources out there for you to use.  Don't put your faith in the Microsoft Lync Mobile Deployment Guide - it does not have any of the gotchas in it at all!! 

Resources:

TechNet Deployment Guide

Jeff shertz has a great blow post you can use: http://blog.schertz.name/2011/12/deploying-the-lync-2010-mobility-service/

Jeff does an excellent job clearing up some of the confusion surrounding deployment.

Most notably, the challenge you will run into with certificates and their assignments, how to deploy internally and externally.  There are some good blogs to help with this process, and as always, advise with your partner before attempting to do it on your own.  On this one, there are a ton of catches.

Good luck and enjoy your mobile client!

Continue reading
  5681 Hits
Matt Scherocman

MIcrosoft Office 365 Now Supports Removal of Directory Sync

Earlier this month, Microsoft announced that Office 365 will now support the ability to break Directory Synchronization if a customer chooses to do so.

Though through the Office 365 Admin page, when enabling Directory Synchronization it still gives the warning that if it is enabled it cannot be disabled, the fact is you can use the Office 365 Online PowerShell module allows you to connect to your environment and disable it. 

In the past, if a user was brought over by Synchronization, that user was permanently managed from the Directory Sync (DirSync), and if DirSync was disabled or removed, the user account became stale. The only thing that you could do to manage that user online was to reset their password.  You could not delete the account, and couldn't modify other aspects of the user account.

The addition of this alleviates many headaches for those out there moving from BPOS (used DirSync as a migration tool) to eliminate the on premise server required to run it.  Moving to Office 365, former BPOS customers can now manage their users online without that need.  This applies to many small businesses that were frustrated with the need to continue to have another server that isn't a domain controller, on premise to run Cloud based mailboxes.

In addition to this, I recently ran into a similar scenario where I was extracting mailboxes from a an envioronment over the 1,000 limit to use the batch migration.  Since these mailboxes were being extracted for the purpose of an acquisition, the installation requirement of Directory Synchronization in the staged migration scenario (note that you can run a staged migration on 100 users or less without Directory Sync).  I then was required to run Directory Synchronization, at the risk that the mailboxes I was extracting would become stale longer term, and if not setup in the acquiring companies Directory, could eventually be removed by accident or deteled.  Note that I had to run a filter of MIIS to ensure that only users with a specific attribute in the Directory could be copied to the cloud.

By disabling Directory Synchrnization I can then modify those accounts, and evenutally make them Cloud only.  And longer term, enable a new Directory Synchronization to take place with no risk.

   

Continue reading
  12228 Hits
Matt Scherocman

Exchange Online Deleted Items Retention Workaround

So, we all have that person, or should I say people, in our organization that use deleted items as a means to actually organize email. Usually, it is because they don't want to organize it. They just delete it and figure they can find it later. This amazing irony of deleting something, then using it as a search folder is somewhat impaired by Exchange Online in Office365. Microsoft's policy for deleted items retention is 30 days which means your favorite deleted items organizer will close Outlook one day and lose their primary means for searching email.

Fortunately, or unfortunately, there is a workaround for this called Litigation Hold in Exchange Online. This accidental feature design for legal keeps all mail retained permanently, and allows deleted items to be stored indefinetely. The challenge is whether or not you really want to do this. Or do you want to take the opportunity to force good behaviors? And the answer is that you don't have a choice because it's the CEO or CIO who is doing it, and they dictate the business rules while we as IT Services cannot. We find ways to make it work.

Before you begin   To learn how to install and configure Windows PowerShell and connect to the service, see Use Windows PowerShell in Exchange Online.

Run the following command to configure the litigation-hold duration for a mailbox that’s already on litigation hold.

Set-Mailbox  -LitigationHoldDuration <duration, in days>

Example   The following command sets the duration of the litigation hold on Ann Beebe’s mailbox to one year.

Set-Mailbox "Ann Beebe" -LitigationHoldDuration 365

Run the following command to put a mailbox on litigation hold and set the litigation-hold duration.

Set-Mailbox  -LitigationHoldEnabled $true -LitigationHoldDuration <duration, in days>

Example   The following command puts Pilar Pinilla’s mailbox on litigation hold, and sets the litigation-hold duration for 7 years.

Set-Mailbox "Pilar Pinilla" -LitigationHoldEnabled $true -LitigationHoldDuration 2555

Note   You have to use the IncludeLitigationHoldDuration parameter with the Get-Mailbox cmdlet to view the value of the litigation-hold duration. For example, run the following command to display all litigation-hold settings for Pilar Pinilla.

Get-Mailbox "Pilar Pinilla" -IncludeLitigationHoldDuration | fl Litigation*

After this you will get a pop-up box with two options: one is a note that you can send to the mailbox owner telling them the details of being on litigation hold, in this case because you need to keep all deleted email indefinetely. Then, a URL if you want to point them to a policy online. As you'll notice, the mailbox is in pending. It will take up to 60 minutes to take effect in Exchange Online.

I hope this was helpful. As always, more posts to come!

Continue reading
  6813 Hits
Matt Scherocman

What is Versionless?

Versionless software is software that is always up to date with incremental improvements.  Microsoft has flipped the coin.  Clients used to have to wait for functionality to be available in the cloud.  Now the cloud gets the functionality first and on premise comes later.  This change is tremendous for clients.  The number one obstacle that clients have told me to utilizing new software is the deployment.  Now in the cloud, Microsoft takes care of that deployment and keeps the product up to date.  From the slides you can see their commitment to the cloud and how much functionality is being released on a regular basis. The 2013 graphic was produced in the late summer time frame so it doesn’t include new functionality like encryption included in the E3 plans that came out later in the year.
What we've delivered 1

What We've Delivered 2

 

This posting is provided “AS IS” with no warranties, and confers no rights.

Continue reading
  10508 Hits
Matt Scherocman

How Does The Office in Office 365 and Terminal Servers Work?

Office Pro Plus licensed through Office 365 is powerful while each licensed user can install the software on up to five devices for their own usage.  What happens when one of those devices needs to be a terminal server?

The problem is that terminal server cannot use the downloaded media from Office 365 while the 365 version includes subscription authentication.  Basically, this is technology that allows the software to verify that it has been paid for by connecting the installation to a user’s access for Office 365.  This authentication breaks when installed onto a terminal server due to the multiple user nature of the technology.

So, Microsoft has granted an exception for users to be able to take advantage of the exception.

“ Media Eligibility with Remote Desktop Services (RDS) If the user to whom you have assigned an Office 365 ProPlus license uses the software on a network server with RDS role enabled, in lieu of installing a copy of the software provided with Office 365 ProPlus on one of the five permitted devices pursuant to the Product Use Rights for Office 365 ProPlus, that user may 1) install one copy of the Office Professional Plus 2013 software on a network server and 2) access the Office Professional Plus 2013 software from any device.  Upon termination of your Office 365 ProPlus subscription you must uninstall Office Professional Plus 2013 software from the network server.”   This is from Microsoft Product Use Rights Guide - http://www.microsoft.com/licensing/about-licensing/product-licensing.aspx which is the best source for Microsoft licensing rules.

Practically, customers need to procure a single volume license media copy of Office Professional Plus and install that directly on the terminal server.  Most customer will already own this copy from a previous volume license (Open, Select, or EA Agreement).  For the clients who still need media, my suggestion would be to open a new Open Business agreement with Microsoft.  These agreements are low commitment with only five licenses of any type needed.  An organization could order a single copy of Office Professional Plus and then four other low cost items.  Hosted encryption, which can be used with Office 365 to encrypt sensitive emails can be had for less than $25 per year.

This posting is provided “AS IS” with no warranties, and confers no rights.

Continue reading
  11747 Hits

Welcome to the Interlink Cloud Blog

All content provided on this blog is for informational purposes only. The owner of this blog makes no representations or warranties regarding the information from our partners or other external sources.