Comments (7)
This may be possible in the future once I finally switch the product over to
Visual Studio. For now most users rely on scripting for mass deployment.
Original comment by [email protected]
on 13 Apr 2011 at 4:08
- Added labels: Type-Enhancement
- Removed labels: Type-Defect
from eventlog-to-syslog.
I have no experiences creating Windows software packages, but it sounds like
http://wix.sourceforge.net/ would be able to help creating MSI packages - no
matter what compiler is being used for the binaries.
Original comment by [email protected]
on 13 Apr 2011 at 8:04
from eventlog-to-syslog.
I have heard of wix, but never used it myself. I may look into it in the
future, although for now using VS will probably be the quickest and easiest
method.
Original comment by [email protected]
on 15 Apr 2011 at 2:49
- Changed state: Accepted
from eventlog-to-syslog.
We were facing the same problem, so I created this WiX source file as a
starting point (see attached file, tested on Windows 2008 R2 only).
On install it will place the 2 binaries in system32, install the service and
start the service.
On uninstall it will stop the service, remove the service, remove the 2
binaries, evtsys.cfg and remove registry keys.
It has some issues:
1) I'm not happy with the way the services gets installed and started, but it
gets the job done.
2) 64bit only
3) Update to a newer version is untested. In our case we will always uninstall
(this will remove your configuration from the registry!) and install the new
version.
In the wxs file, replace LOGSERVER with your correct server and it will
configure on install time.
Creating the MSI is done by running:
candle.exe evtsys.wxs
light.exe evtsys.wixobj
Original comment by [email protected]
on 3 Aug 2011 at 8:41
Attachments:
from eventlog-to-syslog.
To have the LOGSERVER value be able to be changed during install, surround it
with []'s. So:
ExeCommand='-i -h LOGSERVER'
becomes:
ExeCommand='-i -h [LOGSERVER]'
Then specify the value on the command-line during install:
msiexec.exe /i x:\some\path\evtsys.msi LOGSERVER=foo
Original comment by [email protected]
on 24 Oct 2011 at 8:40
from eventlog-to-syslog.
Thanks a ton for the help, Nathan!
Also, to get this working with both 32 & 64 bit, just straight up delete any
references to 64-bit from Roman's evtsys.wxs. Then call candle.exe with or
without the flag '-arch x64' to make 32 or 64 bit builds, respectively.
Original comment by [email protected]
on 24 Oct 2011 at 9:55
from eventlog-to-syslog.
I made an atempt to produce working msi package for both 32 and 64 versions
which I will be able to use in office to unatended installation on multiple
machines. This was my first contact with WiX, but I must say it's quite nice.
Result is attached. The main diffrences in compare to previous one are:
- Use standard ServiceInstall without CustomCommand for installing the service
- Accept all options used by service and write it down in to registry before
initial startup (use LOGHOST=x.x.x.x in the msiexec)
- Checks the admin privilages before atempt to install service
You can use following command to build both 32 and 64 bit versions
candle -arch x64 -dPlatform=x64 -o Evtsys-x64.wixobj Evtsys.wxs
candle -arch x86 -dPlatform=x86 -o Evtsys-x86.wixobj Evtsys.wxs
light -ext WixUtilExtension Evtsys-x64.wixobj
light -ext WixUtilExtension Evtsys-x86.wixobj
Original comment by [email protected]
on 9 Jun 2012 at 1:46
Attachments:
from eventlog-to-syslog.
Related Issues (20)
- Cannot start service dispatcher HOT 2
- Unable to download source code HOT 1
- Facility switch doesn't work
- Can't install on 2K Server HOT 3
- Wrong "File version" number at EXE-file HOT 2
- could be installed on hyper-v server (core) HOT 3
- Host configuration don't work at instalation HOT 2
- -a option only working in console mode HOT 2
- Events not showing HOT 3
- Specify Security, Application, or System event? HOT 2
- evtsys service (via svchost process) burn all CPU HOT 5
- service not work anymore from suspend state HOT 3
- Evtsys consumes almost all memory of the server HOT 5
- version 4.5.1 does not start service on Windows Server 2008 R2 HOT 1
- Is it possible to failover between servers, instead of sending to all servers?
- Cannot initialize access to registry: "System\CurrentControlSet\Services\EventLog\Application\EvtSys"
- Unable to load multiple EventSource:EventIDs in config file HOT 1
- Does not work on Server 2012 HOT 1
- evtsys.cfg do not seem to work
- Windows Server 2003 config file problem
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eventlog-to-syslog.