Jump to content

Marius

Administrators
  • Posts

    1272
  • Joined

  • Last visited

Posts posted by Marius

  1. Pulseway allows you to restrict access for Dashboard and Web Application by IP Address so only designated IPs will be able to connect.

    To add a restriction start Pulseway on a monitored PC and click "Change Account Details".
    On the account detail you can add IP addresses that are allowed to access either Dashboard or Web App or both.

  2. Hi Daniele,

    Thank you for your support, really glad you find our solution useful.

    You can get a 25 PC's subscription and you can upgrade later to 50 PC's by getting another 25 PC's subscription. If you know that you are going to need 45 it's better to get the 50 PC's subscription from the start.

    Marius

  3. In possible in the Active Directory module show all user logged in the Domain ¿? Not only the local session active session in the Server. Will be really great add.

    Another add will be a possibility to see all shares on the Server and the active connection, and the option to disconnect any active session.

    Is posible to show in the notification when a user is logged in a server, the IP address from the conection is made ?

    I have a request, but is for a PC Dashboard app. Is possible you make a popup details info menu like IPad app when press or click on a Server or PC ¿? and the possibility to organize by group like the web app ¿?

    I am planning to visualize your app in a 46” touchscreen and if you PC dashboard have this feature will be fantastic!!!

    Thank you for your support. We plan to enhance the AD module and will add the logged in users.

    Shares management is another one that we plan to add.

    The external IP - we are investigating this to see how to implement.

    We started the dashboard development for viewing the computer details and sending commands - should be available in a version or two.

    Please send us a picture with the dashboard on the big screen :)

  4. Server Requirements

    • Windows Server 2008 R2, 2012 or 2012 R2
    • 2+ GB RAM
    • .NET Framework 4.0 (or higher)
    • SQL Server 2008/R2, 2012 or 2014 (Express Edition or higher)
    • 1 static IP address
    • 1 SSL Certificate or a Wildcard Certificate or SAN Certificate (self-signed certificates are not recommended)

    Required steps before installing the Pulseway Enterprise Server

    • Obtain the SSL certificate for pulseway.<yourdomainname>
    • Add a DNS entry for pulseway.<yourdomainname> -> Public IP address
    • Install the SSL certificate in IIS
    • Install SQL Server 2008/R2, 2012 or 2014 (Express Edition or higher) on your server

    Note: Pulseway Enterprise Server will also work on an Amazon EC2 small instance.

  5. Pulseway supports Wake on LAN and Wake on WAN over Internet.

    The mobile application will send a magic packet in LAN while on WiFi.
    As well, our cloud servers will send the same magic packet to the public IP address on UDP 9 (you can change the port number and assign a different port number for each computer using the Pulseway app installed on your PC, go to System->Wake on WAN over Internet, default is 9).

    Please make sure that the router forwards those packets in the LAN and that the PC supports Wake on LAN (check BIOS and network interface settings).

    The only limitation at the moment using Wake on WAN over Internet occurs when our cloud servers have the last public IP used by your computer and your public IP changes. The magic packet will be sent to the last known public IP and will fail to wake the computer. We are planning to solve this problem in the future using a different method.

  6. Most likely it's not a BIOS issue. What Operating System do you have on that computer?

    We are using performance counters for reading the total CPU usage, are the performance counters working for you?

  7. Pulseway can be installed on Windows 2008 R2 Server Core Installation.

    Before installing Pulseway you will need to download and install .NET Framework 4 for Server Core from:

    http://www.microsoft...s.aspx?id=22833

    Instructions

    • Important: Make sure that your computer has the latest Windows service pack and critical updates. To find security updates, visit Windows Update.
    • If you are installing on Windows 2008 Server R2 on Server Core, you need to install Windows 2008 Server R2 SP1 and follow the instructions below before you install .NET Framework 4
      • Turn on WoW64: Start /w ocsetup ServerCore-WOW64
      • Turn on .NET 2.0 layer: Start /w ocsetup NetFx2-ServerCore
      • Turn on .NET 2.0 layer for WoW64: Start /w ocsetup NetFx2-ServerCore-WOW64
    • On this page, locate the Download button and then click it to start the download.
    • To save the download to your computer so that you can install it later, click Save.
    • To cancel the download, click Cancel.
    • After installing .NET Framework 4 on Windows 2008 R2 SP1 Server Core, it is highly recommended you install critical .NET Framework 4 updates available on Windows Update.

    System requirements

    Supported Operating Systems: Windows Server 2008 R2 SP1

    •  
    • Windows Server 2008 R2 SP1 Server Core or later
    • Supported Architectures:
    • x64
    • Hardware Requirements:
    • Recommended Minimum: Recommended Minimum: Single processor with 1.4 GHz (x64 processor) or 1.3GHz (Dual Core) with 512 MB RAM or more
    • Minimum disk space: 2 GB (32 GB or greater required for OS)
×
×
  • Create New...