Is Windows Azure officially supported for Exchange 2013?

Though Exchange 2013 can be installed on Windows Azure, however can somebody help me in knowing that if its officially supported with it OR can live environment of Exchange be setup on Windows Azure?

Hinte is correct.
You can set up a Exchange 2013 lab in Azure. You may have seen that Henrik Walther has done just that:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/deploying-exchange-2013-hybrid-lab-environment-windows-azure-part1.html
But this is just for practice / training.
Besides lack of support, cost of sufficient resources to run E2K13 correctly would be greater than simply using O365 / Exchange Online.
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.

Similar Messages

Is smb 3.0 already supported for exchange 2013

Hello,
We are looking to deploy exchange 2013. We have a netapp storage and vmware environment.
I was wondering if smb 3.0 is already supported for exchange 2013. I read in a blog of 2012 that it wasn't supported at the time. We would like to use it instead of a iscsi lun.

Hi,
Based on my knowledge, it is still not supported for Exchange 2013 up to now.
Here is an article for your reference, please refer to the "Exchange storage requirements" section.
Exchange 2013 Virtualization
http://technet.microsoft.com/en-us/library/jj619301.aspx#BKMK_Prereq
Another related article for your reference.
Exchange 2013 Storage Configuration Options
http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

SOFS support for Exchange Server 2013

Hi all,
I am aware of the following factors:
1. Exchange only supports block-level storage
2. Using SoFS as DAG FSW is not supported.
But may I confirm whether Microsoft supports the scenario below?
==============================================
My client has one set of Windows 2012 R2 Scale-Out File Servers to support their hyper-V farm. Storage is Dell MD3000 with Windows 2012 R2 Storage Space. Is it supported by Microsoft to run Exchange Server 2013 and Exchange Server 2010 in the virtual machines
which are running on SoFS? Assume IOPS has been properly sized.
==============================================
Regards,
William
William Yang

Hi,
There is no official documents talked about whether the Windows server 2012
Scale-Out File Server is supported for Exchange 2013 and Exchange 2010.
Generally, the supported storage configuration in Exchange 2013 is listed in the article below:
https://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
Hope it helps.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

EXMON "exchange server user monitor" for Exchange 2013?

Hello,
it Looks like EXMON is not supported for Exchange 2013. Is this correct or can i use it with Server 2012 R2 and Exchange 2013 (CU6++) ?
Is there any alternative to check high log growth rate to see which user is responsable for this?
Thanks for Feedback.
best,
Martin

Hi Martin,
Yes, ExMon is not supported for exchange 2013.
Except the suggestion above, here is an exclusive application for you reference, it could retrieve statistics for all or selected mailboxes in a specified database and server, it may give you some help:
Exchange Server Mailbox Statistics Tool - v1.6.2
The tool retrieves mailbox statistics which includes Folder Count, Total Items, Associated Items, Deleted Items, Total Items Size, Deleted Items Size, Oldest Item Date, Newest Item Date, Items Age, Mailbox Age and Quota details. It also includes an additional
option named "Archive Statistics Planner" which will let you search mailboxes and provide statistics report with specific dates.
Best regards,
Niko Cheng
TechNet Community Support

How to configure a proxy server for Windows Azure Tools in Visual Studio 2013

Hi Visual Studio/Azure Tools team
I would like to use the Windows Azure tools in Visual Studio 2013 to manage my Azure Web sites (Server Explorer -> Windows Azure -> Web Sites) from within my corporate network which is secured using a proxy server. Unfortunately, I am not able to use
the Windows Azure tools since the required HTTPS connection to windows azure is not going through the default configured proxy. Instead, Visual Studio tries directly to connect to port 443 which is blocked by our corporate firewall (and yes: there is no way
around using our proxy server). Other visual studio features like NuGet, updates, etc. work fine and use the configured proxy server.
So my question: How can I configure visual studio respective its Azure tools to use a proxy server instead of a direct connection? I already tried configuring the proxy server within the file devenv.exe.config but this doesn't show any effect for Windows Azure
tools.
Regards
tschaena

As we have very similar problems I consider the found solution a work arround an existing problem which will not work if corporate FW policy does not allow such changes.
In my mind, any tools in charge of dealing with some sort of FW protocols should deliver the following information, should make it absolute clear how to setup that the request packages are setup rigth at the first time.
a) proxy server
b) proxy port
c) proxy user
d) proxy users-password
e) proxy.auth.Preference="BASIC"
And for moste tools (including Visual Studio and AZUR Tools) it is absolut unclear
a) how to setup that on a per tools basis
b) OR who inherits this information from whom i.e. use the same as IE does, what if we use FireFox or any other browsers?
I understand that developers requested to cure such problem areas will often have difficulty to gain all required elemenst used to realy test the solution.
But I can tell you: I loos more time figthing down the FW setups for my clients. WHat I do at home in a sniff, takes ages to be realised by all the various clients on the market where each has to deliver the same sort of information but actually does not,
or has it just somewhere, but not in the vicinity of the demanding user.
Good examples i.e. NetBeans IDE where the Option Menu shows very clearly what information is required to pass through a FW/Proxy; but even there, the hint to start with a BASIC authentication schema is not part of this OPTION menu and must be added a JAVA
environment value. But at least, it works.
Sepp

