Category: Skype for Business

December 13th, 2019 by Todd VanderArk

As artificial intelligence (AI) and machine learning systems become increasingly important to our lives, it’s critical that when they fail we understand how and why. Many research papers have been dedicated to this topic, but inconsistent vocabulary has limited their usefulness. In collaboration with Harvard University’s Berkman Klein Center, Microsoft published a series of materials that define common vocabulary that can be used to describe intentional and unintentional failures.

Read Solving the challenge of securing AI and machine learning systems to learn more about Microsoft’s AI taxonomy papers.

The post Finding a common language to describe AI security threats appeared first on Microsoft Security.

Posted in Skype for Business

December 13th, 2019 by johnacook

Migrating from Skype for Business Online to Microsoft Teams at your pace, providing its done before July 2021 o’course – Blogabout.Cloud
— Read on www.blogabout.cloud/2019/12/1125/

Posted in Skype for Business

December 13th, 2019 by Paul Lorimer

Microsoft Office 365 is now available for organizations and enterprises from our new cloud datacenter regions in Switzerland.

The post Microsoft Office 365 now available from new Swiss datacenter regions appeared first on Microsoft 365 Blog.

Posted in Skype for Business

December 13th, 2019 by Chandler Johnson
Planning a data migration and want to ensure all your metadata stays intact during the transition? Click to see how Oak Ridge National Laboratory did it.

Posted in Skype for Business

December 13th, 2019 by UC Now Skype/Teams News Feed
By Ryan Daily
A look at the latest news coming out of the SD-WAN market and from Microsoft, LogMeIn, Logitech, and Observe.AI.

Posted in Skype for Business

December 13th, 2019 by Author

Its was announced a while back that Microsoft will be switching off Skype for Business Online in July 2021, which gives their customers time to look at the options for migrating to Microsoft Teams. In my own organization my approach was “Microsoft Teams Roadshow” where I demonstrated to the back office staff the power of Microsoft Teams then moved them to Teams Only. At Microsoft Ignite 2019 it has been announced of 2 new modes which Teams Administrators can implement within their businesses.

Adoption is the biggest challenge for any organization, so let’s look at the options available.

Skype for Business with Teams Collaboration

This allows users to still use Skype for Business for chats, calls and schedule meeting but they can use Teams for group collaboration.

Skype for Business with Teams collaboration and meetings

This allows users to still use Skype for Business for chats and calls but all meetings and group collaboration are undertaken within Teams.

Islands Mode

This allows users to use both Skype for Business and Teams features if you want to adopt usage in this approach.

Regards
The Author – Blogabout.Cloud

Posted in Skype for Business

December 13th, 2019 by Randy Chapman
Hello Readers, I hope you’re well. Super quick post about a new feature in Microsoft Teams that has been super popular judging by the popularity of a Tweet I posted yesterday. Oooh! Live Captions in #MicrosoftTeams meetings has landed 👍👍😉 pic.twitter.com/K7rGdFpr4L — Randy Chapman (@randychapman) December 12, 2019 Microsoft Teams now has live captioning in […]

Posted in Skype for Business

December 13th, 2019 by Randy Chapman
Hello Readers, I hope you’re well. Super quick post about a new feature in Microsoft Teams that has been super popular judging by the popularity of a Tweet I posted yesterday. Oooh! Live Captions in #MicrosoftTeams meetings has landed 👍👍😉 pic.twitter.com/K7rGdFpr4L — Randy Chapman (@randychapman) December 12, 2019 Microsoft Teams now has live captioning in […]

Posted in Skype for Business

December 13th, 2019 by Author

In recent times I have started to become a bit of an “expert, well I will use that word loosely” for Windows 10. Hybrid Azure AD Join is becoming a very popular option for a lot of the clients that I am currently working with and pops up all the time in discussions about “Modern Management” of Windows 10. I have experienced a few highs and lows when implementing Hybrid Azure AD Join and want to share that knowledge I have gain over the past 6 months.

What is Hybrid Azure AD Join?

Hybrid Azure AD Join is where your Windows 10 device is connected to your local Active Directory Domain and synchronized using Azure Active Directory Connect (AADC) to Azure AD.

Why would you do this?

