Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've been trying to remotely create a process using WMI (through PowerShell) and i'm experiencing some trouble :

The details :

Remote Server : Windows 2003 R2 (Domain controller).

Local Computer : Windows XP SP3

Situation :

I'm trying to remotely from the Windows XP station to launch a command (notepad.exe, or echo command)...

on the Windows 2003 Server and this systematically fails with the error 3 stating I don't have enough "sufficient privileges". (The account I use is Domain Admin and part of the local administrators group on the Remote Server).

I have read that some settings had to be changed from the WMI control security properties. And some stuff in the gpedit.msc.

All these changes have been applied.

PS U:\> Invoke-WmiMethod -ComputerName SERVER01 -Class Win32_Process - 
Name Create -ArgumentList "Notepad.exe" 
__GENUS          : 2 
__CLASS          : __PARAMETERS 
__SUPERCLASS     : 
__DYNASTY        : __PARAMETERS 
__RELPATH        : 
__PROPERTY_COUNT : 2 
__DERIVATION     : {} 
__SERVER         : 
__NAMESPACE      : 
__PATH           : 
ProcessId        : 
ReturnValue      : 3 

However, i tried to perform the exact same operation on another server and this time it seems to work...

PS U:\> Invoke-WmiMethod -ComputerName SERVER02 -Class Win32_Process - 
Name Create -ArgumentList "Notepad.exe" 
__GENUS          : 2 
__CLASS          : __PARAMETERS 
__SUPERCLASS     : 
__DYNASTY        : __PARAMETERS 
__RELPATH        : 
__PROPERTY_COUNT : 2 
__DERIVATION     : {} 
__SERVER         : 
__NAMESPACE      : 
__PATH           : 
ProcessId        : 5540 
ReturnValue      : 0 

The ONLY difference that i know is that one is a domain controller and the other is not...

I already tried the -Authentication Packet, -Impersonation Impersonate ... but still the same error.

I've been reading a lot about this problem on forums and blogposts but none of the information helped me solve my issue...

Furthermore, like I said, it works on a simple server, but not on the PDC. I hope someone has a clue and i'm sure someone has.

And Thanks in advance for your help. (of course, if any additional info is needed, i will be happy to provide)...

Franz

share|improve this question
    
It seems the issue is due to the fact that the server is a Domain Controller... Indeed, the DCOM Security settings are not the same. –  Franz Jul 14 '11 at 8:00
    
I see you mentioned this, but -Authentication 6 usually fixes my DCOM security issues. Although I mostly see these issues on Windows 2008 R2 as the default settings are different than Windows 2003 –  Chad Miller Jul 17 '11 at 14:03
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.