Where problems arise
Profile issues may originate from storage latency, capacity, exclusions, locked containers, antivirus configuration, multiple sessions, network failures or an unsuitable recovery design. Resolving only the visible error is then insufficient.
Our approach
- Assess profile and storage architecture.
- Measure sign-in times and errors.
- Check size, growth, exclusions and maintenance.
- Review permissions, availability and backup and recovery decisions.
- Test with representative users and applications.
- Document management and incident procedures.
Outcomes
Outcomes
A substantiated FSLogix design or root cause analysis, a tested configuration and a clear recovery procedure. Where possible, sign-in time, error rate and profile growth are compared before and after the change.
Technology
Technology used in these services
- FSLogix
- Azure Virtual Desktop
Frequently asked questions
Is FSLogix the same as backup?
No. A profile container makes a profile available, but does not replace a separate backup and recovery strategy.
Can a damaged profile always be recovered?
Not always. Recovery options depend on the cause, storage and available recovery points. Recovery must therefore be designed and tested in advance.