Quantcast
Channel: Wyse and Windows Embedded Standard (WES7, WE8S) - Recent Threads
Viewing all 77 articles
Browse latest View live

Wyse D90D7 Image not consistant

$
0
0

I create a image on USB keys a few years ago that work great.  Now I just created a new set of USB keys for a new batch of D90D7's and having 2 issues with them. 

The first is was the we can appear to join the domain just fine but can log on when looking can see the unit does not join fully.  (Domain Administer User is SID and not "Admin User"), we can remove the client from the domain, wait a few hours and then it will reconnect.

The 2nd issue, is that it appears that the image when re-flashed to the unit does not seem to fully flash the unit, it just appears to be.  I have tried with write filter on and off, no difference.

Steps:

Take image of original, make changes to images, save pre sysprep image, run sysprep, pull image, and the push the image.   All the steps appear to finish correctly.

Any assistance would be appreaciated.


Enable 802.1x on WES7 D90D7

$
0
0

We are just beginning to test 802.1x in our environment, and while I can manually configure to test, does anyone have a recommendation to configure via WDM script or otherwise?  (Beyond setting the dot3svc service to automatic.)

Problems with File Based Write Filter on Latitude 3460

$
0
0

I have a batch of Latitude 3460's with WES7 64 bit installed.  As part of the deployment to end users these are customized by means of local group policy lock downs, wallpaper changes, region and language changes, the VMWare apps removed, Teamviewer and a printer driver installed.  As you can imagine doing this manually one by one is time consuming so I have used MDT 2013 to sysprep and capture a configured 3460 (the FBWF is disabled at this point) and then created a standard client install task sequence in MDT to deploy the captured image.

Everything works fine until I come to enable the FBWF after deployment.  I am running a batch file with the following contents (the exclusions taken from a configured 3460 before sysprep):

bcdedit /set {default} bootstatuspolicy ignoreallfailures
fbwfmgr /enable
fbwfmgr /addvolume C:
fbwfmgr /addexclusion C: \Wyse\WDA
fbwfmgr /addexclusion C: \Wyse\WCM\ConfigMgmt
fbwfmgr /addexclusion C: \Users\Public\Documents\Wyse
fbwfmgr /addexclusion C: "\Program Files\Wyse\WDA\Config"
fbwfmgr /addexclusion C: \ProgramData\Microsoft\eHome
fbwfmgr /addexclusion C: \Windows\Temp\MpCmdRun.log
fbwfmgr /addexclusion C: \Windows\WindowsUpdate.log
fbwfmgr /addexclusion C: "\ProgramData\Microsoft\Windows Defender"
fbwfmgr /addexclusion C: "\Program Files (x86)\Windows Defender"
fbwfmgr /addexclusion C: "\Program Files\Windows Defender"
fbwfmgr /addexclusion C: \Windows\CCM\clientstate.dat
fbwfmgr /addexclusion C: \Windows\CCM\wedmtrace.log
fbwfmgr /addexclusion C: \Windows\SMSCFG.ini
fbwfmgr /addexclusion C: \Windows\CCM\ServiceData
fbwfmgr /addexclusion C: \Windows\CCM\StateMessageStore.sdf
fbwfmgr /addexclusion C: \Windows\CCM\InventoryStore.sdf
fbwfmgr /addexclusion C: \Windows\CCM\ComStore.sdf
fbwfmgr /addexclusion C: "\Program Files\Ericom PowerTerm WebConnect"
fbwfmgr /addexclusion C: \Users\Administrator\AppData\Roaming\Eircom
fbwfmgr /addexclusion C: \Users\User\AppData\Roaming\Eircom
fbwfmgr /addexclusion C: \WebConnect
fbwfmgr /addexclusion C: \Users\User\AppData\LocalLow
fbwfmgr /addexclusion C: \Users\Administrator\AppData\LocalLow
fbwfmgr /addexclusion C: \Regfdata

When I reboot I get the following message:

[IMG]s15.postimg.org/.../IMG]

If I then open explorer in the background, disable the filter, reboot, run the above batch file again and reboot the filter works at expected from that point on.  There is no pattern to this either as on a couple of occasions I have had to disable and run the batch file 3 or 4 times to get it to kick in and on another I've been able to run the batch file while the message above was displayed, reboot and it kicks in.  I feel like I'm missing a step but can't figure out what and looking for help.  I have tried to speak to Dell on this but I'm struggling with their support as I am being transferred between different departments several times and nobody seems to understand what Windows Embedded or a write filter is.

Any ides?

Uninstall Lync 2013 vdi

$
0
0

Hi, i cant find any solution for uninstall LYNC vdi client from Wyse WES7 terminal. When Lync installed, users cant use hotkey like alt + tab and other in citrix (receiver) sessions.

pls anybody for any solution.

Thx

Problem registering latest WES7 image through WDM 5.7

