Known issues for each component of NightWatchman, including WakeUp Servers, and client agents. 

On this page:

Issues specific to NightWatchman Management Center

NightWatchman Management Center upgrade might fail if SQL Server has been upgraded

When installing the NightWatchman Management Center 7.1 or 7.2 the previous version is uninstalled – this is triggered by the MSI for the new version. If the previous version is 7.0.200 or earlier, and if SQL has been upgraded since you installed 7.0.200 or earlier, the uninstall may fail.

See this knowledge base article.
NightWatchman Management Center fails to register with the ActiveEfficiency server if you use its FQDN or a DNS alias.When NightWatchman Management Center is installed with ActiveEfficiency server integration enabled, it will fail to register with ActiveEfficiency if you use its FQDN or a DNS alias. 
NightWatchman Management Center cannot communicate with WakeUp server (using WMI) following an installation or reinstallation.The NightWatchman Management Center console service may have cached WMI permissions associated with the target WakeUp server namespaces.Restart the console service. If its location has changed, modify the WMI permissions on the WakeUp servers. For more information, contact 1E Support.
NightWatchman Management Center cannot be uninstalled if the SQL Server is unavailableThe NightWatchman Management Center uninstallation fails if SQL Server is unavailable.Ensure the SQL Server is running and can be reached.
The NightWatchman Management Center installer allows component installation on workstation operating systems (such as Windows 7)The only valid component can be installed on a workstation is the NightWatchman console. 
Power policies are never applied to certain computers.The NightWatchman Console shows computers that have only the WakeUp Agent installed (but not the NightWatchman Agent). Power policies can be applied only to computers running the NightWatchman Agent. If you are unsure about the NightWatchman client version on a particular computer. right-click it to check its properties. 
Scheduled events may not work if a power policy contains times that are less than 3 minutes after the time of application to the client.When applying a power policy, ensure that the time for the scheduled events is more than 3 minutes after the current time. 
Maintenance window or alarm clock wake-on-LAN packets may not get sent whilst policy changes are occurring.The NightWatchman Console Service scheduler gets refreshed when power policies are created or edited. If this happens at the exact moment that a maintenance window starts or an alarm clock is scheduled, then wake-on-LAN packets may not be sent. Since these events typically occur out-of-hours, it should not normally be an issue. 
When a maintenance window end-action is set to ‘do nothing’ the computer may still go to sleep or hibernate.The Maintenance Window ‘do nothing’ action simply means that NightWatchman itself will take no action at the end of the event. If the computer was woken up from a sleep state it will be returned to that state by Windows two minutes after the end of the maintenance window, unless a user interaction occurs during this time. 
Not updating existing power policies in NightWatchman Management Center for enabling power optimization by default.With the 7.1 1E Agent, the power optimization feature is enabled by default. But existing power policies are not updated with a NightWatchman Management Center 7.1 installation. So, on a 7.1 1E Agent, when a old policy if fetched with policy refresh, it disables power optimization on the Agent. Existing policies will be refreshed on clients when they change or when the client is new. 
Upgrading NightWatchman Management Center 7.2 (or earlier versions) to 7.2.500 fails when TLS 1.0 is disabled.If TLS 1.0 is disabled in your environment and you upgrade NightWatchman Management Centre 7.2 or earlier to 7.2.500, the upgrade will fail.Enable TLS 1.0 for the upgrade and disable it post-upgrade.

Issues specific to the Reporting Website and the database

