I tried a couple of methods of installing LibreELEC in a VMware virtual machine before finding the solution. The first was to simply pass through a Jump drive with a bootable image to the virtual machine. This didn’t work as I discovered that vSphere virtual machines cannot boot from USB.
I also tried converting an image file to an .iso and booting from that – that also didn’t work.
I finally discovered the LibreELEC virtual appliance and simply deployed that to vSphere.
I would typically just post a link, but it appears that the LibreELEC mirrors seem to change so it is best to know how to get a link to the .ova file.
First head to the LibreELEC download page. What we are looking for is a link named info behind which is a mirror list.
On the mirror list page you can see that I have two mirrors available in the US:
Notice that I have the first portion of the path to a LibreELEC image selected. This URL takes me to the full listing of available LibreELEC images on that mirror.
Copy the link to the LibreELEC .ova file and then run the vSphere Client to start deploying the virtual appliance.
Click the File menu and then Deploy OVF Template.
Paste the LibreELEC .ova hyperlink and then click Next to continue through the rest of the deployment wizard.
Zentyal Server is an open source Linux small business server, that can act as a Gateway, Infrastructure Manager, Unified Threat Manager, Office Server, Unified Communication Server or a combination of the above.
I am performing this setup on a minimal virtual machine installation of Ubuntu Server 14.04. At the time of writing Zentyal 3.5 is the most current Zentyal release.
First make sure that repositories and software are up to date:
sudo apt-get update
sudo apt-get upgrade
Add the Zentyal 3.5 repository to /etc/apt/sources.list:
echo "deb http://archive.zentyal.org/zentyal 3.5 main extra" | sudo tee -a /etc/apt/sources.list
Enter a password for Tiny Tiny RSS to register with MySQL – a random password will be generated if left blank:
Confirm your application password:
Next we need to use nano to edit some configuration files.
First we need to edit our server address in /etc/tt-rss/config.php:
sudo nano /etc/tt-rss/config.php
Find the line define('SELF_URL_PATH', 'http://yourserver/tt-rss/'); and change it to define('SELF_URL_PATH', 'http://localhost/tt-rss/'); (as per the server address that we set previously):
Press Ctrl + O then Enter to save the changes to config.php and then Ctrl +X to exit nano.
To get Tiny Tiny RSS to update feeds we need to edit /etc/default/tt-rss:
sudo nano /etc/default/tt-rss
Change DISABLED=1 to DISABLED=0 to allow the Tiny Tiny RSS daemon to be started:
Press Ctrl + O then Enter to save the changes to config.php and then Ctrl +X to exit nano.
Start the Tiny Tiny RSS service:
sudo service tt-rss start
Obtain the IP address of your Ubuntu Server installation:
Open a browser on another machine and navigate to your Tiny Tiny RSS URL:
Login with the username: admin and the password: password.
Click Actions, Preferences and Users to change your admin password and add users. You can import feeds under the Feeds tab or click Exit Preferences and then Actions, Subscribe to feed to add feeds manually.
I’ve lost count of the number of times that I have installed Ubuntu Server on my VMware vSphere box – so I finally looked in to performing an unattended install.
I could have setup DHCP and TFTP servers and done PXE boot from images over the network – but I wanted to work on something quicker than that (and I don’t have that much spare RAM on my vSphere box as it is).
So I settled on re-mastering an Ubuntu Server .iso image. The result is an unattended install, except for the initial boot screen (where I need to select a minimal virtual machine installation anyway).
The following steps were performed on Ubuntu Desktop.
The -r switch copies directories recursively and -T specifies no (singular) target directory.
Now we have a copy of our Ubuntu .iso to work on in /opt/serveriso – but we need to make these files writable:
sudo chmod -R 777 /opt/serveriso/
With this preparation done we can start customizing things.
If we look at the isolinux/langlist file we see all the supported languages listed that Ubuntu supports (in an abbreviated format):
I am only interested in an English install so I am going to overwrite the contents of isolinux/langlist with the single abbreviation for English, which is “en”.
echo en >isolinux/langlist
This stops the language selection menu from appearing during installation.
The next step of the process is to create a kickstart file – this will provide the server install with the answers to the various questions asked during installation, such as timezone, username, password, partition structure and so on.
Install Kickstart Configurator:
sudo apt-get install system-config-kickstart
Click the Dash button and type kickstart and then click on the kickstart application.
Obviously you should customize your settings as you see fit – I have provided mine for reference.
Click File, Save File and save the kickstart file ks.cfg to /opt/serveriso.
While using the Kickstart Configurator you may have noticed that the Package Selection screen did not work. Fortunately we can manually edit the ks.cfg file so that the packages that we want are installed during Ubuntu Server installation.
At the end of ks.cfg add %packages and then list the packages that you want installed. I chose to install nano, openssh-server and open-vm-tools:
Today I set about installing Windows Server 2012 in a virtual test environment. Further down the road I plan to look at publishing remote applications, but for now let’s begin with installing Active Directory.
This is a basic outline of the post-installation steps that I will follow:
Change the machine name
Set a static IP address
Install Windows Updates
Install Active Directory Domain Services
Promote server to Domain Controller
1. Change the machine name
From the desktop press Ctrl + X and then click System on the pop-up menu. Under Computer name, domain and workgroup settings click Change Settings.
In the System Properties window click the Change button and then change the Computer name. Click OK to exit.
2. Set a Static IP Address
From the Start Screen click Control Panel and then click Network and Sharing Center and then click the link for your Ethernet connection.
In the Ethernet Status window click the Properties button. Scroll down and select Internet Protocol Version 4 (TCP/IPv4) and then click the Properties button.
Set your static IP address, Subnet mask, Default gateway and Preferred DNS server.
My settings are provided just so that you have a screenshot. I am using a NAT network provided by VMware Player.
3. Check for Windows Updates
From the Start Screen click Control Panel and then click Windows Update. If necessary turn updates on and then Check for updates and install them.
4. Installing Active Directory Domain Services (ADDS)
From the Server Manager Dashboard click Add roles and features.
Review the Before you begin screen for any actions that are required prior to installing roles, role services or features, and then click Next.
Select Role-based or feature-based installation and then click Next.
Select your server from the server pool and then click Next.
Select Active Directory Domain Services from the list.
Review the role services and features to be installed and click the Add Features button.
You will be returned to the Server Roles page of the Add Roles and Features Wizard, click Next to proceed.
On the Features page of the Wizard the Group Policy Management feature is automatically selected, click Next.
Review the AD DS page and then click Next. If you do not have a DNS server on your network you will be prompted to install DNS later.
The Confirmation page gives the option to Export configuration settings and to Restart the destination server automatically if required. Configure as required and then click Install.
The previously selected roles and features will now be installed. Click Close to exit the wizard.
5. Promote Windows Server 2012 to a Domain Controller
An Alert notification will appear on the Server Manager Dashboard prompting you to Promote this server to a domain controller.
Review the domain deployment options. I will Add a new forest called Pricklytech.local. Click Next.
Select the Forest functional level (FFL) and the Domain functional level (DFL) from the two drop-down menus – they should be set to the highest level that your environment supports (to enable as many AD features as possible). The FFL, for example, can be set to Server 2003, 2008, 2008 R2 or 2012.
Next specify domain controller capabilities. I have Domain Name System (DNS) server selected as I do not yet have a DNS server in this particular test environment. You will also notice that Global Catalog is checked and greyed out – because this is the first domain controller in a new forest.
Type and confirm the Directory Services Restore Mode (DSRM) password. DSRM is a safe mode boot option that is used to repair / recover Active Directory.
Review the DNS delegation alert. In my environment no action is required – so after closing the alert I clicked Next.
The NetBIOS domain name is supplied – click Next.
The default paths for the AD DS database, log files, and SYSVOL are displayed. Click Next.
Review your selections. You can export a Powershell script to automate additional installations by clicking the View script button. Click Next.
A prerequisite check is run. If All prerequisite checks passed successfully click Install to continue.
Once the server is successfully promoted it was automatically rebooted.