Hi Robert,  Based on the following MS article: [URL] this is the default behavior for your OS based on the SAN Policy.  Also you can check the white-paper from EMC: EMC Symmetrix with Windows Server 2003 and 2008 Best Practices planning on p. 20-21.  Regards, Kleanthis
When we provision a windows host on a VMAX we present a 50Gb boot lun at lun 0.  When storage is presented on the initial install lun 0 is marked as read-only and the intel admin has to use the diskpart utility to clear the attribute.  If we only present just a lun 0 it is not marked read-only; this happens when we present the boot lun and additional luns.  This is all prior to loading the operating system or anything on our standard HP server with emulex LP11000/LP12000 HBA's.  This is on a VMAX using thin provisioning and masking views; director flags are preset on at the HBA level.  I am trying to find out what is causing the read-only attribute to be picked up by the server as the disk is read/write on the storage array.  HP server model is 380/580 Emulex HBA LP11000/12000 Windows 2008 R2 64bit VMAX 20K runing 5876 enginuity Thin provisioning Masking view with dual pathing Boot from SAN
Microsoft boot from SAN lun 0 read-only attribute