2024:Grooper Infrastructure - Revision history

Dgreenwood: Dgreenwood moved page 2024:Grooper Infrastructure (Concept) to 2024:Grooper Infrastructure without leaving a redirect

2026-01-08T17:27:02Z

Dgreenwood moved page 2024:Grooper Infrastructure (Concept) to 2024:Grooper Infrastructure without leaving a redirect

← Older revision	Revision as of 12:27, 8 January 2026
(No difference)

Dgreenwood at 17:53, 10 July 2025

2025-07-10T17:53:38Z

← Older revision		Revision as of 12:53, 10 July 2025
Line 105:		Line 105:
	\|		\|
	Required for checking user's group membership		Required for checking user's group membership
	* The user installing the Grooper web client must also have the capability to query the domain in order to enter the credentials for the Grooper app pool identity.
	\|-		\|-
	\|		\|

Dgreenwood: /* Grooper Service Users */

2025-07-10T17:51:09Z

Grooper Service Users

← Older revision		Revision as of 12:51, 10 July 2025
Line 160:		Line 160:
	==== Grooper Service Users ====		==== Grooper Service Users ====

	The Grooper ~~Service user account must have the following~~ permissions:		The Activity Processing service automates task processing for Batches in Grooper. They need a minimum set of permissions in order to execute tasks.

			{\|class="wikitable"
			\|
			'''Permission'''
			\|
			'''Type'''
			\|
			'''Reason'''
			\|-
			\|
			Users
			\|
			Local
			\|
			Run the installed applications (Grooper)
			\|-
			\|
	File store access		File store access
	* Type: NTFS\Share		\|
	* Reason: Read and write access to the Grooper file store location		NTFS\Share
			\|
			Read and write access to the Grooper file store location
			\|-
			\|
	Database access		Database access
	* Type: SQL		\|
	* Reason: Read and write access to the Grooper database		SQL
			\|
			Read and write access to the Grooper database
			\|-
			\|
			Logon As Service
			\|
			Local Security Policy
			\|
			Run services installed via Grooper Command Console
			\|}

	~~Logon As Service~~		Other Grooper services may require additional permissions. For example, an Import Watcher's user may need access to directories used for importing file content.
	* Type: Local Security Policy
	* Reason: Run services ~~installed via Grooper Command Console~~

	=== Client Computer ===		=== Client Computer ===

Dgreenwood: /* Grooper App Pool User */

2025-07-10T17:49:58Z

Grooper App Pool User

← Older revision		Revision as of 12:49, 10 July 2025
Line 88:		Line 88:

	{\|class="wikitable"		{\|class="wikitable"
	\|~~style="width:20%"~~\|		\|-
			\|
	'''Permission'''		'''Permission'''
	~~\|style="width:20%"~~\|		\|
	'''Type'''		'''Type'''
	~~\|style="width:30%"~~\|		\|
	'''Reason'''		'''Reason'''
	\|~~style~~=~~"width:30%"~~\|		\|-
	'''Required?'''		\|colspan=3\|
			'''''Always Required'''''
	\|-		\|-
	\|		\|
Line 104:		Line 106:
	Required for checking user's group membership		Required for checking user's group membership
	* The user installing the Grooper web client must also have the capability to query the domain in order to enter the credentials for the Grooper app pool identity.		* The user installing the Grooper web client must also have the capability to query the domain in order to enter the credentials for the Grooper app pool identity.
	\|
	~~Yes~~
	\|-		\|-
	\|		\|
Line 113:		Line 113:
	\|		\|
	Run the installed applications (Grooper)		Run the installed applications (Grooper)
	\|
	~~Yes~~
	\|-
	\|
	~~C:\Release~~
	\|
	~~Local\NTFS~~
	\|
	~~Run MsBuild for compiling Object Libraries in Grooper~~
	\|
	~~Yes~~
	\|-		\|-
	\|		\|
Line 131:		Line 120:
	\|		\|
	Read and write access to the Grooper file store location		Read and write access to the Grooper file store location
	\|
	~~Yes~~
	\|-		\|-
	\|		\|
Line 140:		Line 127:
	\|		\|
	Read and write access to the Grooper database		Read and write access to the Grooper database
			\|-
			\|colspan=3\|
			'''''Conditionally Required'''''
			\|-
	\|		\|
	~~Yes~~		C:\Release
			\|
			Local\NTFS
			\|
			Run MsBuild for compiling Object Libraries and custom scripts in Grooper
			* Required when implementing Object Libraries or other scripting.
	\|-		\|-
	\|		\|
Line 149:		Line 145:
	\|		\|
	Run services installed via Grooper Command Console		Run services installed via Grooper Command Console
	\|		* Required if also using the application pool identity as a service account running Grooper services
	~~Optional~~
	* Required if also using the application pool identity as ~~the~~ service account running Grooper services
	\|}		\|}

