It wasn't that simple, but it works in my environment. You could however join this data to the VPX_ENTITY table, to get distinct ENTITY ID's. Keep in mind, if you have a VM in previous years, and you delete it, that, if you create a new VM, and it has the same name, then this data will be incorrect. It now only lists the VM's that were first powered on in 2007. If the VM was never started in 2004/2005/2006, then should be able to view all the VM's that were powered on in 2007, and then only pull the ones that weren't in the 2004/2005/2006 list. This shows me all of the VM's that were powered on in 2004, 2005, and 2006 Where NAME = '' and (Year(convert(nvarchar,START_TIME,101)) = '2004' or I ran this query against my VC database to show all the different start times for my VM's. ESX is the house of VM, same principle.Ī basic way to see the first entries of a VM, would be to use a SQL query: They each were added separately, but as a WHOLE they make the house more valuable and livable. does it matter? NO, the house just went up in value.All that matters is value. When you build a house, when did you add that new kitchen floor, deck, roof, or carpet. If you created an ESX host and it only had 3 VM's, then you might have a problem explaining that, but the detail level for a VM is irrelevant. That's EXACTLY what I told our management.
![vm esxi 6.5 how to transform date to other computer vm esxi 6.5 how to transform date to other computer](https://filedb.experts-exchange.com/incoming/2020/06_w27/1471846/ESXi7.0bA.png)
Does it really matter WHEN each and every VM came into existence. How much is this going to cost us, and when are we going to see the return on our investment. From THIS point on, we saved $250,000.00 by using VM Ware (or whatever) and thus justifying the cost of the license, which is all they really want to know. If you created 20 VM's last week, or last month, or 100 VM's last year, who really cares? The main point is going forward, how much we save by using Virtualization. Thankfully, ESXi includes an implementation of the cron utility that can be. It is very useful for scheduling scripts or specific commands to run on a defined schedule daily, weekly, monthly and everything in between.
![vm esxi 6.5 how to transform date to other computer vm esxi 6.5 how to transform date to other computer](https://www.informatiweb-pro.net/images/tutoriels/virtualisation/vmware/esxi-6-5/4-nom-serveur/1-esxi-6-5-networking-tcp-ip-config.jpg)
![vm esxi 6.5 how to transform date to other computer vm esxi 6.5 how to transform date to other computer](https://cf-images.us-east-1.prod.boltdns.net/v1/static/1971571333001/441be907-0794-438a-8a81-0782a32629a3/2050ec42-b9b2-4ec5-a4c0-c8f375d5169c/1280x720/match/image.jpg)
I understand the management point of view, but as the question I asked, what does it matter WHEN the VM's were implemented, only the CURRENT status is ALL that matters. The utility cron is a job scheduler in Linux/Unix based operating systems.