Intune Deploy - Powershell version 4.0 or higher is required

[Paulklerkx]

Hi,
Intune deploy tool 22.4 shows this message when I start it.

https://mitownsville-my.sharepoint.com/ ... g?e=5xvdqs

can't get the image link to work, the message is that it needs powershell 4 minimum. this is on windows 10 so it is V5.1

Name Value
---- -----
PSVersion 5.1.19041.5486
PSEdition Desktop

[Catalin]

Hello Paul,

First of all, please accept my apologies for the quite delayed reply on this.

This is indeed really strange.

I have run a quick test on my Windows 10 machine, version 22H2 and I wasn't able to reproduce this issue.

Screenshot_238.png (92.91 KiB) Viewed 15157 times

What version of Windows 10 are you currently running?

I'll discuss tomrorow with our dev to see what exactly we are checking for the PS version and will followup with you here.

Best regards,
Catalin

[Paulklerkx]

Hi, thanks for the response. I am running Windows 10 Enterprise 22H2 OS build 19045.5487.

Name Value
---- -----
PSVersion 5.1.19041.5486
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.19041.5486
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

One thing, the error comes when you click the next button on that window you showed.

[Catalin]

Hello Paul,

Upon further investigations, it looks like we only launch PowerShell.exe with a parameter.

That parameter is exactly the file version from $psversiontable, converted to string.

Below you can find a download link for a debug version of the tool, which should give us some more details as to what exactly is failing.

Link to intune.exe

After downloading the zip and extracting it, please copy it into the following location:

Code: Select all

"C:\Program Files (x86)\Caphyon\Advanced Installer 22.5\bin\x86\intune.exe"

replacing the original one.

After all that, redo the scenario and please forward me a screenshot of the erorr.

Best regards,
Catalin

[Paulklerkx]

Hi, the issue appears to be with an unsigned Powershell script (we have policy requiring allsigned.)



I checked the temp directory and the file doesn't exist.

[Catalin]

Hello Paul,

If possible, could you please upload the image (e.g. on imgur) and forward me the link?

It looks like I can not see the screenshot you attached.

Screenshot_240.png (10.3 KiB) Viewed 15020 times

In the meantime, I will discuss with our dev about this.

Best regards,
Catalin

[Paulklerkx]

https://imgur.com/a/ZOruXeL

[Catalin]

Hello Paul,

Thank you for that!

I have forwarded this to our dev and will followup on this thread as soon as I will have more info.

Best regards,
Catalin

[Paulklerkx]

Hi, any updates?

[Catalin]

Hello Paul,

Although the issue had the "Customer" tag, it looks like I somehow forgot to add this thread in the issue to later know to notify you.

I apologize for that.

This issues has been fixed in version 22.7 of Advanced Installer (released last month). In the meantime, we released version 22.8 as well, which you can download from here:

https://www.advancedinstaller.com/download.html

Best regards,
Catalin

[Paulklerkx]

thanks for the update, I have 22.7, the issue still exists. I'll try 22.8

[Catalin]

Hello Paul,

I'm sorry to hear that the problem is still reproducible - perhaps we misunderstood the issue here and fixed something else.

Did you have any luck with the latest version?

Best regards,
Catalin

[Paulklerkx]

Hi, 22.8 still has the issue. I have also just now installed 22.9 and the issue still exists.

the process is

• Create an MSI
  Save and build
  go to Package Definition - Deployment
  Click the link "Launch Intune Deploy Tool"
  Error appears

I notice for the "SCCM" tool, there is a config with server, site code, login creds etc. There isn't any of that for the Intune tool, is it maybe something missing there?

[Catalin]

Hey Paul,

I'm sorry to hear that this still does not work.

I discussed with the developer in charge of this feature and we will investigate this as soon as possible. I will update this thread if I'll require more information from your end.

With the vacation season here, please expect a little bit of a delay in our reply.

Thank you for your understanding!

Best regards,
Catalin

[Catalin]

Hello Paul,

As promised, here is my followup on this issue.

Upon further investigation, this seems to possibly be caused by a GPO regarding PowerShell scripts and their signatures (the AllSigned execution policy from PowerShell).

Could you please confirm that this is the policy on your end?

When that feature is used, we create a temporary powershell script that does the work behind the courtains.

Now, the problem comes from the fact that the PowerShell script is not signed.

The next problem would come from the fact that, even if we sign the PowerShell script, the GPO will still not allow it to run, because that GPO requires the certificate to be trusted on the machine and that means to manually install our certificate in the Trusted Root stored.

I have now created a ticket so that we can find a fallback mechanism for this.

Once I'll have more information, I'll update this thread.

Thank you for your patience and I'm really sorry for the inconvenience this has caused you.

Best regards,
Catalin