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

Failed install without cached credentials?

We are using Enterprise 5.2.2 and trying to deply Sophos out to 800+ desktops/laptops/servers. Its been a bit of a nightmare. Different problems every time. This time I am having problems getting Sophos deployed to 146 PCs. If I RDP into the maching with my domain admin credentials and log back off, I can install it fine. However If I never log into that PC the install will fail.

Why is this happening? Why would cached credentials matter? Any way around this? The account I am using is a domain admin account.

:53931


This thread was automatically locked due to age.
Parents
  • It is a push through the SEC. Most PCs throw up the generic error that you get for just about everything that failes. 0000002e. This is not a DHCP or DNS problem. Last night even cleared the DHCP address leases and set a new lease time of 8 hours instead of 24. So all of the DHCP leases are new and all of the DNS A records are new. I have 900 computers that are imported. I only have 147 of those that are being managed.  I have tested everything I possible could to get this to work. All of these PCs are the same setups, under the same GPOs and I am using the same admin account that I setup with Sophos admin credentials.

    I have a couple of computers that I have been testing with. Most of the time if I log into that PC with my domain admin credentials it will do the install. Some computers will create the Task and fail on the install, some act as if the task was never created. (At least I never see it or a system log for it).

    There are pretty much different reasons for each install fail that I see. I cant go through all 900 computers and fix each one. But here are a few that I have come across. Most of them can be resolved just by me logging into the PC.

    One PC that I am testing on will not even do a bootstrap install. Creates an error log Event ID 36887. The following fatal alert was received: 40.

    Another is 3rd party software can not be removed when there is no software....

    80% of the computers that are being managed. Are still saying Awaiting Policy Transfer. I have "comply with" on all PCs.

    :53949
Reply
  • It is a push through the SEC. Most PCs throw up the generic error that you get for just about everything that failes. 0000002e. This is not a DHCP or DNS problem. Last night even cleared the DHCP address leases and set a new lease time of 8 hours instead of 24. So all of the DHCP leases are new and all of the DNS A records are new. I have 900 computers that are imported. I only have 147 of those that are being managed.  I have tested everything I possible could to get this to work. All of these PCs are the same setups, under the same GPOs and I am using the same admin account that I setup with Sophos admin credentials.

    I have a couple of computers that I have been testing with. Most of the time if I log into that PC with my domain admin credentials it will do the install. Some computers will create the Task and fail on the install, some act as if the task was never created. (At least I never see it or a system log for it).

    There are pretty much different reasons for each install fail that I see. I cant go through all 900 computers and fix each one. But here are a few that I have come across. Most of them can be resolved just by me logging into the PC.

    One PC that I am testing on will not even do a bootstrap install. Creates an error log Event ID 36887. The following fatal alert was received: 40.

    Another is 3rd party software can not be removed when there is no software....

    80% of the computers that are being managed. Are still saying Awaiting Policy Transfer. I have "comply with" on all PCs.

    :53949
Children
No Data