Jump to content

Recommended Posts

Posted
(Side-note: I've also edited login.aspx on our setup to change the string on the sign-in page from "Domain\username" to just "Username" to ease any confusion.)
Posted
UPDATE!

 

This is apparently not the behaviour for all clients. My clean Win10 test environment was fine, but then a colleague's Win7 school laptop didn't like having e.g. "GREENABBEY\[email protected]" as the username and would prompt twice without accepting the latter, so I've now corrected for this too.

 

In webscripts-domain.js, just above the previous edit beginning with if ( -1 == strDomainUserName.indexOf("@") ), insert this:

 

if ( -1 != strDomainUserName.indexOf("") )

{

strDomainUserName = strDomainUserName.substring( strDomainUserName.indexOf("") + 1, strDomainUserName.length );

objForm.elements["DomainUserName"].value = strDomainUserName;

}

 

So that section of the code should now look like this:

 

strDomainUserName = objForm.elements["DomainUserName"].value;

if ( -1 != strDomainUserName.indexOf("") )

{

strDomainUserName = strDomainUserName.substring( strDomainUserName.indexOf("") + 1, strDomainUserName.length );

objForm.elements["DomainUserName"].value = strDomainUserName;

}

if ( -1 == strDomainUserName.indexOf("@") )

{

strDomainUserName = strDomainUserName + strDomainName;

objForm.elements["DomainUserName"].value = strDomainUserName;

}

strPassword = objForm.elements["UserPass"].value;

 

This should ensure that, regardless of whether the user enters "username", "GREENABBEY\username" or "[email protected]" for the initial sign-in, it will go down as "[email protected]" and should work fine! :)

 

I cannot get this to work for Windows 7 clients - I still get the second prompt after launching the app and requiring domain\username

Posted
This is how that whole section of code should look:

 

[ATTACH=CONFIG]41359[/ATTACH]

 

After inserting the code and logging on for the main screen it removed the first character from the username, so comes up saying invalid login!

Posted
Something can't be quite right with the way you've edited the file then. That's a direct screenshot from ours and it's working fine on Server 2016. Alternatively, perhaps some modifications are needed for 2012 R2 after all - can anyone else confirm who got it working?
Posted
Something can't be quite right with the way you've edited the file then. That's a direct screenshot from ours and it's working fine on Server 2016. Alternatively, perhaps some modifications are needed for 2012 R2 after all - can anyone else confirm who got it working?

 

Yes using 2012 r2 here - with the modifications it doesn't second prompt on windows 8.1 but on 7 it does.

Posted
has anyone been able to test this on 2012 R2 as to whether they are still prompted on Windows 7 clients the second time and requiring domain\username like i do?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...