- This topic is empty.
19. March 2009 at 22:48 #2004
We have 100+ v90’s that we use as cybercafÃ©s.
From my email to wyse;
With the new 2Ghz chipâ€¦after a new burn, it will always prompt with NEW HARDWARE FOUND. I initially thought that this would be a onetime prompt, but it now prompts after every new burn. It seems that we can get around it by logging back in as ADMIN, turn off the WF, boot back to USER, boot back to Admin and turn on the WFâ€¦thatâ€™s a lot of extra steps that we never had to do this with old burns.
When creating your original image do you remember running prep_4_man?
—ODD SINCE NO ONE SAID ANYTHING ABOUT THIS AT TIME OF PURCHASE—
After running that we started to have issue with a few machine no longer showing up in WDM. After talking to WYSE they suggest the update.
Got around that and during the series of upgradesâ€¦I was told to got from 4.1 to 4.5.1 to 4.5.3 and then to 4.7â€¦followed by 4.7.1
Then had, Setup was unable to initialize the required librariesâ€¦thanks to you monkeys I was able to fix that.
Then I had the MMC Snap-in error which was fixed with;
To remove the current failed MMC > go to dos prompt and change your path to c:Program filsWyseWDM
regsvr32 -u rptmmc.dll
Delete the rptmmc.dll from c:program filesWyseWDM and replace it from your WDM 4.7.x installer
re-register the rptmmc.dll > regsvr32 rptmmc.dll
Open the WDM gui
Click on File menu > Add/remove snap-inÂ > add the new WDM snap in
Delete the old WDM snap-in
Now I have the Hserver is not running when I attempt to open WDM.
Ran thru the HServer not running doc, everything seems correctâ€¦but WDM still says Hserver is not running.
Am I really at the point of uninstalling WDM and IIS, then starting over?
**on a side note, you monkeys and ConfGen’s technicalhelp.de have been 100 times more helpful than WYSE. Thanks for all the helpful info**
.20. March 2009 at 7:55 #15475
thanks for the nice words. TT, all the other guys and gals and myself just love help you around Wyses great products.
OK, they not always running as smooth as expected but compared to other vendors (and believe me I know what I am talking about) Wyse is doing a fantastic job.
Are you running your WDM server on a MSDE or SQL server? Could you connect to the DB via any SQL management tool? Or can you use WDM SQL Queries or MDTools from my website?
If so, please delete the content of the Server table and reboot the WDM server.
CG20. March 2009 at 19:05 #15478
Hey Thanks! Yeah these WYSE have saved me a bunch of time!
I came in today, attempted to run both sql tools…something about passwords were incorrect. I decided, heck lets uninstall and reinstall WDM.
Funny thing is, I probably should have just started there. The WYSE tech had said, YOU NEED TO RUN THRU ALL THE UPGRADES.
Uninstalled, ran disc clean up…extracted the WDM zip to a temp2 location…ran setup and everything seems great.
Thanks again for the tools and help!
– Wally20. March 2009 at 19:59 #15479
heh@ the fact that…the reason we started this was due to the fact that a few machines stopped automatically being detected by WDM. Everything seem to be working well, but those machines are still not showing up. I am able to manually add them and it looks like the imaging is working…but it is taking forever to image.
.21. March 2009 at 10:15 #15480
What units (all V90)? What firmware? What HAgent version?
Manually adding a device will never help you here. This is mainly for adding defect devices to get them flashed to recover them.
CG5. May 2009 at 22:53 #15764
I am back with another weird one.
Everything has been fine, a few machines still don’t show up…but we can add them manually and they work fine. Everything was working great until today…it threw up a message that it could not connect to the FTP when trying a GET IMAGE. Testing the repository fails. Everything looks good in IIS and nothing changed in IIS, but it says NO PROTOCOLS AVAILABLE.
Any ideas on the FTP/NO PROTOCOLS AVAILABLE.
.6. May 2009 at 8:08 #15767
Check if the password of the local user “Rapport” has expired. Set it to “Never expire”.
CG2. June 2009 at 21:36 #16002
updated to 4.7.2
trying to pull or push from V90LE XPe
TFTP READ ERROR
talked with wyse they suggested;
The â€˜Environmental Errorâ€™ message is usually an indication the contents of the swrep folder did not properly get copied to the WDM server.
From the install folder, locate the swrep folder.
Copy all of the files and the folders from the swrep folder to c:inetpubftprootrapport (note your FTP folders may be in a different location)
Try to pull or push the image again/
Did that and no change, Uninstalled and Reinstalled No Change.
any ideas, i am waiting on L2 support to get back to me.
— thanks in advance!
— wally21. December 2009 at 20:33 #17314
hi monkeys…im back!
am i missing something? why would we only be able to push 5 images at a time out to our thin clients? the first 5 pickup the the boot images process and the rest of them are given the WAIT command.
is something wrong with my setup or is there a setting that i missed?
– wally22. December 2009 at 8:30 #17318
First of all it woul dbe great to open new topics instead of always adding new questions to your original thread.
5 clients is the limit in the WDM Workgroup Edition. You can verify that in Configuration Manager-Preferences-Scheduling.
The Enterprise Version does not have this limit.
CG22. December 2009 at 22:25 #17330
Thanks that did the trick!
- You must be logged in to reply to this topic.