?
Solved

Cannot create exchange 2013 linked mailbox user with powershell, but works with GUI

Posted on 2014-08-02
2
Medium Priority
?
951 Views
Last Modified: 2014-08-03
Hi everyone.
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.

Please help

Best regards
Peter
0
Comment
Question by:Peter Nørredal
  • 2
2 Comments
 

Author Comment

by:Peter Nørredal
ID: 40237031
Hi Again
When testing further, I realized that the error Begins when I try to create customers with 17 characters or more, regardless of combination (I.E: Exchange-mails.dk Status= Fail (17 characters), Cykelbanditten.dk status=fail (17 characters, but without a dash (-))

Is there by any chance a buffer size limit in Exchange powershell ?
so it cannot hold more than 16 characters - I´m confused to the MAX

Thanks
0
 

Accepted Solution

by:
Peter Nørredal earned 0 total points
ID: 40237143
I think I figured out what the problem is.

The SAM-Account-Name (User Logon Name (pre-windows 2000) when creating a new Linked Mailbox user cannot exceed 20 characters - so I have to format the output of this before creating the AD user object in account forest.

Some times I really HATE that backwards compatibility Microsoft insist of keeping in Active Directory.

Thanks
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you have come across a situation where you need to find some EDB mailbox recovery techniques, then here you will find the same. In this article, we will take you through three techniques using which you will be able to perform EDB recovery. You …
Steps to fix error: “Couldn’t mount the database that you specified. Specified database: HU-DB; Error code: An Active Manager operation fail”
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question