NightWatchman Management Center Report Console may not display in Internet Explorer Metro applicationsThe Internet Explorer Metro application framework imposes security restrictions on which sites may be opened. Depending on the local security configuration, it may be necessary to open the NightWatchman Management Center Report Console in the desktop version of Internet Explorer. 
Cancelling the install wizard when the installer is in the process of setting up the database may result in the database being left in an inconsistent stateBack-up any existing database before running the installer. When installing, check that all information has been entered correctly in the installation wizard before proceeding and when you have committed to the installation, allow it to complete. If for any reason you have interrupted the installation when it is processing the database, (and you have not created a database back-up prior to running the installer) contact 1E support who may be able to help with the recovery operation. 
The reports print preview in Internet Explorer does not render multiple page reports correctly.To print reports, or view them as printed, export the report using the option on the report and then print or view from a third party application. 
The repair option in the installer does not fully repair an installation.The repair option in the NightWatchman Management Center installer will only restore certain aspects of the installation (such as stored procedures and installed files). It will not re-create or re-configure IIS-based components. The best way to perform a full repair is to uninstall and then re-install NightWatchman Management Center (without selecting to drop the existing database). 
Problems associated with tier names with apostrophes.Defining tier names with apostrophes in the NightWatchman Management Center reporting Website and database causes issues when displaying reports. Avoid names with apostrophes, for example do not use Administrator’s as a building or location name. 
Report Console and Web service display errors after installation.The Report Console and Web service have been migrated to use .Net 4.5. The installation of the .Net 4.5 framework will normally register ASP.Net 4.5 with IIS. However, under certain conditions it may be necessary to re-register ASP.Net with IIS manually by running aspnet_regiis -iru from the .Net framework folder (typically at C:\Windows\Microsoft.Net\Framework[64]\v4.0.30319). For more information, please contact 1E support. 
Computers with names longer than 30 characters are no loaded from the database.Mac clients can have names of up to 64 characters in length. NightWatchman Management Center only currently supports names of up to 30 characters. 
VB Script uses DNS domain name while the database uses the NetBIOS domain name.The Import Wizard VB scripts are supplied as examples only. Map_AD_OUs_To_NWM_StagingTable.vbs uses DNS domain name while the database uses the NetBIOS domain name. You can either modify the scripts or engage 1E Consulting Services, if you need help. 
Cannot contact the NWM Web Service in if NWM server v7.1 was installed in distributed environment.In environment of Windows Server 2016 and SQL Server 2016/17 if database server is different the NWM Web Service cannot be contacted therefore issue in communication with WakeUp server and 1E Agent. 

Issues specific to NightWatchman reporting

Certain NightWatchman reports show minor discrepancies in the number of minutes reported for a day.NightWatchman discards power state transition data with a duration of less than a minute. This may result in minor discrepancies in the number of minutes reported for a day. 
Long names set for groups are truncated on report displays.NightWatchman reports are optimized for printing. Because of this, group names longer than 25 characters truncated in the reports. In graphs, they are truncated to 17 characters for the labels. 
Specific parameters selected in the cross-reference reports will not generate a report.

When using the new cross-reference reports, it is possible to make incompatible selections in the parameters. For certain combinations this results in nothing being displayed when you generate the report.

These reports rely on grouping to show the relationship between the selected parameters. Problems occur when one of the values selected for the Report For or And parameter is from the lowest tier (Department or Building) while the All value is selected for the counterpart report option and the value selected in the Show field is from the highest level tier (Region or Company). In this case the group by field cannot have a value as there is no higher tier to perform the grouping.

There are two similar scenarios that allow configurations that are not appropriate to the cross-reference report, one will generate a report and the other will not. These are:

Report forDepartment

Setting these values will result in the Group by field being unavailable. However, if you click Generate a report is created that does not use the cross referencing. Setting these values also results in the Group by field being unavailable and when you generate the report, nothing is displayed.

Report forDepartment

If you want to generate a report based on these values, do not use a cross-reference report. Use one of the standard organization and location reports.

Extrapolated values can be incorrect for computers that have not been in a group for an entire reporting period.If a computer has been in a group for less than a month (for yearly reports), the extrapolated value for a full year will assume that it consumes the same amount as for the final full month – it is likely that the calculated yearly value may under-report the likely contribution from these computers. 
Reports are not generated when you enter a single digit day or month.The date entry picker requires all single digit dates to be preceded with a zero. 
Minor discrepancies occur between monthly and daily savings reports.The savings shown in the monthly report may differ from the sum of the savings in the corresponding daily reports. The discrepancy is greatest when the power behaviour is close to baseline and is due to the daily report not handling negative savings. 
When exiting the Power Behavior wizard, the organization and location dropdowns revert to Department and Building.The Power Behavior wizard does not keep track of the previous settings and so reverts to using the lowest level tier values on exit.

