Your customer is using a virtual desktop infrastructure (VDI) for their support engineers. Multiple users will be logging into the same device, and they want to detect activities for each user.
I vaguely recall something about needing to install the client in a specific mode for VDI setups, but I can't remember if it was per-user or something else.
I’m a bit confused about whether we need separate configurations for each user or if the default mode would suffice. I feel like we did a case study on this.
I think option C sounds familiar from our practice questions, especially regarding per-user settings. It might be the right choice for tracking individual user activities.
I remember we discussed the importance of user-specific configurations in VDI environments, but I'm not sure if that's what they mean by "separate steering configuration."
This seems like a tricky one, but I think option C is the way to go. Peruserconfig mode should give us the user-level tracking we need without a lot of extra overhead. I'm feeling pretty confident about this one.
I'm not too familiar with Netskope, so I'm not sure which option would be the best approach. I think I'll need to do some quick research on the different modes and configurations to make sure I understand the implications of each choice.
Okay, I've got it! Option C is definitely the best choice here. Installing the Netskope client in peruserconfig mode will give us the user-level visibility we need without having to manage a bunch of separate configurations. Nice and straightforward.
Hmm, I'm a bit confused by the different options here. I'm not sure if creating separate configurations for each user is really necessary, or if the default mode with DTLS would be sufficient. I'll need to think this through a bit more.
This seems like a straightforward question. I think option C is the way to go - installing the Netskope client in peruserconfig mode should allow us to detect activities for each user.
I'm not too familiar with Netskope, but Option B sounds like it would involve a lot of overhead to manage separate steering configurations for each user. That doesn't seem very scalable.
Option C seems like the most straightforward solution. Installing the Netskope client in peruserconfig mode should allow for individual user detection without the need for separate configurations.
Glen
3 months agoThurman
3 months agoDavida
3 months agoRolf
4 months agoSonia
4 months agoJose
4 months agoOllie
4 months agoPenney
4 months agoGail
5 months agoCarin
5 months agoAja
5 months agoLeontine
5 months agoRosita
5 months agoTawna
5 months agoFreida
5 months agoGayla
5 months agoStanton
10 months agoFrank
8 months agoAlmeta
8 months agoViola
9 months agoLindsey
10 months agoDorethea
9 months agoRegenia
9 months agoAlethea
9 months agoRoyal
10 months agoYolando
10 months agoBen
10 months agoCheryll
10 months agoHelaine
11 months agoGlory
11 months agoHelaine
11 months ago