Contents
| Easy heading | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
By understanding and modifying these fields as necessary, you can effectively manage the auto-upgrade process for GYTPOL clients, ensuring that they are always up to date with the latest version and enhancements.
| Anchor | ||||
|---|---|---|---|---|
|
...
By following these steps, you can seamlessly integrate GYTPOL with your SIEM system, enabling the transmission of pertinent data for analysis and monitoring purposes.
| Anchor | ||||
|---|---|---|---|---|
|
...
By following these instructions, you can generate more detailed logs to provide the GYTPOL support team with the necessary insights to assist in resolving any issues or enhancing the system's performance.
| Anchor | ||||
|---|---|---|---|---|
|
...
In essence, this JSON file acts as a filter, ensuring that only devices linked to the approved domains are considered for the Policy Validation process. This targeted approach streamlines the process by narrowing down the focus to specific domains, enhancing the accuracy and relevance of the analysis performed by the Group Policy Modeling Wizard.
| Anchor | ||||
|---|---|---|---|---|
|
...
By understanding and adjusting these settings as needed, you can optimize GYTPOL's reporting intervals and logging detail for effective troubleshooting and monitoring.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
This mechanism ensures that VDI instances under the same Pool name are properly managed and categorized within GYTPOL's UI, irrespective of minor numerical or hyphen variations in their names.
| Anchor | ||||
|---|---|---|---|---|
|
...
When editing any of these parameters within the configuration files, it's essential to bear in mind that restarting the gytpol Updater service is imperative. This reboot guarantees that the modifications are integrated effectively, ensuring the smooth functioning of the service in alignment with the updated configurations.
For customers who do not utilize a Cloud API or operate within closed environments, the designated file will lack any entries for "access keys" values. In such cases, this parameter will remain absent from the configuration.
...
During the initial installation process, it's recommended to substitute this file with the version located within the client zip package provided by the GYTPOL team. This ensures that the file's contents are in alignment with GYTPOL's recommended configuration, tailored to the specific client's needs and circumstances.
| Anchor | ||||
|---|---|---|---|---|
|
...
Please ensure to incorporate the appropriate SQL server name and database name in the actual file according to your configuration needs.
| Anchor | ||||
|---|---|---|---|---|
|
...
Within this folder, you are expected to store the client files (e.g., MSI, PKG) necessary for the automated update procedure, which was elaborated upon in the Analyzer section. The URL specified in the "clientUpgrade.json" file directs to the contents of this folder, facilitating the seamless auto-update process. This organized approach ensures that the correct client files are accessible for updates and contributes to the efficiency of the auto-update mechanism.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
If you opt to alter either of these ports, it's imperative to remember that both the HTTP and HTTPS ports need to be changed simultaneously. While you have the flexibility to select different port numbers, it's essential to avoid ports already in use by GYTPOL's internal processes, as indicated in the RsopRepository > URLs.json configuration. This ensures smooth communication while accommodating your specific port preferences.
"throttledUrls": This parameter signifies the limit of concurrent reports allowed per second. The default value is set at 50 reports per second. It's strongly recommended not to modify this number unless specifically requested by the GYTPOL team. Any adjustments in this regard should be carried out only under the guidance of GYTPOL's experts. If needed, further troubleshooting steps can be found in the provided resource.
...
"permissions": By default, access to the user interface (UI) is extended to Authenticated Users. The management of roles and permissions is conducted within the UI itself, accessible through the "Roles and Permissions" screen. Users within the designated group gain access to the UI, with their access level aligned to the roles assigned to them. Should no roles be granted, an error message will emerge. If necessary, it's possible to switch the group from Authenticated Users to any security group within the Active Directory. However, it's important to note that mere membership within a group is insufficient; actual access levels are established via the Roles screen. This setup ensures controlled and tailored access to GYTPOL's UI in line with your security requirements.
| Anchor | ||||
|---|---|---|---|---|
|
...
By ensuring that the appropriate permissions are granted, you can facilitate the seamless execution of tasks within the GYTPOL system. This step plays a pivotal role in maintaining the operational integrity and effectiveness of various tasks within the application.
| Anchor | ||||
|---|---|---|---|---|
|
...
Navigate to the Security Options within your system settings.
Locate the option related to storing network credentials.
Confirm that the setting is configured as "Disabled."
| Anchor | ||||
|---|---|---|---|---|
|
...
Certain services could encounter difficulties when starting after system restarts or updates. Any related errors or issues will be documented in the Application log within the Event Viewer. This log provides valuable information about service startup problems and helps identify any issues that need attention.
You have multiple options to troubleshoot and identify errors in this situation, with the event log being the most convenient method.
...
Navigate to the folder associated with the service. This information can be found in the "Path to Executable" line in the services section.
Locate the executable file related to the service.
Run the executable by typing its name followed by "--console" and press Enter. For example, if the executable is "Analyzer.exe," you would type "Analyzer.exe --console".
This command will display the service startup process and potentially provide more information about any errors encountered during startup.
| Anchor | ||||
|---|---|---|---|---|
|
...
By running the service executable with the "--migrate" parameter, you will initiate the database migration process. This process ensures that any required additional tables, columns, keys, and other objects are created within the database according to the product's requirements. Importantly, this approach will also handle any timeouts that might occur during the migration process, allowing the database updates to complete successfully.
| Anchor | ||||
|---|---|---|---|---|
|
...
Add the "Everyone" group with Full Control permissions to the security settings of the relevant folder. Ensure that these permissions are applied to all child objects within the folder.
Run the service executable with the "--migrate" parameter and allow the migration process to complete.
Once the migration is successful, remove the "Everyone" group from the folder's security settings.
Start the affected service through the System Services utility.
...
the migration process to complete.
Once the migration is successful, remove the "Everyone" group from the folder's security settings.
Start the affected service through the System Services utility.
...
Could not allocate a new page for database ‘gytpol_<DBNAME>’ because of insufficient disk space in filegroup ‘PRIMARY’
LocalDB (including SQL Express) databases have a maximum disk space allocation of 10GB. If your database file exceeds this limit, the service will fail to start. It's advisable to transfer your databases to an external SQL server, whether it's dedicated or shared. Preferably, opt for a dedicated server for better performance.
Keep in mind that after migration, certain data won't transfer, such as created action rules (mutes, remediations, and auto-remediations) and the activity log of actions.
...
| Anchor | ||||
|---|---|---|---|---|
|
...
If a proxy server is configured, it will be displayed in the command output.
Powershell:
$proxySettings = Get-ItemProperty -Path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings'
if ($proxySettings.ProxyEnable -eq 1)
{
Write-Output "Proxy Server: $($proxySettings.ProxyServer)"
}
else {
Write-Output "Proxy is not enabled."
}
If proxy is set, this will be the result:
...
Once you've made this change, a folder named "archive" will be created in the "C:\Program Files\WindowsPowerShell\Modules\gytpol" directory. This folder will contain logs and information that can be shared with the GYTPOL support team for advanced troubleshooting purposes.
Each individual task, scan, or remediation action initiated by GYTPOL will generate a corresponding folder containing logs, commands, and results. These folders are valuable for diagnosing any failures or issues during the process.
...
The GYTPOL support team will then be able to analyze the logs and information within the zipped folder to assist in identifying and resolving any issues.
To revert the change made to the "archiveEnabled" field and disable the creation of the archive folder, you can follow these steps:
...
By providing the detailed information from the developer tools, the GYTPOL support team will be better equipped to diagnose and address the issue you are encountering with the GYTPOL web application.
| Anchor | ||||
|---|---|---|---|---|
|
...
By ensuring that the vdiImages.json file is edited correctly and maintains the proper JSON format, you can prevent errors and ensure the smooth functioning of the GYTPOL Analyzer service.
| Anchor | ||||
|---|---|---|---|---|
|
...
Stop the Existing Instance of gytpolServer: If the gytpolServer task is already running, you should stop the existing instance before making the change.
Modify gytpolServer Task Settings: Open the Task Scheduler and navigate to the gytpol folder in the main Task Scheduler Library. Locate the gytpolServer task and change the task behaviour as shown in the picture below:
| Anchor | ||||
|---|---|---|---|---|
|
...
Open the Services application:
Press Win + R, type services.msc, and press Enter.
Find and select the "gytpol GPMCPROXY" service, right-click on it, and choose "Restart."
Find and select the "gytpol Data Repository" service, right-click on it, and choose "Restart."
