Mailbox Creation

My Macbook has two accounts. My wife and myself. My wife's mail account will not allow her to add additional mailboxes (For example Shopping). When we try to do so we receive the following notice "Unable to create path -/Library/Mail/Mailboxes/Shopping.mbox".
My mail account works fine and I can add mailboxes at will.
Suggestions?

Bob,
Clarify: you have two User Accounts on your Macbook, and in the one used by your wife, Mail and her email account will not allow this? Or is it one User Account and two email accounts?
Ernie

Similar Messages

Multi Tenant public folder primary mailbox creation - auto-discover warning.

Here is the background.
2013 running a primary domain (contoso)
multiple tenants (microsoft) (Lenovo) (Dell) all setup with Custom Attributes that keep them separate. with unique EAP's GAL's etc
I am trying to now implement Public Folders. 2013 is somewhat different to what i have experience with in 2k7/ 2k10
As i understand it, i need to have a Primary Public Folder Mailbox (in this case Contoso_Public) and then secondary Public Folder Mailboxes for each tenant (Microsoft_Public, Dell_Public and Lenovo_Public)
My issue lies in when i create the primary Public Folder Mailbox, all tenants are prompted with an Autodiscover record for [email protected] in outlook.. "Allow or Deny"
I dont want the tenants to see this as they should only see Microsoft_Public or Dell_Public.
I cant use get-mailbox | where {$_.customattribute1 -eq "Dell"} | set-mailbox -DefaultPublicFolderMailbox "Dell_Public" for example until the Public folder Mailbox has been created..
But i cant create the PFMailbox without the Autodiscover for contoso_Public appearing for ALL users on the Exchange box.
What am i missing here?
Is there a way to create a PFMailbox with permissions during creation so that all users aren't prompted for the Autodiscover of a PFMailbox they wont ever have access to?
Cheers,
DEE

Hi,
Do you mean the public folder still cannot be seen even you logged the Outlook 2007 good user on an Outlook 2013 machine?
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2007 mailbox creation error

Hi,
We are having problems with our standard AD/Exchange adapter when creating users with a mailbox.
We currently have the following setup:
- Sun IdM 8.1.0.7
- There are 4 DC, and two Exchange 2007 Servers.
- The gateway runs on a seperate Win2003 R2 32 bit server (but is a member of the AD).
The error we are getting is this:
PowerShell:41b59779-b9cb-487f-b200-4b9836dc176d is not a mailbox user.
It seems like the gateway has a preferred DC when creating accounts.
But when creating the Exchange account, the Exchange server has a different preferred DC,
where the AD account is not yet present. (there is an 5 minute replication interval)
We don't have a test enviroment with the same setup, which makes it a bit tricky to find the problem,
and testing possible solutions for it. Out test enviroment consists only of 1 DC, and 1 Exchange server so
the errors does not exist there.
Is there anyone who has seen something like this before, and in that case, is there a solution for it?
Or it's maybe better if a put it like this: Is there anyone who is running multiple DC:s and multiple Exchange Servers
without these problems? And in that case, are you creating the user and the mailbox at the same time?
I would gladly provide some more info and logs, if you specify what might be interesting to see.
Thanks and kind regards,
Henrik

Some additional info:
Today the process goes like this:
First we create the user and does not set the RecipientType -> The user is created in AD (without Mailbox)
Second we set the following attributes when we want the user to get a Mailbox: (5 min delay)
EmailAddressPolicyEnabled = false
PrimarySmtpAddress = [email protected]
RecipientType = MailboxUser
Database = <our-db-here>
The user now gets his mailbox, but the email generated by Exchange is used when I look at the user.
And also the EmailAddressPolicy stays enabled.
Any ideas about the attributes I'm trying to set here?
Regards,
Henrik
Edited by: user1154522 on Apr 12, 2011 8:44 AM

Regarding MailBox Creation

