Equipo physical Exchange 2003 Virtualizacion

Similar Questions

• Exchange 2003 / 2010 on vshpere foundation 4.1

  We are a small organization with 60 mailboxes on a physical server to Exchange 2003.  My VMWare environment consists of 710 2-Dell servers with 32 GB of ram and vmfs volume unique raid 10 on each server.  There is no SAN and this seems to serve us well, even if a San would make things like Vmotion and HA as possible, that's what we have at the moment.

  Ideally I would like to move the exchange Server 2003 on a VM host and continue to use this platform for another year or two, but there seems to be problems of performance that are best addressed in the 2010 version.

  Would it not possible to run Exchange 2003 on one of my servers host with the VMFS volume shared using storage for databases and log files?   What I do need to provide some physical drives dedicated for exchange databases, or is there any recommended configuration: for the virtual drives for a small exchange on VMWare Server?

  Jim

  From a disk I / IO perspective if you have only 60 users, I don't think that you will have problems even if you use Outlook in Mode online (as opposed to the Cached Mode).  In addition, there are a few things you should think about to / consider:

  (1) Exchange 2003 is not supported in a machine virtual on a hypervisor/platform. You can't get support from Microsoft if you are running Exchange 2003 in a VM on vSphere, Hyper-V, whatever it is.  I've had clients essentially turned almost immediately without even best effort support for Microsoft.  I'm not sure of the importance of technical support Microsoft for you, but for many of my clients, the risk is not worth...  Customers choose to migrate to Exchange 2010 (or 2007 for years before) that supports virtualization complete.

  Microsoft has created the program (SVVP) Validation of virtualization server to validate their applications running on virtual machines on multiple platforms.  I would check that out to see exactly what is and is not supported all the way back to Exchange 5.5 If you can believe it.

  http://www.windowsservercatalog.com/SVVP.aspx?svvppage=svvpwizard.htm

  (2) Exchange 2010 offers big improvements over Exchange 2003 in more than a reduction of inputs and outputs.  There are so many new features of the product that it is useful to consider migrating directly to Exchange 2010.

  If you really want to virtualize it, I would follow advice from design even for physical Exchange 2003 servers.  You don't need the physical disks dedicated to the database/log, but you may want dedicated virtual disks for easy management.  In addition, you can just follow normal recommended or even existing P2V your Exchange Server.

  So to sum up - Yes you can virtualize Exchange 2003 and as small as your environment, it should run perfectly, but it is not supported by Microsoft.  I would consider an upgrade to Exchange 2010 as preferred approach if possible.

  Matt

  http://www.thelowercasew.com

• Best practices for Exchange 2003 with VMWare ESXi 3.5 and iSCSI SAN

  Hello guys,.

  Here's the Q? We have 1 physical Exchange 2003, the HOST of 4 and 1 iSCSI SAN with LUN 3, 1 for data, 1 for VMWare and 1 for SQL, if we're going to virtualize it, I don't know where to put data Exchage and newspapers. I do not think that that is a good practice to put together the data but I do not have another SAN. So, what can I do?

  Thank you.

  We have 813 mailbox.

  I agree with cainics, start an average size and go from there.  I know it's a production mail server and you can not exactly 'play' with the settings because this requires time, but if you do the VM too big, you would have nothing left for other virtual machines.

  I would go 2 vCPU and at least 4 GB of RAM, maybe 8GB.  There must be parameters for the Exchange mailbox 813 and X users # to implement your environments in order to get an idea of the amount of RAM that will be... 4GB seems minimal to me, but 8 GB would probably be better like that.

• Cluster Exchange 2003 on ESX4i on one physical host, use local storage

  I'm trying to implement a 2 node Exchange 2003 on a physical ESX4i cluster use local storage.  I have 2 network cards, assigned drives to be on a different SCSI controller, when I set up the first node of the cluster, I am not able to select the disc that I put in place for the Quorum, it will only install on the C drive, which is the OS disc. What should I do to be able to use the shared disks configured for the cluster.

  So, once the scan is complete you should have a section called "Quorum resource Detection", is there something there?  By default, Windows attempts to use the smallest available partition that is not the system partition, which is larger than 500 MB and a shared bus.  This last point is key, see photo.  It's the only thing I can think of for that is why you wouldn't see the quorum...

  -alex

