User Profile
Neill
Brass Contributor
Joined Aug 27, 2018
User Widgets
Recent Discussions
Exchange SE Transport Rule Query
I'm trying to use a transport rule to send a notification to an audit mailbox with a note of the names of all attachments being sent externally with From, To, CC, BCC details. It sort of works. Rule If message has an attachment that's larger than or equal to 0 bytes Do the following Set audit severity level to 'Not specified' and send the incident report to <audit mailbox>, include these message properties in the report: sender, recipients, subject, cc'd recipients, bcc'd recipients, severity, sender override information, matching rules, false positive reports, detected data classifications, matching content. If I send a message to: 'email address removed for privacy reasons', cc: 'email address removed for privacy reasons', bcc:'email address removed for privacy reasons' with 2 attachments the report includes the following: Sender: <sender> Recipient: To & CC Attachments: Only 1 attachment name i.e. Missing an attachment name and the BCC entry Is this a bug or a feature? I presume it is just flagging the first attachment greater than 0 bytes which is annoying but that wouldn't explain the missing BCC entry.80Views0likes1CommentRe: Exchange Build Release Date
Outblaze1 Going by this link it looks like it must have been somewhere between October 22 - 15.1.2375.32 and November 22 - 15.1.2375.37 https://learn.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019 I presume you'll already have seen this Did you get a custom hotfix from Microsoft maybe?3.9KViews0likes1CommentRe: Exchange 2016 database
manoubi Database size on disk will never reduce by removing mailboxes. If you have deleted the mailbox then after 30 days (by default) the detached mailbox will drop out of the database and Exchange will release the internal space back. If you have completely emptied the database of mailboxes then you could dismount the database, delete all copies and re-mount database which will recreate about 256MB of files. If you can't remove all mailboxes then best bet is to create a new one and add any new mailboxes to that. The old database should at least stop growing after 30 days once it purges the old mailboxes.1.3KViews0likes0CommentsRemoving AD tools from Exchange server
I've been asked if it is A) possible and B) supported to remove the ADDS tools from Exchange after installation. Obviously it's possible to just remove but would it break anything. I've had a good search around the web but can't see the actual reasoning that they are there as a pre-req. apart perhaps from the initial requirement to update schema, add OU's and security groups etc. But since that bit can be done on a non-Exchange server it's a question I can't answer. Perhaps so the AD module is available for scripts etc.? Unfortunately in this instance I can't just say "If Exchange wants it installed in the first place then just live with it". 😞945Views0likes1CommentRe: Disable users ability to create rules...
Nathee021 It looks like it can be set in OWA policy under Information Management / Inbox Rules. I'd thought in Outlook you'd be able to set it via Group Policy but I've had a look at the available options in the OL2016 template and don't see anything which covers it. Which is a bit strange. You would think that anything that could be enabled / disabled in OWA that isn't OWA exclusive should also be configurable in Outlook. Failing that you'd probably have to look at updating the My Base Options roles for the users which I think includes rule settings. So users would still see rules management in Outlook but wouldn't be able to apply any changes.24KViews0likes13CommentsRe: Exchange 2019 Failover with DAG Question
mmazurkiewcz269 So the FSW is on AN Other server which isn't an Exchange server, isn't a DC and is in the same AD domain? 1. Check that the domain Exchange Trusted Subsystem group is actually in the local admins group of the FSW. This catches a lot of people out. e.g. It might be set via group policy or some sort of security scanning util might take it out as not being an approved group. 2. Run Get-DatabaseAvailabilityGroup command and make a note of the FSW directory, on the FSW check if this folder exists and that there are files in it 3. Check that there are no firewalls between any of the 3 servers, especially on port 445 4. If for some reason you are using Windows firewall on the FSW check that it is using the domain profile. I've seen cases where Network Location Awareness sets the wrong profile and thus blocks traffic. NT3.2KViews0likes1CommentRe: Exchange 2019 memory requirements
Dan_Snape No error. See this - https://docs.microsoft.com/en-us/exchange/plan-and-deploy/system-requirements?view=exchserver-2019 Mailbox: 128 GB minimum recommended. Exchange 2019 has large memory support (up to 256 GB) Remember MS are using physical servers to run Exchange online which are presumably coming with at least 128GB RAM. They probably aren't bothering to test anything smaller.8KViews0likes0CommentsRe: Exchange 2019 memory requirements
Blade1966 For running in a VM it is 'only' a 64GB minimum according to the mailbox role calculator. Remember that MS were very clear at launch that Exchange 2019 is directed at huge multinationals with tens of thousands of mailboxes or those companies who can't move stuff to the cloud for security reasons. Neither of which will probably worry about the extra cost. If you don't meet the minimums then I believe MS will still support you but it would be a best-effort rather than we will definitely fix this. On the other hand the end-of-life dates for 2016 and 2019 are exactly the same so unless there is some super-spiffy thing in Exchange 2019 that you like the look of, unlikely, I know what I would do. Regards NT8KViews0likes0Comments
Recent Blog Articles
No content to show