| I work in the NHS, this is the current user experience 1. Type in user name and password onto computer 2. Logs in to windows, normally taking ~60 seconds, unless you've got the computer where the WiFi signal is poor (yes, WiFi on desktops!) and you get a 'no log in servers' 3. Windows finally loads, click the icon for the software for viewing blood test results 4. An internet explorer window opens, then closes, then after 10 seconds the software opens 5. Type in your username and password, wait 10 seconds 6. Now I want to prescribe some medications, close the first software (computer can't cope with two things open at once), click the logo for the prescribing software 7. A Google Chrome window opens, slowly loads the prescribing software website 8. Type in username and password 9. Navigate through the slow and unintuitive prescribing software 10. Oh wait, I can't prescribe this particular drug without checking a blood test result, close the prescribing software and go to step 4 11. Some alarm goes off, so I have to lock the computer and run. Return from dealing with the alarm, go back to step 1 |
1) PC is desperately under-provisioned, probably several years old and upgraded to Windows 10
2) Too large roaming profile (easy situation to get into and hard to spot other than "it's slow")
3) Too slow AD profile server to get the large profile from
4) Internal websites "should" use NTLM authentication if available, which would remove the requirement to log in again, but forwarding this outside the domain properly is remarkably hard
5) Smartcard auth can offer the dropin use case with no typing, but it's a pain to provision and costs more
In many cases you'd be better off with an IBM 3270 terminal but with higher resolution text and images...
In my previous job we built a Windows CE-based system that let you log in instantly by tapping a keyfob and brought the screen you were last using up anywhere on the site, running on fifteen-year-old hardware. It was for selling beer.