Forum Replies Created
-
Posts
-
Wyse offers a device manager software suite (Wyse Device Manager) which will allow you to manage and image XPe devices. It comes in two flavors workgroup (up to 750 seats all installed on one WDM server) or enterprise which does come w/ a fee and is recommended when using 750+ devices or if you need to distribute the install (ex: FTP or SQL installed on different server than the WDM server.)
You will need to upgrade to at least 4.4.1 before upgrading to 4.5.3. I hope this helps.
The i2d files are the image files, the CRC.txt is simply holds the CRC check value should you want to use a CRC utility to make sure the download isn’t corrupt.
Using Wyse Device Manager – go to device manager and highlight the “master” device which is setup w/ the config. Next, you just need to right-click the master device and pull or get the config. This will prompt you to create a package on the fly with the config. Once this is complete you can go to package manager locate the package you created and drag and drop it onto the device you wish to push the config to in device manager.
Hope this helps.
If you are using Wyse Device Manager you can setup and pull a master configuration (versus an image) and distribute this to other thin clients.
The MB uses a VIA chipset and yes the same board is used across the board on the Sx0 products with just different flash/ram config. Also, keep in mind if the part number ends with a “L” the board is RoHS compliant.
Couple of questions:
Is the older WDM server still online?
Does the new WDM server carry the same IP address as the old WDM server?
What happens if you manually enter the new WDM server IP address in the XPe control panel WDM applet?If you plan on having a distributed WDM install across multiple machines or more than 750 clients you may want to look at enterprise. You can touch the database if were to ever need to with the full version of SQL. With MSDE you will be limited to the tables you can with other utilities such as MDTools which is for WDM.
The OSM client image builder is not meant for Wyse Device Manager. I think it’s for the provisioning solution.
You mentioned SQL Express 2008, have you tried 2005? Also have you tried hooking in a basic switch instead of crossover cable?
Give this a try. It’s from Wyse but has to be applied via FTP not WDM.
ftp://ftp-us.wyse.com/Pub/Support/firmware/CE/ADDOns/NoMouse/NoMouse.zip
Blackburn, very nice utility!
@BlackBurn wrote:
I wrote a small util which does this for you, I encountered the exact same problem, so I’ve placed this util in the start-up folder and it works perfect.
Are you still using DHCP option tags? If you are installing WSI 1.1.4 you no longer need the option tags. There is a WSI DHCP PROXY service running which will handle the boot floppy/TFTP allocation.
With the latest WSI 1.1.4 version you can run on any isolated network running DHCP services. If you go XP w/ DHCP Turbo you NEED to set a scope. WSI no longer handles this. One trick is to make sure when you install WSI you have an active NIC so everything can bind to the correct network connection. If you are using crossover cable be sure to have the client powered on, this isn’t an issue generally w/ a hub/switch.
The changes were incorporated into the build and the addons was made available for older builds. This has been confirmed w/ Wyse.
