Web WakeUp server configuration

Administrator configurable options for the NWM.ServiceHost.exe.config file are detailed below. After changing these settings, you will need to restart the NightWatchman Console Service and perform an IIS reset, for them to take effect.

...
<appSettings>
    ...
    <add key="MaxMachines" value="100"/>
    ...
</appSettings>
...

...
<appSettings>
    ...
    <add key="AuthorisedMachineModule" 
        value="N1E.WakeUp.Web.AuthorisedMachineModule.dll"/>
    ...
    </appSettings>
...

...
<appSettings>
    ...
    <add key="AuthorisedMachineModule" 
        value=""/>
    ...
    </appSettings>
...

Administrator configurable options for the Web.config file are detailed as follows. After changing these settings, you will need to perform an IIS reset, for them to take effect.

...
<appSettings>
...
<add key="UseActiveX" value="False"/>
...
</appSettings>
...

...
<appSettings>
...
<add key="EnableRDP" value="False"/>
...
</appSettings>
...

...
<appSettings>
...
<add key="EnableStatus" value="False"/>
...
</appSettings>
...

...
<bindings>
...
    <netTcpBinding>
...
        <binding name="NetTcpBinding_MachineSearchService"
            ...
            maxBufferSize="131072"
            maxReceivedMessageSize="131072"
            ...  
            />
...
    </netTcpBinding>
...
</bindings>
...

...
<bindings>
...
    <netTcpBinding>
...
        <binding name="NetTcpBinding_MachineSearchServiceBindingConfiguration"
            ...
            maxBufferSize="131072"
            maxReceivedMessageSize="131072"
            ...  
            />
...
    </netTcpBinding>
...
</bindings>
...

This section describes how to configure Web WakeUp to allow mobile devices to wake computers, the security considerations that should be taken into account and gives examples of the mobile interface.

Website configuration

There are three scenarios that allow mobile devices to use Web WakeUp. In all three cases the Web Wakeup website is hosted in the company's network:

1. The Web WakeUp website is published on a publicly available server.

2. The mobile user connects to the company network using VPN then there should be VPN client installed on the mobile phones.

3. The mobile user located in the office is able to connect to the office network using a wireless connection.

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:

1. It is not possible to verify the mobile user when they connect to the Web WakeUp website.

2. It is not possible to constrain the computers that a mobile user can awaken.

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 mobile interface

The Web WakeUp website has a mobile interface designed to fit onto the smaller screens on mobile devices. This interface only supports the Wake Up Computer page.

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

• On supported devices, after attempting to wake a computer, the wake by name screen will provide feedback on whether the named computer has been awoken.

• On non-supported devices to check whether a computer has been awoken you need to hit the wake up button again after a suitable time.

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:

• blackberry#4.7

• blackberry#4.6

• iPhone

• iPad

• windows phone os 7.0

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.

The iPhone app

There is an interface to Web WakeUp as an iPhone or iPad application, available separately from the Apple Store. This application provides access to all the pages of the Web WakeUp website. An example of the main Web WakeUp screen on the iPhone .

If you are an administrator and have defined a publicly available website for Web WakeUp you may be contacted by iPhone application users requesting the name of the server hosting the Web WakeUp website, the account and password to be used to access the server and the protocol being used for the site.

These details are likely to vary depending on how you have configured the site, but the name of the server hosting the Web WakeUp website must be entered into the iPhone application without using http:\\ or https:\\ prefixes.

During installation, a file called rdp.template is created in the rdp subfolder of the Web WakeUp installation folder. This file is used to control the RDP settings such as the screen resolution etc.

To view the default contents of rdp.template, expand the link:

screen mode id:i:1
desktopwidth:i:800
desktopheight:i:600
session bpp:i:16
auto connect:i:1
full address:s:<ADDRESS>
compression:i:1
keyboardhook:i:2
audiomode:i:2
redirectdrives:i:0
redirectprinters:i:0
redirectcomports:i:0
redirectsmartcards:i:0
displayconnectionbar:i:1
username:s:<USERNAME>
domain:s:<DOMAIN>
alternate shell:s:
shell working directory:s:
disable wallpaper:i:1
disable full window drag:i:1
disable menu anims:i:1
disable themes:i:1
bitmapcachepersistenable:i:1

