Quantcast
Channel: Exchange Server 2013 - General Discussion forum
Viewing all 13303 articles
Browse latest View live

Licensing Ex2k13 and Ex2k16 coexistance

$
0
0

Hi,

customer uses now Ex2k10 and during usage have bought 80 Ex2k13 CAL per user.

As Ex2k10 is near end of support - he want to migrate to mixed Ex2k13 and Ex2k16 env (as for 80 users he has CAL's already).

So 80 users will have mailboxes on Ex2k13 and rest of them (400) will have mailboxes on Ex2k16 (will buy 400 CAL's). The Ex2k13 will get only mailbox role.

So my question is - can he use existing CAL's in that scenario or have to buy 2016 CAL's for every user (as Client Access runs on Ex2k16).

Regs

Jarek


JD


Public folder mailbox size

$
0
0

Hello,

I moved some public folders branches from one PF mailbox to another one. However, after the move, the size of the source public folder mailbox didn't change. Is there some command that I have to execute in order to shrink the source public folder mailbox, or is it something that will be done automatically after certain period of time (e.g. RetainDeletedItemsFor, etc.).

Likely also ItemCount didn't changed, however I didn't noted this number before the move.

Thanks!

Vaclav

Management Tools install failed -- can't reinstall and can't uninstall

$
0
0

Hey all, I'm trying to install Exchange 2013 Management Tools on my Windows 10 workstation and I've hit a snag. The install failed the first time because I had to add IIS Management Console, IIS 6 Management Console, and IIS Metabase Compatibility. I installed them, restarted the installation, and then it failed with with this error:

-------------------------------------------------
Prerequisite Analysis                                          FAILED
A Setup failure previously occurred while installing the AdminTools role. Either run Setup again for just this role, or remove the role using Control Panel.
-------------------------------------------------

I can't run the Setup again because it fails with the same message as above. When I try to remove the failed install by using Control Panel I get this message:

-------------------------------------------------
Error An incomplete installation was detected. Run setup to complete Exchange installation.
-------------------------------------------------

Well, I can't get past the install error and I can't get past the uninstall error. Any ideas on how to get the Management Tools installed or uninstalled? I even tried it using Safe Mode but I'm getting the same error message.

Thanks,

Joe B

Report that shows what restricted meeting rooms user has access to

$
0
0

good day

i need to replicate the permissions for one user but first need to export a csv that shows what rooms UserA  has permission to book. Am wandering if anyone has a good 1 liner for this?

My Emails is hanged via Exchnage 2013 sever

$
0
0
i have 2 exchange server 2013 was hosted in 2 hyper V machines , recenlty i faced an issue for recieving emails , somtimes i didnt get the emails till restart the active server and swapped to the passive one , then i can receive the pending emails , please advice in this issue.

Exchange 2013 Standard + Enterprise Licenses in Same Organization?

$
0
0

Background:

I've been tasked with my company's migration from Exchange 2010 to 2013. In coming up with viable scenarios, I've pulled our license data to see what we're licensed for. We appear to have one Exchange 2013 Standard license, one Exchange 2013 Enterprise license, and 250 CALs of both Standard and Enterprise types. 

In our current 2010 deployment, we have a dedicated CAS server and two DAG servers. We're broadly trying to simplify our server landscape, and in reading recommendations for deployment, I see that mixed-role servers are recommended. My intention is to deploy two mixed-role servers with round-robin DNS allocating connections between them and databases duplicated on both. We have a little less than 250 users, which fits with the CALs (my understanding is that those aren't a total of 500 CALs, but rather that the 250 enterprise CALs "upgrade" the 250 standard CALs). 

My questions:

  1. Can I deploy two mixed-role servers using the two Exchange Server licenses (one Standard and one Enterprise) that I have?
  2. Should I, for simplicity, install them both as Standard, and is that covered by the licensing (i.e. can an Enterprise license "fall back" to cover a Standard installation)? I realize that this will limit me to five databases, and I'd also lose any benefit of the Enterprise CALs.
  3. If I have to install them as their specific editions (one enterprise and one standard), will they coexist fine, and will round-robin-ing between them cause inconsistent user experiencing depending on which a user connects to? 
  4. If the answer to #2 is "no that's not covered" and the answer to #3 is "no, it would be bad", Would an old-style deployment scenario where we use the Standard license to cover a CAS-only server and the Enterprise license to cover a mailbox server enable us to have >5 mailbox databases (even if we still lose the functionality of the enterprise CALs)?
  5. Is there something else about this that I'm missing?

Many thanks in advance for your help!


Save Sent Item to User created folder on a shared mailbox

$
0
0

Hello All,

We have some users in our company who are using shared mailbox to send and receive emails

They want to use the function "Save Sent Item to" to save the sent email in a folder created in the shared mailbox

They can choose the folder but the email is not saved in the specific folder that they want but we can see it in the Sent items folders of the shared mailbox and the user mailbox

I checked some forum before and all i can find is to activate the options MessageCopuForSendOnBehalfEnabled and MessageCopyForSentAsEnabled

Those two parameters are actuelly configured as true and still not working

Someone has already had this type of issue ? Some ideas on how resolved it ? Is it even possible to do what they request ?

Autodiscover Certificate Error on Shared Auto-mount Mailboxes

$
0
0

I'm trying to clean up Autodiscover a bit in our org to get away from using large SAN certs, and creating SRV records for any non-domain-joined machines to find the autodiscover server. We don't have external clients using Autodiscover, so for now I'm just focusing internally.

With our domain-joined computers when users auto-configure their own mailbox, the SCP lookup is successful and Outlook configures with no issues. No problem there.

However, when a user has other shared mailboxes auto-mounted within Outlook, certificate errors still appear. Does SCP not work for shared mailboxes? I've deleted all autodiscover.<emaildomain> entries and created the corresponding SRV records. However, we have some domains with wildcard DNS entries on *.emaildomain, so I still need to track these down to make sure that these resolutions return a 404 so that it uses the SRV record instead.

Anyway, the thrust of my question: Do auto-mounted shared mailboxes not use SCP?


Exchange Server 2013 - Installation Issue

$
0
0

Whenever I get to the Mailbox role: Transport service part of the installation, I am presented with this error:

Error:
The following error was generated when "$error.Clear(); 
          $vdirName = "PowerShell";
          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";
          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";
          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath+ "ClientAccess\PowerShell-Proxy");
        " was run: "System.ArgumentException: The AD configuration for virtual directory 'PowerShell' already exists in 'CN=PowerShell (Default Web Site),CN=HTTP,CN=Protocols,CN=SERVER,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=LMG,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=example,DC=com', please remove this AD configuration manually.
