• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5279
  • Last Modified:

Command Line in SCCM OSD

Hello,

I am having some challenges with applying some reg keys during OSD. I have a task sequence that uses a command line to run a cmd /c REG ADD .... and it does not run or at least it does not add the info to the registry.

Before that step, we use a cmd.exe /c NET LOCALGROUP to add a user to to localadmin and works. What could be preventing this from running?
0
teamfox201
Asked:
teamfox201
  • 6
  • 4
  • 2
  • +1
2 Solutions
 
Neil RussellTechnical Development LeadCommented:
If this is durring OSD then why not just have it done on the base image?
0
 
merowingerCommented:
Could you please post a screenshot from that "run command line" step in the task sequence
0
 
KezziCommented:
Are you updating an existing key or amending one?
I use REG ADD command lines during my task sequence and they fail if the key already exists.  So I add a REG DELETE before that to remove the existing key then ADD it back with the new value.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
KezziCommented:
Also, do you use the /f option to force it?
0
 
teamfox201Author Commented:
Neilsr:  The key values change based on a hta script that runs earlier.

Merowinger:  I am not in front of the comp right now but I know the command works because if I press F8 during the TS and manually type it in, it will work.

Kezzi:  Like the first user suggested the base image has the image version coded into the wim in HKLM\SOFTWARE\Comp Name and that's the only value that doesn't need to get written. I wonder if since the Comp Name key exits, the Reg add "hklm\software\comp name" /v "Owner " /t REG_SZ /d %owner% /f... The variables are passed from the hta script. I could try to delete the Comp Name then use reg add in the T'S. Will test this and report back.
0
 
merowingerCommented:
x64 or x84 machine?
0
 
teamfox201Author Commented:
x86
0
 
teamfox201Author Commented:
Ok so I ran a reg delete in my TS and it does not remove that key. I even added a step to create a random HKLM\SOFTWARE\AA key but that was not created either. I don't get why this is not working. During this stage the OSD in not in WinPE but in the Current OS.

I attached a screenshot of one of the TS commands. REG ADD
0
 
KezziCommented:
ok heres an idea.  maybe the variable isnt being parsed by the reg command.   so have you tried adding a key that does not consists of a %variable%?

if you use variables, i think it has to be a REG_EXPAND_SZ but then that might just write it as %variable% instead of what it parses as.
0
 
teamfox201Author Commented:
I just tried this one and it did not write either.

 random key
0
 
KezziCommented:
you dont need to specify /t REG_SZ as by default its a REG_SZ unless otherwise specified

My command line is simpler than yours.  Mine is just:
REG ADD "HKLM\Software\Build" /v "Version" /d "Windows 7 1.2a" /f
and making sure the Start in: has C:\windows\system32
0
 
teamfox201Author Commented:
OK I am back in business, apparently command prompt scripts in the TS need the Continue on error option checked since it probably does not send back a successful code if it executes.

I thank you all for your support!
0
 
teamfox201Author Commented:
I figured out why my script was not running.
0

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 6
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now