Microsoft Teams vs Cisco WebEx for Meetings

Creating a new teams meeting is as easy as clicking New Teams Meeting in the Office ribbon. It’s built-in to Office.

image

Just one click, add a Title, add attendees, and click Send.

With WebEx, you must first create a New Meeting, then add WebEx to the meeting or click Schedule Meeting in the ribbon via with a 3rd party plug-in.  Since it doesn’t fill in the meeting location field, a pop-up needs to be dismissed to send – another extra click.

Converting an existing meeting to a Microsoft Teams meeting is easy as well. Just open the meeting delete the WebEx content in the body (below the line – Do not delete or change any of the following text. –), click Teams Meeting in the ribbon, and click Send Update.

image

Doing so not only results in the Teams meeting experience, but joining the meeting is now easier too.

To join a WebEx meeting, one must first open the meeting, then click the link.  Sometimes one needs to enter their personal info before clicking Join Meeting, and if the meeting is hosted in a personal room, the meeting can’t start without the host (which is a pain if the person is on vacation).  Notifying the host requires a captcha to be entered. It’s just one hassle after another. After all of this, you’re finally able to select the means of connecting to the call. Even if the meeting starts while you’re waiting, you won’t join the meeting until this step is completed.

Contrast this to Teams. If the meeting is selected in your Outlook calendar, a Join Teams Meeting button appears in the ribbon.

 image

Clicking this takes you straight to the audio/video preview to allow you to adjust your settings before joining the meeting and simply pressing <Enter> or clicking Join now adds you to the meeting.

Meeting attendees also have the option of right-clicking the meeting and clicking the Join Teams Meeting option.

image

So there you have it. Teams meetings are easier to set-up, and easier to join than meetings in WebEx, and all of that saved time adds up – so start converting your old WebEx meetings today! Smile

Mirror: mPING WEATHER TYPES EXPLAINED

In December of 2018, the US Government initiated a shutdown of non-essential services.  As part of this, I noticed that apps like mPING which are used for reporting weather conditions began to have broken links. 

Non-essential Government employees such as the NOAA.gov webmasters threw a tantrum associated with being told that they were “non-essential”.  As a result, even though the servers were humming along just fine, these workers blocked access to their content for the duration of the “shutdown” with a message politely explaining that they would be holding their non-essential information hostage until they were allowed to continue suckling at the teet of the State.

I was hoping to find a mirror for the info but couldn’t immediately.  Now that the Government has resumed it’s non-essential operations (at great economic expense to innocent Software Engineers like myself), I was able to obtain a copy of the information which I will mirror below.

Enjoy!

PS: Another archive of this information exists here: https://web.archive.org/web/*/https://mping.nssl.noaa.gov/types.php


What are all of those weather types that are listed in the mPING app? How do you tell the difference between freezing rain and freezing drizzle?

Test
Sends a test report to confirm that NSSL received your report; you will see a small yellow X appear to show your report was received
Rain and/or Snow
None

No precipitation occurring; most useful shortly before precipitation begins and after it ends

Drizzle

Very small, numerous and uniformly distributed water drops that may appear to float while following air currents

Freezing Drizzle

Drizzle that falls in liquid form but freezes upon impact to form a coating of glaze ice

Rain

Liquid water drops falling that do not freeze upon impact

Freezing Rain

Rain that falls in liquid form but freezes upon impact to form a coating of glaze on exposed objects (this will occur well before any ice forms on the ground)

Ice Pellets/Sleet

Small translucent balls of ice cosisting of frozen raindrops (not to be confused with hail)

Snow

Frozen precipitation in the form of flakes of ice crystals

Mixed Rain & Snow

Usually has the consistency of slush; almost never results in any accumulation

Mixed Rain & Ice Pellets

Often occurs as wet ice pellets mixed with small raindrops; sometimes occurs as falling raindrops containing one or perhaps few small pieces or chunks of ice (not snow)

Mixed ice Pellets & Snow

Snow along with ice pellets; the snowflakes don’t have ice pellets at their core as with ice pellets mixed with rain
Hail (include size)
A chunk of ice falling from the sky ranging from the size of a pea to a grapefruit; hail occurs exclusively in thunderstorms. Sleet is not tiny hail but is instead produced by a different process.
Wind Damage
Severity 1 (Damage Trivial)

Lawn furniture & trash cans displaced; small twigs broken off

Severity 2 (Damage Mild)

1 inch tree limbs broken; shingles blown off

Severity 3 (Damage Moderate)

3 inch tree limbs broken; power poles down

Severity 4 (Damage Severe)

