Appendix A: Frequently asked questions
1. Is it mandatory that the user invoking a remote session has administrator privileges?
A: Not necessary. Any non-administrator user can start a remote session if he/she has invoke permissions to a session configuration on a remote computer. Refer to Chapter 7 for information on how to do this.
2. Do I need PS remoting enabled on all the computers participating in remoting?
A: No. You need to enable PS remoting only if you want to receive commands from a remote machine.
3. Why I don’t see my profile getting loaded when I create a remote session?
A: Good question. PowerShell Profiles are not loaded automatically when you create a remote session. You have to manually run the profile script. Or you can create a custom startup script -– as shown in Chapter 7 – to load the profile.ps1, and use –StartupScript parameter to run the script every time you create a remote session.
4. Is there a place where a comprehensive list of FAQ is provided?
A: Yes. Microsoft’s TechNet has a complete article on this. Refer to
http://technet.microsoft.com/en-us/library/dd315359.aspx
5. Are there any product specific remoting requirements for products such as SharePoint, Exchange, and etc?
Yes. For SharePoint 2010 remoting, check Zach Rosenfield’s blog post:
http://sharepoint.microsoft.com/blogs/zach/Lists/Posts/Post.aspx?ID=45
For Exchange 2010 remoting, check Mike’s blog post:
http://www.mikepfeiffer.net/2010/02/managing-exchange-2010-with-remote-powershell/
For Lync Server 2010, check this TechNet blog post:
http://blogs.technet.com/b/csps/archive/2010/08/03/scriptremotedesktopicon.aspx
6. How do I enable unencrypted traffic in a remoting session?
You can do so by changing WSMan attributes on the client end. At an elevated PowerShell Console, Set-Item WSMan:\localHost\Client\AllowUnencrypted –Value $true