Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 5 subscribers
  • Views 10156 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Windows 7, unlock delay when offsite

Steven

Hi,

I have installed version 5.50.1 on several laptops Dell E6510 with Windows 7.
Several clients complain about Windows unlock delays (sometimes 10 or 30 seconds)
No problem to lock the laptop, but when unlocking the password dialogue remains visible, so you have the impression that the enter key was not pressed.
This only occurs when not connected to the internal network, no connection to the domain controller.
Behavior is always different, sometimes direct unlock, sometimes 5 sec,10 sec, 30sec.
Clients are located offsite, safeguard server is reachable over the internet.

According to support this normal behavior when not connected to DC, but for the end users this delay is very annoying.

Any suggestions, anybody dealing with the same issue?

:6585


This thread was automatically locked due to age.
Parents
  • 0

    Hi FrancoisCaty,

    thanks for your post on this rather old thread.

    We have seen this issue before when a machine that was connected to a corporate network went into a hibernation/standby state and changed the location into a different network or network segment where the physical address for LDAP, Domain logon or Kerberos services changed.

    In addition, the delay at logon with above described scenario only occurred when the SafeGuard Credential Provider was used to logon to the system for the first time after changing the location. The delay does not occur with the Windows Credential Provider.

    Can you confirm the above? In addition to that, do you use the SafeGuard Configuration Protection module on the clients that are affected by the ~10 seconds logon delay to Windows?

    Regards,

    ChrisD

    :37257
Reply
  • 0

    Hi FrancoisCaty,

    thanks for your post on this rather old thread.

    We have seen this issue before when a machine that was connected to a corporate network went into a hibernation/standby state and changed the location into a different network or network segment where the physical address for LDAP, Domain logon or Kerberos services changed.

    In addition, the delay at logon with above described scenario only occurred when the SafeGuard Credential Provider was used to logon to the system for the first time after changing the location. The delay does not occur with the Windows Credential Provider.

    Can you confirm the above? In addition to that, do you use the SafeGuard Configuration Protection module on the clients that are affected by the ~10 seconds logon delay to Windows?

    Regards,

    ChrisD

    :37257
Children
No Data
Unfiltered HTML