- This topic has 1 reply, 2 voices, and was last updated 3 years, 3 months ago by
ConfGen.
-
AuthorPosts
-
June 4, 2021 at 9:49 pm #105527
Hello,
I am hoping someone might be able to point me in the right dimension. My company has ~150 dell/wyse thin clients in production, they are all either newer 3040’s or T10’s. I have included the default ini file below. My issue is that some users report that each morning they have to hard power (either by holding the power button or pulling the power cord) their units before they receive anything on their screens. My belief is the units are failing to wake up after “sleeping” or failing to output video to the monitors. This does not happen to all units, only a subset but there doesnt seem to be much rhyme or reason to the issues. We have tried multiple different brands/models of monitors, have verified it isnt power or network related, seems to be the clients themselves. I should also note they are all on at least 8.3 of thinOS.
I have tried adding the following line to force reboots on the units but that doesnt seem to correct the issue: “reboot=yes Time=06:00-7:15 Idle=30 Wday=Monday,Tuesday,Wednesday,Thursday,Friday”
Once the units have been powered down and then back up everything works as expected. What am I missing here? Thank you much!
;*************************************************************
;* General 1 *
;*************************************************************
Autoload=101 VerifySignature=no;*************************************************************
;* Peripherals *
;*************************************************************
;
Language=UsInclude=$mac.ini
;*************************************************************
;* Display *
;*************************************************************
;
; If you are using a version of WTOS code < 7.0.1_13 please use:
; Resolution=1280×768 Refresh=Screen=1 Resolution=1920×1080 Rotate=None
DualHead=NO
;*************************************************************
;* Time *
;*************************************************************
;
TimeZone=”GMT – 08:00″ ManualOverride=Yes Daylight=Yes \
Start=031421 End=110721 TimeZoneName=Pacific \
DaylightName=Pacific;*************************************************************
;* Network *
;*************************************************************
;
;
VDIBroker=redacted hostname
ConnectionBroker=Microsoft
NoGlobalini=NO
EnableGKey=Yes
AdminMode=NO
Privilege=High EnableTrace=NO
SignOn=No
MaxVNCD=1
VncPassword=”****”
VncPrompt=No
DomainList=”redacted”;*************************************************************
;* RDP *
;*************************************************************;————————————————————-
;- RDP Session 1 –
;- Each line but the last must end with a ‘\’ –
;————————————————————-CONNECT=RDP \
Host=redacted hostname \
Description=”redacted” \
AutoConnect=YES \
Domainname=redacted\
Reconnect=10 \
Colors=true \
Fullscreen=yes \
LocalCopy=noSessionConfig=RDP \
EnableNLA=No \
EnableRecord=NO \
ForceSpan=NO \
EnableTSMM=yes \
EnableGFX=NO \
EnableVOR=yes \
EnableRdpH264=yes \
WallPaper=NO \
Dragging=Yes \
Animation=NO \
Theme=NoSessionConfig=All \
DefaultColor=2June 7, 2021 at 12:00 pm #105534A few questions:
– why are you adding the RDS broker to your wnos.ini and then do not SignOn to it (SignOn=no)? If you are just using the one RDP session, then you can remove the broker
– The units are never shut down, correct?
– Are you able to Ping the units when they are failing?CG
-
AuthorPosts
- You must be logged in to reply to this topic.