Forum Replies Created
-
Posts
-
thanks confgen.
regarding merlin imaging with a non-PXE process….does that mean i could now image xpe devices that are connected to the network wirelessly? This has been a big issue for me historically since most of our xpe devices are wireless (Hospital with mobile carts), and PXE does not support wireless…so when i have had updates that required a firmware image, we have to send a few techs in the field with laptops to do WSI re-imaging.
Of course the imaging speed would be a huge plus too.
we use 100’s of original V90’s with cisco PC card wireless and newer V90LE’s with built in wireless the same way–on rolling carts, and I have not seen any problem.
We have cisco infrastructure, thoug I am not the networking engineer so I can’t say exactly what gear. I have seen no problem with WEP or WPA security. We do not broadcast the SSID either. Good luck as this might be customer-specific issue.
it can pushed out easily.
1. I assume you are familiar at least basically with the scripting language wyse uses in .rsp files.
2. If not already in the image you need to copy over the appropriate .scr screen saver files from an XP box. The default wyse image does not have them present. If necessary you can include the file copy as part of the script.sample .rsp:
[Version]
Number=pr_uchscreensaver
Description=change marquee screensaver to PR request
OS=XP
Category=XP Addons[Script]
; Written by: EBH
;
;
; Check OS, User, Free Space
;
CO “XP”
;
; Query User then lock workstation
;
QU “2” “5”
LU
; merge registry
;
MR “regfilespr_uchscreensaver.reg” “eaauto”
;
; End lockout
;
ELnote that i am referencing a registry file to merge that has the desired screensaver changes I would like to make and i also specify the user account to which to apply the change–screensavers are profile specific so I stating to apply the the change to a “eaauto” autologin user account I have setup. Yours might be the default “user” account. I would set the screensaver the way you like on a test client and then export the needed registry settings and incorporate into you script package.
Hope that make sense–you will need to have some understanding of wyse script building stuff and how to put it together and import into WDM. it’s easy once you get hang of it.
TT–appreciate the response! To answer your suggestion:
1. tested both published version of sound recorder and clinical app launched via web interface. Verified audio set to high quality and that the default.ica coming over has correct parameters for clientaudio=on and audiobandwidthlimit=0 for high quality. Doing same thing from a PC works fine
2. Did same by just copying over an ICA file to launch the published apps and same results as #1…ICA file explicitly has the needed audio settings and it works fine from a PC.You mentioned to check the properties of the session–what else should I check besides what I indicated above? I have combed through everything i can think of to check locally (and again using sound recorder locally works just fine)…any other ideas what local settings to check? I do have an open case with Wyse also…
copy any needed .scr files from a regular windows XP PC from the ..windowssystem32 directory, to the system32 directory on the thin client..Presto you can now configure screensavers for the type based on any .scr files you copied over.
i’ve been sidetracked for awhile, but wanted to update on this thread. i have actually not had any problems installing 8.5i as others have posted as long as you change temporarily the environment variable from temp folder location from z: to c:. My problem is similar to other poster in that I get low virtual memory error/system tray notification on boot up……the bootup gets delayed for an unreasonable amount of time before you see the errors…so bootup is slowed down and then you get the error.
Because of limited memory availablity, Wyse has by default left virtual memory turned off in the base image. If i enable virtual memory it does fix the problem but then i have only 20mb free space which is not enough safety leftover considering i will be using FBWF to allow updates via ePO. Framework service does not appear to be issue and i did fo TT’s advice for dcomcnfg steps anyways, but still have have same issueI have been playing with policy settings in ePO for mcafee, but have not yet found what component is requiring virtual memory. Also not sure if there is a registry hack or some other customization to get past the issue. I have a call into our local Wyse service area manager and he was going to run it past his engineers to see if they have another account doing something similar ( I have to imagine they would but you never know). No word back yet though.
Any other advice from those keeping an eye on this thread?
Thanks TT and CG. I will try 550. Before I get to far with it, let me pose another question–in your opinions is the FBWF functionality suitable for use for Mcafee AV install (vs. partition)? Obviously i will need to exclude a few folders for DAT updates we push through ePO. Historically I have used a locked down VLAN for xpe devices, but we are changing vlan topology from functional to geographic which would mean we would need to create dozens of special vlans for thin clients (one for each closet basically), and this will cause further problems with IP address availability for all these new vlans….so I might be forced to use regular vlan which would mean to sleep at night we’ll need to put AV on the xpe devices. Yes users do not have access to the local file system etc. but the devices can still be considered vulnerable to network based attacks, worms, etc.
By the way, what does WFR1 do for me? Does it have any noteworthy features?
CG–
when i go into the EFF control panel logged in as administrator i still see what i am used to seeing..just the ability to enable, disable and commit changes. I do not see the other items you mentioned where you can add files folders, etc. Doublechecked my image version and it is 3.070551.
Am I missing something? It certainly does not seem like my image has the new filter….i still have the Enhanced Write filter control menu, but not the FBWF stuff. Help I really want to test this out…….
Edit–
I found some other postings in the forum that discuss FBWF and that it is supposedly available in the newest V90 images……i am not finding this to be the case–I downloaded the 3.07 551 build and deployed it to a terminal but i do not see anything to do with FBWF……
FBWF may in fact do what i need…..I am not familiar with this so I apologize if this question is already asked and answered elsewhere in the forum, but is there documentation as to how to configure fbwf?
you can only have one PXE server on your network at a time. Is your old 4.4.1 server still alive? I was not sure if you updated your old server or brought up a whole new server….?
Thanks confgen.
1. To answer your question, no I see no such setting in the scheduling for preferences for what you mentioned. Should I?
2. New problem I found—I had a group of devices I was hoping to setup remotely this weekend, but ended up having to go in to office. First device checked in OK and pulled its DDC (s10 devices, new with 0mb flash reported to WDM). The others would not. I saw in event log that they could not access profile. Checked local rapport account and it was locked out. Unlocked it, and then I had to manually re-enter the rapport password (default r@p8p0r+) in the server settings under the FTP section for each of the clients I was working with. WHat password were they trying to use and why?
lock it down with no priviledge works best for me if you don’t wan’t people messing with anything.
Admins can always get in with high prviledge if you define the “adminmode” parmater in your wnos.ini. THis allows you to right click on local desktop and input credentials to go into high priviledge mode.
Confgen’s utility will help you define this parameter if you are unfamiliar.
there is some good documentation on this site regarding this…..while i can’t quote verse, you basically need to:
1. check the box in WDM to allow checking in from WTOS (blazer) devices into WDM.
2. Either manually point device to your wdm/rapport server in the wnos.ini, or use option tag 187.
3. You must have enterprise version of wdm to do DDC for configuration. This is very cool and there is documentation on this site. You can also see other postings under my name where I had trouble figuring this out. You basically register a package which consists of your INI files and any other related folder structure and then apply that config to a group within a view you setup. I tripped up setting up multiple configs and then there was some confusion with newer Rohs motherboard s10 devices having different reported flash ram size than older models..so learn from my tribulations if you scan my other postings.if you are just using traditional FTP share to make your wnos.ini available and are NOT using DHCP option tags to automatically point the terminals to it, you could setup separate folders and manually point terminals to one or the other folder depending on which INI you want them to get. i.e.–for the ftp server path you could specify server ip/config1/wyse on one terminal and server ip/config2/wyse on another terminal.
If you have a large enterprise and don’t mind investing in WDM enterprise, you could do Default Device Configuration. This is perhaps one of the most powerful tools wyse offers which i have been using successfully with the help of others on this site. [/i]
