I’m pretty sure there’s more to what you’re trying to do than just moving the ISO to the user’s desktop folder.
To get to the user’s desktop folder, you’d need to use a relevance expression - for instance a Relevance expression like I illustrate at Tip - Action Override User settings
parameter "UserFolder"="{(preceding text of first "|" of it | it) of concatenation "|" of profile folders of users of logged on users whose (active of it)}\MyBESContent\{id of action as string}"
However, this has a lot of limitations -
- You need to ‘copy’, not ‘move’, the ISO to the user’s folder, since otherwise it would retain the Administrator-only permissions from the __BESData folder where it was downloaded.
- You need to change all of the ‘wait’ commands with overrides to run in the current user’s context if you’re trying to display messages to the user.
- The fixlet as-written doesn’t require any user input, so while they might see commands running, they shouldn’t be able to interact with it.
- If you apply the overrides to run in user context, there must be a user logged on. They probably also need admin rights.
- You need to override the batch commands for wherever you want the ‘SetupComplete.cmd’ batch to end up.
- You have to pay attention to what other areas of the actionscript are doing - for instance the line
waithidden cmd /C rmdir /S /Q "{parameter "workPath"}"would delete your user’s Desktop folder if you’re just changing the value of “workPath” to be the user’s Desktop folder - As the upgrade uses sysprep and possibly USMT to migrate user profiles beween the original and the new Windows installation, I’m not sure if it’ll even work with the ISO in the user’s profile.
The Win10 upgrade fixlets can be difficult to build and troubleshoot - I’d advise against changing the default scripts unless you fully understand the process and have a specific problem you’re trying to work around.