Finally, a lighter version of the Persistent Chat (within Skype for Business Server / Lync Server) is launched which can be easily activated with a simple flip of a switch. Microsoft Teams was launched earlier this month as part of the Office 365 subscription – which is available on Business Essentials, Business Premium, Enterprise E1, E3 and E5. (Reference: Introducing Microsoft Teams)

If you happen to be on either of the subscribed plan(s) mentioned earlier, login to your Office 365 Admin Center and follow the step-by-step guide:


  1. At the Admin Center, Select on Apps > Microsoft Team
  2. “Flip” on the ON switch at the top right and click on Save


So when that’s done, download the Microsoft Teams client App here and you can start creating your own Virtual Groups / Teams and start collaborating!


Hello and Happy Monday! Yes, I know and I’m sorry that I’d left my blog “in the cold” as life-work and business has took away most of my time since I’ve started my own (Woo-Hoo!). In this article, I’m about to share about another Cloud platform which involves integration with Microsoft Office 365.

As the industry “all” moves to the cloud, the dependencies of deploying and configuring Cloud platforms gradually increases as well.

Recently, I was involved with an Office 365 with Symantec.Cloud integrated (Mail & Web) and we’d to setup a Schemus Server (similar to Microsoft’s Azure AD Connect) which synchronizes the Active Directory’s Users and Objects to Symantec.Cloud platform. Activating the tenant was pretty straight forward as we already had the tenant ready during the evaluation stage (Proof-of-Concept), next thing is to configure Schemus.

While trying to establish the relationship between the Symantec.Cloud with Schemus, the following error message was presented on the setup window:







Can’t access the Symantec.Cloud service. There was a problem communicating with the Symantec.Cloud service server: WS Security The message has expired (WSSecurityEngine: Invalid timestamp The security semantics of the message have expired)

To resolve this issue, make sure the following entries are in-place:

  1. If you’ve recently changes your password for Symantec.Cloud service, update your most recent password at Schemus Configuration OR at the Schemus Windows, click on Edit > Settings > Symantec.Cloud and modify password field
  2. Make sure that the specified URL is accessible and not filtered/blocked by the Firewall
  3. System Time is the same as the Internet time







We ran into the issue on item #3 and what we’d to do was just simply modify the system clock and click on Apply. Close the Schemus and re-launch the settings window and Walla! the problem went away. Based on Symantec Technical Support, updating the system clock to establish the communication with Symantec.Cloud is only one-time off, so for those organizations whom aren’t following the Internet time, the Schemus server would be able to resync its time with either the Active Directory or NTP Server.

I’ve just notice my past articles that on Skype4B / Lync Room Systems, it appears that I’ve missed out a guide on how to provision the Room System via Office 365. To perform this tasks, it is assume that your tenant has an Exchange Online Plan 1 with Skype for Business Online Plan 1 (Office 365 Business Essentials / Premium / E1 / E3 / E4) in-place.

  1. First, logon to your Office 365 Admin Portal and launch the Exchange Admin Center page
  2. Create / Provision an Resource (Room) Mailbox.  Give the ‘Room’ a name (example: MY-KUA-Meeting Room) and an Email Address (Mandatory). The rest of the fields are optional
  3. Once complete, launch the Windows Azure Active Directory Module for PowerShell as Administration (Run As Administrator)
  4. Key in the following command line:

Set-ExecutionPolicy Unrestricted
$cred=Get-Credential admin@$org
$sess=New-PSSession –ConfigurationName -Credential $cred -AllowRedirection -Authentication basic -ConnectionUri
Import-PSSession $sess
$password = Read-Host “Enter password” -AsSecureString
set-Mailbox -Identity $rm -type Room -EnableRoomMailboxAccount $true -RoomMailboxPassword $password
Set-CalendarProcessing -Identity SmartRoom -AutomateProcessing AutoAccept
Set-CalendarProcessing -Identity SmartRoom -AddOrganizerToSubject $false –DeleteSubject $false

Close the PowerShell window screen and login using the account that has been provisioned earlier onto the Room System.


I would like to thank all of my friends & visitors whom visited (or still visits) my site. I hope the materials posted are helpful and your continuous support are highly appreciated!

Here’s a summary of how my Blog Site throughout 2015:

The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 35,000 times in 2015. If it were a concert at Sydney Opera House, it would take about 13 sold-out performances for that many people to see it.

Click here to see the complete report.