• Deployment of Exchange 2010 in an Exchange 2003 environment

  Hello

  I recently installed Exchange 2010 in an Exchange 2003 environment.  I need help on migrating all my settings to Exchange 2010 - mailbox recipient policies, address book offline, free/busy, etc.
  I looked these TechNet following help sheets, but by getting a little confused:
  http://TechNet.Microsoft.com/en-us/library/aa996719.aspx (Exchange 2013 requirements)

  http://TechNet.Microsoft.com/en-us/library/ee332348.aspx (upgrade of the Exchange 2003 Client Access)

  http://TechNet.Microsoft.com/en-us/library/aa998186.aspx (Exchange 2003 - Planning Roadmap for upgrade and Coexistence)

  http://TechNet.Microsoft.com/en-us/library/ee681662.aspx (to install Exchange 2010 in a mixed Exchange 2003 and Exchange 2007 organization)
  I have two domain controllers.  Exchange 2010 is not installed on a domain controller, but Exchange 2003 is one of them.  I would like to eventually decommission the Exchange 2003 environment and implement and to Edge transport server in its place.  Exchange 2010 is installed on a Virtual Machine.  It running SP3, the latest service pack.  Exchange 2003 is on a physical machine, and it running SP2.
  Please help me simplify what exactly I have to do to migrate configurations from 2003 to 2010.
  Thank you for your much appreciated assistance.

  TK

  Unfortunately is not on this site.  Server questions should be asked on Technet

  http://social.technet.Microsoft.com/forums/en-us/home

• Virtualization of Exchange 2003

  We are about to start (finally) virtualization of our systems.  One of these systems is a Standard Exchange 2003 on Windows 2003, using DAS server and serves about 600 boxes mailbox (if users concurrent max would be around 200 users).  Current physical area includes 3 disks, C, D and E.  C is for system D is application/newspapers and E is for banks to information (only 2 - public and private).

  After reading the various articles and best practices I came with a plan.  Could you get it someone please let me know if it is a good idea?

  In a test environment first of all (with DC operation), separated from the production network:

  Plan of P2V is the current physical Exchange box using VMware Converter Standalone.   Each physical disk would be converted to a virtual disk.  It will implement a SAN to shared storage iSCSI.  Thought create LUNS separate D and E drives, just don't know if this is necessary.  All Exchange and protection antiviruss services will be stopped during the P2V.  I tried to make a cold-clone, but don't know if I can due to the fact that we won't have a VMware enterprise license.

  Once that P2V is complete, power to the top of the new virtual machine.  Remove any vendor (HP Insight) specific applications and drivers.  Then, start the Exchange services and test.

  If successul, process document, repeat the test and before you run on the production system.  Once final, production VM is created, physical stop and turn on VM again.

  If you're ok with the unsupportability of the solution, then I say go ahead and virtualize it.  I still believe that deploying a new server and migrate the mailboxes are the cleanest way to do but to understand the limitations it.  All the more that I would recommend if you could back migration to Exchange 2010 rather than another server in 2003.  There is no direct upgrade from Exchange 2003 to 2013 path so you will need to go to Exchange 2010 in a first time in any case.  Might as well get ready now.

  Migration is easier because then you're not taking all issues with the server of your virtual infrastructure.  It is also pointless to worry about uninstalling the hardware drivers, of unnecessary software, etc.

  I had some success with P2V migration running on Exchange servers.  As I said earlier, you will have the best chance of success if you can organize the downtime to stop all of the Exchange during the P2V services.  That's how I managed in the past.

  Do your homework and understand what works best for you.  I'm sure you can succeed with two approaches.

  Good luck!  Feel free to come back and post how things went or if you need any help.

  Matt

  http://www.thelowercasew.com

• Exchange 2003 P2V - duplicate name exists on the network

  Exchange 2003 P2V

  Hello

  I just finished the p2v for exchange 2003, now, I get an error that a duplicate name exists on the network - what do I do?

  Thank you

  You must stop the physical Exchange Server.

• Migration of interns of exchange 2003 to Microsoft Cloud Exchange

  Hello

  I need help migrate my internal data from Exchange 2003 to Microsoft Cloud. It's my first time

  the display, if more information is needed please let me know. I bought Office 365 with Exchange for my client.

  Server - SBS2003

  Customers - Office 2007 and 2010

  Thank you

  Ty

  Hello

  Your Question is beyond the scope of this community.

  I suggest that repost you your question in the Forums of SBS.

  https://social.technet.Microsoft.com/forums/en-us/home?Forum=smallbusinessserver

  And here:

  https://social.technet.Microsoft.com/forums/Exchange/en-us/home?Forum=exchangesvrgenerallegacy

  See you soon.

• Exchange 2003 Migration to Office365 with SSO

  Hi all

  Merry Christmas to start!

  I work for a company that run Exchange 2003. We plan to do a migration to Office365 and I am researching on the best solution.

  I am aware that there are three main options available, hybrid/intermediary/putting in service.

  My instincts suggest that the best option would be to complete the migration using the staging process, but I think that if I take this route I can't implement single sign on? This is the case...

  If so, is this means to ensure single sign-on can be used, then I can only implement a hybrid solution?

  Hello

  And a Merry Christmas to you, too.

  Your Question is beyond the scope of this community.

  Please repost your Question in Exchange for TechNet Forums.

  https://social.technet.Microsoft.com/forums/Exchange/en-us/home?Forum=exchangesvrgenerallegacy

  See you soon.

