Forum Replies Created
-
Posts
-
Sorry I read it to fast and didn’t fully read the screen shot you put in there. Ignore my post since I can’t erase it.
Are you one server 2016 or 2019 and use SCCM? I found out wms uses SCCM port and had to change the port in : C:\Program Files\DELL\WMS\Tomcat-9\conf\server.xml.
I ask Dell what was recommended to change it to and they wouldn’t really give me an answer.
Sorry I didn’t get back to you but, I did upgrade one of my test servers with no problems.
I have not yet. But I will post here my results when I get a chance.
Not in any of my experience. I’ve made many WMS test servers and the database is in the main upgrade or install file.
Just an FYI if your running on prem and using Windows 2016 or 2019 server and use SCCM I found that that after I installed 3.3, the tomcat server wouldn’t stay running. I figured out that SCCM uses port 8005 and so does the tomcat server.
You can change it here C:\Program Files\DELL\WMS\Tomcat-9\conf\server.xml if you need to. Dell doesn’t have a recommended port if that one is being used.
I had to use this format 0x0c273bfa030101 or 0x0c273bfa instead of this 0x0c27,0x3bfa,0x03,0x01,0x01. The old format wouldn’t work with Imprivata for my testing. I had gotten Dell involved and I was told not to use the comma format and bingo everything worked.
I asked for a product improvement on to get a setting to remove the float bar but haven’t heard or seen anything regarding it. Additionally I asked for that during the 2 betas but I think it just fell on deaf ears.
Will it boot to the point you can’t get into the bios? If so can make a bootable thumb drive using Dell Wyse USB Imaging Tool 3.4.0. If it is not getting to the Dell splash screen I have to warranty or toss them.
Let us know how that goes please. I tried over a year ago and we couldn’t find any that were longer.
Hello,
I’m not sure if this will help but I migrated to WMS a few years ago but I had to turn off no global ini in the advanced settings then I put this line it the INI of each thin client group and then rebooted the thin clients after changing the DHCP options.
CCMEnable=yes CCMServer=xx.xxx.xx.xxx:8080 GroupPrefix=defa GroupKey=(group/folder name in wms) MQTTServer=xx.xxx.xx.xxx:1883 AdvancedConfig=yes Override=yes
I didn’t reset them like your doing. Also WMS didn’t have the Enrollment Validation when I migrated. You could try turning it off and see if that helps at least until you get everything moved.
Just wanted to ask if you’re activating the group token. I made a new OU group and it is grayed out without it activated when I tried to move a thin client to it.
I put a ticket in with Dell for this last April that went to the L3 team. In the end I was told it was considered a security enhancement. With the release of WMS 1.4.1, users cannot bookmark the WMS domain login direct link anymore. So you always have to go the the first screen (https://WMSserver/ccm-web/). I’ve also found it happens after the web page times out and you get logged out, then I try to log in right away. I basically bookmarked the first page and always hit the bookmark.
Hello,
I work at a hospital to and had to work a lot with our network team to get the 3040s roaming better. Here are the settings that seemed to help our set up.
Roam sensitivity > meduim
Disable Band > 2.4G so it just uses 5G. This helped a lot because most of the hospital’s wireless devices were using 2.4G my network team said that the band is over saturated. This was just done in the last year after upgrading the APs.
Prefer Band > none
Disable N > yes. I got the idea for this setting from another hospital in Washington they said it improved their roaming and it did for our hospital too.
I had to work with my network team on the TCPTosDscp and UDPTosDscp settings. I was told that these setting allow the my network team to prioritize the packets from the thin client. So these settings might be different than what we use but here is what I got on a advanced line. Privilege=High TCPTosDscp=AF31 UDPTosDscp=AF31.
Hope this helps.
Chris
I got the same message when I upgraded from 8.6_412 to 8.6_511. I contacted one of our Dell reps and he said to put the advanced line in “Signon=yes EnableMessage=no”. This did remove the message from the thin clients. He also said this would be a non issue after we can upgrade to 9.x. I was told apparently someone in a security role deemed this message necessary if a client “could” use non-secure communication.
