#This remove script is used for repositories containing users Email If the user has email existing on the repository, you will use the following section: $user = Get-VBOEntityData -Type User -Repository $repository -Name Email #Fill in "REPOSITORY" with the name of the repository as it is showing in Veeam Backup for Office 365 and the email address of the user you wish to remove the data for = Get-VBORepository -Name "REPOSITORY" #This script will show you what a data a user has on a particular repository $User1 = Get-VBOLicensedUser -Organization $org -Name you are not sure what data a user has on a repository, you can use the following: "" and the users email address = Get-VBOOrganization -Name "" #Fill in the domain name as it is shown in Veeam Office 365 #This will show that the user is licensed This next step will show you the user that is licensed and can be used later to see that the user is no longer licensed in the software: Something in the variable line is incorrect. If the variable does not return a result, then This will automatically load the required toolkit to run these commands.Ĭommand containing variables does not return a result, check your variables to
To start the process, you will need to open PowerShell from Veeam Backup for Microsoft Office 365. User will be marked as white space and will be written over on the following That this will not shrink the size of the database. Before we start deleting data, I would like to point out
Once you have queried the user by the right identifying attribute, you can then delete all data that the user Getting startedīe used in any combination if that component is present on the repository for I spent many hours with trial and error to figure out the right combinations and wrote this to save you the same headache. So, if the user’s email is sent to one repository and OneDrive sent to another, the script you would need to use to delete this data is different for each repository. The configuration database saves users’ identifying information per repository, based on the component that was backed up to that repository.
Seems simple enough, right? I found out very quickly that this could get complicated really quickly, especially when you have your users separated by components (like OneDrive and email) stored on different repositories. Otherwise, you have to wait the 31-day threshold for the license to be reallocated. This can be REALLY useful if you accidently backed up a user and no longer need to keep the data. In order to remove a license from a user, you first need to delete that user’s data from all configured repositories and run the remove license command with PowerShell. Here is a hot topic for Veeam Backup for Microsoft Office 365 users: how to reallocate a license to a user without waiting 31 days.
0 kommentar(er)
