AW: [mssms] Powershell CM cmdlets as system

[Roland Janus]

I guess it starts with the console not even working, once that does the
scripts might.

But when I start the script as system, it can’t connect to the CM-drive. I
guess because access doesn’t work, hence I start with getting the console
working first.

 

You’re script doesn’t use the CM-cmdlets, but regular wmi commands. That
probably would work for me to.

Maybe it is sms provider related.

 

-Roland

 

 

Von: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com]
Im Auftrag von Andreas Hammarskjöld
Gesendet: Montag, 18. April 2016 10:42
An: ms...@lists.myitforum.com
Betreff: RE: [mssms] Powershell CM cmdlets as system

 

What is the exact issue? We got a similar thing here:
http://2pintsoftware.com/branchcache-enable-task-sequences-sccm/ 

 

I know the status filter rule + PS is very tricky on the quotes and you have
to start the right PS by using full cmdline to the right version of PS.

 

From: listsadmin@lists.myitforum.com <mailto:listsadmin@lists.myitforum.com>
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Roland Janus
Sent: den 18 april 2016 08:10
To: ms...@lists.myitforum.com <mailto:ms...@lists.myitforum.com> 
Subject: [mssms] Powershell CM cmdlets as system

 

What is required on the server to have Powershell ConfigManager cmdlets run
as system within a status filter rule?

 

The computer account is in the same group as my account, granting full admin
access to CM and SMS provider.

I’ve also enabled “SYSTEM” to have remote access on DCOM.

 

The script doesn’t seem to have CM access.

So I’ve tried running the console as system (psexec), but the console
complains about not having enough access.

What am I missing?

 

-R