Workaround: Manually change the settings back before generating a new report.
If the browser is refreshed, when creating a power behavior, it disappears.The new power behavior is not saved until the Power Behavior dialog is closed. Close the Power Behavior dialog and re-open it to refresh. 
When the back arrow is clicked multiple times when drilling into a consumption report, the Report console may show an errorThis is a bug in the Microsoft control used by the Report console. 
The times shown in WakeUp-related reports appear to be incorrectWakeUp reports display times in UTC time, and do not consider the timezone of the targeted computers. 
Data does not get loaded by default for Power consumption reports For Power consumption reports under Power Management > Consumption > Group Comparison, no data appears by default. It gets populated after clicking on Generate button. 
Shrinking of data content on 'Manage Power Behaviors' dialog box In 'Manage Power Behaviors' dialog, content window started shrinking on clicking on the table record and extra white space starts appearing. 

Issues specific to the WakeUp Server

Multiple WakeUp servers in AFR Strategy which are configured with global boundaries may compete with one another for primary and alternate agents on common subnets.By default, a WakeUp server is allocated a global boundary in AFR Strategy, which means it attempts to discover primary and alternate agents for all known subnets. If multiple WakeUp servers are configured in this manner, they will compete with one another for these agents, irrespective of the ordering of the WakeUp servers in the NightWatchman Management Console. This can cause WakeUp requests to fail. Multiple WakeUp servers installed in AFR Strategy must be correctly configured with non-overlapping boundaries. 
WakeUp server does not de-register active agents if they move out of its site boundaries.If the boundaries for a WakeUp server are modified (in the NightWatchman Management Center or in Configuration Manager), any discovered primary or alternate agents will not be de-registered and rediscovered automatically.
Workaround: Manually de-register and rediscover the agents from the 1E WakeUp console.
Uninstallation of WakeUp server installed on Configuration Manager 2012 server does not prompt to close Configuration Manager console.The uninstallation of WakeUp server without closing the Configuration Manager 2012 console could prevent the uninstallation of 1E WakeUp server Configuration Manager components. When uninstalling 1E WakeUp server, ensure that the Configuration Manager console is closed. 
Log format inconsistencies in WakeUp server logs.The log format for WakeUp server was changed in 6.1 to be compatible with the Microsoft SMS Trace format. Log data generated prior to the upgrade are not migrated to the new format. 
Upgrade reverts service to running under Local System account.When upgrading, the WakeUp service runs under the Local System account. The previous service account details are not retained during the upgrade. 
Installing for a Configuration Manager implementation that has been migrated from a 32-bit OS to a 64-bit OS results in the WakeUp extensions being placed in the wrong directory.If Configuration Manager is installed on a 32-bit OS and the system is migrated to 64-bit OS, using the Configuration Manager site repair wizard, the location for the restored Configuration Manager is it's previous location of C:\Program Files.  On 64-bit systems 32-bit code should actually reside in C:\Program Files (x86).

