I am wondering how to build a MSI package with a licenses included?
I have the Avast Endpoint Protection Suite Plus with a years subscription.
The first two MSI packages I have built give me “Running in Trial Mode” messages.
I was going to let Avast push everything out but my boss and I don’t want to open all the TCP & UDP ports required as we have 10+ routers I would need to work on. I get the same Trial Mode message if I push the install out and I was informed it was because I needed to open TCP & UDP ports.
if the client can connect to the server it will receive its license. To manage the clients from the console it is needed to open some ports tho.
If you dont open the ports you wont be able to manage the clients and they will all start updating from internet and no reporting will be visible in the console.
My Network is about 150 miles long and I have VPNs between all of my sites so the Avast console should work internally. We just don’t want to open up the TCP & UDP ports to outside networks.
So back to my question how do we create a MSI file with a serial number embedded or already applied?
the console itself spits out an EXE file instead of MSI (see my RFC thread)
havent seen anything about extracting that file and build your own MSI, not to mention including the license
OK I got the MSI with licenses all figured out I had missed 1 checkbox that said Server. Click on it and you will see your EAS server and then everything works great.
Now that I can make a MSI package I though lets go back and see if I can do a push install. First I removed Avast 7 from my Windows 7 PC. Then I created a new task and for software I choose my own working MSI package as it is in the list. All good up to there. My problem is avast can’t seem to see me in the network? I can ping my domain name from the Avast Server? here is the end of the install log file:
03/08/13 12:15:18: Init DOMAIN\My-Machine-Name:
03/08/13 12:15:18: My-Machine-Name: Get Account
03/08/13 12:15:18: My-Machine-Name: not found in domain list
03/08/13 12:15:18: My-Machine-Name: Finished with error
03/08/13 12:15:18: TerminateAll
03/08/13 12:15:19: rinstall end 87
which console you using if you created an MSI? hopefully not the 4.x console (ADNM)
if it is the EA then MSI is new, but last time i checked its still an EXE file that comes out.
did you make sure the filled in user account for pushing is a domain admin account? at the task you have to fill it in with domain \ username without the spaces
OK, I got my Push Installer running. In the Client Side task I made a new push installer and fought with it for awhile but I am getting very close using the MSI package I built last week. By fight I mean the domain field is filled in with my subdomain and the administrative account has the same subdomail entered: ie subdomain\admin is the admin user name.
Now I think the only thing I am fighting is a conundrum. My MSI packake deletes my old Avast and installs the new version 7 just fine.
My MSI package when delivered with a push from Avast will result in an error simular to this one:
03/11/13 11:04:40: InstSvc begin
03/11/13 11:04:40: avast! Remote Install Service
03/11/13 11:04:40: Avast is installed in C:\Program Files\Alwil Software\Avast4
03/11/13 11:04:40: DSA_FileVerify C:\Program Files\Alwil Software\Avast4\Setup\Sfx\avast.setup error
03/11/13 11:04:40: InstSvc end 0
So what I did was manually delete the old Avast from the Windows 7 Control Panel / Programs & Features
Then I tried my push routine again, the one that generated the above error and everything works. Avast installed. So I guess I have to find a way to delete “old” Avast from my client machines using Avast and then chain my “push” routine to the delete routine? Does anyone have any good ideas as to why my MSI package just works from the desktop and fails from a push?
