Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 13588 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

Air-gapped SEC521 Install, unable to get endpoints to be managed or get software to them.

roberts2

I have set up and air-gapped SEC521 server, I have followed KB article 64899.

I have copied the Warehouse files over from the connected server. Because of the way we run the network I can not push software to the endpoints to update.

So then following the quick start guide for manual install it says to look in View Bootstrap locations, to install agants on the terminals, the address is something like \\server\SophosUpdate\CIDs\SAVSCFXP\S000\ But I do not have CIDs directory in that location.

So I copied the CIDs directory from the source server, and it allowed me to install the agents and the install, down load packages and seem to work, but they do not show as managed in SEC console. I have established that this is because the Parent Address in the registry is incorrect, as it has copied from the source server.

So my question is this, Ihave read on here that I should not copy the CIDs directory, so if I don't copy that directlry at what point or how is the "new"CIDs directlry created, because I do not have one.

I realise I am doing something wrong but I have read so many KB and guide articles on the Sophos site I am now at the point of giving up and using something else that will configure easier.

HELP PLEASE!

:47377


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

    Hello roberts2,

    thanks for sharing the solution (and the underlying problem).

    Now that I've read it, it looks distantly related to the Problem updating a standalone computer with current definitions. But it's probably not. In the mentioned case the metadata (i.e. filenames) was corrupt whereas I assume that you encountered data corruption (i.e. checksum errors).

    you should mention this sort of thing in the KB articles

    I'm not sure how this sort of thing should be mentioned other than please make sure your copy is correct? Which kind of drive is this? Data corruption (actually it's data "absence") can occur on NTFS formatted thumb drives if you don't wait long enough before unplugging them - though I don't think that you did this. I don't think an NTFS formatted device is generally unfit for transfer-

    Christian   

    :47882
Reply
  • 0

    Hello roberts2,

    thanks for sharing the solution (and the underlying problem).

    Now that I've read it, it looks distantly related to the Problem updating a standalone computer with current definitions. But it's probably not. In the mentioned case the metadata (i.e. filenames) was corrupt whereas I assume that you encountered data corruption (i.e. checksum errors).

    you should mention this sort of thing in the KB articles

    I'm not sure how this sort of thing should be mentioned other than please make sure your copy is correct? Which kind of drive is this? Data corruption (actually it's data "absence") can occur on NTFS formatted thumb drives if you don't wait long enough before unplugging them - though I don't think that you did this. I don't think an NTFS formatted device is generally unfit for transfer-

    Christian   

    :47882
Children
No Data