It allowed organizations to define more than one password and account lockout policy in a single domain, and apply those policies to different sets of users. The change did not require a reboot of the XenApp server(s).The fine-grained password policies feature was introduced in Windows Server 2008. Name: LogonUIHeight | Type: REG_DWORD | Value: 600 (Decimal)Īfter creating the keys shown above, the logon disclaimer window was larger, the scroll bar was gone, and the users could once again click OK without worrying about focus or scroll bars.Name: LogonUIWidth | Type: REG_DWORD | Value: 800 (Decimal).HKLM\Software\Wow6432node\Citrix\CtxHook\AppInit_DLLS\Multiple Monitor Hook.To set the width and height of the logon disclaimer window, add the following registry keys: If the scroll bar was not to the far left of the disclaimer page, the OK button “wouldn’t work”, which confused the users.Ĭitrix support told me the logon disclaimer window has a default size of 600 and 520 (H) but that the size can be adjusted (in this case increased) so as to get rid of the scroll bar in order to maintain the focus of the disclaimer window. The problem I have seen when using Server 2012R2 is that the logon disclaimer is “larger” than it was with Server 2008R2 and thus when the users launched applications from the 2012R2 server, the logon disclaimer page had a scroll bar. Thus, some organizations disable the logon disclaimer on the by disabling policy inheritance on the XenApp Server OU and others leave the disclaimer in place so as to ensure any users making XenApp connections from non-domain computers will have to acknowledge the logon disclaimer. When publishing applications from Citrix XenApp, if the logon banner is applied via GPO at the domain level, users must acknowledge the disclaimer when accessing published applications….so they acknowledge once when logging into their domain computer, and then again when launching published applications. Many clients that I work with (I’d say over 90%), have logon disclaimers that must be acknowledged prior gaining access to enterprise resources…seen below is simply an example I found online to serve as a frame of reference:
0 kommentar(er)
