Due to security requirements, our Exchange 2013 servers are non-internet facing. IPs will only route internally.
Is there a way to download/update the built-in 2013 Anti-malware product definitions on a regular basis?
I can't find anything regarding configuring an internet facing repository server or someone's custom scripts to accomplish this.
We do have SCCM in our environment as well if that can be leveraged in 2013.
Any and all help is appreciated!
Thank You,
Chris
Hi all,
I did New-MailboxExportRequest -Mailbox ... -FilePath \\....pst from working instance of Exchange 2010 and tried to Import that PST file into Exchange 2013 using Shell. As usual there was Alert that Import PST of mailbox has been queued. It was started by me, etc ...
Few hours later I ran Get-MailboxImportRequestStatistics -Identity test\mailboximport and found StatusDetail=FailedMAPI, PercentComplete=69
Because I'm going to migrate about 30 mailboxes in similar way, could you clarify what the problem is it and how to avoid it?
Thanks,
P.S. another attempt using PowerShell to Import same PST finished on 10% with FailedMAPI (or FailedOther???). Also how to figure out which user\mailboximport??? number relates to specific Import process?
Image may be NSFW.
Clik here to view.
Hi all,
I assume it's okay to post Exchange 2010 questions in here? If not sorry, anyway...
We currently run Exchange 2010 SP2, I've been reading about how to upgrade to SP3, but I still have a few questions.
1. 90% of our users just use OWA. Does SP3 change the requirements at all as far as browsers that are compatible with OWA?
2. We use Managed Folder Mailbox Policies (rather than the new Retention Policies), that can only be configured through the command line. Does SP3 still support Managed Folder Mailbox Policies?
3. If already running SP2, is there really any reason NOT to got o SP3?
Any help is appreciated, thanks.
Error:
The following error was generated when “$error.Clear();
if (Get-Service WMSVC* | ?{$_.Name -eq ‘WMSVC’})
{
Set-Service WMSVC -StartupType Automatic
Start-SetupService -ServiceName WMSVC
}
” was run: "Falha do Serviço 'WMSVC' ao atingir o status 'Running' neste servidor.".
Installed on a Hyper-V (2012 Server). I would love to move exchange do a Phisical server but i must uninstall this one first! :-/
any ideas!?
[]´s Walter Ferry Dissmann
Upgraded Lotus Notes version into newer 8.5 it has complex functionalities. These functions are not easily graspable and it takes long time to understand, I decide to export my data into another (MS Outlook) platform, is it possible, I want new updates about conversion in cost-effective manner. And if yes then suggests me the way?
Hi,
I am in the process of migrating our users from Exchange 2003 to Exchange 2010. I have done 5 so far, and hit an issue.
Server is a fresh install of Windows 2008 64 bit- Fully updated
Exchange is 2010 Standard - SP2 and updated
The Server is running 8 gig of ram.. and CPU / performance levels are minimal at 1 - 2% cpu. Memory usage is a consistent 4.64 Gig... it never changes
The issue i am having is that when a user connects in Cached mode in outlook ( tried 2007, 2010 ) "Updating this folder" is displayed for a very long period of time, before new emails come in. This happens evey time outlook is restarted.. Times vary, but generally its at least 3 minutes... It took 7 minutes for one user to start and recieve their email...
The update time on Exchange 2003 was 20 seconds, so its very noticable and users are complaining.
Without Cache mode, emails are instant, but again, the send / recieve bar along the bottoms sits there, at about 50% for 3 - 7 minutes, although emails do come in quicker..
It doesnt seem like a network speed issue, as ive done a few tests and the server connection is fine.
Any ideas ?
Thanks
Hi
Our MS Exchange 2010 is installed on Domain controller (Server A windows 2008R2). Now we have procure another server for dedicated DC(server B) and we will depromt DC role from server A.
Dose this process effect Exchange? What are prerequisite for this?
MaST MaX
Hey everyone,
I'm trying to installing Exchange Server 2010 and when I hit the install of the "Hub Transport Role" I get this error:
The following error was generated when "$error.Clear();
if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
{
Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
}
" was run: "The property 'RMSComputerAccounts' is on a read-only object and can't be modified.".
Any thoughts or ideas on how to fix this? I know it has something to do with the Active Directory Rights Management Services but I'm not sure how to grant write privileges to what I need.
Federation or Auth certificate not found: xxx. Unable to find the certificate in the local or neighboring sites. Confirm that the certificate is available in your topology and if necessary, reset the certificate on the Federation Trust to a valid certificate using Set-FederationTrust or Set-AuthConfig. The certificate may take time to propagate to the local or neighboring sites.
We have a hub spoke DC setup with primary data center and than multiple sites all sites have a GC DC .. When my exchange 2013 servers does the AD Site Scan it only bring back the DCs in the primary DataCenter and one Site, 2010 would show all sites in the log files .. Am I missing something do I need to setup the Fed / Auth Cert ? And if so whats the best way?
David Ulrich
Hi all, I have following scenario to plan for and implement:
- I have Exchange 2007 set on old server that I want to replace for my domain. Current server server as both mailbox and edge transport. New Exchange will also be 2007 (iirc main real benefit of 2010 is better handling of large mailboxes on slower drives).
- We have acquired a company, with completely separate domain; I want to [eventually] set up on my Exchange.
- That company currently has front-end/back-end model set up (with DMZ). They are on Exchange 2003.
- They will stay within their own domain bounds for now, but are dependant on our infrastructure and eventually will be absorbed into my domain.
What should be my approach for deployment of new Exchange? The idea is, that I'm deploying the new Exchange, migrating my users in my domain to it, then at some point (rather sooner than later) I'm bringing new company to it. Until then they are working on the old Exchange, on their old server(s). Obviously I mean I want to have new domain's AD connected to new Exchange.
I've read a bit here and there and I guess I should set up new domain as a part of the forest, prior to setting up new Exchange. Is that enough? Or are there some initial setup requirements on the Exchage I need to take care of? Does it impact my domain or their domain's ability to work on old servers?
I have also a related question about AD migration - both domains are single domains within their own forests; this still requires running the ADMT, correct? There is no way of transferring whole domain, intact, including naming (well, maybe making minor change to the domain name), etc.?
Thanks,
Cris
Hello all,
I have installed 2 exchange 2013 servers (1x Client Access, 1x Mailbox) in an existing 2010 SP3 environment.
This migrated mailbox cannot be accessed by OWA nor by Outlook 2013 clients. Get-Mailbox does show the mailbox in the new 2013 database.
How can I troubleshoot this?
Regards,
Stephan van der Plas
You know you're an engineer when you have no life and can prove it mathematically
I have a hybrid setup with on premise 2010 SP3 to O365 Wave 15 and on premise 2013. I am getting close to having all mailboxes moved off of 2010 and either into the cloud or onto the on premise 2013 server. Once this process is complete, how do i decommission the 2010 server and move the hybrid config to 2013? I have tried to run the hybrid config wizard on 2013 to upgrade the hybrid, but it fails with the error "ERROR : Subtask Configure execution failed: Upgrading hybrid configuration from Exchange 2010...No Inbound connector found on the Office 365 tenant. at Microsoft.Exchange.Management.Hybrid.UpgradeConfigurationFrom14Task.UpgradeFopeConnectors(ITaskContext taskContext) at Microsoft.Exchange.Management.Hybrid.UpgradeConfigurationFrom14Task.Configure(ITaskContext taskContext) at Microsoft.Exchange.Management.Hybrid.Engine.ExecuteSubStep(String subStepName, ITaskContext taskContext, ITask task, Func`3 substep, Func`4 createException, Boolean throwOnFalse)"
There is an inbound connector in our O365 tenant that was upgraded from FOPE to EOP by the Wave 15 upgrade. Our hybrid config works. I want to make sure that it continues to work after i decomm the 2010 server. My final intent is to maintain our on premise 2013 server in hybrid config with our O365 tenant as i have some mailboxes that need to remain on premise.
I've been searching the past two days and reading a lot, and I still have some questions about the best next steps in our migration. We have a very simple 1 server Exchange 2010 environment (Server 2008 R2 in Hyper-V) with a Barracuda device sifting email before delivery. I installed Exchange 2013 as a new Server 2012 Hyper-V VM after reading the guides and making sure we have Exchange 2010 SP3 and installing Exchange 2013 CU1. Things are fine so far, but unfortunately we have the "Ambiguous URL" situation discussed in this article:http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx
I have enabled Outlook Anywhere on 2010 for all connections (fast/slow) using the method suggested in the article.
I have not fully configured all the URLs on 2013 yet since I don't know the full effect it might have.Currently,"mail.domain.com" is just a CNAME pointing to "exch2010.domain.com" and all URLs on 2010 are using that FQDN.
I'd like to update things so that we are using recommended values for the CAS and everything else, and I'd like "mail" to be used in the URLs for client access (OWA, IIS) so this isn't such a headache next time. I think my next step should be to change the URLs on 2010 to use "mail.domain.com" instead of the FQDN and then set up "mail.domain.com" on 2013 as well before eventually repointing "mail" in DNS.
Does that sound right? Should I expect any difficulties or temporary outages for users in Outlook or on mobile devices?
Hi All,
My current enviroment consists of 1 - 2003 Enterprise server as the DC with Exchange 2003 installed on the same machine and it has shares for file storage. This server also has 2 network MFP printers that are shared.
I have another 2003 Enterprise server thats a member server and it's only purpose is to support 1 mission crital application and has some shares for file storage.
I want to install on a new machine 2008 R2 Enterprise server as the DC and the other new machine install another 2008 R2 server as a member for Exchange 2010 only. On another Machine install 2008 R2 as a member for the mission critical application.
What is the best resaonable course of action to migrate from the 2003 servers to 2008 R2 servers. I googled on this type of setup and I only found a couple things, but it did not help. Should I begin by migrating the DC first, transfer the FSMO and then join the Exchange server as a member to the new DC and migrate from exchange 2003 to 2010, then demote the 2003 server?
If anyone knows of some type of step by step instructions on this type of senerio somewhere on the net or MS website to help the best way to migrate this, it would be greatful. Or even can provide there own steps for the best practice of this type of migration.
Thanks
BTW, I thought I was in the section of the forum that was for Exchange 2010. However, the only choices I had was for Exchange 2013. My appoligies for posting this here, I could not locate one in the list of forms to post it in. If a moderator see this, Please post it in the right section if this is an inappropraite forum.
Mailbox role: Unified Messaging service FAILED
The following error was generated when "$error.Clear();
$lochost=hostname;
$ums=Get-UMService -Identity $lochost -DomainController $RoleDomainController;
Set-UMService $ums.Identity `
-DomainController $RoleDomainController `
-IrmLogPath ($RoleInstallPath + "\Logging\IRMLogs") `
-IrmLogMaxDirectorySize 262144000 `
-IrmLogMaxFileSize 10485760 `
-IrmLogEnabled $true
" was run: "The term 'hostname' is not recognized as the name of a cmdlet, function, script file, or operable pr
ogram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.".
The following error was generated when "$error.Clear();
$lochost=hostname;
$ums=Get-UMService -Identity $lochost -DomainController $RoleDomainController;
Set-UMService $ums.Identity `
-DomainController $RoleDomainController `
-IrmLogPath ($RoleInstallPath + "\Logging\IRMLogs") `
-IrmLogMaxDirectorySize 262144000 `
-IrmLogMaxFileSize 10485760 `
-IrmLogEnabled $true
" was run: "Cannot convert 'System.Object[]' to the type 'Microsoft.Exchange.Configuration.Tasks.UMServerIdParam
eter' required by parameter 'Identity'. Specified method is not supported.".
During a mailbox migration from Ex2010 to Ex2013, the Ex2013 server shut down unexpectedly. The database cannot be mounted anymore. About half of the mailboxes have completed the move to the Ex2013 database.
I've ran ESEUTIL /mh and it showed the database was in dirty shutdown state. Running ESEUTIL /r supposedly was successful, but the database still is in dirty shutdown state.
Because this happened the migration batch was running there was no backup of the Ex2013 database (would've run back up after the migration completed). The only backup we have is of all the mailboxes on the Ex2010 database before the migration batch was started.
Would there be any issues restoring the Mailboxes that were already moved to Ex2013 with backup from when those mailboxes were still on Ex2010?
Andrew Shin, TechNet Forum replies
Hello good morning, i need help, i need to migrate two diferente exchange servers (2007 and 2010) into a third fresh server, the two exchange servers have different AD structures and both host email mailboxes from different domains, i want to migrate them into one exchange server 2013, anyone has an idea on how to perform this?
Hey there
I have a Small Business Server 2011 with Exchange 2010 SP3 installed. As with the release of Exchange Server 2013 CU1 I want to migrate to 2013. I am following a technet blog post (http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx) to migrate Cross Org and Cross Forest. This is what I do:
Prepare-MoveRequest: works like a charm, user gets created in target forest and shows up in 2013 Mailbox Migration Console ("Migrate to this forest") in ECP.
Second I try to migrate the mailbox:
New-MoveRequest -Identity "DN or UPN of User in Target Forest" -RemoteLegacy -TargetDatabase "Mailbox Database Name" -RemoteGlobalCatalog"FQDN of Source DC" -RemoteCredential $remote -TargetDeliveryDomain "Target domain name"
The output is the following:
RemoteLegacy moves must involve Exchange 2010 or lower versions only.
I understand that this used to happen without SP3 and CU1, but why would I still get this message after upgrading? I also tried to move the mailbox from the other side (legacy exchange server):
New-MoveRequest -Identity "UPN" -Outbound -Remotehostname "TargetMailServer" -RemoteTargetDatabase "DB" -RemoteCredential $remote -TargetDeliverydomain "domain"
Output is the following:
The remote server doesn't support client 'legacy exchange fqdn' version (14.3.123.2 caps:05FEFF). Missing functionality: 'TenantHint'.
This confuses me. SP3 should be 14.3.123.4 (which is the version for all server roles in EMC).
Any idea why this happens?
Hello Everyone,
System Information:
Exchange 2013 - and ADDC (separate server) - Windows 2012
Outlook 2010 clients
Widnows XP SP3 (client)
Background:
Just configured Exchange and DC (separate server). I mostly ran default settings for Exchange 2013 but put logs on separate drive. I was able to access OWA no problem.
I can ping and I can resolve exchaneServer.xxx.local domain name.
Problem:
I am having a problem with Outlook not being able to create a mailbox.
Image may be NSFW.
Clik here to view.
I tried several accounts but they also how the same issue. I also tried several desktops (in and outside of the domain)
Our current setup has a CAS and HT split vs. installed on one server. We only process about 100 emails/hour and have 150 employees. Is there any reason to have them split?
Is there any way to combine them on the same server again without having to reinstall everything?
Would it be better to install a third server with everything on it and then move the parts over that I want?
Thanks!