Creating public folders Exchange 2013 powershell

Hello, we have exchange server 2013 with a lot of public folders 
We use script to create this folders and to manage them.
With upgrade to 2013 command New-PublicFolder was changed.
parameter -server was deleted, and now we gaining error: 
 Creating Public Folder
New-PublicFolder : Cannot find information about the local server XXX.XXXXXX.com in Active Directory. This may be related to a change in the server name.
+ New-PublicFolder -DomainController $dcserver -Name $grpn -Path '\Projects'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-PublicFolder], LocalServerNotFoundException
  + FullyQualifiedErrorId : [Server=XXXXX,RequestId=XXXXXXXXXXXXXXX,TimeStamp=19.04.2014 3:55:21] 465E6BC6,Microsoft.Exchange.Managemen 
t.MapiTasks.NewPublicFolder
Now i found a solution but is it normal to use something like this :
$exsession = New-PSSession -ConfigurationName Microsoft.Exchange –ConnectionUri "http://$mailserver/PowerShell/" -Authentication Kerberos
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) New-PublicFolder -DomainController $dcserver -Name $grpn -Path '\Projects'} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Enable-MailPublicFolder -DomainController $dcserver -Identity $pffn} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Add-PublicFolderClientPermission -DomainController $dcserver -User $grpnpg -AccessRights 'Author' -Identity $pffn} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) remove-PublicFolderClientPermission -DomainController $dcserver -User "Default" -Identity $pffn -confirm:$false} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Add-PublicFolderClientPermission -DomainController $dcserver -User "Default" -AccessRights 'CreateItems' -Identity $pffn} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Add-PublicFolderClientPermission -DomainController $dcserver -User "Anonymous" -AccessRights 'CreateItems' -Identity $pffn} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Set-MailPublicFolder -DomainController $dcserver -Identity $pffn -HiddenFromAddressListsEnabled $true} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Add-DistributionGroupMember -DomainController $dcserver -Identity $grpnpg -Member $pfpn} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
#Closing remote session
Remove-PSSession $exsession
is there any other solutions to do this operations?

Hello, we have exchange server 2013 with a lot of public folders 
We use script to create this folders and to manage them.
With upgrade to 2013 command New-PublicFolder was changed.
parameter -server was deleted, and now we gaining error: 
 Creating Public Folder
New-PublicFolder : Cannot find information about the local server XXX.XXXXXX.com in Active Directory. This may be related to a change in the server name.
+ New-PublicFolder -DomainController $dcserver -Name $grpn -Path '\Projects'
You can specify the parameter mailbox but that is optional.
Example:
New-PublicFolder -Name SomeName -Path \Projects -mailbox "PF Mailbox"
...and you have more examples in the Technet Article New-PublicFolder
Martina Miskovic

