1. October 2020 at 14:03 #53178
I’ve just tested 8.6_511 and now get a message at the logon screen stating configurations are from an unsecure source.
I noticed the below in the release notes, but wondered how to turn off the message or better yet fix it? My WMS server is in Dell hosted (https://eu1.wysemanagementsuite.com) and is a secure https URL to our tenant.
Any ideas before I roll this out to production?
Security messaging has been expanded to warn users when client configurations are obtained from an insecure source.1. October 2020 at 14:47 #53180
Also saw this.
to your WMS policy under Advanced.
CG1. October 2020 at 15:32 #53193
Thanks for the suggestion.
That doesn’t seem to have made any difference to the message at the logon screen.
2 items configured
No Global INI
Baseline Configuration 8.6
SignOn=yes EnableMessage=no1. October 2020 at 15:35 #53194
Strange as it is working for several others.
Post your full wms.ini as can be found on the client under System Tools.
CG1. October 2020 at 17:26 #53200
I cant post for some reason11. October 2020 at 10:26 #53238
We are experiencing the same issue with 8.6.511 and trying to remove the security popup on login, currently running on-prem WMS 3.0 and tried to add the “SignOn=yes EnableMessage=no” in advanced and the WMS.ini no reference at all.11. October 2020 at 11:42 #53240
What do you mean by „no reference“?
CG11. October 2020 at 11:53 #53245
When I look in the WMS.ini on the thinclient I was excepting to see reference to the what we put in advanced section on the console, example “SignOn=yes EnableMessage=no”.
Thanks11. October 2020 at 12:04 #53251
Post your WMS.ini
CG11. October 2020 at 12:05 #53252
TimeZone=”GMT + 10:00″ ManualOverride=Yes TimeZoneName=”Australian Eastern Standard Time (AEST)” DaylightName=”Australian Eastern Standard Time (AEST)” TimeZoneName=”AUS Eastern” daylight=Yes start=100107 end=040107
Signon=Yes SaveLastDomainUser=no LastUserName=No
TimeServer=xxxxxxxx DateFormat=dd/mm/yyyy TimeFormat=”12-hour format”
AdminMode=Yes Admin-Username=xxxxxxxx ShowAdmin=Yes
Privilege=none EnableTrace=No LockDown=No ShowDisplaySettings=No EnableKeyboardMouseSettings=No DisableChangeDateTime=No
SignOn=Yes ExpireTime=0 RequireSmartCard=No SCRemovalBehavior=0 IconGroupStyle=Default DisableGuest=No
MaxVNCD=1 VNCD_8bits=No VNCD_Zlib=No
VNCPrompt=yes accept=10 ViewOnly=No ActiveVisible=Yes
SecurityPolicy=warning SecuredNetworkProtocol=No TLSMinVersion=1 TLSMaxVersion=3 DNSFileServerDiscover=Yes TLSCheckCN=Yes
Screen=1 Resolution=DDC Rotate=None refresh=60
device=mtouch mult_touch=No mult_jitter=30
Dualhead=Yes Mainscreen=1 Align=Bottom Swap=No Taskbar=mainScreen Orientation=hort MonitorAutoDetect=Yes
ScreenSaver=180 LockTerminal=0 Type=0 PictureTimer=6 PictureOrder=Default PictureCheck=Default PictureLayout=stretch Sleep=0 Unit=No
Screen=2 Resolution=ddc refresh=60 rotate=none
desktop=”Staff Screensaver 3200×1800-TAFE-ENTERPRISE4.png” layout=Stretch
SysMode=VDI Toolbardisablemouse=no Toolbardelay=0 toolbarautoquit=Yes Toolbar_no_conmgr=No Toolbardisablehotkey=No ToolbarEnableOneSession=No toolbarstay=1 toolbarclick=No ToolBarAutoQuit=No EnableLogonMainMenu=No
host=xxxxxxx SecurityMode=low ConnectionType=PCoIP AutoConnectList=”” EnableUnAuthenticatedAccess=no
unmapprinters=no unmapserials=no smartcards=no disablesound=no mapdisks=no disksreadonly=no unmapusb=no VUSB_DISKS=yes VUSB_AUDIO=no VUSB_PRINTER=no VUSB_VIDEO=no MultiMonitor=yes FullScreen=yes ondesktop=all
KeySequence=yes Ctrl+Alt+Del=yes Ctrl+Alt+Up=no Ctrl+Alt+Down=no Ctrl+Alt+Left=no Ctrl+Alt+Right=no Win+L=yes Alt+Tab=no
EnableLocal=yes11. October 2020 at 12:12 #53257
And please a screenshot of your Advanced section
CG11. October 2020 at 12:17 #5325811. October 2020 at 12:23 #53259
Dumb question, but re you sure the client is in the correct group?
None of your advanced settings can be found in the WMS.ini.
CG11. October 2020 at 12:34 #53260
You are spot on, I was excepting to see them normally in the end of the WMS.ini. They are 100% in the correct group, I am checking the group tokens and create a new Group as we have recently upgraded from 2 -3. Something is not working correctly, I know the token must change in release 3 of WMS.11. October 2020 at 20:01 #53263
Old tokens will still work.
Only new tokens have to be complex.
Do you see the client checking in to WMS?
Could you post the client’s eventlog?
- You must be logged in to reply to this topic.