[http] sslCAInfo = C:/Users/<username>/AppData/Local/Programs/Git/mingw64/ssl/certs/ca-bundle.crt

As Debian is not in the list of the endorsed distributions, if you want to run a Debian based VM in Azure, you have to build it yourself. The whole process is detailed on the following page but some additional guidance my help some folks: https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-create-upload-vhd-generic/

I'm going to walk you through the steps that I took to create my Debian 7.0 image in Azure:

1. Create a virtual machine with hyper-V (or other virtualization tools) and install Debian
2. Configure the VM
3. Upload the VHD to azure and create your image

1- Create your VM

I've downloaded the network installation ISO from this location: https://www.debian.org/distrib/netinst (AMD64 version)

Then you need to create a VM with a fixed VHD, I'd recommend to size it at 30 GB to make is fast enough to upload and still large enough to handle any future updates but this is your call at the end of the day. The maximum that you can have is 127 GB. This is how it looks on Hyper-V.

Then proceed with the installation of your distribution of Debian, including the default disk partitioning. In my case, I have selected the default configuration all the way until the selection of roles.

For the selection of roles, I've unselected the "Debian desktop environment" and "Print Server" and added the "SSH server". Once the VM is in Azure, SSH will be the only way to access and configure it so make sure you add this.

Wait until the end of the installation and you are ready to proceed to the next step.

2- Configure the VM

• First we need to modify the kernel configuration to ensure that the console messages are redirected to the first serial port.

Edit the /etc/default/grub file and modify the GRUB_CMDLINE_LINUX parameter as follows:

GRUB_CMDLINE_LINUX="console=ttyS0 earlyprintk=ttyS0 rootdelay=300"

You can find additional information on the configuration of grub on this page: https://www.gnu.org/software/grub/manual/html_node/Simple-configuration.html

• Second we need to install the Azure Linux Agent. The official source can be found on github: https://github.com/Azure/WALinuxAgent

Before we need to install git and sudo with the following command lines from a privileged prompt:

• apt-get install git –y
• apt-get install sudo -y

Clone the github repository to the directory you like with: git clone https://github.com/Azure/WALinuxAgent

This should create a WALinuxAgent directory where you have launched the command.

Then you need to copy the waagent file to /usr/sbin/waagent

Change the execution rights and then execute /usr/bin/waagent –install

You can see the logs associated to the installation of the Azure Linux Agent in /var/log/waagent.log

Then modify the /etc/waagent.conf file to set the agent parameters as follows:

• ResourceDisk.Format=y
• ResourceDisk.Filesystem=ext4
• ResourceDisk.MountPoint=/mnt/resource
• ResourceDisk.EnableSwap=y
• ResourceDisk.SwapSizeMB=2048 ## NOTE: set this to whatever you need it to be.

Finaly, run the following commands:

• sudo waagent -force -deprovision
• export HISTSIZE=0
• logout

and then shutdown the VM.

3- Upload the disk to Azure and create the image

Ensure that on the machine where you have created the VM you have the latest Azure powershell cmdelts and run the following:

Add-AzureVhd -Destination https://mystorageaccount.blob.core.windows.net/mycontainer/debianimage.vhd -LocalFilePath 'D:\VMs\DEBIAN\debianvhd.vhd'

Make sure that you adjust according to your environment the destination url and the local file path. The upload will take some time depending on your network bandwidth.

Once the vhd file has been uploaded, you can create your azure image. Under the "Virtual Machine" section, select the "Images" tab.

Then click "create" and fill the fields. The VHD URL points to the file that you have just uploaded.

4- Use the image

Your image is ready to be used as any supported Azure images from the gallery under "My Images" to create a new VM in Azure.

5- Additional information

You can get more information on the following links:

• Create non endorse Linux images for Azure: https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-create-upload-vhd-generic/
• Git repository for WALinuxAgent: https://github.com/Azure/WALinuxAgent
• Azure Linux Agent user guide: https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-agent-user-guide/
• Grub configuration: https://www.gnu.org/software/grub/manual/html_node/Simple-configuration.html

With those tools, you have several options:

• Deploy a supported Linux distribution and use Chef to manage this virtual machine (also called node)
• Deploy a Windows virtual machine with the Chef agent installed
• Use knife to deploy Virtual Machines in Azure
• Integrate in a recipe the configuration of Azure resources