This enables you to manage your Windows 10 devices from Microsoft Intune and leverage the offers from the cloud. Most organizations today have the required Microsoft subscriptions to implement Microsoft Intune but are unaware of how to start their journey.

What do I need for Hybrid Azure AD Join in a Managed Domain?

  • Azure Active Directory Connect version 1.1.819 or greater
  • Devices must be able to connect to the following URLs
    • https://enterpriseregisteration.windows.net
    • https://login.microsoftonline.com
    • https://device.login.microsoftonline.com
    • https://autologon.microsoftazuread-sso.com
  • All Computer Objects from your on-premises Active Directory must be within the sync scope
  • Service Connection point (SCP) is created for device registration (Completed via running AADC)

Implementing Hybrid Join for your organization

We are now going to run through the steps required to gear up your environment for Hybrid Join, first of all we are going to create the SCP using AADC. When you launch AADC you see “Configure device options”, select this option and proceed

Configure device options

In this section you will receive the following Overview of what can be configured and in this case, we are looking at Hybrid Azure AD Join only.

Hybrid Azure AD Join enables devices in your Active Directory forest to register with Azure AD for access management. Computers in your organization will automatically discover Azure AD using a service connection point (SCP) object that is created in your Active Directory Forest.

Device writeback is a prerequisite for enabling on-premises conditional access using AD FS and Windows Hello for Business. Device writeback synchronizes all devices registered in Azure AD back to on-premises. The device are synchronized to a device container that is created in your Active Directory forest.

Important Note

Device writeback requires the Active Directory Schema version to be Windows 2012 R2 (level 69) or higher
Connect to Azure AD
Configure Hybrid Azure AD Join and proceed
Tick “Windows 10 or later domain-joined devices.” It is worth remembering that your Windows 10 devices need to be synchronized and Proceed
Tick your Forest
Select Azure Active Directory
Click Add
Enter your Enterprise Admin Credentials
Proceed
Configure and this completes this task

You can confirm that the SCP has been created by launching ADSI Edit and browse to the location displayed below.

Now we have configured Active Directory we need to create a new GPO that configures the Windows 10 device to AutoEnroll into Azure AD. First of all we need the correct GPO templates installed in your SYSVOL, these templates can be download by the below URL.

https://docs.microsoft.com/en-us/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy#configure-the-auto-enrollment-for-a-group-of-devices

Once you have installed the required GPOs to your primary domain controller you’ll be able to “Enable automatic MBM enrollment using default Azure AD”

Computer Configuration –> Policies –> Administrative Templates –> Windows Components –> MDM
Enable Policy and select Device Credential, User Credential is a legacy option but its recommended to use Device.

Once this policy enabled and linked to the OU where your computers are located, they will become Hybrid Azure AD Joined.

Gotchas !!!

This Microsoft link is your friend if you encounter any issues with Windows Enrollment Errors
https://docs.microsoft.com/en-us/intune/enrollment/troubleshoot-windows-enrollment-errors

You can also follow the official Microsoft documentation
https://docs.microsoft.com/en-us/azure/active-directory/devices/hybrid-azuread-join-managed-domains

Regards
The Author – Blogabout.Cloud

Posted in Skype for Business

December 13th, 2019 by Shelly Bhardwaj

In Exchange 2010 we have the facility to export to PST directly from the Exchange server without further interventions unlike its predecessor where in Exchange 2007 you needed to setup another computer with a 32 bit Office installation. Also we don’t need the burden of the ExMerge as with Exchange 2010 it introduced the New-MailboxExportRequest PowerShell cmdlet that we can use to export the PST files at our pleasure.

Unfortunately, for us there is no functionality in the GUI of the Exchange Management and command line is your only choice to export to PST a mailbox or a set of mailboxes. First things first, although you have Exchange 2010 this does not make you able to export mailboxes using the command. For this to work you must have your Exchange 2010 running SP1 or later.

We need to check if the username you are exporting the PST files with, has the right permissions. On the folder you must have the username you are exporting with as full control along with the Exchange Trusted Subsystem.

Open the Exchange Management Shell and type the below to give your user the right permissions.

New-ManagementRoleAssignment –Role “Mailbox Import Export” –User “YourUsername”

To export mailboxes, you cannot use a direct drive like D:PSTFiles, you will need to have a share. For the share you will need to give full permissions to the user you are exporting with. An example would be \srv01d$PstFiles.

