Hello,
My apologies for the radio silence on the blog, its been a very busy time, I'll look to update everyone with some System Center R2 stuff once I've sorted my test lab out.
Tuesday, 20 August 2013
Thursday, 27 June 2013
How to set the Computer Name to a the Serial Number during OSD SCCM 2012 SP1
Hello,
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!
Scenario
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 (http://heinrichandsccm.blogspot.co.uk/2013/04/how-to-setup-and-configure-sccm-2012.html)
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.
Enjoy
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!
Scenario
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 (http://heinrichandsccm.blogspot.co.uk/2013/04/how-to-setup-and-configure-sccm-2012.html)
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.
Enjoy
Sunday, 9 June 2013
SCCM 2012 SP1 Remote Control/Tools Only
Ola,
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.
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 ... https://thedesktopteam.com/events/
I hope to see some of you in London.
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 ... https://thedesktopteam.com/events/
I hope to see some of you in London.
Friday, 24 May 2013
SCCM 2012 SP1 How to boost PXE boot speed
This is a very simple trick I picked up to boost PXE boot, from the distribution point complete the following
From HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP
Add a QWORD value (for 64bit Server OS , I'm using Server 2012) and call it RamDiskTFTPBlockSize
Give it a Hexadecimal value of "4000" or a decimal value of "16384".
I wouldn't advise you go higher than this, but you can drop it if need be.
PXE boot again and you will see a increase in speed.
Enjoy
:)
From HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP
Add a QWORD value (for 64bit Server OS , I'm using Server 2012) and call it RamDiskTFTPBlockSize
Give it a Hexadecimal value of "4000" or a decimal value of "16384".
I wouldn't advise you go higher than this, but you can drop it if need be.
PXE boot again and you will see a increase in speed.
Enjoy
:)
Thursday, 16 May 2013
SCCM 2012 SP1 Management Point error "Call to HttpSendRequestSync failed for port 80/443 with status code 500, text: Internal Server Error"
Tell you what, I have to blame my sales team for this error. Let me explain, they like to push the latest and greatest and that's fine, until you forget old trick of the trade as you have been working with Windows Server 2012 since before it was officially launched ...
So, SCCM 2012 SP1 Management Prole on Windows Server 2008 R2, you need to register ASP.NET v4 with IIS. If you don't you will see the error below in your mpcontrol.log or in the System State Messages in the monitoring workspace.
P.S you don't have to run this on Windows Server 2012 as it used .NET v4 by default.
Solution:
Run the following elevated command prompt on the affected Management Point.
Enjoy.
So, SCCM 2012 SP1 Management Prole on Windows Server 2008 R2, you need to register ASP.NET v4 with IIS. If you don't you will see the error below in your mpcontrol.log or in the System State Messages in the monitoring workspace.
Call to HttpSendRequestSync failed for port 80/443 with status code 500, text: Internal Server ErrorNow I would like to point out that with SCCM 2012 pre SP1 this was never an issue as it uses .NET 3.5.
P.S you don't have to run this on Windows Server 2012 as it used .NET v4 by default.
Solution:
Run the following elevated command prompt on the affected Management Point.
cd /d %windir%\Microsoft.Net\Framework64\v4*Any questions please ask.
aspnet_regiis –i –enable
Enjoy.
Wednesday, 15 May 2013
SCUP for Windows Server 2012 (SCCM 2012 SP1)
Good news, Microsoft have finally update their documentation to show that Windows Server 2012 and SCUP can now play ball together.
I have also managed to integrate this with SCCM 2012 SP1 and its working like a charm.
http://blogs.technet.com/b/configmgrteam/archive/2013/05/14/support-announcements-for-may-2013.aspx
Enjoy
I have also managed to integrate this with SCCM 2012 SP1 and its working like a charm.
http://blogs.technet.com/b/configmgrteam/archive/2013/05/14/support-announcements-for-may-2013.aspx
Enjoy
Subscribe to:
Posts (Atom)