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.


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.

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.

Deploying Windows XP SP3 without GPO and WSUS

If You are managing wide infrastructure of your organization You could be unpleasantly surprise that Windows XP SP3 is not deployed to every Windows XP machine.

For some reason WSUS is not an option and GPO is upgraded to Windows Server 2008 R2 functionality. What You will do?

Using GPO is not an option because of too much configuration and lot of requested modification.

Using of logon script could be a point.

Requests is that you can deploy and install Windows XP SP3 without disturbing users.

At first we must create temporary user with administrative rights

After that we must download lsrunas tool. We will use it for passing the password. You can download it from here.

After that we will put Windows XP SP3 (WindowsXP-KB936929-SP3-x86-ENU) in network share accessible for domain users.

Check that every user can see it.

Create .bat script with following parameters

lsrunas.exe /user:tempadmin /password:password /domain:domain /command:xpsp3.cmd /runpath:

Create .cmd script with parameters:

net use x: /delete /y (where x is logical name of ntw share where SP3 is)

net use x: \\server\share ( reconnect share)


cd sp3 (where Sp3 is name of directory where .exe file is)

WindowsXP-KB936929-SP3-x86-ENU.exe /quiet /promptrestart

Job done.

You can use this switches:

[/help] [/quiet] [/passive] [/norestart] [/forcerestart] [/warnrestart] [/promptrestart] [/overwriteoem] [/nobackup] [/forceappsclose] [/integrate: ] [/d: ] [/log: ]
/help Displays this message
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
/warnrestart[: ] Warn and restart automatically if required (default timeout 30 seconds)
/promptrestart Prompt if restart is required
/overwriteoem Overwrite OEM files without prompting
/nobackup Do not backup files needed for uninstall
/forceappsclose Force other programs to close when the computer shuts down
/integrate: Integrate this software update into
/d: Back up files into
/log: Create log file at

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


and after that deployment ended successfully.

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