RDS Gateway - Why are RAP changes requiring reboot to take effect?
i have win2k8r2 rds gateway. using ad groups in rap define network resources can accessed users. part, it's working expected, finding changes ad group (e.g. remove server) not taking effect immediately. users still able establish new connection server has been removed ad group. if reboot rds gw, change seems take effect, , users can no longer access removed server.
while haven't tested extensively yet, change may take effect after period of time, without requiring reboot ... doesn't me either. need have such changes take immediate effect.
i've searched web without luck, awkward topic meaningful results on. can tell me definitively when changes ad groups take effect in rap ... , how can force take immediate effect (without reboot)?
thanks,
rob
thank posting in windows server forum.
case, have manually tested in lab environment , works fine me. have removed user ad , has been removed rd rap policy , don’t need restart server. deleted user cannot able take remote session after that.
after adding user again server ad group able take remote connection , @ time didn’t have restart server.
please try check setting again, doesn’t required restart of server take effect.
hope helps understand!
thanks,
dharmesh
Windows Server > Remote Desktop Services (Terminal Services)
Comments
Post a Comment