What are all the attributes that must be added to the LDAP for creating mail boxes (INBOX/TRASH/SENT/DRAFT) .
Whenever i try to do add the following entries:
nswmExtendedUserPrefs :meDraftFolder=Drafts
nswmExtendedUserPrefs :meSentFolder=Sent
nswmExtendedUserPrefs :meTrashFolder=Trash
The last one(nswmExtendedUserPrefs :meTrashFolder=Trash) overwrites the previous entries(nswmExtendedUserPrefs :meSentFolder=Sent
, nswmExtendedUserPrefs :meDraftFolder=Drafts
Whereas if you provision a user and do login thro the console ,these properties are properly set in the LDAP.
How to create the mailboxes from the LDAP?What entries need to be added in the LDAP ?

Basically what i am trying to do is :
1.I need to provision a user in the LDAP if the user is new / update the users account such that the updated user has mail box access if the user already exist.
2.Whenever we create a new user and use mboxutil to list the users mail box , it shows nothing for the newly created user.
3.Whereas if you do login/logout thro the console [for the newly created user ]and then if you try mboxutil to list users mailbox ,it shows INBOX/DRAFTS/TRASH/SENT mailboxes.
4.Another way of creating a mailbox is using javamail.If you try to query the users mailbox it creates only INBOX and not the other mailboxes[SENT/TRASH/DRAFTS].
My question is :
Is that sufficient if we provision a user in the LDAP with the very basic attribute.Or do i need to add any other specific attribute.?
Please also let me know what are all the attributes that i need to use while provisioning a user who has access to Calendar as well as Messaging Server.

Error msg: Mailbox Creation Failed

I'm getting this error message with: "Unable to create path ~/Library/Mail/Mailboxes/Mail Archive.mbox"
I'm assuming a linked problem is associated with trying to copy my mailboxes from my Powerbook to my desktop. When I couldn't do this - I tried setting up a mailbox on my desktop and got this message.
I couldn't find this topic - any suggestions most welcome!

Apparently, Mail has a bug that causes ~/Library/Mail/Mailboxes to sometimes be a file instead of a folder, and that prevents Mail from creating any mailboxes there.
Verify/repair the startup disk (not just permissions), as described here:
The Repair functions of Disk Utility: what's it all about?
After having fixed all the filesystem issues, if any, proceed as follows:
1. Quit Mail if it’s running.
2. In the Finder, go to ~/Library/Mail/.
3. Locate Mailboxes. If it’s a file instead of a folder, move it to the Trash.
4. Open Mail. A new Mailboxes folder should be created automatically and that should fix the problem.
If ~/Library/Mail/Mailboxes is already a folder, then the problem must be something else (e.g. a permissions issue). In that case, don’t trash anything. Instead, open /Applications/Utilities/Terminal, type the following command (you can just copy it here and paste it in Terminal), and press <Return>:
ls -ld ~/Library/Mail ~/Library/Mail/Mailboxes
Copy the output of that command from Terminal and paste it in your reply to this post.
Note: For those not familiarized with the ~/ notation, it refers to the user’s home folder. That is, ~/Library is the Library folder within the user’s home folder, i.e. /Users/username/Library.

Mailbox Creation Failed

We just transferred to a new IMac, and I cannot create any mailboxes. I can create Smart Mailboxes (which I find useless), but to create a normal mailbox, I get the message "Unable to create path ~/Library/Mail/Mailboxes/xxxx.mbox." Any suggestions about what I am doing wrong?
Thanks,
Cheryl

In the ~/Library/Mail folder there is a folder for each of your accounts. I take it you only have one. These folders are called POP-mailaccountname or IMAP-mailaccountname. They hold the mailboxes associated with accounts - Deleted, Drafts, Inbox etc. Additional mailboxes that you create are not associated with specific accounts, and go in the Mailboxes folder - or should do, if you could create any.
You did not say whether you have write privileges to the Mailboxes folder. If you haven't, change them so you have. If you have, quit Mail and make a new folder in Mailboxes eg Test.mbox then restart Mail and see if it spots it.
AK

Unwanted mailbox creation/display- .mailboxlist, procmail.log, etc..

I'm using my university's IMAP webmail service set up through Apple Mail.
Apple Mail is displaying all of these unused folders such as .mailboxlist, procmail.log, .proc-mailrc-blacklist, etc...
What do these mailboxes do and how do I make them not be shown in Mail?
Thanks

Are all the server-stored mailboxes subfolders of a parent folder called “mail” maybe? If that’s the case, you could solve the problem by typing the name of the parent folder (i.e. mail, if that’s how it’s called) in Preferences > Accounts > Advanced > IMAP Path Prefix so that Mail ignores any files & folders on the server that aren’t within it.

Mailbox creation on ipod touch

how do I create new mailboxes on mail on my ipod touch? Are inbox and trash the only ones allowed?

Dear lllaass - I don't know what did it, but I shut it down last night. This afternoon I tried again it it started updating!!! So thank you! Now I will click on this "This solved my question". sharon 543

Mailbox creation on AD using ActiveSync form

Hi all,
Through the activeSync, I want to create a user and his mailbox on AD whenever a user is created on an Ldap resource.
During feedop=Create:
I can create a new user in AD, but not the mailbox. It appears that I can't set any value in the mailbox attributes (proxyAddresses, mailNickName, homeMDB).
It behaves like IDM doesn't recognize these attributes despite they are defined in the schema mapping. I check the userview of the new created user, and these attributes are not available.
During feedop=Update:
I can set the mailbox attributes and the user mailbox is created successfully.
Is it a normal behavior on the AD side?
Someone has any solution to this? Wha mailbox cannot be set during the feedop Create?
Thanks,

Hi,
now I can create Exchange Mailboxes, too! :-)
I added
-homeMDB
-homeMTA
-msExchHomveServerName
in the Resource Schema Map.
(On te Resource Page: Edit Resource Schema in the Resource Action field)
Then I updated the "Exchange Server 2000 attributes" section in the AD User Form.xml with the correct values (for homeMTA, homeMDB, server names...).
In order to submit the "mailNickName" attribute I created a field in the AD User Form.xml like this:
<Field name='accounts[$(RESOURCE_NAME)].Mail Nick Name'>
<Display class='Text'>
<Property name='title' value='Mail Nick Name'/>
<Property name='size' value='20'/>
<Property name='noNewRow' value='true'/>
</Display>
<Default>
<ref>waveset.accountId</ref>
</Default>
</Field>
I appreciate any of your comments on that. ;-)

