Forum Replies Created
-
Posts
-
I just ran across this issue with a new 5070 image I’m building and thought I’d offer this tip:
First, I deleted the file C:\Wyse\OOBE\OOBE_First_Boot.bat. Unfortunately, upon restart, the User account bounced back to the logon screen every time it attempted to log on. Not ideal.
I poked through the Application log and found that the logon process was trying and failing to run that file. To fix it, I just edited the Userinit value in the registry.
Go to the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Open the string Userinit and remove the path “C:\Wyse\OOBE\OOBE_First_Boot.bat”
Reboot and you will never see the Quick Launch again.
Thanks for your reply. That is too bad.
I’ve been poking around in the UWF docs, and I was going to try a workaround with a logoff script that would commit certain settings, but according to comments I found on github, it appears to be unwilling to touch HKCU settings even on a manual commit.
Oh well – users are going to just have to unpin the connection bar every time they log in. 🙂
Thanks,
ChrisI do not believe it can be done legitimately, no.
Beware that there are some people selling Wyse 5070 Windows thin clients on Amazon for extremely low prices. I bought one to test a few months ago when we were having issues with Dell not being able to supply enough for our order.
What I received was originally (by the service tag) a ThinOS thin client, but the seller had removed the flash drive, installed a blank SSD, and installed a (probably pirated) copy of Windows 10 Home. Not useful as a thin client, unfortunately.