In this post, I'll explain how to use Chef to apply a specific configuration to a Windows machine in Azure using a configuration file. This is done with the three following steps:

1. Create the cookbook (the file that defines what should be applied on the VM)
2. Create the VM in Azure and indicate to that VM how to get it's configuration
3. Monitor the deployment

In this example, let's deploy a Windows VM running Apache. You can use similar a approach to deploy any roles and features or third party applications on you VM.

The Azure Configuration

Chef works with a client running on the machine that needs to be configured (a Node) and a Run List either on a Chef Enterprise server or hosted. On Linux, Chef uses SSH to connect to the node and deploy the client. With Windows you can use WinRM to perform the same operation however, the integration of Chef with Microsoft Azure facilitates this process.

In Azure, Chef appears as an extension of the virtual machines. To deploy the client, you only need to select the check boxes as follows.

Before we can actually deploy a VM using that approach, we need to take some preparation steps.

The configuration file

Chef uses configuration files, called cookbooks, to apply settings on the system. Here are the steps that we need to perform to create the configuration file that will install Apache, configure it and open the proper Firewall port on the system:

1. You need to have knife installed on your machine. Go to https://getchef.com to install it on your machine and define your local repository.

    

2. Add to your repository the "windows" cookbook that has been developed by OpsCode.

   This cookbook that is freely available will facilitate the next steps. Here is where you can access the repository: https://github.com/opscode-cookbooks/windows.

    

3. Create your own cookbook

   Knife cookbook create MyAzureCookbook

    

   

4. Modify the cookbook that you have just created

   Open the MyAzureCookbook\recipes\default.rb file to indicate the steps that needs to be done to configure the system.

    

   This is how the file will look like (be careful, it is case sensitive):

    

   # This line will install Apache2 from the current source on internet
   windows_package 'apache2' do
       source 'https://apache.osuosl.org//httpd/binaries/win32/httpd-2.0.65-win32-x86-openssl-0.9.8y.msi'
       action :install
   end
   

   # Copy the configuration file for apache in the right location
   cookbook_file 'C:/Program Files (x86)/Apache Group/Apache2/conf/httpd.conf' do
       source 'httpd.conf'
   end
   

   # Install Apache as a service on Windows using the command line
   windows_batch "ApacheAsService" do
       code <<-EOH
       "C:\\Program Files (x86)\\Apache Group\\Apache2\\bin\\Apache.exe" -k install
       EOH
   end
   

   # Create the file from a template that will be home page of our site
   template "C:/Program Files (x86)/Apache Group/Apache2/htdocs/index.html" do
       source "index.html.erb"    
   end
   

   # Enable Port 80 on the Firewall of the VM
   powershell_script "FWPort80" do
       code <<-EOH
       New-NetFirewallRule -DisplayName "Allow Apache" -Direction Inbound -Program "C:\\Program Files (x86)\\Apache Group\\Apache2\\bin\\Apache.exe"
       EOH
   end
   

   # Ensure that the apache service is started
   service "Apache2" do
       action :start
   end
   

   You also need to create two files:

• MyAzureCookbook\templates\default\index.html.erb

  <html>
       <body>
          <h1> Welcome to My Demo </h1>
          <h2> Hello, <%= node["fqdn"]%> !</h2>
          <P>
              This server has <%= node["kernel"]["cs_info"]["total_physical_memory"].to_i / 1048576 %> MB of memory.
          </P>
       </body>    
  </html>

• MyAzureCookbook\files\default\httpd.conf

  Copy the default httpd.conf file and modify or verify the following lines:

  ServerRoot "c:/Program Files (x86)/Apache Group/Apache2"
  ServerAdmin test@demo.com
  ServerName AzureVM1:80
  

  Finally you need to modify the file \MyAzureCookbook\metadata.rb and add at the end

  depends 'windows'
  

1. Upload all the cookbooks to the server.

   knife cookbook upload MyAzureCookbook
   knife cookbook upload windows

   

   If your cookbook has a syntax error, it will be detected at that time.

How to deploy a Windows VM

In the previous steps we have prepared our configuration files, now let's walk through the deployment itself.

From the Azure management portal start to create a new VM from the Gallery and select a Windows 2012 R2 image.

Define the properties of the VM. In this sample, we'll use "AzureVM1" for the name of the VM and "azureuser" for the administrator.

