Home intune setup intune troubleshooting microsoft intune mobile device management

Intune Connector Acting Up? Here's How to Fix Setup Issues

Updated: • 0 • min read
Table of Contents

Hey folks! Having trouble setting up your Microsoft Intune Connector? Getting that annoying “prematurely ended” error message? You’re not alone! This guide will walk you through fixing those pesky setup issues, getting your connector up and running, and back to securing your devices like a pro.

Intune Connector Setup
image just illustration

The Dreaded “Premature Ending”

Let’s face it, seeing setup wizards crash is frustrating. Specifically, if you’re trying to install the Intune Certificate Connector (NDESConnectorSetup.exe) and you’re hit with this message:

“Microsoft Intune Connector Setup Wizard ended prematurely because of an error.”

…well, it’s time to roll up our sleeves and get to troubleshooting!

Digging Deeper: The Symptoms

Besides the frustrating error message, you’ll probably see some equally cryptic entries in your SetupMSI.log file. They might look something like this:

MSI (s) (20:5C) [09:17:19:129]: Executing op:
CustomActionSchedule(Action=ConfigureIISLimits,ActionType=3170,Source=C:,Target=C:\\Windows\\SysWOW64\\inetsrv\\appcmd set  config \"Default Web Site\" -section:requestFiltering -requestLimits.maxQueryString:65534 -requestLimits.maxUrl:65534,)
CustomAction ConfigureIISLimits returned actual error code 1168 but will be translated to success due to continue marking
WriteIIS7ConfigChanges:  Error 0x80070002: Site not found for create application
WriteIIS7ConfigChanges:  Error 0x80070002: Failed to configure IIS application.
WriteIIS7ConfigChanges:  Error 0x80070002: WriteIIS7ConfigChanges Failed.
CustomAction WriteIIS7ConfigChanges returned actual error code 1603

Don’t worry if this looks like gibberish. The key takeaway is that something’s amiss with your IIS configuration.

The Root of the Problem: The Default Web Site

Nine times out of ten, this issue boils down to one thing: the name of your Default Web Site in Internet Information Services (IIS) Manager has been changed. Maybe it’s now “Default Web Site1” or something similar. This seemingly small change throws the Intune Connector installer for a loop.

Default Web Site
image just illustration

Here’s an example of what a renamed Default Web Site might look like in IIS Manager:

  • Original Name: Default Web Site
  • Changed Name: Default Web Site1

This is the culprit! Let’s fix it.

The Fix: Restoring Order to Your IIS

The solution is surprisingly simple. We just need to rename the Default Web Site back to its original name. Here’s a step-by-step guide:

  1. Open IIS Manager: Fire up IIS Manager on your server. You can usually find it by searching for “IIS” in the Windows search bar.

  2. Find the Default Website: Expand <Server Name>\Sites. You’ll see a list of websites. The Default Web Site should be there, but it might have a different name. If you see multiple websites, you’ll need to identify the correct one. Here’s how:

  • Right-click each site and select Manage Website > Advanced Settings.
  • Look for the website with an ID of 1. That’s your Default Web Site, regardless of its current name.

  1. Rename the Website: Once you’ve found the correct website (ID 1), right-click it, select Rename, and change the name back to Default Web Site. You might get an error message like “Unable to connect to Default Web Site1.” Don’t panic; it’s safe to ignore this message.

  2. Restart the Installer: With the Default Web Site name restored, run the NDESConnectorSetup.exe file again. This time, the installation should proceed without a hitch.

IIS Manager
image just illustration

Double-Checking Your Work

After the installation completes, it’s a good idea to double-check everything is working as expected. You can do this by testing your certificate enrollment process. If you encounter any further issues, consult the official Microsoft Intune documentation for more advanced troubleshooting steps.

A Final Word (or Two)

Hopefully, this guide helped you conquer that pesky Intune Connector setup error. Remember, even seemingly small changes to your IIS configuration can have unintended consequences. By understanding the cause of the problem and following these simple steps, you can quickly get back on track.

Now, go forth and secure those devices! And if you have any questions, comments, or further insights, feel free to share them below. We’re always happy to hear from you and learn from your experiences. Come back anytime for more tech tips and troubleshooting guides!

Post a Comment