This message was deleted.
# microsoft-fslogix
s
This message was deleted.
n
When I did it, I honestly just let them create a brand new OST file. DIdn't feel it was worth trying to migrate a file that contained just 3 months of cached data.
j
Yeah it's all just cache. Let it recreate one time
r
nods
No issues with the Outlook profile "just working" after the migration?
n
None in that environment. If anything, it'd fix OST issues, haha.
since the fix was always to kill that file and let Outlook recreate it.
My alternative plan - should letting them recreate it not be approved - was to use WEM to copy the data to a directory in the profile container pre-change, then use WEM to copy it back to the normal directory post-change.
r
this environment isn't a lot of users, but thinking about this moving forward for environments that DO have a lot of users
n
I only tested that on my account, but it seemed to work fine.
Yeah, I went with Profile and ODST containers originally, thinking that I could just delete the ODST should they have issues. Then it seemed like a waste managing both, so I created a start menu shortcut for users to self-service their own issues in Outlook (PS script).
I empowered them to fix their own shit, not that most of them ever did it without instruction.
It was fun writing a job aid that said 'click on 'Fix Outlook. You're done'
r
yeah, that's a challenge here
n
At least if you have that shortcut, if you get a ticket you can instruct them to click on it and be done with it.
r
yeah
n
For good posture, here's the script I had for that shortcut.
I had one for Outlook, Teams, BlueJeans, Webex, and WEM.
r
Ah, this is awesome, dude, thanks!
πŸ‘ 1
j
Yep just recreate. It’s just cache.
r
yeah, just tested, seems to be seamless enough. Thanks guys!
b
Do you have UPM + ODFC and the need to merge all into a Profile Container? Thinking about a migration scenario with different policy sets. I'm in the same situation and the Script from @Nick Panaccio is a great idea.
r
FSLogix for both containers. We were using OD, but since that's just a disaster, migrating the environment to new Server 2022/2203VDA without ODFC.
b
is a Big Bang migration planned? wondering how you could apply the FSLogix policy. Group based VHD location settings are possible, but disabling the ODFC on a per group basis? never tested that. Include/Exclude group could be a solution.
r
it seems to work fine, just logging in after removing it. I think I was making up an issue that didn't exist. πŸ˜„
b
nice! gonna test this as well. sometimes things are easier than expected 😁