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

Change Software Distribution path

macoy

I was able to upgrade our existing Sophos Enterprise Console (SEC) from 3.1 to 4 and also was able to migrate all of the settings to the new Sophos Update Manager (SUM).

I now on the process of fine tuning my installation. As what I have stated on my previous post I extracted the SUM and SEC upgrade on a separate drive (drive D:\). What I noticed is that the bootstrap location or the software distribution path is placed on drive C:\ (\\<server name>\SophosUpdate). I want to transfer this bootstrap location to drive D:\ so that everything is present there on my Sophos folder which is located on drive D:\.

Now, what I did is I created a new shared folder on my Drive D:\ and I added it on the Software Distribution tab on SUM. How ever I couldn't  place the original bootstrap location which is \\<server name>\SophosUpdate on the left side of the selection so that the my new shared folder which is located on drive D:\ will be the one left on to the Update to: field. I have already disabled the sharing of the original bootstrap location on drive C:\.

Are there any other ways wherein I could transfer the bootstrap locations to the other drive that I have which is on Drive D:\ so that whenever I am going to download the updates from the Sophos all of the software updates will be placed on the shared folder that I have created on drive D:\ and not on its original bootstrap location which is \\<server name>\SophosUpdate which is on drive C:\.

Thanks....

:1217


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

    Hi,

    Reading through this article, I've some questions that there doesn't seem to be reasonable answers to but I believe I've figured out. This is specifically aimed at sites using remote SUM servers.

    Firstly, remote SUM sites don't have an SEC folder (they only have the c:\program files\sophos\update manager folder). So the instructions to mod the system.xml file change and you'll find that file in the UM folder. You can mod that and restart the SUM service which indeed allows you to move the warehouse and working folders. BUT, and it's one big BUT, SUM continues to write the CIDs folder back into the c:\program files\sophos\update manager\update manager folder. Great! Now none of the clients update because you've repointed the SophosUpdate share at your new location when it's writing the CIDs bck in the original location.

    Hold on though. I found that if you mod the config.xml file and change the CID locations in that for each package you have subscribed to, and restart SUM again, it will correctly write CIDs to the new location. However now of course, the central SEC console shows the remote SUM as not matching configuration. If you now make the remote site comply with configuration back on the central SEC, it rewrites the config.xml but leaves your new locations alone making it comply again with configuration and BINGO! you now have a fully functional remote SUM with working, warehouse and CIDs folders not stored on your precious C drive.

    Matt

    :6381
Reply
  • 0

    Hi,

    Reading through this article, I've some questions that there doesn't seem to be reasonable answers to but I believe I've figured out. This is specifically aimed at sites using remote SUM servers.

    Firstly, remote SUM sites don't have an SEC folder (they only have the c:\program files\sophos\update manager folder). So the instructions to mod the system.xml file change and you'll find that file in the UM folder. You can mod that and restart the SUM service which indeed allows you to move the warehouse and working folders. BUT, and it's one big BUT, SUM continues to write the CIDs folder back into the c:\program files\sophos\update manager\update manager folder. Great! Now none of the clients update because you've repointed the SophosUpdate share at your new location when it's writing the CIDs bck in the original location.

    Hold on though. I found that if you mod the config.xml file and change the CID locations in that for each package you have subscribed to, and restart SUM again, it will correctly write CIDs to the new location. However now of course, the central SEC console shows the remote SUM as not matching configuration. If you now make the remote site comply with configuration back on the central SEC, it rewrites the config.xml but leaves your new locations alone making it comply again with configuration and BINGO! you now have a fully functional remote SUM with working, warehouse and CIDs folders not stored on your precious C drive.

    Matt

    :6381
Children
No Data
Unfiltered HTML