Two solutions are possible to show the interface in English:

1. Change your OS  language from your control panel (Regional settings). Yes, that’s a solution, but of course you already thought about that and don’t want to. So, solution 2:

2. Rename the language pack folder within the install directory of your management console. Default language pack locations of SCCM and SCVMM 2012 management console:

• System Center Configuration Manager 2012: C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\[language_code]
• System Center Virtual Machine Manager 2012: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\[language_code]

Close the management console, rename the language pack folder corresponding to your current OS language, restart the console and the default language (English) will be shown.

I found this article, which was very helpful: http://www.altaro.com/hyper-v/error-804-hung-template-creation-in-scvmm-2008-r2/.

These instructions are also working for SCVMM 2012 SP1. Basically, you will adjust one value in your database:

1. Connect to your VMM database with SQL Management Studio
2. Locate the tablet dbo.tbl_WLC_VObject
3. Edit the Top 200 Rows
4. Find the corresponding template name in the column ‘Name’ and adjust the value in ‘ObjectState’ from ‘3’ to ‘0’
5. Restart the Virtual Machine Manager service and you will be able to create the template again

1. Open the registry and navigate to: HKCU\Software\Microsoft\Office\Outlook\Addins
2. Find the corresponding key which matches the Outlook add-in you have installed (for example: HKCU\Software\Microsoft\Office\Outlook\Addins\OcOffice.OcForms)
3. Right-click on the key and choose “Copy Key Name”

In every subkey you will find a registry value “LoadBehavior”. By default it has the value “3”. Every value is explained here: http://msdn.microsoft.com/en-us/library/vstudio/bb386106.aspx#LoadBehavior

4. Now edit or create a Group Policy Object and configure the following settings
5. Navigate to User Configuration > Preferences > Windows Settings > Registry
6. Right-click and select New > Registry Item
7. Paste the key you copied earlier in Key Path

• At Value name, type "LoadBehavior”.
• At Value type, choose “REG_DWORD”
• At Value data, type “00000002”, this will unload the add-in

8. Open the Common tab
9. Select “Run in logged-on user’s security context (user policy option)” and “Item-level targeting”

10. Create a security group in your domain
11. Click Targeting… and add the group you just created
12. At Item Options, select “Is Not”

13. Now make a copy of the just created registry setting you made in the policy. In the copied setting, change the registry value to “00000003”, and change the Targeting from “Is Not" to “Is”. This will load the add-in for any user who is a member of the group.

Now you have two settings configured:

• When an user is not member of the group, the add-in will not be loaded.
• When an user is member of the group, the add-in will be loaded.

This article consists of two parts how to check expiration and renew the certificate:

A. How to check if the SCCM Site Server Signing Certificate is expired

B. How to create a request file to renew the certificate (only working method to renew!)

A. How to check if the SCCM Site Server Signing Certificate is expired

1. In the Configuration Manager Console, navigate to Site Management
2. Open the Properties of your Site
3. Open Site Mode and note the name of the Certificate

4. Click on Browse…

5. Check the corresponding certificate name and check the Valid From date

If the certificate is expired, you have to renew the certificate by following the steps below.

B. How to create a request file to renew the certificate

Be sure to do this outside work hours, because it impacts the SCCM clients.

1. Create a new file ‘sitesigning.inf’ with the following content:

[NewRequest]
FriendlyName = "SCCM Site Signing Server Certificate [your site code]"
Subject = "CN=The site code of this site server is [your site code]"
MachineKeySet = True
[RequestAttributes]
CertificateTemplate = ConfigMgrSiteServerSigningCertificate

2. Save the file and open an elevated command prompt.

3.Type the following commands in the folder where you saved the file:

certreq –new sitesigning.inf sitesigning.req

certreq –submit sitesigning.req sitesigning.cer

4. Select the correct CA:

Output of certreq commands:

The certificate is now requested at your Certificate Authority.

5. Issue the certificate in your CA in Pending Requests and remember the Request ID

6. In an elevated cmd on the SCCM server again, type the following command:

certreq –retrieve [requestidnumber] sitesigning.cer

7. Select the correct CA again:

8. Open the local Certificate store by opening an new mmc and add Certificates (Local Computer)

9. Check if the certificate is present in Personal / Certificates (a little key must appear with the certificate! if not, the certificate does not contain the private key)

11. In the Configuration Manager Console, navigate to Site Management

