I am trying to figure out how we hide the local datastores from showing up in Vsphere 5.5 From what I can find it looks like permissions. How do you do it within permissions for just the local datastore
In order to hide this datastore using permissions you have to perform the following :
Open vSphere -> Inventory -> Datastores -> select the VMFS datastore -> select Permissions -> Click the user or group in the list and set them to "No Access" - Do not propagate. We want this to take effect only on that datastore.
In order to hide this datastore using permissions you have to perform the following :
Open vSphere -> Inventory -> Datastores -> select the VMFS datastore -> select Permissions -> Click the user or group in the list and set them to "No Access" - Do not propagate. We want this to take effect only on that datastore.
You can group them in folder and make no access permission. (do not forget to keep one Admin atleast)
-------------------------------------------------------------------------
Follow me @ www.vmwareguruz.com
Please consider marking this answer "correct" or "helpful" if you found it useful
T. Sateesh
VCIX-NV, VCAP 5-DCA/DCD,VCP 6-NV,VCP 5 DCV/Cloud/DT, ZCP
IBM India Pvt. Ltd
Hi, Why do you want to hide it? What is the purpose for this? I don't really see any advantage of doing this, it is far better to name the datastore with something like local-esxiservername and have a process not to use the local datastore for production VM.
---
If you found this or any other answer helpful, please consider the use of the Helpful or Correct buttons to award points.
vfk
Systems Manager / Technical Architect
VCP5-DCV, VCAP5-DCA, vExpert, ITILv3, CCNA, MCP
We have no need for LOCAL datastore. Our ESXi lives on SD cards and all we use is NFS mounts for the rest. Very Simple. If I have 50 servers there is no need for me to see the local datastore, so now I only see the 5 Connected NFS mounts and that is all. MUCH cleaner.
Installing ESXi 5.1 requires a boot device that is a minimum of 1GB in size. When booting from a local disk or SAN/iSCSI LUN, a 5.2GB disk is required to allow for the creation of the VMFS volume and a 4GB scratch partition on the boot device. If a smaller disk or LUN is used, the installer attempts to allocate a scratch region on a separate local disk. If a local disk cannot be found, the scratch partition (/scratch) is located on the ESXi host ramdisk, linked to /tmp/scratch. You can reconfigure /scratch to use a separate disk or LUN. For best performance and memory optimization, VMware recommeds that you do not leave /scratch on the ESXi host ramdisk.
---
If you found this or any other answer helpful, please consider the use of the Helpful or Correct buttons to award points.
vfk
Systems Manager / Technical Architect
VCP5-DCV, VCAP5-DCA, vExpert, ITILv3, CCNA, MCP
