User Profile
anneoday
Iron Contributor
Joined 9 years ago
User Widgets
Recent Discussions
Re: "Accidental" email archiving during typo correction
gszatmari This has been driving me nuts! I knew I kept getting emails going to archive but wasn't able to figure out what the trigger was until today. When I finally figured it out, I came in here to see if others had noticed it too. Thank you for posting! I do have a small workaround to avoid it, but not a fix to stop it for good (cough code release cough). The problem only happens when you're working from a reply (or forward) that is within the frame of the Outlook app, and doesn't happen on a version of the same message that has been popped out to a new window. So for an individual message where you want to make sure to avoid it, use the pop out to new window button then compose the message. And for the person who's annoyed by this frequently, they may want to set their application default to always pop out on compose and reply. I notice that the popped out window also is a little friendlier on that point of where it's suggesting the solution. It still doesn't want you to just start typing over or backspacing or deleting the word, but it seems to respond a little better if you do a double-click on the word, that hover card disappears a little faster and you can start working on the change you want to make.Re: Migrated videos still in Stream (Classic)
As far as I'm aware, the issues with the Migration tool were resolved, yes. Some things to look into ... You're saying that those 10 remaining visible were definitely migrated, right? Because if you had a filter set to migrate only certain videos based on criteria like number of views or published after a certain date, then maybe those 10 remaining visible were in fact not migrated because they were filtered out. (That is normal behavior, for the channel to display what was not migrated.) Check your inventory report to make sure that those 10 visible weren't perhaps ones that were ineligible for migration, or duplicated videos. In the Msoft documentation, they give a detailed description of an order of operations on a single video to determine where it ends up. So you can have what looks like a Companywide or Group Channel that displays 20 videos, but 10 of them were uploaded by someone to their own personal channel first, and they shared it into the group channel. Those 10 would go to that person's OneDrive whenever you migrate their personal channel, but they are still going to show up in the Companywide\Group channel until you have migrated their personal channel. Then it gets extra confusing if the end-user did an upload twice ... same video can APPEAR in two places but only stored in one (described above). But also, they could have simply uploaded the video twice so that it is DUPLICATED and stored in two places. Running a full inventory report after your migration might help you figure out what's going on. IsEligibleForMigration will tell you if any of those 10 were not eligible for reasons like not published, error state, or deleted. MigratedDestination will tell you line by line what video migrated where. See if the 10 you're looking at have values in this column. ContainerVideosInClassicUI will tell you how many videos were appearing to the end-users when they viewed the channel. For your described probablem, it may say 270, but if you filter the report for that particular container, your filter may only give you 260. If none of that helps and it does seem like your mysterious 10 videos should have been migrated, were in fact migrated, and have not been hidden from Stream (Classic), then you should probably open a ticket for support. April 15 is approaching fast for everyone!Re: Videos (1613) are marked as Ineligible for migration.
Shivaprasad Pendyala I'm going to reply to your queries in reverse order. Query 2: It would be great if we have a script to pull in information The "Inventory Report" is available to assist with this. It has almost everything you asked for. In summary, you'll go to Stream (Classic) with Stream Admin role or SharePoint Admin role, go to the Stream Admin page, reports section, and download the script. After downloading, you'll still need to set up a "token" text file that you populate with data gathered from your browser's Developer Tools pages. This inventory report will generate multiple CSV files that can be concatenated into a single report, giving you an idea of what videos you have to work with. In the article below, it doesn't mention a new column available in the report, "IsEligibleForMigration" so you can zero in quickly on videos that are or are not eligible. https://learn.microsoft.com/en-us/stream/streamnew/migration-details#stream-classic-video-report Thus, videos that are ineligible for migration are: Videos that aren't published or in draft, meaning the only person that can see it, is the original uploader. Admins should ask these users to publish their video, so that they're picked by the tool for migration. Videos that are in processing or upload error state and thus aren't able to be played. They can never be migrated. Videos that are deleted by the user and are in the recycle bin Query 1: Why we are able to see the stream videos are ineligible for migration. Until Stream (Classic) is completely disabled in your environment, video owners will still be able to make changes to existing data, such as publishing videos previously uploaded (uploading should now be disabled), or deleting videos. Thus, that value in "IsEligibleForMigration" may change for individual rows based on activities of the video owners. Also note that recycle bins may be emptied, and deleted videos do purge by age, so the rows in your inventory report may shrink over time.Re: Old EEEU not working and transition from Classic to SP
Jennifer Loudiana Going out on a limb here, but I think they introduced a problem when they tried to fix the fact that the folders were previously getting stamped with "last modified by" information that was incorrect. Now folders are getting stamped with last modified by "stream migration admin," and every time you touch the destination folder with the Migration tool, it's going to alter permission on that folder again. In our case, we were migrating multiple Companywide Channels to a single site collection, single "Stream Migrated Videos" folder. My fix was to go into advanced settings on this folder, seeing the classic SharePoint permissions interface, and do a "Grant Permission" step. In that dialog box, there's a check available for "Share everything in folder, including items with unique permissions." In this process, I granted permission to the site's Visitors group which included EEUE. I was unable to figure out how to do this in the modern permissions interface, and I also had trouble in the modern permissions dialog with choosing the site collection's built-in security groups (owners, members, visitors) because it wants to use M365 groups published in the GAL. But the local site collection security groups are easier find and use in classic dialog box.Re: Insert Stream (SharePoint) Link in PowerPoint
charleneevans That function you're after should be fixed ... sort of! If you'll store your presentation on SharePoint or OneDrive, then use the web version of the PowerPoint application to edit it, you should find that the "insert video" feature from the Web app offers more options including SharePoint and OneDrive. I've been able to test successfully with links to videos stored in SharePoint and OneDrive. If you don't want to keep your PowerPoint presentation stored in the cloud after you made this change, then you should be able to download it and the video will still work. It will just ask if it's OK to open the video in your browser (as it would if it were a Youtube video or other web based source). I believe the PowerPoint desktop app was planned for this same update, but that you might need to update what you have installed on your workstation if you aren't seeing this fix yet. Sorry I don't have the PowerPoint app versions handy to tell you what release has this fix in it.Re: Public group migration
It appears this has been identified as an issue under investigation with an estimated fix of November 15, 2023. At least that's what this sounds like to me. https://learn.microsoft.com/en-us/stream/streamnew/migration-tool-release-logs EEEU Permissions are not applied to videos associated with public M365 groups | *Fix estimate: November 15, 2023: Microsoft 365 groups created on Stream (Classic) with Privacy settings set to Public can be viewed by everyone in the organization. When these groups are migrated to Stream (on SharePoint), EEEU permissions are currently not applied due to which users who aren't a part of the destination SP site can't view those videos. This affects all videos associated with public Microsoft 365 Groups but migrated as part of other containers as well. We're working to fix this issue, post which, all migrated videos associated with public Microsoft 365 sites would have EEEU permissions.Re: Public group migration
JWiersem1925 FYI I was just able to confirm that we are seeing the same problem. Will raise a support ticket. Thank you for posting this here, because knowing that it could be an issue saved me a ton of time with troubleshooting or worse yet not realizing it was a problem and going ahead with migration.Re: DestinationMapping Report, Script, and Upload
Updating my post with my own findings from trial and error. Oh, hey, the documentation changed. Previously it said "If your SharePoint has more than 50-K sites, Microsoft 365 group autodestination mapping may not work perfectly." That number has changed to 100-K sites as of 9/25/2023. After getting the Destination Mapping template downloaded, the Microsoft Documentation seems to suggest that you have to run StreamClassicVideoReportGenerator_V1.11.ps1 with some parameters to create a new file with destination paths filled in. As near as I can tell, the only purpose of this step is for mapping M365Group containers that show up as NULL in the MigrationDestinations.csv. It will proceed to "automap" those NULL values to the respective SharePoint sites for those M365 Groups. I don't think it's going to help you in cases where the M365 Group has already been deleted, the M365 Group exists but has no SharePoint site, or where you want to map any container to a site different from the site suggested by the Migration tool. But as I said, I wasn't able to get the script to work, so I'm kind of guessing about what it's supposed to do. From there, I tried doing some manual filling in of Destination Paths to the CSV file for some M365 Group Containers and Companywide Channel containers. Generally it seemed to work well. It did not like one site that had double quotations in the container's name. It does seem to me that this whole process is a bit limited by the fact that you have to move your containers to the Migrations tab just in order to be able to set destinations. I was hoping to set all my destinations now and migrate in waves later. I guess I can still do that, but I was hoping to only move things to the Migrations tab when I was actually ready to migrate them. If you really need help with mapping your M365 Groups, I'd suggest you or someone who is an Exchange admin run the Get-UnifiedGroup command so you can find the appropriate group by PrimarySMTPAddress (as indicated in the Stream Inventory Report on the "ContainerEmailId" column) and locate its SharePointSiteURL to put into the MigrationDestinations.csv for the Destination Path column. Here's a sample of the command. Get-UnifiedGroup -Resultsize Unlimited | Select Name, DisplayName, PrimarySmtpAddress, SharePointSiteUrl | Export-CSV AllUnifiedGroups.csv -NoTypeInformation (other properties you might find helpful: Guid, GroupMemberCount, WhenCreatedUTC, ManagedBy) Tip: if you haven't tried the "tagging" function of the SharePoint Stream Migration Tool yet, it works really well! It gives a nice visual on the tags and helps be able to filter your containers whether you're working from the Scans tab or the Migrations tab. https://learn.microsoft.com/en-us/stream/streamnew/understand-the-tool#tags https://learn.microsoft.com/en-us/sharepointmigration/mm-tagging Tip: In my work with the Stream Migration, I've now run into issues with one Container that had a Pipe symbol in its name, and another with double quotes in its name. So if you're just getting started on all this, you might want to review all your Container names for things like that and consider changing them to eliminate headaches later, or be prepared to carefully scrutinize any import or export files you may use. Here's my summary rewrite on how to work with the Destination Mapping. To Download the Destination Mapping Template: -Launch the Stream Migration Tool from Admin Center (Admin Center > Setup > Migrations > Mirosoft Stream) -Select some containers you want to work with and scan them -Once Scans are complete for each container, select them again and "Add to Migrations" -Click the Migrations tab -Once on the Migrations tab, click the "Upload Destinations" button -On the popup\dialog box for Destination uploading, there's a link for "MigrationDestinations (.CSV)" -Click that link, to download a CSV file that will list only the containers you've loaded into the Migrations Tab -That MigrationDestinations.csv file has the following headers: Name (for reference only), Source Path (for reference only), Destination Path, Migration status (for reference only), Created on (for reference only), Task ID To edit the Destination Mapping File -Open in Excel or text editor and make changes to the Destination Path column only. To upload a Destination Mapping File after editing: -From the Migrations tab, click the "Upload Destinations" button -On the popup\dialog box for Destination uploading, Specify the CSV file containing the altered Destination PathsDestinationMapping Report, Script, and Upload
We have a tenant with more than 50K SharePoint sites. According to the documentation, we should plan to upload Migration Destinations because automapping may not work correctly. I've been trying to get the "MigrationDestinations" script to work and so far have had no success. When I download the sample, it's only downloading the list of containers presently showing on the Migrations tab. When I run the script, it seems to only want to look for M365Group containers with Null values. So first I had to find an M365 Group that had no destination path set already, load that into the Migrations tab just in order to try testing out the script. Once I ran the script, it didn't seem to want to run until I was willing to do a full inventory report first. OK fine, got that done. Then I ran the command with the " -CreateDestinationPathMappingForM365GroupContainers true -MigrationDestinationCsvFilePath" bits again, and it gave me an empty file with header. I don't know if it's having an issue with Exchange or not ... I'm guessing it's just doing a Get-UnifiedGroup command which I can do, so I don't think it's an issue with not-enough-permissions. So as a test, I then took my empty output file and added one line to populate one destination for one M365 group that previously had no destination set, and that seemed to work. Just for grins and giggles, I put an email address in there of the person's OneDrive where I want that M365 Group content to go, and it seemed to take that. Could anyone here confirm for me the following assumptions: 1) The only purpose of this script is to fill in MISSING destinations .... as long as we have destinations already filled in or are able to set them in the GUI, then there is not some other requirement that says we have to run the script. 2) This script is only intended to map M365Groups to their respective SharePoint sites, it does not allow for deviations from that. 3) If I choose to manually build a CSV with Destination Paths and use the Upload Destinations feature, that should work. Reference: https://learn.microsoft.com/en-us/stream/streamnew/migration-details#destination-mapping-report Thanks!Re: Videos in Stream Classic Channels not showing up in Migration tool
Jennifer Loudiana Did that end up working for you? I'm taking a fresh look at documentation today and forgot all about the "49.9K containers" problem. We are nowhere near that size, so it's not an issue for me. https://learn.microsoft.com/en-us/stream/streamnew/migration-process Nuances for large customers: If your Stream (Classic) has more than 49.9-K containers, you would need to, either manually add containers or delete migrated containers and then you'll be able to discover more. UI has a limit of 49.5-K containers, with a 0.5-K buffer to add containers manually. https://learn.microsoft.com/en-us/stream/streamnew/step-by-step-guide#migrating-nuance-for-large-customersRe: Stream Icon in App Launcher Still Launches Stream (classic) After Enabling Read-Only in Classic
Wade_Besack I think you may need to make a change on the app launcher. In M365 Admin Center, navigate to the settings, then Stream, which has just one option, to set the App Launcher Tile. It offers "Automatically switch," "Stream (on SharePoint)," and "Stream (Classic)."Re: Stream Classic inventory report - how does the report determine container name for orphaned videos?
I'm sorry I don't know the "logic" behind the distribution of orphans into their respective containers, but am seeing a similar kind of distribution where there's about 100-300 videos per container, then a couple are over that. In our organization, most of this orphaned content is coming from people who have left the organization, or from M365 groups where the group was deleted. For the first scenario, there's really no one left to speak to the need for the contents, and we don't have the bandwidth to go chasing down managers of every termed worker who may have ever uploaded a video to classic. For the second scenario, it's possible to figure out what group it was connected to by way of the "Owners" column which offers an email address for the M365 group it was posted into. But since we're talking about people who left the company, and about groups that have been deleted, it's our plan to put all the Orphaned content into site collection(s) that are restricted to admins only. If someone is looking for content, we can find it for them and move it to a destination they want. That approach may not work for everybody, but we are figuring the important thing is to "rescue" the data out of classic before it goes away. Getting it migrated to anywhere on SharePoint accomplishes that, and getting content claimed and distributed is secondary.
