Preparing Domain for Exchange 2013 in an Exchange 2010 Organization

When preparing the domain for Exchange 2013, can we use the same Organizational Name as was used for Exchange 2010 or should we select a new variation?

When preparing the domain for Exchange 2013, can we use the same Organizational Name as was used for Exchange 2010 or should we select a new variation?
You dont have define the org name since it already exists. 
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

  • Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8

    I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
    I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error.  Is this even possible?  I cannot find any documentation on this scenario yet.
    VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
    version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
    VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
    The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
        + FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

    Hi Steve,
    I'm a little confused what you are saying. Here is my understanding:
    When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
    If I have misunderstood your concern, please let me know.
    For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
    2007.
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

    Hi Team,
    I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
    Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
    open and throws an error of some "cannot open set of folders".
    Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
    Kindly share some KB or tip. Any help is appreciated. Thank You.
    Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

    I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
    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.

  • Some help with migrating exchange 2010 to exchange 2013 + installing another exchange 2010 to be edge-forefront-proxy server

    Hi guys (and girls)!
    Hear me up. The idea is like this:
    A friend of mine has currently Exchange 2010 SP3 in his environment with Forefront Protection installed on it. As we all know Forefront Protection is discontinued in Exchange 2013 environment because Exchange 2013 on-premisses is using integrated tool for
    doing that, but a friend of mine would really like to stick with Forefront Protection because it is "much better tool" then integrated stuff in 2013.
    Ok, so here's the idea. Exchange 2010 SP3 with Forefront is installed on Phisical machine (so, not virtualized) on 2008 r2 std OS. We decided to move to Exchange 2013 because we wanted to achieve DAG on Exchange 2010 but we realized that is not possible
    because 2008 R2 STD OS does not support failover-clustering functionality, but you are able to achieve that on newer OS for example 2012? Ok, so we bought another server, where we are planing to install Vmware Esxi and put two virtual machines on it.
    One Will be 2012 r2 STD OS with Exchange 2013 on it, the other Will be 2008 r2 STD with Exchange 2010 Edge role + Forefront on it. We are planing to move Exchange 2010 production server to virtual machine Exchange 2013, and newly virtual machine
    with Exchange 2010 edge server will only be "a kind of Proxy server with Forefront functionality". What concers me?
    Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
    One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
    Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
    bostjanc

    Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
    already answered by PS CL above
    One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
    No it does not as long you don't make any changes on send/receive connector and do the EdgeSubscription. As soon as you do the Edge subscription there will be send/receive connector created, so pay attention how to setup the Edge Server.
    Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
    Just install the Edge Transport Server and make sure you install ADLDS services.
    as you have mentioned you are doing to install both Mailbox and Edge server on the same VMware - it is a single point of failure.
    Where Technology Meets Talent

  • Exchange 2013 in coexistence with 2010, Outlook keep looking for Exchange 2010 server slow connection

    All,
    not sure if this topic has already answered, but can't find anything around.
    Here's the scenario. Migrating from a single Exchange 2010 to a cluster of 2 + 1 Exchange 2013. Two in a site, One in the other site (DC).
    I have migrated successfully a firsat batch of users. Mail flow works perfectly. The only thing is that often the migrated users are experiencing a long time (about 30 minutes) to get their Outlook syncronized. Both OL 2010 and 2013 doesn't make any difference.
    They're using OL Anywhere, and I've already tried to rebuild the profile.
    From a check on the OL connection status, looks like they're still looking for something on EX2010, but no idea what could be. If I disable the cache mode it works smooth and quick.
    My best guess is that is something in cache they're trying to keep updated... but still this doesn't explain the huge delay.
    Any help would be highly appreciated!
    Thanks!

    Hi Alessandro,
    What happens in OWA? I guess it should be good.
    Did you have public folders with Exchange 2010? Were they moved over to Exch 2013? Technically you should move the PF to the latest version from the legacy version before moving over the users?
    - Moved the PF to OL2013. same behaviour
    May be the outlook clients are looking for th OAB? Did you move the OAB to Exchange 2013?
    - Did this too.
    Try running outlook on safe mode and see what happens? may be one of the outlook add-in's are looking for something on Exchange 2010?
    - Will try that....
    Can you do a Test Email Auto Configuration in outlook (Hold CNTRL key and right click on outlook icon on status bar) and see if the exchange url's are pointed to Exch 2013?
    - Will try that....
    Is this happening to all migrated users or specific? Are they BlackBerry users?
    - All users and there are no BB users
    Do you have any archived emails on those migrated users? May be outlook is looking for some archived stuff on the Exch 2010 side?
    - I instructed Exchange to migrate also the archiving database, however There are no archived mailbox on 2010
    Could this be because of any calendar entries? May be migrated user mailboxes are having issues with working with non-migrated mailbox calendars?
    - This maybe a possibility. I have only 10 users actively using Exchange, while all others have the mailboxes only because they've Lync. I've completed all migrations today, so there shouldn't be anything left on 2010
    Let me know how it went - all the best!
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. Regards, Siva

  • Does Edge transport server for Exchange 2013 work with Exchange 2010?

    Hello everyone,
    I want to install Edge transport server for my Exchange servers,
    Could you tell me if Edge transport server 2013 works with Exchange 2010?
    Thank you in advance

    Hello
    tip:
    https://technet.microsoft.com/en-us/library/jj898583%28v=exchg.150%29.aspx
    2   If you want to create an EdgeSync
    Subscription between an Exchange 2010 Hub Transport server and an
    Exchange 2013 SP1 Edge Transport server, you need to install Exchange
    2010 SP3 Update Rollup 5 or later on the Exchange 2010 Hub Transport
    server.
    sorry my english

  • Exchange 2013 - The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold

    Noticed at about noon that no emails had been received all day. Began to investigate and found that the MS Exchange Transport service had been set to deny email submission because it was using too much memory on the server (91%). 
    The error message makes me think that we may have been getting used by malware or something similar.“The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the
    configured threshold.” 
    There are also several warning messages that list particular IP addresses and say that a connection from that IP was denied because there were already the maximum number of connections (20). 
    From what I can tell, all of the IP addresses are from Taiwan. 
    The time period for which some emails may be missing is from close of business yesterday ( 4/3/2014) through about 12:45 today (4/4/2014). 
    From the time I spent reading and trying to figure out the error, I think we may need to readjust our throttling policies to prevent this from happening. 
    The exchange server is currently running at 90%+ CPU and 50%+ memory usage the majority of the time, and I’m not sure how to fix it.
    Also, I cannot get into EMS I get a access denied message from the destination computer. (Exchange server) I want to get into there to change the throttling policy back to default, since we disabled it.
    The Error reads:
    The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer <Exchange> returned an 'access denied' error. Change the configuration to allow Kerberos authentication
    mechanism to be used or specify one of the authentication mechanism supported by the server. (How do I do this?) To use Kerberos, specify the local computer name as the remote destination. (I'm trying to use EMS while logged into the local Exchange server)
    Also verify that the client computer and the destination computer are joined to a domain. (Exchange is on our domain, and the computer trying to connect is the same computer) To use basic, specify the local computer name as the remote destination, specify
    Basic authentication and provide user mane and password. Possible authentication mechanisms reported by server.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
    I assumed control of this exchange system already in place and I do not have much experience with exchange 2013 or server 2012. I do know 2008, but that doesn't help very much in this situation.
    Recent changes to the system:
    About three days ago we switch our sessions policy to allow many more connections, and I believe this caused the issue. This is what I changed it to:
    Made the registry DWORD (32-bit) "Maximum Allowed Sessions Per User" and modified the value to 1000. Location of registry change @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
    I just changed it to 10 from the 1000. I'm hoping this solves this. So far no.
    Also, I am not the best in the shell or command line interfaces. Any help would be wonderful!

    Hi,
    Yes, could be hardware performance issue. Try recycle the Transport process and see if the issue persists.
    Thanks,
    Simon Wu
    TechNet Community Support

  • How do i connect manually to Exchange 2013 from Outlook 2007/2010 in another forest?

    Hello All,
    I have a source organization: Windows 2003 domain + Exchange 2010 SP3 + smtp domain acme.com
    Target organization: Winows 2012 R2 domain + Exchange 2013 CU3 + smtp domain  acme.com
    We are migrating to target organization.
    I want to connect Outlook 2007/2010 to their target mailbox (Exchange 2013) from a machine which is joined to Source DOmain.
    I couldn't use autodiscover, because as the machine is joined to source domain, autodiscover it's mapping to Exchange 2010.
    It only works when I machine is joined to target domain.
    Any idea how to connect manually to eXCHANGE 2013 mailbox from a machine which is joined to source domain?
    Regards
    José Osorio

    Hi,
    Firstly, I’d like to explain, Autodiscover service can be used cross forest:
    1. the two forests must be trusted.
    2. configure a mail contact in the original forest.
    For more information, please refer to the partition named how to configure the Autodiscover service for cross-forest moves in the following article:
    http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx#BKMK_ConfigureForCrossForestMoves
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2013 ECP redirects to 2010 OWA still

    I have a new Exchange 2013 SP1 server on a 2012 R2 OS where I've installed both Mailbox and Client Access roles in an existing Exchange 2010 environment.  Initially ran into some DNS issues that caused errors installing the Client Access server, but
    I fixed those, removed Exchange 2013 and reinstalled with no errors.  In every scenario so far, trying to access the ECP redirects you to the 2010 OWA.  I have been scouring threads for hours and tried everything I've seen, but to no avail.  I
    have tried:
    1) Using the https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15 URL, which still
    redirects to the 2010 OWA
    2) Creating a new user account with all of the same rights as the domain admin but has no mailbox, which redirects to the 2010 OWA and throws an error that there is no mailbox.
    3) Setting the domain in IIS authentication settings for the ECP on both the 2013 and 2010 server.
    Does anyone have any ideas here on what to try next?

    Try creating a mailbox for the administrative account on the Exchange 2013 server or moving the existing mailbox.
    I've seen issues like you're experiencing in various forms before myself, though not exactly as you've reported.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2013 CAS-MBX / Exchange 2007 Edge Mail flow

    I am in the process of migrating from Exchange 2007 to Exchange 2013.  I have installed my 2013 Cas/MBX into my environment with the existing 2007 Hub/MBX and existing 2007 Edge.  Mail flow on the 2007 side is unchanged (working) but on the 2013
    side I am able to receive mail but I can't send (from test mailbox).  It just sits in the que on the 2013 CAS/MBX until it expires.
    Any ideas?  My Exchange 2007 servers are both upgraded to SP3 Rollup 13 so the versions should be fine.

    I redid my edge subscription (applying the xml on the 2013 hub).  All works the same (mail flow on the 2007 side works fine but unable to send out for mailbox's that live on the 2013 side).  One thing I noticed is that when I ran start-edgesynchronization
    I get the following:
    RunspaceId     : xxxxxx
    Result         : CouldNotConnect
    Type           : Recipients
    Name           : XXXX
    FailureDetails : The LDAP server is unavailable.
    StartUTC       : 9/15/2014 2:03:23 AM
    EndUTC         : 9/15/2014 2:03:23 AM
    Added          : 0
    Deleted        : 0
    Updated        : 0
    Scanned        : 0
    TargetScanned  : 0
    RunspaceId     : xxxxxx
    Result         : CouldNotConnect
    Type           : Configuration
    Name           : XXXX
    FailureDetails : The LDAP server is unavailable.
    StartUTC       : 9/15/2014 2:03:23 AM
    EndUTC         : 9/15/2014 2:03:23 AM
    Added          : 0
    Deleted        : 0
    Updated        : 0
    Scanned        : 0
    TargetScanned  : 0
    I am able to ping my domain controllers / edge server and I can also telnet to ports 389 & 3268.  I have restarted my Active directory topology service

  • Deploy exchange 2013 with current Exchange 2007 organization

    Dear All
        our company will update exchange 2007 to exchange 2013, on AD site we already update Forest functional level and Domain functinal level  to Windows 2003 ( can not up to windows 2008 yet because have some ad that run windows 2003 server
    ) but one thing that I'm not sure, between migration we can not full tranfer mailbox form exchange 2007 to exchange 2013 in one time, we need to migrate on night time manybe one day we can migrate only 100 user per night, my question is
    1. which exchange 2013 server role that we will install first ( mailbox or CAS)
    2. on migration time, can we let's user used exchange 2007 to main of OWA and SMTP or not? we need all user's mailbox tranfer to exchange 2013 complete first after that we will switch OWA and SMTP

    1. Mailbox, or install both on the same server at the same time.   (Edited:  First I said CAS, which used to be true, but now you need the Mailbox role to run PowerShell, so you have to install Mailbox first.  Consider a dual-role server,
    however, because there aren't a lot of cases where you need separate CAS and Mailbox role servers.)
    2. You cannot.  Exchange 2013 mailbox users must use the Exchange 2013 CAS.  You can have users use their respective CAS while migrating, but that requires two sets of URLs and is therefore more confusing for the end user.  I recommend planning
    to deploy Exchange 2013 CAS, a legacy URL for Exchange 2007, and switch your hostnames to Exchange 2013.  This is all spelled out in the Exchange 2013 documentation.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2013 SP1 and Exchange Online Protection (EOP)

    Hello, I have just set up a new install of Exchange 2013 and connected mail flow with EOP. Mail is flowing, and I can access emails through the Outlook Web App. However, I cannot get Outlook 2013 to link up to the new configuration. I got Outlook for Mac
    to work, no problem. But, I get an error on outlook 2013 that says it must sync folders for a first time to open.
    Any help would be appreciated.
    Thanks!

    Hi 
    Use another user to test, check whether he can use Outlook to access his mailbox or not?
    If this user also cannot connect to his mailbox, I suggest you go to check whether all the Exchange services are started, make sure RPC client access service is started.
    You do need to replace the self-signed certificate.
    If you don't want to buy a certificate from a Third-Party Issuer, then install Windows CA and issue a certificate from there.
    Even if it does work with the self-signed certificate using Outlook 2007, it is not a supported configuration and you will not be able to connect with Outlook 2010/2013.
    I have seen new installation of EX13 having SSLOffloading turned on causing the problems. Turn if off if you do.
    Set-OutlookAnywhere -Identity 'SERVERNAME\rpc (Default Web Site)' -SSLOffloading $false
    Let us know the output of the above so that we can proceed further.
    Remember to 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 Check out my latest blog posts on http://exchangequery.com

  • Exchange 2013 DLP with Exchange 2010 mailboxes

    Ive got an Exchange 2007/2010 environment. I've been looking at Exchange 2013 and am interested in the DLP funtionality.
    There are no plans to move mailboxes to Exchange 2013 but would it be possible to install an Exchange 2013 CAS/Mailbox server in my environment and route email through it to make use of the DLP ?
    Current environment consists of Exchange 2010 DAG, Casarray and hub transport servers, and Exchange 2007 mailbox servers, CAS and hub transports. Mail to the internet is sent to a smarthost.
    Thank you.

    Hi Maria,
    DLP Policies are actually a specific transport rule. Since the transport rules with Exchange 2010 didn’t provide such feature to monitor and check the e-mail
    content, I am afraid, in theory, it’s not possible.
    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

  • Addition of Exchange 2013 server to Exchange 2010 organization broke Exchange

    This is somewhat of an emergency, since Exchange is down completely for us right now.
    I just migrated from SBS2003 to Exchange 2010 on Windows 2012 over last weekend. Everything is now stable, and SBS2003 is shut down. Now I am attempting to migrate from Exchange 2010 to Exchange 2013.
    The plan was this:
    Install Exchange 2013 on another server (Windows 2008R2)
    Wait until everything is replicated
    Remove the Exchange 2010  server from the organization
    Uninstall Exchange 2010
    Install Exchange 2013 on the Windows 2012 server
    Wait until everything is replicated
    Remove Exchange 2013 from the Windows 2008R2 server
    But here is what actually happened:
    Installed all Exchange 2013 prerequisites on the Windows 2008R2 server
    Began Exchange 2013 server setup on the Windows 2008R2 server. Included both Mailbox & CAS roles
    At step 11 of 15 (not sure what that was, though), received this error message:
    Error: The following error was generated when "$error.Clear();
            netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes   
            " was run: "The term 'netsh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
    and try again.".
    And setup halted. I ran the netsh command via the command prompt, and it correctly said something about four rules being created or updated (not sure of exact verbiage). Now, when I try to restart setup, it says it is in the middle and will try to complete
    but stays at 0%. But here is the most immediate issue:
    Now I cannot access e-mail from any workstations (says Exchange server is unavailable)
    Opening EMC on the Exchange 2010 server: I get as far as Microsoft Exchange -> Microsoft Exchange On-Premises and get this error:
    The attempt to connect to http://[Exchange 2010 FQDN]/PowerShell using "Kerberos authentication failed: Processing data from remote server [Exchange 2010 FQDN] failed with the following error message:
    Couldn't find Enterprise Organizaiton container. (Note that it refers to the local server as remote server)
    I get an event 7031 on the Exchange 2010 server: The Microsoft Exchange Service Host service terminated unexpectedly
    Opening the Exchange Management Shell on the Exchange 2010 server yields the same message regarding "Couldn't find the Enterprise Organization container..."
    It also says, "Connecting to [Exchange 2013 server FQDN], then says connected to that server. Opening EMS on the Exchange 2013 server seems to connect correctly to the Exchange 2013 server, but there is no EM Console available there.
    At this point, I am lost. I will continue to research this online but may have to call Microsoft soon, since we are entirely down at the moment. Any help is much appreciated!

    All of the above, I believe. And E2003 is on the DC (and functioning just fine); E2012 on a member server (this is a very small environment--they have only the DC, a DB2 database server, and a lightly-used and old terminal server). I just spent 12 hours
    on the phone with MS support on this issue, and it has now come down to this: the Exchange 2013 installation will not run to completion. It has failed repeatedly at a few points today, all related to the shell being unable to access Windows EXEs or environment
    variables with variations on this error:
    "...not recognized as the name of a cmdlet, function, script file, or operable program..." for each of these:
    netsh (windows exe)
    sc.exe (windows exe)
    hostname (windows command that returns workstation name)
    These all work from the command prompt. I am currently stuck on sc.exe failing on each attempt to install Exchange 2013 or Exchange 2013 SP1. Nor can I just remove it--it insists on attempting to proceed with installation even with the manual command-line
    argument to remove it instead.
    At this point, I am awaiting a night call back from Microsoft support, since the technician that worked on it with me for 12 hours today had to go home.

  • Exchange 2013 transition to Exchange Online

    Hello all,
    I'm needed to transition mine Exchange 2013 from on premises to Exchange online. I will use cutover migration, but I have question related to resource mailbox:
    Will resource mailboxes, like rooms etc. will be migrated in same batch as everything else?
    BR,
    Janis

    Hi,
    As far as I know, Resource Mailboxes (Room, Shared, Equipment) is moved between on-premise Exchange servers in the exact same way as User Mailboxes:
    http://social.technet.microsoft.com/Forums/exchange/en-US/f60d736d-0d45-4c27-adc8-a7e04afdb6e3/resource-mailboxes-and-contacts-move-during-transition-to-exchange-2013?forum=exchangesvrdeploy
    Based on my research, there is nothing special for resource mailboxes in the transition from on-premise to Exchange online:
    http://technet.microsoft.com/en-us/library/jj898486(v=exchg.150).aspx
    And you’re welcomed to confirm it on our Exchange online forum:
    http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

Maybe you are looking for

  • PROCEDURE IS NOT EXECUTED WITH IN THE DATABASE TRIGGER

    The follwing databse trigger works fine but the procedure lv_calc_pkg.p_orders_executed(:new.stock_code,:new.selling,:new.buying,:new.qty,:new.price); is not executed please help CREATE OR REPLACE TRIGGER SE.LV_SUMMARY_TRADE_TR AFTER INSERT ON SE.LV_

  • Query for clearing the caches automatically in the portal?

    Hi There, We are using EP Portal 6,currently we are having Oracle Archive logs issue which slows down the system.Now we are clearing the caches in the System Landscape-> Universal Worklist & Workflow->Universal Worklist Administration->Universal Work

  • Confirmed Dimensions. OBIEE Not able to pull data from two fact tables.

    Hi Experts, I have a very simple set up of Star Schema with two fact tables and 1 dimension. Both fact tables joined to the dimension at the same level. When i pull a column from both fact tables and the dimension table in OBIEE, it has to create sim

  • BP Opening balance

    Hi all, How to enter the Business partner outstanding balance in SAP B1 2007 B Pl-08. for e.g... The cutomer ABC is having consolidated balance==1000 Rs. Balance agaist invoice1==100  Bill No-1  Bill Date--02/02/2009 balance Against invoice 2==500 Ba

  • How to Transmit video over h263-2000/rtp

    I want to transmit a 3gp video over h.263-2000/RTP but this format is not supported by JMF APIs. I tried installing Fobs4jmf plugin in order to read 3gp video file but the supported output formats are h263/rtp and jpeg/rtp....nothing about h263++/rtp