Start a Conversation

Unsolved

This post is more than 5 years old

22021

June 1st, 2015 09:00

WYSE D90Dd7 Thin Client drops trust relationship

WYSE D90Dd7 Thin Client drops trust relationship

We have a satellite office that runs about 25 of the WYSE D90D7 with Windows 7 embedded. There are 2 these that lose the trust relationship with our domain and have to be dropped from the domain and then added back on. This office is about 100 miles from our main office and having them send it over means they are typically out of that TC for 2 days on what takes 4 minutes to fix.

I searched and came across turning off automatic machine account password, however in reading, that seems a larger risk than we are willing to take.

Does anyone have any solutions to this?

June 1st, 2015 09:00

I can relate as well on this, work in an environment that include sites that only operates on VSAT connections and we have over 90 of these D90D7 systems deployed experiencing the same problems falling off the domain randomly. Of course the sales pitch was delivered that these things can be used as stand-up Kiosk machines and we don't require a VDI environment. Well, now that we speak to Wyse Support, they are surprised that we are not using VDI and they can't seem to understand why we wouldn't. Well, sure, if the company has a VDI Infrastructure and its 100% stable on VSAT connections, then we wouldn't have this problem, right? I don't think that is so easy to compare cause the use of these things is simple stuff, all web base only Kiosk. Our other "Desktop/Laptop" machines do not behave like these things do and they sit in the same location. As a result, I am asked to start from scratch and deploy them out via SCCM. At this point, image is in SCCM, packages I want are loaded and test deployment has been successful. The only thing that keeps us in mind of this problem is the fact we didn't exclude the machine password at C:\Windows\System32\config from the Write-Filter the first time around. Also, I noticed that on several machine's Event log supports failure to apply GPO due to not enough memory, not sure way that 10 GPOs would eat up the entire RAMDISK but whatever. We will be starting with the basics, the golden image is from the USB tool from Dell Wyse. The Capture will be done using SCCM and the deployments will include the base image with 10 relatively small packages 1-1.5GB installed if that and the we will add these to an OU without Inherit GPO from the top Domain. Other speculation during our troubleshooting on our current ones was that these devices were on isolated VLANs where they can't get out to the Internet, Corporate only traffic instead and perhaps routing or form of networking was causing this mess...but I am not so sure.

Any other thoughts? Humor me please.

No Events found!

Top