I believe in Hyper-V!

System CenterCategory Archives

Windows Server and System Center 2016 now available! #MSIgnite

Hi there,

Today on Microsoft Ignite the Windows Server team announce that they have released the Windows Sever and System Center 2016 to the public. I need to mention this is Evaluation edition. In mid-October, Windows Server2016 will be GA (generally available). GA is the RTM version, it means the final product.

So, what to do now? Download, try, enjoy Smiješak s namigivanjem!

You can download the evaluation bits from the following links:

Windows Server 2016:

System Center 2016:

Before you install new version of Windows Server 2016 and System Center 2016 read documentation and you will find out what’s new in this great new products from the Microsoft kitchen Smiješak.

Just one more thing. You can follow what’s new in IT world here #MSIgnite.



Automatic Deployment of TeamCompanion through System Center 2012 R2 Configuration Manager

Last week I received a request from one of our customers about the options for automatic deployment of TeamCompanion to end users. In this blog post I would like to explain and show you how this can be achieved using System Center 2012 R2 Configuration Manager. As always, I’ll lead you through the procedure using lots of pictures :) .

Which prerequisite do we need to start our procedure? An Active Directory, the System Center 2012 R2 Configuration Manager, a couple of domain members, and goodwill.

Additionally, your developers need to prepare appropriate packages as follows:

1. SQLSysClrTypes.msi (download from here)
2. ReportViewer.msi (download from here)
3. Ekobit.TeamCompanion.Installer.exe
4. TeamCompanionSetup.exe

The order of the packages is important, so please create exactly in the order stated above.

If you don’t know how to create Applications and Packages here is a guide.

Do the same for the ReportViewer.msi, Distribute Content and Deploy applications.
Now we need to create three TeamCompanion packages with this order:
– TeamCompanionSetup /S /C
(where /S mean silent and /C is for a user)
– TeamCompanion /S

Do the same for the rest of packages, Distribute Content and Deploy applications.

After you have prepared all this, you are ready to implement your automatic deployment of TeamCompanion

Step 1.

Open the System Center 2012 R2 Configuration Manager console and go to Software Library|Applications and create two applications (Microsoft System CLR Types for SQL Server 2012 & Report Viewer) like in the picture.

After you have created Applications, you need to Distribute Content and you need to Deploy applications to the selected clients in the environment.

Step 2.

Create three packages (TeamCompanionInstaller.exe, TeamCompanionSetup /S /C and TeamCompanion /S).


You are finished on the System Center 2012 R2 Configuration Manager side. Let’s look the client side now!
On the client side, Outlook 2013 and Team Explorer 2013 must be installed to be able to push complete package installation of TeamCompanion.


Finally, open Outlook to access TeamCompanion features, connect to your Team Foundation Server and enjoy ;)


For more information about TeamCompanion please visit our web page www.teamcompanion.com

Enjoy the day ;)



Issue with Migration of Virtual Machines |System Center 2012 SP1 Virtual Machine Manager|

Today I tried migrate virtual machine from one stand alone Hyper-V host to another through System Center 2012 SP1 Virtual Machine Manager and got errors like in the picture below.
The first error was: The credentials supplied to the package were not recognized…
and the second was: Live Migrating Hyper-V virtual machines may fail with error 0x80070569


After a little of investigation I found resolution on Ben Armstrong blog and on Microsoft support site. So, what we have to do?

1. Step
– Open Properties on the Hyper-V host
– Go to the Host Access
– Add Run As account created earlier


2. Step
– On the Domain Controller create new GPO with the parameters like in the picture below and Link in OU where your Hyper-V hosts are.


– Update group policy on every Hyper-V host | gpupdate /force |. (You may need to wait several minutes for Active Directory replication to occur).


We are done! Open VMM Console and migrate VMs as you wish.



Voila, VM is migrated. Of course, migration time depends on the virtual machine size.

Enjoy in day!