Installing WakeUp, a 32-bit application, correctly places its Configuration Manager extensions in the original Program Files (x86) directory. If this occurs, the work around is to manually move all the WakeUp extensions from where they get installed to C:\Program Files (x86)\Microsoft Configuration Manager\AdminUI\ to where they need to be for the restored Configuration Manager location: C:\Program Files\Microsoft Configuration Manager\AdminUI
Manual collection wake-ups do not work on certain Configuration Manager collections.Manual wake-ups for specific Configuration Manager collections whose names contain apostrophes will not result in a wake-up being sent. There is no detectable error – it fails silently. 
When agents are not found and wake-ups are sent by the local agent using subnet directed broadcast, centrally held statistics may not be accurate.When agents are not found, a local agent is instructed to send wake-ups. In such an event, statistics are not rippled back up the Configuration Manager hierarchy to the central site. This may lead to inconsistent information displayed in the WakeUp console. 
WakeUp cannot wake-up machines when accessed via remote Configuration Manager Admin Console.The WakeUp installer does not set the Remote Enable permission for Everyone on the ROOT\N1E\WakeUp WMI namespaces. This prevents any non-administrator working on a remote Configuration Manager Admin Console from using WakeUp to wake-up machines. To fix this problem you need to apply the WMI permissions manually – see the WakeUp Installation Guide. 
Incomplete wake up success reporting following on from a service restart.If the WakeUp service is restarted, results for deployments sent within 5 minutes prior to the restart will be incomplete. Additionally, some wake-up requests may fail to be sent. If this occurs, use the Configuration Manager Admin Console to manually wake-up the Configuration Manager Collection to ensure software delivery. It is not possible to retrospectively correct the reported results for the original deployment. 
Manual wake-ups initiated at the Central Site are not forwarded to the Primaries.If the Central Configuration Manager Server is unable to resolve the DNS name of the Configuration Manager Primary Servers, the WakeUp service will not be able to forward requests to the Primaries for manual wake-ups. 
WakeUp server Agent State Manager is inefficient when handling large numbers of subnetsWakeUp server Agent State Manager is inefficient when handling large numbers of subnets without clients or without a last-man-standing. As a result of this, you may get random wake-up failures as certain subnets do not discover agents before the job times out. 
WakeUp Server installer reports "Cannot contact the NMC Web Service" if reporting is enabled on the NightWatchman Management Center Configuration screen.

WakeUp Server requires an HTTP connection to the NightWatchman Management Center web service. If the NightWatchman Management Center web server was installed or reconfigured to use HTTPS only then you will see this error during installation of WakeUp Server.

WakeUp Server reporting is required to register the WakeUp Server in NightWatchman Management Center, so that NightWatchman can manage its subnets.

Add an HTTP binding, and retry the installation of WakeUp Server.

Issues specific to the Windows NightWatchman Agent

When using the command line setting shutdowntime=XX:XX, the shutdowndays setting MUST also be used.From version 6.1, when using the shutdowntime=XX:XX setting, the shutdowndays setting must also be used. 
A maintenance window set with a power down action to occur 5 minutes after the it begins may fail.If the power down action of a maintenance window is set to 5 minutes, the action may not be executed. 
Upgrading the NightWatchman client to use HTTPS instead of HTTP does not result in any change.When upgrading and changing any NightWatchman client communications from HTTP to HTTPS, you must uninstall the client first before installing it with the new settings. 
Switching between NightWatchman 32-bit and 64-bit variants.Upgrading between the 32-bit and 64-bit variants is not supported by the NightWatchman installers. To switch from one variant to the other on a 64-bit Windows OS, you must first uninstall the currently used variant and then install the other using the appropriate NightWatchman installers. 
Retryinterval setting overrides the countdownsecs value in certain conditions.When the retryinterval is set to a value less than the countdownsecs value, it overrides its set value and results in a countdown equal to the retryinterval. 
The process exception list is limited to 1000 characters.When loading a process exception list into NightWatchman, if the file length exceeds 1000 characters, any entries that occur after this limit is ignored. 
If the process exception list limit has been reached, or is close to being reached, new names added may replace the last item added.Once the process exception list has been populated to the maximum allowed size, adding a new entry from the command-line will overwrite the last entry in the registry key if the new name does not exceed the limit. This can cause unexpected behaviour as a previously added. 
The NightWatchman installer does not remember the previous installation path.If you attempt to install NightWatchman over a previous installation with a custom installation directory, instead using the custom directory, NightWatchman uses its default. Installation will take place successfully but not to the previous custom location. 
On Windows, where machines are woken by WakeUp, automatic shutdown will not abort on mouse movements or keystrokes.This only takes place when there is no user logged onto the machine. Under these circumstances, there is a small window of opportunity for NightWatchman to shut down the machine while a user is typing in their user name and password in an attempt to log on. If this occurs the solution is to turn on the machine manually and log back in. 
NightWatchman fails to shutdown a machine if the Message Options dialog is open in Outlook.NightWatchman will fail to shutdown a machine if the Microsoft Outlook Message Options dialog is open. In general this behaviour on encountering unforeseen conditions when attempting to close applications prevents data from being lost. 
Silent upgrade of NightWatchman from earlier 5.x releases may cause machine reboots without prompting.