Large trees uprooted or snapped; roofs blown off

Severity 5 (Damage Extreme)

Homes and buildings destroyed
Water Spout
Not displayed but sent to the NWS
Tornado (on ground)
Not displayed but sent to the NWS
Flood
Severity 1 (Flood Minor)

River/creek overflowing; cropland/yard/basement flooding

Severity 2 (Flood Moderate)

Street/road flooding; stranded vehicles

Severity 3 (Flood Serious)

Homes and buildings filled with water

Severity 4 (Flood Severe)

Homes, buildings and cars swept away
Mudslide/Landslide
Most often areas of soil mud that becomes loose due to lots of rainfall and then slides down a hilside; sometimes an entire hillside will come loose in a layer and slide
Reduced Visibility
Dense Fog

Visibility reduction caused by very tiny condensed water droplets so small that they cannot be individually distinguished; essentially a cloud on the ground

Blowing Dust/Sand

Visibility reduction caused by strong winds lofting sand and dust, most often from dry and barren soil

Upgrading SSRS Tooling

Over the years I’ve been told that in order to support SQL Server Reporting Services (SSRS) files (RDL) that I had to install the decade-old Visual Studio 2008 product.

More recently, I came across some info that indicates that this may not be the case, so I’m sharing it here in case it is able to help someone upgrade to current tools.

VS 2008

To work on SSRS reports (RDL files) one needs Visual Studio 2008 with the BIDS extension installed.

BIDS download – https://www.microsoft.com/en-us/download/details.aspx?id=30438

Note

Historically, the Visual Studio shell used to create SQL Server content types has been released under various names, including SQL Server Data Tools, SQL Server Data Tools – Business Intelligence, and Business Intelligence Development Studio. Previous versions came with distinct sets of project templates. To get all of the project templates together in one SSDT, you need the newest version. Otherwise, you will probably need to install multiple previous versions to get all of the templates used in SQL Server. Only one shell is installed per version of Visual Studio; installing a second SSDT just adds the missing templates.

SOURCE: https://docs.microsoft.com/en-us/sql/ssdt/previous-releases-of-sql-server-data-tools-ssdt-and-ssdt-bi

VS 2017

It may be possible to work on SSRS reports with Visual Studio 2017 via the Microsoft Reporting Services Projects add-on.

https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio

This requires the SQL Server Data Tools (SSDT) workflow to be installed via the VS 2017 installer.

clip_image001

Git Fatal: Authentication failed for

Issue

> git pull –tags origin master

fatal: Authentication failed for ‘{repository URI here}’

Resolution

  1. Go to Control Panel\All Control Panel Items\Credential Manager in Windows
  2. Select Windows Credentials
  3. Scroll down to Generic Credentials
  4. Edit git: credentials with updated password

Authentication will now succeed

Upgrading Magenic/MAQS from V4 to V5

If you get an error like this while upgrading Magenic/MAQS from V4 to V5:

Severity Code Description Project File Line Suppression State
Error Could not install package ‘Microsoft.Extensions.Configuration 2.1.1’. You are trying to install this package into a project that targets ‘.NETFramework,Version=v4.5’, but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

Tried clearing the NuGet cache in VS 2017 but that didn’t help.

Solution

Troy Walsh suggested this solution…

Unfortunately, there is no clean upgrade path from V4 to V5.
The team has made several big changes, such as moving to .Net Standard 2.0, lazy initialization of the web driver, support for multiple web drivers in a single test, slitting of the config file sections and adding support for .Net Core to name just a few.

So there are 2 ways to upgrade

The hard way:

  1. Make sure you are using VS2017 or above
    https://marketplace.visualstudio.com/items?itemName=NuGetTeam.NuGetPackageManagerforVisualStudio2015#review-details
  2. Update your projects to 4.61 or above – https://docs.microsoft.com/en-us/dotnet/standard/net-standard

  3. Update your using statments
    using Magenic.MaqsFramework to using Magenic.Maqs
  4. Use the system under test configurations
    Config.GetValue(“WebSiteBase”) to SeleniumConfig.GetWebSiteBase()
  5. Remove any project references to Microsoft.VisualStudio.QualityTools.UnitTestFramework
  6. Use nuget to add the MSTest.TestAdapter package
  7. Update your app.config so it has a Selenium specific section
  8. Set the App.config to copy always

The easy way:

  1. Install the latest MAQS templates. – https://marketplace.visualstudio.com/items?itemName=vs-publisher-1465771.MAQSOpenFramework
  2. Create a new project

Copy your code into the new project
Note* You will need to update your using statements and any place you use the config settings

