I have a new installation of SBS 2011 Trial with Exchange 2010. I've run the "Connect to internet wizard", the "Fix my network Wizard" and the "set-up you internet address" wizard and everything completes successfully without error. I've configured my local accepted domains. However, if I set-up a new user mailbox within Exchange or add a maibox to an existing user in AD, then go into the user properties and select the "Email Addresses" tab, the whole OS freezes. Any ideas? Also, if I log into OWA and send an email from the admin acct to the admin acct, the email are saved to Drafts and never go anywhere. Confused what is going on... Any help is appreciated...

Never seen that lock up the system before. I would suspect either bad hardware or a bad installation of SBS. Emails going in to Drafts is usually a sign that one of the Exchange services isn't running. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

what could be "wrong" with the hardware? Where would you look first? The Exchange services not running are IMAP, monitoring, POP3, and server extension for WIndows Backup Can't find the SMTP service in SBS 2011...

There is no SMTP Service in Exchange 2007 and higher. It is part of the transport service. If there was an SMTP service then you would have much bigger problems as that is not supported to be installed on a server with Exchange. As for hardware, could be anything. RAID controller, motherboard etc. I work on the basis that if a server is going to fail, it does so shortly after coming out of the box, so if new hardware it could be a problem there. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hi Keeebs, Any updates on this issue? For this issue, I suggest you follow these steps to troubleshoot the problem: 1. Use Exbpa to do a health check for the Exchange Server. if you got any error, please follow it suggestion to troubleshoot the problem. 2. Please check the event log, if there is any error please paste in your next post. Thanks, EvanPlease 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.

I must apologize, in my frustration, I left out this was a virtualized install on ESXi. The problem was I was using VSphere console to access the OS. I switched to RDP - problem solved.

That is a common problem - you need to change the video driver. You should use the one in C:\Program Files\Common Files\VMware\Drivers\wddm_video Don't use the drive in the "Video" directory as that will hang the system. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Thanks!!