Thanks! That helps.

Did you intend the ";" on the end to be part of the command line? In other 
words do I use that string litterally as you entered it?

PowerShell.exe -ExecutionPolicy Bypass -Command Enable-PSRemoting -Force;





________________________________
John Marcum
Sr. Desktop Architect
Bradley Arant Boult Cummings LLP
________________________________

From: [email protected] [mailto:[email protected]] On 
Behalf Of Trevor Sullivan
Sent: Friday, September 20, 2013 11:31 AM
To: [email protected]
Subject: RE: [MDT-OSD] RE: Enable WinRM

The command that Trevor posted is a call to the PowerShell commands directly. 
The winrm.cmd you're using is legacy, and probably won't see a lot of continued 
development from Microsoft (AFAIK).

Cheers,
Trevor Sullivan

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
 On Behalf Of Marcum, John
Sent: Friday, September 20, 2013 11:07 AM
To: '[email protected]'
Subject: [MDT-OSD] RE: Enable WinRM

Wonder why I was getting an error then? What's the different in using the WinRM 
command and the command that Trevor posted?

To simplify things I think I may just enable it via GPO instead. Looks like I 
can just set the service to automatic and create a listener on IPv4* and that 
should do the trick. Is that right?









________________________________
John Marcum
Sr. Desktop Architect
Bradley Arant Boult Cummings LLP
________________________________

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Friday, September 20, 2013 11:03 AM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] RE: Enable WinRM

Winrm is an exe, no need to use a command shell to launch it.

J

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
 On Behalf Of Daniel Ratliff
Sent: Friday, September 20, 2013 10:50 AM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] RE: Enable WinRM

Missing cmd /c.

Daniel Ratliff

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Marcum, John
Sent: Friday, September 20, 2013 10:36 AM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] Enable WinRM

Is anyone enabling WinRM in a task sequence? I am trying on Win 7 x64 and the 
step in the task sequence reports it is failing. I am just running the command 
line winrm qc -q

________________________________
John Marcum
Sr. Desktop Architect
Bradley Arant Boult Cummings LLP
________________________________


________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.

________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

Reply via email to