I have a Proxmox server with a few zpools. One of the zpools rust01 is a 4-disk zpool, where the metadata and write cache were some nvme m.2 drives on the motherboard (one for each - I know, stupid, but that's what was done).

It appears as though the rust01 has had a catastrophic failure. When I click on rust01 in the Server View, I get the following error: could not activate storage 'rust01', zfs error: cannot import 'rust01': I/O error (500)

• When I go to { Server } > Disks > ZFS, I do not see the rust01 zpool.

• When I go to { Server } > Disks I don't even see the 4-disks or the special metadata -file or the read/write cache drives.

• When I run zpool status -x I get all pools are healthy

• When I run zpool import rust01 I get the following message:

  cannot import 'rust01': I/O error
  Destroy and re-create the pool from
  a backup source.
  

When I run zpool status rust01 I get cannot open 'rust01': no such pool, When I reboot the server, below is the error emailed to me:

ZFS has detected that a device was removed.
impact: Fault tolerance of the pool may be compromised.
eid: 10
class: statechange
state: UNAVAIL
host: pve01
time: 2024-09-14 21:20:32-0500
vpath: /dev/nvme2n1p1
vphys: pci-0000:41:00.0-nvme-1
vguid: 0x297D516B1F1D6494
devid: nvme-Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0T815592K-part1
pool: rust01 (0xE4AAC2680D8B6A7E)

When I run zpool destroy rust01 I get the following error cannot open 'rust01': no such pool. Ideally, I would like to get rust01 back online. I am fairly certain the issue is the special metadata disk mentioned in the email above. That said, I would be happy to destroy and recreate rust01. All of the VMs on that disk are backed up, so I can easily restore if needed. My problem, however, is that I can't find a way to get Proxmox/ZFS to release the disks associated with the corrupt rust01 zpool. Below is the output of lsblk:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    1 465.8G  0 disk 
|-sda1        8:1    1  1007K  0 part 
|-sda2        8:2    1     1G  0 part 
`-sda3        8:3    1   464G  0 part 
sdb           8:16   1 465.8G  0 disk 
|-sdb1        8:17   1  1007K  0 part 
|-sdb2        8:18   1     1G  0 part 
`-sdb3        8:19   1   464G  0 part 
sdc           8:32   1   3.6T  0 disk 
|-sdc1        8:33   1   3.6T  0 part 
`-sdc9        8:41   1     8M  0 part 
sdd           8:48   1   3.6T  0 disk 
|-sdd1        8:49   1   3.6T  0 part 
`-sdd9        8:57   1     8M  0 part 
sde           8:64   1   3.6T  0 disk 
|-sde1        8:65   1   3.6T  0 part 
`-sde9        8:73   1     8M  0 part 
sdf           8:80   1   3.6T  0 disk 
|-sdf1        8:81   1   3.6T  0 part 
`-sdf9        8:89   1     8M  0 part 
sdg           8:96   1     0B  0 disk 
sdh           8:112  1     0B  0 disk 
sdi           8:128  1     0B  0 disk 
sdj           8:144  1     0B  0 disk 
sdk           8:160  1     0B  0 disk 
sdl           8:176  1     0B  0 disk 
sdm           8:192  1     0B  0 disk 
sdn           8:208  1     0B  0 disk 
sr0          11:0    1  1024M  0 rom  
sr1          11:1    1  1024M  0 rom  
sr2          11:2    1  1024M  0 rom  
sr3          11:3    1  1024M  0 rom  
zd0         230:0    0     4M  0 disk 
zd16        230:16   0    80G  0 disk 
`-zd16p1    230:17   0    80G  0 part 
zd32        230:32   0    64G  0 disk 
|-zd32p1    230:33   0     1M  0 part 
|-zd32p2    230:34   0     2G  0 part 
`-zd32p3    230:35   0    62G  0 part 
zd48        230:48   0    40G  0 disk 
|-zd48p1    230:49   0   600M  0 part 
|-zd48p2    230:50   0     1G  0 part 
`-zd48p3    230:51   0  38.4G  0 part 
zd64        230:64   0    32G  0 disk 
|-zd64p1    230:65   0    31G  0 part 
|-zd64p2    230:66   0     1K  0 part 
`-zd64p5    230:69   0   975M  0 part 
zd80        230:80   0    90G  0 disk 
|-zd80p1    230:81   0   100M  0 part 
|-zd80p2    230:82   0    16M  0 part 
|-zd80p3    230:83   0  89.4G  0 part 
`-zd80p4    230:84   0   523M  0 part 
zd96        230:96   0    90G  0 disk 
|-zd96p1    230:97   0   499M  0 part 
|-zd96p2    230:98   0   128M  0 part 
|-zd96p3    230:99   0  88.5G  0 part 
`-zd96p4    230:100  0   920M  0 part 
zd112       230:112  0   100G  0 disk 
|-zd112p1   230:113  0   499M  0 part 
|-zd112p2   230:114  0    99M  0 part 
|-zd112p3   230:115  0    16M  0 part 
`-zd112p4   230:116  0  99.4G  0 part 
zd128       230:128  0    64G  0 disk 
|-zd128p1   230:129  0     1M  0 part 
|-zd128p2   230:130  0     2G  0 part 
`-zd128p3   230:131  0    62G  0 part 
zd144       230:144  0    90G  0 disk 
|-zd144p1   230:145  0   500M  0 part 
`-zd144p2   230:146  0  89.5G  0 part 
zd160       230:160  0    60G  0 disk 
|-zd160p1   230:161  0   100M  0 part 
|-zd160p2   230:162  0    16M  0 part 
|-zd160p3   230:163  0  59.4G  0 part 
`-zd160p4   230:164  0   450M  0 part 
zd176       230:176  0    32G  0 disk 
|-zd176p1   230:177  0     1M  0 part 
|-zd176p2   230:178  0     2G  0 part 
`-zd176p3   230:179  0    30G  0 part 
zd192       230:192  0   100G  0 disk 
|-zd192p1   230:193  0   450M  0 part 
|-zd192p2   230:194  0    99M  0 part 
|-zd192p3   230:195  0  15.8M  0 part 
|-zd192p4   230:196  0  89.4G  0 part 
`-zd192p5   230:197  0   256K  0 part 
zd208       230:208  0    32G  0 disk 
|-zd208p1   230:209  0   600M  0 part 
|-zd208p2   230:210  0     1G  0 part 
`-zd208p3   230:211  0  30.4G  0 part 
zd224       230:224  0     1M  0 disk 
nvme1n1     259:0    0   1.8T  0 disk 
|-nvme1n1p1 259:1    0   1.8T  0 part 
`-nvme1n1p9 259:2    0     8M  0 part 
nvme3n1     259:3    0   1.8T  0 disk 
|-nvme3n1p1 259:4    0   1.8T  0 part 
`-nvme3n1p9 259:5    0     8M  0 part 
nvme0n1     259:6    0   1.8T  0 disk 
|-nvme0n1p1 259:7    0   1.8T  0 part 
`-nvme0n1p9 259:8    0     8M  0 part 
nvme2n1     259:9    0   1.8T  0 disk 
|-nvme2n1p1 259:10   0   1.8T  0 part 
`-nvme2n1p9 259:11   0     8M  0 part 

There are other VMs on this host running on other zpools, that appear fine. As such, reinstalling everything is not an option I want to entertain.

UPDATE: After running through the steps outlined in Fix your dead SSD with the power cycle method the 4TB hard drives are showing up in Proxmox, albeit the zpool is not accessible. Some progress, but still no access to the data.

Any ideas on how to proceed other than a wiping the disks in the affected zpool?

I am trying to request a LetsEncrypt certificate using DNS validation. My DNS provider is Google DNS. No matter what I do, I keep receiving the following error:

 [EROR] File C:\LetsEncrypt\{GCP-ServiceAccountKey} does not exist

Where {GCP-ServiceAccountKey} is the Key I generated from the GCP Cloud console.

Below is the command I am running to try and generate the Cert request:

.\wacs.exe --target manual --host adfs.public-facing.com --installation script --script ".\Scripts\ImportADFS.ps1" --scriptparameters "'{CertThumbprint}'" --validation gcpdns --serviceaccountkey {Purposely-removed-ServiceAccountKey} --projectid {Purposely-removed-ProjectId} --verbose

I'm pulling my hair out here. What am I doing wrong or missing?

I followed the steps in the link below to install the Edge policy templates into Active Directory.

https://pureinfotech.com/install-microsoft-edge-group-policy-templates-windows-10/

However, after doing so, I am noticing that all of my other policy templates are missing from GPO. For example, I am no longer able to see Control Panel, Desktop, Network, Shared Folders, etc.

What is the correct way to import custom policies into AD without overriding all of the other policy templates?

EDITED TO PROVIDE MORE INFORMATION (see below):

Before I add the Edge-related ADMX files under the SYSVOL Central Policy share, when I expand User Configuration > Policies > Administrative Templates, I see the following: Following the instructions in the above-linked article, I need to create a PolicyDefinitions folder under \\domain-controller\SYSVOL\Policies and then drop in the ADMX files. After doing that, below is what I see (note that the Software Settings, Windows Settings and other folders are all now missing): I've seen a few articles online saying you just need to copy the files under C:\Windows\PolicyDefinitions to the Central Policy store. Before blindly following those instructions, I wanted to get information from the community if I'm importing these Edge-related ADMX properly or if there is another way to import these Edge-related ADMX files so that it doesn't "overwrite"/hide the other policies as shown in the screenshots above.

I am running a RHEL 8 server, trying to utilise the SDK for Privilege Vault.

I am following the instructions to install the SDK Secret Server Scripting Tool for DevOps (click here) on the Linux server but running into an issue when trying to initialise the Client. I am getting the following error:

Failed to load x�Z, error: libunwind.so.8: cannot open shared object file:

No such file or directory Failed to bind to CoreCLR at '/var/lib/tss/libcoreclr.so'

The issue appears to be related to the libunwind missing. But when I try to install that package, I am getting the following error:

Last metadata expiration check: 2:20:23 ago on Wed 21 Dec 2022 08:00:44 AM EST.

No match for argument: libunwind

Is there something obvious I am missing here?

I have WDS and MDT installed on a Windows Server in my network. The WDS server is on the same subnet as the client machine. I am getting the following error on my VMware VMs when trying to boot LiteTouch over PXE:

I can't figure out how to get rid of the error. I've tried:

1. Recreating the LiteTouch boot image in MDT and re-importing it into WDS.
2. Rebooting the WDS/MDT server multiple times.
3. Switching the client VM's adapter type between E1000E and VMXNET3.
4. Deleting and remounting the hard drive on the VM.

Any other ideas on what I should do to troubleshoot?

I have an MDT/WDS server (VM) with both MDT and WDS installed on it. I've had this server for a few years, with several WDS/MDT deployments happening from it each day (automated). I've never had an issue with the server previously.

Last week we move the VM to a different ESXi host, hosted in a different data centre, and all of a sudden the LiteTouchPE_x64.wim and Boot.wim has been taking ages to load. Below is a screenshot showing the loading screen I'm talking about.

When this was running in our old data centre, this loading screen would only show for a few seconds. Now, it is taking several hours.

Below is the troubleshooting we've done so far:

1. We're not experiencing any issues on the ESXi host the MDT/WDS server is running on.
2. Both the WDS server and PXE client are running on the same ESXi host (so it doesn't feel as though this is a networking issue).
3. I've tried importing the drivers into MDT for our Lenovo ST50 (the ESXi host), and that hasn't changed the performance.

Does anyone know what would cause the boot wims to run so slow?

We have two locations, one in Miami (192.168.3.0/24) and the other in New York (192.168.5.0/24). The two locations are linked via VPN. I wanted to set up an Read-only Domain Controller (RODC) in New York, with servers and PCs running in that location using that DC for DNS and Authentication.

I've come across the following RODC tutorial from Microsoft:

https://tech.iot-it.no/microsoft/microsoft-windows-rodc-setup/

To achieve what I am looking for (i.e. DNS and authentication) in the remote office, do I really need to create a new Site and DNS Zone?

Is there a more simplified configuration for my needs?

I have configured Claims Provider Trust in ADFS and I am getting only Email in NameID. I can not make changes to Third party Claims Provider Trust, so I have to get WindowsAccountName using the Email Address, which I received in NameID from Third Party IDP and forward it to Outlook Web Access (on-premise).

I've found that when I use the following Claim Rule, sign-in works, but only if the user's UPN and email address match. If there are differences between them (e.g. sAMAccountName=jdoe; [email protected]; Email=Jonathan.Doe@contoso.com), the value forwarded to Exchange causes an error to be thrown.

c:[Type == "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier", Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/format"] == "urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified"]
 => issue(Type = "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer = "AD AUTHORITY", OriginalIssuer = c.OriginalIssuer, Value = regexreplace(c.Value, "(?<user>[^\@]+)\@(.+)", "contoso\${user}"), ValueType = c.ValueType);

How can I look up a user via their email address, and return theirWindowsAccountName in domain\username format?

Overview

I have an Exchange hybrid deployment, with one Exchange 2019 server on-premise and an EXO subscription. Our autodiscover.domain.com is pointing to our on-premise Exchange environment. As is mail.domain.com.

Problem

I'm trying to configure the Outlook App on my Android phone, trying to connect to an on-premise mailbox and it is not working.

When I open the Android, I enter the users email address [email protected]. Then, I choose Exchange for the mailbox type. Then, after entering the server details and my credentials, I get the following error:

Login Error

Please check your email and password and try again

Troubleshooting done so far

With this being a hybrid environment I'm not sure where to go to get logs. That said, below is the troubleshooting I've done so far:

1. Confirmed that inbound mail flow from external sources to [email protected] works without issue.
2. Confirmed that outbound mail flow from [email protected] works without issue.
3. Was able to successfully log in to OWA externally, from another network.
4. Confirmed that there are no firewall rules blocking access to the on-premise Exchange server.

Question(s)

• Are there any logs I can grab from the Outlook Android app to troubleshoot? And, how do I do that?
• What should be my next steps.

Overview

We have a 300-user environment. Each time a member of staff leaves we use MDT fully wipe their machine and reinstall Windows 10/11. This means that while a new member of staff gets the previous staffer's computer, the machine was fully wiped with a fresh Windows 10/11 install.

We would like to improve this process by introducing additional steps in the MDT task sequence that would backup the computer to a network location BEFORE wiping and re-installing Windows. The idea being, if we later find that the previous staffer had an important file on their PC, we could restore/mount the backup and retrieve that file.

Question(s)

1. Is MDT even a good candidate for this?
2. I wanted to know if anyone has had any real world experience with doing this via MDT?
3. Would anyone be able to give advice on the best way/option to use to backup the PC? And, or mount and restore file(s)?

Environment

1. 300 PCs/users
2. 99.9% of machines are Windows 10
3. Storage really isn't an issue for us. We have tons of it, and budget to buy more.

We have an MDT server provisioned in our environment that used for two processes.

1. The deployment of PCs. i.e. Help Desk personnel provision new machines using the images in MDT/WDS.
2. A nightly hands-off process related to MDT.

Within the Bootstrap.ini file we have the following settings:

[Default]
SkipBDDWelcome=YES
DeployRoot=\\192.168.1.2\DeploymentShare$
UserID=example
UserPassword=hello
UserDomain=me.local

This works great. Meaning, when someone loads LiteTouch they are not asked to authentication. They are instead just taken right into selecting the Task Sequence.

That said, what I would really like to do is set the UserID, UserPassword and UserDomain based on the MAC address. Basically, something like what's below:

[Default]
SkipBDDWelcome=YES
DeployRoot=\\192.168.1.2\DeploymentShare$

[7A-81-CC-E9-A4-70]
UserID=example
UserPassword=hello
UserDomain=me.local

The idea being that, everyone should need to authenticate except for one specific MAC address. If the computer being imaged has the MAC address specified above, then use the UserID (etc) values specified above.

I tried this a couple of times, and LiteTouch appears to ignore the credentials unless they are under [Default]. I can't find any documentation to know whether that's buy design, or if there is something I'm doing wrong.

Anyone have any ideas?

Looks like I've found myself in a bit of trouble here...

Background information

I am trying to clean up a domain that had 5 domain controllers, bringing it down to a two-DC environment. It is a very small environment with less than 20 machines. We ended up with 5 domain controllers simply as a result of unfinished work that we're finally getting around to in an effort to raise the domain functional level from 2012 to 2019.

The setup is as follows:

• bmdc9 is Windows Server 2016 the PDC with all of the FSMO roles.
• bmdc8 is Windows Server 2016.
• bmdc10 is Windows Server 2016 Core.

The goal is to create a new domain controller bmdc13 and bmdc14 which will both be Windows Server 2019. Then, to raise the domain functional level to 2019.

Current issues:

#1: Whenever we run the DC demote wizard on bmdc8 we're getting an error saying:

No other domain controller could be contacted, but other domain controller objects are in the directory. If you are certain that this is the last domain controller for the domain and want to proceed, confirm that this is the last domain controller in the domain.

The problem is, this is NOT the last DC. VMs bmdc9 and bmdc10 are still up and active.

#2: Whenever we shut down bmdc10 we completely lose all DNS for external addresses. Meaning, if we try to ping www.google.com we get an error message saying: (Answered this myself, see Nov 5th comment below)

Ping request could not find host www.google.com. Please check the name and try again.

#3: When I run repadmin /replsum I am getting the following output:

What really strange here is that bmdc6 no longer exists. It was demoted earlier today (without errors) and removed from the domain gracefully.

#4: Whenever I go into Active Directory Sites and Services I am seeing more DCs than I should do:

For some reference:

• bmdc4 was demoted earlier today.
• bmdc6 was demoted earlier today.
• bmdc8 up and running, but I would like to demote.
• bmdc9 up and running. The current PDC.
• bmdc10 up and running, but I would like to demote.

Other information:

In case it is helpful, below is some additional information:

Question(s)

Basically, I'm at a loss as to how unhealthy my environment is at the moment.

• Why am I getting the replication errors? And, how do I clean that up?
• Why are the old demoted DCs still showing up under Active Directory Sites and Domains? (i.e. bmdc4 and bmdc6). How do I remove them?
• Why is DNS not working unless bmdc10 is up even though all NICs in our network have bmdc9 as the primary DNS server and bmdc10 as the secondary?
• Is it safe to proceed with demoting bmdc8 even with the aforementioned 'last domain controller' warning?
• What's the quickest non-intrusive way to fix all of this?

My ultimate goal is to migrate over to Server 2019 and raise the domain functional level to 2019. I don't care if that involves creating more DCs and retiring everything I have now, just as long as I don't lose the objects/users/computers/passwords in my current domain.

If anyone can help me out, that would be amazing. Thanks in advance.

Update(s)

2021-11-05 @ 14:06: This is what I get when I run repadmin /showreps

Default-First-Site-Name\BMDC9
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: **REMOVED**
DSA invocationID: **REMOVED**

==== INBOUND NEIGHBORS ======================================

DC=xxxx,DC=local
    Default-First-Site-Name\BMDC8 via RPC
        DSA object GUID: **REMOVED**
        Last attempt @ 2021-11-05 13:49:37 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        5700 consecutive failure(s).
        Last success @ 2021-06-15 11:19:34.
    Default-First-Site-Name\BMDC10 via RPC
        DSA object GUID: **REMOVED**
        Last attempt @ 2021-11-05 13:56:14 was successful.

CN=Configuration,DC=xxxx,DC=local
    Default-First-Site-Name\BMDC8 via RPC
        DSA object GUID: **REMOVED**
        Last attempt @ 2021-11-05 13:49:37 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        3444 consecutive failure(s).
        Last success @ 2021-06-15 10:51:35.
    Default-First-Site-Name\BMDC10 via RPC
        DSA object GUID: **REMOVED**
        Last attempt @ 2021-11-05 13:49:37 was successful.

CN=Schema,CN=Configuration,DC=xxxx,DC=local
    Default-First-Site-Name\BMDC8 via RPC
        DSA object GUID: **REMOVED**
        Last attempt @ 2021-11-05 13:49:38 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        3427 consecutive failure(s).
        Last success @ 2021-06-15 10:51:35.
    Default-First-Site-Name\BMDC10 via RPC
        DSA object GUID: **REMOVED**
        Last attempt @ 2021-11-05 13:49:38 was successful.

DC=DomainDnsZones,DC=xxxx,DC=local
    Default-First-Site-Name\BMDC8 via RPC
        DSA object GUID: **REMOVED**
        Last attempt @ 2021-11-05 13:49:38 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        3465 consecutive failure(s).
        Last success @ 2021-06-16 17:20:40.
    Default-First-Site-Name\BMDC10 via RPC
        DSA object GUID: **REMOVED**
        Last attempt @ 2021-11-05 13:49:38 was successful.

DC=ForestDnsZones,DC=xxxx,DC=local
    Default-First-Site-Name\BMDC8 via RPC
        DSA object GUID: **REMOVED**
        Last attempt @ 2021-11-05 13:49:38 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        3431 consecutive failure(s).
        Last success @ 2021-06-15 10:51:35.
    Default-First-Site-Name\BMDC10 via RPC
        DSA object GUID: **REMOVED**
        Last attempt @ 2021-11-05 13:49:38 was successful.

Source: Default-First-Site-Name\BMDC8
******* 5700 CONSECUTIVE FAILURES since 2021-06-16 17:20:40
Last error: 8456 (0x2108):
            The source server is currently rejecting replication requests.

Overview

We have a server dedicated to AzureAD Connect. We're a small organisation (less than 300 staff). I am considering installing the ActiveDirectory PowerShell module (click here) on the same server.

Question(s)

1. Has anyone here done this before?
2. Did anyone run into issues doing so?
3. Any advice, warnings, etc.?

Overview:

In our environment, we have MDT + WDS. Each night a Windows 10 VM boots and MDT installs Windows 10, along with downloading and install the latest updates from Microsoft. The "install.wim" we're using was copied from a Windows 10 ISO downloaded from MSDN.

This process works excellent so long as we continue to run this process using the "install.wim" file from a Windows 10 ISO as the base image. If we use DSIM to capture a new image (i.e. after the MDT-managed Windows 10 install and MS updates), the process only partially works. Meaning, when attempting to run the same task sequence on a newly-capture "install.wim", MDT installs Windows 10, but it doesn't auto-login, download and install the latest Microsoft updates. Instead, after Windows 10 installs, Windows 10 just sits at the logon screen.

Desired outcome:

I would like to install Windows 10 using MDT and capture that installation using DSIM. After that, we want to import that newly-installed and newly-patched version of Windows 10 into WDS and at a later date be able to re-run the task sequence on the new base image. Meaning, MDT would a) install Windows 10. Then b) auto-login and download and install the latest Windows updates. Finally c) shutdown the machine once all of that is complete. I should be able to run these actions on any Windows 10 base image we specify.

Steps to reproduce:

1. Import the unedited Windows 10 "install.wim" into WDS.
2. After running the "import the Operating Systems" wizard in MDT (to read OSs from WDS), configure a task sequence to install, patch and shutdown Windows 10.
3. Use the above-mentioned task sequence to install Windows 10. (All works excellent so far).
4. Detach the C-Drive and attach the C-Drive as an additional drive on a separate machine, i.e. a Windows Server 2016 VM. Then, run DSIM to capture the Windows 10 install. The DSIM command used is as follows:

dism /Capture-Image /ImageFile:"E:\MDT_Capture_Files\Win10Capture_DISM.wim" /CaptureDir:F:\ /Name:"Windows10CaptureDISM"

5. In WDS, replace the above-mentioned Windows 10 "install.wim" with the WIM created by DSIM.
6. Boot the computer (in Step #3), reinstall Windows 10 using MDT. This is where things go wrong. Windows 10 installs, but the auto-login does not work. Even when we manually sign in, the rest of the MDT task sequence does not run.

Overview:

We have a demo environment where we have installed Exchange 2019. The Exchange 2019 server is set up in Classic Hybrid mode with centralised mail transport enabled. Inbound emails are successfully flowing through Office 365 to our on-premise Exchange mailboxes. However, outbound messages (sent from on an on-premise mailbox) is not received by external recipients.

Steps to reproduce:

• An external user sends an email to [email protected] (i.e. EOP mailbox).
• Mia replies to the email.
• The external recipient never receives the email.

Troubleshooting done so far:

• In OWA there is no indication that the email was not sent, or will not be delivered. The outbound email is sitting in the Sent folder.
• Within EXO Exchange Admin Center Mail Trace reports do not show any outbound messages leaving Mia's mailbox.

Question(s):

1. Exchange hybrid was configured by following this YouTube video thread. Are there any steps the trainer has missed?
2. Where can I go to begin troubleshooting why the outbound email from EOP is not sending?

I'm trying to get Postfix to pipe ALL email coming in on a specific domain to a PHP script. So far I've been able to do this via a tutorial I found on the web and also editing the /etc/postfix/virtual file with something like what's below;

@domain.com root

The problem is that Postfix is re-writing the original recipient email address (for example [email protected]) to [email protected] and the PHP script receiving the email does not get the original recipient ([email protected]). It is important that the PHP script sees [email protected] instead of [email protected].

Is it possible for Postfix to direct all incoming mail to the PHP script without modifying the address like in the example above?

Note: There can/will potentially be 10,000's of incoming email addresses.

Any ideas on how I can get Postfix to do what I want?