Scenario 1
This scenario involves exporting a LinuxInstaller stub from your SEPM and repackaging the offline installation package.
- Export a LinuxInstaller stub from your SEPM server: Exporting client installation packages
- Download the seplpkg tool to any Linux or Windows machine with Internet access and use it to create a fully installable package, by running the following command:
on Windows OS:
seplpkg-windows-amd64.exe --platform rhel7 --product RU5 repackage <path-to-LinuxInstaller-stub-from-your-SEPM>
or on Linux OS:
./seplpkg-linux-amd64 --platform rhel7 --product RU5 repackage <path-to-LinuxInstaller-stub-from-your-SEPM>
Note: replace "platform" and "product" arguments, depending on your needs. The example above will create a SEP 14.3 RU5 package for RHEL7. Please check other available arguments here.
- Copy the new repackaged installer to the "offline" Linux server, make it executable and run with the argument -g, to ignore repository and use local packages. Like so:
chmod u+x LinuxInstaller
./LinuxInstaller -- -g
Scenario 2
This scenario involves creating an unmanaged offline installation package first, then importing the client-server communications file (Sylink.xml) from your SEPM.
- Download the seplpkg tool to any Linux or Windows machine with Internet access and use it to create a fully installable package, by running the following command:
on Windows OS:
seplpkg-windows-amd64.exe --platform rhel7 --product RU5 dl
or on Linux OS:
.
/seplpkg-linux-amd64 --platform rhel7 --product RU5 dl
Note: replace "platform" and "product" arguments, depending on your needs. The example above will create a SEP 14.3 RU5 package for RHEL7. Please check other available arguments here.
- Copy the new repackaged installer to the "offline" Linux server, make it executable and run with the argument -g, to ignore repository and use local packages. Like so:
chmod u+x LinuxInstaller
./LinuxInstaller -- -g
- Export the client-server communications file (Sylink.xml) from your SEPM: Exporting the client-server communications file (Sylink.xml) manually
- Transfer and import the client-server communications file (Sylink.xml) to your Linux server with the following command:
/opt/Symantec/sdcssagent/AMD/tools/sav manage -i <path-to-your-sylink.xml>