Hi,If I use a comdlet to create or update users are the connections used secure (SSL encrypted)?I have one management station and a number of exchange servers spread around a WAN. I use that one machine to perform all my administration via cmdlets. The server on which I run the exchange management shell and the domain controller with the appropriate role are not the same and I need to be able to state that the connections are secure and can not be eavesdropped on.I have not been able to find anything in the documentation or in any blogs. If the connection is not secure then that would mean I can not use the cmdlets.Wilfred

The best thing to do would be to implement IPSEC on your servers: http://technet.microsoft.com/en-us/network/bb531150.aspx

Implementing IPSEC on all servers is a huge change. We're now using ADSI, with encryption turned on, and LDAPS for our management. I am looking for the same solution for the cmdlet's, or is all traffic encrypted by default?It would be a step backwards if that is not possible and would delay the project. Just changing a couple of hundred DC's is not something that will be greeted with enthousiasm.Wilfred