IT Consultant Everyday Notes

Just some problems/solutions storage

Monthly Archives: October 2012

SCCM 2012: Why Microsoft does not call SCCM SCCM?

Several years (I believe with start of SCCM 2007) Microsoft corrected me with the acronym: “Do not call it SCCM – it should be ConfigMgr”. At that point of time they explained it this way: “SCOM does not sound good, so it will be OpsMgr, then SCCM will be ConfigMgr”. Hmm… I recently bumped into an article explaining it a bit differently, with more sense:


According the article we had (officially) ConfigMgr for 2007 and nothing is blessed for SC Configuration Manager 2012. One of variants – CM12. I am voting for it, but still think most of my Clients will call it SCCM and may be confused with another acronym Sad smile

SCCM: How to deploy a shortcut

1. Create a shortcut Winking smile

2. copy the shortcut to a file share where you keep your package source files

3. Create a package containing the shortcut

4. Create a program to copy the shortcut to a location you need. Do not forget to put “cmd /c” if you use “copy” command. So it will look like:

cmd /c copy yourlink.lnk <destination folder>\*.*

Where to copy? First of keep in mind SCCM Client works under SYSTEM account and will not put the shortcut to a specific user desktop – for that better use GPOs. What you can do is to put the shortcut for All Users.

In Windows 7 All Users Desktop is located %ProgramData%\Desktop you will not have access to this folder probably, but SCCM Client will.Smile


In one case we needed to put a file in SYSTEM32 folder. I know it is not a good idea to put files there, but it was a requirement of a third-party app. If you try to run a program to copy a file to C:\WINDOWS\SYSTEM32 you may have a surprise – on 64-bit OS your file will occur in c:\WINDOWS\SYSWOW64  instead of \SYSTEM32!

To workaround this behaviour you can use a Task Sequence:

1. Add a Run Command Line step to a custom TS.

2. Configure the step Disable 64-bit file system redirection

3. Add you Package (that instructs the TS to copy it to a local cache)


4. Add command line.

Lync 2010: User activity report failed with “An error has occurred during report processing. (rsProcessingAborted) Query execution failed for dataset ‘CallList’. (rsErrorExecutingCommand)”

Issue: User Activity report failed with “

An error has occurred during report processing. (rsProcessingAborted)

Query execution failed for dataset ‘CallList’. (rsErrorExecutingCommand)

For more information about this error navigate to the report server on the local server machine, or enable remote errors.”



1. It happens after CU installation. For me – after CU7, some people report it happens after CU6 too.

2. Read instructions in CU KB – you must update database! using something like :Install-CsDatabase -Update -ConfiguredDatabases –SqlServerFqdn <SQL Server without instance> –UseDefaultSqlPaths

In my case SQl FQDN did not work – I put NETBIOS name. I guess the main idea is to put how it is displayed in your Topology Builder.

3. Start Lync 2010 Deployment Wizard and redeploy Monitoring Reports. I did it from Front-End Server.

4. Above mentioned KB does not instruct you to update Monitoring Database – this is from other KB Winking smile

my command looks like: Install-CsDatabase -DatabaseType Monitoring -Update –SqlServerFqdn <Monitoring Server Name>

in my case, again, server name was just a NETBIOS name and I ran it from a Front-End server.

SCCM 2012: Azure-based cloud Distribution Point

SCCM 2012 SP1 introduces a new feature – cloud-based Distribution Point (DP). The DP must be based in Microsoft Azure.

Peter blogged here step-by-step for the DP creation.

SCCM 2012: OSD–Should Office (or any other App) be a part of base image?

Rapael blogged some measurement for three scenarios:

1. Post OSD installation via Application Installation

2. Post image installation in the same TS

3. OSD when Office is a part of the image.


The winner is – method #2. Of course it depends on your network, TS, number of apps etc and need to be tested in your environment. But still good information.

SCCM 2012: Silent installation

A good guide (including silent SQL installation, silent Admin Console installation and silent Primary site installation) is in Sandbu blog

Lync: Phone Edition LG-8540 –Firmware Update

I recently found an old LG-Nortel 8540 and decided to put it to my Lync 2010 environment (all other phones are almost all Aastra).

