Just rolling out the product and on half our pc's...some xp and some windows 7 keep getting error The installation could not start......etc. The pc's are turned on...what is the issue.
This thread was automatically locked due to age.
Just rolling out the product and on half our pc's...some xp and some windows 7 keep getting error The installation could not start......etc. The pc's are turned on...what is the issue.
HI,
Are they running a firewall?
I would check they meet the requirements to push the install task to them.
Setting throught GPO: http://www.sophos.com/support/knowledgebase/article/111180.html
Setting locally: http://www.sophos.com/support/knowledgebase/article/29728.html
Worse case, maybe a pull installation could be the answer for you. The following article lists the switches to install the client software: http://www.sophos.com/support/knowledgebase/article/12570.html . To generate a deployment string, it's quite easy to just deploy to machine you can deploy to, monitor the scheduled tasks, and once the Sophos install task is created, check its properties.
The other option is to try creating the following registry key DWORD on the management server machine:
Under:
HKEY_LOCAL_MACHINE\SOFTWARE[wow6432node]\Sophos\EE\
create a DWORD value called "EnableTaskScheduler2 " and set it to 1.
This will force the task to be created using the newer task scheduler interface. This is to be the default in SEC 5.1 and seems to be more reliable.
Hope it helps.
Regards,
Jak
HI,
Are they running a firewall?
I would check they meet the requirements to push the install task to them.
Setting throught GPO: http://www.sophos.com/support/knowledgebase/article/111180.html
Setting locally: http://www.sophos.com/support/knowledgebase/article/29728.html
Worse case, maybe a pull installation could be the answer for you. The following article lists the switches to install the client software: http://www.sophos.com/support/knowledgebase/article/12570.html . To generate a deployment string, it's quite easy to just deploy to machine you can deploy to, monitor the scheduled tasks, and once the Sophos install task is created, check its properties.
The other option is to try creating the following registry key DWORD on the management server machine:
Under:
HKEY_LOCAL_MACHINE\SOFTWARE[wow6432node]\Sophos\EE\
create a DWORD value called "EnableTaskScheduler2 " and set it to 1.
This will force the task to be created using the newer task scheduler interface. This is to be the default in SEC 5.1 and seems to be more reliable.
Hope it helps.
Regards,
Jak