Domain User Account
For Domains Only: At the top of the page you have the ability to enable task scheduling for dSupportSuite with the Windows Task Scheduler under the specified domain credentials.
- This causes the Maintenance, the Heartbeat, and other tasks that would need internet access and full machine access during that time to run with the credentials specified here.
- If left blank, the local system account is used, which is the recommended practice for non-domain machines.
Config Password Option
An optional password can be specified to restrict access to two critical areas. This is really unnecessary, as you will read about below in these two areas:
- You may password protect the full configuration (not Config Lite.) Note the full configuration can only be accessed by running dSupportSuite.exe with the /config parameter, via D7, or by holding the SHIFT key down while executing dSupportSuite.exe. It is never installed as a start menu shortcut.
- The Client Identifier configuration can be password protected, but is only used when you want to re-assign a new client ID to an existing installation. The Client Identifier configuration can only be accessed by running dSupportSuite.exe with the /ClientID command line parameter, or via d7.
Custom Installer Options
These settings are specified to control the custom installer’s behavior.
- Place a Run shortcut on the Desktop – Optional. One will always be placed in the Start Menu, however, under a sub-folder of your company name.
- Place an Uninstall shortcut in the Start Menu – Note an installer entry will always be shown in Windows Control Panel for uninstall, so this isn’t *necessary* and may be omitted.
- Place a Config Lite shortcut in the Start Menu – This option starts Config Lite, which is convenient for configuring only a few minor client settings that it is ok for the end user to access.
- Open Config Lite after install – Same as above, this opens Config Lite after install for the convenience of entering in client specific details such as name / phone number / email address of the person using that workstation, to be used in automated emails by the system.
- Start Menu URL – Specify a URL you wish to appear in the start menu here. Do NOT put http:// in front of this URL string! If you do, the :// throws off Windows as it attempts to make a file of that name.
- Email an initial Heartbeat on install – does just that, a full Heartbeat on install is a convenient way to keep track of who/how many installs you’ve done and get an initial health report on the PC.
Some reporting is generated during maintenance routines, either by dSupportSuite itself or possibly by a custom application you have configured. This tells dSupportSuite where to store the reports. You have several choices:
- [app_directory]Reports – This keeps reports inside dSupportSuite’s own application directory. They are temporarily stored in the Reports subdir, and will be deleted each and every time dSupportSuite is relaunched.
- %systemdrive%Support[your app name] Reports[Date] – This keeps them in the Support folder in the root of the OS drive, within a subdir with your app’s name, and another subdir for the date the reports were generated. This is a good location to keep the reports on the customer’s machine, but out of their immediate view. These reports are never deleted.
- %allusersprofile%Documents[your app name] Reports[Date] – Good for keeping the reports where your client can access them (in their own documents) these reports are organized in subdirs by date as above and are never deleted.
- _________[Date] – Define your own custom location on the hard drive here, and have reports organized by dated subdirs. The standard Windows environment variables described at the beginning of this manual can be used here.