Skype for Business upgrade

Regarding all hype about Skype for Business last days her is short overview about it

  1. Skype for Business is available as upgrade for Lync client.
  2. Upgrade is available from 15th of April as KB2889923.

S4BKB28899233.

Knowing which KB is bring this change, System Administrators or responsible persons for updates will be able to control will this update will be applied or not. This will give most of companies time to adopt and test new functionalities of Skype for Business.

SQL collation and System Center

What is SQL collation? SQL collation refers to a set of rules that determine how data is sorted and compared. Character data is sorted using rules that define the correct character sequence, with options for specifying case-sensitivity, accent marks, kana character types and character width.

SQL collation knows to be pretty annoying thing, especially if you chose wrong one.

I find out that on hard way. After I was install SCCM 2012 RC and I was try to „upgrade“ to RC2.

Where is the catch? Catch is when you going to install SQL server, by default it picks up collation from regional settings (in my case Croatian). You can change collation during installation but if you are not careful enough you could face with serious problem (like me). Why? Because RC will work fine but upgrade to RTM will be almost impossible.

Here are few pictures how to choose right collation

Collation 1Collation 2Collation 3Collation 4

Microsoft supports upgrade System Center 2012 products from RC to RTM. RTM (or RC2) will asks for SQL_Latin1_General_CP1_CI_AS collation on your SQL. Now you have problem if you pick wrong collation before or you didn’t pick it at all (you have default created on regional settings bases).

Only way to resolve the problem is to uninstall SQL and install it again with correct collation.

But if you are using existing SQL you need to (can) change collation before installing SCCM 2012.

How can you do that? You can do that using a script: “Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=
MSSQLSERVER /SQLSYSADMINACCOUNTS=demo\administrator /SAPWD= Pa$$w0rd /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS“

Collation 5

You must do that before starting setup SCCM 2012, or setup will fail with error message about wrong collation. If you have right collation, setup will create CM_xxx database (where xxx is site code)

And for last thing, you can’t change collation on existing CM_xxx database. Why? CM_xxx database is really complex, and collation change will fail. Colleague of mine Luka Gros tried but he didn’t make it. He received error every time.

I show this on demo on my presentation on Windays12 and this was one of tricks which I presented for SCCM 2012

Conference time in April

Conference time in April is over.

I had two presentations this month. First one was at MS NetWork 2.0 in Mostar, Bosnia and Herzegovina.

MS NetWork 2.0 presentation was about how to turn datacenter into private cloud solutions.

Second one was at WinDays 12 in Rovinj, Croatia. This one is called SCCM 2012 Tips And Tricks.

Presentations will be available on SlideShare during this weekend and link for demos is on the right side

Have nice weekend

D.

Reinstalling WSUS after SCCM installation

If you want to use SCCM 2012 as a software update point (SUP), you will have to install WSUS first.

On Windows Server 2008 R2 installation of WSUS is integrated as a server role. You don’t need to download installer separately.

Catch is that you will need to use SCCM server database. But if you install WSUS first You will probably install its own database.

Correct steps will be:

1. – Install SQL server , and create database for SCCM use

2. – Install WSUS, and point it to SCCM database

3. – Install SCCM

But if you are install your SCCM as I do, then you will have a problem.

My steps was:

1. – install WSUS

2. – Install SQL

3. – Install SCCM

After this my only option was to uninstall WSUS, and install it back again with correct parameters.

Uninstall was completed successfully. But on installation I was faced with error. Error was “the update could not be found there may be a network connection issue”.

This error is caused by setting in GPO of SCCM server. To resolve this You must point to gpedit.msc and then go to Computer Configuration – Administrative Templates – Windows Components – Windows Update. Put “Automatic Updates” and “Specify Intranet Microsoft update service location” to “not configured”.

Important thing is that you have proxy settings configured in your correctly web browser .

After this I was able to continue with installation without error.

Why is this update option important?

WSUS using Dynamic Installer to download all needed content for installation from Microsoft websites. Wrong thinking is that WSUS binaries is on server or on CD.

Now my WSUS is working fine and I can go further with SCCM 2012

SCCM Client won’t show device is server console

Usually when You install SCCM 2012 client after few minutes device appear in console view. But what if device wont show after couple restarts? (couple days)

I don’t know why this error occurred but, this is steps for resolving problem.

No Site Configured

At first, you must check connectivity to SCCM 2012 server. If connectivity is ok and you can reach server by its name do this.go to tab SITE

go to tab SITE

Site Configuration

Write number of assigned site and press Find Site

You will receive notification that Configuration Manager has successfully find site to manage this client

Site COnfigured

Check General tab again now it looks like this

Site showed up in Config client

Notify that you still don’t have “Client certificate” and “Connection Type”

But after few minutes everything is fine

After Few minutes

Your client is now visible in your SCCM console and you can manage it.

Too much switch could kill you

If You want to implement Dot.NET framework 4.0 using SCCM 2012 you have whole workaround on MSDN site. But something can go wrong. Where is catch?

Here we go.

First of all you must create package in SCCM 2012. When you creating package for deployment, you will be prompted to create a program. During program creation You are asked for command line . Of course You want to install Dot.NET framework without user interference. So switches is needed.

When I Google it i find this syntax on MSDN site:

dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT

But installation ended up with error. Trying to troubleshoot is not giving any result.

So I just change syntax to:

dotNetFx40_Full_x86_x64.exe /q

image

and after that deployment ended successfully.

My conclusion is: Use just needed switches, Try not to COPY/PASTE from other solutions