On my first blog post about Microsoft Hyper-V R2 which you can find here I received a lot of reactions and I always appreciate it to get any type of response (except the 380 spam comments per day). Most of the people agree with the statements and some don’t. I’d like to start this article with stating that it was not my intention to bash Hyper-V as a product, I really think Hyper-V 2012 is a great hypervisor, it’s the management what is creating the issues.
So now with the upcoming version of Hyper-V 2012, which will be released as a beta version on the 29th, I’d like to look at what’s changing in regard to my earlier article. Of course the complete hypervisor management architecture consist of Hyper-V and SCVMM 2012.
The focus of this article is (again) mainly on what it means for VDI scenarios however I think that most of the conclusions will go for whatever scenario.
So what’s new in Server 2012, Hyper-V 2012 and SCVMM 2012 and why does it matter!
The reason for this article is to explain why I don’t like Hyper-V R2 in a production scenario especially for VDI. In a next article I will go into detail about why I think Hyper-V v3 is likely and hopefully going to proof me wrong!
The people I work with closely know I tend to hate Hyper-V R2 for production (VDI) scenario’s and I will start with explaining why. The short version is that you need to many components to manage the hypervisor which leads to technical issues.
To finish the Powershell Microsoft Active Directory blog post series here is a script which I used for a customer. The script is used for moving the Terminal Server Home Drives of all TS users to a Central Directory. The central directory is based on the ServernameShare%USERNAME% value. The TS Home Drive location was set manually and different location were used. We needed to change this to one single location. Doing this manually would take us months so we need to automate these tasks.
With the introduction of Microsoft App-V v4.5 Microsoft introduced the manifest.xml file. To read more about the manifest file please read this blog post by Rodney Medina MVP on App-V and owner of Softrgidblog.com.
The PowerShell App-V script I will show you today will perform two actions. One is adding the Virtual Application to the App-V client by using the manifest file and the second is performing a full load of the added Virtual Applications.
Here we are with already the latest part in the Powershell and Active Directory blog series. In part 3/4 we worked with getting information from AD Object attributes which are not defined in the schema. In this part we will work on modifying the settings on these attributes.
Back again with a new post in the Powershell and Active Directory series of posts. Remember when I said I will show you how to work with attributes that are not schema attributes? By default you can do a $var.schemaatrributename like $user.name or $user.DistinguishedName. This is not possible for for example the TerminalServiceHomeDrive attribute because this strange enough is not a schema attribute.