Similar Messages

  • Cross-forest access to public folders Exchange 2013-2007

    Dear.
    We have an Exchange 2007 org in one forest and an Exchange 2013 org in another forest.
    User accounts remain in the 2007 AD, mailbox moved to Exchange 2013 in the other forest, so a linked mailbox.
    What do I need to do in the Exchange 2007 public folders to give the migrated mailboxes (not migrated users) access to these public folders?
    Thanks for the support.
    Regards.
    Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

    Hi Stephen,<o:p></o:p>
    <o:p> </o:p>
    Do you have trust between Exchange 2007 forest and Exchange 2013 forest? Please set up a trust between the two forests. Then set the public folder client  permission
    to see if we can access the
    public folders.<o:p></o:p>
    <o:p> </o:p>
    If not, since Public folder cross forest migration is not supported in from an Exchange 2007/2010 forest to an exchange 2013 forest, refer to forum:
    http://social.technet.microsoft.com/Forums/office/en-US/51da1b97-fbb1-4f81-87da-c3370960c4ab/crossforest-public-folder-migration?forum=exchangesvrdeploy
    http://social.technet.microsoft.com/Forums/office/en-US/663f0dc3-a977-408a-93c7-94584fbefc62/public-folder-issue-cross-forest-migration-exchange-2010-to-2013?forum=exchangesvrdeploy
    <o:p></o:p>
    Title: Migrate Public Folders to Exchange 2013 From Previous Versions<o:p></o:p>
    Link:
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx<o:p></o:p>
    <o:p> </o:p>
    So for public folder migration,
    the only supported path is cross forest 2007/2010 to 2007/2010 and then inter forest 2007/010 to 2013. Or
    we can first export all the public folder to PST from the Exchange 2007 forest, then import the PST to the Exchange 2013 forest.
    <o:p></o:p>
    Regards, Eric Zou

  • Creating a New Email address policy for users in another Domain with Exchange 2013 powershell?

    Hi
    Everyone
    Is it possible to create a new-emailaddress policy with Exchange
    2013 Powershell, for users within OU´s located on another different
    domain/forest than where Exchange 2013 is installed?
    There
    is a Transitive, two way trust between the domain/forest where the users are
    located - and the Exchange 2013, multi tenant domain.
    Further
    more, and if possible, I need to create linked mailboxes to all these users as
    well.
    Í have been struckling with this issue for weeks, so please anyone -
    advice - and comment.
    Best
    Regards
    Peter
    A-ONE Solutions

    Hi Siddharth
    I want to create a new e-mailaaddress policy - and after that create linked mailboxes/users in my account domain with powershell.
    Can you help me achieve that ?
    I have a powershell CMDlet, but i doesn´t work. (Cannot fint user OU in my account domain)
    CMDlet is as follows:
    New-EmailAddressPolicy -Name $CustomerName   -RecipientContainer "OU=$CustomerName, OU=kunder, DC=Domain, DC=local" -IncludedRecipients 'AllRecipients' -ConditionalCustomAttribute1 $CustomerName -Priority '1' -EnabledEmailAddressTemplates SMTP:%2g%1s@$AcceptedEmailDomain
    Where $Customername = test.dk
    and Account domain is = OU=kunder, DC=Domain, DC=local
    But the command fails with:
    New-EmailAddressPolicy : Couldn't find organizational unit "OU=Test.dk, OU=kunder, DC=Domain, DC=local". Make sure you have typed the name correctly.
    At line:52 char:1
    + New-EmailAddressPolicy -Name $CustomerName   -RecipientContainer "OU=$CustomerNa
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [New-EmailAddressPolicy], ManagementObjectNotFoundException
        + FullyQualifiedErrorId : [Server=HE-MBX03,RequestId=2cbe1b51-4af2-4c04-9f7e-e440000975e6,TimeStamp=24-03-2014 12:58:19] 2D00FD2A,Mi 
       crosoft.Exchange.Management.SystemConfigurationTasks.NewEmailAddressPolicy
    So, I cannot find the OU on the Account forest/Domain, even though the OU do exists in the Account domain. 
    Verifying with this: 
    Get-ADOrganizationalUnit -Identity "OU=$CustomerName,OU=kunder,DC=Domain,DC=local" –Server ‘DC01.domain.local’| FL
    This works fine, Can you please help/assist?
    Peter

  • Exchange 2013 - powershell - create search folder for items larger than 24mb

    Hi all,
    is it possible to use PowerShell and create search folder in spesific mailbox that contains items larger than 25mb?
    Thanks!
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Ok this should be possible.
    I just tested a basic idea of what you want to do on Exchange 2010 SP3. IF you need me to test on 2013 let me know.
    Add the account you want to run the powershell search as to the "Discovery Management" role in AS or ECP.
    This gives you access to the "search-mailbox" command. Using this you should be able to build a search that moves mail to a different folder.
    http://technet.microsoft.com/en-gb/library/dd298173(v=exchg.150).aspx
    Thanks,
    Edit: something like this would help but the target mailbox would be there own I guess
    Search-Mailbox -SearchQuery “Size:>25MB” -TargetMailbox SomeMailbox -TargetFolder Export -LogOnly -LogLevel Full
    Ok so I have found a issue where the command does not allow the source mailbox to be the same as a target mailbox. I dont know if this will help you then unless you go through a long process of moving the mail out then back but thats very long.
    You could create a rule for this but it would have to be run manually with specific settings so I guess that might not work as user training can be difficult. 
    You could write a VBA macro for this and then apply it to all you machines.
    Or there is a 3rd party tool that could help you called
    Auto-Mate
    Sorry I could not be more helpful.
    Good luck

  • Problems with cmdlets within the Exchange 2013 powershell

    Hi,
    i've following problem: I can't access all possible powershell cmdlets within the exchange powershell. For example following cmdlet is missing: "Get-Queue". Also we have trouble with some other cmdlets: Get-Mailbox only lists one of 30 mailboxes
    and if we want to modify a mailbox identified by the logonname an error shows up that the user can't be found. Only the one listed user can be modified.
    What can I do to solve this problem?
    Yours
    Achim

    Hi Achim,
    You need to be assigned appropriate permissions or roles before you can run all cmdlet. Although all parameters for this cmdlet are listed, you may not have access to some parameters if they're not included in the permissions assigned to you. For example
    to run Get-Queue cmdlet - your user account must be assigned the "Organization Management" or at least "Server Management" role.
    You can try this to view roles assigned to your account:
    Get-ManagementRoleAssignment -RoleAssignee 'yourUserAcc' -Role "organization*" | fl role
    Get-ManagementRoleAssignment -RoleAssignee 'yourUserAcc' -Role "*transport*" | fl role
    Otherwise you can view and change role assignments with EAC:
    In the EAC, navigate to Permissions > Admin Roles.
    Select the role group you want to view the members of.
    In the role group details pane, view the members in the role group details pane.
    ▲ Vote if Helpful / Mark if Answer
    MCSE: Messaging 2013 Charter / Private Cloud / Server Infrastructure
    MaximumExchange.ru

  • Unable to move mailbox to newly created database in exchange 2013

    Hi, i created a new database in our existing exchange server 2013 sp1 and i was trying to move my mailbox to the newly created one using the EAC. But the mailbox is not getting moved and i am not receiving any errors. Is there anything else i need to do
    after creating the database.
    Please advise.

    Hello
    lets play again:
    new-moverequest -identity useremailaddress -targetdatabase new database
    after two minute get move req log
    get-moverequest -identity useremailaddress |get-moverequeststatistics -includereport |fl
    or if have got more DC specified one Dc with -domincontroller DCname
    sorry my english

  • Cannot access Exchange 2013 powershell after cu6 update

    Hi All,
    Getting this error message when I try to access powershell.
    The WinRM client cannot process the request. It cannot determine the content type of the http response"
    Any ideas?

    thanks but i notice that the update stopped at the mailbox role: transport service.
    will the same solution above work?
    Error:
    The following error was generated when "$error.Clear();
     $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
     foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
     " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ConnectorMappingConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with
    the settings on Receive connector "EX2013\Incoming from Internet - Dummy". A Receive connector must have a unique combination of a local IP address & port bindings and remote IP address ranges. Change at least one of
    these values.
     at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
     at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
     at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
     at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
     at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Error:
    The following error was generated when "$error.Clear();
     $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
     foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
     " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ConnectorMappingConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with
    the settings on Receive connector "EX2013\Default
    Frontend EX2013". A Receive connector must have a unique combination of a local IP address & port bindings and remote IP address ranges. Change at least one of these values.
     at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
     at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
     at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
     at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
     at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

  • Public folders from exchange 2007 to exchange 2013

    HI I am new to exchange, i am planning to do the migration of Exchange 2007SP3 UR10 to Exchange 2013 CU7, I want to move public folders from exchange 2007 to exchange 2013. wht is the procedure to move and wht are the commands to know how many public folders
    i have.I just want to be aware before the installation so that later i can avoid issues.please do guide me

    Hi Quiett,
    please find  how to move public folders on ttp://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part1.html 
    You can replace your servers names and follow exactly the proedure that is shown there. I strongly suggest to read also the 2nd page (replication) before you start. Please be aware of
    Set-OrganizationConfig –PublicFoldersLockedForMigration $True , so you cannot change the source side whle migrating.
    Regards,
    Martin

  • Exchange 2007 SP3 RU compatibility with Exchange 2013 lattest CU

    Hi Team,
    I have question, I want to migrate my exchange 2007 to 2013.
    right now exchange 2013 already provide CU7. 
    My question is, is exchange 2013 CU7 compatible with Exchange 2007 SP3 lattest RU (SP3 RU15) ?
    is there any limitation of version if i want to upgrade Exchange 2007 to 2013
    Thanks Before

    Hello,
    The first thing I would say, is that the MINIMUM supported update for Exchange 2007 is SP3 RU 10, so you should be ok with RU15 installed with Exchange 2013 Cu7.
    https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
    The second thing I would say, and I am not sure how you're current environment is configured and how you plan on configuring your future environment, but if you are using Public Folders, Exchange 2013 CU7 changes the way public folders are handled during
    coexistence.  I would recommend taking a look at this blog post from The Exchange Team
    https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx 
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • What I should look out for, Exchange 2013

    I have a Exchange 2010 server on Server 2008R2. I just installed Exchange 2013 on Server 2012R2. Anyone know what changes i need to make to begin moving users over to the new server? Shouldn't it have pulled all the settings over from the other exchange
    server?

    Hi,
    To migrate from Exchange 2010 to Exchange 2013, you can refer to the articles provided by Amit Tank.
    For one thing about public folders, Exchange 2013 users can access public folders on Exchange 2010, but Exchange 2010 users can't access public folders on Exchange 2013. If you still use public folders, you need to migrate mailboxes before moving public
    folders to Exchange 2013.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 Public Folders Cannot Change Permissions Errors from Management Console and Powershell

    This problem does not affect new public folders, only old ones that have probably been on Exchange 2000/2003 servers in the past. Migrations I believe did go smoothly but now have errors.
    Error Reported is:
    Microsoft Exchange Error
    The following error(s) occurred while saving changes:
    Add-PublicFolderClientPermission
    Failed
    Error:
    Failed to modify the MAPI.NET table property of the object "000000001A447390AA6611CD9BC800AA002FC45A030064004E9CC2F8DD46B5E1E4578DE6D8030000000278E90000" on server "FQDN.Server.Name". See inner exception for more information.
    MapiExceptionNonCanonicalACL: Unable to modify table. (hr=0x80004005, ec=2409)
    Diagnostic context:
        Lid: 40487   EMSMDBMT.EcDoRpcExt2 called [length=218]
        Lid: 56871   EMSMDBMT.EcDoRpcExt2 returned [ec=0x0][length=356][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropModifyACL [64]
        Lid: 17082   ROP Error: 0x969    
        Lid: 27745 
        Lid: 21921   StoreEc: 0x969    
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropModifyACL [64]
        Lid: 22086 
        Lid: 27128 
        Lid: 27232   StoreEc: 0x8004010F
        Lid: 27128 
        Lid: 27232   StoreEc: 0x8004010F
        Lid: 22086 
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x3D210102
        Lid: 19149   Error: 0x0
        Lid: 24509   Error: 0x0
        Lid: 31229   Error: 0x0
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 6671    StoreEc: 0x8004010F
        Lid: 24976 
        Lid: 24952 
        Lid: 25472 
        Lid: 7972    StoreEc: 0x969    
        Lid: 26532 
        Lid: 4920    StoreEc: 0x969    
        Lid: 5119    StoreEc: 0x969    
        Lid: 5247    StoreEc: 0x969    
        Lid: 17916   StoreEc: 0x969    
        Lid: 4814    StoreEc: 0x969    
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849 
        Lid: 21817   ROP Failure: 0x969    
        Lid: 29150 
        Lid: 20446   StoreEc: 0x969    
    OK
    From ExFolders we get error "Exception: Object Reference not set to an instance of an object"
    Any thought on how to fix permissions, people who already had permission in the past can see and access them OK and all objects, but we cannot change/update or remove permissons
    We alos receive similar error from the powershell.

    Hi,
    Could
    you please  add a new public folder hierarchies with ADSIEdit as following setups.
    For how to use ADSIEdit ,you can access:
    http://technet.microsoft.com/en-us/library/cc773354(WS.10).aspx
    1.Run ADSIEdit, right click Exchange Administrative Group under “Configuration \ services \ Microsoft
    Exchange \ Organization name \ Administrative groups”.
    2.Select New Object.
    3.Select msExchPublicFolderTreeContainer for the class and click Next.
    4.Enter the following for the value:
    Folder Hierarchies, click Next.
    5.Click Finish.
    6.Create
    Public Folder Tree Object.
    7.Right click CN=Folder Hierarchies -> New Object.
    8.Selected msExchPFTree for the class.
    9.For the value we entered, "Public Folders" and clicked next.
    10.Clicked on the "More Attributes" button, selected msExchPFTreeType .
    11.Set the value
    to 1.
     Note: This is very important that this value is set
    to a value of 1 as This tells Exchange that this is a MAPI Tree.
    12.Click Ok and then finish.
    13.We then went
    to the properties of the newly created "Public Folders" Tree object in
    ADSIEdit.
    14.Copy the distinguished name value
    to the clipboard and then click cancel.
    15.Navigate
    to the Storage group that contains the Public
    Folder Store for this server and get properties of the server.
    16.Locate the msExchOwningPFTree attribute and paste in the value that was copied
    from the Public folders Distinguish name attribute.
    17.Restart the Information Store Service.
    18.Mounted and dismount the PF store.
    19.Open Outlook with administrator,give full permission to default owner.
    Hope it can help you!

  • Exchange 2013 / 2010 / 2007 - Public Folders

    I have read that legacy public folders and 2013 public folders canot co-exist.
    If I have legacy public folders A, B and C, does this mean...
     that if I migrate folder A to 2013, i cannot maintain a replica on legacy systems, but folders B and C are still accessible
    ..or..
     If I migrate folder A to 2013, I must migrate folders B and C also.
    If I am need to import folder D, from an external Exchange 2013 installation, into my legacy public folder system, is it possible to migrate folder D out of the external 2130 environment into my legacy public folder environment? If so, is there any extra functionality
    2013 PF has that the users will lose if the folders are down graded to legacy?
    Thanks!
    Tom

    Hi,
    User mailboxes on Exchange 2013 servers can connect to legacy public folders, but legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 server.
    Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously.
    Before you migrate public folders, you need to migrate mailboxes to Exchange 2013 first.
    Please refer to the following article.
    http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx
    Besides, here is a related thread for your reference.
    http://social.technet.microsoft.com/Forums/office/en-US/7603f02e-beb4-4c3d-8cb9-613ad806766b/public-folder-migration-from-multiple-exchange-2007-to-exchange-2013?forum=exchangesvrsharingcollab
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 Public Folder Migration Problem

    Hi All,
    Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.
    I have followed the guide for public folder migration here
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.
    We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.
    However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders.  Administrators can create them
    fine from the ECP - just not from outlook.
    It also appears some users cannot see some folders that they have permissions to.
    Can anyone assist with some ideas to resolve ?
    Thanks.

    Question?
    Are you able to create the Folder in OWA?
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:
       LinkedIn:
    Check out CodeTwo’s tools for Exchange admins   
    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.
    it is not functionally possible to create Public Folders in OWA user interface in Exchange 2013!.... From admin ECP it works fine!
    My Bad, that's what I was trying to say.
    Testing the same thing in the LAB, should have some update tomorrow morning.
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:   
    LinkedIn:   
    Check out CodeTwo’s tools for Exchange admins   
    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.

  • Problems moving public folders for 2k3 to 2k7 migration

    Hello,
    i'm having problems with moving the public folder from the 2k3 to 2k7, following the steps i've found on mig docs and googling for this issue and i cant seem to solve it, letme detail:
    There are only 3 user created public folders, all with contacts, they weight less than a MB combined.
    So first thing, iin E2k3 ESM i right click the public folder store and select "move all replicas", it works succesfully.
    if i expand the pf store and check replicas i see a ton of system folders with 2 replicas.
    i also check every user folder, change the replication to always and urgent and resend changes/synch content from 2k3 to 2k7
    Now according to migration documents the "pf instances" should empty by itself after some time....
    well it's been a day and in fact i see more items than before on the 2k3, if i expand the instances on the 2k7 i see 4/5 folders, none of the user ones!.
    I also ran the moveallreplicas.ps1 script.
    if i run Get-publicfolder -recurse |fl name,replicas i only get:
    Name     : IPM_SUBTREE
    Replicas : {}the next step is apparantely to move the public folder "folder" itself from the 2k3 admin group to the 2k7, i can do that and it gives no error but i'm worried that if i decommision the 2k3 that it will all fail horribly.
    ¿whats going on, how can i move this thing for once?

    Hi,
    Make sure you have added the Exchange 2007 in the Replication tab list of all folders in Exchange Server 2003.
    In Exchange 2003, please increase the logging level to Maximum on the diagnostic logging categories: Replication Incoming Messages and Replication Outgoing Messages.
    Here is a related article which can help you for your reference.
    How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003
    http://support.microsoft.com/kb/842273/en-us
    Another useful article:
    Some Public Folder content is not replicating from Exchange 2003 to Exchange 2007
    http://blogs.technet.com/b/dblanch/archive/2009/04/10/some-public-folder-content-is-not-replicating-from-exchange-2003-to-exchange-2007.aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2003 will migrate to Exchange 2010 or Exchange 2013

    Hi,
    Exchange server is on exchange 2003 on windows 2003 R2. 
         I had an architecture of parent & child domain controllers, Where parent company is closed Down. But we have an additional Domain Controller
    of parent DC in our premise.
    Due to this fact exchange organization is also unavailable & cannot make modification on my exchange server configurations (Global Settings, such as changing recipients attachment restrictions, everything is grayed out).
    Is there any way where we can have staged migration. I mean can I keep old & new server running together & keep few users on new Exchange organization & rest of them be on an existing server itself. (I tried testing this too, but email delivers
    to mailbox store, so, it checks a name & say “Mailbox not available”)
    If I create a new domain environment, I have challenge of migrating users (This I can achieve with ADMT, but actual story starts with mailbox migration)
    Real pain is, I have more than 500 users, can I achieve direct migration over a weekend. (few are POP & OWA users, around 50)
    Can anyone help in this please.
    Imran

    So, you have exchange 2003 which is inaccessible! Database files .EDB and .STM is there, but Mailboxes are not available.
    And you are planning to create new environment (As you don't have any other option).
    This is a cross forest migration. Which exchange you are planning to install in new environment? I would suggest 2013.
    The only available option you have (As current environment is Inaccessible), Export the PST from EDB files.
    Create Mailbox on Exchange 2013 and Import the PST.
    Do you have Public Folder Database?
    If yes, apply the same process on it.
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    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.

Maybe you are looking for