Under certain circumstances, running NightWatchman50.msi will reboot the machine on which it’s being installed, without prompting. This appears to be related to older versions of certain antivirus and anti-malware products holding the NwmSvc.exe file open. They appear to sometimes do this immediately after the service stops, such that it is still open when Windows Installer attempts to overwrite it with the new version.

This only affects customers upgrading from a previous release of NightWatchman 5.0. Upgrading from NightWatchman 4.x is not affected. It only affects installations that use the “/qn” Windows Installer switch (this is typically the case when deploying the upgrade via SMS).

Customers experiencing this problem are advised to investigate the following options. One of these should be an acceptable workaround:

  • Turn off realtime AV scanning while the installer is running
  • Upgrade to the latest version of your installed AV software, if available
  • Stop the NightWatchman50 service before running the installer. This should give your AV software plenty of time to finish scanning the NightWatchman files

Edit the msiexec command line to include REBOOT=ReallySuppress. This will suppress the reboot. In this case, however, the computer should be rebooted as soon as possible in order to complete the installation.

NightWatchman saves Office 2007 PowerPoint blank documents.If a blank unedited PowerPoint document is open when NightWatchman shuts down a machine a backup file is created. 
Shutdown script fails to close down Outlook when it is using synchronisation.Synchronisation should be allowed to complete before NightWatchman proceeds with shutdown. A timeout exists in Outlook.vbs. This is set to 12 seconds. If synchronisation takes more time than this to complete, shutdown will fail. Increase timeout settings in Outlook.vbs. Search for string “NwmScript.TimeoutSecs”.
Unable to view original Notepad file.NightWatchman is unable to identify the full path to a Notepad text file during log off. It is possible to view the Backup File, but it is not possible to view the Original File from the NightWatchman Backup List dialog. NightWatchman will also identify this file as previously unsaved. This limitation only applies to Notepad. 
Shutdown scripts will fail for files with filenames longer than 150 characters.To fix this problem you will need to rename the file to have a name shorter than 150 characters. 
When relicensing using the installer the license key must be entered in all uppercase characters.The license key is not actually case sensitive, but the interactive installer will not accept the key unless it is entered in all CAPS. Using the command line to relicense does not require any particular case to be used. 
Power Optimization data is not calculated correctly when Windows XML files have days entries in random orderIf data in powercfg generated XML is not fetched properly (in sorted order on date) then data is not being calculated correctly. 
Power optimization currently supports single battery laptop/tabletsCurrently, the Power Optimization feature does not support more than one battery device. 
Not updating existing Power Policies in NWMC for enabling Power Optimization by default.With 7.1 1E Agent, Power Optimization feature will be ON by default. But existing Power Policies are not updated with NWMC 7.1 installation. So on a 7.1 1E Agent, when a old policy if fetched with Policy Refresh, it turns OFF Power Optimization on Agent. 
Nightwatchman Agent stuck in infinite loop after changing client system time zone.When client system time zone is changed then Nightwatchman Agent keep trying to generate powercfg reports. 
During upgrade FIPS enabled checkbox doesn't get populated as checkedIn FIPS enabled environment FIPS enabled checkbox doesn't get populated as checked during upgrade in interactive mode. However it remains as enabled. 

Issues specific to the WakeUp Agent

