The combination of openSUSE Tumbleweed’s rolling release style, the qualtify of applications available on the Linux platform (including snaps, flatpak, and AppImage files), I feel like I have found a nice home for personal computing use – all without a single dime in license fees for my Operating System. It’s completely free, open-source, and I’m in control of the OS and my data. Fantastic!
Many of my friends have heard me talk a great deal about ownCloud. I talk about it, because it is a tool that does so much for me and is completely FREE and open source. You can run ownCloud on a server at home or anywhere you can run a Linux server. As of version…
This past week, our managed services team at OrcsWeb ran into an issue with Remote Desktop Services 2012. We had a client setup request for RDS on their Windows Server 2012 machine. We were to install the Session Host, Web, and Service Broker roles. This server was to point to our existing 2008 R2 RDS Licensed server. This 2008 R2 server’s only job is to provide central point of management for RDS CALs.
A Windows Server 2012 box cannot point to anything but another Windows Server 2012 box for licensing. This was not an issue, we just stood up a Server 2012 box to replace our 2008 R2 RDS box, where its only role would be a license server.
Once the new server was up and running, RDS licensing role installed, configured and validated with CALs for our server versions, including Server 2012 RDS, we attempted to point our RDS session host installation to the new licensing server.
To do this, I launched Server Manager, selected Remote Deaktop Services from the left panel, in the Role section I selected Overview, then selected the tasks drop down in Deployment Overview and selected Edit Deployment Properties.
I then went to the RD Licensing section to add my license server. I added my licensing server via FQDN, and was promptly greeted with an error message.
“The license server specified is not valid. Verify the server name and specify a valid server name before saving the settings.”
During a project I am working on, I had to replace the NICs in my Dell blade servers running CentOS 6.4 minimal installation.
Here was my scenario:
Dell M600/610 blade servers. 2x onboard Broadcom NICs, 4x Broadcom NICs via mezz slot.
I replaced the Broadcom mezzanine quad-port card with an Intel quad-port card , due to a problem with Broadcom drivers and my application.
Most of my sysadm experience is working with Windows server and Windows to its credit handles this change very well; however with CentOS, especially the minimal installation server I have, it is not as intuitive. After some quick searching I found some information on how to do this. I did not find a guide per se and I have some iSCSI configuration as well which needed attention. Here is how I did this, hopefully someone will find my experience helpful.
I assume that you have replaced your NIC and are trying to set it up in CentOS.
The first thing you should do is take a look at all of your current ifcfg files and make backup notes on the interfaces before doing anything else.
# cd /etc/sysconfig/network-scripts
Take a look at all of the ifcfg-xxx files in the directory. The quickest way to get a backup of your text files would be to display the file and copy and paste the contents (listing the full path just in case):
UPDATE 06/20/2013 – Included steps to update Dell Firmware and BIOS. I also updated when to setup the /etc/mulitpath.conf file, updated the order of some software install steps and fixed some formatting and mistakes to make the process more smooth.
UPDATE 03/30/2013 – The original post used older tools to try and make this work. I had issues with multipath and decided to call Dell as my MD3000i was still in warranty. While they would NOT support this or my OS, they did offer me the latest Resource CD and answered a few questions along the way. Thanks to their help, and various blogs on the interwebs, I can confidently setup CentOS 6.4 to a Dell MD3000i utilizing MPIO. I’ve also submitted this blog to my technician, along with my /etc/multipath.conf file to share with the Dell ESS team should any other Dell customers inquire on this setup, they would have a reference. I’ve successfully setup three different Dell servers using this procedure.
Recently I worked on a project to stand up a CentOS based XEN environment using Dell hardware. I’ve used Linux in the past, mostly on test machines and for specific software vendor builds. My experience and day-to-day in my career has been in Windows Server administration, so I decided to extensively document my configuration and experience during the setup over a series of posts.
The hardware involved (minus switching, Cisco) in this project is all Dell, specifically, Dell PE servers (M600’s) and a Dell MD3000i. The XEN servers will be utilizing the iSCSI space for 3.8TB of R10 storage.We are using some specialty software that requires the use of CentOS, so the base OS for these boxes will be CentOS 6.4. By choosing CentOS 6, this will allow us to use XEN v4.
Dell supports RHEL6, so they inadvertently support CentOS 6 as well; however, the md3000i product is EOL, no further firmware updates have been released, and the resources will not officially support RHEL6. I documented my setup and configuration of the host components as I went and turned it into this guide so that anyone searching for help with this particular setup may be helped.
Before beginning this guide, I assume that you have your server built fresh and are ready to begin configuration. Need help installing CentOS 6? You can find the ISO here:
Have you ever been in a situation where you needed to ping a server? Most everyone that has used a computer has done this at some point. As a System Administrator, I use this utility on a daily basis. Just fire up a command prompt or PowerShell and type, “ping MYSERVER01” and press enter. Easy…