Minimum User Requirements for SiteRemote Server Database Backups

When using the database backup options of the SiteRemote Server Configuration Tool the resulting job will be added to the Windows Task Scheduler. The job requires a user account, the name of which you have to state in the Server Configuration Tool (using [server name or domain name]\[user name], e.g. SRServer\Backupuser).

In order for the job to run successfully the user you choose needs a minimum set of specific rights.

If you use a local SQL database (for the SiteRemote database) and you are not using the SQL Server Management Studio for backups, the user for the SiteRemote database backup needs db_owner rights on the SiteRemote SQL database (the default name of the database is SiteRemoteBackEndServer). Note that there are no special requirements for the user regarding the Mongo DB database used for the SiteCaster part of the server.

The user also needs read and execute rights for the Data and Mongo folders and their subfolders of the SiteRemote directory (by default C:\Program Files (x86)\PROVISIO\SiteRemote\Data and C:\Program Files (x86)\PROVISIO\SiteRemote\Mongo).

Of course the user needs write rights for the backup destination folder (by default C:\Users\Public\Documents\SiteRemoteBackups).

Finally, because the job is added as a Windows task, the user needs the Windows user right to log on as a batch job.


Note that the basics described above also apply to the new SiteKiosk Online Server. Paths and names need to be adjusted.

Using Different User Agents for Websites in SiteKiosk Windows Chrome Browser

For compatibility reasons or identification purposes it can be useful or even necessary to modify the user agent of the browser. You can do that for the browser as a whole in the configuration of SiteKiosk under Start Page & Browser -> Customize.

Replacing the whole default user agent string of SiteKiosk instead of just adding something to it is described here (Chrome) and here (IE).

But a modification that helps on one website can lead to problems on another website. So it can be useful to edit the user agent only for certain pages while on others the default user agent is used. You can do this with SiteKiosk Windows by editing the configuration file of SiteKiosk with an editor like Notepad. Look for urlSpecificUserAgents in the file and create entries for your URL(s). There are two options, you can either just add something to the default user agent of SiteKiosk or you can fully replace the user agent. 

This is how adding something to the default user agent for a specific URL looks like (as you can see, wildcards (*) are supported):

"url": "*whatsmyuseragent.org/*",
"userAgent": {
"add": "SiteKiosk Windows"
}

In this example SiteKiosk Windows is added to the default user agent for the specified page, while other pages receive the default user agent.

You can have as much different specific user agents as you need. This is how more than one looks like:

"urlSpecificUserAgents": [
{
  "url": "*.google.*",
  "userAgent": {
	"add": "Edg/$(ChromiumVersion)"
  },
  "url": "*whatsmyuseragent.org/*",
  "userAgent": {
	"add": "SiteKiosk Windows"
  }
}
],

The option to replace the full user agent string with a custom one looks like this:

"url": "*whatsmyuseragent.org/*",
"userAgent": {
"full": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36 Edg/89.0.774.76"
}

This example uses the user agent string of Edge (Chromium engine).

Note that using a user agent that mimmicks another browser can lead to display problems with a webpage. Always test the settings before using them in your production environment.