RPC Error in ISE but not when I run manually in console

Question

I'm having a very strange issue. I developed a function that invokes SCCM Machine policy refresh on a remote computer:
Function Refresh-SCCMMachinePolicy {
param($computer = $null)
$ms = new-object system.management.managementscope
$ms.path = “\\$computer\root\CCM”
$mc = New-Object System.Management.ManagementClass($ms , ‘sms_client’,$null)
$mc.invokeMethod(‘TriggerSchedule’,'{00000000-0000-0000-0000-000000000021}’)
Write-Host "Machine policy refreshed on $computer" -foregroundcolor yellow
I set the $computer to a machine name and run these line by line from the console and it works but if I try to run the following in ISE it gives me an RPC error...:
Import-Module 'smodule.psm1'
Import-Module 'ConfigurationManager.psd1'
$computers = get-cmcollectionmembership -CollectionName 'Test'
foreach ($computer in $computers)
Refresh-SCCMMachinePolicy -computer $computer
Remove-Module 'smodule'
Remove-Module 'ConfigurationManager'
I get this error:
The following exception occurred while retrieving member "invokeMethod": "The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)"
At smodule.psm1:74 char:5
+     $mc.invokeMethod(‘TriggerSchedule’,'{00000000-0000-0000-0000-000000000021}’)
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], ExtendedTypeSystemException
    + FullyQualifiedErrorId : CatchFromBaseGetMember
The function above is loaded from smodule.psm1 file.
I also have tried saving the ISE script above as a PS1 file and running it from the console but I get the same error. Both machines have executionPolicy set to bypass.
I have tried many different Firewall configurations to no avail as well. Not sure it would be a firewall issue anyway as it works from the console... Am I missing something?
Thanks!
Tony

Answer 1

Oddly enough, now after I fixed the quotes, it gives me the error in the console too...
I know it was working before because I was watching the SCCM logs on the client and when I would run it, the appropriate logs would start updating...
Update: opened a console window with Admin credentials and it worked...
Yep, you'll need to run elevated.
Don't retire TechNet! -
(Don't give up yet - 12,950+ strong and growing)