onsdag den 6. marts 2019

Manage multiple cloud accounts in Chrome

The more Office365 tenants you manage, the more the daily browser struggle becomes real.
Recently i found a great way to manage this that i want to share.

The usual situation, you are logged in to your own tenant in O365 - and now you have to manage a different customer tenant, you go to "Incognito" or "In Private" browsing in Edge...this works kind of OK, but being incognito you actually miss out on some of the features in the browser.

And even when using incognito you can run in to problems:
  • You get access denied on a page but it is unclear which identity the browser actually tried to log on with.
  • You may have to type in passwords multiple times for each account in different browsers
  • If you make the browser remember password, it might log you in automatically and will be difficult to change accounts.
  • If you are using Incognito, you will have to type in username and password every time
  • If using link from your mail you automatically login with the account last used in that browser session and that may not be the account you need

Chrome has a nice feature builtin in to manage this using "personas"
It builds separate browser entities with own cache.

Here is how to:

Open your Chrome browser and click on the small picture/ icon at the top right corner.
And select "manage people"


It will now open the people directory - and from here you can create all the "accounts" you need.
When creating a new persona/ account it will ask you for Gmail login, there is no need for that.



In the Next dialog, name the new account/ person - example with the tenant name or customer name.
Remember to remove check-mark if you do NOT want the Desktop Shortcut that will be created.

Now just click add and skip all the gmail account steps, they are not needed.

And then your all set - and can easily switch between and access all your tenants.
Icons stack up nice in the systray and on the desktop :)

Have a nice day.
& Please share this info.


søndag den 3. februar 2019

Microsoft Teams coexistence modes - get the journey right.

As more and more organisations are now beginning to either pilot, or fully adapt Microsoft Teams, i often get questions like, where do we begin and whats the best migration path from SKYPE for Business

Answers are never the same, because it depends on the individual org's current situation combined with the plans and requirements for Teams, but there are some basic methods that apply to all.

Luckily there are tons of great resources out there to help you plan and execute the pilot and/or the migration.

Please note this article has emphasis on the SFB > Teams coexistence, where Teams is so much more than just meetings, chat, presence and Telephony - so most likely this will be on bit in a more complex - collaboration in general - project
Also the migration itself is only a tiny portion of a Microsoft Teams project, the adaptation in the org as well as the integration into existing business processes is also key to success.

But let me move one step further into the migration itself.

Things to consider:

1. How are you using Skype for Business today - and did the initial requirements change that was evaluated when SKYPE or LYNC was introduced ?

2. Which end result do you expect and aim for, and which business needs will you meet ?

3. Who are your stakeholders and ambassadors for the project  and who shall pilot (if any) ?

4. Are there any technical implications ? (like PSTN availability)

5. Which path does the above choices point to, and does it fit your "optimal" path ?

The number one resource for help and information you find here:


https://aka.ms/successwithteams

Here you will find tons of helpful information, as well as ready to use resources, like Email templates, scoping templates, user profiling guidance etc
All nicely packaged into one zip file:
https://aka.ms/UpgradeSuccessKit

When planning your path in my point of view, one of the most important steps is understanding and thus deciding on the correct coexistence mode for your org.

Her are the 5 modes in overview.
Mode
Routing Behavior
Meeting Scheduling
Client Experience
Islands
Incoming VOIP calls and chats land in same client as originator, except if recipient is federated and in islands mode, in which case they land in SfB.1
Both
End users can initiate calls and chats from either client, and can schedule meetings from either client.
SfBOnly
Incoming calls and chats are routed to Skype for Business
Skype for Business only
End users can initiate calls and chats from Skype for Business only, and only schedule Skype for Business meetings. (NOT YET ENFORCED)
SfBWithTeamsCollab
Incoming calls and chats are routed to Skype for Business
Skype for Business only
End users can initiate calls and chats from Skype for Business only, and only schedule Skype for Business meetings. They can also use Channels in Teams. (NOT YET ENFORCED)
SfBWithTeamsCollab
AndMeetings
Incoming calls and chats are routed to Skype for Business
Teams only
End users can initiate calls and chats from Skype for Business only and only schedule Teams meetings. They can participate in Teams channel conversations. (NOT YET ENFORCED)
TeamsOnly
Incoming calls and chats are routed to Teams
Teams only
End users can initiate calls and chats from Teams only. Skype for Business is only available to join meetings.
As annouced last year new tenants are now defaulting to Teams Only - but if your tenant is created before Nov. 18. 2018 (like most other) your users are now in "Islands Mode"
https://support.microsoft.com/en-au/help/4465277/microsoft-teams-now-the-primary-client-for-meetings-and-calling

