Exchange 2013 - Unable to execute test-ActiveSyncConnectivity cmdlet

Hello,

I am troubleshooting some Exchange Server 2013 problems related to ActiveSync, and I need to be able to use the test-ActiveSyncConnectivity cmdlet.  I've followed the steps as outlined in the Microsoft Doc here.  However, I receive an error message during the initial New-TestCasConnectivityUser.ps1 script execution (looks like setting attributes to the test mailbox), and I'm unable to execute the test-ActiveSyncConnectivity cmdlet after the script completes.

[PS] C:\Windows\system32>cd \temp
[PS] C:\temp>& $env:ExchangeInstallPath\Scripts\New-TestCasConnectivityUser.ps1
Please enter a temporary secure password for creating test users. For security purposes, the password will be changed r
egularly and automatically by the system.
Enter password: ***********
Update test user permissions on: EXCHANGE13.[REDACTED].local
Click CTRL+Break to quit or click Enter to continue.:
UserPrincipalName: extest_ba8013b96ceb4@[REDACTED].local
A parameter cannot be found that matches parameter name 'MaxSendSize'.
    + CategoryInfo          : InvalidArgument: (:) [Set-Mailbox], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Set-Mailbox
    + PSComputerName        : exchange13.[REDACTED].local

A parameter cannot be found that matches parameter name 'RemotePowerShellEnabled'.
    + CategoryInfo          : InvalidArgument: (:) [Set-User], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Set-User
    + PSComputerName        : exchange13.[REDACTED].local

test-ActiveSyncConnectivity : The term 'test-ActiveSyncConnectivity' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the
path is correct and try again.
At D:\Program Files\Microsoft\Exchange Server\V15\Scripts\New-TestCasConnectivityUser.ps1:83 char:5
+     test-ActiveSyncConnectivity -ResetTestAccountCredentials -MailboxServer:($ma ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (test-ActiveSyncConnectivity:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException


You can enable the test user for Unified Messaging by running this command with the following optional parameters : [-UM
DialPlan <dialplanname> -UMExtension <numDigitsInDialplan>] . Either None or Both must be present.

[PS] C:\temp>

Open in new window


I am a domain admin, and RemotePowerShellEnabled is set to True for my user.  Exchange 2013 is updated to CU8.  Any help on how to troubleshoot and resolve is appreciated.
John SzeglinAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hayes JupeIT DirectorCommented:
hey,
so you can work around this by using

Test-ActiveSyncConnectivity  -UseAutodiscoverForClientAccessServer $true -MailboxServer (Get-Credential user@domain.com)

I've not seen that error when creating a test user before with the script - and find it quite odd.
Have you tried deleting the existing user/mailbox - and then re-running the script? it looks like there's something busted with the test user which may already exist (but be broken?) - I'm not really sure on that part of it.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.