SOURCE: https://github.com/Magenic/MAQS/issues/5#issuecomment-407429302

Get your Groove back by making a Windows CD toaster!

 

  1. Press the Start button and type Media Player then click to open it.
    clip_image001
  2. In the Organize menu, select Options…
    clip_image002
  3. Select the Rip Music tab.
    clip_image003
  4. In your Microsoft OneDrive account, create a Music subfolder and set that as the location to save ripped music.
    clip_image004
  5. In the Rip settings section set the recording format and audio quality to your liking, but make sure the Rip CD automatically and Eject CD after ripping boxes are checked (this is what makes it act like a toaster!)
    clip_image005
  6. Install and run the Groove Music app on your Windows 10, Android, or iOS device (install from the Store if needed: https://www.microsoft.com/store/apps/9wzdncrfj3pt) and sign in using the same Microsoft Account you use for OneDrive.
  7. clip_image006

  8. Now just insert a CD in the drive and watch the magic!

 

Notes:

  1. You can set this up on any PC with OneDrive and Windows Media Player so you can rip music at home, at work, or on the go.
  2. You can also copy music files you’ve already ripped into the OneDrive – even upload them to your Music folder via OneDrive in your favorite web browser on any device.
  3. Keep in mind, once the song is ripped, it must be uploaded which depends on your Internet connection – but as long as you’re not in a hurry, the experience will be magical. I set it up for my Mom and she was able to master the process – now she has all of her favorite music wherever she goes.
  4. Anyone in select regions can do this for FREE, no subscription required. Here’s a list of the places this will work today:

Argentina, Australia, Austria, Belgium, Brazil, Canada, Denmark, Finland, France, Germany, Ireland, Italy, Mexico, Netherlands, New Zealand, Norway, Portugal, Spain, Sweden, Switzerland, United Kingdom, United States.

More info:

https://www.microsoft.com/groove/Onedrive

Cortana on Band 2 can’t reach your Phone

One of my favorite features of the Microsoft Band 2 is the voice link to Cortana – without having to un-pocket my phone.  Unfortunately, when I tried that, I got the following message.

Cortana: Sorry, I couldn't reach your phone...

Fortunately, a brief chat with MS Band Support led me to this elaborate but effective solution.

  1. Unregister the Band from within the Microsoft Health app (under My Microsoft Band in the hamburger menu [≡]).
  2. Remove the Band from your Bluetooth settings screen (tap and hold to Delete)
  3. Uninstall the Microsoft Health app
  4. Restart your phone (on Lumia 950 XL, press and hold power button until the phone vibrates – then release the power button and phone will re-start)
  5. Reinstall the Microsoft Health app
  6. Reset the Band (swipe to the Settings tile [⚙], swipe right to Power [⏻], swipe right to Reset Device and confirm your selection)
  7. Go through the Band set-up process

After this, I was able to issue voice commands to Cortana through my Band 2 again.

Update: I used the voice command feature at about 6p after resolving the issue around 1p, but by 10p when I tried to use it, the feature had failed again, displaying this message.

Update #2 (2016-04-07): I put some feelers out on common support sites for Band 2 and the Lumia 950 XL. 

Cortana on Band 2 can’t reach your Phone (answers.microsoft.com)

Cortana on Band 2 can’t reach your Phone (forums.windowscentral.com)

How often are you able to successfully use Cortana via Band 2? (Straw.pl)

How often are you able to successfully use Cortana via Band 2? (Reddit)

All I was able to learn, after several weeks, is that it’s a very common problem (which is an understatement).  At this time, here’s what we seem to have learned:

Band 2 Cortana works fine with iOS, Android, and Windows Phone 8.1 devices.

Band 2 Cortana doesn’t work with Windows 10 Mobile devices.

I took my fully updated Lumia 950 XL and Band 2 to my local MS store after scheduling an Answer Desk appointment.  I was told that this has been a known issue since November and that there seems to be very little discussion on it since then… it seems to have stalled.

Also, since my initial post, Band 2 and Microsoft Health apps have been updated and installing these updates have not resolved the issue.

It’s troubling to me that such core functionality of flagship products has gone unrepaired for six months!

Make Sure Bluetooth is on and your phone is close by

Update #3 (2016-06-09): Even though there have been several updates to Windows 10 Mobile (I’m now on Fast Ring), the Health App, and the Band 2 firmware, the problem still persists.  Rod Trent over at WinSuperSite.com has written the following article about the situation though:
Constant Problems with Windows 10 and Lumia 950 Make for Irate Microsoft Band Owners