Forum Replies Created
-
Posts
-
Hi Conf,
I have tried all the possibilities to upgrade D10D,D10DP PCoIP to the latest OS. Dell website listing 4 to 5 OS’s but none of them are being pick up by the PCoIP devices.
BIOS: ThinOS 8.6_024 BIOS package for Dell Wyse 5010 thin clients with PCoIP.
ThinOS 8.6_206 English Raw Image file for Dell Wyse 5010, 5040 and 7010 thin clients with PCoIP
Operating System
22 Nov 2019ThinOS 8.6_013 English Merlin Image file for Dell Wyse 5010 thin clients with PCoIP
Operating System
16 Jan 2019ThinOS 8.5_024 English Raw Image file for Dell Wyse 5010, 5040 and 7010 thin clients with PCoIP
Operating System
19 Dec 2018ThinOS 8.5_009 English Merlin Image file for Dell Wyse 5010 and 5040 AIO PCoIP thin clients with 8 GB flash
Operating System
28 Aug 2018ThinOS 8.5_009 English Merlin Image file for Dell Wyse 5010 and 5040 AIO PCoIP thin clients with 4 GB flash
Operating System
28 Aug 2018ThinOS 8.5_009 English Merlin Image file for Dell Wyse 5010 and 5040 AIO PCoIP thin clients with 2 GB flash
Operating System
28 Aug 2018Appreciate your help.
Regards,
Hi All,
the problem solved by capturing one of the AIO 5040 and pushed the image to the corrupted AIO 5040 device.
Thank you very much for your great support.
Regards,
HI Conf,
I have tried using the USB Imaging Tool 3.0 to capture one of the AIO 5040, but when I tried to boot from USB on one of the devices, I’m not getting the Boot from USB. Even though the Boot from USB option in BIOS is enabled and Boot from USB in boot option is set at top.
Regards,
Hi Conf,
The 5040 using 8.2 ThinOS version and I managed to upgrade using your file.. Now almost all my 5040 AIO devices are able to get the file OS file and Bios file using WDM
C:\inetpub\ftproot\Rapport\WTOSCONFIG\WNOS
PD10_wnos
ZD10_wnos
I have only one of the 5040 which is getting the PXE stage, but I’m unable to get it the OS installed on it. My colleague has formatted and I don’t know how to bring it back up again.
Appreciate your help on this.
Regards,
Hi Guys,
I’m stuck with AIO 5040, I have tried all images, always getting these type of messages;
NBP is too big to fit in free base memory.
File is too big.
Appreciate your help.
Regards,
Hi Conf,
The issue resolved by upgrading the firmware to the latest version 8.2..
Now I’m able to connect to vWorkspace connector and launching desktop..Thanks for your help.
Hi Conf,
Heres’ the details;;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator 7.4.01 *
;* Copyright by Thomas Moellerbernd *
;* *
;* https://technicalhelp.de *
;* *
;*************************************************************;*************************************************************
;* General 1 *
;*************************************************************autoload=2
AdminMode=yes Admin-Username=OECFONCBOK Admin-Password=OIHMLHCDPFCEOEDD
Privilege=None Lockdown=yes HideSysInfo=yes HidePPP=yes HidePN=yes HideConnectionManager=yes ShowDisplaySettings=Yes EnableKeyboardMouseSettings=yes SuppressTaskbar=auto;*************************************************************
;* General 2 *
;*************************************************************Locale=English
EnableGKey=yes
MirrorFileServer=yes
FormURL=vWspform.jpg;*************************************************************
;* General 3 *
;*************************************************************AutoSignoff=yes
SysMode=VDI toolbardisablehotkey=yes;*************************************************************
;* Peripherals *
;*************************************************************Language=ar_bah
KeySequence=yes Ctrl+Alt+Del=yes Win+L=yes
MouseSpeed=1;*************************************************************
;* Display *
;*************************************************************; If you are using a version of WTOS code < 7.0.1_13 please use:
; Resolution=DDC Refresh=
Screen=1 Resolution=DDC
Desktop=Wallpaper.jpg Layout=Center
Screensaver=15 LockTerminal=yes Type=1 PictureTimer=6;*************************************************************
;* Time *
;*************************************************************Timeserver=192.168.10.22 Timeformat=”12-hour format” Dateformat=dd/mm/yyyy
TimeZone=’GMT + 03:00′ ManualOverride=yes Daylight=yes Start=030507 End=100507 TimeZoneName=”Arab Standard Time”;*************************************************************
;* Network *
;*************************************************************Device=Ethernet Speed=”Auto”
VDIBroker=http://ServerName.Domain.Com:8080
ConnectionBroker=vWorkspace vwsxmlenable=yes EnableVWGateway=No
SignOn=Yes
DomainList=”xxx.com”
MaxVNCD=1
VncPassword=”OIHMLHCDPFCEOEDD” Encrypt=yes
VncPrompt=Yes Accept=10;*************************************************************
;* General Session *
;*************************************************************SessionConfig=ALL UnmapPrinters=no VUSB_AUDIO=yes VUSB_VIDEO=yes VUSB_PRINTER=yes Resolution=default FontSmoothing=no
UniSession=yes;*************************************************************
;* RDP *
;*************************************************************SessionConfig=RDP AutoDetectNetwork=yes Dragging=no EnableGFX=no EnableRdpH264=yes USBRedirection=RDP
Thanks for your fast reply CG. Is there way around that? Does the ThinOS works on laptops and I can manage them with WDM?
The idea around that to convert the laptops to a dummy fully functional devices where users cannot miss around with it and at the same time I can manage them.
Appreciate your reply.
Regards,
