Script not working about intunedrivemapping HOT 8 CLOSED

I'm in a similar boat Anaylor. Couldn't get it to do anything, despite it showing as successful in Intune. I finally toggled it over to run as SYSTEM instead of the Logged in USER. This created the Schedule task, but I can't get that to run. It looks like it's calling a VBS file. When I tried to run the VBS File manually, It comes back with error at line 7 character 2. I don't know what I'm doing wrong, but here the VB code.

Dim shell,fso,file

Set shell=CreateObject("WScript.Shell")
Set fso=CreateObject("Scripting.FileSystemObject")

strPath=WScript.Arguments.Item(0)

If fso.FileExists(strPath) Then
	set file=fso.GetFile(strPath)
	strCMD="powershell -nologo -executionpolicy ByPass -command " & Chr(34) & "&{" &_ 
	file.ShortPath & "}" & Chr(34) 
	shell.Run strCMD,0
End If

from intunedrivemapping.

Hi guys @anaylor130683 @etreater "Script not working" is not a really helpful description for an issue.

• Can you verify connectivity to the network share by manually accessing the share from a test machine?

  • Keep an eye on password / Windows Hello for Business prompts - if you receive them you need to investigate this first

• If you have configured security group filtering verify the output of the following PowerShell function: https://github.com/nicolonsky/IntuneDriveMapping/blob/master/IntuneDriveMapping/wwwroot/bin/IntuneDriveMappingTemplate.ps1#L32 and check if you have line of sight to an Active Directory Domain Controller

@anaylor130683 PowerShell execution policy does not interferer when the script is executed via Intune or scheduled task as both mechanism bypass the execution policy

@etreater the vbscript is only a wrapper to suppress the PowerShell window from appearing. It takes the path of the PowerShell script as command line argument

from intunedrivemapping.

from intunedrivemapping.

@etreater I published a new version of the script and populated the project wiki with some troubleshooting info and details.

Your problem is probably related to the issue that your machines don't have the $env:USERDNSDOMAIN environment variable - you find the required adjustments in the wiki. Just update the $searchRoot variable with your active directory domain name e.g. "intra.contoso.com".

from intunedrivemapping.

from intunedrivemapping.

Then you need to investigate the ‘Get-ADGroupMembership’ function in the script - what does it return in your case? It usually returns all groups (sam account name format) the user is a member of. You also need to specify your group filters with sam account format without any domain prefix. @etreater

from intunedrivemapping.

from intunedrivemapping.

@etreater glad that it resolved your issue. I‘ve also added the sAMAccountName stuff without the domain prefix to the wiki.
Cheers, nicola

from intunedrivemapping.