After this we can now start exporting the mailboxes.

The simple command to export the whole mailbox of a user is below

New-MailboxExportRequest –Mailbox “SourceMailbox” –FilePath “Destination”

This will star the export process of the mailbox. If you have an archive mailbox to export you will need to add the –IsArchive at the end.

If you have some old mailboxes which were disconnected, the command remains the same but you cannot directly export a disconnected mailbox. You would need to create a new user in your Active Directory and then you would need to connect the disconnected mailbox to that user. After this you can use the New-MailboxExportRequest.

Exporting a mailbox has some extra options like the IncludeFolder, ExlcudeFolder and export time period. These can come in handy when you are exporting by year or preparing to export a mailbox for Office 365 migration and you don’t want to export the Deleted Items or the SPAM folder for example or you will only need to export the Inbox folder. Here are some examples on how to export the mailboxes with these options.

New-MailboxExportRequest –Mailbox JamesSmith –FilePath \srv01d$PSTFilesJamesSmith.pst -IncludeFolder “#Inbox#”

The above command will export the mailbox of JamesSmith but will only export the folder Inbox.

New-MailboxExportRequest –Mailbox JamesSmith –FilePath \srv01d$PSTFilesJamesSmith.pst -ExcludeFolder “#DeletedItems#”

The above will export the whole mailbox of James Smith but will exclude the folder called DeletedItems. If you have wanted to export the whole mailbox apart from more than one folder you would need to add multiple folders using the comma as a separator. This part is also applicable to both include and exclude. An example is below.

New-MailboxExportRequest –Mailbox JamesSmith –FilePath \srv01d$PSTFilesJamesSmith.pst -ExcludeFolder “#DeletedItems#”, “#Spam#”

Another option as said is the export by date range. This comes with command of lt which means less than and gt which means greater than. If you wish to export all the mailbox of a user till 2017 you would need to set the command as below.

New-MailboxExportRequest –Mailbox JamesSmith –FilePath \srv01d$PSTFilesJamesSmith.pst -Content Filter {(Received –lt ‘01/01/2018’)}

If you wish to export all the mailbox of a user from 2017 onwards, you would need to set the command as below.

New-MailboxExportRequest –Mailbox JamesSmith –FilePath \srv01d$PSTFilesJamesSmith.pst -Content Filter {(Received –gt ‘01/01/2018’)}

If you wish to export all the mailbox of a user from 2016 till 2017 only, you would need to set the command as below.

New-MailboxExportRequest –Mailbox JamesSmith –FilePath \srv01d$PSTFilesJamesSmith.pst -Content Filter {(Received –gt ‘12/31/2015’) (Received –lt ‘01/01/2018’)}

To view the status of the export one can use the Get-MailboxExportRequest cmdlet.

Thou this is not so informative at least you will know if it complete, in progress or failed. To get just a little bit of information on the mailbox you are exporting you can use the below command where the name is the name of the mailbox export job you are executing. This can be found by looking at the Get-MailboxExportRequest results.

Get-MailboxExportRequest –Name MailboxExport | fl

There is a way also to get the percentage of the whole export for a particular mailbox. The command is the Get-MailboxExportRequestStatistics and it will give you where the mailbox is right at that moment.

Get-MaibloxExportRequest | Get-MailboxExporRequestStatistics

When exporting a lot of mailboxes you will notice that the completed and failed are not automatically cleared from the list and you would need to do this through PowerShell by typing the following command for each status.

Get-MailboxExportRequest | where {$status –eq “Completed”} | Remove- MailboxExportRequest

Of course to clear the ones that are marked as failed you would need to change the status on the command from Completed to Failed.

On top of this there are some disadvantages, which are human error as it’s easy to make a mistake especially when making various folder exclusions and date ranges. The fact that you can only export using the PowerShell command line and the margin of error is big. Alternatively, Stellar Converter for EDB can export mailboxes with no issues and that the administration effort was minimal. Apart from that, the application is a great tool to import directly from an EDB file to Office 365.

 

 

Photo by Charlize Birdsinger on Unsplash

The post PowerShell Commands to export Exchange 2010 mailbox to PST appeared first on MSB365.

Posted in Skype for Business