From SCCM 2012 RC to SCCM 2012 SP1 in few steps.

I finally upgrade my System Center Configuration Manager form RC version to RTM version with SP1 included.

As I had “small” collation problem I couldn’t just simply reinstall it. For that reason I was uninstall my SCCM completely. Plan was to keep server name in Active Directory and to keep same site name.

In that reinstallation I was separate my SQL server from my SCCM server. Now I have SQL 2012 SP1 for all (future)System Center products, and SCCM is connected to it.

After one working day my job was done and I have fully functional SCCM. Now I have to wait for clients to contact SCCM. Most of clients were contact SCCM in next two days, but some clients don’t.

Then I use some old stuff which can be found on Niall Brady forum. As I’m very lazy Smile, and I don’t want to type all over again You can find solution for deploying/redeploying clients here.

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