- This topic is empty.
-
Posts
-
Hello all I have recently ventured into the world of thin clients with Wyse R90LW’s and I have a couple questions/issues.
1. I was able to do the whole image how I wanted, capture it off my client and image several machines with that image. That part worked great. These were for home workers that VPN into our WAN to work. But even though I can ping these machines from the WDM server when they are connected to VPN (Cisco VPN) I can’t seem to get them to report in or show up on the subnet discovery. They worked fine while in the office but not over this VPN (its on a different subnet as well, which I also added to WDM.) I was able to manually add a machine and connect to it with remote shadow but I could not get it to do anything else like give me a diagnostics report. Possible because I didn’t know the mac address for this unit so I put all 0’s on the manual addition, don’t know.
2. My other issue is no matter how perfect you think your image is when you deploy it something always ends up missing. It seems these home workers are all up in arms over a missing shortcut from their favorites in IE. I will say now I have never written scripts for anything so I could use some assistance on creating an update package that would simply just copy a new shortcut to the User favorites folder. I have looked at some examples but I am not confident I will get it right. Also these thin clients have WES (Windows Embedded Standard) not XPe, not sure if that matters, it seems the same as XPe 🙂
Thanks in advance for any help.
I think I may have figured out number 2. but someone that knows please confirm.
[Version]
Number=OWA_Favorites
Description=OWA Favorite added
OS=WES
Category=WES Addons[Script]
; Author: Prepared and Written by Me
; Date:
; Version:
; Notes: Add OWA shortcut to favorites
;
;
; Check Operating System, Check SP level and Confirm free space
;
CO “XP”
CF “C” “1000”
;
;
; Query User and Lockout
;
QU
LU
;
; Main Script actions
;
XC “files*” “C:”
;
;
;
; Finish and End Lockout
;
ELThen I would create a folder called
filesDocuments and SettingsUserFavorites
and put the shortcut file in there.That look good , do I need to do an RB reboot at the end? Also is the CO still considered XP with Windows Embedded Standard?
Hi and welcome in a thin world.
1. I guess the issue is that the clients try to contact the WDM while they aren’t on the VPN. When they got connected they should try it again in an hourly intervall. Have you waited that long?
And also remember that the client will checkin with their local IP address and not with the VPN IP they got. So the WDM server will not be able to contact them directly.
So NATting is a bit difficult.2. Your script
CO “XP”
CF “C” “1000”
;
;
; Query User and Lockout
;
QU
LU
;
; Main Script actions
;
XC “files*” “C:”
;
;
;
; Finish and End Lockout
;
ELcould be streamlined a bit.
You should do it like that:
[Version]
Number=OWA_Favorites
Description=OWA Favorite added
OS=WES
Category=WES Addons
[Script]
; Author: Prepared and Written by Me
; Date:
; Version:
; Notes: Add OWA shortcut to favorites
;
;
; Check Operating System, Check SP level and Confirm free space
;
;
;
; Query User and Lockout
;
QU
LU
;
; Main Script actions
;
XC "files*" "C:"
;
;
;
; Finish and End Lockout
;
EL
A RB command to reboot the client at the end is not needed as 1. the client will reboot by default to reenable the write filter and 2. it is not needed 🙂
HTH
CGOk I was on the right track, I figured I didn’t need it to check the OS or space in this case. Why would I get this error now when I try to add the package?
“The file name must be the same as the script’s [Number] value.”
I verified that the folder I put the files in has the same name as what I have in the Number= line in the script if that is what they mean.
Also if I don’t have a WES Addons catagory do I need to add that, I could not figure out how to add more catagories to the Package Manager, maybe this is a limitation to the free version?
As for my device reporting problem I can see what you mean, if they are by default trying to report on the public IP then they would not get to it as its a 10. private IP on our WAN space. So how would I get these devices in the field to report in and get updates? Would I have to change the WDM to the public IP and open the WDM server up to the internet at 80, 443 and 21? Not something I wish to do really and would that even work? Thanks for the help, much appreciated! (BTW a Wyse Tech in a sale meeting pointed me to your website, its been very helpful. We plan to buy more of these if we can get them to work like we want from workers homes)
1. name the script OWA_Favorites.rsp then it should work. The category/folder is created automatically while the script is imported.
2. If the WDM is accessable directly it will work. Of course you cannot send packages to the clients but these packages will reside in the “Scheduled packages” and will be executed as soon as the clients check in.
CG
- You must be logged in to reply to this topic.