Direct Access: Unable to Add a New Entry Point
“The cmdlet did not run as expected.” Zoiks! Here’s how I fixed it…
The Issue:
I was trying to add a new entry point to our Direct Access Multi-Site configuration and it failed with the error “The cmdlet did not run as expected.” I also had a warning informing me that the DNS entry for the web probe could not be created and it should be created manually. (I think this warning was unrelated to the main issue of the entry point installation failing.)
The Solution:
Our organisational Direct Access infrastructure was built on Microsoft Server 2012 R2.
When I built the new Entry Point server in our Dubai office I used Microsoft Server 2016. This was why it failed as you cannot mix operating systems.
Bizarre, I know.
So I rebuilt the Entry Point server, this time using Microsoft Server 2012 R2, the same as all of our other DA and Entry point servers, ran the ‘Add Entry Point’ wizard again and bingo! It worked.
Get my books:
ConfigMgr - An Administrator’s Guide to Deploying Applications using PowerShell
“Understanding Microsoft Intune: Deploying Applications Using PowerShell” is available for purchase at all good book stores and online outlets. Don’t miss out on the opportunity to take your application deployment skills to the next level. Get your copy today!
