Yet Another IT Professional Blog

I’m a big fan of easy deployment, scripting, automating etc… Therefore I love deployment tools. I am constantly using tools like Microsoft System Center, WDS, MDT, etc… Thanks to these kinds of tools, I can be alone and have the workforce of an IT army :)

I am not sure if this happens under all circumstances but I wasn't able to use the boot.wim file from a Server 2012 R2 setup media. In my WDS server, I added a boot.wim file from the Server 2012 R2 setup ISO as a new Boot Image. I used a vm to boot into the PXE server and try the new boot image but I got the following error; File: \Windows\System32\winload.exe Status : 0xc000000f Info: The selected entry could not be loaded because the application is missing or corrupt.

I have a VMDK file that was used for a Windows Server VM as a secondary disk to store only archive files. When I had to scrap the VM and redo it from 0. As any lazy admin would do, I tried to be smart and just reinstall the OS on a different VMDK and copy over the secondary VMDK, rename it, attach it to the virtual machine and off you go… Things are never as easy as you imagine it would be with computer systems J . Here is another adventure of just a renaming simple VMDK file; If VSphere Gui doesn’t let you rename a file, you can do it through a PuttY ssh session;  Open an SSH session to one of your hosts.   Browse to your DataStore which has the VMDK file. cd /vmfs/volumes/DatastoreName/originalname Use the following command to rename a file;    vmkfstools -E "originalname.vmdk" "newname.vmdk" For more information about manipulating files in datastores or using the “vmkfstools”; http://kb.vmware.com/selfservice/microsites/search.do?c...