Tag Archives: configmgr

ConfigMgr 2012 R2, Query HKLM with Hardware inventory

introduction:

When you like to use a registry keys query in a ConfigMgr collection, you first have to Extend SCCM client Hardware Inventory with a Custom Attribute value.

You can do this with this description of Jyri Lehtonen.

After this you have changed the Configuration.mof en the MyInventoryExtension.mof

ConfigMgr-inventory-configurationmof

configuration.mof

MyInventoryExtension.mof

MyInventoryExtension.mof

Now create a Collection with a query

create collection query

create collection query

Select the value of the registry key

query value

query value

 

the query looks like this:

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_Custom_UMCGDeployID_1_0 on SMS_G_System_Custom_UMCGDeployID_1_0.ResourceId = SMS_R_System.ResourceId where SMS_G_System_Custom_UMCGDeployID_1_0.TSVersion = “BUILD017_00”

ConfigMgr Task Sequence with OSD Options Chooser and computer OU move

The OSD Options Chooser will display an option chooser box during OSD when a computername starts with MININT or MINWINPC (unknown computers). The user can type a computername and choose in which Active Directory OU the computer will be placed during the installation. It will set a Task Sequence variable OSDDepartment which will be used in the Task Sequence to move a computer to another OU.
When the computername doesn’t start with MININT or MINWINPC the Options Chooser won’t pup-up.

In this example the OSD Option Chooser will ask for a computer name and gives 4 computer type choices. The installation will be un-anttended and will close when the computername does NOT start with MININT or MIN-WINPC.

1. Create a source directory and place the two file with the name:
• OSDOptionsChooserv3.hta
• OpenDesktop.vbs

You can find the source at the end of this page.

2. Check the code in the: OSDOptionsChooserv3.hta

3. Check the code in the: OpenDesktop.vbs
Change the values in the .vbs

4. Create a Configuration Manager Package and deploy it to the distribution points.
BLS0122 OSD Options Chooser

5. Open the boot image and add the Optional Component:
HTML (WinPE-HTA)
deploy this boot image to the distribu-tion points.

6. Open a Task Sequence and add the OSD Option Chooser package right after Partitioning the disks.
This first part will show the Option Chooser for unknown computers (MININT or MINWINPC).

7. The second part will move the computer to the OU which was specified in part one.

8. Open the Options tab and ad a Task Sequence Variable OSDDepartment.

__________________________________________________________
I included one zip file with the OSDOptionChooser and OpenDesktop.vbs script we used within our company.

We added extra lines to the original script:
window.close
and
SysVarReg.RegWrite “HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Hostname”, sTSMachineName

And added parts for setting the Task Sequence variable OSDDepartment (OU options).
We deleted some parts we didn’t need.
####################################################################

####################################################################

you can find the original OSD Options Chooser script Created by Nick Moseley at http://t3chn1ck.wordpress.com

Installing an SSD equipped machine with the Configuration Manager Task Sequence is causing problems. #yam

We had a problem deploying new laptops / notebooks with Sollid State Disk (SSD). They just came out of the box. The vendor had them pre-installed with eg. Windows 7.

We see that there is a problem when an Operating System is distributed by System Center Configuration Manager to client computers with SSD. There is no problem Continue reading

System Center configuration Manager 2012 SP1; How to change the Automatic Client Upgrade checkbox from greyed out to editable?

In Configuration Manager 2012 SP1 you could run into an Automatic Client Upgrade property being greyed out even if the user is a full administrator.

 Sites Hierarchy Settings         Site Settings Properties - automatic Client Upgrade - grayed out

In this example the user is a member of an Active Directory group called ADSBehWPBSCCMLG that has Full Administrator rights within the Configuration Manager site but is not able to use the Automatic Client Upgrade settings.

administrative users

 

Solution

  • log in with the account which was used when the site server was installed.
  • Go to Administration | Security | Administrative Users. Continue reading