PDA

View Full Version : Won't read XML file


bateslabel
July 14th, 2009, 03:50 PM
I am doing a trial for our company. I am having an issue where the package won't read the xml file. I created a temp folder, shared it out, and put both the msi and the config file in the same folder. But the msi does not read the xml file. What am I doing wrong?

Cudni
July 14th, 2009, 03:52 PM
any messages errors or info?

bateslabel
July 14th, 2009, 03:58 PM
{QUOTE-> any messages errors or info? <-QUOTE}


No. It just installs but without any changes listed in the xml file.

Brambb
July 14th, 2009, 04:01 PM
The config file has to be named 'cfg.xml' in order to be automaticly catched by the installer.
Im not really sure about this, but I thought it only works if you install it silently, ie with the use of a batch file. If you just double click the MSI and follow the setup it wont catch the .xml file. (But I may be wrong on this!)

Batch file I use looks something like this:

@echo off
net use t: \\server\esetsetup /persistent:no /yes
t:\eavbe_nt32_enu.msi /qn REBOOT="ReallySuppress"
net use t: /delete /yes


Share contains the msi installer, the config file (cfg.xml) and the above install.bat

/edit; For more command-line options (and push installations) you can read the ERA manual. It has a client install guide.
/edit2: In this (http://www.wilderssecurity.com/showthread.php?t=241369) topic I also explained how to use a self extracting file to use as a installer. Might be of use.

bateslabel
July 14th, 2009, 04:09 PM
{QUOTE-> The config file has to be named 'cfg.xml' in order to be automaticly catched by the installer.
Im not really sure about this, but I thought it only works if you install it silently, ie with the use of a batch file. If you just double click the MSI and follow the setup it wont catch the .xml file. (But I may be wrong on this!)

Batch file I use looks something like this:

@echo off
net use t: \\server\esetsetup /persistent:no /yes
t:\eavbe_nt32_enu.msi /qn REBOOT="ReallySuppress"
net use t: /delete /yes


Share contains the msi installer, the config file (cfg.xml) and the above install.bat

/edit; For more command-line options (and push installations) you can read the ERA manual. It has a client install guide. <-QUOTE}

I have been trying to do a remote install doing a push installation using xml config. The file is named cfg.xml. Is that the wrong way? I am reading from the manual and unless I am reading it wrong I should be able to do it like that.

Brambb
July 14th, 2009, 04:14 PM
Are you using ESET RA for that?
http://www.eset.com/download/ESET_ERA_User_Guide_EN_rew.pdf - In this manual its explained in detail how to push a clients installation with RA.

bateslabel
July 14th, 2009, 04:17 PM
{QUOTE-> Are you using ESET RA for that?
http://www.eset.com/download/ESET_ERA_User_Guide_EN_rew.pdf - In this manual its explained in detail how to push a clients installation with RA. <-QUOTE}

Yes that is the manual I am using. Chapter 4.

Brambb
July 14th, 2009, 04:23 PM
So what is the exact problem you have with ERA? Having trouble making a package? or pushing it out to clients?

In the first post your talking about a share and you want to install from it? (then you can use that batch file for it)

bateslabel
July 16th, 2009, 04:07 PM
I was able to figure it out and it is working good now ;D

Brambb
July 16th, 2009, 04:22 PM
Glad to read you have it all working :).