However I see Islands modes as a bit confusing for your users - they simply will have a hard time working out what goes where - and that is NOT a great start for a pilot or migration.
In this mode there isn’t really any connection between Skype and Teams, they are two independent systems. If you send a message from Skype it would end up in Skype, if you send a message from Teams it ends up in teams.
So basically you now have to chat clients, and to make matters worse if you have federated contacts their messages will end up in the main client for federated chat - meaning SFB if your'e in Islands.


Here is a graphic view of Islands mode (no seriously)

So the first recommendation would be - select and move to the "ONLY" mode that best fits your organisation.

Also important to note, when in Teams Only, federated messages will end up in your Teams client, but in the background they will actually be routed by SFB.

When you start moving users out of islands mode it’s will get confusing unless you move everyone out. If user one is in Teams only, and user two is in Islands, then user 2 sends a Skype message to user 1, he will receive it in Teams, but if user one then sends a message back, user 2 will receive it in Teams. This behavior will be frustrating and confusing for users, and will not make help to make the pilot a success

So what is the best way to avoid these caveats - well when you have decided on the Pilot - first thing is to move EVERYBODY to Skype for Business with Teams collaboration mode- so this needs to be done on tenant level. https://docs.microsoft.com/en-us/microsoftteams/enable-features-office-365
Then setting the pilot users to Teams Only - thus leveraging the interoperability features between the two platforms.
Meaning no chat in Teams - if users want that, they can opt in on the pilot :)

So what about the other features.

Calls are handled like the chat messages, so they will follow the above policy.

Meetings are basically still coexisting - the modes basically only affects the ability to schedule meetings from Outlook - meaning you can join both types of meetings - even when in "Teams only" mode, you will still have a mini SFB client in your Office to join SFB Meetings hosted by a colleague or an external part.

Also lastly please note that there is or at least was another mode called "Legacy Mode" where , if you where to message a colleague from your Teams client, and this colleague not yet has had his Teams client opened, message would get rerouted to SFB - this will no longer be the case, this mode has deprecated - which is good because it was kinda messed up.






tirsdag den 22. januar 2019

Cloud Connector Edition and HTTP Proxy issue.

Hi all.

I recently came across an CCE problem for the first time, and hopefully this info can help others that may end up in the same situation.

Some customers are required, for compliance reasons, to run the Cloud connector behind a HTTP proxy. This is well documented in the Design and Planning whitepapers - so far so good.

The customer i worked with had all this in place. But when one CCE in HA went into "error" state in the portal they proceeded to do uninstall and install process - but then ran into problems.

After building the first server (AD) the script failed in the attempt to contact the servers via the Management Hyper-V vSwitch - connectivity was ok the hosts could ping the VM (with firewall disabled) but still the script failed with this error.




Wait-MtMachineOn : Can't connect to machine 192.168.213.2 after waiting 600 seconds. At C:\Program Files\WindowsPowerShell\Modules\CloudConnector\Internal\MtAddc.ps1:329 char:9+ Wait-MtMachineOn $machineIPAddress $vmAdminCredential -WaitOffFirstly $t ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Wait-MtMachineOn



This error points to connectivity issues. We thought we had that covered




