I don't have access to boxes that have root\mscluster, so I can't help you; but 
what I can suggest is that you experiment with your script(s) under system 
context on a box you expect to work.

psexec -s -i cmd.exe

to get you to system context on a box; then it's just experimenting with your 
scripts until the output shows up like you expect it to.

 
Sherry Kissinger



________________________________
 From: Deon Taljard <[email protected]>
To: "[email protected]" <[email protected]> 
Sent: Tuesday, July 16, 2013 2:28 AM
Subject: [mssms] SCCM 2012 Custom Inventory
 


Hi,
 
I’m trying to inventory the classes in root\MSCluster on our servers via SCCM 
2012.
 
I’ve added the classes via the SCCM console but no rows get returned.  I’ve 
created a powershell script that creates a custom WMI class and reads from 
these classes into the new class that works perfectly if I’m logged into the 
server and test it.
 
If I deploy the script via SCCM it returns no rows – so I guessing same 
problem.  Seems like the SYSTEM context doesn’t have access to this.
When I used vbscript in sccm2007 this method worked.  I’d prefer to use 
powershell going forward.
 
I’ve also tried running the SCCM agent on the server under an administrator 
service account but this just seems to break the agent from an inventory point 
of view.
 
The only other way I can think of is to create a scheduled task that runs the 
script but I’d prefer to keep it closer to SCCM and schedule directly with SCCM.
 
Anyone been successful in doing this ?
 
Thanks
Deon  
________________________________
  
 The information 
transmitted is intended only for the person or entity to which it is addressed 
and may contain confidential and/or privileged material. Any review, 
retransmission, dissemination or other use of, or taking of any action in 
reliance upon, this information by persons or entities other than the intended 
recipient is prohibited. If you received this in error, please contact the 
sender and delete the material from any computer.
Furthermore, the information contained in this message, and any 
attachments thereto, is for information purposes only and may contain the 
personal views and opinions of the author, which are not necessarily the views 
and opinions of the company.
________________________________


Reply via email to