A customer complained that POP3 was no longer working. After looking into this, it turned out that PopProxy was Inactive on the Exchange 2013 server. As to why it was inactive is unknown.
To start the PopProxy was challanging, generally you change ServerComponentState using the maintenance requester for most components. However running the following command did nothing:
Set-ServerComponentState -State Active -Requester Maintenance -Component PopProxy -Identity AB-EXCH-01
To start the PopProxy component, I needed to use the Exchange 2013 Health API as a requester.
Set-ServerComponentState -State Active -Requester HealthAPI -Component PopProxy -Identity AB-EXCH-01
To start the PopProxy was challanging, generally you change ServerComponentState using the maintenance requester for most components. However running the following command did nothing:
Set-ServerComponentState -State Active -Requester Maintenance -Component PopProxy -Identity AB-EXCH-01
To start the PopProxy component, I needed to use the Exchange 2013 Health API as a requester.
Set-ServerComponentState -State Active -Requester HealthAPI -Component PopProxy -Identity AB-EXCH-01
As shown below:
Hi Clint, I have this problem after each time the server gets restarted. Do you know what would be causing this or how to resolved it without having to type this command after each reboot?
ReplyDelete
Deletebuy windows 10 product key , window 7 product key stores , windows 2003 enterprise for sale , windows 8 enterprise license key sale , windows ultimate 32 bit product key , windows 7 professional termékkulcs , windows 10 product key , windows server multipoint server 2012 , lba3tc
Deletewindiws 7 key , office 2013 activation keys , online windows 7 keygen , windows anytime upgrade key ultimate , windows 10 serial key finder , windows 10 product key for clean install , microsoft visio professional 2016 , buy office 2010 product key online , s3x3qu
windows 10 pro key
office 2013 pro key sale
cheap visual studio key buy