Theese are my Troubleshooting checklists with CCE connectivity issues. 

  1. VLANS: Confirm that no VLAN's have been configured on the Host machines 
  2. Virtual Switches: Confirm that the Virtual Switches configured on in Hyper-VHost appliance have the identical names as defined in the Cloud Connector Configuration File 
  3. Management Switch IP: This is set by CCE script, but could be changed by someone. Confirm that it's assigned an IP address in management switch subnet range as defined in the Cloud Connector Configuration file. 
  4. IP address of the Host network adapter bound to the Cloud Connector SfB Corpnet Switch must have an IP address assigned to it in the same subnet range as the Corpnet subnet defined in the Cloud Connector INI file. This IP address can be configured as an alternate IP address if the you have requirement to have a different IP assigned on this adapter for managing the host computer. 
  5. Proxy Exclusions: If you are using a proxy server for Host appliance, confirm if you have made the appropriate proxy exclusions in WinHTTP for the CCE Management and Corpnet subnets as defined in the Cloud Connector INI file. 
  6. If a proxy server is required on the host machine, then you should configure a proxy exclusion for the Management and Corpnet subnets defined in Cloud Connector INI in the proxy bypass list. Otherwise host to VM connectivity will fail and prevent the deployment of Cloud Connector Edition. To bypass the proxy, specify WinHTTP Proxy settings set with your proxy server and a Bypass-list including the "192.168.213.*” network used by your Cloud Connector Managements services and the Skype for Business Corpnet subnet as defined in your CloudConnector.ini file. Otherwise, management connectivity will fail and prevent the deployment and auto recovery of Cloud Connector. The following is a sample winhttp configuration command: netsh winhttp set proxy "10.10.10.175:8080" bypass-list="*.local;1.*;172.20.*;192.168.218.*'<local>". https://technet.microsoft.com/en-us/library/mt605227.aspx#Anchor_2 
  7. To ensure Internet downloads work, make Proxy settings per-machine rather than by user. Otherwise Cloud Connector downloads will fail. This can be done either with direct registry change, HKLM\Policies\Microsoft\Windows\CurrentVersion\Internet ## Settings: ProxySettingsPerUser with Value of 0 (disabled), or Group Policy Computer>Administrative Templates>Windows Components> Internet Explorer: Make Proxy settings per-machine (rather than per user). https://technet.microsoft.com/EN-US/library/mt605227.aspx 
  8. Internal CCE Domain and SIP Domain are defined the same: https://support.microsoft.com/en-ph/help/3214408/-can-t-connect-to-machine-ip-address-after-waiting-600-seconds-error-a
  9. Invalid IP Addresses: Check if the switches on the CCE AD VM have Automatic Private IP Address (APIPA) of 169.x. Connect to the Host Appliance and open Hyper-V Manager from Control Panel > Administrative Tools Select the CCE VM (name will start with CCE Build #) Click on Networking Tab in the bottom pane and view the Networking Connection IP's 


If the IP addresses are 169.x addresses, this is because the Convert-CcIsoToVhdx failed on Windows Updates because base VM couldn't connect to Window Update Service to run updates. When this happens, the process errors out with a warning and information on how to connect to the machine to run updates and once that's done, re-run the Convert-CcIsoToVhdx with -GeneralizeOnly parameter to sysprep and generalize the Base VM machine, copy the VHDX to "Site DirectoryBits\VHD\SFBServer.vhdx". When sysprep is not performed, the Unattend.XML answer file containing information to setup machine obtained from CloudConnector.ini file will not be used as the initial startup asking the questions will not be run. To resolve this, the customer should re-run convert cmdlet in Administrative PowerShell on the CCE Appliance as follows:



  1. Convert-CcIsoToVhdx -IsoFilePath <Windows ISO File Path, including file name> -PauseBeforeUpdate 
  2. When the script prompts that updates are ready to be run, connect to the Base VM using credentials provided in the instructions provided in the PowerShell output 
  3. Make any necessary adjustments to allow the computer to connect to Windows Update Service
  4. Complete all Windows Updates and restart the VM 
  5. When updates are completed, answer prompt in PowerShell output to continue the process 
We Checked all parts of the above 2 lists

But still same error. !?

Then we saw this in the NETMON trace:


TCPPayload: SourcePort = 80, DestinationPort = 52127


- Http: Response, HTTP/1.1, Status: Bad request, URL: http://192.168.213.2:5985/wsman


ProtocolVersion: HTTP/1.1


StatusCode: 400, Bad request


Reason: Bad Request



And although we had a mental checkmark on the Proxy part a clever colleague suggested to clear the Proxy Cache with this command:

“netsh winhttp reset proxy” on the HOST



And Hey Presto - after this was done install-ccappliance script went thorugh and the CCE came back online







Hope this will be usefull to someone :)

Happy SKYPE'ing.

mandag den 14. januar 2019

Skype For Business server January CU released

Hello Folks :)

A new cumulative patch has been released for SKYPE for Business server 2015.

Version number for Core components is 6.0.9319.537

To find your current patch level run this command on a SFB server


