- This topic has 8 replies, 3 voices, and was last updated 7 years, 2 months ago by
.
-
Posts
-
We are using WDM 5.5.1. We used to be able to reboot terminals without issue, but, suddenly not. I cant pinpoint what changed. What’s odd is, if I send a reboot command to a terminal, the device does nothing. It just sits there. If I manually go and rbeoot the terminal, upon startup, it does the restart I sent previously.
Functions like remote shadow works no problem.
We’re going to 5.7.1 soon, but, won’t know if that’s a resolution until we go to it.
As you describe it, this sounds like WDM is scheduling the reboot package successfully.
However, either the client never receives the update, WDM does not send the notification out or the client just does not react.
At reboot of the client, it is checking in to WDM. Therefore, it receives the package information and executes it.
This leads me to reason #1 – client does not receive the update notification for whatever reason.
You can simulate this by right clicking the device and select “Refresh Device Information” after scheduling the reboot. That way the client will also reboot.
Maybe a network trace will sched some light on this issue. Just to see if WDM is sending out the notification or the client does receive this.CG
Not sure it means anything, but, when I right click and hit reboot, WDM kind of hangs for a few seconds. The mouse turns into an hourglass, but then comes back. The same hiccup happens when I did refresh device information.
Doing, in order, reboot device, then refresh device information, did not reboot the terminal. Rebooting the terminal manually though, as usual did do it.
I’ll poke around with some network traces though. See what I might find. This definitely worked once upon a time, when the environment had less of a count, but, I doubt that should matter.
I should clarify these are 5010 D10DP Models. Below is our wnos.ini. As I said this used to work fine, the reboot function, and I don’t recall making changes to the ini in between these 2 periods, but, I could be forgetting something. Just thought I’d post it.
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator 6.3.06 *
;* Copyright by Thomas Moellerbernd *
;* *
;* https://technicalhelp.de *
;* *
;*************************************************************;*************************************************************
;* General 1 *
;*************************************************************autoload=1
AdminMode=yes Admin-Username=REMOVED Admin-Password=REMOVED
Privilege=None Lockdown=yes
MirrorFileServer=yes;*************************************************************
;* General 2 *
;*************************************************************FormURL=logo-new_vdi_V10.jpg
;*************************************************************
;* General 3 *
;*************************************************************Autopower=yes
AutoSignoff=yes Reboot=yes
Shutdowncounter=10
SysMode=Classic toolbardelay=0 ToolbarStay=1
AddCertificate=REMOVED.crt
AddCertificate=REMOVED.cer;*************************************************************
;* Display *
;*************************************************************DeskColor=”0 51 102″
Desktop=REMOVED.jpg
Screensaver=10 LockTerminal=no Type=3 PictureTimer=10 PictureCheck=always
;Screensaver=”0″ LockTerminal=no Type=2 Image=REMOVED.jpg
Dualhead=yes MonitorAutoDetect=yes;*************************************************************
;* Peripherals *
;*************************************************************Device=audio Volume=25
;*************************************************************
;* TCX *
;*************************************************************TCXLicense=REMOVED
;*************************************************************
;* Time *
;*************************************************************TimeZone=’GMT – 05:00′ ManualOverride=yes Daylight=yes Start=030207 End=110107 TimeZoneName=”Eastern Standard Time” DayLightName=”Eastern Daylight Time”
;*************************************************************
;* Redirection *
;*************************************************************Device=vusb ForceRedirect=0x0911,0x0c1c,0x01,0x01,0x00
;*************************************************************
;* Network *
;*************************************************************Device=Ethernet KeepAlive=600
VDIBroker=REMOVED
SignOn=Yes
DomainList=”REMOVED1, REMOVED2″
PasswordServer=REMOVED
MaxVNCD=1
VncPassword=”REMOVED” Encrypt=yes
ConnectionBroker=VMware Securitymode=None
OneSignServer=https://REMOVED KioskMode=yes TapToLock=0 AutoAccess=VMW EnableFUS=yes SecurityMode=Full
SessionConfig=PCoIP USBRedirection=PCoIP;*************************************************************
;* Wireless / 802.1x *
;*************************************************************IEEE8021X=yes network=wireless access=WPA2-ENT eap=yes eaptype=EAP-PEAP peapeap=EAP-MSCHAPV2 peapmschapun=REMOVED peapmschappwdEnc=REMOVED peapmschapdm=REMOVED
Device=Wireless Mode=Infrastructure SSID=REMOVED RoamSensitive=Medium DisableBand=2.4G DisableWLAN=EnetUp;*************************************************************
;* General Session *
;*************************************************************SessionConfig=ALL MapDisks=yes DisableSound=No
;*************************************************************
;* RDP *
;*************************************************************SessionConfig=RDP DefaultColor=2
Include=$mac.iniDo you have any idea what port number is needed to open?
I am facing the similar problem on a remote site and I think it is blocked by the firewall.
Communication between server and client is done through port 80 and 443.
There are several other ports, eg. for VNC.
You can find a complete list in the WDM documentation (admin guide or install guide).CG
- You must be logged in to reply to this topic.