IT Consultant Everyday Notes

Just some problems/solutions storage

Monthly Archives: January 2013

Audiocodes: MediaPack 1xx–connected phones cannot call each other

I am configuring Lync 2013 to communicate with AudioCodes MediaPack 118 Enhanced Voice Gateway (the device is not certified for Lync 2013).

Listening port on Lync: TCP 5068

Listening port on Audiocodes: TCP 5060

Audiocodes FXS line 1: 2001

                           line 2: 2002

Lync – Phones traffic flows without problem.

Issue: When I tried to call between phones connected to MP-118 I got a busy signal. Phone call does not pass.

Resolution: In Protocol Configuration – Protocol Definition – SIP General Parameters I had SIP destination port set to 5068 (port on my Lync 2013). It looks like Audiocodes used this port by default for all SIP connection (including connection from connected phone to Audiocodes SIP server itself).

So I added port 5060 to my routing rule describing route for phone-phone calls (switch to  Advanced Parameter list):


Lync 2010: LS Response Group Service logs Event ID 31196 every 2 minutes

Issue: my Lync 2010 Front-End server logs

Log Name:      Lync Server
Source:        LS Response Group Service
Date:          1/29/2013 12:44:08 PM
Event ID:      31196
Task Category: (2001)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      <front-end server>
Collaboration platform has failed to provision the data.

Collaboration platform has failed to provision the data because of the following exception:
Exception: Microsoft.Rtc.Collaboration.ProvisioningFailureException:Cannot read contacts from Active Directory: Active Directory server "DC Server Name" is not available. Try again later. …

Resolution: Restart Lync Service Response Group service.

found here

Lync 2013: Control Panel HTTP Error 401.1

I am working with Lync/OCS –> Lync 2013 upgrade project. I installed Lync 2013 on my Windows Server 2012.

Issue: When I try to access Lync 2013 Server Control Panel from the Front-End Server I get “Http Error 401.1” after three unsuccessful logon attempts. I can connect to the Control PAnel from other machines though (with the same credentials set)

Resolution: Fortunately I found this thread and followed Lync MCM Jeroen Reijling advice:

Logon on to the Front-End Server with an account that is member of the local admins group

  1. Start “regedit”
  2. Go to “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa”
  3. Right-click the Lsa registry subkey, point to New, and then click DWORD Value
  4. Type DisableLoopbackCheck, and then press ENTER
  5. Right-click DisableLoopbackCheck, and then click Modify
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor, and then restart the server.

Now Control Panel is accessible:


Certificate WEB request failed with: This Web browser does not support the generation of certificate requests.

Issue: I am trying to send a certificate request from my Windows 2012 Server running IE 10 (default).

The request fails with the error: “This Web browser does not support the generation of certificate requests.”


Resolution: Press F12 and select IE 10 Compatibility View. After that CertSrv page should be displayed properly:


SCCM 2012: Boot images not updated after upgrading to SP1 in System Center 2012 Configuration Manager

In my upgrade I did not see this issue, but it looks like some people have it. To resolve it:

  • Rename the boot.wim and the default boot wims in each architecture folder of the <smsinstall>OSD\boot\ folder – both the i386 and x64 to <wim>.bak
  • Starting with the i386 folder first…Find the install folder of the ADK, which should be here if you installed with the defaults: “C:\Program Files (x86)\Windows
    Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim”. You will need to copy the winpe.wim to the <smsinstall>OSD\boot\i386 folder. Rename it to boot.wim.
  • You will also need to copy it again, but this time rename it so it matches the name of the default boot wim for the site – so it should look like boot.<packageid>.wim
  • Update default boot image. Click “Execute Method” -> input object path as SMS_BootImagePackage.PackageID=”<Image ID you see in the Console e.g. POL00001>” -> UpdateDefaultImage
  • You will need to do this for the x64 folder as well. Do not do this for any custom boot images – this is just to update the default boot wims installed during setup of the site.

