Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 5 subscribers
  • Views 29070 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

SGE 5.60 - autologon issue

secadm

Hi everyone,

I upgraded SGE and 3 clients to 5.60 and one of the upgraded clients has problem with Autologon / POA. Installation process completed successfully and connection with the server exists, but after reboot I can see message "Autologon will continue shortly." everytime. Two of the upgraded clients have no problems. Could anyone tell me what might be wrong? I have to give this laptop back to one of manager, so problem is quite urgent.

Edit: I reinstalled Windows 7 a few times ( with disk format) with the same effect. In the status pane of SGN Client I can see: SGN user state is pending and Data packets prepared for transmission = 2. Additionally in the Management Center in inventory section for this machine POA checkbox is unchecked, but in the policy POA is enabled.

I have to decide and tell to my principal if it is a problem with hardware ( so they have to buy another laptops) or it is a problem with software.

:12969


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

    Hi sallzall,

    thank you very much for posting. Actually the trace file does contain the most and best information for us to check if things are ok.

    At your side you could check if the SGN POA kernel is properly written to the disk (open a cmd prompt > chkdsk c:\ (No Parameters!) > see if there is approx 98mb of bad sectors on the drive).

    Additionally you can check in the Management Center if the machine has reported any events back that would point to a problem.

    Last but not least you can check if the encryption does kick in > should those machines also not start to encrypt there is a problem with the kernel but this would then still require further analysis.

    Finally you could also try to change the log on name (user@domain instead domain\user) - eventually things will change then?

    Regards

    Dan

    :17919
Reply
  • 0

    Hi sallzall,

    thank you very much for posting. Actually the trace file does contain the most and best information for us to check if things are ok.

    At your side you could check if the SGN POA kernel is properly written to the disk (open a cmd prompt > chkdsk c:\ (No Parameters!) > see if there is approx 98mb of bad sectors on the drive).

    Additionally you can check in the Management Center if the machine has reported any events back that would point to a problem.

    Last but not least you can check if the encryption does kick in > should those machines also not start to encrypt there is a problem with the kernel but this would then still require further analysis.

    Finally you could also try to change the log on name (user@domain instead domain\user) - eventually things will change then?

    Regards

    Dan

    :17919
Children
No Data
Unfiltered HTML