Microsoft confirmed with an update to the original Office 365 notification (MC208577) that they will allow Teams users to upload their own custom background images in May 2020. However, if you can’t wait, you can upload your own images today.
On the PC you are using, go to; %AppData%\Microsoft\Teams\Backgrounds\Uploads folder and you should be able to select those images for a meeting background.
Upload custom image for Microsoft Teams
I have uploaded large high-fidelity JPEG photos to this folder and been able to use them as a background, but it seems like resizing the background to 1 MB or thereabouts is a good idea. Apart from deleting the image file from the folder, there’s no way to remove it from a PC after it’s uploaded. If you use Teams on several devices, you’ll also find that images don’t roam across devices. You must upload and maintain images on each device.
On Macs, the images should be copied to: /users/<username>/Library/Application Support/Microsoft/Teams/Backgrounds/Uploads
Easy and straight forward … here is a screen of where to do that… yes notice you choose from these choices … having custom picture from your own computer or whatsoever is not yet…. but as of now here we have some professional and fun background pictures 🙂
The date is: 13 of October 2020 .. so a year from now I’d say.
Please check Microsoft Product Cycle from this link, Here
And you can search for whatever Microsoft Products to see the end supported date.
Note that If you still have SharePoint 2010 Farm, start planning for Migration and honestly speaking just go to SharePoint 2019. and use the new Modern Experience; in which I will write about in a new post.
Unfortunately no direct migration, you still have to go to SP2013 then 2016 and finally 2019.
You will see Servers for each farm, you can use Azure VMs temp for migration that will help you to reduce Servers cost unless you have the resources on-premises.
We use Backup Content DB using SQL back up most likely for Migrations Option, meaning you are migrating from SharePoint 2016 to SharePoint 2019.
in that case, to migrate we use the command Mount-SPContentDatabase
So most likely this is used for migrations.
But if you use the Backup-SPSite option using PowerShell, then you may be moving your site collection in the same Farm from one web application to another and you can definitely move it from one Farm to another but within the same SharePoint Version, so this is not migration.
So the what do you want to do is …. what you will use..
Join the webinar by Datapolis and Mai Omar Desouki.
Everyone needs a time off! However in the summer season there can be a hassle to get your holidays approved. You send a request to your manager and do not know what happens next. Managers also have tough days because they often do not have full view on who’s on vacation and if they have enough people working. How to solve that?
Agenda In this webinar by Mai Omar Desouki, Senior SharePoint Consultant at Vodafone Egypt and founder of Dubai SharePoint User Group we will show you how make an easy and efficient holiday approval workflow that is a must-have for every company. We will use SharePoint Designer to build a workflow that keeps employees in loop, gives insights to managers and validates users’ balance of their free days- so that everyone could enjoy their holiday! We will work on on-prem SharePoint 2013 as a development environment and then we will deploy the workflow online.
Kindly, we have some wish list, we wish it would be available in SharePoint 2016, at least some of it..
Apps; when we insert apps as App Part, its basically inserted in iFrame! We really need a better way.
MS, I hope you could include the Office Web App Server in SharePoint Server just like you did in FAST Search Server.
We need a UI for Tenancy configuration,
We need a UI for Property Bags in Central Administration, it’s actually painful in PS.
I don’t know why the Search Topology was removed in SP 2013, it was available with UI in SP 2010, I’d recommend we have a UI for Search Topology. Although I know there is PS to do so but there was already a UI. I understand the Search Topology changed heavily, which requires more work in its UI.
Some stuff to complete its configuration, we have to write PS, I am okay, I love PS but why not have a UI for it; these are:
The Workflow Manager – Register-SPWorkflowService.
The Apps subscription required service application to be running although in UI; it doesn’t exists.
The Restore-SPSite has no UI, although the Backup-SPSite has a UI.
The Import-SPWeb has no UI, although the Export-SPWeb has a UI.
The Translation Service Application, everyone saw it, we thought initially, no code needed but in order to use it, we have to write some code, why not make it easier.
Device Channels, and adding the user agent, If just the user updated or upgrade his/her device, he lost the master page we did for his/her agent, it’s a very static thing and not dynamic at all; why not add screen margins instead or plus the user agent to change his/her master page based on the dimensions, I know this can be done from JS or CSS, but we have already a UI, Device Channels where we add the user agent, I hope we can add as well the screen dimensions; iPad, iPhone, Android, Tables/Phone.. and so on.
We really need to have a field type “Multiple Browse/Upload”; a field where user can upload multiple images/docs from wherever, what we have now, is a site column where we can browse but max is one file; although this exists only in site columns and not when creating column in lists/libraries, to me is fine but to End User, he hates me when I show him how J .. lots of steps.
We need a way to restrict sandbox on one web application and not on the other one on the same server! We did another server just to stop the Sandbox Solutions on one web application; even the Resource Points effects all web applications, we may need to make each web application with different Sandbox Resource Points. I know it is deprecated so no more enhancement here but just saying my wish list.
This is what I can think of right now, I may add to this list more later.