Impero workplace pro client connectivity
DISCLAIMER - Any changes made as outlined below are carried out as your own risk, we cannot accept responsibility for any registry changes made and outcomes thereafter. We have tested the below scenarios with no issues. If you are unsure we recommend that you apply the below changes in an isolated environment.
When the Impero Client is installed, it will perform 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
Method 2: ServerIP 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 an 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 will not be a viable option if you have more than one impero server on the same network, you will need to use method 2 if you have more than one Impero Server.
Method 2: Server IP text file
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;
In the following directory create a ServerIPFixed.txt in this following location;
OSX à Library à Application Support à ImperoClientSrv à ServerIPFixed.txt
Once this file has been replaced the Mac will have to be rebooted
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: You will need to 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 ‘Add...’
- Click ‘Browse...’
- Select the VBScript and click ‘Open’
- Click ‘OK’
- Click ‘OK’
Comments
0 comments
Please sign in to leave a comment.