Additions : 7
Updates : 5
Regards
The Author – Blogabout.Cloud
Check what Outlook versions are connecting to you Exchange servers
If you are running Exchange 2010, 2013, 2016 or 2019. You will need to run the following PowerShell script and in this example I am going to be targeting Exchange 2010.
# This is just default path to Exchange 2010 RPC logs. Change it to match your Exchange version.
$logpath = 'C:\Program Files\Microsoft\Exchange Server\V14\Logging\RPC Client Access'
# We limit the amount of logs by timeframe. This is to get more current view.
$files = Get-ChildItem $logpath |Where-Object {$_.LastWriteTime -ge (Get-Date).AddDays(-15)}
# Now, let's get the logs.
$logs = $files | ForEach {Get-Content $_.FullName}| Where-Object {$_ -notlike '#*'}
# We covert the data to PowerShell objects
$result = $logs |ConvertFrom-Csv -Header date-time,session-id,seq-number,client-name,organization-info,client-software,client-software-version,client-mode,client-ip,server-ip,protocol,application-id,operation,rpc-status,processing-time,operation-specific,failures
# And finally we filter the client information and group it by version number.
$result | Where-Object {$_.'client-software' -eq 'OUTLOOK.EXE'}|group client-software-version
Once you have obtained the required information, you need identity which Outlook version is contacting to your Exchange server by using the following table.
| Version number | Name |
| 5.0.3165.0 | Outlook 2000 |
| 6.0.7654.12 | Outlook 2000 |
| 6.0.8153.0 | Outlook 2000 |
| 6.0.8165.0 | Outlook 2000 |
| 6.0.8211.0 | Outlook 2000 |
| 6.0.8244.0 | Outlook 2000 |
| 10.0.0.2627 | Outlook 2002 |
| 10.0.0.4115 | Outlook 2002 SP2 |
| 10.0.0.6515 | Outlook 2002 SP3 |
| 10.0.0.6742 | Outlook 2002 SP3 |
| 11.0.5604.0 | Outlook 2003 |
| 11.0.6352.0 | Outlook 2003 SP1 |
| 11.0.6555.0 | Outlook 2003 SP2 |
| 11.0.8000.0 | Outlook 2003 SP2 |
| 11.0.8161.0 | Outlook 2003 SP3 |
| 11.0.8200.0 | Outlook 2003 SP3 |
| 11.0.8303.0 | Outlook 2003 SP3 |
| 12.0.4518.1014 | Outlook 2007 RTM |
| 12.0.6024.5000 | Outlook 2007 RTM |
| 12.0.6211.1000 | Outlook 2007 SP1 |
| 12.0.6300.5000 | Outlook 2007 SP1 |
| 12.0.6315.5000 | Outlook 2007 SP1 |
| 12.0.6423.1000 | Outlook 2007 SP2 |
| 12.0.6504.5001 | Outlook 2007 SP2 |
| 12.0.6509.5000 | Outlook 2007 SP2 |
| 12.0.6529.5000 | Outlook 2007 SP2 |
| 12.0.6539.5000 | Outlook 2007 SP2 |
| 12.0.6550.5000 | Outlook 2007 SP2 |
| 12.0.6554.5000 | Outlook 2007 SP2 |
| 12.0.6557.5000 | Outlook 2007 SP2 |
| 12.0.6562.5003 | Outlook 2007 SP2 |
| 12.0.6606.1000 | Outlook 2007 SP3 |
| 12.0.6661.5000 | Outlook 2007 SP3 |
| 12.0.6665.5000 | Outlook 2007 SP3 |
| 14.0.4734.1000 | Outlook 2010 RTM |
| 14.0.6025.1000 | Outlook 2010 SP1 |
| 14.0.6109.5000 | Outlook 2010 SP1 |
| 14.0.6117.5001 | Outlook 2010 SP1 |
| 14.0.7151.5000 | Outlook 2010 |
| 14.0.7157.5000 | Outlook 2010 |
| 14.0.7160.5000 | Outlook 2010 |
| 15.0.4128.1019 | Outlook 2013 Preview |
| 15.0.4727.1000 | Outlook 2013 |
| 15.0.4753.1003 | Outlook 2013 |
| 16.0.4229.1029 | Outlook 2016 |
Regards
The Author – Blogabout.Cloud
Whats new in the microsoft 365 Roadmap today? 24th February 2021
Additions : 7
Updates : 38
| New Features | Current Status |
| Forms: Split sending and sharing entry point | In Development |
| Microsoft Forms: Correct Answer choice feature added to Microsoft Forms Poll in Teams Meetings | In Development |
| Microsoft Teams: AI based historical poll suggestion for Teams meeting | In Development |
| Microsoft Teams: AI based option suggestion for Teams meeting polls | In Development |
| Microsoft Teams: AI based poll question suggestion for Teams meeting | In Development |
| Microsoft Teams: Data reports after Teams meeting class | In Development |
| Microsoft Teams: Data reports for polls after Teams meeting | In Development |
Regards
The Author – Blogabout.Cloud
Whats new in the microsoft 365 Roadmap today? 23rd February 2021
Additions : 0
Updates : 2
| Updated Features | Current Status | Update Type | ||
|---|---|---|---|---|
| Microsoft Defender for Office 365: Blocking URLs and Files with Tenant Allow/Block List | Rolling Out | Status | ||
| Exchange: Online – Tag for external email messages received | In Development | Title, Description |
Regards
The Author – Blogabout.Cloud
Deploying Webex Call App in Microsoft Teams
In this post I am going to show you how to install the Webex Call app for your end users at a administrative level from the Microsoft Teams console.
So in April 2020, Cisco announced a new Call App for Microsoft Teams. The app launches calls through Webex technology, even when you click the call button in Microsoft Teams.
To access this functionality, follow these steps:
- Verify users have accounts activated in the Webex Control Hub
- Ensure users are registered to the Cisco Webex Calling or Unified Communications Manager
- Make sure users have the Webex app
- Ensure you have Administrator privileges for Microsoft Teams
- Update phone numbers for users in the Azure Active Directory
So lets get to it;
Launch https://admin.teams.microsoft.com
Go to Teams App –> Setup Policies
Best Practice / Recommendations
It is always best practice not to modify the Global (Org-wide default) policies. It recommended to create a new policy which will limit impact to the production environment.
Once you have either create a new policy or decided to modify the global policy. Click Add Apps
Search for Insights and click Add
While in the policy you may decide to add Insights as a Pinned App, you will need to add Insights app as shown below
Click Save
The Webex call application will now be installed and added to pinned apps with the Teams Client. As a global admin launch the application for the first time to approve the application in your Microsoft tenant.
As you can see below you now have the ability to make Webex call through Microsoft Teams.
Now for the Pros / Cons.
Pros:
- Simple way to connect Webex calling functionality with Microsoft Teams
- Embedded buttons in Teams make the function easy to use
Cons:
- Only works to connect two VoIP calling strategies. You can’t connect your chat messages or file sharing this way.
- Calling opens a new window, which means there are more tabs for users to keep track of.
- Only works to add Webex Calling to Microsoft Teams. You can’t add Microsoft calling to Webex instead.
Regards
The Author – Blogabout.Cloud
Install the microsoft Viva Insights app within your organization
In this post I am going to show you how to install the Microsoft Viva Insights app for your end users at a administrative level from the Microsoft Teams console. So lets get to it;
Launch https://admin.teams.microsoft.com
Go to Teams App –> Setup Policies
Best Practice / Recommendations
It is always best practice not to modify the Global (Org-wide default) policies. It recommended to create a new policy which will limit impact to the production environment.
Once you have either create a new policy or decided to modify the global policy. Click Add Apps
Search for Insights and click Add
While in the policy you may decide to add Insights as a Pinned App, you will need to add Insights app as shown below
Click Save
The Insights applications will now be installed and added to pinned apps with the Teams Client
Regards
The Author – Blogabout.Cloud
Whats new in the Microsoft 365 Roadmap today? 20th February 2021
Additions : 1
Updates : 6
| New Features | Current Status | |||
|---|---|---|---|---|
| SharePoint: Page Analytics | In Development | |||
| Updated Features | Current Status | Update Type | ||
| Information Governance: New retention engine for SPO | Launched | Status | ||
| Planner: More labels | In Development | Description | ||
| Outlook for Android: Text predictions | Rolling Out | Status | ||
| Microsoft Teams: Block Downloads for Teams meeting recordings on OneDrive and SharePoint | In Development | Status | ||
| SharePoint: Image Lightbox | Rolling Out | Status | ||
| Microsoft Planner: More labels | In Development | Title, Description | ||
| Microsoft Teams: Block Downloads for non-channel Teams meeting recordings on OneDrive | In Development | Title, Description | ||
| Forms: Specific User Sharing for Response Collection | Rolling Out | Status |
Regards
The Author – Blogabout.Cloud
Deploying WebEX Add-in for Microsoft 365 using centralized Deployment
Before deploying anything from the Centralized Deployment it is recommended that you check if your organisation supports this process.
This can be easily done by installing the following MSI and running the following PowerShell Cmdlets;
https://www.microsoft.com/en-us/download/details.aspx?id=55270
Import-Module O365CompatibilityChecker Invoke-CompatibilityCheck
During my testing, I had to manually connect to Exchange Online using the following cmdlet;
Connect-ExchangeOnline
Once I had manually connected to Exchange Online the Invoke command completed successful and drop the output file here;
c:\windows\system32 called output.csv
In the containing csv file you will see something like below.
If your organization meets all requirements, complete the following steps to publish an Office Add-in via Centralized Deployment:
- Sign in to Microsoft 365 Admin Portal and select Integrated apps
- Click Get apps
Search for Cisco Webex;
As you can see from below you are returned with 3 options
– Cisco Web Scheduler
– Cisco Webex Teams
– Cisco Webex Meetings – This completed by Azure AD Apps
I am now going to install Scheduler and Teams in this article. Click Get it now
Click Continue
Specify who the app for as per the screenshot below
Press Next
Press Next
Press Finish Deployment
It may take about 24 hours before the Add-In is available on the client device.
Regards
The Author – Blogabout.Cloud
Whats new in the Microsoft 365 Roadmap today? 19th February 2021
Additions : 5
Updates : 8
Regards
The Author – Blogabout.Cloud
Whats new in the Microsoft 365 Roadmap today? 18th February 2021
Additions : 1
Updates : 16
Regards
The Author – Blogabout.Cloud