get-csserverpatchversion
(Yes i am aware that this lab server needs CU's :))


This patch contains a very long list of fixes in alot of different areas - and also a brand new feature allowing your organisation to make the Move to Microsoft Teams in on step, like it is possible in Skype for Business Server 2019.

To download the CU go to: https://support.microsoft.com/en-us/kb/3061064



For installation instructions go to:
https://support.microsoft.com/en-us/kb/3061064


The Fixes included in this CU are:
  • 4458680 Skype for Business Web App or Skype Meeting App doesn’t respect conferencing policy for AllowParticipantControl and AllowExternalUserControl
  • 4458689 Skype for Business on Mac can’t save a password when AllowSaveCredentials is False and “Keep me signed in” is selected
  • 4464370 Skype for Business UCWA clients can’t be distinguished on CDR report if connection is internal or external
  • 4458698 Notify Skype for Business on Mac and mobile users that the conversation is an interop conversation in Skype for Business Server 2015
  • 4345985 “Failed to setup database rtcxds” error when you upgrade the SQL Server 2008 R2 back-end database in Skype for Business Server 2015
  • 4132306 Invitee visibility delay when a UCMA application uses AudioVideoMcuSession.BeginDialOut to create a conference
  • 4458688 Support to prevent external file transfer especially for Skype for Business on Mac users in Skype for Business Server 2015
  • 4458695 QoE Call Detail SubReport shows a wrong caller/callee connection type in Skype for Business Server 2015
  • 4459712 Update parameters of Move- CsUser in Skype for Business Server 2015
  • 4458691 Optionally turning on/off the OAuth protocol is available in Skype for Business Server 2015
  • 4458694 New trusted application endpoints are always assigned to the same routing group in Skype for Business Server 2015
  • 4458676 Busy Options settings are removed if you change the Call Forwarding settings with a mobile device or third-party phone device in Skype for Business Server 2015
  • 4458679 Inactive RGS workflow that has deleted queues can’t be imported by Import-CsRgsConfiguration in Skype for Business Server 2015
  • 4458686 Configuring a watcher node test user fails in the German version of Skype for Business Server 2015
  • 4458684 Local Configuration Store can’t be installed when disabling TLS 1.0/1.1 in Skype for Business Server 2015
  • 4343061 Event ID 1000 (0xc0000005) and RtcSrv.exe of the SBA/SBS crashes after startup in Skype for Business 2015 and Lync Server 2013
  • 4458683 Can’t switch the meeting audio to a UCWA client in Skype for Business Server 2015
  • 4458682 “Failed creating application activity” error when you use the Test-CsUcwaConference cmdlet in Skype for Business Server 2015
  • 4458677 Escalation to LBR VoIP user fails when a same site LBR user is in a P2P call with a PSTN user in Skype for Business Server 2015
  • 4458693 Can’t join a LBR enabled conference after a user uses the “Call me at” feature in Skype for Business Server 2015
  • 4458697 Skype for Business Front-End servers connecting to Exchange online for OAuth doesn’t use proxy server
  • 4458692 Incorrect caller ID is shown on the Skype for Business client in a call-forwarding scenario
  • 4458690 RGS call forwarding to a queue or SIP address not working in Skype for Business Server 2015
  • 4464374 Can’t create a Skype meeting on behalf of someone else by using the Outlook for Mac client in Skype for Business Server 2015
  • 4464375 The Test-CsPhoneBootstrap and Test-CsClientAuth cmdlets not working in Skype for Business Server 2015 that’s installed on Windows Server 2016
  • 4464372 Skype for Business Server 2015 UCMA services crash on service startup when running on Windows Server 2016
  • 4464373 Can’t escalate a peer-to-peer call to a conference if VbSS is used in screen-sharing in Skype for Business on Mac
  • 4464371 Support Rate my Call feature for Skype for Business UCWA clients in Skype for Business Server 2015
  • 4458678 Skype for Business VbSS application sharing not working for UCMA based Contact Center in Skype for Business Server 2015
  • 4458687 “An error occurred during this screen presentation” error occurs in VbSS application sharing conference in Skype for Business Server 2015
  • 4470530 Can’t make an outbound PSTN call by using Skype for Business on Mac if LBR is enabled
  • 4470531 Support moving users from on-premises to Teams in Skype for Business Server 2015
As always happy SKYPE'ing

tirsdag den 6. november 2018

Bye Bye SFBOnline part 2

At Ignite this year it was announced that automatic Teams upgrades will begin November 1. 2018 for SFBOnline organisations (without enterprise voice)

Microsoft has already started offering automatic updates from Skype for Business Online to Microsoft Teams for their direct customers. Starting from November 1. 2018, Microsoft will extend this offer to partner-associated customers, administrators will be given advanced notice via email and through the Office 365 Message Centre.

And this morning November 6. we got the upgrade message on our own tenant.
Yeah i know its in Danish - but you get the picture :)

And those of your running tenants with less that 500 users - better start preparing.

