I ran into an odd problem in our Exchange 2013 DAG hosting setup. A brief description of is we´re running it as account/resource topology, two Exchange 2013 servers in DAG, two Exchange 2013 domain controllers. (Forest level 2012 R2)
Until yesterday we had, no problems creating customers (forest account users, OU´s, Exchange databases and linked mailboxes). Suddenly I ran into a problem creating the Linked mailbox part, using our PowerShell scripts. (They have worked until now, with no problems)
Well, here´s the deal.
I´m trying to create a new hosting customer (xxx.dk) - creating OU´s in account domain - and creating Exchange 2013 - customer database, E-mail address policy, OAB and ABP. All is fine, until I´m trying to create new Exchange Linked mailboxes for the users in the Account domain with PowerShell.
Getting this error:
” Exception calling "SetInfo" with "0" argument(s): "A device attached to the system is not functioning”
The customer name exceeds 15 characters in the name (18 to be exact) – and my theory is that the number of characters in the customer name is the real problem, not the PowerShell script – or connection to the account domain/forest.
The funny part is, that I can create linked mailboxes from the GUI – without any problems on that same customer ??? What the F***
What is going on here in Exchange 2013 PowerShell?
I can still create new customers with names (i.e mail-hosting.dk) – with 15 characters without any problem at all. No errors using our present Exchange PowerShell scripts. So I guess any scripting error out of the loop. Or?
Is my theory, regarding the number of characters in the Customer name crazy – or is there a limitation in Exchange 2013 PowerShell, when connection to the Account forest ?
Alternatively, is it a limitation in server 2012 R2?
Sorry about the long description.