11. Open the Properties of your Site

12. Open Site Mode, click on Browse and select the new certificate

The certificate is now renewed.

You can check the SMS_POLICY_PROVIDER status again under: System Status > Site Status > [Site code] > Component Status

If the certificate is correctly renewed, the message ‘SMS Policy Provider successfully signed all policy assignments with the new Site Server Signing Certificate.’ will appear. Your SCCM clients will then be functional again.

1. Insert the original Windows 7 / Server 2008 installation DVD
2. Reset the computer, boot from DVD
3. Choose option "Repair your computer"
4. Start command prompt

Type in the following commands:

C:\ 
CD C:\Windows\System32 
MOVE Utilman.exe Utilman.exe.bak
COPY Cmd.exe Utilman.exe

5. It may be necessary  to enable the administrator account by using the following command:

NET USER administrator /active:yes

6. Restart windows. At the login screen, type Windows-U, this will now open cmd.exe.

Type in the following command:

NET USER administrator <NEWPASSWORD>

Login as administrator
Delete Utilman.exe and rename Utilman.exe.bak back to Utilman.exe in C:\Windows\System32.

This article consists of two parts how to indicate and resolve the problem:

A. How to check if the SCCM Site Server Signing Certificate is expired

B. How to create a request file to renew the certificate (only working method to renew!)

A. How to check if the SCCM Site Server Signing Certificate is expired

1. In the Configuration Manager Console, navigate to Site Management
2. Open the Properties of your Site
3. Open Site Mode and note the name of the Certificate

4. Click on Browse…

5. Check the corresponding certificate name and check the Valid From date 

If the certificate is expired, you have to renew the certificate by following the steps below.

B. How to create a request file to renew the certificate

Be sure to do this outside work hours, because it impacts the SCCM clients.

1. Create a new file ‘sitesigning.inf’ with the following content:

[NewRequest]
FriendlyName = "SCCM Site Signing Server Certificate [your site code]"
Subject = "CN=The site code of this site server is [your site code]"
MachineKeySet = True
[RequestAttributes]
CertificateTemplate = ConfigMgrSiteServerSigningCertificate

2. Save the file and open an elevated command prompt.

3.Type the following commands in the folder where you saved the file:

certreq –new sitesigning.inf sitesigning.req

certreq –submit sitesigning.req sitesigning.cer

4. Select the correct CA:

Output of certreq commands:

The certificate is now requested at your Certificate Authority.

5. Issue the certificate in your CA in Pending Requests and remember the Request ID

6. In an elevated cmd on the SCCM server again, type the following command:

certreq –retrieve [requestidnumber] sitesigning.cer

7. Select the correct CA again:

8. Open the local Certificate store by opening an new mmc and add Certificates (Local Computer)

9. Check if the certificate is present in Personal / Certificates (a little key must appear with the certificate! if not, the certificate does not contain the private key)

11. In the Configuration Manager Console, navigate to Site Management

11. Open the Properties of your Site

12. Open Site Mode, click on Browse and select the new certificate

The certificate is now renewed.

You can check the SMS_POLICY_PROVIDER status again under: System Status > Site Status > [Site code] > Component Status

If the certificate is correctly renewed, the message ‘SMS Policy Provider successfully signed all policy assignments with the new Site Server Signing Certificate.’ will appear. Your SCCM clients will then be functional again.

1. Open the SQL Server Configuration Manager (Start / Microsoft SQL Server 2008 R2 / Configuration Tools / SQL Server Configuration Manager)
2. Navigate to SQL Server Network Configuration / Protocols for [instance name]  and open TCP/IP

3. Open the tab IP Addresses and navigate down to IPAll
4. Fill in the desired port at the TCP Port field

5. In order to take effect, the SQL Server (instance name) service will have to be restarted

The SQL Server Database Engine will now listen on the configured port.

‘Cluster Shared Volume…’ is no longer available on this node because of ‘STATUS_BAD_NETWORK_PATH(c00000be)’.’

Open the Properties of the network adapter used for your cluster HeartBeat network and enable File and Printer Sharing for Microsoft Networks. The Cluster Shared Volume should now be available from the other nodes.

The following command line can be used in a batch file to automate the driver installation:

rundll32 printui.dll PrintUIEntry /ia /b "Printer Name" /f "filename.inf" /m "Printer model from inf file"