If and how this will affect your org depends on how you use SFBOnline today - example, if you run Enterprise Voice automatic upgrades will NOT be offered.

  • Organizations below 500 employees who are currently looking to deploy Skype for Business Online will now only be able to deploy Teams.    
  • Any organization currently on Skype for Business Online (without Enterprise Voice) can continue using Skype for Business.  However, starting November 1st, these organizations will be upgraded to Teams over the coming months. 
    • Organizations not interested in automatically upgrading can contact support on how to disable or postpone the upgrade.
  • Organizations currently on Skype for Business Online with Enterprise Voice functionality can continue using Skype for Business, these organizations will not be moved to Teams starting November 1.   
  • Organizations over 500 employees currently looking to deploy Skype for Business Online will still be able to but may want to consider Teams as it will eventually be the primary communications tool in Office 365.  

So what now - should we panic ? 

No definitely not - you should upgrade :) The thing to do as an admin is to get up to speed ASAP on what this change means for your users and your organisation - and get ready to do the upgrade.
Luckily Microsoft has provided TONS of info, guidelines tips and tricks nicely packaged in a small user friendly framework

This Breaks down as I see it into these main areas of focus:


  1. Define the people that need to be involved in planning and executing the upgrade.
  2. Define the scope, timeline and key success factors.
  3. Ensuring technical readiness - both on endpoints and on your corp network
  4. End-user readiness - training and awareness.
  5. Executing the upgrade steps in a controlled matter
  6. Measure your KPI's on usage, performance and user involvement.
As mentioned Microsoft has made ready a whole bunch of resources, I will highlight a few.
All are accessed through the link in the notification email.

During the whole process user involvement is key and from early info on the upgrade to actually ensuring that they embrace and adopt Teams - use these great email templates.

Understand the different journeys and modes to use during the upgrade:

Make sure to train yourself and your admins / Superuser early

Make sure the network is ready (assuming you already run SFBOnline it probably is)

The actual upgrade:

Monitor the quality



Thats it for now, as always happy Skype'ing.. or Teaming i guess. :)




lørdag den 6. oktober 2018

Answer AA and Call queues from Teams

Call Queues and Auto Attendants has now gone GA for Teams use.

This is a big thing, enabling the Teams users to be a part of the already created Call queues and Auto attendants for the customer.

An important prerequisite is that you have already gone through Interop and Upgrade configuration.
https://docs.microsoft.com/en-us/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype

As users are used to in SFBO, the Teams users will be able to differentiate between incoming CC calls and direct calls, both visually in the toast, and through different ringtones.

The Toast:

The settings:


This is another important step for organisations that are considering or planning the move to Teams as their enterprise Voice platform.

However early tests are showing some delays in Call routing process... also on SFBO calls through Call Queues often lag 3-5 seconds before Toast arrives, but on Teams it seems worse, this will hopefully be adressed ASAP by MS

Go to the Techcommunity Blog for further details
https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Answer-Auto-Attendant-and-Call-Queue-calls-directly-from-Teams/ba-p/222382

torsdag den 4. oktober 2018

Bye Bye SFBO

From the beginning of Time (When Teams was launched) we all patiently awaited the day where MS would announce feature parity - and when they finally did - i guess the recent announcement at MS Ignite last week was no big surprise after all.

And we all knew that eventually Teams would replace SFBO - and that integration was already in place


Now that this integration is complete, Microsoft are planning to make Microsoft Teams the primary communications client in Office 365.

Most importantly, from 1st October 2018, new Office 365 customers with 500 seats or less will be onboarded to Microsoft Teams and will not have the ability to use Skype for Business Online.

If you already have customers that are using Skype for Business Online, they will still be able to do so (and this includes the new users that they might provision) until they complete their transition to Microsoft Teams.

Microsoft has already started offering automatic updates from Skype for Business Online to Microsoft Teams for their direct customers. Starting from November 1. 2018, Microsoft will extend this offer to partner-associated customers, administrators will be given advanced notice via email and through the Office 365 Message Centre.


So for those of you who either has a new SMB customer in the making with plans of utilizing SFBOnline, or even a larger customer that hoped to do POC on a new tenant - well i Guess plans have changed.

Source: Tony Redmond - and announcement made at Ignite2018
https://techcommunity.microsoft.com/t5/Microsoft-Teams/No-Skype-for-Business-Online-for-Small-Office-365-Tenants/td-p/261062



BUT as always - HAPPY SKYPE'ing