Packages can’t be delivered to Standard User account on WES7

  • This topic is empty.
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #6860
    • Total Post: 6
    • Newbie


    I’m new to the WYSE environment, but so far I’ve been playing with it and it seems really neat and simple to use once you get the hang of it! I apologize in advance if this is a known issue or simple…but I’ve been racking my brain scouring the web for answers.

    So after figuring out how to deliver packages and build scripts and such, I started testing them on 2 devices- we have 1 WES and 1 WES7. Neither of them will be joined to our domain where I work.

    I wrote a batch file for adding shared printers- it logs into our print server, adds the printer and sets it as default.

    The Rapport script just pushes the batch file to the Z: drive on the device then runs it and deletes it when finished. I can get the script to work on the user account on the WES machine, but not the WES7. Of course since it is just the “standard user” account, I can’t even execute the script line by line to see if it is even pushing the file (can’t view Windows Explorer).

    Logged in as the local admin account, it works fine- it moves the file and executes the batch file. To test, I changed the “standard user” account to an “administrator” account in User Control, but that doesn’t change anything either.

    Is the WES7 user account more locked down than the WES user account? Or why would this work on one device and not the other? Sorry, this got longer than I thought it would…but I thought it’d be good to give all the details of what I’ve tried so far.

    Thanks in advance

    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    Can you post your WDM script?


Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.