Forum Discussion
Solved
The case of Persistent, SessionHost assignment remains even if the user is unassigned from AppGroup.
Is this in the specifications? Here is what I tried: 1). Created HostPool as a personal type (persitent is true). 2). After signing in as a user, that user was assigned to the session host. 3)....
kyohei_ : Yes, this behavior is by design, in two ways:
1. The removal of the user from the app group does not remove the session host assignment.
2. Through the cmdlets, you can't simply re-assign a session host to a different user. We view this as tight security, since a user likely had local data on the VM (as opposed to the pooled scenario where that user's profile was on a user profile share).
To re-assign that session host, you need to completely remove it from the environment, then re-register the host.
