It actually has zero to do with the odd character. The reason it is failing is that the _"Set-CASMailbox" commands acts upon the user's mailbox to allow the device, however the command is trying to pass the device's DistinguishedName as the identity of the user's mailbox, which isn't going to work. It looks like more scripting work is needed. See the post below.
http://www.zerohoursleep.com/2014/03/bulk-approving-existing-activesync-devices-after-enabling-activesync-quarantine/ On Mon, May 12, 2014 at 1:05 PM, Kennedy, Jim <[email protected]>wrote: > So.... > > > > $Devices = Get-ActiveSyncDevice -ResultSize Unlimited > > $Devices | Foreach-Object{Set-CASMailbox $_.DistinguishedName > -ActiveSyncAllowedDeviceIDs @{Add=$_.DeviceId}} > > > > Is not liking Apple device names. They all have this odd character as > below. > > > > iPad*ยง*ApplDQTFNEQHDFHW > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *ccollins9 > *Sent:* Monday, May 12, 2014 11:38 AM > *To:* exchange > *Subject:* Re: [Exchange] RE: Active Sync and passwords. > > > > | %{Set-CASMailbox -Identity $_.smtpaddress -ActiveSyncEnabled $true} > > > > something like this. > > > > This will not accomplish his goal. This command would just simply allow > that user's account to interface with ActiveSync devices (which I am > presuming is already set on all his user's mailbox accounts). It will not > classify a previously "blocked" device as "allowed". See my other email > for the link that will accomplish that goal. > > > > On Mon, May 12, 2014 at 11:30 AM, Javier Santana < > [email protected]> wrote: > > | %{Set-CASMailbox -Identity $_.smtpaddress -ActiveSyncEnabled $true} > > > > something like this. > > >
