Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario  1 : for internal outlook connectivity 
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Similar Messages

  • External emails not received after shutdown of Exchange 2010 in coexistence with Exchange 2013

    I have exchange 2013 and exchange 2010 in coexistence mode. All mailboxes have been moved to Exchange 2013 and firewall/spamfilters already pointed to Exchange 2013 CAS server. I can receive/send from and to external addresses, however when I shutted down
    the Exchange 2010 all incoming external mails were not received. What could be the cause?

    Start by re-checking how the device that takes the traffic from the external MX IP to internal is configured.
    Sniff the traffic to ensure that it is hitting 2013 directly.
    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.

  • Exchange 2010 CAS array with Exchange 2013 Mailbox Servers

    Here is our current scenario,
    Exchange 2007
    2 - Hub Transport Servers
    2 - CAS servers (cluster NLB)
    2 - Mailbox servers (clustered)
    Exchange 2010
    2 - Huib Transport Servers
    3 - CAS servers (array NLB)
    2 - Mailbox servers (1 DAG)
    We have not migrated any users to the Exchange 2010 environment yet. We're thinking that at this point we would rather go from 2007 to 2013. Does the 2013 mailbox server work with a 2010 CAS array?

    Hi,
    As far as I know, CAS array doesn' t exist in Exchange 2013. And OWA and other requests can be proxyed and redirected from Exchange 2013 to Exchange 2010.
    For more information, you can refer to the following article:
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2010 co-existence with Exchange 2007 issue NDR size Four Times then we send

    Hi All,
    I am facing some strange issues of NDR size four times then we send like if I send 1 MB message to internal OR external recipient then we receive 4 MB NDR.
    Even we send one black mail with subject Test mail of 4 kb then we receive 16 kb NDR is it due to architecture change or something else.
    Everything was fine with Exchange 2007 but facing this issues after we change the mail flow to Ex2010.
    Any help really appreciated
    Regards
    Anand S
    Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

    Hi Anand,
    From your description, the NDR size is four times than original message size. I would like to verify the following thing for troubleshooting:
    How many people has this issue, only one or all the people?
    If only one user has this issue, I recommend you move the user's mailbox to another mailbox database and check the result.
    If all the people have this issue, please enable Pipeline tracing and see if there is any hint. If the issue persists, please install the latest Service Pack and Rollup and check the result.
    Here is an article for your reference.
    Enable Pipeline Tracing
    http://technet.microsoft.com/en-us/library/bb125018(v=exchg.141).aspx
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2010 ambiguous URL'S issue while coexist with exchange 2013

    Hi ,
    Please correct me if i am wrong and also all of you tell me your valuable suggestions.
    Like as said in the below article we are having an exchange 2010 ambiguous url's in place.
    Referred
    article : 
    http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx
    As said in this article, if we have exchange 2010 ambiguous url's in place we will face issues during exchange 2013 coexistence.I agree with that point .
    Question : On such case why don't we use a separate namespace for internal and external outlook anywhere settings in exchange 2013 which is different from cas array name and also there is no need to disturb the existing exchange 2010
    environment by changing the rpc client access attribute in exchange 2010 databases or by forcing the exchange 2010 internal outlook clients to connect via OA. Please clarify my doubt and say whether the mentioned scenario is possible or not ?
    Note : Same time please consider the new namespace which is going to be utilized on exchange 2013 outlook anywhere settings is available on SAN certificate.
    Regards
    S.Nithyanandham

    Hi ,
    Please someone shed light on this case.
    Regards
    S.Nithyanandham
    Thanks & Regards S.Nithyanandham

  • Exchange 2010 OWA usage in Exchange 2013

    Hi,
    I have Exchange 2010 with Sp3 Currently running in environment, Now we have plan to Migrate it to Exchange 2013.... Total number of mailbox is around 26000.
    Before Migration we want below things to keep in mind...
    1. We want to Use existing exchange 2010 OWA url ( mail.abc.com ), How to accompolish this as it will take couple of months to migrate all mailbox ?
    2. Can i use my Existing Exchange certificate to get the above goal done ?
    3. What will be the steps and pre-requsite to achieve the Goal ?
    An Early reply would be appreciated !! 
    Amit

    Hi Amit 
    First Change SCP of Exchange 2010 CAS VIP to Exchange 2013 CAS VIP.
    Configure external  DNS records accordingly.DNS entries should be pointed to Exchange 2013 CAS from Exchange 2010 CAS.
    Ensure that you are having a seperate name for CAS array from external ews url
    Outlook Anywhere should be enabled and Url should be external URL which points to Exchange 2013.
    Authentication for OUtlook Anywhere should be - NTLM
    for OWA exchange 2010 - FBA and windows 
    Point your new CAS server to the firewall or TMG . Now from exchange 2013 all request will be proxied to 2010 users 
    You cannot use the same certificate . YOu need to add seperate entries as the host name for new servers will vary
    Apply a new certificate with all the required site names included in Exchange 2013 CAS.
    Whats more you can refer my blog as well 
    http://exchangequery.com/2014/05/02/things-to-consider-before-configuring-autodiscover-in-exchange-20102013-coexistence-scenarios/
    Cheers :)
    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

  • Is it possible to connect my mid 2010 Macbook Pro with my 21.5" iMac 11,2 so that I can work with dual screens?

    Is it possible to connect my mid 2010 Macbook Pro with my 21.5" iMac 11,2 so that I can work with dual screens?

    try xxx - may work
    _may_ work.

  • Exchange 2013 Outlook Client connectivity

    I'm migrating from Exchange 2010 to Exchange 2013 and on the final stages. I pointed the external and internal DNS records to Exchange 2013. I moved one mailbox to Exchange 2013 and then tried to create a new Outlook client profile and bring the mailbox
    up however the client would not connect. It stated trying to connect encrypted and unencrypted. It did not work. I checked nslookup and the IPs are all set pointing to Exchange 2013. I then checked my certificates. I have a certificate that is a wild card.
    When I checked assigned services on my wild card it had IIS and SMTP assigned. Also in IIS on the default site bindings what should you use as a certificate on the two https settings? Originally they were the local generated certificate. I changed them to
    the wild card no luck. Please assist.

    Try running through this and see if it gives you some ideas on what is wrong:
    https://testconnectivity.microsoft.com/
    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

  • Owa working but outlook cant connecting to the new mailbox in Hosted exchange 2010 SP1

    hi i recently join one organization they having Hosted Exchange 2010 Sp1 i created one new organization Unit and created 
    new MailBox but didnt give any permissions so when i try to connect to OWA then i log in and send and recive e-mails but when i try to connect to Outlook it say the name not found ...........
    please help me

    Hi sorry for so late respons i was on leaves .
    new User not connected automatically getting the message "user name Not found " also when i try to connect manually the error message " there is problem with the security certificate. the name on the security certificate is invalid or does not match ..." also
    Outlook some problem with some old Mailboxes
    from Exerca i get the following errors i.e Certificate related 
    The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
      Autodiscover was tested successfully.
    Additional Details
        Elapsed Time: 2927 ms.
    Test Steps
            Attempting each method of contacting the Autodiscover service.
      The Autodiscover service was tested successfully.
    Attempting to test potential Autodiscover URL https://xyz.co.uk/AutoDiscover/AutoDiscover.xml
      Testing of this potential Autodiscover URL failed.
    Additional Details
             Elapsed Time: 417 ms.
    Test Steps
    Attempting to resolve the host name xyz.co.uk in DNS.
      The host name resolved successfully.
    Additional Details
    Testing TCP port 443 on host xyz.co.uk to ensure it's listening and open.
      The port was opened successfully.
    Additional Details
    Testing the SSL certificate to make sure it's valid.
      The SSL certificate failed one or more certificate validation checks.
    Additional Details
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server xyz.co.uk on port 443.
      The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    Additional Details
    Validating the certificate name.
      Certificate name validation failed.
      Tell me more about this issue and how to resolve it
    Additional Details
        Attempting to test potential Autodiscover URL https://autodiscover.xyz.co.uk/AutoDiscover/AutoDiscover.xml
      Testing of this potential Autodiscover URL failed.
    Additional Details
    Test Steps
    Attempting to resolve the host name autodiscover.xyz.co.uk in DNS.
      The host name resolved successfully.
    Additional Details
    Testing TCP port 443 on host autodiscover.xyz.co.uk to ensure it's listening and open.
      The port was opened successfully.
    Additional Details
    Testing the SSL certificate to make sure it's valid.
      The SSL certificate failed one or more certificate validation checks.
    Additional Details
    Elapsed Time: 270 ms.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.xyz.co.uk on port 443.
      The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    Additional Details
    Validating the certificate name.
      Certificate name validation failed.
      Tell me more about this issue and how to resolve it
    Additional Details
        Attempting to contact the Autodiscover service using the HTTP redirect method.
      The Autodiscover service was successfully contacted using the HTTP redirect method.
    ..........................   Please help me how to resolve

  • How to disable Exchange 2013 Outlook Anywhere for internal Outlook client

    Hello;
    By default, Exchange 2013's Outlook Anywhere is enable for all user mailbox, if I disable the Outlook Anywhere per user mailbox, the user will not able to connect his Outlook client to Exchange 2013.  What is the best method to disable the Outlook anywhere
    on mailbox but let the Outlook 2013 still able access to Exchg server.
    The initial idea is to prevent user from access to company Exchange server from ANYWHERE, we just want to open the Outlook Anywhere for the authorized user only.  Looks like Microsoft did not think about the security.
    thanks!

    Hello;
    By default, Exchange 2013's Outlook Anywhere is enable for all user mailbox, if I disable the Outlook Anywhere per user mailbox, the user will not able to connect his Outlook client to Exchange 2013.  What is the best method to disable the Outlook anywhere
    on mailbox but let the Outlook 2013 still able access to Exchg server.
    The initial idea is to prevent user from access to company Exchange server from ANYWHERE, we just want to open the Outlook Anywhere for the authorized user only.  Looks like Microsoft did not think about the security.
    thanks!
    I don't understand your request. If you disabled Outlook Anywhere, Outlook will only be able to connect via IMAP or POP3.
    If you want to disable this ability and allow some then perhaps use cas-mailbox to disable in bulk and then enable only those allowed:
    http://technet.microsoft.com/en-us/library/bb125264(v=exchg.150).aspx
    The MAPIBlockOutlookRpcHttp parameter enables or disables access to the mailbox by using Outlook Anywhere (RPC over HTTP) in Microsoft Outlook.
    Valid values for this parameter are:
    $true   Only Outlook clients that aren't configured to use Outlook Anywhere (RPC over HTTP) are allowed to access the mailbox. By default, Outlook 2013 is configured to use Outlook Anywhere.
    $false   Outlook clients that are configured to use Outlook Anywhere (RPC over HTTP) are allowed to access the mailbox.
    The default value is $false.
    Twitter!:
    Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Outlook 2010 behaves strange with exchange 2013

    Hello,
    I imported a san certificate with a domain name for local use. This is exchange.xxxx.xx . This is also a A-record pointing to the same ip of the actual server.
    The name of the exchange server itself is mail01.xxxx.xx .
    My laptop is not a part of the domain. When i want to add my mailbox i use exchange.xxxx.xx for the server. My username can't be resolved. When i use the name of the server mail01.xxxx.xx then it works.
    I tested this with outlook 2013 and exchange.xxxx.xx could resolve my mailbox.
    So for outlook 2010 i need to use the name of the server where exchange 2013 is installed.
    For outlook 2013 i can use the alias exchange.xxxx.xx.
    Anyone has any idea ? It's not blocking. We haven't started the migration yet :p

    Hi,
    Based on my knowledge, in Exchange 2013 environment, the server name option is filled with the new type"mailbox GUID+@+ the domain portion of the user's primary SMTP address" when we configure the Exchange account in Outlook client.
    In your case, I recommned you add the following record in the host file of the computer which installs the Outlook 2010: the host name Exchange.domain.com points to your server IP address .
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support
    Thx for your feedback. I will check this out.

  • Outlook 2010 gets disconnected with Exchange 2010

    Hi
    We are facing a strange issue that some Outlook users are getting disconnected and it reconnects after 1 or 2 hours or after changing the IP of the system. During the Outlook disconnection period we can't even telnet on port 433 to the CAS BLB name or IP
    (same time we can able to ping CAS name). The security and network team is checking the same, is there any thing to be checked with Exchange servers regarding this issue?
    Thanks in Advance
    LMS

    Also I found a similar article "http://social.technet.microsoft.com/Forums/exchange/en-US/06f4d721-a778-4437-b43a-9ad6ca70344b/outlook-clients-randomly-disconnected-from-cas-array?forum=exchange2010"
    which almost explains the same issue - users are getting disconnected and even unable to telnet teh cluster IP and getting connected after a few minutes.
    So we will go ahead and re configure the NLB. We plan to keep the existing NLB on one server and remove and add second node and do the same for the other. What do you think?
    LMS

  • Exchange 2010 coexist with exchange 2013

    Hi All ,
    Planning to have a coexistence scenario in my environment which is mentioned below
    Exchange 2010 - ambiguous url in place - OA enabled 
    For mapi/rpc traffic - mail.domain.in -  exchange 2010
    For https traffic - mail.domain.in - exchange 2010
    mail.domain.in will get resolved in to cas array in exchange 2010 .
    After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
    exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
    just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
    Note : 
    On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
    Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
    Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
    exchange server via exchange 2013 server.
    question : I would like to know above mentioned scenario is possible or not ?
    On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
    So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
    All of you tell me your valuable suggestions.
    Regards
    S.Nithyanandham

    Hi,
    Going Straight to the point... and answering your question...
    The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
    As per Exchange Team...
    In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
    breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
    their DNS cache expires after the shared FQDN is moved to CAS 2013.
    As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
    change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
    URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
    on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
    fix existing Outlook clients with the old value in the server field. 
    So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
    Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
    Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
    Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
    Outlook 2013: 15.0.4420.1017 (RTM or later)
    I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
    As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
    Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
    From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx> 
    Hope it can help you!
    Cheers,
    Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

  • Outlook Users connection issues after Mailbox Migration from 2007 to 2013

    Hi,
    We have a coexistance between Exchange 2007 SP3 and Exchange 2013 CU7. There is an issue when after migrating the user from exchange 2007 mailbox to exchange 2013, the outlook keeps on prompting for password when it is being launched. Checking the Connection
    Status we found that there is a connection to the old 2007 Server and the type is Exchange Public Folder. I have migrated the public folder and checked the Mailbox of the user and found that the DefaultPublicFolderMailbox is set to the 2013 Public Folder Mailbox.
    If I check my 2013 MailboxDatabase Properties, It sill shows that PublicFolderDatabase Properties is still pointing to the 2007 Public Folder Database. Any resolution on this?
    Another issue is, We set outlook anywhere on the 2013 to use basic authentication, however, when users are migrated to 2013 the Outlook client changes to NTLM. even if we set the outlook to basic to make it work, it still comes back to NTLM after a while.
    I did most of the resolutions online to use powershell to make changes to outlook anywhere but no luck. any suggestions is highly appreciated.
    Thanks & Regards,
    Arthur

    Hi,
    For the first problem, please check the msExchHomePublicMDB attribute for mailbox database in Exchange 2013, you can check this attribute in ADSIEdit.
    If this attribute is pointing to Exchange 2007 public folder database, please set to blank. After that, please restart the information service.
    And for the second question, I suggest we open a new case for this issue. In order to avoid confusion and keep track of troubleshooting steps, we usually troubleshoot one
    issue per thread in order to find a resolution efficiently.
    Thanks for your understanding.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 logon statistics with powershell

    I am trying to get some logon statistics from a Exchange server 2010, I am using the following command, 
    Get-MailboxServer | Get-LogonStatistics | Select UserName,ClientVersion,LastAccessTime,ServerName, but it returns this, 3587.0.32963.1, as a version
    number.
    I have read that it is af bug in Exchange 2010. Does anyone have a workaround?

    Right, I guess along with IP address Outlook doesn't send version information either back via Get-LogonStatistics...
    The client IP address for an Outlook 2010 client is not logged in Exchange when you use the Get-LogonStatistics command -
    http://support.microsoft.com/kb/2292750
    However you can get Version information from RPC Client Access Logs located in below folder...
    \Program Files\Microsoft\Exchange Server\v14\Logging\RPC Client Access

Maybe you are looking for

  • How to reinstall iPhotos without previous apple id for mac book

    I bought a macbook and have the master password. But i can't update iPhotos because i do not have the previous owners apple id. How can i reinstall or update

  • Pen drive + mov = ??

    exported a movie from final cut express up at school and put It on my flash drive. I got home and tried to copy it to my mac and it said insuficient privelages. Then ejects the drive. I try using vlc, fce, and fcp but to up avail. I bet that if I try

  • Frequent mail sync with iCloud

    Has anyone else had this problem? Since upgrading to Mavericks the OSX mail program syncs ALL my folders with my iCloud account every two minutes or so. This clobbers my WiFi connection quite hard. Under previous OS versions mail folder sync happened

  • PleASE PLEASE HELP THIS IS DRIVING ME MAD

    This should be so simple, all I have is a java class which I need is used to ax a oracle db and returns a recordset. 1st q do I need to reg this class or does web logic look in a specific area and reg them automatically. 2nd question I have a jsp pag

  • Crosstab query using pure SQL only

    Hi all, Found a lot of threads on crosstab, but none seems to address what I need. I need to perform crosstab query using pure SQL only & the number of columns are dynamic. From a query, I obtained the below table: Name Date Amount Alex 2005-06-10 10