• SBS 2003 migrating exchange 2003 to exchange 2010

  Hello

  It is possible o migrate from exchange 2003 on SBS 2003 to new windows server 2012 STD with exchange 2010, but does not move the FSMO rules to windows 2012? I can't downgrade SBS 2003 because I have an application that cannot be migrated from Small Business SERVER 2003.

  Best regards

  Marcio Moreira

  Try asking in Exchange Server Forums:
  http://social.technet.Microsoft.com/forums/Exchange/en-us/home?category=exchangeserve

• How can I restore and old information store (Exchange 2003) to my Exchange Server existing (Exchange 2010)

  Nice day

  3 months ago I installed Exchange Server 2010, now I need to recover a mailbox from a backup. The backup was performed while he was still Exchange 2003. I want to know is you can restore an old Exchange 2003 database in the Exchange 2010 recovery store, and if so what is the way forward. PS I use symantec backup exec 2010 R3 as backup software.

  If it is not possible, is there any other way to retrieve mailbox information

  Any help will be much appreciated.

  Hello Wh@pd@p,

  I suggest posting your question on our forums TechNet for Microsoft Exchange Server, located here again:
  http://social.technet.Microsoft.com/forums/en-us/category/ExchangeServer

• How to switch my domain server 2003 & exchange 2003 Server

  I have Windows 2003 Server domain with exchange 2003 server running on the same machine, I want to improve my server domain to Windows server 2008, both my exchange to Exchange Server 2007 server, tell me the procedure, if I upgrade my server exchange server or domain first. What are the steps to do this.

  Support is located in the Windows Server Forums:
  http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer/

  Support is found in the Exchange Server forums:
  http://social.technet.Microsoft.com/forums/en-us/category/ExchangeServer/

• Exchange 2003 with clusters

  Hello

  I'm new with Exchange 2003 cluster environment in our Organization, we have a network that will make all activity the network down, then after 12 to 14 hours. Network will rise

  Our Exchange is configured in the cluster with call tool Symantec Enterprise vault archiving environment, we also have the ANTI-SPAM called Sonic Wall filter

  I just wanted to know what kind of care I have to take before and after the network outage?

  Your suggestion of all will be of great help for me

  Kind regards

  Patricia

  Hello SwapnilJain27,

  It would be better to post in the forum of Exchange Server.

  You can find the category that fits your question below:
  http://social.technet.Microsoft.com/forums/en-us/category/ExchangeServer

  Thank you!

• Exchange 2003 Server kept receiving unknown Email sending out through SMTP and the paper jam in the queue folder

  Hello Sir,

  I have a problem with one of my SBS Exchange 2003 servers.

  At first, I was getting a lot of 3008 errors for a non-delivery report with a status code of 5.0.0 was generated for recipient rfc822; address email is removed from the privacy * all these repeated error messages from the event log, SMTP and Exchange Routing service...

  I looked around and discovered more than 10000 .eml in my x:\program files\exchsrv\mailroot\queue folder.  At first, I thought that my server or one of my workstations was compromised, but all workstations have local antiviral software (symantec endpoint protection), my server software also has antiviral and I have a mail server antivirus (symantec endpoint protection).  I scanned all of the computers on the network and even tried almost all of them closing to see if new entries have been created in the queue.

  Unfortunately, more than entries kept by appearing so I kept looking.  By opening one of the .eml, I discovered my own responsibility that I attach to outgoing emails if I have my server acted as a mail relay.  I checked for this and I have been clean.  I kept searching in the .eml and discovered different origins IPs of the Internet.  Am I right to assume that my mail server is BOMBED or attacked with emails with false return addresses and my mail server sends return NDR for spammers/compromised machines on the net?  I tried to stop the exchange services and tried to rename the vsi file 1 to something else as one of the suggested MSKB, but the file was protected.  How can I stop this, it's slowing down my mail server and fill out my HD.  I can't block the IP to shippers because it comes from everywhere.  Help!  There are about 2 to 5 new .eml created every minute!

  TKS and best regards,

  LT

  Hi Lennet,

  Your question is more complex than what is generally answered in the Microsoft Answers forums. It is better suited for the IT Pro TechNet public. Please post your question in the forum TechNet for assistance:

  Microsoft Exchange Server

  Hope the helps of information.

• Exchange 2003 migration to Exchange 2010

  Dear Sir/Madam

  I have a partner who has a parent and a child domain, it has exchange 2003 is installed in the child domain.

  He wonders if he can install exchange 2010 in the partner area & migrate all the exchange 2003 from the child domain in the newly installed exchange 2010 in the area of the partner.

  Please repost your request in one of the most appropriate Microsoft Exchange Forums.  Thank you!