Posts Tagged ‘2012’

So, my journey with Windows Server 2012 has started. The primary focus of my company’s journey is Hyper-V3. So far, the results are impressive. We are running a cluster consisting of 4 nodes connected to a DAS.

So, my lessons learnt so far.

1. As per my previous article, be careful with your Hyper-V NICs. While I am discussing NICs, the inclusion of “Out the box” NIC Teaming is great and so far no issues at all. Works well and allows us to simplify the administration of our Virtual switches and allows for more tolerance in terms of the loss of a NIC. Before, should we loose a NIC, all VMs attached to that NIC would loose connectivity, that is now a thing of the past and our NIC Teaming is fully supported by Microsoft. NICE!!!

2. Increased VHD hard drives, this is achieved by introducing a new type of file format called a .VHDX which allows for “Virtual Hard Drives” larger than 2TB. This works nicely and I have personally created a few VHDx’s larger than 2TB. There is no little “gotcha”, or at least this was in my environment. The creation of this .vhdx file is rather time-consuming and very IO intensive with a DAS. I will try to remember to update you when I try this same procedure on my Equallogic SAN. However, for now, I would recommend you test this process first and see if you run into the same IO issues as I did, before creating numerous .vhdx’s in your production environment.

3. Virtual CPU increase. This has been particularly helpful with our process of creating a new environment. It is quite amazing how much more “CPU” can help with this. Finally I could create a VM with over 2TB of usable space in one drive and have more than 4 vCPU’s, what a pleasure. So I would create my “Core Services” and throw massive CPU and RAM at the VMs to create them and update, once completed I would remove the additional resources and then “sweat” the VMs.

4. Hyper-V Replica. This is a great tool for us and almost feels like it was custom written for us. I guess pretty much everyone is thinking that. However, there is a slight spanner in the works for us. By this I mean a little bit of a re-think in terms of how we present storage especially to the VMs which we want to have as part of our “DR Cloud” if you will. We present a lot of our additional drives directly via iSCSI, This is great and iSCSI works well, VERY well. However when you are trying to think about a DR situation, it adds complexity as you can replicate the VM only, you then need to replicate the presented iSCSI volumes and then reconfigure the network cards. Hence the “re-think” we are looking at a better way to work around this. We want and need Hyper-V replica.

ODX Offload. This is one I am waiting to test, our SAN Vendor has promised this in the next release of their firmware. More to come on this as soon as I can give some more information on this.

More to come I promise,

Follow me.

facebook-small322252222 twitter-small322252222




So, my journey with System Centre Service Manager 2012 Beta has begun and so far I have indeed found some funnies.

I will be blogging about them, to make everyone else’s life a little bit easier and in the hope of better product adoption for this product. It is simply put a fantastic product.

Ok, so the first time I ran the upgrade (remember I have a pre-prod environment), so I was able to rollback and did not have to follow Disaster Recovery with the Failure. I will cover the Disaster Recovery steps that I will follow in Production if I have an issue.


So, like I was saying, I ran into a Reporting Services error when upgrading the Data Warehouse. So I rolled back to a previous state as I am using VMS. However, to resolve this particular issue, I ran the upgrade again. However, this time I opened the SQL Reporting Services webpage and allowed the reporting services webpage to load to completion before running the upgrade.

Reporting Services

I suspect due to the limited specs on my virtual environment, the slow opening and hence communications with the Reporting Services caused my first failure. The second attempt was perfect.

I now had SCSM 2012 Beta Data Warehouse.

So, here is a breakdown of what I did.

1. Install Cumulative Update 2 for System Centre Service Manager 2010 SP1

2. Install Windows Server 2008 R2 Service Pack 1

3. Backup Encryption Key

4. Restart Server

5. Check the status of SQL Reporting Services (services.msc)

6. Check the status of Reporting Service (web site). First load of this website was VERY slow.

7. Disabled Data Warehouse Jobs

8. Waited 10 Minutes

9. Run the Upgrade

10. We have successfully upgraded the Data Warehouse Server.

11. The only thing I did differently this time, I left the reporting services website open the whole time of the upgrade process.

With Analysis Services(Cubes), Permissions are controlled differently. Open SQL Management Studio, and ensure that you connect to Analysis Services and NOT Database Engine and then specify the SQL Server and assign permissions as needed so that people can/cannot access Cubes within Service Manager 2012 Console.

More to follow soon on the Management Server.

Follow me

facebook-small32225 twitter-small32225