Documenting all of the components of the install and configuration.
The first thing we did was build a Windows virtual machine in Azure and configured the license server manually. Our end goal was to build a fully automated system using CI/CD.
We originally opted to keep the license server as a static server, running 24/7/365 in Azure however that doesn't break down the full monolith, nor does it really leverage the cloud. My task was to focus on the license component and it proved to be the most challenging. A Windows and Linux VM that must run simultaneously.Breaking up a single physical server running several applications.Licensing requirements for the applications, dependency on a dedicated licensing server with a static MAC address.Overview of the technical considerations: The server had to provide the licenses to 2 running virtual machines, one Linux and one Windows, which had to be spun up simultaneously and communicate for the applications to work. You had to provide the vendor with your MAC address, which was then embedded into their license file. The licensing setup was also tedious to configure and took over a day to setup. Our biggest blocker was the licensing for two of the applications, each license was tied to the MAC address and machine name of the physical server.
The customer wanted an automated and repeatable solution to rid themselves of various pain points in their current system. The software vendors had not even vetted their software for use in the cloud, but gave us approval to proceed.ĭesigning for the new cloud infrastructure we highlighted the technical blockers of migration their production system to the cloud. A lift and shift was a possible but would not enable the application nor the customer to fully embrace the capability of the cloud. I have recently been working on a customer project migrating their on premises physical server and its applications to Azure. It is a time consuming and there is nothing agile about this process. In my customer's use case, we had to reach out directly to the software vendor to re-install our application, request a new license and wait almost an entire day to provide the license file.
This causes a slew of issues such as: replacing hardware in your servers, running multiple network cards (think redundancy), virtualizing your environment, or even just setting up a highly available configuration of your application. I am using windows 7 for this tutorial, so I will use windows DOS terminal.Many established software companies have tied their licensing to the MAC ADD of your server/computer. to run the arp utility, open your command terminal. Go to the printer, usually devices will have the MAC ADDRESS printed on the back, so for example, lets say my printer has this MAC ADDRESS: so how do you find the correct ip address? this is what I would do the printer may be in your network and you probably are just pinging the wrong ip address for that printer. However, there is a way for example, if I have a network printer connected to my LAN but I can't ping it. IP Address is layer 3 of the OSI Model, and the MAC Address belongs to Layer 2 "is it possible to ping a device using only the mac address of the machine? or what tools I can use to check if a device is connected to the network"ĪNSWER: the answer is no. Today's questions is regarding networking. You can find MAC address on the following devices: This identifier helps network communicate with each other. It is a unique identifier set by the manufacturer and is permanently set into the hardware equipment. The MAC address is an identifier for computer network hardware. MAC Address means Media Access Control Address. Please follow these instructions to successfully ping a network MAC access.