Forum Replies Created
-
AuthorPosts
-
Also, try making sure your boot order in BIOS is setup right. If it’s only set to PXE boot, it might not be trying other media.
I’m not familiar with the x90, so if this makes no sense in regards to that client, please just disregard it! π
That did the trick! Thanks a ton for the link!
Are there any entries in the event log that might be related to this?
Can you start the service manually? I would give that a shot and see if you get any errors. Drop to a command prompt and type:
Net Start HServerInit
See if you get any error messages doing that.
And yes, this service not running will cause problems when trying to scan segments. You should see an error message about Hserver being disabled when you try to scan.
It’s hard to say, as the prep_4_man.bat is something custom, but it seems like it should work fine.
1. Go through the first question that WDM ask when running
“Get Device Image” Stopping at Ready to register package.This starts the imaging process. Stopping before it actually takes the image is going to give you time to prepare the machine for imaging.
2. Run “prep_4_man.bat” on the device.
I’m assuming this prepares the device for duplication. It probably runs some type of sid changer, and maybe some other custom settings. I’d have to see the contents to be fore sure, though.
3. Pull the power cord.
I’d recommend a graceful shutdown instead of pulling the power cord. Nothing like a possible problem creeping up on all of your machines because the base machines wasn’t shut down properly.
4. Complete the Registering package and changing it to “Roll On Boot”. In Software Packages under Update Manager.
At this point, you’re finishing the job and telling it to PXE boot and grab your image the next time you turn it on.
5. Start the device. (And HOPE that it takes it. Or else i will have to go through the order above again.)
When you turn it on, assuming PXE is working properly, it should PXE boot and grab an image for you.
Those are the basic steps for imaging a v90 terminal. I hope that your prep_4_man.bat file runs some sort of sid changer.
– Wyse Devige Manager MMC:
When viewing ‘update manager > scheduled tasks’ the error ‘Timeout Expired – SQL database’ appears. Sometimes after trying 10 times we can view the scheduled tasks.I’ve seen this issue when problems were occuring on the database server. It might be worth checking your database server to make sure it is operating properly.
– When it is possible to deploy an image (on a V90 for example) The client boots, connects to the wyse server, but then displays ‘Environment Failure’
The IIS components seem to be working fine (http, ftp)From my experience, this indicates you’re trying to push an image to a machine that the image isn’t compatible with. I don’t know if that is the only cause for this, or if it is even the correct answer.
For example, I have quite a few v90 machiens in the field. Apparently the v90 is discontinued, and was replaced by the v90L. I wasn’t aware that my company had been purchasing them until they started calling me with this error. The image that I had created for the v90 didn’t work with the v90L.
– When running rptdiag.exe the tool gives an error at ‘Testing Database’ ‘Currently validating: Rapport Web Service’ ‘Connection To HServer failed’ And a C++ error appears afterwards
I’ve had problems with iis crashing, thus making connections to the HServer impossible. It’s possible that hserver isn’t available while you’re trying to test the database. Try giving the computer a restart to refresh all the services and make sure they’re up and running. I know that in some environments, rebooting the server is a no-no. In that case, you can try this script to restart the “core” WDM services.
:Init
@Echo Off
Cls
:Stop
Echo
Echo Stopping Core WDM Services
Echo
Echo ΓΒ¦ World Wide Web Publishing Service
Net Stop W3Svc
Echo ΓΒ¦ Microsoft FTP Services
Net Stop MSFTPSVC
Echo ΓΒ¦ Rapport
Net Stop RAPPORT4
Echo
Echo Core WDM Services Stopped
Echo
:Start
Echo
Echo Starting Core WDM Services
Echo
Echo ΓΒ¦ World Wide Web Publishing Service
Net Start W3Svc
Echo ΓΒ¦ Microsoft FTP Services
Net Start MSFTPSVC
Echo ΓΒ¦ Rapport
Net Start RAPPORT4
Net Start HServerInit
Echo
Echo Core WDM Services Started
Echo
Just save the contents to a text file and rename it RestartWDM.cmd or whatever you want to all it. Then double click it.
– On a sidenote, the IIS logs from the Wyse HTTP site is filled with:
‘VSQL02 192.168.10.2 80 PUT /hserver.dll &V01|&IMAC=00806454B029|CID=117||WFE=1|WF=0|OS=1|VI=1|AL=c:programΓΒΌfilesrapport’
Wich is a non-existing path.This looks to me like a transaction where the thin client is checking in with the WDM server. Is 192.168.10.2 a thin client? I’m pretty sure it is, because of the MAC address — I believe the 008064xxxxxx block belongs to Wyse.
If I had to take a guess, and this is a complete guess, I bet AL is something like Agent Location, and shows the location on the thin client where the WDM/Rapport agent is installed. So look on your thin client for this directory, not your server.
While I know I didn’t give any concrete fixes, hopefully I got you looking in the right direction.
I would recommend trying to upload something to the FTP server using the Rapport user and a third party FTP client. If the permissions are not set up properly on your FTP server, even a local administrator can get denied access to the files.
That will verify that the problem isn’t with transferring the files to the FTP server and allow you to concentrate your efforts elsewhere. Just make sure you’re using the Rapport user and not your account, as it will do the FTP of the image as Rapport, not the person logged in and running the application.
Testing the Master Repository is great, but I believe all that does is log in and make sure it can access the repository. It doesn’t test uploading or downloading. So, while it is a great tool, it won’t help you test permissions that are actually applied to your FTP server.
If you do find problems, let us know and we can help you figure it out! If not, well, let us know that too!
I’ve run it both ways —
DEP enabled for all essential windows programs and services. With this setting, you don’t get to specify any applications to disable DEP for. This is the way it’s running now. I don’t believe IIS is considered an essential windows program/service, is it?
DEP enabled for all programs and services except except those that I select. With this setting, I disabled DEP for IIS (put a check in the box to select it) and it still had problems.
Dep is enabled and configured as:
Turn on DEP for essential Windows programs and services only
I’ve seen the exchange/smtp patches out there from Microsoft. In fact, it sounds like thats exactly what the problem is. However, exchange isn’t on the machine, and when I had posted that message, all patches were up to date.
I see a few 7023 event IDs popping up, but I don’t see anything relating to IIS out there.
You know — maybe we jumped too far ahead at first. Are the clients set to PXE boot? They won’t show up as imageble if they can’t PXE boot.
No, it shouldn’t be a problem. I was just trying to get a better picture of what you’re doing.
In WDM, does your client show up as Imageable? You might have to scroll over to see it, but it should show on the device manager screen
Really?
I could swear I saw it somewhere, but I could be wrong. I deal with many apps, and I could be mixing two of them together. I apologize for the inaccurate information.
You might be able to run something like filemon and see what file is missing and try to fix it that way.
What image are you trying to deploy, and how are you deploying
I have taken a brand new S90 out of the box and installed some standard apps we use i.e. SMS 2003 client, 2X load balancer client and Etrust Anti virus. This was setup standalone and then I have discovered it in WDM. I am now trying to push it to all other S90Γ’β¬β’s
This slightly confuses me. Did you set up a machine the way you wanted, and now you’re trying to take an image of it to push to other machine?
I’ve never seen this error before, but it looks like a DLL might be missing or not registered.
I know WDM needed a version of the Dot Net Framework… you might want to try reinstalling it. I can’t find which version it requires, and I even flipped through the install guide — it just isn’t there.
Haha — I bet.
But I just spent 3 months troubleshooting this problem with Wyse, and those questions cover just about everything we did. I know how frustrating it is to be so close to a fully functional WDM server, and have a problem like this.
-
AuthorPosts