The user account “SSAdministrator” is the service account used to proxy all document and data access requests to individual clients. This account is used when authorizing access for most Square 9 Windows Services, in addition to acting as the Application Pool user for both GlobalSearch and GlobalCapture. When GlobalSearch is installed it creates the SSAdministrator account and requires that the user performing the installation create a password. While a complex password is not required by GlobalSearch, it must comply with your system’s password requirements for the application to work properly. The password is case sensitive.
Change Password in Application Pools
The Application Pool identity of the GlobalSearch and GlobalCapture application pool needs to be updated to reflect the new password.
Open the Microsoft Internet Information Services Manager (IIS) on the GlobalSearch server.
Expand the server to see the Application Pools folder.
Within the Application Pools folder, right-click on the SmartSearch4 application pool and select Advanced Settings from the context menu.
In the Advanced Settings window, under the Process Model section, click on the Identity tab.
To edit the Identity, click the More (three dots) button.
In the Application Pool Identity window, select Custom account and click Set.
In the Set Credentials window that appears, enter the credentials of the local or domain SSAdministrator:
Enter the local or domain username of the SSAdministrator in the User name text box.
Enter the password of the SSAdministrator in the Password text box.
Confirm the password in the Confirm password text box. Your domain location will depend on where you want your users to be located and authenticated from. For local installations, users will be on the Local System, therefore you will need to use the local SSAdministrator. For domain installations, users will be on the domain in the Active Directory therefore, you will need to use the domain SSAdministrator account.
In the Advanced Settings, Application Pool Identity, and Set Credentials windows, click OK.
If the SmartSearch4 application pool is not currently running, right-click on it to select it and then in the context menu, click Start.
Repeat steps 3 through 9 for the GlobalCapture application pool.
Once the identity has been updated, make sure the application pool is running. If it’s not, right-click on the pool and select Start from the context menu.
Update Services
Since GlobalSearch version 4.2, the Service Console has been released as an efficient way to update all GlobalSearch services, although the services can still be accessed through the normal Windows Service menu. All GlobalSearch services must be updated from the Services Console for permissions to be properly applied; the ssContentSearch service is the only exception. To set the ssContentSearch service permissions, please use the procedure in the “Change the SSAdministrator Password#Update the ssContentSearch Service” section below. If the services do not update from Service Console on your system you will need to update the SSAdministrator password manually on each service.
Run the Service Console
Note that if you are using GlobalCapture version 2.3 or lower you will still have to run the C:\GetSmart\GC_ServiceConsole\ServiceConsole.exe in addition to the updated service console if your GlobalSearch is 6.1+
Right-click on the Service Console and click Run as an Administrator. The console is located C:\GetSmart, or wherever the GetSmart directory is stored.
Once the console is open, to stop all the services, click Stop All.
Enter in the SSAdministrator or the service user in User text box and the corresponding password in the Password and Confirm text boxes.
Click Set Services. A minute wait time is required before you can restart the services.
Once a minute has passed, click Start All. The services will restart one by one.
Once all the services have been started, close the service console.
GlobalSearch 6.1+, GlobalCapture 2.4+
As of 6.1.x Service Console is located in a different folder path.
You can search for Service Console in the Windows menu instead of running the file directly.
Service console also has the ability in 6.1 and above to update the Authentication Server. Which you don't need to do for a password change.
GlobalCapture Service Console stand alone.
Some customers have stand alone GlobalCapture. Meaning you only have GlobalCapture. Your service console is located in a different folder.
C:\GetSmart\GC_ServiceConsole ServiceConsole.exe
Update the ssContentSearch Service
Launch the Windows Service menu. This can be reached by running Services.msc, or it can be found under your Administrative Tools.
Right-click on the ssContentSearch service and go to Properties.
In ssContentSearch Properties, on the Log On tab, change the logon user in the This account text box.
Click Browse and select the SSAdministrator. The user you will use should be the same user entered in the Service Console and the Application Pools. Verify that the domain name is consistent with the other applications.
Enter the updated password in the Password and Confirm password text boxes and click OK.
In the Windows Service Menu, verify any other service running as the SSAdministrator has been updated as well. Both the S9 GlobalAction and the GlobalCapture_1 services will most likely stay running as Local System. This is normal and they can function without issue as Local System. Depending on your installation, these services may have been changed to run as the SSAdministrator user instead. If so, you will need to update them using steps 2 through 5.
Update GlobalCapture Portals
The GlobalCapture Portals are the last section that will need to be updated.
Browse to the GlobalCapture menu.
Once signed in, click the Manage (wrench) icon.
From the menu on the left, select Portals. By default, there are three portals installed: Batch Portal, Analytics Portal, and Square9 API Portal. All three portals run off the SSAdministrator or service user. If you have additional portals, all of them will need to be updated as well.
Click on the More Options () icon and select Edit.
Verify that the SSAdministrator is listed as either the domain or local user, depending on your installation. If need be, change the username to correspond with the user used in the previous “Application Pools” and “Services” steps.
Enter in the new password in the Password text box.
To finish, click Save.
Repeat steps 4 through 5 for the other portals until all passwords have been updated. The Test Connection (circle) icons located in the top left of each row to should now be green to indicate successful Portal connections.
Update Windows Scheduled Tasks
If you have any Scheduled Tasks that use the SSAdministrator user you will have to update the password for those tasks as well. You will need to check each scheduled task, the "Author" does not always match the "Run As" configuration on the task
Simply double click on any of the scheduled tasks and click "Ok" on the popup and it will prompt you to update it.
Update MongoDB SSAdministrator Users
It is important to note that this step only needs to be taken if you have authentication set up for your instance of MongoDB and you are running an instance of GlobalCapture prior to 3.0, for more information please see the Enabling Mongo Authentication Knowledge Base article.
In the event that you need to reset your SSAdministrator password, you will need to update the Mongo database users. You should first make sure that you have updated your SSAdministrator password using the instructions above.
This update can be performed one of two ways listed below:
Mongo Shell
MongoDB users are case sensitive, “ssadministrator” is not the same user as “SSAdministrator” in mongodb terms. The casing will have to match exactly what you used in the service console.
Open an authenticated Mongo shell by running the following commands using an administrative command prompt. Replace "MyAdminUser" and "MyAdminPassword" with the Mongo admin username and password you created.
In the Mongo shell, run the following commands. Replace "SSAdministrator" and "MySSAdministratorPassword" with the username and password (respectively) for your Square 9 service account.
JS
use WorkflowEngine
db.updateUser("SSAdministrator",{pwd:"MySSAdministratorPassword"})
Repeat the previous step for the ServiceEngine, PortalSecurity, and CaptureWorkflow databases. To do this, replace "use WorkflowEngine" with "use ServiceEngine", etc.
Restart the ssBatchPortal, S9GlobalAction (or GlobalAction_1 depending on version), and GlobalCapture_1 services.
Mongo Database GUI (i.e., Robo3T or MongoDB Compass)
MongoDB users are case sensitive, “ssadministrator” is not the same user as “SSAdministrator” in mongodb terms. The casing will have to match exactly what you used in the service console.
Open your MongoDB visualizer of choice and sign in with the Mongo admin username and password you created.
In your MongoDB visualizer, you should see all your databases in the Object Explorer, and expanding each will show you a Users object containing your SSAdministrator user.
For each database (ServiceEngine, PortalSecurity, CaptureWorkflow, etc.) you will want to open a shell by right-clicking on the database. Run the query below replacing "SSAdministrator" and "MySSAdministratorPassword" with the username and password (respectively) for your Square 9 service account.
