Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 14 replies
  • Subscribers 1 subscriber
  • Views 22289 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

New setup - cant deploy to users - installation could not be started

dalboy

Hi guys

OK i have installed

Enterprise Console 5 on a server 2008 machine.

I had problems with the database at first and it wouldnt load the interface.  Followed steps online and after lots of messing around I managed to load the console succesfully.

I have managed to protect the server it is already on OK

However, this is a new domain with new antivirus - I can see the 1st workstation i have setup when I do a scan via active directory.  But when I try to protect the computer after a while I get:

Installation could not be started 0x0000002e

Ive done the usual google searches and cant get it to work.

The workstation I am trying to protect is windows 7 64bit.

I have tried to follow the below:

http://www.sophos.com/en-us/support/knowledgebase/111180.aspx

I think I have done it correctly 

Firewall rules and services seem to be correct.

Are there any tests I can do to see what I have missed?

when i do protect computer the administrator password is accepted but then at the end i get the error

Can it be to do with a problem connecting to the database still? If i right click the problem computer in sophos to view computer details i get the error "cannot open database sophos51.  Login failed for user sophosm (which is what the account is in active directory)

Any help appreciated, I did try to follow the setup steps but what they dont seem to match with what I have on screen

thanks!

:27283


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

    Hi,

    Edited: Thanks to Christian being on the ball!

    The first thing I would try is:

    1. On the Sophos management server run:

    runas /user:[domain]\sophosm cmd.exe

    replacing [domain] with your domain name.

    2. In the new command prompt running in the sophosm context, I would run:

    sqlcmd -E -S .\sophos -d SOPHOS51 -Q "Exec dbo.SDDMBootstrapDataGet"

    Does this return an error or some XML?

    If it errors, maybe: http://www.sophos.com/en-us/support/knowledgebase/116454.aspx would be of use?

    The main things to check with deployment are:

    1. The user you are entering in the deployment wizard can log on to the management server.

    2. The computer you are protecting can be accessed using the netbios machine name, i.e.

    \\[computer]\C$

    I would suggest, testing this whilst logged on to the SEC server as the same account you are using to deploy.

    3. I would check that the scheduled task is being created on the target endpoint.

    4. The client can resolve the CID location based on the path in the scheduled task.  If maybe that the Server creates the task asking the client to run setup.exe, but the client is then unable to locate setup.exe in the CID. 

    http://www.sophos.com/en-us/support/knowledgebase/12455.aspx gives an overview of what takes place.

    That should be a good start.  As you're using SEC 5.1, the deployment to the endpoint should be more reliable than even SEC 5.0.

    The article:

    http://www.sophos.com/en-us/support/knowledgebase/116754.aspx

    should be used for SEC 5.1 in a domain environment.

    Regards,

    Jak

    :27285
Reply
  • 0

    Hi,

    Edited: Thanks to Christian being on the ball!

    The first thing I would try is:

    1. On the Sophos management server run:

    runas /user:[domain]\sophosm cmd.exe

    replacing [domain] with your domain name.

    2. In the new command prompt running in the sophosm context, I would run:

    sqlcmd -E -S .\sophos -d SOPHOS51 -Q "Exec dbo.SDDMBootstrapDataGet"

    Does this return an error or some XML?

    If it errors, maybe: http://www.sophos.com/en-us/support/knowledgebase/116454.aspx would be of use?

    The main things to check with deployment are:

    1. The user you are entering in the deployment wizard can log on to the management server.

    2. The computer you are protecting can be accessed using the netbios machine name, i.e.

    \\[computer]\C$

    I would suggest, testing this whilst logged on to the SEC server as the same account you are using to deploy.

    3. I would check that the scheduled task is being created on the target endpoint.

    4. The client can resolve the CID location based on the path in the scheduled task.  If maybe that the Server creates the task asking the client to run setup.exe, but the client is then unable to locate setup.exe in the CID. 

    http://www.sophos.com/en-us/support/knowledgebase/12455.aspx gives an overview of what takes place.

    That should be a good start.  As you're using SEC 5.1, the deployment to the endpoint should be more reliable than even SEC 5.0.

    The article:

    http://www.sophos.com/en-us/support/knowledgebase/116754.aspx

    should be used for SEC 5.1 in a domain environment.

    Regards,

    Jak

    :27285
Children
No Data