The device had an old OCS 2007 RTM firmware: 1.0.522.101 (1.23). Apparently I am lucky – people with older firmware must to install OCS 2007 RTM in order to update the device firmware to this version ( Smile

Issue: My device successfully connected to Lync (with old firmware) but did not want to upgrade it to a recent one – 4.0.7577.410


1. I installed OCS 2007 R2 Std in my Lab. One server.

2. Updated it with the latest CU. UPDATE DATABASE FIRST! (

3. Download the latest firmware for LG 8540 for OCS 2007 R2 (3.5.6907.222 (1.23)) (

4. Install the update and approved it as described here:

5. Start the device and logged in as “\username” not just domain\username here is why:

7. Nothing happened – no updates!  Sad smile

8. tried to get update using IE /DeviceUpdateFiles_Int/UCPhone/LG-Nortel/IP8540/A/ENU/3.5.6907.0/CPE/CPE.nbt">http://<OCS FQDN>/DeviceUpdateFiles_Int/UCPhone/LG-Nortel/IP8540/A/ENU/
– got a blank page instead of the file.

8.1. Static Content feature was missed from IIS installation – installed it. Still nothing

8.2 Removed <mimeMap fileExtension=".cat" mimeType="binary/octet-stream" />  from c:\windows\system32\inetsrv\configuration\applicationHost.config and rebooted the server (just iisreset did not help)– I can download file successfully now. The solution was found here:

9. So do the device – successfully got the update.

10. I can monitor it in log files (I am using CMTRACE.exe from SCCM to see logs “live”)




11.As soon as the device was updated to 3.5.6907.222 I plugged the phone to my production network hoping it will accept 4.0.7555.4066 I have downloaded and approved for Lync as described in a nice Jeff’s article. Unfortunately it did not happened Sad smile

12. Some research leaded me to that thread and I realized I am not alone. It looks like due to cert issue LG 8540 cannot get the latest and greatest firmware (CU6, June 2012) and need to be upgraded to a previous (CU5, March 2012). The problem is the patch is not available anymore! All links point to CU6 even from CU5 KB. Luckily  Lync15 posted a link to his SkyDrive where he uploaded the old CU5. Whole thread is here direct link is here. Problem in details is described by Jeff here. Thank you guys!

13. I removed the latest firmware for LG 8540 from my Lync and published CU5 instead:


14. Restarted the phone and it successfully got 4.0.7577.4066 from Lync.

15. Now we can add CU6 Lync Device Updater and LG 8540 accepts it.


Reference: Jeff on Lync Phone Troubleshooting:

Server 2012: Hyper-V on Gigabyte P67X-3DR

I am updating my home Lab to Server 2012. As a part of upgrade one of my Hyper-V hosts got the new OS. As soon as I enabled Hyper-V role it rebooted and sit forever showing me nice new windows logo (no logon screen).


I found resolution here. USB3 controller should be disabled in BIOS. Hopefully Gigabyte will fix it in later BIOS updates.

From this forum it looks like Windows 8 with Hyper-V role is affected too!

Lync: CU7 (October 2012) is available

Lync: How to install CWA on Windows Server 2008 R2 SP1 for Lync integration.

Note: Communicator WEB Access 2007 R2 role is not supported on Windows Server 2008 R2 as per so use the instructions on your own risk. CWA is supported on Server 2008 SP2, you may decide to use that platform.

As you probably know Communicator Web Access (CWA) is not provided with Lync. Microsoft recommends to use Lync integration with Outlook Web Access (OWA) instead. Some people (me included) think this is a bad replacement. In this situation you may need to install CWA in your Lync environment.

In my situation I had a Lync-OCS 2007 RTM coexistence for migration purposes (so AD schema was properly extended for both OCS 2007 RTM and Lync) and CWA installed in OCS environment. CWA worked well for both OCS and Lync users.

Finally migration was completed and I needed to decommission OCS pool. That means CWA will stop to work. Microsoft recommends to reinstall CWA and point it to Lync pool in this situation. Unfortunately CWA for OCS 2007 RTM is not flexible enough to give a list of pools to connect to. CWA for OCS 2007 R2 can do it though. So, I decided to install CWA 2007 R2 to my Lync Monitoring Server (that let me save a server and migrate CWA from Server 2003 to 2008 R2 SP1, standard platform for my environment).

Problem 1: I prepared  IIS as described here and here and  tried to install CWA as it should be normally done (as described for example here) and the attempt was failed – CWA setup could bot find OCS 2007 R2 infrastructure.

Resolution: Rerun OCS forestprep. In my case AD schema was updated when 2008 R2 DC were introduced and that affect OCS settings for some reasons.

After that CWA software was installed, I followed the next step in Deployment Wizard to activate the role, create the web site and Publish it.

Problem 2: All logs were nice and green, but Server never listened for communication from my Lync FE. That’s it – CWA client could send messages, but newer received them! In addition I could not find CWA console Sad smile

Resolution: There are multiple steps. Fist of all I needed to deactivate the installed CWA. Since console was not available I ran a command prompt as Administrator and navigated to <Installation media>\Setup\amd64\setup\cwa There are three files there. I ran cwamain and it deactivated the role uninstalled bits. Next step is install it back. In addition to prerequisites installed before I installed Desktop Experience feature (read to know why). Check installed components: ifs OCS Core Components are not installed you may need to use  Orca MSI editor to edit OCSCore.msi file to drop a condition line (describing OS Version):


Install CWA software again. Update with the latest OCS 2007 R2 patches available here: At this point the System asked for reboot, but I denied and activated CWA. Install Virtual Folders. Publish CWA. Reboot the machine now.

Go to Lync Topology Builder and Merge OCS 2007, OCS 2007 R2 Topology. Microsoft says Lync cannot coexist with both OCS RTM and R2, so I worried if it will work in my case since I had OCS 2007 RTM infrastructure (almost decommissioned) and OCS 2007  R2 CWA. The matter in fact it works!

Last step is “Publish Topology” from Lync Topology Builder.

After that I could successfully connect to my CWA and use it for IM exchange with other Lync Clients.


One problem is without resolution – CWA console is not installed, so it can problematic to change an MTLS certificate (WEB cert can be changed from IIS console).  —   Update: my fault! Forgot you need to install Admin Console separately in OCS 2007 R2 Winking smile