Background

I have a BizTalk 2013 R2 server that has several Send Port Groups configured to send EDI messages. Occasionally we need to pause one of the send ports. During this time we would like messages to be queued instead of discarded, similar to how BizTalk keeps messages that don't have any subscriptions at all.

Configuration

Here is a simplified example of one of these port groups:

EdiOutPortGroup (filter: EdiDst == CustomerId)
  |-- PartnerFtpSendPort
  |-- LocalArchiveSendPort
  |-- SomeOtherSendPort

Question

How can I temporarily stop the LocalArchiveSendPort without losing the messages that would normally be delivered there?

I would like new messages to queue up and be sent once the port is active again, but b/c there are still other active Send Ports in the group, new messages are delivered to the active ports with (seemingly) no way to resend them to LocalArchiveSendPort later.

TL;DR: How do I make sure that the SMTP server doesn't accept external messages for distribution groups that are set to require authentication?

I have an Exchange 2010 server that has multiple distribution groups where some of the groups are used only internally (RequireSenderAuthenticationEnabled == $true) and some are used publicly (RequireSenderAuthenticationEnabled == $false).

The public groups work as expected.

The internal groups work as expected for internal (i.e. authenticated) users, however, the SMTP service is not rejecting messages from external users. Instead, it accepts the message into the queue:

250 2.6.0 <[email protected]> [InternalId=3951] Queued mail for delivery

But then fails to route the message:

Source                  : ROUTING
EventId                 : FAIL
InternalMessageId       : 3951
MessageId               : <[email protected]>
Recipients              : {[email protected]}
RecipientStatus         : {550 5.7.1 RESOLVER.RST.AuthRequired; authentication required}

So the end result is that the message is never received by the group, however, the sender doesn't know this b/c according to our SMTP server the message was accepted.

How do I ensure that the SMTP server rejects the message instead of queuing it for delivery? (I thought this was the default behavior but I'm not sure what might have changed)

The relevant receive connector is set up as follows:

Update 2019-03-19:

I have confirmed that running the same scenario on another environment (Exchange 2010 on SBS 2011) produces the expected results. I created two groups, set the RequireSenderAuthenticationEnabled flag accordingly, and the private group rejects external email at the SMTP connector with the following message:

550 5.1.1 User Unknown

The relevant SMTP connector has the same settings on the Authentication and Permission pages.

Update 2019-03-21:

After installing Exchange 2010 SP3 R26 the results are still the same.

In trying to reduce the storage bottleneck on a Windows server (2008 R2) I need to find the files that have the highest I/O over a long period of time (aka 'hot' files) so I can move those to SSD storage. How can I track the I/O of the file system over a longer period of time (i.e. days to weeks) so I can see which files would benefit most from the move?

The Sysinternals utility procmon allows me to gather I/O statistics for short periods (i.e. from seconds to many minutes), but I don't think it's suitable for long term logging.

I would prefer a built-in solution, but will consider any others as well.

I am trying to come up with a way to consolidate two routers into one. I have the following network configuration:

 LAN <-- a/24 --> NAT Firewall <-- x/29 --> Router <-- y/30 --> Internet
                                    |
 LAN2 <-- b/24 --> NAT Firewall <---

where a/24 and b/24 are my internal subnets, x/29 is a small block of public IPs we have been assigned, and y/30 is the internet connection supplied by the ISP.

Typically the ISP would own the router, but in this case we will own the NAT firewalls and the router. I'd like to avoid setting up three separate pfSense appliances and want to consolidate the whole thing into something like this:

 LAN <-- a/24 --> Firewall/Router <-- y/30 --> Internet
                      |
 LAN2 <-- b/24 <------

I would still need to be able to assign an address from the x/29 block as the external NAT address for each LAN, and allow port forwarding on those addresses to servers on the LAN (ex: web server).

Is it possible to combine multiple route hops using a single pfSense firewall?

UPDATE: To clarify, the x/29 is routed 'through' the y/30 block from the ISP's standpoint. In other words, the GW for the x/29 is one of the addresses in the y/30 block.