Tag Info

New answers tagged

1

This happens when you're missing the .Net types Exchange uses. PowerShell remoting perfomrs some serialization that makes some objects end up as "PsObject" instead of the full strongy typed object. The solution is to install the Exchange Management Console on your client computer, this will include the .Net types you need.


1

Try this: Set-ADServerSettings -ViewEntireForest $true -WarningAction SilentlyContinue Then run the command set.


0

Same issue in our Company - we are working via a proxy server for http/s traffic and after adding the FQDN of our Exchange server into the proxy exclusion list on Chrome. Close outlook reopen and all was working again, this also fixed my Out of Office issue.


0

You may consider Exchange Server Deployment Assistance a web based application just you have to select what kind of deployment you were interested and then its provide you step-wise instructions to get this job done: However, you may also check this to understand in more details on exchange migration to office 365 via cutover migration Moreover, you may ...


0

Get-MailboxDatabase -status | Select name,whencreated,DatabaseSize,AvailableNewMailboxSpace | export-csv e:\dbinfo3.csv -notypeinformation


0

Sorry for the late response on this but I submitted a ticket with Double Take and this issue is caused because when Double-Take Application Protection creates a job, it sets the msExchOwningPFTree Attribute from the standby server (Target) to NUL. This setting is necessary for public replication between the live Exchange Servers and the standby Exchange ...


2

You need to start from scratch on Office 365 and perform a cutover migration following the detailed step-by-step instructions here. You will need to obtain a valid public SSL certificate and ensure that autodiscover and outlook anywhere (RPC over https) are correctly set up and working. You can test this at http://exrca.com. If you're unable to make this ...


0

I found this was NOT to do with the N2k file It was because I removed the mail box from Exchange server (2007) before I removed them from the groups is the DSA.MSC on one of the DC's. If you have this for a user in a group re-add them to the groups, give them a mail box, then remove from the groups and DISABLE (remove the mailbox/exchange properties from ...


2

It will never try the second server if it can connect to the server with the highest priority. It will only try the second server if it cannot connect to the first server. The error appears to be a server resource error on the other side. Most times (not always) a different MX record will point to the same server via a different network path, so hitting ...


0

Old post, but could be useful to someone else: I had exactly that trouble, and solved updating time on vmware host (and rebooting exchange). Note: time sync from hypervisor was deactivated, and exchange server (after booting up) showed no time skew with DC.


0

There is no standard practice for manually copying around Exchange transaction logs because nobody should be doing this; if you need them for point-in-time recovery after a full backup, the correct thing to do is to perform an incremental backup, which will include all transaction logs since the last backup.


0

The Backup plan is entirely dependent on what type of environment your are running. Lets assume it's a MS SQL server, since it's Server2008 and Exchange 2010 in the tags. Info on choosing a strategy: Back Up and Restore of SQL Server Databases Info on Transactionlogs backups: Transaction Log Backups A typical set-up would be a Full Backup, as is now, at 8PM ...


0

I experienced this issue recently and this was one of the only threads available on the issue so I wanted to add my comments. I also found this article, which hints that Outlook 2011 doesn't like when emails are encoded with "Windows-1252". The email I saw this issue with was in fact encoded in Windows-1252. What was strange was the e-mail source was also ...


1

On the DRsite run the following command on exchange powershell. Update-PublicFolderHierarchy -Server "DR_SERVER" If the DR server has not synchronised for a while this might be causing the error. Above will update hierarchy and might allow you then remove.


2

Install exchange on the new server Move all mailboxes to new exchange server If you installed CAS/HUB on the new servers then configure the relevant namespace and connectors Decommission the old exchange server for more details please have a look on below given links: Exchange 2010 Migration Step by Step Guide: ...


1

Uninstall all components of Exchange 2010 except for Hub Transport and Management Tools. As long as your send connector is correctly configured, server reports will go out to the internet. I'd also recommend removing the internet domain from the accepted domains list and just leave domain.local. I've migrated half a dozen SBS2011 machines to Office 365 and ...



Top 50 recent answers are included