Type in the correct printer model after the /m switch which is defined in the .inf file.  You can determine the model names by opening the .inf file or using the Add printer wizard while manually selecting the .inf file.

Make sure all installation source files reside in the same folder as the .inf file. Using this command line there will be no confirmation box. You can use additional switches to show a confirmation message. All command line switches can be found in this article:

http://technet.microsoft.com/en-us/library/ee624057(WS.10).aspx

• Cluster Shared Volumes on Hyper-V R2 (Windows 2008 R2) can only be used by using iSCSI (you can use pass-through disks in your VM’s, but these are not suitable for CSV’s).
• Virtual Fibre Channel adapters are supported in Hyper-V R3 (Windows Server 2012) and will require much less configuration.
• So, Cluster Shared Volumes within virtual machines on Windows 2008 R2 can only be realized in two ways:
  • Over your TCP/IP network, using iSCSI, where your network storage has to be configured as an iSCSI target.
  • Over your Fibre Channel connected storage, but only by using a third party tool which will function as an iSCSI target to provision the disks. For these purposes, Microsoft provides the free Microsoft iSCSI Software Target software: http://www.microsoft.com/en-us/download/details.aspx?id=19867
• Each solution has it’s advantages and disadvantages:
  • iSCSI advantages: With iSCSI, you only need the iSCSI Initiator tool which is natively included in Windows 2008 R2 to connect a network storage disk. No additional software is required.
  • iSCSI disadvantages: For iSCSI you need to use your Ethernet network. Therefore you need to create a Ethernet connection between your Hyper-V hosts and storage. Best practice is to use dedicated redundant cabling (teaming / trunking) only for your iSCSI communication. Or you could use your existing cabling, but make sure your iSCSI traffic is separated by using  a VLAN and make use of QoS to provide the proper bandwidth.  VLAN’s must  be configured on all of the switches between your Hyper-V hosts and storage. So, with iSCSI you need to (re)configure your existing network and at the same time, considering if your network meets the proper requirements.

  • iSCSI target software advantages: the Microsoft iSCSI Software Target makes sure you will stay within your storage Fibre Channel network, because traffic does not leave the Hyper-V hosts.
  • iSCSI target software disadvantages: You need software. Software has to be installed on a Windows machine. This Windows machine has to be a virtual machine. Of course, you can use an existing virtual machine, but this creates another problem. With a piece of software installed on a single virtual machine, you will create a single-point-of-failure. Also, you are creating another layer between your Windows hosts and network storage, which increases complexity and has it’s influence on performance.

Configure direct iSCSI connection

My recommendation is to use an direct iSCSI connection to your network storage for performance and failover capabilities at network level (trunking / teaming). Of course, your network storage has to support iSCSI, but most will do.

Follow these steps to create your iSCSI network:

1. (Additional: connect your Hyper-V hosts to your network storage by using the proper cabling; CAT6 for Gigabit connections). Or use the existing LAN.
2. Choose a network range and a VLAN ID.
3. Create the iSCSI target on your network storage, assign an IP address in the chosen network range and the VLAN ID. Create the LUN’s and  IP assignments for your virtual hosts.
4. Create the VLAN ID on the switches connected between your Hyper-V hosts and your network storage. Additionally, configure QoS on the switch ports.
5. If you used dedicated cabling in step 1, create a vSwitch on your Hyper-V hosts, assign it to the physical network card, define the network range and assign the VLAN ID.
6. Assign an extra virtual network card to your virtual machine, only for iSCSI communication. Assign the VLAN ID.
7. Make sure in the Failover Cluster Manager, the network card is not used for cluster communication.
8. Assign the virtual network card an IP address in the chosen range and define the subnet mask. Do not fill in the default gateway or DNS servers. Turn off DNS registration, LMHOSTS lookup and NetBIOS in Advanced TCP/IP settings. Disable services and protocols which are not needed:

9. Open the iSCSI Initiator and fill in the IP address of the iSCSI target. This is the IP address configured in step 3. The disks configured in step 3 will be presented.
10. Add the discovered volumes in the Failover Cluster Manager \ Nodes \ Cluster Shared Volumes.

Configure an iSCSI software target

For a complete guide how to configure CSV’s with Microsoft iSCSI Software Target, I recommend this post: http://blogs.technet.com/b/mghazai/archive/2009/12/12/hyper-v-guest-clustering-step-by-step-guide.aspx