EHLO Again! The Exchange Team Blog Defined

Happy to register and look forward to increased interaction between registered users and the team. Maybe then someone will provide a proper answer as I am very concerned that we are being pushed into an unsupported state. We were just told by PSS that

"The product team is aware of with this DCR request for Exchange 2013 CU3. However, they won't fix it since the business impact is very minimum with acceptable work around (using adsiedit.msc) and cost/risk of fix is high" Seeing as how the change in the gui

to restrict the number of auto attendant transfer digits to the number of digits in the dial plan extensions was JUST INTRODUCED in CU3, I fail to see how the cost/risk of the fix is high. If it was, the team would not have introduced this useless and aesthetic

change in the first place! We have been told that the team has suggested using ADSIEDIT to directly edit the XML file that controls the auto attendant settings. If the team and PSS expect us to accept the adsiedit workaround as a legitimate, long-term solution

to this issue, then we would appreciate an official statement from both PSS and the Exchange team explicitly stating that the adsiedit method is the recommend AND SUPPORTED method to deal with this issue. Thank you, Wes