as described in Clifton Hughes blog

SCCM 2012: SCCM 2012 SP1 Client update failed. Error: “Couldn’t verify ‘C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ authenticode signature. Return code 0x800b0101

UPDATE: Microsoft published updated binaries for SCCM 2012 SP1 addressing this (and other minor) issues. You should use this new file set  for new installations. Links are here:


I upgraded my Lab SCCM to 2012 and decided to try “Client autoupdate” feature introduced with SCCM 2012.

Unfortunately the attempt failed and I saw

Couldn’t verify ‘C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ authenticode signature. Return code 0x800b0101

in ccmsetup.log on the Client.

Signing certificate for the msi looks like:


so it looks expired for me  Smile

Fortunately Microsoft published  – Cumulative update 0 (CU0)  including an update (download)

I download the update and ran it on my SCCM


it did not pass from the first time, of course:


I should say the warning is a bit confusing – from the first sentence – Reboot is not required, from the second – I must restart the computer. Winking smile. Reboot the server and try again!

This time it looks better:





create packages:


and proceed with install:


Checking certificate again:


and the msi is validated successfully and the client is installed:


Do not forget to deploy the update to another Primary servers.

Anoop found some confusion between KB and the update wizard:

I still think the updates is not necessary for CAS…

SCCM 2012: How to move DP Content Library to an alternative drive

Content Distribution model is significantly changed in SCCM 2012. Well-known SCCM 2007 procedures for moving DP content from one disk to another does not work for 2012 as a result.

Fortunately Microsoft published ContentLibraryTransfer.exe tool (a part of SCCM ConfigMgr 2012 SP1 Toolkit available for download here). This tool can be used for the content transfer.

Note: In the toolkit description Microsoft listed SCCM 2012 SP1 as a supported product; so I assume it may not work or at least not supported for SCCM 2012 RTM.

Command syntax:

ContentLibraryTransfer –SourceDrive <Letter> –TargetDrive <Letter>


1. The tool must run locally on the distribution point; it cannot be run from a remote machine.

2. The tool must run only when the distribution point is not actively being accessed by client computers. If the tool is run while client computers are accessing the content, the content library on the destination drive may have incomplete data or the data transfer might fail altogether leading to an unusable content library.

3. The tool must only run when no content is being distributed to the distribution point. If the tool is run while content is being written to the distribution point, the content library on the destination drive may have incomplete data or the data transfer might fail altogether leading to an unusable content library.

You can read detailed instructions in documentation for the Toolkit.

SCCM 2012: Access Denied while trying to download updates

I tried to download monthly updates to my Deployment Package. The attempt failed with Access Denied for all updates. It turned out that even my account is a local admin on the SCCM server I need to add it with Full rights to the source share (both NTFS and Share permissions) where my Deployment Package is located.


As soon as I added the account implicitly and granted rights to it SCCM successfully downloaded necessary updates to the Deployment package.

SCCM 2012: Automatic Client Upgrade

Just a reminder where the settings  Smile are located:

Go to Administration-Site- Configuration – Sites

Select your site and click Hierarchy Settings in ribbon

Select “Automatic Client Upgrade” tab in popup window:



SCCM: Client cannot get Policies automatically; site mode is “Unknown”

In some situations (list for SCCM 2007 is available in this article) you may found an SCCM client cannot get Policy from the server even though it is assign to the site and can see the server (site mode is displayed as “unknown” though on Client side).

Both SCCM 2007 and SCCM 2012 (RTM) is affected. The issue is promised to be fixed for SCCM 2012 with SP1 (available now).

The root cause is a Client Provisioning mode. To detect if the client is in this mode you can check:

32bit Windows OS

64bit client Windows OS

Also, checking the Mobileclient.tcf file in the ccmsetup directory of a fully built machine shows SMSPROVISIONINGMODE=1 in the client install section – on a healthy client this should be

A fixing script for SCCM 2012 is provided in that article