A user asked about running FSLogix and UPM together without issues. It was suggested to not use Director for logon times as ControlUp is more accurate and to focus on the Windows logon time. It was also recommended to use the logon duration analysis script provided by ControlUp and establish a baseline. Additionally, FSLogix integration interrogates a remote file share every 5 minutes and does not provide free space info, other than that it can be requested via Solve UserVoice. Links provided: https://www.controlup.com/resources/blog/entry/analyzing-logon-duration-just-got-better/, https://www.controlup.com/script-library-posts/enable-requirements-for-logon-duration-analysis/.
Read the entire ‘Logon Time Metrics in ControlUp with FSLogix and UPM’ thread below:
Keen to get involved with FSLogix metrics, but traditionally we retained UPM to get metrics on logon times, even though we wholly use FSLogix for profiles. This was because, apparently if its excluded, then Director can’t figure out logon times. Our ControlUP triggers monitor CVAD Average Logon Times. Will this break if we exclude UPM? Wondering if there is a supported config that will allow us to have both from ControlUP, Logon times, and FSLogix integration?
Don’t use Director for logon times. It’s crap 🙂 and not very accurate. Controlup is much better. I tend to ignore the CVAD Logon Duration and focus on the Windows logon Time. The data in Director and Controlup just indicate if there is an issue but will not tell you what the issue is. Have you looked at the logon Duration script controlup provide this is what will help you.
@member the warning around UPM is in response to inconsistent results we saw during BETA testing. In rare scenarios on customer deployments, the Machine metrics for FSLogix were not retrieved by us and it only occurred when UPM was installed, this was a WMI issue but could not be replicated on demand. We had countless successes of running both FSLogix and UPM, so I would welcome your feedback on your experience.
thanks @member – the issue we have with Windows Logon Time, is as far as I can see. This is a Machine metric, one that will alert on every incident. Whereas the CVAD one is an average based on a ‘folder’, that we can trigger a single action / email. Unless there is a way to average out all of the Machine metrics and generate a single action?
@member not sure i follow can you detail more
sorry, I said Device, i meant Machine.
Have u used the logon duration anylis script yet?
is Windows Logon Time an average? We use CVAD Average Logon Duration, as it calculates an average.
Michine logon time is average yes but if u want a proprer refection of a user logon duration u should be focusing on session
i generaly ignore the machine average
I’ve just found it, its not under Machine. Its under Session, is it one of these you reccomend?
not sure what that is?
before u set a trigger have u established a baseline? otherwas u will just be spamed
we just configure to alert on anything that goes over 45 seconds.
I’ve just found this under folder..! Looks like this may give us what we want, and not be dependent on CVAD?
Before implementing a logon duration trigger on a site, I always take the time to establish a baseline and set stress level counters. This involves monitoring user sessions and determining who is exceeding the established baseline. Once this information is gathered, I run a login duration analysis script to identify any potential issues.
By following this process, I can quickly determine if the customer is experiencing any significant issues and validate the established baseline.
than then yest you could set that an average logon trigger on the machines but i tend to do it on the session but with the correct basline you will get spamed alot
login duration analysis script is ur best friend if u think there is an issue
yep i found it against the machines too. I’ll have a play! Thanks.
@member Thanks Matt, we’ll try it with keeping UPM in for now and feedback.
its very good but you need to enable some stuff for it to work
https://www.controlup.com/resources/blog/entry/analyzing-logon-duration-just-got-better/
https://www.controlup.com/script-library-posts/enable-requirements-for-logon-duration-analysis/
yeah we use that script quite often for troubleshooting, cheers
@member What are the Remote Share metrics, that are mentioned in that article? I can’t find much reference to it. It would be cool if it could report on disk space on the share.
Hi @member. Where do you see “Remote Share metrics”? In which article?
@member thank you for the screenshot, with the FSLogix integration we interrogate the remote file share to pull back sizing information per FSLogix container. By default this occurs every 5 minutes, the registry key allows you to control this to reduce iOPS on your remote storage if required.
At this time we do not provide remote storage free space, however with our new UserVoice feature (via Solve) you can raise this as an idea and if you tag @member and myself we can consider this. UserVoice is also another way for you to add weight behind existing ideas, the more requests an idea receives the higher the probability we will develop it.
Continue reading and comment on the thread ‘ControlUP Monitoring: Combining CVAD Logon Times with FSLogix Integration without UPM? Supported Configuration?’. Not a member? Join Here!
Categories: All Archives, ControlUp Real-Time DX, ControlUp Scripts & Triggers