Detecting Corrupted Disks in FSLogix Profile Management

A user asked how to detect corrupted disks in FSLogix profile management when the profile share was full. Another user suggested creating a ScriptAction to be run when the user logs in so details can be captured and alerted if thresholds are exceeded. The ScriptAction will enter the thresholds into the arguments. It will be shared once finished. https://controlupcommunity.slack.com/archives/C046GSUMTJ9/p1670282169889989

Read the entire ‘Detecting Corrupted Disks in FSLogix Profile Management’ thread below:

Hi, we use FSLogix for profile management, recently our profile share filled up and some disks got corrupted – atleast some indicate now that a scan or repair is needed. The users can still log on and work with a affected disk. I want to detect these corrupted disks over a trigger. So far i tired to detect them over Windows Event ID’s like 55, 98 and 131. However the trigger doesn’t detect every disk at the moment, has anyone an idea to improve this?

Hi Jonas, I’m currently working with a customer on the exact same thing. I am going to update the FSLogix ScriptAction so it will be run when a user logs in, capture the details and then alert if thresholds are exceeded. you will be able to enter the thresholds into the arguments of the ScriptAction. I’m hoping to have it read early next week. I can send you the ScriptAction once done.

Hi Anthony, it would be awesome if you could share the Script Action when you finished it, thanks in advance 🙂

https://controlupcommunity.slack.com/archives/C046GSUMTJ9/p1670282169889989

Give me a shout if you need a hand with it

Continue reading and comment on the thread ‘Detecting Corrupted Disks in FSLogix Profile Management’.  Not a member? Join Here!