What’s the difference in provisioning disk on Vmware Vspher

When we are going to create a virtual machine, or when we add a new disk to an existing VM, we are forced to choose the type of virtual disk that we will make available to that machine.

There are currently three types of virtual disk that can be created and made available to virtual machines:

Thick Provision Lazy Zeroed – is a standard “thick” disk, meaning all space is allocated at the time of its creation. In this virtual disk format, any data that exists on the physical device is maintained at the time of creation, and are only “zeroed” as the virtual machine writes its data.

Thick Provision Eager Zeroed – is a “thick” disk that supports some cluster features, such as FT. It also allocates all the necessary space at the time of its creation. The difference to the “lazy” (or flat) format is that the data on the physical device is all zeroed at creation time. The creation time for this type of disc may take longer than the others.

Thin Provision – In this type of disk only a minimum space is used at the time of its creation. As more physical space is needed, the “thin” disk will increase in size, reaching the size initially allocated.

Raw Device Mapping

There is also the possibility of making a RDM (Raw Device Mapping) disk available to the virtual machine. An RDM disk allows a VM to access a storage LUN (Fiber Channel or iSCSI) directly. The RDM disk is actually a .vmdk file created in the datastore that maps to the LUN in storage. It only has some metadata information and notes for the physical disk.

RDM disks can be configured in two different ways: virtual compatibility mode and physical compatibility mode.

In virtual mode, the mapped LUN is presented to a virtual machine exactly as a virtual disk created in a VMFS datastore. The true hardware features of the LUN become invisible to the VM. In virtual mode you can benefit from some features of VMFS, such as “file locking” and “snapshots”.

In physical mode, the VMkernel transfers most of the SCSI commands to the mapped LUN, allowing greater integration of the VM with the LUN. The physical mode is useful in virtualizing machines that have SAN management agent and also in creating clusters between physical machines and virtual machines, or between virtual machines on different hosts.

Continue Reading

How to Enable Minimal Server Interface on Windows Server 2012 R2

Hello friends.

In the last weeks in my studies on Windows Server I found this feature in our servers Windows is in a cluster with medium to large can bring notes reductions of features such as memory and cpu.

What is affected when I uninstall the Graphical Server Shell?

In some cases, when you uninstall the Server Graphical Shell, Windows features that depend on Server Graphical Shell will also be uninstalled. In Server Manager, a pop-up dialog box will warn you about what will be uninstalled.

Methods of installation?

  1. Server Core – always installed and enabled; the baseline feature for all Windows Servers
  2. Server Graphical Management Tools & Infrastructure – functionality for Minimal Server Interface
  3. Server Graphical Shell – equivalent to Server with a GUI

How to enable the Minimal Server Interface in Windows Server 2012?

You can enable or disable the Minimal Server Interface through the GUI or from the command line using Windows PowerShell.

Using the Remove Roles and Features Wizard to Configure Windows Server Management Interfaces

Or to switch from a full GUI to a server interface using PowerShell, you must use the Remove-WindowsFeature cmdlet:

Remove-WindowsFeature -Name Server-GUI-Shell -Restart

To change the minimum server interface to a full GUI, you can use the Get-WindowsFeature and Install-WindowsFeature cmdlets:

Get-WindowsFeature Server-GUI-Shell |Install-WindowsFeature -Restart

Important to remember that after applying these options the server must be restarted to validate the configurations.

Any questions or problems just look for me.

Continue Reading

How to Enable Access-based enumeration in Windows Server 2012

First you need to add the File And Storage Services role to the server and reboot the server.
Then go to File And Storage Services in System Manager.

Press Shares, select your shared folder, right-click and press Properties.

Under Settings you will find the Enable access-based enumeration-setting.
Enable it and Apply your changes.

Or

To enable access-based enumeration by using a command line

1-Open a command prompt window on a server that has the Distributed File System role service or Distributed File System Tools feature installed.

2-Type the following command, where <namespace_root> is the root of the namespace:

dfsutil property abe enable \\
<namespace_root>

 

Thoughts and opinions here are mine.

 

Continue Reading

How to remove protection on OU in Windows Server 2012

Message:You do not have sufficient privileges to delete OU, or this object is protected from accidental deletion.

  1. Open Active Directory Users and Computers.
  2. Click on View then click on Advanced features.
  3. Right-click on the OU and select Object ta
  4. Uncheck the option Protect object from accidental deletion
  5. Remove the OU.

Remark: If this OU has AD objects under it, you will not be able to remove it if one of the objects is protected against accidental deletion.

Is a very simple solution.

Continue Reading

How to Create a Storage Pool with PowerShell

The three things that are required are:
The storage pool name
Which disks to use to create the pool?
The storage subsystem (Storage Spaces)

The cmdlet we use to create the storage pool is New-StoragePool. While the only
The name of the storage pool will be passed through the “FriendlyName” parameter.

The disks to create the storage pool on will be passed into the New-StoragePool in the “PhysicalDisks” parameter. Which are either pooled, or can be made even easier using the “-IsPooled” parameter (which will either provide all of the disks that are already pooled, or if set to false will all return
The Get-PhysicalDisk cmdlet can be run as part of the -PhysicalDisk parameter, or can be run previously and the results stored in a variable. If creating a script that will be reused, it’s advisable to use a variable, so that it is easier to read and understand.

Code below:

$s=Get-StorageSubSystem

$disk=Get-PhysicalDisk -FriendlyName PhysicalDisk16

New-StoragePool -FriendlyName Pool1 -StorageSubSystemUniqueId $s.UniqueId -PhysicalDisks $disk

That is all that is needed to create a basic storage pool. However, these optional parameters for New-StoragePool may provide some benefit.

Continue Reading