After months of the official launching of Windows 10, since it was a public holiday yesterday and I finally get to “cool off” myself to run an upgrade my DELL Latitude E7440 running on Windows 10 Insider Preview to a RTM. As most laptops doesn’t come with any DVD ROM (including mine) any longer, all I’d to do is extract the ISO contents into a USB thumb drive and run the bootsect cmdlet to make the USB bootable.

I’d an existing partition from a single disk and I’ve stored most of my important files & documents on the second partition, so all I’d to do is select the partition which I intend to wipe out and give a fresh installation to my laptop during the Windows 10 wizard setup. Well… life isn’t that straight forward as expected when I’d selected the partition that I’d wish to install Windows 10 after deleting a couple of other partitions from the previous setup, the wizard had stopped me from moving forward with the following error message:

Windows cannot be installed to this disk. The selected disk is of the GPT partition style

OK – this isn’t good as I’d not make any external backups of my files and I can’t wipe off the entire disk (the second drive is actually just a partition) to convert it to MBR so allow the Windows 10 setup continue. At first I thought it was due to the UEFI hardware compatibility issue, so I’d tried changing the BIOS settings into allowing legacy devices but no luck, the wizard still returns with the same error message and selecting the second partition doesn’t help as well (Duh, the entire disk has been GPT’ed)

A quick search on the Internet saved my day – basically there’s a tool known as Rufus actually allows to abstract ISO images and create into a bootable USB. Using this sneaky little tool, all I’d to do is select the following settings on Rufus:

Rufus ISO Bootable

  • Select the USB thumb drive that you intend to extract the ISO contents into
  • GPT Partition schema for UEFI (*IMPORTANT*)
  • NTFS File System
  • Select the Windows 10 ISO image
  • Leave the remaining options to its own default values
Click Start to create the Windows 10 USB Bootable Media and there you go, another Windows 10 into an existing laptop🙂

My colleague and I were running a project of Office 365 with a given THIN timeframe, we’d ran a couple of research looking for scripts to enable the Office 365 Users with the appropriate license and customized to fit into ours and I would like to take this opportunity to share this to those who need help on this as well.

With the given scenario & environment:

  • Running on Azure ADSync & ADFS 3.0
  • All User Objects has been synchronized to the Office 365
  • You manage to export all of the sync users into a CSV format

To do this, launch the Azure Active Directory module for PowerShell:

  1. Connect to the Microsoft Online Services (Connect-MSOLService)
  2. Find out what SKU or Plans that you’re entitled or Subscribed using Get-MSOLAccountSKU. The PowerShell cmdlet should return you with the following format: Tenant:ENTERPRISEPACK
  3. Next, declare the environment variables for Path where the CSV is stored and the type of License queried earlier at Step 2
    $path = “<Drive Letter>:\Filename.csv” (“D:\MSOLE3.csv”)
    $lic = Tenant:ENTERPRISEPACK
  4. Now, you’re ready to assign the licenses with this cmdlet
    Import-Csv $path | foreach {Set-MsolUserLicense -UserPrincipalName $_.UserPrincipalName -AddLicenses “$lic”} -Verbose
  5. Once it is done, verify the licenses are correctly assigned:
    Import-CSV $path | Get-MSOLUSer | Out-GridView

Just recently participated in the Skype for Business ELITE Training (APAC) in Singapore, part of this training is to ensure Customers are able to maximize the full potential of SfB 2015 – through Adoption activities.

Microsoft has release a couple of RASK along the way since Lync 2010 and Lync 2013; now with On-Premise, Cloud as well as Hybrid deployment available, the features, functions and most importantly User Experiences differs based each organizations’ deployment mode. This Year – Rollout Adoption & Success Kit 2015 is released as well!

I won’t be covering the entire contents through this Blog but hopefully I’m able to share some of my experiences using these resources; feel free and download the contents from here – Skype for Business 2015 Rollout Adoption & Success Kit

I’d a deployment recently where the customer wanted to seek feedback from the employees in a mass while leveraging on their Office 365 E3 Plan, in which Yammer Enterprise was the prefect answer to this scenario.

This was a greenfield deployment as no users was on the platform yet and we’ve decided to use Azure ADSync to synchronize all User Objects to the Office 365 Cloud. The synchronization was a smooth sailing one and activating Yammer based on this guide – Yammer Activation Guide and this guide – Changing SharePoint Online Newsfeed to Yammer Enterprise.