Windows Azure Platform Support: "Prompted for "Windows Activation" when logging onto a Windows Azure Role Instance using RDP"

Symptom
When a user interactively logs (using RDP client) on to a Windows Azure Role Instance running Windows Azure Guest OS 1.11, they see a “Windows Activation” dialog box.
Action
The user can ignore this dialog box by simply clicking either “Cancel” or “Activate Later” button on the “Windows Activation” dialog box. This pop-up window is just an UI issue in Guest OS 1.11 and no OS functionality
issue. All Role instances running any version of Windows Azure Guest OS has valid volume licensing key and are already activated. There is no need to provide any activation key to validate the OS.
Please don’t try to activate Windows Azure Guest OS using your Windows Server OS Key, this will cause unexpected downtime and will require a reboot. Activating Windows Azure Guest OS is not a supported scenario.
Workaround
Use the next available OS or any previous version of OS (e.g., 1.10) to work around this issue.
Other forum references:
RDP on Webrole with newest guestOS: why is it asking for windows activation
Windows Azure Platform Support - If you found this post useful, let us know by clicking "Vote as Helpful". - #wapsupport

this is still an issue and the work around did not work

Database encryption supported in Exchange 2013?

hi,
according to this:
http://technet.microsoft.com/en-us/library/aa998022(v=exchg.80).aspx
MS doesn't support storing Exchange databases on EFS volumes.
Is the recommendation the same for Exchange 2013?
Is there any support for encrypting databases in an Exchange 2013 environment other than in transit traffic?
Thanks,
rudif

Yes Bitlocker
http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
Windows BitLocker (volume encryption)
Windows BitLocker is a data protection feature in Windows Server 2008. BitLocker protects against data theft or exposure on computers that are lost or stolen, and it offers more secure data deletion when computers are decommissioned.
Supported: All Exchange database and log files.
Supported: All Exchange database and log files. Windows failover clusters require Windows Server 2008 R2 or Windows Server 2008 R2 SP1 and the following hotfix:
You cannot enable BitLocker on a disk volume in Windows Server 2008 R2 if the computer is a failover cluster node. Exchange volumes with Bitlocker enabled are not supported on Windows
failover clusters running earlier versions of Windows.
For more information about Windows 7 BitLocker encryption, see
BitLocker Drive Encryption in Windows 7: Frequently Asked Questions.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Running setup.exe for Exchange 2013 does nothing

Hi All,
Unable to find this issue anywhere else, please excuse if it's a duplicate of another issue.
Basically, I have a new 2008 R2 server setup, added it to a domain, and want to install Exchange 2013 on this new server. There are no Exchange servers anywhere on the domain.
The server is fully up to date, including .Net 4, and looking for updates results in zero new updates found.
When I run setup.exe for Exchange 2013, a command prompt appears for less than a second, then closes, then nothing else happens.
Did a fresh reboot before trying to install, and after waiting about 20 minutes to see if anything happened after the vanishing command prompt, rebooted again, tried again, same result.
There is nothing called Exchange anywhere on the server that I can find, no setup logs or anything, and I am totally stumped.
Thanks in advance for any advice.
Michael

Hello,
Exchange 2013 need to be installed on windows server 2008 R2 SP1. If you use windows server 2008 R2 SP1, I sugegst you check if there is any exchange server via ADSIEDIT.
CN=Configuration,DC=Domain ->CN=services ->CN=Micorosft Exchange ->CN=Organization ->=Administrative Groups ->CN=Exchange Administrative Group ->CN=Servers
Here is the article for your reference.
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx#WS2008R2SP1
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

BPA for Exchange 2013 still in beta!?

Exchange 2013 is over 2 years old.
Is Microsoft ever going to release a BPA for their flagship messaging platform that's NOT in beta?

Hi,
At present, there is only a beta of Best Practices Analyzer for Exchange 2013 available. If you want to get the latest information about it, please pay attention to the Exchange blog.
For your convenience:
http://blogs.technet.com/b/exchange/
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

PowerGUI Powerpack for Exchange 2013

Is there a powerpack that can be added to the powerGUI script editor for scripting in exchange 2013?

Hi,
Based on my search, currently, there is no official document about
PowerGUI Powerpack for Exchange 2013.
However, we can connect to Exchange server using remote shell.
For more details about this, please refer to the following article.
https://technet.microsoft.com/en-us/library/dd335083(v=exchg.150).aspx
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

