Вы находитесь на странице: 1из 1

WHO WE ARE FEATURES SCREENSHOTS SERVICES NEWS CONTACT US DOWNLOAD DOCS FORUM

Installation Search for:

Search …

Installation Search

The Display Monkey digital signage solution consist of two ASP.Net web applications,
Management of content and settings (DisplayMonkey_Management or DMM) and
Docs
Presentation (DisplayMonkey or DMP) for rendering content on Display’s. Content and Getting Started
settings are stored in MS-SQL server database. Display Monkey Management
Dashboard
Pre Requisites Currently Displayed
IIS – Internet Information Services Display
IIS with the following server roles/features needs to be installed and con gured:
Change Displayed
ASP.Net 4.5
Frames
Windows Authentication
Re-order Frames

Microsoft Windows Designated Locations


The following versions of MS-Windows are supported: Media Alternatives
Windows 7 Media
Windows 10 Setup
Windows Server 2008 R2 Organization
Windows Server 2008 Levels
Windows Server 2012 Location
Windows Server 2012 R2 Canvas
Many features in Display Monkey (1.3.4.162) has been con rmed not to be working Panels
correctly on Windows 2016 (IIS 10 and ASP.Net 4.6.x). Other versions of Windows may Other
work but are yet to be veri ed. Application Settings
Report Server Accounts
Microsoft SQL Server
The following versions of MS-SQL are supported: Microsoft Exchange

SQL Server 2008 Accounts

SQL Server 2008 R2 Microsoft Azure Account

SQL Server 2012 Open Authorization

SQL Server 2012 Express (OAuth) accounts

SQL Server 2014 Frame Templates

SQL Server 2014 Express Error Messages


Display Monkey Presentation
Step 1 | Copy Applications Register
Unzip the downloaded le and copy the two folders DisplayMonkey and Look and Feel
DisplayMonkey_Management to a desired location e.g. C:\inetpub\wwwroot. Set Installation
appropriate folder permissions as needed. Upgrade from Previous Version

Step 2 | Create Applications


From the IIS management console create a new application pool that is using .Net version Recent Posts
4.x. We recommend to use the built-in NT AUTHORITY\Network Service or a Domain New Maintenance Release
Account as the Application Pool Identity (User). March 6, 2019
New Feature Release
Right click on the folder under Default Web Site copied in step 1 and select Convert to March 21, 2018
Application and select the newly created application pool. Repeat the Convert to Application New Maintenance Release
step for both folders (DisplayMonkey and DisplayMonkey_Management). For the August 21, 2017
DisplayMonkey_Management application enable Windows Authentication under IIS – New Maintenance Release
Authentication May 11, 2017
New Feature Release
May 9, 2017

Create Application Application Pool

Step 3 | Create Database


From SQL Management Studio create a new database with the name DisplayMonkey.
Create a new SQL user named DisplayMonkey and set the Membership to db_owner. Open
the SQL script named install.sql found in the subfolder SQL in the downloaded le and run
it. To also install demo data run SQL script named demo_data.sql.

Step 4 | Con gure Database Access


From Windows explorer locate and open (using notepad or equivalent) the Display
Monkey Presentation web.con g le located in the root folder (e.g.
C:\inetpub\wwwroot\DisplayMonkey) and change Data Source to the SQL server name
where the Display Monkey database was created on in step 3. Change User ID and
Password in accordance with SQL user created in step 2.

Adjust the same values in the Display Monkey Management web.con g le located in the
root folder (e.g. C:\inetpub\wwwroot\DisplayMonkey_Management).

If a different database name was given in step 3 please aslo adjust Initial Catalog in both
web.con g les.

Web Con g

Post Installation
If the Display Monkey presentation application (e.g. http://DisplayMonkey) is hosted on a
different server (or not in a root folder) than the Management application (e.g.
http://DisplayMonkey_Managment) the relative or absolut path to the Presentation
application should be entered. See page Application Settings for more information

Multi Presentation Server Environment


When using Display Monkey in a wide area network (WAN) we recommend to deploy
multiple presentation applications that all are connected to a single instance of the
Display Monkey Management application. This will allow for presentations to be cached
and rendered locally while management of content, settings and displays are done at a
single host.

Since passwords are encrypted additional steps needs to be taken to grant access to the
RSA Key Container when Display Monkey Presentation (DMP) application is deployed on a
different machine to Display Monkey Management (DMM).

Start by navigating to Setup – Other – Report Server Accounts (or Microsoft Exchange
Accounts) in DMM. Setup at least account with user name and password. This will create
the RSA Key Container on the machine running DMM. Export the container using the
script exportDmRsaKey.bat found in the installation folder. Please note that le path
found in the script may have to be adjusted depending on local environment.

Import the exported RSA Key Container to each instance of DMP that is installed using the
script importDmRsaKey.bat. Please note that le path found in the script may have to be
adjusted depending on local environment.

If different Application Pool Identities are used between DMM and DMP accesses also
needs to be granted to the imported RSA Key Container. The script grantDmRsaKey.bat can
be used to grant access to a speci c user (Identity). Please note that le path found in the
script may have to be adjusted depending on local environment.

For more information on RSA Key Containers see https://msdn.microsoft.com/en-


us/library/yxw286t2(VS.80).aspx

Вам также может понравиться