NightWatchman Enterprise 7.3

Due to the nature of the mobile devices it is not possible to check the credentials of the mobile user logged on to the Web WakeUp website. This has two direct consequences:

For these reasons we only recommend that you avoid using configuration scenario 1 above and only use configuration scenarios 2 and 3. This allows security to be managed via VPN or wireless connection to ensure that only mobile users with company network access are able to browse to the Web WakeUp website.

The interface on mobile devices differs slightly depending on whether it is on the web.config list of supported devices.

To add a device to the list of supported devices the browser on the device must be Javascript enabled and support DHTML. You then edit the web.config file located in:

C:\Program Files\1E\WebWakeUp\Website

This XML file configures various aspects of the way that Web WakeUp runs.

To add a mobile device, edit the comma-delimited ValidMobileOSVersions key in the <appsettings> section to include one or more of the following text strings:

The # in blackberry indicates specific support for versions 4.7 and 4.6, while Windows phone OS is version 7.0 and the for the iPhone and iPad – any version.

<appSettings>
  <add key="CustomErrorPage" value="GenericErrorPage.aspx" />
  <add key="PingTimeoutPeriod" value="20000" />
  <add key="MaxPingRetry" value="10" />
  <add key="UseActiveX" value="False"/>
  <add key="EnableRDP" value="False"/>
  <add key="RDPTempDir" value="C:\ProgramData\1E\Web.WakeUp\RDP\"/>
  <add key="ActiveXVersion" value="1.7.0.96"/>
  <add key="AuthenticationModule" value=""/>
  <add key="EnableStatus" value="true" />
  <add key="ValidMobileOSVersions" value="blackberry#4.7, blackberry#4.6, iphone, ipad, windows phone os 7.0"/>
</appSettings>

Unlike other settings in the web.settings file, after changing the ValidMobileOSVersions parameter there is no need to perform an IIS reset before the changes take effect.