Exchange mailbox creation for child domain

Hi Friend,'
I want to add a child domain,some thing like group.domain.com. We have an exchange 2013 in the network, my requirement is to create 50 users in the child domain and create mail accounts for this child domain users.
My main challenge is to create the CDC and my exchange have the name space domain.com and my CDC is group.domain.com,but i want to add users in mailserver for the CDC users as [email protected]
I know how to add additional suffix in exchange and AD :
http://www.sysguru.in/2014/09/creating-additional-suffixname-space-in.html
Is it possible to use the same scenario for my CDC users also?
Regards

Hi,
In your case, if you want to add additional suffix in your Exchange server in the child domain, you need to add the root domain as an accepted domain.
Here is an article about accepted domain for your reference.
Accepted domains
https://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Automatic Mailbox Distribution problem after Creating New AD Site

We redesigned our Active Directory Sites a little while ago. We moved the subnets and servers from the old sites to the new sites. We haven't removed the old sites yet, but that will happen soon. We haven't noticed any issues with the new
sites except for one weird issue and that is that Automatic Mailbox Distribution no longer works, in fact if you don't specify a database with the enable-mailbox (or new-mailbox) commands it will fail with an error that load balancing failed to find a valid
mailbox.
The problem, from the output of an enable-mailbox, command appears to be a site problem (from the fact that the automatic mailbox distribution discards sites that are not in the same site as the user). The verbose output has the command checking the
old site even though the server is in the new site. I've already checked the databases and none of them have the IsExcludedFromProvisioning or IsSuspendedFromProvisioning properties set to TRUE
My question is how do I make the databases show up as in the new site rather than the old site?
Any and all help with this issue is appreciated.
This is the output from the command:
VERBOSE: [16:36:50.864 GMT] Enable-Mailbox : Initializing Active Directory server settings for the remote Windows
PowerShell session.
VERBOSE: [16:36:50.864 GMT] Enable-Mailbox : Active Directory session settings for 'Enable-Mailbox' are: View Entire
Forest: 'False', Default Scope: 'domain.local', Configuration Domain Controller: 'DC01.domain.local', Preferred Global
Catalog: 'VMDC01.domain.local', Preferred Domain Controllers: '{ VMDC01.domain.local }'
VERBOSE: [16:36:50.864 GMT] Enable-Mailbox : Runspace context: Executing user: domain.local/All Users/AD/Admin1,
Executing user organization: , Current organization: , RBAC-enabled: Enabled.
VERBOSE: [16:36:50.864 GMT] Enable-Mailbox : Beginning processing &
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 0 for cmdlet extension agent "Query Base
DN Agent".
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 1 for cmdlet extension agent "Rus Agent".
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 2 for cmdlet extension agent "Mailbox
Resources Management Agent".
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 3 for cmdlet extension agent "Mailbox
Creation Time Agent".
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 4 for cmdlet extension agent
"Provisioning Policy Agent".
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 5 for cmdlet extension agent "Admin Audit
Log Agent".
VERBOSE: [16:36:50.927 GMT] Enable-Mailbox : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient Write
Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient Scope(s):
{}, Exclusive Configuration Scope(s): {} }
VERBOSE: [16:36:50.927 GMT] Enable-Mailbox : Searching objects "domain.local/All Users/SM/GP/User1" of type
"ADUser" under the root "$null".
VERBOSE: [16:36:50.942 GMT] Enable-Mailbox : Previous operation run on domain controller 'VMDC01.domain.local'.
VERBOSE: [16:36:50.974 GMT] Enable-Mailbox : Load Balance : Database container located at 'CN=Databases,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local'.
VERBOSE: [16:36:50.974 GMT] Enable-Mailbox : Searching objects of type "MailboxDatabase" with filter
"(&((IsExcludedFromProvisioning Equal False)(IsSuspendedFromProvisioning Equal False)(Recovery Equal False)))", scope
"OneLevel" under the root "Databases".
VERBOSE: [16:36:51.005 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.021 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.021 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.021 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.021 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.021 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.052 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.052 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.052 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.052 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Load Balance : The search for databases returned an empty result. This
could happen if all databases are excluded from the Load Balance process.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Load Balance : There is no available database. Refer to previous verbose
messages for more information.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Admin Audit Log: Entered Handler:OnComplete.
Load balancing failed to find a valid mailbox database.
+ CategoryInfo : NotSpecified: (0:Int32) [Enable-Mailbox], RecipientTaskException
+ FullyQualifiedErrorId : 4AE0EA04,Microsoft.Exchange.Management.RecipientTasks.EnableMailbox
VERBOSE: [16:36:51.083 GMT] Enable-Mailbox : Ending processing &

Hi,
From your description, I would like to clarify the following thing:
By default, all online and healthy mailbox databases on Exchange 2010 servers in the local Active Directory site can be chosen by automatic mailbox distribution to store a new or moved mailbox. Mailbox databases in other AD site can't be chosen by automatic
mailbox distribution to store a new or moved mailbox.
What's more, I recommend you use the following cmdlet to enable mailbox and check the result.
Enable-Mailbox -Identity xxx -Database xxx
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Trying to Migrate a Mailbox to O365

Hello. I don't know much about scripting or PowerShell but I'm having troubles getting something to work and I'm hoping that someone might help me out. I am running O365 in a hybrid config with my on premise Exchange 2010 server. Because I'd
like to keep my on premise Exchange server and my local domain controllers, I was told elsewhere that, to create new accounts, I have to create them locally, migrate them up to Office 365 and then assign an O365 license to them. That is how I have been
creating all of my new users and shared mailboxes in the 6 months or so that we have been using O365. I have begun dabbling with PowerShell and I'd like to find a way to automate the mailbox creation a bit. I have figured out how to create a new
local mailbox and set all necessary properties on it but I would also like to be able to migrate it up to O365 via PowerShell and that's the part that I'm having trouble with. Here's what I have so far:
New-Mailbox -Name JustaTest -Alias JustaTest -OrganizationalUnit "mydomain.com/My OU" -Database "Mailboxes" -UserPrincipalName [email protected] -Shared
Add-MailboxPermission JustaTest -User "MyDomain\Me" -AccessRights FullAccess
Add-ADPermission JustaTest -User "MyDomain\Me" -ExtendedRights Send-As
Set-Mailbox "JustaTest" -EmailAddresses SMTP:[email protected],[email protected]
$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $Session
New-MoveRequest -Identity “JustaTest” -Remote -RemoteHostName “localmailserver.mydomain.com” -TargetDeliveryDomain mydomain.mail.onmicrosoft.com -RemoteCredential $Session
The first 4 lines work great but the problems begin when I get to the move request. I'm getting this when it gets to that part:
C:\Windows\system32>New-MoveRequest -Identity "JustaTest" -Remote -RemoteHostName "localmailserver.mydomain.com" -TargetDeliveryDomain mydomain.mail.onmicrosoft.com -RemoteCredential $Session
Cannot process argument transformation on parameter 'RemoteCredential'. Cannot convert the "System.Management.Automation.Runspaces.PSSession" value of type "Deserialized.System.Management.Automation.Runspaces.PSSession" to type "System.Management.Automation.PSCredential".
+ CategoryInfo : InvalidData: (:) [New-MoveRequest], ParameterBindin...mationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,New-MoveRequest
+ PSComputerName : localmailserver.mydomain.com
Any assistance that can be provided would be very much appreciated.
Thanks in advance.
-Chris

Hi Chris,
You passing the PSSession object ($Session ) to -RemoteCredential.
Aren't you suppose to Pass the Admin credential object here ($UserCredential )
Incorrect:New-MoveRequest -Identity "JustaTest" -Remote -RemoteHostName "localmailserver.mydomain.com" -TargetDeliveryDomain mydomain.mail.onmicrosoft.com -RemoteCredential $Session
Corrected:
New-MoveRequest -Identity "JustaTest" -Remote -RemoteHostName "localmailserver.mydomain.com" -TargetDeliveryDomain mydomain.mail.onmicrosoft.com -RemoteCredential $UserCredentialorGet-Mailbox -Identity "JustaTest" | New-MoveRequest -Remote -RemoteHostName localmailserver.mydomain.com -RemoteCredential $UserCredential -TargetDeliveryDomain "mydomain.mail.onmicrosoft.com"
How about we validate the below points as well. Like is Get-Mailbox working on remote or not.
After Step 4, the
Exchange Online cmdlets are imported into your local Windows PowerShell session as tracked by a progress bar. If you don’t receive any errors, you connected successfully.
A quick test is to run an Exchange Online cmdlet—for example, Get-Mailbox—and see the results.
If you receive errors, check the following requirements:
A common problem is an incorrect password. Run the three steps again and pay close attention to the user name and password you enter in Step 1.
To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to your Exchange Online organization.
Windows PowerShell needs to be configured to run scripts. You only need to configure this setting once on your computer, not every time you connect. To enable Windows PowerShell to run signed scripts, run the following command in an elevated Windows PowerShell
window (a Windows PowerShell window you opened by selecting Run as administrator).
Set-ExecutionPolicy RemoteSigned
The account you use to connect to Exchange Online must be enabled for remote Shell. For more information, see
Manage remote PowerShell access in Exchange Online.
TCP port 80 traffic needs to be open between your local computer and Exchange Online. It's probably open, but it’s something to consider if your organization has a restrictive Internet access policy.
Best way to learn PowerShell is to track the PS cmdlets used while doing it in EAC. Check out this wiki which should be applicable for O365 as well
Exchange Admin Center Cmdlet Logging In Exchange Server 2013 SP1
References:
Hybrid Mailbox moves and EMC changes
Error in Moving Mailboxes to O365
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Help desk cannot assign retention policies to new mailboxes

I am running Exchange 2010 SP1. I would like to give my help desk the ability to create new mailboxes. When a new mailbox is created, we select the option to assign a Retention policy to it. I added the help desk members to the "Recipient
Management" group. They can now create new mailboxes but they get an access denied error when they select a retention policy to be assigned to it. As a member of the "Organization Management" group, I am able to assign retention policies to new
mailboxes.
With the RBAC editor, I created a custom management role group called "Mailbox Management" based on the "Recipient Management" group and added the "Retention Management" role to the group. I believe this will give them the permissions to apply retention
policies to new mailboxes but it also gives them the permissions to create/modify/delete retention policies themselves. I only want to give them the rights to add mailboxes to retention policies.
I assume I need to create a custom management role and assign this new role to my new management role group but can someone tell me the minimum role entries I need for my help desk to be able to assign rentention policies during the mailbox creation
wizard process?
Steve

Hi Steve,
Due to you post the issue in a wrong type, and we changed the type to give you a suggestion.
Please refer to below information:
http://technet.microsoft.com/en-us/library/dd638205.aspx
The permissions required to configure messaging policy and compliance vary depending on the procedure being performed or the cmdlet you want to run. For more information about messaging policy and compliance, see
Messaging Policy and Compliance, refer to above article you could find out what permissions you need to perform the procedure or run the cmdlet, then you coudl create a roleassignment
for the customized role group.
Regards!
Gavin
TechNet Community Support

Error when Creating new Mailbox - PowerShell - Storage Error

Hi Guys,
I have been working on a new exchange install and when I try to create a new mailbox or new mailboxdatabase I keep getting the following error.
WARNING: The cmdlet extension agent with the index 0 has thrown an exception in OnComplete(). The exception is:
System.TypeInitializationException: The type initializer for
'Microsoft.Exchange.Data.Storage.NativeStorePropertyDefinitionDictionary' threw an exception. --->
System.NotSupportedException: Not supported field(MailEnabled)
type(Microsoft.Exchange.Data.Storage.PropertyTagPropertyDefinition).
   at
Microsoft.Exchange.Data.Storage.NativeStorePropertyDefinitionDictionary.PropertyDefinitionSets.BuildWellKnownSets()
   at Microsoft.Exchange.Data.Storage.NativeStorePropertyDefinitionDictionary..cctor()
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Storage.PropertyTagPropertyDefinition.TryFindEquivalentDefinition(PropTagKey key, Boolean
isCustom, PropType type, TypeCheckingFlag typeCheckingFlag, PropertyTagPropertyDefinition& definition, Boolean&
createNewDefinition)
   at Microsoft.Exchange.Data.Storage.PropertyTagPropertyDefinition.InternalCreate(String displayName, PropTag
propertyTag, PropertyFlags flags, TypeCheckingFlag typeCheckingFlag, Boolean isCustom, PropertyDefinitionConstraint[]
constraints)
   at Microsoft.Exchange.Data.Storage.PropertyTagCache.InternalPropertyDefinitionsFromPropTags(TypeCheckingFlag
propertyTypeCheckingFlag, MapiProp mapiProp, StoreSession storeSession, PropTag[] propTags, Int32&
resolvedPropertyCount)
   at Microsoft.Exchange.Data.Storage.RecipientTable.GetRecipientPropertyDefinitionsFromMapiTable(Boolean&
originalColumnsChanged)
   at Microsoft.Exchange.Data.Storage.RecipientTable.BuildRecipientCollection(Action`2 recipientCollectionBuilder)
   at Microsoft.Exchange.Data.Storage.CoreRecipientCollection..ctor(ICoreItem coreItem)
   at Microsoft.Exchange.Data.Storage.CoreItem.Microsoft.Exchange.Data.Storage.ICoreItem.GetRecipientCollection(Boolean
forceOpen)
   at Microsoft.Exchange.Data.Storage.CoreItem.GetRecipientCharsetDetectionData(StringBuilder stringBuilder, Boolean
isComplete)
   at Microsoft.Exchange.Data.Storage.ItemCharsetDetector.BuildCodePageDetector(MemoryStream& cachedHtmlBody)
   at Microsoft.Exchange.Data.Storage.ItemCharsetDetector.DetectCpidWithOptions(Charset userCharset, MemoryStream&
cachedHtmlBody)
   at Microsoft.Exchange.Data.Storage.ItemCharsetDetector.SetCachedBodyDataAndDetectCharset(Char[] cachedBodyData,
Charset userCharset, BodyCharsetFlags charsetFlags)
   at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.CalculateCharset()
   at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.OnBufferFull()
   at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.CloseDetectorConversionStream()
   at Microsoft.Exchange.Data.Storage.BodyCharsetDetectionStream.Flush()
   at Microsoft.Exchange.Data.TextConverters.ConverterEncodingOutput.Flush()
   at Microsoft.Exchange.Data.TextConverters.Internal.Text.TextCodePageConverter.Run()
   at Microsoft.Exchange.Data.TextConverters.Internal.Text.TextCodePageConverter.Flush()
   at Microsoft.Exchange.Data.TextConverters.ConverterWriter.Flush()
   at Microsoft.Exchange.Data.TextConverters.ConverterWriter.Dispose(Boolean disposing)
   at System.IO.TextWriter.Close()
   at Microsoft.Exchange.Data.Storage.BodyTextWriter.<CloseWriter>b__11()
   at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer, String methodName, LocalizedString
exceptionString, CtsCall ctsCall)
   at Microsoft.Exchange.Data.Storage.BodyTextWriter.CloseWriter()
   at Microsoft.Exchange.Data.Storage.BodyTextWriter.Dispose(Boolean disposing)
   at System.IO.TextWriter.Dispose()
   at Microsoft.Exchange.ProvisioningAgent.MailboxLoggerFactory.XsoMailer.Log(AdminLogMessageData data,
LogMessageDelegate logMessage)
   at Microsoft.Exchange.ProvisioningAgent.AdminLogProvisioningHandler.OnComplete(Boolean succeeded, Exception e)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.OnComplete(Task task, Boolean succeeded, Exception exception)
Does anyone have any idea what is causing this, the server is running Microsoft Exchange 2010 SP2. I don't want to complete an upgrade to SP3 until I have got this issue resolved first.
Any suggestion are welcome.
Kind Regards
TPark IT Technician

In terms of what's causing it, the clue is in the stack above.
its one of the cmdlet extension agents. Which one? Well the one at index 0
Run this, and you should find its the Mailbox Creation Time Agent
Get-CmdletExtensionAgent | select Name, priority
Get-CmdletExtensionAgent | select Name, priority
I'd then run Test-Servicehealth to check services are all responding.
Can you post the exact command you are running to get this?
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

MacMail question--how to get "mailbox" changed from "on my mac" back to server?

I'm still learning Mac..... (and don't know if I'm even posting in correct forum).
Got iMac last year. I use aol email address and I keep all personal and important emails so my inbox is rather large, but when I got a new Macbook Air, I decided to clean up my mailbox a bit and learned about mailboxes and smart boxes, etc., and so I set up a few mailboxes on my MBA without realizing that it would affect mail on my desktop! Dumb, I know. I just didn't realize it meant on that particular mac. Duh.
Anyway, can I undo my mailbox creation and put everything back into the inbox on server for now?
Many thanks for your help.
Tab

How do I move the mail back to the server? I guess I'm not googling the right terms because I can't find any instructions. I created a test mailbox to try and move it back to the "inbox" and nothing happened (drag and drop). I'm new to Mac and "just get by" in my knowledge of using it.
Thank you.

Mailbox Creation

Similar Messages

Maybe you are looking for