OK – that never worked either. Called the 64bit powershell and still no results. Looks like I might have to go the scheduled task route or get Orchestrator to run it for me.
From: Deon Taljard Sent: 17 July 2013 08:59 AM To: [email protected] Subject: RE: [mssms] SCCM 2012 Custom Inventory Hi Sherry, Thanks that helped me troubleshoot. It would appear that the Failoverclusters module doesn’t exist on 64bit machines in the 32bit powershell cmd – I call that module to execute my script. SCCM executes scripts in 32-bit mode I think. Going to try and force it to 64bit mode on 64bit boxes – or try and see if I can get the module to load in 32bit mode. Thanks Deon From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: 16 July 2013 09:22 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] SCCM 2012 Custom Inventory 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]<mailto:[email protected]>> To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[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. ________________________________ ############################################################################################# 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. #############################################################################################
