Update Win Server with Mirror tool didn't work

[FrankM 0]

Hi,

 

I want to update a Windows Server without internet via mirror tool and shraed folder

But I get the error "Module update failed" Product update failed" Could not connect to server.

I installed the mirror tool under linux:

MirrorTool --repositoryServer AUTOSELECT --intermediateRepositoryDirectory /tmp/repoTemp  --outputRepositoryDirectory /opt/eset/mirror/RepoMirror --languageFilterForRepository de_DE en_US DE en_US --downloadLegacyForRepository --productFilterForRepository Security --offlineLicenseFilename .....

My smb.cfg:

[mirror]
path = /opt/eset/mirror/RepoMirror/
   public = yes
   writable = no
   printable = no
   guest ok = yes
   browseable = yes

 

Folder on the mirror server:

/opt/eset/mirror/RepoMirror/com/eset/apps/business/efs/windows/v7/
total 44K
drwxr-xr-x 11 root root 4.0K Oct 13 09:58 .
drwxr-xr-x  4 root root 4.0K Oct 13 10:15 ..
drwxr-xr-x  4 root root 4.0K Oct 13 09:58 7.0.12016.1

 

I configured an new policy with:

 

Create update mirror

storage folder: \\ESET_Server\mirror\com\eset\apps\business\efs\windows\v7

disabled "Enable HTTP server"

Username DOMAIN\Administrator

 

Via Windows explorer the share is accessible

 

ESET Security Management Center (Server), Version 7.2 (7.2.2236.0)
ESET Security Management Center (Web Console), Version 7.2 (7.2.230.0)

 

Anny clue?

 

Thanks

Edited November 9, 2020 by FrankM

[Marcos 5,250]

I would change "path" from " /opt/eset/mirror/RepoMirror/"  to "/opt/eset/mirror/RepoMirror/com/eset/apps/business/efs/windows/v7/" and the path to the mirror to "\\ESET_Server\mirror"

[FrankM 0]

after the suggested changes, same error

 

[FrankM 0]

I also try to map the  to z: in windows and set z: as path in the policy. Same error

[Marcos 5,250]

What about installing http server and making the mirror accessible via http?

[FrankM 0]

Hm, but where I have to configure the path?

What I did:

Install a Apache virthost on port 2221, DocumentRoot /var/www/html/mirror/ an the eset server

the path structure  the mirrortool creates: /var/www/html/mirror/mirror/com/eset/apps/business/ees/windows/v7

In the police I configure:

Update -> Updates -> Module Updates -> Custom Server: hxxp:\\eset:22221

   Program component update -> Custom Server: hxxp:\\eset:22221

  Update Mirror -A enable HTTP server

   http server -> port 2221

[Marcos 5,250]

Is the machine with the mirror called "eset"? You might want to use the IP address instead.

[FrankM 0]

Hello Marcos,

 

yes the name of the mirror server is eses. to use IP address didn' make a change

I get the error "File not found on server" If I try to use http

 

[Marcos 5,250]

Sorry, I didn't realize what the issue was. With the document root set to /var/www/html/mirror/, the path in the update setup on clients should be http://eset/mirror/com/eset/apps/business/ees/windows/v7:22221 according to your information above.

The following link should open in a browser:

http://eset:22221/mirror/com/eset/apps/business/ees/windows/v7/update.ver

[FrankM 0]

Its really confusing.

 

if I use the parameters  intermediateRepositoryDirectory and outputRepositoryDirectory, as decribed above, I get the path .."/com/eset/apps/business/ees/windows/v7;", but without any file named "update.ver" and it don't work.

If I use --intermediateUpdateDirectory and --outputDirectory, I get a path like "mirror/eset_upd/ep7/" and a file named update,ver. This way is working.

[Marcos 5,250]

While the first parameters serve to create a local repository with installers, the second parameters are used to create a mirror with update files.