Most of these correspond to the standard parameters for controlling RDP and may be changed by the administrator. The exceptions are <ADDRESS>, <USERNAME> and <DOMAIN>. These should not be changed as they are update by Web Wakeup.

It is possible to modify the images for the Web WakeUp website to your corporation's branding requirements.

Currently, branding is done is through modifying the images that form the backgrounds to various parts of the Web WakeUp website. Modifications to the structure of the pages is not supported. Replacement images must have exactly the same dimensions as the originals.

The following Jpeg images are found in the %installdir%\Website\Imagesdirectory:

Once the images have been replaced, browsing the website or refreshing the browser displays the new images.

The Web WakeUp tables added to the Agility Framework database are also supplied with an SQL Server Agent job that can be used to populate the tbWWU_Authorised_UserMachines table from a .csv file.

The SQL Server Agent job is called Web WakeUp, Import Authorisation. Before running it, you must first create the source authorization input file and set the SQL Server Agent job to use the file.

The authorization input file format

The input file for the Web WakeUp, Import Authorisation SQL Server Agent job is a .csv format file where each line in the file contains the following information in the following format:

• <User ID > is the user whose authorization is being set. When using Windows authentication <UserID> should be in the format DomainName\UserName.

• <Computer Name> is the netBIOS name of the computer the <UserID> is allowed to wake.

• <Domain Name> is the domain the computer is running on.

The example below is an authorization input file with three entries:

Revised 9/4/2009 ESA for WWU implementation,,
ACME\rachel,devwks1,ACME
ACME\rachel,devwks2,ACME
ACME\joey,saleswks2,ACME

Although the first line must also have three comma separated elements, it is treated as a header line and ignored. Notice how the first line, as it is ignored by the import process, can be used as a place to store notes on the file.

Setting the authorization input file

To set the SQL Server Agent job to reference a specific authorization file you need to modify the SQL Server Agent job's Import CSV step in SQL. The command-line for this step is:

EXEC [dbo].[spWWU_Import_Authorised_UserMachines] 'C:\CN-DN-PU.csv'

Change the default file referenced at the end of the command-line to point to your file. For example, to set the SQL Server Agent job Web WakeUp, Import Authorisation to use C:\1EWWU\ACME\acme.csv:

EXEC [dbo].[spWWU_Import_Authorised_UserMachines] 'C:\1EWWU\ACME\acme.csv'

To edit this job in SQL Server Management Studio:

1. Navigate to SQL Server Agent/Jobs.

2. Right-click 1E Web WakeUp, Import Authorisation and choose Properties from the context menu to open the Job Properties - 1E Web WakeUp, Import Authorisation dialog.

3. In the Select a page column on the left, choose Steps to display the Job Step List in the right pane.

4. Select the only job step Import CSV and click the Edit button to display the Job Setp Properties - Import CSV dialog.

5. In the Command: field, edit the currently displayed SQL command from:

   Copy

   EXEC [dbo].[spWWU_Import_Authorised_UserMachines] 'C:\CN-DN-PU.csv' 

   to (in order to point to your particular authorization file):

   Copy

   EXEC [dbo].[spWWU_Import_Authorised_UserMachines] 'C:\1EWWU\ACME\acme.csv'

6. Click OK to save your changes and close the Job Step Properties - Import CSV dialog.

7. Click OK to close the Job Properties - 1E Web WakeUp, Import Authorisation dialog.

8. You can then execute the modified job to import the specified data:

   1. Right-click the SQL Server Agent/Jobs/1E Web WakeUp, Import Authorisation node and select Start Job at Step... item from the context menu.

   2. The job will start running. In the Start Jobs - <ServerName> dialog confirm that the Status returned at the end is Success.

   3. Click Close to complete the job execution.

9. After execution open the table tbWWU_Authorised_UserMachines to confirm the results are as expected.

When the SQL Server Agent job is run

The following steps shows what happens when the SQL Server Agent job is run:

1. Existing entries in the authorization table are removed, except for 'power user' type entries where the computer name is set to "*".

2. The new entries from the input file are added to the authorization table.

You can invoke Web WakeUp to wake-up specific computers from your company portal site using the Web WakeUp site URL.

<SiteHost>/WebWakeUp/WakeUpByName.aspx?Machine=<Domain\ComputerName>

<SiteHost>/WebWakeUp/MobileWakeUp.aspx?Machine=<Domain\ComputerName>