Thursday, 27 June 2013

How to set the Computer Name to a the Serial Number during OSD SCCM 2012 SP1


Its 11:30pm on a Thursday, I was falling asleep but I shot out of bed in the realization that I have wanted to post this for a while now, so I just got up and did it!

Lets assume you have a bunch of PC's and you want to come up with a naming solution to automatically re-name them as part of the OSD, the serial number is a good idea and its almost guaranteed to be unique, right? Correct. Now some people will advise that you run a script or use WSNAME amongst other solutions, and these solutions do work, but I have recommend this much simpler solution instead for SCCM 2012 SP1.

My client had a requirement that the company's acronym formed the formed the first part of the PC name, followed by a number.

For example, AAAA1234

Now I will assume that you have SCCM 2012 SP1 installed with MDT and you have configured Config Manager integration, if you don't fear not, I have document the entire process here (

This is how its done
First we need to edit the task sequence, so you need to add 3steps the first is the "Use MDT Package" step just after your "Apply OS" step

The next step is "Gather" and ensure you set it to "Gather only local data (do not process rules)"

The third step is the "Set Computer Name" step this is done by adding a "Set Task Sequence Variable" this can done by clicking "Add" from the menu above your task sequence and looking for the "Set Task Sequence Variable" option. You can now rename this to Set Computer Name for example.

Make sure you have the following in place as shown below, you will need the sequence variable to set to OSDComputerName. The value can then be set to %SERIALNUMBER%

Once saved you can then alter this slightly to AAAA%SERIALNUMBER% this will then change the Computer Name to AAAA123456 if "123456" was the serial number.

One last important note please make sure you test this before mass roll out, and also that you make 100% sure that you have added these steps after Apply OS and before the Apply Windows Settings step.


Sunday, 9 June 2013

SCCM 2012 SP1 Remote Control/Tools Only


I was asked provide instructions to install the SCCM console on a few desktops so that the security team can use it for Remote Tools (Control) only ...

I didn't install the console for anyone. And neither should you, instead you just need to complete the following to give your analysts the ability to use Remote Control and nothing else.

So, to do this you will need to do the following.

Firstly make sure that you add the names of the technicians you want to have access to remote tools into the Remote Tools Operators role based security group in the Administration workspace in the SCCM console.

Next, from the file directory where the SCCM console is installed (C:\Program Files\Microsoft Configuration Manager\AdminConsole\bin\i386) copy the following files into a New Folder (Name it whatever you like)

1. 00000409 (Its a folder, copy the entire folder)
2. CMrCVieiwer (Application)
3. RdpCoreSccm.dll

Place these files onto a pen drive or somewhere sensible on the technicians PC, next you can launch the CmRcViewer application, enter the PC name of the target PC, and away you go.

Enjoy - Any questions please let me know.

Tuesday, 4 June 2013

The Desktop Team - Path to Windows 8

One and all,

I have some good news, I have recently been invited to join the Desktop Team as a blogger.

I am however sad to say that I haven't had the time to actually start putting anything on the new blog as of yet.

But, we are hosting a brilliant event on the "Path to Windows 8". Its going to be a brilliant day away from the office discussing all things System Center and Windows 8. I promise you a line up MVP's and wonderfully talented people sharing their knowledge.

Details on the event can be found here ...

I hope to see some of you in London.