Script deployed by SCCM, writing file to network

[BryanP]

I'm trying to run a script against my computers with SCCM.  It's a very simple powershell script (it has to be, I'm not much of a scripter), and it works perfectly from the command line.  However, when I try to deploy it from SCCM it fails every time.  I've tried writing directly to the share, I've tried mapping a drive, I've tried deploying it with admin rights and using the logged in user's rights. 

I'm hoping someone here can tell me what I'm doing wrong.  The script is below.  I know it works, but I don't know why I can't deploy it.

 

# Write the value of the AutoAdminLogon key to $val

$val = Get-ItemProperty -Path "hklm:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" -Name "AutoAdminLogon"

 

# If the AutoAdminLogon key information exists and it is anything other than 0
# write that information to a file on a network share.
# File will be <computername>.txt

    if($val)
    {

if($val.AutoAdminLogon -ne 0)

        {
        $val | Out-File \\<sharelocation>\AutoAdminLogonLog\$env:COMPUTERNAME.txt"
        }
    }

 

[GarthMJ]

First what do you mean does deploy?

Personally, I would bother with this, instead, I would create a custom inventory item and inventory that. Regkeytomof is the most popular one for that. https://www.enhansoft.com/blog/how-to-use-regkeytomof

[BryanP]

I've been trying to follow those instructions, but when I get to the final step I get an error about "No valid classes or settings were found to import from the MOF file." 

I've gone back through the instructions to make sure I was following them exactly, not missing any characters on the copy & paste, etc, but I get the same results.

Any suggestions?

[GarthMJ]

Without out your mof edits there isn't much anyone can do to help. So post them.

 

Keep in mind that many of us will be out at Mmsmoa.com next week. so expect delayed replies. my flight leaves at 6 am tomorrow. :-) :-(

[BryanP]

Thank you.  I'll get that as soon as I can. 

[BryanP]

Sorry it took so long to get back to this.  I had several things come up that pushed this way down my list of priorities at work for the last week or so. 

I've gone through the entire process again today and I'm getting the same results.  I've attached these files:

 

configuration.mof - this is the untouched configuration.mof file in my inboxes\clifiles.src\hinv folder.

RegKeyToMof_WinLogon.txt - This contains the output of the configuration.mof tab of RegKeyToMof after I selected SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon, and changed the Group label to Custom_Registry.

RCM.mof - this contains the output from the to import in Admin/AgentSettings/HardwareInventory/SetClasses/Import tab

appended_configuration.mof - this is the configuration.mof file listed above with the content of RegKeyToMof_WinLogon.txt appended, in case you need to make sure I didn't screw that up.

Any help is appreciated.  Including "Oh, you might want to click that first ya idjit." 

 

appended_configuration.mof

configuration.mof

RCM.mof

RegKeyToMof_WinLogon.txt

[GarthMJ]

I just imported the RCM.mof and it imports without issues and I'm seeing data in my test lab using these mof edits.

 

[BryanP]

I'm still getting the same error, but at least now I know it's probably something I'm doing wrong.

I haven't had time to look at this, it's been kind crazy here (except that crazy is normal).  I'm about to be gone for a week, and at least for the moment the urgency on this has dropped. 

I'll work on it some more when I get back and hopefully I can figure it out.  Thanks for the help.