Archive for July 11th, 2012

Update: CentOS based virtual appliance for Microsoft Hyper-V Server incl. IGEL UMS Server Version 1.1

Wednesday, July 11th, 2012

cloud-client.info IGEL Universal Management Suite Appliance for Microsoft Hyper-V
—————————————————————————————————–

Version: 1.1

Release Date: 10.07.2012

Copyright 2012 cloud-client.info

EMail: blog@cloud-client.info

This is a non commercial release without any official support by IGEL Technology or cloud-client.info.

Use on your own risk, the publisher is not responsible for any damage or issue related to the use
of this free release.

Requirements for the VM:
2 GB RAM
12 GB HDD

Donate:
If you want to invite me to a beer for my work, just make a donation via
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZJUS6BDX9EWLQ

Getting started:
Copy the folder cloud-client.info IGEL UMS Appliance 1.0 to your Hyper-V VM folder.
Import the VM via the Hyper-V console and set the Network Card to the Network you want to connect to.
Start the VM, by default the VM will pick up a DHCP address. If you want to use a static IP you can
configure this in the DHCP Server by assigning a IP to the VM’s MAC-ID (see below).
After the vm is startet open the VM console and login to the System with the username igel (credentials
see below. Now you can assign also a static IP (Network setup is on the right in the top menu).
On the desktop you can see two links to open the UMS console or administrator tool.

Note: I’ve setup default directory rules, new clients will directly moved to the device folder. You can
motify this of course depending on your needs.

Tested with:
Windows 2008 R2 SP1

Users:
Default User: igel Password: igel
Root User: root Password: igel
IGEL UMS Main User: Administrator Password: igel
IGEL UMS Sub Admin User: igel Password: igel
FTP User: igel Password: igel

Operating System:
CentOS 6.2 Kernel 2.6.32-220.14.1.el6.i686

Network:
Hostname: igelrmserver
IP: DHCP
MAC-ID: 00:15:5D:01:A6:47 (Do not change the MAC-ID!)

Installed Services:
IGEL Unversal Management Suite 4.02.100 with enabled automatic registration for thin clients (DHCP or DNS entry required!) incl. cloud-client.info UMS Template 1.0.20
Telnet Service
VNC Service
Hyper-V Integration Services 3.2 (Note: start mountcdrom.sh in console to mount a cd/dvd; see Microsoft KB2600152)
Firewall (Disabled by default)
XDMCP connections enabled (Free Windows XDMCP Client=http://sourceforge.net/projects/xming/files/)
OPENSSL
proftpd (Configured with anonymous read/write access, warning: the appliance is not designed to handle a lot firmwares, watch the free available hdd space)

1.1
—–
– Updated IGEL Universal Management Suite to Version 4.02.100
– Updated cloud-client.info UMS Template Version 1.0.20
– Updated manuals in the manuals folder
– Added cloud-client.info whitepapers available in a folder on the desktop
– Anonymous ftp access disabled, use ftp user igel password igel
– Updates applied to CentOS system
– Fixed issue in the IGEL UMS 4.02.100, UMS Administrator doesn’t start with Java
error if no Internet connection is available. Fix for Linux and Windows Server,
open the RMAdmin.confi in the rmadmin folder with a text editor and change the
line “addjars ../rmguiserver/common/lib” to “addjars ../rmguiserver/lib”.
1.0
—–
– First release

Download is available here: Offline, download latest Version

Fix: UMS Admin doesn’t start after a 4.02.100 installation and if no internet connection is available.

Wednesday, July 11th, 2012

After installing the new UMS Server 4.02.100 it can happen that the UMS Administrator tool doesn’t start anymore with a Java error message andĀ if no internet connection is available, Linux and also Windows Server can get this behavior.

The fix is quite simple, open the file RMAdmin.config in the rmadmin folder with a text editor; the folder is placed in the UMS installation folder (C:\Program Files (x86)\IGEL\RemoteManager\rmadmin). Now change the line “addjars ../rmguiserver/common/lib” to “addjars ../rmguiserver/lib” and save the file. Now start the UMS Administrator again and the error is gone.

Cheers
Michael