IGEL – Error No Setup Data Received

Written by Allen White on. Posted in IGEL

In the IGEL UMS I came across an issue where if I sent out a UMS-TC profile to my IGEL thin clients the profile would take an age to try and deploy then it would eventually come back with a result of the action failed.

igel error no setup data received

igel error no setup data received

Digging further into the error by double clicking on theĀ  error I could see this error.

igel cannot get profile

igel cannot get profile

This error was down to the IGEL clients not being able to connect to the UMS server correctly.You may also notices that the IGEL clients are slow to respond when using the UMS.Tto fix this we can add an entry into DNS.

On your DNS server create an A record as seen below and point it to your UMS server.

igelrmserver

The IGEL units will use this to connect to the UMS and you should have no further problems sending out profiles to thin clients

 

 

 
 
Related Posts Slider

Related Problems

Setup An IGEL Thin Client As An Internet Kiosk With UMS
A step by step guide on how to use the IGEL Universal Management Suite (UMS) to setup a Thin Client in Kiosk mode.
READ SOLUTION
Scan And Import IGEL Thin Clients Into Universal Management Suite
A step by step guide on how to setup your IGEL clients with a static or DHCP address then import and scan them into the IGEL Universal Management Suite
READ SOLUTION
IGEL Thin Client – Invalid Certificate
When importing the IGEL thin client you come across a error stating Certificate invalid or invalid certificate. Here is how to fix i.
READ SOLUTION
IGEL UMS banner
This step by step guide will guide you through the installation of the IGEL universal management suite.Information on the various installations of the UMS
READ SOLUTION
The Attempt To Connect To Powershell Using Kerberos Authentication Failed The WinRM Client Received And Http Server Error Status (500)
When you launch the EMC you see either the message The WinRM Client Received An Http Server Error Status (500) or The attempt to connect to http://server.domainname.com/powershell using "kerberos" ...
READ SOLUTION
Outlook 2003 Gives Connect To Instance Error When Connecting To Exchange 2010
When you connect to exchange 2010 with outlook 2003 , you may see the error connect to instance. This is a known issue and microsoft have provided a fix
READ SOLUTION
Exchange 2010 ECP error 400
When logging into the ECP you get an error 400 , bad request - you can fix the issue by recreating the folders in powershell.
READ SOLUTION
Setup An IGEL Thin Client As An Internet
Change The Resolution On An IGEL Thin With
Scan And Import IGEL Thin Clients Into Universal
IGEL Thin Client – Invalid Certificate
Step By Step Installation of IGEL Universal Management
The Attempt To Connect To Powershell Using Kerberos
Outlook 2003 Gives Connect To Instance Error When
Exchange 2010 ECP error 400

Tags:

Allen White

Allen is a Technical Consultant for an IT company in the North East of England and holds the following accreditations. MCSA, MCSE, MCTS, MCITP, CCA, CCSP, VCP 4,5 and HP ASE, AIS - Network Infrastructure. Backup Academy Certified. I run this site in my spare time so if I help you then PLEASE take the time to share using the share tools on the site.

What Do You Think?

Search Solutions

Categories

(c) Techieshelp.com. Please be aware, all information is provided freely, any information used is done so at your risk and Techieshelp will not be held responsible for any issue that may occur.