Year: 2014
Carrying on the theme from the Active Directory FSMO roles article, I thought I would put a little information around another really important AD component – the Global Catalog server.
The following article covers what is the Active Directory Global Catalog server, why it is important and the best practises around its placement…
Every new Active Directory forest/domain requires certain FSMO roles to be available in order for it to function successfully. The good news is that these roles are automatically installed by default. Although they are installed automatically, it is still important to understand the purpose of each FSMO role and where best to place them within your environment.
The following article outlines the function of each of the Active Directory FSMO roles, their purpose and more importantly some considerations around their placement.
Important Update
As of September 2015, I have released version 2 of my PowerCLI Script Template, which includes a number of improvements over this version, in particular the use of the new PSLogging PowerShell module that significantly improves the creation and management of log files. This version of the template is no longer supported or maintained, so please upgrade to the new version today!
Version 2 of the template is available here – PowerCLI Script Template v2.
A while a go I posted up my PowerShell Script Template which turned out to be pretty popular with fellow PowerShellers.
I recently create another slightly modified template when working with PowerCLI, so I thought I would share it here. Here is my PowerCLI Script Template to be used for all your VMware scripts…
When you rename a virtual machine in VMware, the VM’s folder and files on the datastore do not get renamed automatically. This can make troubleshooting difficult as it will be almost impossible to find a renamed VM whilst browsing a datastore.
To fix this, you normally do a Storage vMotion of the VM, which would rename the folder and all of the corresponding VM files to the new name. Unfortunately in vCenter 5.0 and 5.1 a Storage vMotion does not rename the VM files, it will only rename the folder.
There is a fix for this so that the VM files get renamed as well. Here is how to do it…