Forum Replies Created
-
Posts
-
@jmccammond wrote:
I am using XPE and mcafee EPO and having no problems…
Same here.. Currently EPO3.6.1/McAfee8.0i. Got it going by using the “McAfee 8.0 AV Install on an XPe” document and registry keys.
Wondering if there are documents/registry keys available for an 8.5 install as I’m preparing to upgrade to 8.5 accross the enterprise.
@thinkthin wrote:
Awesome, so what brand was the faulty 1GB RAM SIMM’s?
Others can now check this out if they hav the same issue…
The faulty 1GB’s were Apacer. The new ones are Infineon. I haven’t been able to test the new ones as of yet.
We received 5 new Winterms recently. I just checked and theses ones have a different memory module “Infineon”.
Just a follow up…
Seems like RDP6 is the fix.. I have created a rdp6 package and pushed it to 5 of the winterms that were BSODing and the winterms haven’t blue screened since. We are pushing the package to an additional 20 winterms tonight to verify this fix.
Thanks for help TT and Jeffz!
Thanks jeffz
The Wyse rep wasn’t able to show up today. However, we just tested RDP6 on one of the BSODing winterms and so far so good… We also figured out how to stop the double authentication.
I will test on more winterms during the week and post and update
Thanks for all the help guys.
We have an engineer from Wyse coming to the office tommorow to take a look at our issue. Jeffz if you have any additional info I could give to the engineer that would be great.
Thanks!
thanks for the replies TT
its nice to at least have suggestions.
which is more than I have received from Wyse recently…I really hope they didn’t give me a bad image… I don’t even want to think about reimaging all these machines… especially since we can’t image over the network.
If all else fails I will try configuring a clean image from scratch and test it out. I actually talked to the author of the McAfee article “Bob F” over at wyse. Ironically that article was posted a couple days after i spoke with him 😀
Found another person having a very similar issue…
http://gathering.tweakers.net/forum/list_messages/1198606I beleive that is Dutch so here is a horrible translation via altavista.
The firmware is one that Wyse sent to me that has an additional partition so I could install McAfee VirusScan Enterprise.
Version 3.03 – Needs to be updated with Cl #
(Build 0461.1024)Windows 2003 Server SP1
Office 2003 SP2I am not the only one experiencing this…
http://www.thinplanet.com/community/boards/post.asp?p=111000000&t=772&b=Thin+Client+Devices
Hey tt,
Sorry for the late reply.. been busy sorting out some issues with these winterms…
Yeah it definately is a weird one.. I can’t seem to replicate it here but yet I’m getting more and more users calling with the same issue. I have Wyse looking into it but we have no resolution yet…
There has been a couple different stop errors but the most common being 0x0000008e and 0x0000000A. The documents are located in a mapped network drive.
Although the stop codes are different, they all occur while the user is using Microsoft Word inside one of our terminal servers.
Those files were buried in some .cab files on my windows xp machine. Finally found them though and copied them over to the v90.
Seems like this only happens with local printers.
Thanks TT!
@thinkthin wrote:
Hi Karaziel,
If you alter the global setting in under the Rapport-Configuration Manager-Preferances-Scheduling for the Default Query Buttons will this work around the issue? I have not tried this…
I tried to set the global settings but it does not apply to the write filter process, just the script.
There is an additional process that runs to manage WriteFilter
It has its own QU command built in.
There’s no easy way to modify itBummer… If you guys are able to find out any more info on this subject please let me know! I will be frequenting this site as I am about to rollout 500+ v90’s!
Thanks!
