SelfeServe License Request Administation
Hello Microsoft Community! In our Org , using the powershell module MSCommerce, we have already set the AllowSelfServicePurchase policy to Disabled for all products as we do not want our Members to purchase licenses or sign up for trials on their own. This has not stopped our Members from making requests for licenses. We'd like to have our Members utilize our established process for requesting licenses vs using SelfServe. Is it possible to stop this altogether vs only being able to disable the purchasing function? Here is an example of our policy status and the weekly digest email we just received.
Unable to Remove-SPOUser from personal sharepoints properly
Hello, I had to add a global administrator account literally on every single personal sharepoint, asSite Collection Administrators, to delete a user from each personal sharepoint, with a certain email but associated with a old sharepoint ID (the user was re-added to our Office 365 and he had issues when other were sharing links from personal sharepoint to him, access denied even with the right email, because he have now other sharepoint ID). Now I want to remove thatglobal administrator account from every personal sharepoint (using: Remove-SPOUser) , using a global administrator account A to remove the global administrator account B that I've added everywhere (Account B was added with Account A login with: Set-SPOUser)(otherwise will get: Remove-SPOUser : A user may not remove his or her own account from a site collection.), but cannot do that because, seems like I need to use an account that is already a Site Collection Administrator, to perform this action, so I am unable to leave just the Primary Site Collection Administrator (the own user). Over web sharepoint admin center, I can remove and add everyone using Account A, even remove Account A fromSite Collection Administrators, it simply doesn't work in the same way when connected overConnect-SPOService. Please advise how can I remove thatAccount B, and leave only thePrimary Site Collection Administrator asSite Collection Administrator?
Loop parameters missing after PowerShell update
I'm trying to give a few users access to the new Loop collaboration platform and I'm getting stuck trying to update SharePoint parameters so that file sharing can be enabled in Teams and SharePoint. I have updated to the most recent version of the Management Shell for SharePoint Online. When I run the command Get-SPOTenant, I don't see the IsLoopEnabled or IsWBFluidEnabled parameters. Our SharePoint Online version is 16.0.0.23508 Any suggestions would be appreciated.Exchange Online help with powershell
So long story short. We have 9 domains in our org and when people transfer from department to department we are required to disable their old account and create a new one or sometimes we have contractors that become FTE's. Most of the time the department allows them to take their mail but because it's a new account I have to migrate the mailbox in the recycle bin to the new one under the new account. I have scripted this process and everything is working except when I try to catch and use the Exchange GUID in a variable. After I grab it, I do a Write-Host and it prints just fine but when it gets to New-MailboxRestoreRequest to use the GUID, I get the following: I can copy and paste the output of the Write-Host in place of the variables and it works. I just don't want to have to do that every time. Here is the script with identifying information stripped. Thanks in advance for the help. #Connections Connect-ExchangeOnline $Session = New-PSSession –ConfigurationName Microsoft.Exchange –ConnectionUri http://exchangeServer/PowerShell/ -authentication Kerberos Import-PSSession $Session -disablenamechecking set-adserversettings -viewentireforest $true #Set your variables $upn='Jane.Doe' $oldDomain='thisdomain.com' $newDomain='thatdomain.com' #Get Old and New GUIDS $oldEmailGUID=get-exomailbox -SoftDeletedMailbox -UserPrincipalName $upn'@'$oldDomain -PropertySets all | select name,primarysmtpaddress,exchangeguid,legacy*,whencreated,whenchanged Write-Host $oldEmailGUID.ExchangeGuid $oldEmailGUID=$oldEmailGUID.ExchangeGuid $newEmailGUID=get-exomailbox -UserPrincipalName $upn'@'$newDomain -PropertySets all | select name,primarysmtpaddress,exchangeguid,legacy*,whencreated,whenchanged Write-Host $newEmailGUID.ExchangeGuid $newEmailGUID=$newEmailGUID.ExchangeGuid Start-Sleep -Seconds 5 #Copy Old mailbox to New Mailbox New-MailboxRestoreRequest -Name $upn -SourceMailbox $oldEmailGUID -TargetMailbox $newEmailGUID -AllowLegacyDNMismatch -CompletedRequestAgeLimit 7 -ConflictResolutionOption keepall –LargeItemLimit 5 #-BadItemLimit 2000 Start-Sleep -Seconds 5 #Add X500 forwarding address **must first remove from old account through AD #Get Old x500 $oldEmailX500=Get-exomailbox -SoftDeletedMailbox -UserPrincipalName $upn'@'$oldDomain -PropertySets all | select name,primarysmtpaddress,exchangeguid,legacy*,whencreated,whenchanged Write-Host $oldEmailX500.LegacyExchangeDN $fullX500ValueCheck='@{Add = X500:'+$oldEmailX500.LegacyExchangeDN+'}' Write-Host $fullX500ValueCheck #Add X500 forwarding address **must first remove from old account through AD Set-remoteMailbox -Identity $upn'@'$newDomain -EmailAddresses @{Add = 'X500:'+$oldEmailX500.LegacyExchangeDN} -verbose ##### Show Restore Status #### #get restore guid $mailboxRestoreRequestStatsGUID=Get-MailboxRestoreRequest -Name $upn Write-host $mailboxRestoreRequestStatsGUID.RequestGuid #Check Status **update guid from previous step Get-MailboxRestoreRequestStatistics -Identity $mailboxRestoreRequestStatsGUID.RequestGuid | select targetmailboxidentity,status,statusdetail,failuretype,message,estimatedtransfersize,bytestransferred,EstimatedTransferItemCount,itemstransferred,percentcomplete,*stalled*,overallduration
Powershell Script to Generate eDiscovery Case
Hello Everyone, Currently working on a series of scripts that I will be using to administrate Office365 regularly for my clients, including one to generate the eDiscovery search and export. In my script I found that the param -OneDriveLocation for New-ComplianceSearch comes up as an invalid parameter. The whole premise behind this is to automate the user decommissioning process as much as possible, even if the last step is to log into the compliance center and download the clickonce application to export the zipped up export, we can easily save 30~60 minutes per user decommissioning we have to run, with an average of 3 a day it allows my techs on our service desk to work on other tickets during that time frame.
