Installation Folder

By default, the installer creates the following folder on most English-language installations of Windows.  Avanti components are installed in this folder.  The Installation Options window allows the user to change the default installation folder.

Firewall Exception

Installation and repair configure an inbound Windows Firewall allow rule for the installed dec.exe on Domain and Private networks only. Public networks are not included automatically. If remote console access is needed on a Public network, an administrator must create a separate, appropriately restricted rule in Windows Firewall with Advanced Security. Do not add Public access to the installer-managed rule: repair restores that rule to Domain and Private. If a non-Windows firewall is deployed, configure the required access there too. Organizational policy or other blocking rules may override the local exception.

The managed rule is named Avanti (installer) followed by a path-specific identifier, in the Avanti installer-managed rules group. Upgrade and repair disable old inbound allow rules named Avanti for this exact executable path, retaining their disabled records. Rules for other paths and separately named administrator rules are left unchanged. Uninstall removes only this installation's managed rule. The firewall helper uses Windows PowerShell 3.0 or later and supports the Windows 8 / Windows Server 2012 baseline.

If firewall setup or cleanup fails, Setup reports a warning and continues; this does not confirm that the intended rules are in place. Check administrator rights, the Windows Firewall service and organizational policy. Inspect the rules in Windows Firewall with Advanced Security, then retry with Repair or configure access manually. After an uninstall warning, remove any obsolete rule for this executable yourself. Firewall changes are not rolled back with a failed installation, and an interrupted operation may leave partial changes. Review the rules after a failed or interrupted setup. If Setup reports a timeout, the helper may still be running; let it finish before retrying or changing rules.

Installation Log File

InstallMate normally writes the setup log to the installing account's %TEMP% folder. If setup runs with another administrator's credentials, check that account's temporary folder rather than your own. On a typical English-language Windows installation the folder is C:\Users\<username>\AppData\Local\Temp; the actual path may differ.

At the end of a setup session, InstallMate normally renames the log using this pattern:

PackageName-yyyymmddThhmmss-type.log

The date is year, month, then day; the time is hour, minute, then second. PackageName identifies the installation package, and type identifies the session, such as Install, Remove, or Register. Locate the log by its package name and timestamp instead of assuming a fixed filename.

Before the final rename, the log is named PackageName.log for a new installation or Setup.log for other sessions. Check these names too when diagnosing an interrupted setup. Supplying /log:logpath on the installer command line overrides the final log destination.