$
0
0

Hi all,

Hopefully someone can offer some insight.

We have 6x D90D7’s currently on the bench for testing. I have installed WDM 5.7, everything running fine. All repo’s up and green.

Started out discovering the devices, that went smoothly. Then, due to my lack of knowledge i attempted to push out a configuration i had created in Configuration Manager and managed to upload to WDM, however that failed.

Did some research and found that i needed to update the Boot Agent, HAgent and WCM Agent. Boot and HAgent updated with no problems. Tried to register WCM Agent 1.4.2.0 using PkgRegister.exe but that failed. Registered ok using the wizard on locally installed WDM and was showing up in Other Packages.

Attempted to push that out and file was copied to the ThinClient (C:\Temp) but nothing else happened, i had to run the app manually. Afterwards WCM was up to version 1.4.2.0.

Tried to push out the configuration i had created, again, with no success.

Found an updated WES7 image from the dell site, BDB0_0895_16GB.exe.

Tried registering this using Web UI and the local Device Manager console and while they show that the process completed, nothing ever appears in either Web or local app. I can see the folder gets created in C:\inetpub\ftproot\rapport\ but nothing ever appears in there, so there is nothing to push out.

I have also tried extracting that file as it comes in the form of a 7zip executable, but running this on Server 2012 errors, stating incorrect OS.

The clients are obviously connecting to the WDM server otherwise the initial updates of HAgent and BootAgent wouldn’t have gone through. I have also managed to successfully pull an image from one of the D90D7's.

What am i missing? Documentation is extremely scarce and the standard guides do not deviate from a perfect scenario.

I’m sure there is a lot of detail i have neglected to include, but please ask, i’ll be happy to provide it.

Thanks in advance

Wyse 5010 thin client

$
0
0

I have just acquired some 5010s with WES7.

They all seem to be constantly using up ~25% of their CPU capacity with system interrupts which is making them sluggish.

I've tried turning off as many services as I can without bricking it, but nothing seems to affect it. None of the listed processes seem to be using it.

This happens out of the box with not alterations made.

Anyone got any ideas as to what is causing these interrupts and how to stop them?

Thanks

Guy

Problem configuring Receiver 4.4 on Windows Embedded with WCM

$
0
0

Good afternoon chaps,

We have some Thin Clients on the bench in the lab for testing. They're Dell\Wyse D90D7's or 5010's, same thing, running Windows Embedded 7 Standard.

We're almost there with regards to configuration. We'd like to have them boot straight past the Embedded OS and load Citrix in appliance mode. Unfortunately i cant seem to get the Account to load properly.

We're using Wyse Configuration Manager v1.5 to create config files that are pushed out from the WDM server. There are options for the type of connection to Citrix; XenApp, XenDesktop, Storefront and Gateway. I have attached a screenshot of the WCM options.

In summary:

