Handling an Impero client connectivity issue

When the Impero Client is installed, it performs a UDP broadcast to detect an Impero Server to connect to. On occasion, such as within VLAN environments, this UDP broadcast may fail to detect and connect to an Impero Server.

 

In such cases, there are a number of ways in which you can ensure that your Impero Clients connect to your Impero Server:

 

Method 1: DNS entry (Only if you have 1 ImperoServer on your network)

Method 2: ServerIPFixed text file

Method 3: Editing registry keys through Group Policy

Method 4: Deploy a ‘startup’ script through Group Policy

 

If you are unsure which method to use feel free to give the support line a call.

 

Method 1: DNS entry

Open DNS Manager, Drill-down to your domain under Forward Lookup Zones and create a New Host (A or AAAA) record in DNS.

 

Call the entry 'impero_server' (or 'impero-server') with the IP Address of your Impero Server machine.

This is not a viable option if you have more than one Impero server on the same network, it is required that you use method 2 if you have more than one Impero Server. 

 

 

Method 2: ServerIPFixed text file - Windows and MacOS

Windows;
 In the directory for Impero on the client machines (C:\Program Files (x86)\Impero Solutions Ltd\Impero Client\), create a file named 'ServerIPFixed.txt' - the contents of this file should be the IP address of the server. Once the ImperoClientSVC service (or the machine) has restarted, the client will connect to the server.

MacOS;

Application/Impero directory on the macOS device, once this has been put in place the macOS Device requires a restart, or you can kill the Impero task in ActivityMonitor.

 

Method 3: Editing registry keys through Group Policy

 

64-bit Clients 

 

Create a Group Policy Object named ‘Impero Registry ServerIP 64bit’.

 

Start ‘Group Policy Management Editor’ and go to ‘Computer Configuration\Preferences\Windows Settings\Registry’.

 

Create a new registry item as outlined below:

 

Action: Create

 

Hive: HKEY_LOCAL_MACHINE

Key path: SOFTWARE\Wow6432Node\Impero Solutions Ltd\ImperoV3

Value name: ServerIP

Value Type: REG_SZ

Value Data: IP address of Impero server e.g 192.168.1.9

 

32-bit Clients

 

Create a Group Policy Object named ‘Impero Registry ServerIP 32bit’.

 

Start ‘Group Policy Management Editor’ and go to ‘Computer Configuration\Preferences\Windows Settings\Registry’.

 

Create a new registry item as outlined below:

 

Action: Create

 

Hive: HKEY_LOCAL_MACHINE

Key path: SOFTWARE\Impero Solutions Ltd\ImperoV3

Value name: ServerIP

Value Type: REG_SZ

Value Data: IP address of Impero server e.g 192.168.1.9

 

Please ensure that the GPO is linked to the relevant domain, site or OU.

 

Method 4: Deploy a ‘startup’ script through Group Policy

 

Create a VBScript (.vbs) file containing the following code:

 

Dim WshShell, OSBits, serverIP

Set WshShell = WScript.CreateObject("WScript.Shell")

OSBits = GetObject("winmgmts:root\cimv2:Win32_Processor='cpu0'").AddressWidth

serverIP = "0.0.0.0"

On Error Resume Next

If(OSBits = "32") Then

  WshShell.RegWrite "HKLM\SOFTWARE\Impero Solutions Ltd\ImperoV3\ServerIP", serverIP, "REG_SZ"

Else        

  WshShell.RegWrite "HKLM\SOFTWARE\Wow6432Node\Impero Solutions Ltd\ImperoV3\ServerIP", serverIP, "REG_SZ" 

End if

 

NOTE: It is necessary that you replace 0.0.0.0 with the IP address of the Impero Server.

 

To add this script to Group Policy:

 

- Create and/or edit an appropriate GPO to start ‘Group Policy Management Editor’. 

- Navigate to ‘Computer Configuration\Policies\Windows Settings\Scripts (Startup/Shutdown)’.

- Open ‘Startup’.

- In the Scripts, tab click ‘Show Files...’.

- Copy the VBScript into the directory.

- Click on ‘Add...’

- Click on ‘Browse...’

- Select the VBScript and click on ‘Open’

- Click on ‘OK’

- Click on ‘OK’