26 avril 2013

vSphere 5.1 update 1 release fixes Storage vMotion rename “bug”

vSphere 5.1 update 1 is released today which contains several updates and bug fixes for both ESXi and vCenter Server 5.1. This release contains the return of the much requested functionality of renaming VM files by using Storage vMotion. Renaming a virtual machine within vCenter did not automatically rename the files, but in previous versions Storage vMotion renamed the files and folder to match the virtual machine name. A nice trick to keep the file structure aligned with the vCenter inventory. However engineers considered it a bug... [Lire la suite]
Posté par jcdemarque à 11:17 - - Permalien [#]
Tags : , , ,

30 janvier 2013

Storage vMotion does not rename files?

A while back I posted that 5.0 U2 re-introduced the renaming behavior for VM file names. I was just informed by our excellent Support Team that unfortunately the release notes missed something crucial and Storage vMotion does not rename files by default. In order to get the renaming behavior you will have to set an advanced setting within vCenter.. This is how you do it: Go to “Administration” Click on “vCenter Server Settings” Click “Advanced Settings” Add the key “provisioning.relocate.enableRename” with value “true” and click... [Lire la suite]
Posté par jcdemarque à 15:17 - - Permalien [#]
Tags : , , , , , ,
19 novembre 2012

How to tackle the default database in Exchange 2013

The steps are the same, as in the 2010 world.   As in Exchange 2010, installation of 2013 Mailbox role creates a new mailbox database with a name “Mailbox Database *”, where * represents a long number. Exchange administrators prefer to follow a naming convention and keep things clean. Easiest will be to rename the default database to something that suits your naming convention. Click the Edit button and rename the database & hit the Save button. --> Please see the rest on the blog... [Lire la suite]
Posté par jcdemarque à 22:40 - - Permalien [#]
Tags : , , , , , , ,