Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intune does not show script was successful #3

Open
couchcoder opened this issue Feb 26, 2021 · 2 comments
Open

Intune does not show script was successful #3

couchcoder opened this issue Feb 26, 2021 · 2 comments

Comments

@couchcoder
Copy link

I have been able to successfully implement this script and have the script successfully sync the Sharepoint library with OneDrive but Intune shows the script as failed on each computer instead of showing as successful.

@Zonnald
Copy link

Zonnald commented Oct 7, 2021

It appears that when resolving the local $synchpath - the intune tenants path doesn't match the local therefore the Get-ChildItem fails to find any new child objects.

In the case I have been debugging the company tenant name is ACME SOLUTIONS PTY LTD
The sync path includes C:\Users\uname\ACME SOLUTIONS PTY LTD\Documents
The local path however somehow ended up being C:\Users\uname\acme.com.au\Documents

The customer explains that he wanted acme.com.au but was pushed(?) to use ACME SOLUTIONS PTY LTD

So using this script happily creates the share and syncs it but because the local resolution of the path is different to what Intune uses. As there is no child item this while loop never finishes.

When run on Intune manager I guess it eventually kills the process so the log indicates no success. or Failure

@Zonnald
Copy link

Zonnald commented Oct 8, 2021

I found that the issue was the user of the $ENV:ONEDRIVE environment variable. then stripping off the last folder name with the SPLIT-PATH command. It was then concatenated with the $UserUpn.HOST value which was there the acme.com.au came from.
The workaround was to do the SPLIT but hardcode the next part of the path to match what the local drive was using (ACME SOLUTIONS PTY LTD). Hopefully, I can resolve this in a more elegant way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants