Make it easier to use BITS with powershell remoting
Votes from Connect: 23
Original Date Submitted: 5/22/2012 8:58:19 AM
Site Name: PowerShell
Feedback ID: 743030
Frequency: Always Happens
Regression: Yes, this happens in all previous versions
Currently you need to do some serious developing to be able to use bits in a remoting session. Because bits doesn't allow a user logged in with powershell remoting to start jobs: "The remote use of BITS is not supported".
The remoting session has to impersonate System, or call via a process running as System, to be able to call bits.
I want the winrm service to be able to fix this automatically, the powershell commands (in the BitsTransfer module) should work transparently, in the same way the do locally.
The bits ps module wont be a serious replacement for .net framework components (webclient) before it works remotely. It's also a inconvenient surprise that scripts which works locally doesn't works in a remote session.
Product Studio item created by Connect Synchronizer due to creation of feedback ID 743030 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=743030).
1. Log in remoted with powershell (invoke-command is sufficient).
2. Import BitsTransfer module.
3. Run any bits command.
Bits ps module command should work as is does locally.
Internal BugId: 3588
Diego Perez Botero [MSFT] commented
I can confirm that this was fixed as part of the Windows 10 Anniversary Update. Please refer to the updated MSDN documentation: https://msdn.microsoft.com/en-us/library/windows/desktop/ee663885(v=vs.85).aspx#manage_ps_remote_sessions