Upon logging onto the Microsoft Office 365 main page ( and selecting the Yammer tile, Yammer page couldn’t seem to be loaded and we’re redirected to this page with an error message:

Sorry, but we’re having trouble signing you in. We received a bad request

Yammer-SSO 01


When attempting to directly login via Yammer, the page was not redirected to the Office 365 Portal Login page and we keep receiving that the username & password was incorrect. As the usage of the platform was top priority, we’d to raise a support service request with Microsoft Office 365 Support Team – luckily the issue was easily resolved by perform the followings:

  1. Login to the Office 365 Admin Portal, go to Admin > SharePoint
    Yammer-SSO 02
  2. Click on Settings
    Yammer-SSO 03
  3. Under the Enterprise Social Collaboration option, select back to Use SharePoint Newsfeed (default) and wait for an hour (personal recommendation) and click OK
    Yammer-SSO 04
  4. After an hour, switch back to Use Yammer Service and click OK
    Yammer-SSO 05

Once that is done, the Single-Sign On has been resolved and users can now login using the same credentials as the Office 365/On-Premise Active Directory.

 Take away lessons: During the troubleshooting process, the Yammer team had sent a separate activation email to the Portal Admin in which doesn’t fix the Single-Sign On issue but further complex the situation – in which all users are able to login to Yammer but the password will be different with the Office 365 Portal. Use the steps above and see whether if this works. Else fail, you can use the Yammer Directory Sync tool to synchronized both user accounts and password before escalating back to the Office 365 Technical Support. 

This is somewhat a “throwback” article (sigh, time to look for a new ISP Provider) as the post was stuck at my draft till it was “officially” published😦

Although there’re various materials available from the Internet on how to join a Lync Online Meeting – either through Lync On-Premise or Office 365, I’d came out with a short guide to help some customers/readers especially users whom are part of the organization but still wishes to use Lync Online Meeting to join meetings.

  1. Usually you’ll receive an Online Meeting Calendar invite from the sender, within the content it as a hyperlink/URL with the word Join Online Meeting
  2. Upon clicking the Lync Meeting URL, the web page brings you to Online Meeting page which it’ll starts detecting whether you have a native Lync Client installed. If not, you’ve an option to use Lync Web App
  3. Usually you’ll join as a Participant (Guest). Upon loading up the page, type in your preferred display name to join the meeting. If this is the first time joining such meeting and there is not Lync Web App Plugin detected, you’ll see this:-
  4. Select the Install Lync Web App plug-in and click on Join the Meeting
  5. Select RUN when prompted
  6. Lync Web App plugin will then start the installation
  7. Once the installation completes, the web page will automatically refreshes. Type in an appropriate Name and Select on the Join the Meeting
  8. You’ll be placed at the Lync Virtual Lobby till the presenter verifies your identity and Admits you into the Meeting session
  9. If you receive a warning message, select on Allow to grant the plugin permission to interact with your machine. I would recommend to select the Always allow the plug-in for this domain to ease future access
  10. If you’re Windows Firewall is enabled, select on Allow access to grant access for the plugin. If this is not available, you may need to grant the it manually from the Windows Firewall option. If you do not grant the plugin through the Windows firewall, you’ll experience difficulties such as there’re no output for its audio and/or video during the meeting session
  11. Once you’re done, Enjoy the Meeting!

Many thanks to @KatherineChen as the meeting organization and initiator for this guide to help out the SEA MVP in joining our monthly MVP Meetings!

Recently I’d carried out a Proof-of-Concept (PoC) for a customer on a SMART Lync Room System (LRS) to replaced their existing Video Conferencing solution – which isn’t too “Unified”, several limitation when it comes to Group Meetings and worse off is the user experience was horrible (and that’s why I’d the opportunity to go in)

The PoC was straight forward where the LRS will be connected to Microsoft Office 365 account where it can be easily configured and demonstrated; simply just an account for the LRS which has Exchange & Lync license assigned would get the entire LRS up and running. However, it wasn’t as smooth as it seems as when the Exchange Calendar doesn’t appear and the “Round Loading Screen” keeps rotating.

Thanks to a good friend from the Lync/Skype for Business MVP @OliverMoazzezi, he’d pointed out that there was a bug within LRS and a temporary workaround can easily solve this issue:

  1. Reboot the System into Admin Mode
  2. Select the Network Connection Configuration. At the Network Connections Windows, activated the Address Bar and type Regedit which opens up the Registry Editor
  3. Maneuver to HKLM\Software\Microsoft\Office\15.0\Lync > Right Click on the Key (icon shows as folder) > Permissions.. > Click on Add > type in Everyone > Grant Full Control                LRS-Registry-Permissions
  4. Reboot the System and the Exchange Calendar will appear

For On-Premise LRS User, you may refer to for additional steps to resolve the similar issue.

%d bloggers like this: