I have not figured this out yet. Yes the issue is that each drive is using the serial number as part of the names as well. I tried some %pre section options as well with no success. So still manually installing this on each server and using the GUI to install currently. Very frustrating. I appreciate your assistance. I will keep trying. Thanks!
Original Message:
Sent: May 20, 2024 10:41 AM
From: n2ocharged
Subject: Automated KS
Not sure if you got this figured out but the KS file should have your drive name on it.
There are other ways to use a device location (IE: PCIE port it is located on) but you would have to have all the same machine, hardware IDs, etc...
Here's a snippet of my KS file... pay attention to the single quotes ' ' with drive3 name.
install --firstdisk=<drive1 name>,<drive2 name>, <'Drive3 name with spaces'> --overwritevmfs --novmfsondisk
You cannot use wildcards, the name of the drive has to match the name in the KS file.
Some drives have the serial number in the name which makes it a little difficult... the only way I've been able to figure this out is trial and error with the drive & installation since I've had no formal training with VMWare / Broadcom software.
I'm fortunate enough that I have, for the most part, all the same drive names on all of our devices.
I'm trying to learn a better way to do this that will look for a drive with a specific size using the %PRE section and pull the drive name from it, if I can. I don't know if this is possible but it would make a lot of sense to be able to do it this way.
I may be over complicating this but, again, no formal training.
Cheers,
Nate
Original Message:
Sent: May 06, 2024 02:28 PM
From: skey4867
Subject: Automated KS
I have reviewed this document but still no luck or understanding. I have added some information from my environment to maybe assist with my problem. Here is the output regarding my two disk I am working with. Again the problem is that the SAMSUNG SSD presents as the firstdisk and I want to exclusively ignore it and install on the M.2 SATA Drive. I will be installing on several different systems with the exact same hardware so I cant hardcode verbatum of each drive cause the host is presenting them with serial numbers.
Original Message:
Sent: Apr 18, 2024 07:10 AM
From: ganeshteja55
Subject: Automated KS
Have you validated this
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-61A14EBB-5CF3-43EE-87EF-DB8EC6D83698.html