Parameter name: VirtualDirectoryName
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

It would be a great help if someone could help me fix this issue.

Thanks

Alex

Issue: Share calendar between exchange on-premises(exchange 2013) and exchange online in hybird enviroment

$
0
0

Currently, We have an issues:

User on Exchange on-premises can see calendar users on the Exchange online, Nevertheless the user on exchange online can NOT see users on Exchange on-premises. We used tool via this url https://testconnectivity.microsoft.com to check autodiscovery

with the result that there's no problem (the user on exchange online can see users on Exchange on-premises).

On Outlook-app we use Fiddle Tool to trace log (image1). 

Base on log, we realize that Autodiscover had tookEWS( Ex: https://mail.contoso.com/EWS/exchange.asmx) of users on-premises. But in next step it uses [outlook.office365.com/EWS/exchange.asmx] instead of using [https://mail.contoso.com/EWS/exchange.asmx], so that there's no information calendar of user on-premises.

 

Need to change DAG witness server

$
0
0
I am running an Exchange 2010 environment with 2 exchange servers.  I have a Database Availability Group setup so if one server goes offline the other server can pick up the slack.  The system that I am using as the DAG witness server is an older Windows 2003 server that I need to decommission.  So I need to move the DAG witness server to another system.  How do I go about doing this?  Or, what is the best way to do it?  Can I just setup the folder share on another server then go into EMC and change the witness server and Apply and OK?  Or is it more complicated than that?  thanks

EXMON

$
0
0

Hello,

   I have a customer who is still using Exchange 2007 on Windows Server 2003, I know they are doing it wrong since there is no support from Microsoft but on the other hand they are in Financial Crisis and would be moving to Office 365.

I need to troubleshoot the server using EXMON and I cannot find it, can any one help me finding it or share a link to download as its not present on Microsoft.

Thanks

 


http://www.arabitpro.com

Exchange 2013 CU22 and CU23 are failing during prerequisite check

$
0
0

Currently running EX 2013 CU 21 on Server 2012 R2

After installing .net 4.7.2 and trying to run CU22 or CU23 from the elevated command prompt I get the following errors. 

I verified that the account I am executing the setup.exe is a domain admin with memberships in enterprise admin group and  organization Management group in exchange.

The Mailbox and CAS server roles ARE in fact installed on the server I am trying to run the update on.

Error:
The Mailbox server role isn't installed on this computer.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UnifiedMessagingRoleNotInstalled.aspx

Error:
The Mailbox server role isn't installed on this computer.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.BridgeheadRoleNotInstalled.aspx

Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx

Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx

Error:
Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master.  Run setup with the /prepareAD parameter on a computer in the domain MYDOMAIN and site REMOTE SITE, and wait for replication to complete.  See the Exchange setup log for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx

Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx

Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx

Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx

Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx

Any help is appreciated. 




Exchange 2007 Server and Log Parser Query

$
0
0

Hello,

    I need to run this query on Windows server 2003 x64 using logparser but I cannot as it ends up the error

Logparser.exe  "Select TOP 5000 TO_TIMESTAMP(TO_DATE(date), TO_TIME(time)) as [Time],
cs-username as [User],
cs(user-agent) as DeviceID,
TO_INT(EXTRACT_PREFIX(EXTRACT_SUFFIX(cs-uri-query, 0, '_RpcC'), 0, '_')) As RPCCount,
sc-status as Status,
sc-substatus as SubStatus,
sc-bytes as [Bytes],
DIV(sc-bytes, 1024) AS [KBytes], time-taken, DIV(time-taken, 1000) as Sec, cs-uri-query
FROM 'C:\Windows\system32\LogFiles\W3SVC1'
WHERE
RPCCount > 2000 /* <-- Change RPC count as needed */
AND cs-uri-query LIKE '%Cmd=Sync%'
AND cs-uri-query LIKE '%Ty:Co%'
ORDER BY [Bytes] DESC"

https://support.microsoft.com/en-us/help/2711053/high-cpu-usage-when-you-synchronize-a-mobile-device-to-an-exchange-ser

C:\Program Files (x86)\Log Parser 2.2>LogParser.exe "Select TOP 5000 TO_TIMESTAM
P(TO_DATE(date), TO_TIME(time)) as [Time],
Error: Syntax Error: <field-expr>: cannot find a valid <field-expr>: ''


http://www.arabitpro.com


Exchange DateBase on a nework drive

$
0
0

Can we create an exchange database on a network share folder drive? Can we use Symbolic link to resolve it by using MKLINK utility?

We don't want to build another Exchange server. It will cost more money. 

Please let me know? Thanks

Louis


Timeout when managing inbox rules on shared mailbox

$
0
0

Problem: When a user manages a shared mailbox they have access to they get 'Operation could not be performed at this time' when creating a inbox rule on the shared mailbox.

This is what is displayed in the application event log:

Log Name:      Application
Source:        MSExchange Control Panel
Date:          6/22/2016 10:41:39 AM
Event ID:      33
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      EXCH13MBX03.domain.com
Description:
Current User: '"currentuser" on behalf of "sharedmailbox"'
PowerShell exception 'Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException' is translated to string 'The operation you requested couldn't be performed at this time. Please try again later.'.
Original message is: 'Cannot open mailbox /o=pathtosharedmailbox.

This is happens with multiple users and multiple shared mailboxes at specific locations.



Can the built-in domain administrator account be synced for email in a hybrid on prem exchange to office 365 email?

$
0
0

I have  a client that we are migrating from exchange 2013 on prem to office 365.    They use the built-in administrator account for emailing for a number of groups and don't want to change that.    The office 365 system is the mx so all emails flow through it for antispam reasons.   

The administrator account is in an OU that is configured for AD sync but it does not show up in the list in office 365 although all the other names are there so I'm guessing either it can't be synced or I'll have to edit something about the account.   Any email will get a bounce and at least part of that reason is it doesn't sync that account as far as I can see.

CO1NAM11FT028.mail.protection.outlook.com rejected your message to the following email addresses:<o:p></o:p>

administrator@mydomain.com
A communication failure occurred during the delivery of this message. Please try resending the message later. If the problem continues, contact your helpdesk.<o:p></o:p>

CO1NAM11FT028.mail.protection.outlook.com gave this error:
Recipient address rejected: Access denied [CO1NAM11FT028.eop-nam11.prod.protection.outlook.com]
<o:p></o:p>

Critical Error running Exchange Console 2010 on a Windows 10 PC - Can no longer view mailbox properties

$
0
0

I believe this is a recent development.  I run the Exchange Console snap-in from my desktop and I can scroll through the mailboxes, take all sorts of actions, but I cannot right click and select properties - I get a critical error.  If I take the same actions on the Exchange server itself - it operates normally. 

Is there a fix?

Here's the error message:

Microsoft Corporation
Microsoft® Windows® Operating System
10.0.18362.1
Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentException: Cannot bind to the property or column CountryOrRegion on the DataSource.
Parameter name: dataMember
   at System.Windows.Forms.BindToObject.CheckBinding()
   at System.Windows.Forms.Binding.SetListManager(BindingManagerBase bindingManagerBase)
   at System.Windows.Forms.ListManagerBindingsCollection.AddCore(Binding dataBinding)
   at System.Windows.Forms.BindingsCollection.Add(Binding binding)
   at System.Windows.Forms.BindingContext.UpdateBinding(BindingContext newBindingContext, Binding binding)
   at System.Windows.Forms.Binding.SetBindableComponent(IBindableComponent value)
   at System.Windows.Forms.ControlBindingsCollection.AddCore(Binding dataBinding)
   at System.Windows.Forms.BindingsCollection.Add(Binding binding)
   at Microsoft.Exchange.Management.SnapIn.Esm.Recipients.AddressAndPhonePropertyControl..ctor(String layoutXML)
   at Microsoft.Exchange.Management.SnapIn.Esm.Recipients.AddressAndPhonePropertyControl..ctor()
   at Microsoft.Exchange.Management.SnapIn.Esm.Recipients.ShowMailboxPropertiesCommandAction.GetMailboxPropertyPageControlsPerContext(AbstractRecipientsResultPane recipientsResultPane, DataContext mailboxContext, RecipientTypeDetails recipientTypeDetails)
   at Microsoft.Exchange.Management.SnapIn.Esm.Recipients.ShowMailboxPropertiesCommandAction.GetPropertyPageControls(Boolean bulkEditing)
   at Microsoft.Exchange.Management.SystemManager.WinForms.ShowSelectionPropertiesCommandAction.ShowPropertySheetDailog(String propertySheetName, String dialogNamePrefix, Boolean bulkEditing)
   at Microsoft.Exchange.Management.SystemManager.WinForms.ShowSelectionPropertiesCommandAction.OnExecute()
   at Microsoft.ManagementGUI.Commands.Command.OnExecute(EventArgs e)
   at Microsoft.ManagementGUI.Commands.Command.Invoke(EventArgs e)
   at System.Windows.Forms.MenuItem.MenuItemData.Execute()
   at System.Windows.Forms.Command.Invoke()
   at System.Windows.Forms.Control.WmCommand(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ListView.WndProc(Message& m)
   at Microsoft.Exchange.Management.SystemManager.WinForms.DataListView.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   --- End of inner exception stack trace ---
   at Microsoft.ManagementConsole.Internal.SnapInMessagePumpProxy.OnThreadException(Object sender, ThreadExceptionEventArgs e)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at Microsoft.ManagementConsole.Internal.ConsoleDialogHost.ShowDialog(WaitCursor waitCursor, ShowDialogCallback callback)
   at Microsoft.Exchange.Management.SnapIn.SnapInUIService.OnShowDialog(Form form)
   at Microsoft.Exchange.Management.SystemManager.WinForms.UIService.ShowDialog(Form form)
   at Microsoft.Exchange.Management.SnapIn.Esm.Recipients.FindCommandAction.OnExecute()
   at Microsoft.ManagementGUI.Commands.Command.OnExecute(EventArgs e)
   at Microsoft.ManagementGUI.Commands.Command.Invoke(EventArgs e)
   at Microsoft.Exchange.Management.SnapIn.CommandActionAdapter.action_Triggered(Object sender, ActionEventArgs e)

mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.ManagementConsole, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
MMCFxCommon, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Management.SnapIn.Esm, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management.SystemManager, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Common, Version=14.3.214.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.ObjectModel, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Data.Directory, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Numerics, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Drawing.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
WindowsBase, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Net, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Core.Strings, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Xaml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Runtime.Serialization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.Exchange.Extensibility.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Management.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.DirectoryServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.HelpProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Common.IL, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Isam.Interop, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.UserInterface, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.ActiveDS, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.adsiis, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.Migbase, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.DKM.Proxy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.AirSync, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Approval.Applications, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.CabUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Cluster.Replay, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Compliance, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.ApplicationLogic, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Mapi, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Providers, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Storage, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.DatacenterProviders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.InfoWorker.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Live.DomainServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MailboxReplicationService.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessageSecurity, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessagingPolicies.Rules, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.Native, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.StoreProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.AntiSpam.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.SenderId.Core, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Logging.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Worker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.TroubleshootingTool.Shared, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.UMCommon, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.RightsManagementServices.Core, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.ExSearch, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
MSExchangeLESearchWorker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Transport, Version=14.3.214.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Xml.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Accessibility, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Sqm, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
MMCEx, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

Disk cleanup suggestions

$
0
0

Hyper_V server 2012R@ _ exchange

Mobile access

10 users, 3 active, others sporadic

What areas should I look at to cleanup disk usage. I have a180GB disk partition for the s Exchange server. I monthly purge log files. 

Only 2 very active users yet I show only 11 GB free on virtual disk.

Before I add more space, are there some areas I should look at to reduce disk space. This seems to be an awful large use of disk space for so few users. 

Thanks


John Lenz

AD Lockout - Exchange 2013 - Office 365 Hybrid

$
0
0

About a month ago we started having an issue where 2-3 users would get their AD accounts locked out. We have our AD lockout set to 30 attempts in 60 minutes, so any lockouts are likely software issues not user mistakes. We installed a trial of Netwrix auditor. According to that, we have a pair of users, incidentally with the same first name, that have gotten locked out 3 times within 5 minutes of each other. These incidents happened 10-12 days apart. In addition to them, we've had a total of 5-10 users affected.

 

Netwrix shows that the lockouts originated from our local Exchange 2013 server. We have migrated all mailboxes to Office 365, but are running in hybrid mode for AD and Exchange. We have to keep the local server for managing mailboxes, otherwise I would get rid of it. I got into the Exchange server and ran Exmon. We have a few accounts (less than 10) that showed up as connecting. Most of them had a username that was just an SID (or something that looked similar). None of the affected users showed up there.

I checked the IIS logs on the Exchange server at "C:\inetpub\logs\LogFiles\W3SVC1\" and there are a lot of Autodiscover requests from the users that have issues as well as other users that don't have issues. Sometimes the client would run Autodiscover 6 times in an hour for 6-7 hours, then it would go silent for a long while. I don't see any errors or failed logins at least not with the username's in question.

 

Line 2932:
2019-10-22 14:42:40 <Local Exchange IP> POST
/Autodiscover/Autodiscover.xml&CorrelationID=<empty>;&ClientId=KBYKWTJKYERIIVUBQA&cafeReqId=83913601-bc0d-49e7-aba3-654d096d3301;
443 <domain\username> <user machine IP>
Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.4266;+Pro) - 200
0 0 62

Most of our clients are still running Office 2016 MSI edition 32bit. Though one of the affected users is on a domain joined Mac.


Is there another log that I can check to look for the source of this issue? Or is there something else I should try?

Viewing all 13303 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>