The VM can be associated with an existing cloud service or a new one. Either cases, make sure you add HTTP (port 80) on the endpoints so that the requests can reach the server.

In the last configuration step, you now need to provide two files:

• Client.RB: The client.rb file is more or less the configuration file of the chef client. It has the URL of the server to use to download the recipes, the name of the node that will be used in Chef, the location of the cache of the Chef client.

  In the following example, the machine will be represented in Chef with the name of "AzureVM1" and it will be attached to the organization called "dpedemo". The name of the node does not need to be identical to the name of the VM. However, doing so makes it easier from a management point of view.

  log_level :info
  log_location STDOUT
  
  chef_server_url https://api.opscode.com/organizations/dpedemo
  validation_client_name "dpedemo-validator"
  client_key "c:/chef/client.pem"
  validation_key "c:/chef/validation.pem"
  
  file_cache_path "c:/chef/cache"
  file_backup_path "c:/chef/backup"
  cache_options ({:path => "c:/chef/cache/checksums", :skip_expires => true})
  
  node_name "AzureVM1"
  

• Validation Key (.PEM): This file is the validator file that you get from your Chef server or your Chef hosted tenant when you download the starter kit for your organization. In my example, I'll use the file called "dpedemo-validator.pem". Your file sill look like "<your_organization>-validator.pem"

The Run List is the list of recipe that will be used to configure the VM by the Chef client. In this example, we use only one run list but you can add several in the order in which they should be applied.

Note: You can store you configuration file and your validation keys in a storage account to facilitate the deployment and not rely on the host that you are using to deploy the Node.

Monitoring the deployment

During the deployment of the above VM, you will see the following stages of the VM:

The VM is being created and the resources provisioned:

Once the VM has been deployed, the process goes to deploying the extensions. This is when the Chef client is being deployed.

The Chef client registers the node and you can see it appearing in the Chef administration tool. The Cookbook that we have specified in the run list on the Azure portal is reported in the run list on the Chef administration tool.

On the Azure portal, in the dashboard of the VM you can verify that the Chef client has correctly executed the recipe by looking at the extension status.

Finally, let's try to access the cloud service.

Conclusion

There are other options to deploy a desired configuration to a Windows Virtual Machine which we will cover in additional posts. However, if you have already invested in Chef from Opscode and already developed several recipe and cookbooks, this is a way to leverage your investments while doing devops on Windows Azure.

Additional resources

To learn more about the various technologies that we have covered in this post, you can visit the following sites.

Windows Azure:

• General information on Azure: https://azure.microsoft.com/
• Deploy Azure Virtual machine : https://azure.microsoft.com/en-us/documentation/services/virtual-machines/
• Managing the Windows firewall with powershell : https://technet.microsoft.com/en-us/library/jj554908.aspx

Chef / Opscode:

• Screen casts on Chef : https://learnchef.opscode.com/screencasts/fundi-webinar-week-1/
• Creating your first cookbook : https://learnchef.opscode.com/create-your-first-cookbook/
• Creating Windows cookbooks : https://blog.postmarkapp.com/post/74863816767/using-chef-on-windows-is-easier-than-you-think

MSOpenTechnologies:

• https://msopentech.com/
• Using chef to manager azure resources : https://msopentech.com/blog/2014/03/31/using-chef-to-manage-azure-resources/
• List of content on Chef project : https://msopentech.com/opentech-projects/chef/

Products and industry trends.

I believe that 2013 will be remembered as the year in which the traditional release cycles accelerated.

Microsoft has released the SP1 then the R2 version of System Center and Windows Server just about one year after launching the previews version. Many new services for Azure have been made available like Windows Azure Active Directory, the long waited IaaS (Infrastructure as a Service) and several hybrid services like Windows Azure Backup or Hyper-V recovery Manager. This list is just a brief overview of the major updates that have been made available during the last year.

I'm impressed by the speed at which the new services and updates are released and it is not going to slow down in 2014. The approach that we have followed over the last decades consisted of getting a new version of a system (an application, a management suite or simply a new operating system), validating it in the corporate environment then planning a massive deployment. That usually became the company standard for few years.

This approach is not compatible anymore with today's business requirements. The current needs are about constant evolution. The IT must be able to deliver new services constantly. The idea of having a stable environment for few years is more an exception than the common ground. This does not means that the IT should become less reliable, the IT of the future will have to handle continuous changes, starting with the infrastructure.

