RDP 2.x: Deploying ESX Server - HOWTO use NFS as Installation Method?

[McDermontK2]

Apologies for the stupid Question but how do I leverage NFS as my Installation Method (via Kickstart) instead of IIS FTP?

None of the HP documentation seems to offer this capability; however, I'm sure I'm missing something rather obvious.

Can I simply replace (in kickstart .cfg):
# Installation Method
url --url ftp://anonymous:rdp@167.209.10.50/ds/lib/osdist/vmesx2

with something like this:
# Installation Method
nfs -server IP Address -dir /rdp/esx (provided this is where my install media is staged)?

Thank you for your help.

[David Claypool]

FTP was found to be a more reliable and simpler method than NFS. Additionally, it doesn't require a separate Linux NFS server to be set up. Since RDP uses IIS for its web client access, the assumption is that FTP is there and available.

For what purpose do you wish to do a non-standard setup?

[McDermontK2]

Quite Simply:

In our 1200+ Server Environment we do not allow FTP Services due to inherent Security Risk.

Are you saying that NFS will not work with RDP any longer?

[Adrian Clint_1]

Try looking on the Vmware website. I'm sure I've seen threads on the support forums detailing how to do this.

[McDermontK2]

I combed the VMware forums prior to posting here - wasn't able to find anything specific to RDP 2.2 -- there are NFS references to prior RDP versions (before IIS FTP support was added) so still trying to understand definitively if this will work with the latest RDP version.

Seems that it is 'non-standard' based on HP response but if it works we would rather go that way than filing a security exception for FTP services.