I have been playing with vSAN File Services a lot the past couple of weeks. I have been configuration and re-configuring it a few times. At some point, I found myself in the situation where when I wanted to enable vSAN File Services and provide new IP details that I received the following error: “Existing domain information has been pre-populated below”. shown in the below screenshot.
Why did this happen? Well, the configuration details are stored in the objects that form the file shares. I disabled vSAN File Services while I still had file shares running. This then results in the scenario where when you enable vSAN File Services that it detects the file share objects, it will read the configuration details and assume that you will want to configure it with the same Domain/Network details so that you can access the existing shares. But what if you don’t? What if you want a brand new shiny environment? Well, that is also possible and you can do that as following:
- Enable vSAN File Services with existing domain information
- When configured, go to File Service Shares and delete all existing file shares
- When all are deleted, disable vSAN File Services
- When all tasks are complete, enable vSAN File Services again
- Enter new Domain and Networking details
Pretty simple right?
Danilo says
Hello Duncan,
Very great post, thanks!
After doing this, I tried to access the menu “File Shares” on VSAN and received the message “Cannot load shares. Check the logs for more details”.
In this case, what log file do I need to check?
I need to configure the vSAN File Services from scratch, but the older configuration are pops when I tried to enable the vSAN File Services.
Can you help me, please?
Thanks,
Danilo.