Antispam and AntiVirus for Exchange 2013

Dear All,
We running Exchange 2013, Would some please recommand us which antispam filter and antivirus tool is good for exchange 2013. Previously, for exchange 2010 micrsosoft has provided forfront but this has been going to disconnect any future release and
support will be stopped after 31 dec 2015. Do micrsoft have any tool for exchange 2013 for antivirus and antispam.

Hi,
You could have a look at Exchange Online Protection.
http://technet.microsoft.com/en-us/library/jj723137(v=exchg.150).aspx
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

NI-DNET support for LabVIEW 2013

We are using currently NI-DNET 1.6.6 with LabVIEW 2011. I installed now also LabVIEW 2013 on my computer and tried to sync the set of drivers with my LabVIEW 2011 installation.
Well, it seems that NI-DNET doesn't support LabVIEW 2013, at least officially. The NI-DNET and LabVIEW Version Compatibility shows that NI-DNET 1.6.6 supports LabVIEW 2011 and NI-DNET 1.6.7 supports LabVIEW 2012.
The NI System Driver Set November 2013 list NI-DNET 1.6.7 as part of the driver set. When I try to install it, there is no LabVIEW 2013 support.
My question is actually, if there is a plan to include NI-DNET support for LabVIEW 2013 or later in the driver set?
I copied the vi.lib\DeviceNet and vi.lib\nidnet directories from LabVIEW 2011 to 2013 and I can load my programs without any problems. I still didn't build an executable and didn't run them on the test fixture, but the projects can be loaded in LabVIEW 2013 without any brocken VIs. Should I expect any problems running LabVIEW 2013 with the NI-DNET 1.6.6 or 1.6.7 driver?
Nick
Solved!
Go to Solution.

I would update our drivers right away, but unfortunately the NI-Industrial Communications for DeviceNet doesn't support the PCI-DNET cards. We have probably close to 30 of those in the test fixtures. So, we need to use the NI-DNET 1.6.x driver anyway.
It will be nice if the NI-DNET installer can copy the NI-DNET VIs and supporting files to any LabVIEW version, well maybe any 201x. I hope until 2020 we can replace the old cards :-)
Nick

Configuring Lync Server 2013 to be a partner Application for Exchange 2013

Hello Guys,
I just want to share my experience while configuring Lync server 2013 to be a partner Application for exchange 2013 sever.
As mentioned on technet you need to run Configure-EnterprisePartnerApplication.ps1 script that ships with Exchange 2013.
But when I tried to run the script as described on the technet article, I found it always fails with " the accepted domain is not valid"
I have checked my accepted domains many times and i found that there's no issues with my configured accepted domain.
So I started to review the script to find the issue and I found that the script was configured as below
$acceptedDomains = Get-AcceptedDomain ;
if ($acceptedDomains -eq $null)
WriteError ("There is no accepted domain so user can not be created.")
$acceptedDomain = $acceptedDomains[0].Name;
if($UseDomainController -eq $true)
$user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
else
$user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true;
which is totally wrong as below:
firstly it makes $AcceptedDomain variable to equal the Name of the accepted domain.
Not all customers configure the name of the Accepted Domain to be the Domain Name.
Secondly it makes $AcceptedDomain variable to equal the name of the first Accepted Domain.
The first domain may be not the default Accepted Domain.
So I have configured the script as below
$acceptedDomains = Get-AcceptedDomain | ? {$_.Default -eq "True"} ;
if ($acceptedDomains -eq $null)
WriteError ("There is no accepted domain so user can not be created.")
$acceptedDomain = $acceptedDomains.DomainName;
if($UseDomainController -eq $true)
$user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
else
$user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true;
I hope This help.
Thanks
Ahmed Fouad

Hi,
This is helpful, thanks for sharing.
Best regards,
Belinda Ma
TechNet Community Support

It is there an alternative to the Test-SystemHealth powershell cmdlet for Exchange 2013?

Hello
The Powershell cmdlet Test-SystemHealth, that was available on Exchange 2010, is no longer available on Exchange 2013.
Test-SystemHealth cmdlet gathered data about the Microsoft Exchange system and analyzed the data according to best practices.
Are there any alternatives to this for Exchange 2013?
Thanks!

Haven't really played with it too much, but check out Get-ServerHealth
http://technet.microsoft.com/en-us/library/jj218703(v=exchg.150).aspx
Looks to have replaced Test-SystemHealth.

SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The virtual directory 'ecp' already exists under 'server/name'.
Parameter name: VirtualDirectoryName".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
!! And now transport service won't start and mail is unavailable !!
Any help would be appreciated.
I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

Hi,
Thanks for your response.
From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Is Windows Azure officially supported for Exchange 2013?

Similar Messages

Maybe you are looking for