Dgreenwood: /* Grooper Processing Servers */

2025-07-10T13:46:23Z

Grooper Processing Servers

@@ Line 163: / Line 163: @@
 **<li class="attn-bullet"> Be aware this is a ''minimum''.  High volume scenarios will need more cores to process content efficiently.
 * The port for licensing is 13900 by default.
 === Client Computer ===

Dgreenwood: /* The Grooper Web Server */

2025-07-10T13:44:18Z

The Grooper Web Server

@@ Line 78: / Line 78: @@
 **<li class="attn-bullet">'''''BE AWARE:''''' The Grooper application (GrooperInstall_##.##.####.exe) ''must'' be installed on this server.  The Grooper Web Client application (GrooperWebClient_##.##.####.exe) leverages Grooper DLLs to function.
 **<li class="fyi-bullet"> ''For smaller installs, the Grooper Web Server and Grooper SQL Server may be the same machine.  For larger installs, this is not recommended. We recommend a dedicated server for the Grooper Web Server.''
 === Grooper Processing Servers ===

Dgreenwood: /* Windows 11, 2025 and IOT Support */

2025-07-10T13:40:24Z

Windows 11, 2025 and IOT Support

← Older revision		Revision as of 08:40, 10 July 2025
Line 126:		Line 126:
	* '''ReportViewer'''		* '''ReportViewer'''
	: Used for viewing built in '''Grooper Reports''', which uses a Microsoft Reporting framework.		: Used for viewing built in '''Grooper Reports''', which uses a Microsoft Reporting framework.

	~~==== Windows 11, 2025 and IOT Support ====~~

	Windows 11, Windows Server 2025 and Windows IOT are not officially supported. Grooper installations are known to work on Windows 11 machines in most cases. However, these configurations are not officially supported at this time by the Grooper Development Team.

	== About thread allocation for Grooper services ==		== About thread allocation for Grooper services ==

Dgreenwood: Dgreenwood moved page Grooper Infrastructure (Concept) to 2024:Grooper Infrastructure (Concept)

2025-03-03T19:01:34Z

Dgreenwood moved page Grooper Infrastructure (Concept) to 2024:Grooper Infrastructure (Concept)

← Older revision	Revision as of 14:01, 3 March 2025
(No difference)

Dgreenwood: /* Windows 11 Support */

2025-02-04T23:06:31Z

Windows 11 Support

← Older revision		Revision as of 18:06, 4 February 2025
Line 127:		Line 127:
	: Used for viewing built in '''Grooper Reports''', which uses a Microsoft Reporting framework.		: Used for viewing built in '''Grooper Reports''', which uses a Microsoft Reporting framework.

	==== Windows 11 Support ====		==== Windows 11, 2025 and IOT Support ====

	Windows 11 is not officially supported. Grooper installations are known to work on Windows 11 machines in most cases. However, ~~this configuration is~~ not officially supported at this time by the Grooper Development Team.		Windows 11, Windows Server 2025 and Windows IOT are not officially supported. Grooper installations are known to work on Windows 11 machines in most cases. However, these configurations are not officially supported at this time by the Grooper Development Team.

	== About thread allocation for Grooper services ==		== About thread allocation for Grooper services ==

Dgreenwood: /* Windows Prerequisites */

2025-02-04T23:04:53Z

Windows Prerequisites

← Older revision		Revision as of 18:04, 4 February 2025
Line 126:		Line 126:
	* '''ReportViewer'''		* '''ReportViewer'''
	: Used for viewing built in '''Grooper Reports''', which uses a Microsoft Reporting framework.		: Used for viewing built in '''Grooper Reports''', which uses a Microsoft Reporting framework.

			==== Windows 11 Support ====

			Windows 11 is not officially supported. Grooper installations are known to work on Windows 11 machines in most cases. However, this configuration is not officially supported at this time by the Grooper Development Team.

	== About thread allocation for Grooper services ==		== About thread allocation for Grooper services ==