I import the cmdlets and then the CD "sitecode:" fails, and that's probably because of access.
Like I mentioned, using the console with SYSTEM doesn't work either. The same script works when using my account which is in the same group as the site server computer name. -R Von: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] Im Auftrag von Patton, Uriah Allen Gesendet: Montag, 18. April 2016 14:13 An: ms...@lists.myitforum.com Betreff: RE: [mssms] Powershell CM cmdlets as system Are you running the script from the CMSite drive, or calling the CMSite drive from within the script? Configmgr cmdlets and scripts have to be run from the CMSite drive. If from a PowerShell console you import your configurationmanager module, then run "Get-PSDrive" and you should see a drive listed with the Provider showing as "CMSite". To get only the CMSite drive run "Get-PSDrive | where {$_.Provider -match "CMSite"}" you should get a result returned that looks something like this. Name Used (GB) Free (GB) Provider Root CurrentLocation -------- ------------- ------------ ----------- ------ ---------------------- CCM CMSite Site-Server-FQDN Where "Name" is your 3 letter site code and the drive from which all your configmgr cmdlets and scripts should be run. Make sure the first lines of your script has the command "Set-Location CCM:" Or from a PowerShell console you could test it by running the set location command and then running "Get-CMSite" which should return information about your site server. You can change locations as often as you want within the script as long as your current location ( can be found by outputting the Get-Location cmdlet somewhere) is set to your CMSite server drive Thanks, Uriah P. IUSM Department of Pediatrics Systems Administrator From: listsadmin@lists.myitforum.com <mailto:listsadmin@lists.myitforum.com> [mailto:listsadmin@lists.myitforum.com] On Behalf Of Roland Janus Sent: Monday, April 18, 2016 2:10 AM 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
