System is SBS2011 / Exchange 2010. Email to one address is delayed then fails with #550 4.4.7 Queue expired. DNS finds the domain name correctly, we can telnet to their mail server and connect, any suggestions on how to diagnose? Thanks.
Jack Drose
IT Portfolio
Jack - IT Portfolio
I am curious how exchange 2013 and beyond handle space usage for single messages going to many recipients.
For example, if I send 1 10k message without an attachment to 100 recipients all on the same database, does Exchange count each message separately towards storage usage? For example, would the total storage used in the database be 1000KB (~1MB) or would it only be 10k?
What if there is an attachment? If I sent the same 10k message to 100 recipients, but this time I attached a 10MB file, would Exchange store 100 copies of the attachment? Therefore using 1GB of storage, or would it only use 10MB of storage?
What if the same two scenarios above occur, but 50 users are on one database and 50 users are on another?
thanks
When I try to customise the status bar, quota information is showing as "off". Ticking that option make not difference
Hello everybody,
i have an exchange 2010 SP1 Domain in hosting mode with several tenants, the target is remove this server.
I've created a new forest with Exchange 2013 and i have full trusted the two domain with the appropriate security permissions in the Exchange groups. I would like to keep temporally the 2010 as proxy (with CAS) to authenticate users by it let them access to their mailboxes hosted in the 2013.
I tried to move a test mailbox owned by a test tenant named mega.fi with the following command script:
Prepare-MoveRequestHosting.ps1 -Identity test-mega@mega.fi -RemoteForestDomainController s-dc01.scorp.local
Of course i input the correct credentials of the remote domain but i receive constantly this error:
C:\Users\Administrator\Desktop\Prepare-MoveRequestHosting.ps1 : Error looking up source MBX test-mega@mega
forest.
At line:1 char:33
+ .\Prepare-MoveRequestHosting.ps1 <<<< -Identity test-mega@mega.fi -RemoteForestDomainController s-dc01.
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Prepare-MoveRequestHosting
It doesn't find the test-mega@mega.fi mbx and cannot understand why or it cannot write in the remote forest?
Where is the error with my command? I'm using an Admin users which got all permissions on the Host Organizations
These problems a part:
Which is the best practice to move the tenants mailboxes to Exchange 2013 in order to use Ex2010 CAS server as proxy and use the mailboxes hosted in the new domain?
Thanks you a lot
Hi,
I bought a new certificate (Wildcard).When I am creatingEDGE subscription:
New-EdgeSubscription : Edge subscription only supports Cryptographic API certificates. The default certificate with thumbprint ****************** for this subscription isn't a CAPI certificate. Use
Enable-ExchangeCertificate -Services SMTP to set a CAPI certificate as the default certificate.
EDGE 2013 CU15
Who can help ?
How to remove permission on public folder (and subfolders) to all the users?
Script demands from you to to select a user, but how could you do this for all the users?
With best regards
bostjanc
Yasser
New to Audit logs and just noticed a bunch of failures with a bunch of random Account Names that don't exist and coming from a workstation that does not exist on our network.
Account names are for example. FTpuser, operator, test, POS, cashier, Restaurant, etc. (none of these exist on our network)
-Only thing I have determined is it's not coming from our FTP server. If anyone can shed some light on this that would be great!
------------------------------
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: POS3
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: Windows7
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Hello
User want get login history as login owa , outlook . I try command Get-LogonStatistics but seem it not support exchange 2013
Please everyone suggest help me another way
Thanks
Tien
Hello
Can you please let me know, which protocol is used to communicate between two mailbox server, Two CAS servers, Two Hub Servers or mailbox to CAS or Mailbox to HUB or HUB to CAS.
Even same in Exchange 2013 as well,
I want to know which protocol is being used to communicate between two servers in exchange.
Hi
We have windows server 2012 R2 and installed Exchange server 2013 (Build 1044.25).
We have 2 CAS servers and 2 MBX servers. Suddenly one of my one MBX-02 server is hang up and we shutdown for 30 minutes. We checked ccsetup service stopped mode and showing automatic in services panel.
after bring up the server we found cluster event on the servers and witness server CAS-01 also.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 12/22/2016 3:54:35 PM
Event ID: 1130
Task Category: Network Manager
Level: Error
Keywords:
User: SYSTEM
Computer: PDC-EX-MBX-01.abc.com
Description:
Cluster network 'Cluster Network 1' is down. None of the available nodes can communicate using this network. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related
to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 12/22/2016 3:54:35 PM
Event ID: 1127
Task Category: Network Manager
Level: Error
Keywords:
User: SYSTEM
Computer: PDC-EX-MBX-01.abc.com
Description:
Cluster network interface 'PDC-EX-MBX-01 - Heartbeat' for cluster node 'PDC-EX-MBX-01' on network 'Cluster Network 1' failed. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software
errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 12/22/2016 3:56:00 PM
Event ID: 1561
Task Category: Startup/Shutdown
Level: Critical
Keywords:
User: SYSTEM
Computer: PDC-EX-MBX-02.abc.com
Description:
The cluster service has determined that this node does not have the latest copy of cluster configuration data. Therefore, the cluster service has prevented itself from starting on this node.
Try starting the cluster service on all nodes in the cluster. If the cluster service can be started on other nodes with the latest copy of the cluster configuration data, this node will be able to subsequently join the started cluster successfully.
Guy's please suggest me what action should we taken to remove such kind of event on both the servers.
Thanks,
WS
Hello - we are moving users to Exchange 2013 but are seeing some interesting funny's. Outlook is hanging for users, users cant see calendars, cant book meetings etc. If we recreate the Outlook profile it resolves the issues for a while but they do then come back again for some users.
Exchange 2013 is a resource domain to our users - e.g. we logon to "domain x" in AD but our mailbox is on Exchange 2013 in "domain y"
Outlook 2007 - yes its old and there are reasons we have to run this. It is supported though at a certain hotfix which were running.
Anyone able to provide any assistance on this.
Many Thanks.
I have multiple domains (4) in my environment. I have 1 email domain of something@xyz.com We have users that log into xyz.com as their home domain and then we have users the log into the 3 other domains as their home domain. Everyones email resides on domain xyz.com. We have an Exchange server 2013 and migrating to 2016 within 2 weeks. We want to apply a password policy to all logon domains but not to email accounts that logon to another domain other than xyz.com. Example user A logs on domain abc.com and their email resides on domain xyz.com, I want the password policy of abc.com to apply to that user but do not want the password policy of xyz.com to apply to that user because they never login to xyz.com domain. They only use xyz.com for their email. Is this possible and if so how?
Thanks,
Kevin
We have been running an Exchange 2013 Powershell script to export certain mailbox values to a csv and then convert that to an XLS file within the script. I just moved it to a new Win server 2012 management box with Exchange on it. We run it under a service account using a Scheduled Task. It worked flawlessly on the older server but I need to decom that box.
Here is the issue though. On the new server if I run a ExPowerShell window as the service account and then run the script from that window it works like a champ. If I run the exact same script from the Task Scheduler using the service account credentials, it will create the csv and do everything else in the script but will not convert it to an xlsx file. It is using the exact same ps1 file with the exact same credentials – just two different methods.
The part of the script that it won’t run as a task is:
start-sleep -s 2
$xl = new-object -comobject excel.application
$xl.visible = $false
$Workbook = $xl.workbooks.open(“E:\Scripts\Scheduled_Runs\Company_Billing\Company_MailboxExtract.csv”)
$Worksheets = $Workbooks.worksheets
$Workbook.SaveAs(“E:\Scripts\Scheduled_Runs\Company_Billing\Company_MailboxExtract.xlsx”,51)
$Workbook.Saved = $True
$xl.Quit()
start-sleep -s 3
It runs the parts of the script before and after this snippet but will not do the conversion.
Remember it will convert if I run the ps1 file from a EXPowerShell window.
Any ideas on why this piece won’t run when called from a scheduled task? Any clues would be appreciated.
I have exchange 2010 SP2 we have retention policy to archive mail more than 365 days. The problem is it showing two archive files one Personal Archive and other as online archive. and online archive shows as disconnected. I connected disconnected archive mailbox. But It still shows disconnected and while trying to export to pst it says "couldn't find the mailbox".
Could some one help me out as I need to migrate all these pst to Office 365.
Greetings,
I have been wrestling with VSS writers on Exchange servers with backups for some time. It seems to affect different servers at different times.
The common suggestion seems to be: reboot the server.
Really?!?!
Of course there are no errors and the VSS writer is stable on a clean boot - it breaks again at the next backup interval!!
The backup application vendors (it doesn't matter who - take your pick), generally blame Microsoft ("VSS is a Microsoft product, so you need to fix the underlying VSS issue"). Thanks...so helpful.
I've found that restarting the Information Store and/or Exchange Replication service(s) will return the VSS writers to a stable state. Then, running diskshadow to create/end a backup will "manually" flush the logs.
However, at the next backup interval, the VSS writers go back to the dreaded "retryable error" state.
Does anyone have success in determining the root cause of these issues?
Rebooting a server every day just to get a backup is not an acceptable solution.