- This topic has 4 replies, 2 voices, and was last updated 8 years ago by
.
-
Posts
-
HI,
I have a setup where in the config file is on ftp servers, catering to T10 devices.
I also have a wdm 5.5 server for inventory collection of thin clients.So when a thin client boots up,
-contacts dhcp it gets its IP lease
-then contacts WDM server to check in happens
-files server is contacted
-system profile is loadedNow, once my wdm server is down, the checkin obviously does not happen.
But there is a delay of 4min 30 secs before the thin client contacts the file server to load the system profile and bring up the login screen.I need to understand, how can i reduce this delay time or how can i make the thin clients skip the check-in if wdm server is unreachable.
Thanks!
If you are on one of the latest firmware versions, you can add
WDMService=Yes Quickmode=yesThat should help.
CG
I have the firmware version 8.0_512 on T10 devices.
I have the rapportdisable= no paramater, and as per ini guide I added the quickmode=yes.However that infact increased the boot up time.
Without quickmode parameter it tries to look for wdm server for 4min 30 secs.
after quickmode parameter it searches for 7mins 30secs.Kindly advise.
ok, I did try WDMService=Yes Quickmode=yes and it worked.
I have one query around the quick mode parameter, though.
Since the quickmode does not wait for the rest of the boot steps to happen.How does it behave for the Include=$mac.ini parameter.
We use this parameter to upgrade firmware for specific thin clients based on mac ids.So if we have quickmode on, does that mean it will not wait for the mac.ini to do its task of upgrading the firmware and directly come up with the login screen?
Kindly help me understand this bit.
- You must be logged in to reply to this topic.