Dependency on ICMP.When running in Multi-Agent mode, agent detection relies on ICMP packets. WakeUp will not function if these have been blocked by a firewall or router. 
Excludesitesubnets requires CIDR network prefix information to work correctly.Excludesitesubnets entries should always include CIDR network prefix information e.g. If the prefix information is missing behavior may not be as expected. 
Changing from Multi-Agent mode to Stand-alone mode causes unexpected behavior.Changing from Multi-Agent mode to Stand-alone mode is not supported. 
WakeUp Agent discovery does not stop in some cases after a check agent if only the primary is availableWhen we don't find an Alternate Agent, the subnet never gets marked as completed, we leave it in the discovery queue and move to the next subnet. The next time the queue is processed (which is immediately) we'll go through the whole thing again. In case of AFR, ping list keeps on getting appended by local agent IP till the time it doesn't get both the agents. 

Issues specific to the Mac NightWatchman Agent

A "Shutdown Cancelled" message is being generated for every unsuccessful retry attempt.A "Shutdown Cancelled" message is generated each time NightWatchman fails to power down the machine automatically (e.g. if the user chooses to defer the power down). This is the case even if the power down later succeeds after one or more retry attempts. This may cause anomalies in the NightWatchman Management Center reports - for example, the reports may show a higher number of Shutdown Failures  than would otherwise be expected. 
Nightwatchman -g displays an incorrect value for the NightWatchman OnceOff time.The value displayed is in UTC rather than local time. 
Onceoff does not fire after changing the system date.After setting a scheduled NightWatchman event using the onceoff switch, if you change the system date to a point before the scheduled event was due to occur, when the configured time is reached the event will not take place. 
Some computers fail to shut down even when NightWatchman logoffaction is set to Force.Even when the logoffaction is set to Force NightWatchman will not shut down the computer if any of the scripted applications fail to close 
NightWatchman does not shut down computers if the scheduled time is less than 10 seconds in the futureYou need to ensure that NightWatchman has enough time to process the scheduled event before it is triggered.  You should leave at least a minute between setting the shutdown and the scheduled shutdown time.  If you need an immediate shutdown you can use the NightWatchman Shut Down Now... Status Menu item or use the shutdownnow switch on the NightWatchman Macintosh command-line. 
NightWatchman may encounter problems if the NightWatchman Shut Down Now... menu option is selected when multiple users are logged on to a computer.An intermittent problem may occur if there are multiple users logged on with Fast User Switching enabled and an Administrator selects the Shut Down Now... Status Menu item.  When the problem occurs user activity will be suspended and the user will have to force a shut down of the computer. 
Countdown Dialog shows option to shutdown later when retries have run out or have not been configuredWhen the countdown dilaog is displayed is does not currently account for the scenario where no more retries exit and will always show the user the option to retry, however this will not retry and will cancel the power down. 
During the countdown dialog, if any date/time changes occured this could lead to unexpected results.It is advisable that system settings are not changed while NightWatchman is in the process of shutdown down the machine. 
If a scheduled shutdown occurs and the exact same time that a maintenance window expires, the action taken is undefined and could be either the scheduled shutdown action or maintenance window close action.It is advisable not to have overlapping or conflicting maintenance windows, scheduled shutdowns and once off actions at the same time of day. 
OnceOff does not overriding NightWatchman Policy for High SierraOnceOff works with Mac OS X El Captain and Mac OS X Sierra but currently not with macOS High Sierra. 

Issues specific to Web WakeUp

