Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 5 subscribers
  • Views 835 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

5.5 cycling reboot on certain hardware

AHeil

We are using 5.5 client. We have this deployed on Lenovo T500 laptops running Windows 7 both 64 and 32 bit. There is no issue. When we deploy Windows 7 images either 32 bit or 64 bit on our desktops, which are custom vendor builds, the client installs fine and forces a reboot. It will go through post then the Sophos splash screen, then the Autologin will continue shortly window.  Then the machine simply restarts and returns to post.

The interesting thing is this particular hardware supports the same 5.5 client on a XP image. So it seems to me that the issue may be will a bios setting on the mainboard, but only one that is utilized by Windows 7. I have tinkered with the XP virtualization features but none of them seem to make any difference.

Any assistance is appreciated.

~Adam

:3369


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

    We are using 5.5 client. We have this deployed on Lenovo T500 laptops running Windows 7 both 64 and 32 bit. There is no issue. When we deploy Windows 7 images either 32 bit or 64 bit on our desktops, which are custom vendor builds, the client installs fine and forces a reboot. It will go through post then the Sophos splash screen, then the Autologin will continue shortly window.  Then the machine simply restarts and returns to post.

    The interesting thing is this particular hardware supports the same 5.5 client on a XP image. So it seems to me that the issue may be will a bios setting on the mainboard, but only one that is utilized by Windows 7. I have tinkered with the XP virtualization features but none of them seem to make any difference.

    Any assistance is appreciated.

    ~Adam

    Hi Adam,

    Thank you for posting your question in the SophoTalk Community forum.

    There could be any number of things going on here when it comes to custom vendor builds. It could be Windows 7, the BIOS, or you may need to simply toggle *something* when SGN/SGE 5.50 starts up.

    1. Make sure the system BIOS is current.

    2. Read this KBA to understand the Hot Keys at POA.

    3. Then read this KBA to know which Hot keys to press and when.

    4. If that doesn't help then read this KBA about hardware support.

    5. And if you really want to be a nice guy and help the community. Read this KBA on how to collect your hardware info and get it into the product.

    6. This KBA will instruct you on how to downlaod the latest POACFG file and make it apart of your deployment.

    Please let us know how all of this information works out for you.

    :3438
Reply
  • 0
    AHeil wrote:

    We are using 5.5 client. We have this deployed on Lenovo T500 laptops running Windows 7 both 64 and 32 bit. There is no issue. When we deploy Windows 7 images either 32 bit or 64 bit on our desktops, which are custom vendor builds, the client installs fine and forces a reboot. It will go through post then the Sophos splash screen, then the Autologin will continue shortly window.  Then the machine simply restarts and returns to post.

    The interesting thing is this particular hardware supports the same 5.5 client on a XP image. So it seems to me that the issue may be will a bios setting on the mainboard, but only one that is utilized by Windows 7. I have tinkered with the XP virtualization features but none of them seem to make any difference.

    Any assistance is appreciated.

    ~Adam

    Hi Adam,

    Thank you for posting your question in the SophoTalk Community forum.

    There could be any number of things going on here when it comes to custom vendor builds. It could be Windows 7, the BIOS, or you may need to simply toggle *something* when SGN/SGE 5.50 starts up.

    1. Make sure the system BIOS is current.

    2. Read this KBA to understand the Hot Keys at POA.

    3. Then read this KBA to know which Hot keys to press and when.

    4. If that doesn't help then read this KBA about hardware support.

    5. And if you really want to be a nice guy and help the community. Read this KBA on how to collect your hardware info and get it into the product.

    6. This KBA will instruct you on how to downlaod the latest POACFG file and make it apart of your deployment.

    Please let us know how all of this information works out for you.

    :3438
Children
No Data
Unfiltered HTML