Vmware Host Profile purpose

My point is, if you try to create Host profile as a shortcut, so that you do not repeat the same configuration for each ESX Hosts, you will end in more work tweaking the profile, and you are more likely to break things when you attach other ESX hosts to the profile.
So More Risks than Benefits

That is possible.

But the same argument could be stated for developing a Windows Deployment System and Microsoft Deployment Toolkit for the rolling out of Servers and Desktops.

e.g. the development time required to create a working Windows Server 2019 server, or Windows 10 Desktop, could take 6-9 man months - which could be argued is much longer than to create a single Windows 2019 or Windows 10 desktop.

BUT now think of the man-hours and cost savings over 10 years..... once it's been developed.


and can then be used by a IT Technician to rollout servers and desktops, from effectively a MENU!

So Technician..

1. Connects Server/Workstation to LAN.
2. Powers on.
3. Computer Boots from LAN
4. Technican selects 1. Server to 2. Desktop.
5. 2 hours later returns to put server or workstation on users desk.

Very little skilled require, maybe in your lab you do not see the scale of deployment, but when it comes to hundreds of ESXi hosts...

(and it can easily be maintened with little skills, e.g. adding new server and desktop motherboards and devices, drivers)

I meant if you have one ESX host  already in Production  and you create a profile from it and you attach other ESX hosts (that are also in production) to the profile...
That can be very Risky


If you have ESX hosts that are NOT in production yet , and you want to attach them to a profile, then it should be OK..

Thanks

np