While installing Web WakeUp, the value given for the Console Service location is not validated.When the Console Service location is not specified during installation, the installer assumes that Console Service is running on the local machine ("localhost"). If you are installing Web WakeUp on a server other than Nightwatchman Management Center server, please specify the hostname of that server during installation. 
Web WakeUp pages do not show correct error message for unauthorized users.The message displayed for unauthorized access by a user is not correct. Instead of mentioning about the "unauthorized access", it says "computer not found". 
"Wake up computer" page does not show the status of a machine when Web WakeUp is accessed from outside the network.To correctly access Web WakeUp from outside the network, the user must ensure that the ActiveX control is installed mandatorily otherwise the displayed status of the machine might be incorrect. 
Web WakeUp may fail to get status messages if older versions of the WakeUp server are still installed.If versions of the WakeUp server prior to version 6.0.500 are installed then it is possible that status messages when waking up machines could be incorrect. We highly recommend our customers upgrade all WakeUp servers when installing version 6.0.500 (and upwards) of NightWatchman Management Center. 
Uninstalling 1E Web WakeUp does not remove all components.Uninstalling 1E Web WakeUp may leave the "1E Web WakeUp, Import Authorization" SQL batch job.  This must be removed manually following the uninstall. 
The Registration page sometimes shows the message "The current machine <domain\netbios> is not registered."This may occur when the registered computer is an authorized one that was added using the AddAuthorisedMachine method in the 1E Web WakeUp Authorization Services interface without specifying the domain name. The format for the string used to identify the computer when using AddAuthorisedMachine should be DomainName\MachineName. 
The full 1E Web WakeUp website does not display or function correctly on all mobile phones.Browsing to the default 1E Web WakeUp page from a mobile device should display the default mobile page which should display and work correctly on all supported devices. Subsequently clicking the Website link attempts to display the full 1E Website pages which may not display correctly on all supported devices. There may also be update issues for the information presented on the full website related to registering and de-registering computers. 
When clicking the Remote Desktop button in the 1E Web WakeUp interface sometimes the browser asks you to select the application to open the .rdp file.The remote desktop functionality in the 1E Web WakeUp interface requires that the .rdp file association is configured correctly in the browser you are using. If this is not setup correctly you will normally be asked to select the application to open the .rdp file that controls the remote desktop connection. The application mstsc.exe in Windows\System32 is used to open .rdp files. An alternative is to double-click on the .rdp file downloaded by the browser in a Windows Explorer view. 
Searching using particular characters generates a web page error.Entering search strings containing the characters "<!" on the wake up search page causes a web page error. 
Web WakeUp does not use IISHOSTHEADERIISHOSTHEADER is a documented installer property that is recognised by the installer, however instead of using the value, WebWakeUp uses the actual text IISHOSTHEADER in the binding 
Web WakeUp incorrectly identifies DA ServerWhen a DA user logs into the WebWakeup server @ 1E the username and account are not always correct. 

Issues specific to Enterprise View

Additional Browser support.While 1E Enterprise View is fully tested and supported on the latest versions of Internet Explorer, this product has also had basic testing with the latest versions of other commonly used browsers:
  • Firefox
  • Safari
  • Opera
  • Netscape
  • Google Chrome

Enterprise View should work when these browsers are used, but we cannot offer formal support due to the large numbers of different platforms and software versions available.

When Enterprise View is upgraded the Database details in the Database Source file are not retained and have to be entered manually after the upgrade.Upgrading Enterprise View to the latest version clears the Database details in “Database Source” file and requires manual update post upgrade. For this reason we recommend that you make a backup of the “Database Source” file prior to the upgrade. 
Some tiles data is unreadable at low screen resolutions.On some tiles the text becomes unreadable when used on low resolution displays (1024 * 768) with 6 or more tiles. Either use fewer tiles or a higher resolution display to view these tiles. 
EnterpriseView continually shows a ‘waiting’ icon.This happens you cancels the Authentication required logon dialog if you connect from a non-domain-joined computer. Close and re-open the browser and supply the correct credentials when prompted. 
Enterprise View console crashes if authentication dialog is not completed within 1 minute.If the request for authentication is not completed within 1 minute, the dashboard crashes. Close and reopen the browser window and complete the authentication within the 1 minute window. 
Adding tiles when Enterprise View has a maximized tile can corrupt the dashboard display.If a tile is added while Enterprise View has a maximized tile, the new tile may display incorrectly when Enterprise View is restored to the multi-tile view. Refreshing the browser to correct the dashboard display. 
Enterprise View timeouts on large sites.Depending on the performance of the installed hardware, Enterprise View may timeout when displaying tiles on sites with more than 50,000 clients. 
Enterprise View will not load tiles containing invalid XML.Tile definition files containing invalid XML will result in an error being displayed by Enterprise View and the tile will not be loaded. The most common cause of invalid XML is not escaping reserved XML characters.