Choosing Storefront or Gateway, and entering the FQDN of the SF server or the FQDN of the NS yields the same result. An error comes up stating "Cannot connect to DWCM-Citrix" (DWCM-Citrix is the name the account is given when setup from the config file.

Entering either of the FQDN's manually on Receiver works fine, for both SF and NS.

The end goal is to have users log in to the Windows Embedded device which runs Citrix Receiver in appliance mode, with SSO, so user get passed straight over to their relative sessions.

Is there any other way to set the accounts in Receiver for all users? These Thin Clients have a Write Filter so any changes made will need to be done by the local admin account. So i'm thinking it's likely to be a registry setting of some sort.

Does anyone have any experience with setting up Receiver from WCM?

Any ideas would be greatly appreciated.

ZX0 - Wyse - WES7 - Camera drivers

$
0
0

Masters,

 I really need your help - i have no more hair.. -
 We have a few Zx0 wyse with WES7 and some old Nikon Coolpix camera.
 We try to copy images from camera to Windows server, so we plugged it to Wyse but windows not recognised.

 How to install drivers for camera because we can't find any on Nikon site....

Regards


Z90QQ7P identifies to self and WDM as D90Q7P

$
0
0

This is a curiosity but so far doesn't seem to matter operationally.

I have a Z90QQ7P unit that self-identifies (Client Information screen) and shows in WDM as being a D90Q7P.  The label has the correct serial and MAC and reads Z90QQ7P 909805-01L.  The unit is physically quite clearly the Z90QQ7P model.

Any idea why the internal identification is mismatched?

Where is the download site for Windows 10 IoT Enterprise for 7020 thin clients?

$
0
0

I just obtained a few Dell/Wyse thin clients, one of which is a 7020 with the Win10 IoT license.  I don't see images for this unit on the usual Wyse download site.  Can someone explain where it is or how it is supposed to be re-installed?

WDM 5.7.2 - Help!!

$
0
0

Hi all,

It's a long story so i'll bullet point:

  • Downloaded latest image (9..097064.15GB) including fixes for WannaCrypt exploits.
  • Had to update from WDM 5.7.1 to 5.7.2 to manage the new image.
  • Latest image comes with WDA 12.1.1.25, which appears to include HAgent, although i would appreciate confirmation of this....
  • WDM 5.7.2 no longer has a HAgent package for installing.
  • Latest image came with Boot Agent 3.4.4.
  • Latest image didn't come with WCM Agent installed so I've tried multiple versions (1.3.3, 1.4.0.3, 1.4.2.0)
  • None of the versions of WCM Agent i have tried will allow me to push a config from WDM. I always get an error.
  • I tried importing XML manually but when pressing the Import button WCM Agent crashes in all versions with the WDA 12.
  • I've tried numeours versions of the Configuration Manager too. 
  • I have since tried the latest version i could find on the web, WDA 13. Still no joy. 

I have since rolled back to the previous image (9.080895.15GB), but nothing seems to want to push from WDM 5.7.2. It usually will do the first reboot then sit there logged in as the local user with the write filter off and the job never seems to error. I have to delete it manually.

I'm about to delete the WDM server and rebuild from scratch with 5.7.1. 

My question is, does anyone know which versions of WDM work with WDA, HAgent and the Boot Agent. It seems to me like we need to match each of these elements specifically or nothing works.

I've spent the past two weeks, in and out of work hours, trying to get my head around this. It's seriously putting me off buying Dell/Wyse Thin Clients in the future! The lack of support and documentation, on top of the numerous agents and incompatible versions of everything is soul destroying.

Does anyone know how this is supposed to work?

All i want to do is have the devices boot in to the default user account but in Citrix Applicance Mode and have the account already setup so all the user has to do is login to Citrix. Should be pretty simple really....

Wyse D90D8 unable to format internal SSD

$
0
0

Wyse D90D8

SSD is a half module SATA ( Apacer 8Y.F1CD4.LR25B ) 16 gigs mlc - default factory installed.

(it all fails to wipe the disk / repartition)

I've tried connecting it to another computer , use linux boot disk (easeus or minitools partition tools , winPE using diskpart command) Active Boot Disk - it all fails.

Its like the SSD has some write lock - i can't even restore to factory -

Any ideas how to overcome this ? I have several of these in the company but im unable to clean the disks to install something else instead of Win8 which doesn't fit our needs at this moment.

Wyse 5010 No WDM/WCM icons in control panel...

$
0
0

I just bought a bunch of Dell Wyse 5010s to replace some D90D7s. I do not see any WDM or WCM icons in Control Panel like I would see with the D90D7s. Is that normal? Normally I would manually get them to check in since I do not have access to DHCP options.

Best practice for WES7 Thin Client

$
0
0

Hi,

Been looking around for best practice implement WES Thin Client, and still confuse :

  1. Is it recommended to join thin client to domain ?
  2. If so how do we automate it - hear about sysprep, where can i find documentation about it ?
  3. I'm using D90D7 16G/4G cant find c:/windows/setup/sysprep

Every documentation refer to Wyse KB 21514, but still i find it not very clear

Wyse Thin Client X90M7

$
0
0

Hello to all, maybe I can get some help.

I have a Dell Wyse X90M7 thin client laptop, I turned my laptop on and my screen went to the Bios screen and did not load Windows 10.

I have no idea what happened so I went to the support sites to get help and eventually downloaded the firmware tool. I went through the process with the tool I found the right clicks to select what I used to have in my thin client ( I THINK ).

I have a sandisk cruzer 16GB flash drive and after my flash drive had an image on it I plugged it into my thin client and turned it on and nothing was being extracted to my thin client.

I am not a real good Dell Techie but I understand some stuff, but I need help to reimage my thin client.

I hope some one can advise how to do this so I can get my thin client laptop working again.

Thanks to all in advance

Ernest Sauer


D90D7 WES7 screen lag when dragging explorer windows

$
0
0

using WES7, with more than 1 explorer window on screen if we drag a window anywhere around the  screen we get lag and ghosting  - the screen quickly refreshes to remove it but it is noticeable and appears to be following through to the citrix VDi's too.  Our original build did not do this but we have installed so many windows updates, flash updates, HA agent updates etc over the last 2 years could one or more of these be to blame ?  are we better off just getting the latest WES7 build for the device and starting afresh ?

thanks

WCM XML parameter

$
0
0

Hi,

Have been successfully create xml by exporting from existing wyse device, but looking to setup it further. Where can i find the documentation for WCM XML parameter like below ?

<timeZone>
<standardName>SE Asia Standard Time</standardName>
<daylightName>SE Asia Standard Time</daylightName>
<bias></bias>
<daylightBias></daylightBias>
<standardBias></standardBias>
<timeServer>time.windows.com</timeServer>
</timeZone>

Viewing all 77 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>