Event ID 1301 ->1296 -> 1306: Connection Broker Client Failed to Redirect

good afternoon everyone; 

once again i've hit wall in deploying rd services. scenario stated: 

a non-administrator domain user trying log 1 of pooled virtual desktops (running windows 7).

said user gets prompted windows security login domain credentials; instead of being directed virtual desktop, user redirected second logon session actual server. 

ie: user\administrator has logged in session he/she see's server manager, hyper v etc running. 

[please note: when user\administrator attempts log remote desktop services account redirected 1 of pooled vms. both administrator , non-admin accounts on access list pooled vms in settings of golden template, , in usergroup of collection]

when user\non-administrator has logged in see copy of server 2012 running same "data retrieval failure" error on server roles. 

while checking event viewer series of verbose/error codes such. 

verbose 1301: connection broker received non-admin's request redirection

error 1296: connection broker client failed while getting redirection packet connection broker

error 1306: connection broker client failed redirect user user\non-admin. 

now went though troubleshooting illustrated here: https://technet.microsoft.com/en-us/library/ee890979(ws.10).aspx

it's not network issue, since can ping server straight through router, user desktop, firewall, primary dns, alternate dns, , little nic's inbetween. 

has else encountered issue?

good morning amy, 

for first part, nope both users directed different virtual desktops.

and oddly enough found work around morning; when created pool had usergroup selected domain\domainuser; catch group added ad encompass employee , guest accounts. 

what found was, user groups selection screen didn't that; register administrator account having access vdpool; under account created pool i'm assuming. did morning add specific user account usergroup through properties editor under 

>server manager

>>rds

>>>collections

>>>>collectionname

and still no luck on end. that's when straight deleted pool , started scratch; change being during initial setup of pool added specific users usergroup along catch domain\domain users. , works. 

i don't know why works. @ least here's try else having problem. article amy, i'm going save when deploy our rds real world applications outside of test lab. 

-alex

wow sorry, finished typing before had first cup of coffee. not sure doing 1 time non admin account able log in fluke. did find lead on how fix though in thread on here 2013

resolution
========== 
 if connection broker , rd web access used, add computer accounts each server windows authorization access group of domain.  must verify group has read access user properties of each user object deploying personal virtual desktops to:

1. @ properties of user account , select security tab.  check see if windows authorization access group has effective permissions read mstsproperty01 attribute of user.
2. if group not have read access property, following:
a. on security tab of new user account created, click advanced , highlight windows authorization access group , click edit.
        b. change properties tab , check read properties , select ok.

big shout out to ritesh kumar arora for posting fix. bigger shout out coffee. 

Windows Server  >  Remote Desktop Services (Terminal Services)