Forum Replies Created
-
Posts
-
Have you checked to make sure that the client can actually see/use the timeserver? If you need to check that the timeserver is set after you’ve joined the domain, you should be able to open up regedit and goto [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesW32TimeParameters] and check that NtpServer is set to your sntp server.
Also, something we did with our terminals was to extend the MaxPhaseCorrection registry settings so that (hopefully) the client will not fail to sync if the time is out of skew too much.
Open up regedit and navigate to [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesW32TimeConfig] and set “MaxNegPhaseCorrection” and “MaxPosPhaseCorrection” to dword:ffffffffUsual disclaimers apply, I take no responsibility if this breaks your machine, etc etc
EDIT: Something I forgot to mention is that we also shortened the UpdateInterval to dword:00000e10 (3600 seconds)
Sorry for the seemingly silly question, but by ‘default SP3 package’, do you mean use the same SP3 setup as for xp pro?
If so, is the installer smart enough only to update the files that are there, or does it just install everything it has? (While space is not too much of an issue I would still like to keep the image size down as much as possible)
ThanksHi,
Flash memory is not really an issue for us, as all of our 9450’s have 20gb hdd’s in them. Does that make it possible?
Cheers
Hi,
You might find you need to set the DHCP Scope Option 186 to your WDM Server IP Address so the Wyse Client knows where to look for the WDM server. Having never played with WDM Server(s) and clients across different subnets I can only say it should work 🙂 .
When trying to delete an image (or other package/client) you’ll need to make sure there are no active tasks, so go to Scheduled Packages and delete any updates concerning the image/package/client. I’m still getting to understand how the new Merlin imaging process works (so someone else might be able to correct me here if I’m wrong) but I think to use the Non-PXE Option, you need to have the client turned on and booted to windows, then create the job to pull the image, which will tell the HAgent service running on the machine to tell the boot agent it shouldn’t boot to the HDD (or flash in this case). If you’re using PXE (you might need to check that Boot from LAN is enabled on that client) then create the job and right click on it and select Roll to Boot and turn the client on (but again, you might need to set that DHCP Scope option, otherwise the terminal may not be able to find the WDM Server).Hope that helps you. WDM can take a little effort to get setup and learn how to use, but once you get to know it, you can use it to save yourself alot of time in the long run. Let us know how you go. Also, Welcome to the forum! 😀
Hi,
I remember having a similar problem when I upgraded to WDM 4.7.2, I think the thing I checked was the TFTP path, I found it had 2 backslashes (so something like C:Program FilesWDM\TFTP) and getting rid of the extra backslash made it work.
Also, something else I ran into recently, the TFTP server didn’t seem to be serving files (or recieving them either I guess, wasn’t trying to pull an image at that stage), so as stupid as it sounds, in WDM Preferences uncheck ‘Start TFTP Server’, click OK, then re-check it and try again.Hope that helps
Hi All,
Just an update… I got in contact with Wyse on Friday, and I spoke to a nice chap who informed me that it is a known issue. Apparently when you have a ‘-‘ or ‘_’ in your terminal name this behaviour occurs. The good news is that we should be seeing a patch soon 🙂
Hi Oliver,
Two ways spring to my mind…
1. Change the amount of devices you can view on a single page in the preferences section
2. Just query the database directly (the Client table if my memory serves me correctly) with SQL Server Management Studio Express (assuming that you’re using the default MSSQL database engine that comes with WDM)Hope that helps
OK so there seems to be a bit of confusion…
The ftp server we are using is working as it should, as I can make changes to the configuration files and they are received. What we’re having issues with is the http reporting to the wyse device manager server, which seems to have gone pear-shaped since the upgrade to 4.8. When the terminals are on, they periodically checkin with the wdm server by posting their details to a http address (http://wdmserver/hserver.dll). There appears to be 2 types of checkin, a “small” checkin, and a full checkin. I’m making an assumption that periodically a full checkin has to occur, and for the rest of the time a small checkin is used. I’ve checked some of our terminals that are not checking in according to wdm, and they are attempting a full checkin, and the wdm server is returning “&ER|Agent Not Sending valid value”. The terminals that are checking in correctly are just using a small checkin, and this is working, however, according to my assumption, the 20% that we currently have reporting will eventually stop, because they will need to perform a full checkin and will not be able to.
Hope this clears things up,
CheersP.S. The terminals that are not reporting are also showing “HAgent: Invalid Command” in their local event logs.
Thanks for the replies guys.
It doesn’t seem to be an ftp fileserver path issue, as this is still working fine, and any changes I have made have been received. I have checked the wdm server ip on a couple of the devices to verify it, and it was correct as you’d expect, as the wdm server ip hasn’t changed, and the dhcp scope option is the same as ever. As far as I know there have been no changes on the wdm server, and it is running windows server 2003 sp2 (I am planning to upgrade it to 2003 r2 soon). I haven’t tried a network trace yet, but I’ll try that soon and see how i go. Silly question, is it possible that it’s now neccessary to set the wdm server port using dhcp scope options…?
Cheers
UPDATE: I’ve just been running wireshark and i’ve found a terminal that is on and tried to report, and I can see that the terminal sent all it’s information, and the wdm server sent back “&ER|Agent Not Sending valid value”. Is this a wdm bug maybe?
Sorry, I worded that poorly. I have upgraded the HAgent to the latest version by adding commit lines to the script, and then tried running my package again without the commit lines, and it still didn’t work. So upgrading to the latest hagent didn’t fix the problem.
Gavin
Hi,
The WDM Version is 4.7.2 and the HAgent Version is 4.0.5.5. I have also tried upgrading the HAgent to the version that ships with WDM 4.7.2, which I think is 5.1.1.10 (going by the file version) with no luck.
Gavin
OK, Had a look for that value in the registry, but it did not exist. I also attempted to create it and set its value to 1, but it made no difference. I’m figuring there must be options/commands somewhere which tell the hagent what to do when it needs to disable the write filter, because I have a bunch of old scripts which I’m guessing were used on a previous build with a different write filter (venturcom or something) that modify c: drive without any “commits”. Does anyone know of any such options?
Gavin
Edit: I just tried one of my new scripts on the previous build that uses the different write filter and it works fine. So it would seem to be an issue with the Rapport HAgent??
It is entirely possible that the build has been customized, but am not overly sure as it wasn’t done by me. Just to re-iterate the earlier questions, I shouldn’t run into any issues if I use “ewfmgr c: -commit”?
Also, is FBWF a Microsoft Product that’s meant to replace EWF?
Gavin
EDIT: Just had a thought, does EWF/Rapport HAgent have options that can be customized to tell them whether or not to unlock C: drive?
Hi,
You should be able to connect to the database by logging on using administrator credentials (i.e. logon to the server as administrator, then start SQL Server Management Studio) and use Windows Authentication, and it shouldn’t ask for a password. Stop the Rapport service (am not sure whether or not this is necessary, but is probably a good idea). The tables you will need to update are dbo.Install, dbo.Server, dbo.SoftwareRep. I can’t remember if all of the tables contain the ip address or not, but they are the ones that store the server name and/or IP Address, so just have a look, it should be fairly obvious which bits you need to change. If you have any trouble I’ll dig through my documentation and look it up for you.
Once you update the IP Address in the database (and started the Rapport Service again 🙂 ) you should be able to use the WDM console with no issues.
Have Fun,
Gavin
