-
Notifications
You must be signed in to change notification settings - Fork 6
Installing Zombie Service
The easiest route to installing and uninstalling Zombie Service is via command line.
- Navigate to the folder that has ZombieService.exe. In my case that would be a place that I am building Zombie to so \ZombieService\debug location
- Run install command with a
/uflag to uninstall an existing service:C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe /u ZombieService.exe - Run install command to re-install, this time skip the
/uflag:C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe ZombieService.exe
Launch the command line tool, or PowerShell, and type this in:
msiexec /i ZombieInstaller.msi /quiet /qn SETTINGS_PATH="<path to settings>" ACCESS_TOKEN="<access token>" WEB_SERVICE_ENDPOINT="<path to logging service>"
Silent install is pretty useful when Zombie is being deployed to users via batch scripts. It doesn't show the UI, and just takes place in the background. You can optionally pass /log argument followed by a path like so: /log "C:\Some Path.txt" to generate a log file for the install process.
Simply double slick the ZombieInstaller.msi and you will be presented with a series of windows:
-
Zombie Settings Path: This is the path to where your distribution settings are located. I didn't remove this path, because it illustrates that the settings can be made public. That's not an issue. You can also host them on your GitHub repo, which makes managing them a little easier. They can be stored locally, in which case, this would be a local file path.
-
GitHub Token: This is an access token for Zombie to be able to pull stuff from the repo you specified in the settings. This token is never user visible (its replaced with *** in the UI), and is never exported when settings are published remotely.
-
Log Server Path: Path to an optional logging service. Zombie can write logs locally, or to a remote HTTP endpoint. Please see here for more info: Logging to Web Service