Yet Another IT Professional Blog

Windows 10 is coming and Microsoft is pushing out its updates to prepare our computers for this fresh operating system from Microsoft. But do they really need to be that aggressive so that our existing services stops working? Frustrating monday!

This is a storage performance report that I have done on 3 different storage types. I was curious to see the performance difference between different types of iSCSI storage units. I wanted to share the results with others because when I wanted to compare my results with others, I was surprised to see that there are a lot of people discussing about storage technologies and all but no one is actually sharing their benchmarks openly. Because, a storage benchmark can vary a lot depending on your environment, I am going to list my setup so you can compare these results to your own environment as close as possible.

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 am studying for an upcoming Microsoft exam #70-411 and I was practicing the new WDS (Windows Deployment Services) features in the Windows Server 2012 R2 and I ran into a little problem.

Yep... Another update and another bug. I just applied this months updates on my computer at home and guess what? It caused almost a "fatal" error on my VMWare Workstation virtual machines! As soon as my computer boots, I tried to fire one of my vms and I got the following scary message.

Altough it's been a while that Windows 8 is out on the market, I never had to play around with the Windows 8 images and syspreps as I had to with Windows 7. I decided to prepare me a nice updated image of Windows 8 in a vm and sysprep it and use it as template for my lab environment. The plan is simple...