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

Creating packages with Deployment Packager

Alphateam

I'm sure this has to be easy, but I just can't get it to work right. I has to be a simple mistake I'm making, but for the life of me can't figure it out. 

For the source folder I have: C:\ProgramData\Sophos\Update Manager\Update Manager\CIDs\S000\SAVSCFXP 

I have holes in the firewall and updating setup off site. I know it works because Sophos consulting helped me do that part of it. The site is http://sophos.mysite.org/SophosUpdate

I then choose RMS because I want it to use our updating locations. Then hit Build Package. After install it says the Primary Location is c:\user\myusername~1\AppData\Local\Temp\cid_p..... and nothing for secondary. 

If I try not and select RMS and put in that address above it can't connect to the server. 

:50372


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

    Hello Alphateam,

    Unassigned is, in the words of the Console Help, a group where Enterprise Console holds computers before you put them into groups, it's the topmost group in the Groups pane. If you did not configure the -G parameter in Additional setup parameters when you created the package and the computer was previously unknown the SEC it turns up in the Unassigned group (if RMS can connect - BTW, RMS uses ports 8192 and 8194).

    If you do not select RMS (with the checkbox) you must specify the Primary location (as said, the complete path)

    If you do select RMS and choose Configure AutoUpdate to download components you must specify the Primary location as above

    If you do select RMS and choose In the package the computer should appear in the console's Unassigned group. As the Unassigned group has no associated policies you have to move the computer to some other group before it can get an updating policy

    Christian 

    :50576
Reply
  • 0

    Hello Alphateam,

    Unassigned is, in the words of the Console Help, a group where Enterprise Console holds computers before you put them into groups, it's the topmost group in the Groups pane. If you did not configure the -G parameter in Additional setup parameters when you created the package and the computer was previously unknown the SEC it turns up in the Unassigned group (if RMS can connect - BTW, RMS uses ports 8192 and 8194).

    If you do not select RMS (with the checkbox) you must specify the Primary location (as said, the complete path)

    If you do select RMS and choose Configure AutoUpdate to download components you must specify the Primary location as above

    If you do select RMS and choose In the package the computer should appear in the console's Unassigned group. As the Unassigned group has no associated policies you have to move the computer to some other group before it can get an updating policy

    Christian 

    :50576
Children
No Data