Is a continuous change of the infrastructure really compatible with reliability? 10 years ago, I probably would have a more mitigate answer, but today, the new building blocks of the IT simply have this characteristic at their foundation. For example you can evolve a virtual machine from Hyper-V 2012 to Hyper-V 2012 R2 with no downtime, you can also consider Active Directory with continuous upgrade approach since the beginning.

One of the secrets of continuous change is automation. The cloud approach has driven the maturity of automation during the recent years because it brings the human intervention at a more valued level: the creation of the automation pieces. With automation the OS becomes a commodity and scaling in or out an application is not an issue anymore.

The IT teams will need to adjust their organizations to handle those changes in the proper way:

• The IT needs to consider more that failure is part of the software. They will need to put in place structures and processes that mitigate the impact of the failures whatever environment they chose to run on.
• IT Pros will need to learn this new approach of systems management and deployment.
• Root cause analysis of the crash of an OS will not be necessary anymore.

This new approach requires to learn how to implement highly automated systems at the risk of struggling with more work to perform with less resources and less time. The job will undergo a certain transformation that not only includes those news technical skills but also includes a good understanding of the company business.

The transformation of the job

As the business needs of the enterprises evolves, so does the IT teams. Today, the business will go to a public cloud providers to build the solutions that the traditional IT cannot offer or built, creating a Shadow IT (https://en.wikipedia.org/wiki/Shadow_IT). According to Forrester, shadow IT is already happening in your companies, you just not know about it … yet. The main driver for that is that the IT departments do not answer the business needs.

The IT department can try to resisting to this change and may try to use their authority (block access to the providers, write a policy, etc.) but it will only make things worse. A better approach is to embrace the change and leverage the knowledge gained by running and managing applications on-premises. This added value should help getting the application aligned with the company's requirement like privacy, backup and recovery policies. Change has always happened in the IT industry and today, the role is evolving from managing servers to managing clouds and delivering the best possible service to the business.

I believe that 2014 is at the inflexion point for this transformation. This is the moment to jump on the train and evolve your skills. There are some regulation requirements, complexities, network limitations, etc. that will limit the evolution to a full public cloud environment and will require a coexistence between a public environment and on-premises resources. However the pressure to be more efficient in managing the local resources will be higher and the Private Cloud is the way to go. We will then see the development of a hybrid model that interconnects the private and public environments.

Implementing a private cloud and understanding the hybrid model takes time and requires new competencies. They are rare on the market today and it's a good time to gain them. For example, the MCSE Private Cloud certification (https://www.microsoft.com/learning/en-us/private-cloud-certification.aspx) is one of the assets to prove your ability to deploy and manage a Private Cloud. It could be one of your objectives for this new calendar year.

The IT Pros have to give the right framework to the business teams so that the latter can evolve at the right pace while following the company policies. This approach will help reducing the frictions that may exist between the operations teams and the development teams while giving the infrastructure teams a more strategic position. They will have a clearer view on the cost of each application. At the end of the day, what matters to the business is to be able to use a platform that has predictable costs, aligned with the business usage. The evolution to the clouds facilitate this alignment.

The Microsoft view

The hybrid model that leverage the benefits of the public cloud with the customizability of the private cloud bring the ability to better follow the business requirement.

Microsoft has a symmetry between its on-premises products and its public cloud services. This means that all our products leverage the knowledge and best practices gained from running and operating them in the public cloud. For example you can take a machine running from your private cloud and move it to Windows Azure and vice-versa. The availability set check box in a VMM Service Template bring the availability group concept from Azure to your datacenter.

Using the same building blocks on both sides makes the hybrid approach simple to implement and reduce the learning curve for any IT Pros that needs to extend the resources from its datacenter. Because of this symmetry, not only at any time you can use windows azure and step back in case the business requirements have evolved but you can also expect a short ROI (Return Over Investment).

The hybrid approach allows to seamlessly port existing application from you datacenter to Azure and back. The backup that is integrated with Windows Server 2012 R2 and System Center DPM 2012 R2 leverage Azure as a location to secure your data off-premises. SQL azure Data sync integrates the on-premises SQL databases with SQL Azure databases by using a granular mechanism that allows you to select with tables and with rows in each table to replicate and more …

Today you also have appliances like StorSimple that fully integrate the datacenter storage using the traditional interface with Azure and replicate some of the data to the Cloud. It's another approach of the hybrid scenario that can be implemented.

In 2013, Gartner predicted that nearly 50% of the enterprises will have a hybrid cloud implementation in 2017 as indicated by this article: https://www.computerweekly.com/news/2240206459/Half-of-large-enterprises-will-have-hybrid-cloud-by-2017-says-Gartner.

If you look across the stack, Microsoft is today the only vendor that has this symmetry on so many levels.

Conclusion

2014 is going to be another very interesting year!

It is quite clear that hybrid cloud will be a recurring topics. The public cloud consumption is a fact for most organizations today, IT may not yet know about it but in case this is not in the plans yet, they should have a strategy to implement it this year with a framework for its adoption.

The private cloud, if not already in place should be considered with proper diligence to ensure the IT delivers the right services to the businesses with the right timing.

Hybrid will take a bigger place as the usage of the public cloud will grow. The needs for cross-cloud authentication and the requirement to access data across the boundaries of your datacenter will increase. This New Year will bring us a lot of news and several of them will be around the hybrid model.

Happy New Year 2014!

https://msdn.microsoft.com/en-us/library/windows/hardware/dn529133.aspx

Under one single repository you will find all the registry keys, tools and tips to make your Windows Server 2012 R2 perform at its best!

It does not necessarily mean that the server will improve its performance but it may consume the lowest energy for a give performance rate. By following the guidelines that comes in this white paper, you will obtain performance or energy efficiency gains. The settings that are recommended in this document should be take carefully and always have in considerations what hardware you are using, and your datacenter environment.

It also describes each setting and its potential effect to help you make an informed decision about its relevance to your system, workload, performance, and energy usage goals.

It means that if you are a subscriber you can start downloading the binaries and work on your migration procedures in order to be ready for the General Availability of the products.

It also means that you can start testing some of the new capabilities of Windows Server 2012 R2 in your lab. For example:

• Enhanced hypervisor with the generation 2 virtual machines
• Storage tiering to allow a mix of different type of disks to improve speed while keeping the cost of storage down
• New printing capabilities allowing a client to connect to a printer in a branch even if the server is central.
• Remote desktop services
• …

You can read more about the new capabilities of Windows Server 2012 R2 at the following locations :

• https://technet.microsoft.com/en-us/library/dn250019.aspx 
• https://www.microsoftvirtualacademy.com/training-courses/what-s-new-in-windows-server-2012-r2-jump-start#fbid=TuiffRMNuZx
• And don’t forget about some of the videos that explain in more details how things works behind the curtains: https://blogs.technet.com/b/dcaro/archive/2013/06/11/windows-server-2012-r2-first-look.aspx 

The innovation brought by the server are simply enhanced with the new sweet improvements made on the client side with Windows 8.1. Read more about the client improvements at the following locations :

• https://technet.microsoft.com/en-US/windows/dn140266.aspx
• https://www.microsoftvirtualacademy.com/product-training/windows

Download those new versions, test them and implement those new features !

This tool will help you calculate the TCO (Total Cost of Ownership) of deploying a Microsoft Private Cloud vs. a VMware Private Cloud. The tool is very  comprehensive and includes in the equation technical elements like the amount of Gb of storage per VM and non technical data like the salary of the full time employees 

The analysis includes the cost of running systems in a public cloud offering like Windows Azure in the case you want or need to deploy a hybrid solution.

I can only encourage you to use this free tool and compare the results : https://www.datacentertcotool.com/ 

Enjoy building your cloud !

1. Getting the evaluation versions : System Center 2012 R2 and Windows Server 2012 R2 preview can be downloaded at this location : https://technet.microsoft.com/evalcenter/dn205295.aspx 

Please note that VMM 2012 R2 requires the presence of the Windows ADK which can be downloaded at this location : https://go.microsoft.com/fwlink/?LinkId=309908 

2. System requirements: https://technet.microsoft.com/en-us/library/dn281935.aspx 

Note: The self service portal relies on SharePoint 2010 therefore you must install the SSP components on Windows Server 2008 SP1 or Windows Server 2008 R2

3. All System Center products rely on SQL server to store their data. You can find the compatibility matrix of System Center components and SQL on this page : https://technet.microsoft.com/en-us/library/dn281933.aspx

To build my lab, I’ve used the SQL 2012 SP1 version that you can freely download from here : https://technet.microsoft.com/en-us/evalcenter/hh225126.aspx 

Now you are ready to proceed with the installation. I’m not going to walk through all the installation steps.

When you install SQL, pay attention to the Collation settings. If you are going to be in a pure English configuration the default settings are ok but if you are going to manage a multi-lingual environment, please read the following article : https://blogs.technet.com/b/servicemanager/archive/2012/05/24/clarification-on-sql-server-collation-requirements-for-system-center-2012.aspx 

Finally here is the configuration of my lab. All the systems are running in a virtual environment except the host :

In my next post I’m going to explain the System Center configuration that I’ve implemented in order to be able to test almost all the components of this R2 release.

The full study is available here : https://www.gartner.com/technology/reprints.do?id=1-1GJA88J&ct=130628&st=sb 

I regret that the study does not talk much about the hybrid approach and the capacity that the possibility of virtualization platform to deliver it. I believe that hybrid will become more and more used by companies of any size in the future.

In this regards, I think that the Microsoft approach, with a full symmetry between the technologies used to build a private cloud and the ones used in our public cloud services, is unique. No other company has, at this time, a complete offering allowing a customer to move workloads seamlessly from one environment to another, or to deploy and develop a hybrid solution that gets the the compliance and rules from the private cloud while using the elasticity and pay for what you consume of the public cloud.

Happy cloud !

Basically, the issue I had was that my Data Warehouse jobs would fail to complete. At the same time, in the event viewer of my systems I had the following error message :

Log Name:      System
Source:        Microsoft-Windows-Security-Kerberos
Event ID:      4
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SCSMDW.wsdemo.com
Description:
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server smsvc. The target name used was MSOMSdkSvc/SCSMDW. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (WSDEMO.COM) is different from the client domain (WSDEMO.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

In my environment, smsvc is the service account that I’m using for Service Manager. However when I looked at my SPN settings, I had the following :

C:\Users\Administrator.WSDEMO>setspn -Q MSOMSdkSvc/SCSMDW
Checking domain DC=wsdemo,DC=com
CN=SCSMDW,CN=Computers,DC=wsdemo,DC=com
        MSOMSdkSvc/SCSMDW
        MSOMSdkSvc/SCSMDW.wsdemo.com
        MSOMHSvc/SCSMDW
        MSOMHSvc/SCSMDW.wsdemo.com
        TERMSRV/SCSMDW
        TERMSRV/SCSMDW.wsdemo.com
        WSMAN/SCSMDW
        WSMAN/SCSMDW.wsdemo.com
        RestrictedKrbHost/SCSMDW
        HOST/SCSMDW
        RestrictedKrbHost/SCSMDW.wsdemo.com
        HOST/SCSMDW.wsdemo.com

Existing SPN found!

So the situation is that when the Kerberos client tries to validate the authentication, the information he gets from Active Directory are different than the ones that is in the ticket.

Solution applied:

To solve this issue, I took the following steps:

1. Unregister the bad service entry :
   setspn –D MSOMSdkSvc/SCSMDW SCSMDW
   Unregistering ServicePrincipalNames for CN=SCSMDW,CN=Computers,DC=wsdemo,DC=com
           MSOMSdkSvc/SCSMDW
   Updated object
   
2. Register the service entry with the right information :
   setspn -A MSOMSdkSvc/SCSMDW smsvc
   Checking domain DC=wsdemo,DC=com

Registering ServicePrincipalNames for CN=smsvc,OU=ServiceAccounts,OU=demo,DC=wsd
emo,DC=com
        MSOMSdkSvc/SCSMDW
Updated object

I’ve applied this operation for all the service entries that I have found with this error message. then I’ve restarted my servers to ensure that there was no entry in the cache allthough I think it is not necessary.

If you want to learn more about this error message, you can read the following article : https://support.microsoft.com/kb/811889 and this article that explains how the SPN should look like: https://blogs.technet.com/b/kevinholman/archive/2011/08/08/opsmgr-2012-what-should-the-spn-s-look-like.aspx 

You can download System Center 2012 R2 from this location: https://technet.microsoft.com/evalcenter/dn205295.aspx