WDM: Package Questions

  • This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #519
    AvatarJoe
    Member
    • Total Post: 106
    • Legend in Own LunchBox
    • ★★★★★

    I had a couple of questions regarding Packages on Wyse Device Manager.

    1: When importing a firmware package from Wyse, is there a way to change the folder where it’s stored in? I figured I could edit the RSP file that you import and change the Category from Images to something else, but when I do that, the devices I’m pushing an image to fails to PXE boot with an error and the TFTServer log reports that it couldn’t find the file .0 in the TFT directory.

    I wanted to do this to keep my custom images and the default images separate. It drives me crazy that I can’t just drag and drop the images between folders. 🙂

    2: What is the best way to import previously created packages into WDM? I recently had to do a database restore and I lost a few packages. The files are still on the FTP server, but they are unavailable in WDM because they were added after the last backup to the database. I don’t want to have to recreate these images, as I’m sure I can import them back in. Will I need to make a custom RSP script to deploy them?

    #9898
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi Joe,

    Here are a few quick answers…

    – No, you can not drag and drop between folders 🙁
    – Addons can live in any folder however images must be in the “images” folder or they fail when pushed as you discovered.
    – To move folders you need to re-import the package
    – You can create any folder you like when importing from a script but you can not nest folders

    Finally importing old images is easy, if you don’t have a script just download one from wyse.com. Lets say you have V90 image to import, download the factory image, replace the 9V90.i2d with your own and edit the packge Number and description. Easy!

    To see what a script is right click on an existing package and select view script, you can cut and past this to recreate the original .rsp

    Have fun!

    Cheers,
    -TT

    #9902
    AvatarJoe
    Member
    • Total Post: 106
    • Legend in Own LunchBox
    • ★★★★★

    Finally importing old images is easy, if you don’t have a script just download one from wyse.com. Lets say you have V90 image to import, download the factory image, replace the 9V90.i2d with your own and edit the packge Number and description. Easy!

    To see what a script is right click on an existing package and select view script, you can cut and past this to recreate the original .rsp

    I manually imported all of my packages and it was pain. We’ve got ~200 packages. Most of them were just different configurations, and for that, it was pretty easy to get the script. I just wrote a batch script that looked at each directory in my old FTP repository. If it found just a .REG file, then it created the script on the fly.

    The problem, and it really wasn’t a HUGE problem, is getting them back into WDM. As you can imagine, 200 packages takes a long, long time to import and it’s a very boring and repetitive task! 🙂

    Thanks for the tips though, I do appreciate it.

    One thing about images… I found if you used FTP to deploy the images, they could exist in any folder. But if you deployed with the imaging solution, it will fail if the image isn’t in the Image folder. Hopefully that will change in a patch… I would love to organize my packages, and subfolders would be amazing! 🙂

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.