-
1
- #1
If you're configuring synthetic test accounts for use in Lync, you need to use the New-CsHealthMonitoringConfiguration cmdlet. When you do, if your test accounts have a samaccountname that is more than 15 characters, you'll get a fairly obscure error message:
The documentation for the cmdlet, doesn't mention a requirement for length. When you look at you see that from a Windows perspective, the name can usually be up to 19 characters.
If you shorten the samaccountname to 15 characters or less, New-CsHealthMonitoringConfiguration will work.
Do you have your Tek-Tips.com Swag? I've got mine!
Stop by the new Tek-Tips group at LinkedIn.
Code:
New-CsHealthMonitoringConfiguration : Cannot create item "usfwa1l14fepool1.domain.com": "Invalid value for FirstTestSamAccountName. Value must match pattern:[^\\/:\*\?\"<>\|\.][^\\/:\*\?\"<>\|]{0,14}\\[^\\/:\*\?\"<>\|\.][^\\/:\*\?\"<>\|]{0,14}"
At line:1 char:36
+ New-CsHealthMonitoringConfiguration <<<< -identity usfwa1l14fepool1.domain.com -FirstTestUserSipUri "sip:SVC-EIS-LyncSynTest1@domain.com" -FirstTestSamAccountName "Corp\SVC-EIS-LyncSynTest1" -SecondTestUserSipUri "sip:SVC-EIS-LyncSynTest2@domain.com" -SecondTestSamAccountName "Corp\SVC-EIS-LyncSynTest2"
+ CategoryInfo : InvalidArgument: (usfwa1l14fepool1.domain.com
:String) [New-CsHealthMonitoringConfiguration], PropertyArgumentException
+ FullyQualifiedErrorId : InvalidNew,Microsoft.Rtc.Management.Internal.New
HealthMonitoringConfigurationCmdlet
The documentation for the cmdlet, doesn't mention a requirement for length. When you look at you see that from a Windows perspective, the name can usually be up to 19 characters.
If you shorten the samaccountname to 15 characters or less, New-CsHealthMonitoringConfiguration will work.
Do you have your Tek-Tips.com Swag? I've got mine!
Stop by the new Tek-Tips group at LinkedIn.