We recently updated our environment to Exchange 2013 SP1.. So far so good, but we have come across a problem we can't seem to figure out.  In our 2010 enviornment, we were using an edge transport server to apply various legal disclaimers to our outbound email messages (based on recipient domain).  We have since deployed a 2013 edge transport server, but can't seem to get the command together that will allow us to create these rules again.  

This is the command I'm executing:

New-TransportRule -Name 'contoso.com TLS Footer' -Enabled $True -Mode Enforce -RecipientAddressMatchesPatterns '@contoso.com$' -SentToScope NotInOrganization -ApplyHtmlDisclaimerLocation Append -ApplyHtmlDisclaimerFallbackAction Reject -ApplyHtmlDisclaimerText 'The message was protected by the contoso.com TLS Connection.' 

This is the error:

New-TransportRule : A parameter was specified that isn't valid on an Edge Transport server.
At line:1 char:1
+ New-TransportRule -Name "contoso.com tls footer" -Enabled $true -Mode Enforce -Recipien ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (SentToScope:String) [New-TransportRule], ArgumentException
    + FullyQualifiedErrorId : [Server=edge,RequestId=xxxxxxxx,TimeStamp=8/17/2015 7:29:31 PM] [FailureCategory=Cmdlet-ArgumentException] 7C733186,Microsoft.Exchange.MessagingPolicies.Rules.Tasks.NewTransportRule

Any thoughts here?  I've scoured the documentation for this command and can't seem to find what I'm missing.  Why is it considering the 'SentToScope' invalid?

Thanks in advance

• Edited by steelie 11 hours 10 minutes ago formatting

Have you configured Edge Synchronization?

Of course.. That was part of the initial deployment of the edge transport server.  Just for background, the edge server is outside the domain on the perimeter network, and only hosts the edge transport role.  The mailbox and client access roles are hosted inside on different mail servers.  Since I don't have a GUI for edge administration anymore, I can't create the rules without powershell (which in the long run will make this easier, but I can't even get the first one created.)

• Edited by steelie 10 hours 37 minutes ago

I agree with you that such a cmdlet limitation is not documented.  I'll post back if I can find out anything.  I'm afraid I don't have a lab configuration where I can test this out myself.

Can you verify a couple of things?  Please enter:

New-TransportRule -SentToSc

and then press Tab.  Does the parameter name autocomplete?

If you leave out the -SentToScope NotInOrganization parameter does the cmdlet complete?

It does complete successfully to -SentoScope.  We also tried eliminating that property and it fails with the same error, but on the "ApplyHtmlDisclaimerLocation" property.  Very weird... I wonder if the order of the properties is critical?

That would be easy enough to test.  If you let me know the results of more exhaustive testing, I'll be happy to ask about it.