Wyse Thin Clients "blue screening" at unpredictable times.

  • Thread starter Thread starter Bill-MT
  • Start date Start date
B

Bill-MT

Guest
Background Info:
=============
"New" Terminal Server:
--Running: Windows Server 2003sp2. (32bit)
--HP DL380 – Two intel Quad(1.86), 4Gb memory, 150Gb storage, lots free.

Application Software installed:
--Office 2007 {Word, Excel, Access, PowerPoint, Publisher}

IE Plug-ins/Add-ons:
--Alternatiff, Adobe Flash, Adobe Shockwave

Other installed software:
--McAfee AV, Firefox, Java.

Printer is installed on each Wyse V90 Thin-client (XPe) and connected though
via RDP (Remote Desktop Connection) client.

Connected to "new" Wyse V90 [512mb flash/256mb ram] Thin Client Lab (20
clients).

PROBLEM:
==========
New Lab of Wyse Thin Clients (running XPe) blue-screen at ‘unpredictable’
intervals – disrupting student’s work. [and it also scare’s the heck out of
them to see the Windows crash screen come up in the middle of working on a
document].


User Actions
==========
Which seem to cause the “observed” Issues (see next section).
-Touched, Scrolled or otherwise moved the Mouse {within IE, Word, Excel,
Access)
- Opening or while Saving a Document
-Copying or Pasting text to/from clipboard {generally from IE to Word}
-Printing a Document

Issues Observed
============
Problems:
-Blue Screen with message “IRQL_NOT_LESS_OR EQUAL
-Blue Screen with message “PAGE_FAULT_IN_NON_PAGED_AREA
--Image(s) referenced on Blue Screen: AFD.SYS, RDBSS.SYS,
--WIN32K.SYS, MSTSC.EXE, MSTSCAX.DLL
-Error in data encryption this session will end.

A “Working” Solution to above problem(s)
===========================
-Turn off Thin Client… Turn on Thin Client… Re-connect to session,
continue working on session where you left off.
--Sessions don’t close or end and always seem to be available for
reconnection.
--This process (thin client reboot) ALWAYS WORKS… but sometime the “blue
screen” issues continue for that student/session until the Thin Client has
been restarted up to 3 (three) times at which time the session settles down
or the student gets frustrated and walks away.

---Problems are intermittent…
----Sometime happen with only 3 clients (out of 20) active
----Don’t necessarily happen with 20 clients (out of 20) active.

Finally: Our regular XPsp2 desktops connecting via RDP (Remote Desktop
Connection) don’t EVER seem to have any of these problems. That is, their
sessions always seem to be trouble free. However we only have about 3 to 5
desktops configured to connect to this Terminal Server.

Does this sound like just a Thin Client issue or should I be looking at the
Terminal Server for the solution? The Terminal Server is NOT generating any
EVENTS in event viewer.

Could any of the Group Polices I set (note - I followed Technet May 2007
Deploying Terminal Server article pretty closely) be the cause? [Note I've
rebuilt the terminal server on different hardware to see if that helps, but
I've always used the same GP/OU each time].

Are there settings within the RDP "client" I need to be looking into?

Is the XPe Thin Client running out of memory (RAM-based OS, no hard drive)
and if so, why don't we get any errors indications.

Comments, Suggestions?
--
Bill
 
RE: Wyse Thin Clients "blue screening" at unpredictable times.

Hello Bill,

Thank you for using newsgroup!

From your post, please understand Thin Clients not supported in our partner
managed newsgroups. For assistance on this issue, please contact Microsoft
Product Support Services by telephone so that a dedicated Support
Professional can assist you further with your request.

To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US, you can find regional telephone support numbers
at http://support.microsoft.com.

Thanks & Regards,

Ken Zhao

Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security <http://www.microsoft.com/security>
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Re: Wyse Thin Clients "blue screening" at unpredictable times.

Hi Bill,

This is a problem with your thin clients. Have you contacted
Wyse support and asked them for help and/or if there are any
driver or firmware updates? It is unacceptable that the devices
are crashing under normal usage.

Do you have a thin client with *only* the original factory
image (no printer driver or other software added) that you
can test with?

The most common cause of driver-related blue screens are
bad drivers for one or more of the following components:
video, network interface, disk controller. Of course it is
possible that the hardware itself is faulty, for example, bad
RAM.

If necessary you can work with Wyse to analyze the crash
dump file using the windows debugging tools.

-TP

Bill-MT wrote:
> Background Info:
> =============
> "New" Terminal Server:
> --Running: Windows Server 2003sp2. (32bit)
> --HP DL380 – Two intel Quad(1.86), 4Gb memory, 150Gb storage, lots
> free.
>
> Application Software installed:
> --Office 2007 {Word, Excel, Access, PowerPoint, Publisher}
>
> IE Plug-ins/Add-ons:
> --Alternatiff, Adobe Flash, Adobe Shockwave
>
> Other installed software:
> --McAfee AV, Firefox, Java.
>
> Printer is installed on each Wyse V90 Thin-client (XPe) and connected
> though via RDP (Remote Desktop Connection) client.
>
> Connected to "new" Wyse V90 [512mb flash/256mb ram] Thin Client Lab
> (20 clients).
>
> PROBLEM:
> ==========
> New Lab of Wyse Thin Clients (running XPe) blue-screen at
> ‘unpredictable’ intervals – disrupting student’s work. [and it also
> scare’s the heck out of them to see the Windows crash screen come up
> in the middle of working on a document].
>
>
> User Actions
> ==========
> Which seem to cause the “observed” Issues (see next section).
> -Touched, Scrolled or otherwise moved the Mouse {within IE, Word,
> Excel, Access)
> - Opening or while Saving a Document
> -Copying or Pasting text to/from clipboard {generally from IE to Word}
> -Printing a Document
>
> Issues Observed
> ============
> Problems:
> -Blue Screen with message “IRQL_NOT_LESS_OR EQUAL
> -Blue Screen with message “PAGE_FAULT_IN_NON_PAGED_AREA
> --Image(s) referenced on Blue Screen: AFD.SYS, RDBSS.SYS,
> --WIN32K.SYS, MSTSC.EXE, MSTSCAX.DLL
> -Error in data encryption this session will end.
>
> A “Working” Solution to above problem(s)
> ===========================
> -Turn off Thin Client… Turn on Thin Client… Re-connect to session,
> continue working on session where you left off.
> --Sessions don’t close or end and always seem to be available for
> reconnection.
> --This process (thin client reboot) ALWAYS WORKS… but sometime the
> “blue screen” issues continue for that student/session until the Thin
> Client has been restarted up to 3 (three) times at which time the
> session settles down or the student gets frustrated and walks away.
>
> ---Problems are intermittent…
> ----Sometime happen with only 3 clients (out of 20) active
> ----Don’t necessarily happen with 20 clients (out of 20) active.
>
> Finally: Our regular XPsp2 desktops connecting via RDP (Remote Desktop
> Connection) don’t EVER seem to have any of these problems. That is,
> their sessions always seem to be trouble free. However we only have
> about 3 to 5 desktops configured to connect to this Terminal Server.
>
> Does this sound like just a Thin Client issue or should I be looking
> at the Terminal Server for the solution? The Terminal Server is NOT
> generating any EVENTS in event viewer.
>
> Could any of the Group Polices I set (note - I followed Technet May
> 2007 Deploying Terminal Server article pretty closely) be the cause?
> [Note I've rebuilt the terminal server on different hardware to see
> if that helps, but I've always used the same GP/OU each time].
>
> Are there settings within the RDP "client" I need to be looking into?
>
> Is the XPe Thin Client running out of memory (RAM-based OS, no hard
> drive) and if so, why don't we get any errors indications.
>
> Comments, Suggestions?
 
Re: Wyse Thin Clients "blue screening" at unpredictable times.

TP, thanks much for your response, I was pretty much thinking exactly along
the same line, so it's good to get a separate confirmation.

I pretty much figured it was a problem with the 'thin-clients' but since I'm
new to this whole Terminal Server-Thin Client solution I didn't want to take
anything for granted.

In my 20+ years in IT, I've seen enough situations where things are related
in ways you'd never imagine. Thus I've learned (mostly the hard way - is
there any other way) that its always better to never 'assume' and to always
'ask' when you are not sure what's going on. Especially if you have someone
more knowledgable to ask!

Based on your answer at least now I know that thin client issues (at least
of the kind I described) are generally not because of either Server
performance problems or Group Policy settings.

btw: I also contacted Wyse support at the same time I queried this newsgroup
and they responded quite quickly. So I'll see if their fix does the trick.

Thanks for taking the time to answer!
--
Bill


"TP" wrote:

> Hi Bill,
>
> This is a problem with your thin clients. Have you contacted
> Wyse support and asked them for help and/or if there are any
> driver or firmware updates? It is unacceptable that the devices
> are crashing under normal usage.
>
> Do you have a thin client with *only* the original factory
> image (no printer driver or other software added) that you
> can test with?
>
> The most common cause of driver-related blue screens are
> bad drivers for one or more of the following components:
> video, network interface, disk controller. Of course it is
> possible that the hardware itself is faulty, for example, bad
> RAM.
>
> If necessary you can work with Wyse to analyze the crash
> dump file using the windows debugging tools.
>
> -TP
>
> Bill-MT wrote:
> > Background Info:
> > =============
> > "New" Terminal Server:
> > --Running: Windows Server 2003sp2. (32bit)
> > --HP DL380 – Two intel Quad(1.86), 4Gb memory, 150Gb storage, lots
> > free.
> >
> > Application Software installed:
> > --Office 2007 {Word, Excel, Access, PowerPoint, Publisher}
> >
> > IE Plug-ins/Add-ons:
> > --Alternatiff, Adobe Flash, Adobe Shockwave
> >
> > Other installed software:
> > --McAfee AV, Firefox, Java.
> >
> > Printer is installed on each Wyse V90 Thin-client (XPe) and connected
> > though via RDP (Remote Desktop Connection) client.
> >
> > Connected to "new" Wyse V90 [512mb flash/256mb ram] Thin Client Lab
> > (20 clients).
> >
> > PROBLEM:
> > ==========
> > New Lab of Wyse Thin Clients (running XPe) blue-screen at
> > ‘unpredictable’ intervals – disrupting student’s work. [and it also
> > scare’s the heck out of them to see the Windows crash screen come up
> > in the middle of working on a document].
> >
> >
> > User Actions
> > ==========
> > Which seem to cause the “observed” Issues (see next section).
> > -Touched, Scrolled or otherwise moved the Mouse {within IE, Word,
> > Excel, Access)
> > - Opening or while Saving a Document
> > -Copying or Pasting text to/from clipboard {generally from IE to Word}
> > -Printing a Document
> >
> > Issues Observed
> > ============
> > Problems:
> > -Blue Screen with message “IRQL_NOT_LESS_OR EQUAL
> > -Blue Screen with message “PAGE_FAULT_IN_NON_PAGED_AREA
> > --Image(s) referenced on Blue Screen: AFD.SYS, RDBSS.SYS,
> > --WIN32K.SYS, MSTSC.EXE, MSTSCAX.DLL
> > -Error in data encryption this session will end.
> >
> > A “Working” Solution to above problem(s)
> > ===========================
> > -Turn off Thin Client… Turn on Thin Client… Re-connect to session,
> > continue working on session where you left off.
> > --Sessions don’t close or end and always seem to be available for
> > reconnection.
> > --This process (thin client reboot) ALWAYS WORKS… but sometime the
> > “blue screen” issues continue for that student/session until the Thin
> > Client has been restarted up to 3 (three) times at which time the
> > session settles down or the student gets frustrated and walks away.
> >
> > ---Problems are intermittent…
> > ----Sometime happen with only 3 clients (out of 20) active
> > ----Don’t necessarily happen with 20 clients (out of 20) active.
> >
> > Finally: Our regular XPsp2 desktops connecting via RDP (Remote Desktop
> > Connection) don’t EVER seem to have any of these problems. That is,
> > their sessions always seem to be trouble free. However we only have
> > about 3 to 5 desktops configured to connect to this Terminal Server.
> >
> > Does this sound like just a Thin Client issue or should I be looking
> > at the Terminal Server for the solution? The Terminal Server is NOT
> > generating any EVENTS in event viewer.
> >
> > Could any of the Group Polices I set (note - I followed Technet May
> > 2007 Deploying Terminal Server article pretty closely) be the cause?
> > [Note I've rebuilt the terminal server on different hardware to see
> > if that helps, but I've always used the same GP/OU each time].
> >
> > Are there settings within the RDP "client" I need to be looking into?
> >
> > Is the XPe Thin Client running out of memory (RAM-based OS, no hard
> > drive) and if so, why don't we get any errors indications.
> >
> > Comments, Suggestions?
>
>
 
Re: Wyse Thin Clients "blue screening" at unpredictable times.

Bill,

You are welcome. Thanks for reporting back.

Please come back later and post a brief description of the
proposed wyse fix and whether or not it solved the issue. This
will help me and others in the future.

Thank you.

-TP

Bill-MT wrote:
> TP, thanks much for your response, I was pretty much thinking exactly
> along the same line, so it's good to get a separate confirmation.
>
> I pretty much figured it was a problem with the 'thin-clients' but
> since I'm new to this whole Terminal Server-Thin Client solution I
> didn't want to take anything for granted.
>
> In my 20+ years in IT, I've seen enough situations where things are
> related in ways you'd never imagine. Thus I've learned (mostly the
> hard way - is there any other way) that its always better to never
> 'assume' and to always 'ask' when you are not sure what's going on.
> Especially if you have someone more knowledgable to ask!
>
> Based on your answer at least now I know that thin client issues (at
> least of the kind I described) are generally not because of either
> Server performance problems or Group Policy settings.
>
> btw: I also contacted Wyse support at the same time I queried this
> newsgroup and they responded quite quickly. So I'll see if their fix
> does the trick.
>
> Thanks for taking the time to answer!
 
Re: Wyse Thin Clients "blue screening" at unpredictable times.

TP
I was waiting a few days to see if the resolution from Wyse helped or not.
After 5 days - I'm still not sure. The number of BlueScreens may be down.
But I'm noticing "data encryption" errors more. This might be because of the
'fix' or these could have been masked by the more numerus Blue Screens.
Either way - errors still occur but 'maybe' at a reduced rate.

So - as you requested - here is the recommended fix from Wyse:
==========================================
>If I understand your case, you gets blue screen will you are in RDP session?
>Can you please try to setup the RDP client from the thin client to disable
>the bitmap caching and try to increase your ramdisk?
> a) Disable the bitmap caching
> b) Increase the ramdisk

If you have any additional comments on this solution, please reply to this
thread.
--
Bill


"TP" wrote:

> Bill,
>
> You are welcome. Thanks for reporting back.
>
> Please come back later and post a brief description of the
> proposed wyse fix and whether or not it solved the issue. This
> will help me and others in the future.
>
> Thank you.
>
> -TP
>
> Bill-MT wrote:
> > TP, thanks much for your response, I was pretty much thinking exactly
> > along the same line, so it's good to get a separate confirmation.
> >
> > I pretty much figured it was a problem with the 'thin-clients' but
> > since I'm new to this whole Terminal Server-Thin Client solution I
> > didn't want to take anything for granted.
> >
> > In my 20+ years in IT, I've seen enough situations where things are
> > related in ways you'd never imagine. Thus I've learned (mostly the
> > hard way - is there any other way) that its always better to never
> > 'assume' and to always 'ask' when you are not sure what's going on.
> > Especially if you have someone more knowledgable to ask!
> >
> > Based on your answer at least now I know that thin client issues (at
> > least of the kind I described) are generally not because of either
> > Server performance problems or Group Policy settings.
> >
> > btw: I also contacted Wyse support at the same time I queried this
> > newsgroup and they responded quite quickly. So I'll see if their fix
> > does the trick.
> >
> > Thanks for taking the time to answer!
>
 
Re: Wyse Thin Clients "blue screening" at unpredictable times.

Bill,

Under normal circumstances you should get *zero* blue
screens, not a reduced amount. You should be able to
work with bitmap caching enabled if desired. I'm not
saying that you *need* to use bitmap caching in your
environment, but you should be able to without problems.

Remote Desktop Client is a user-mode program and thus
on its own has no ability to blue screen the machine. Using
it may trigger a blue screen, but the root cause would be
a kernel-mode component like a video driver, for example.

Contact Wyse technical support and be polite but persistent.
Ask for them to escalate you to the next support level if
necessary. A knowledgeable tech support representative
will understand that there is something seriously wrong
and that blue screens are not normal.

Did they ask you to send them the specific STOP error?

Did they ask you for a crash dump?

I asked you originally if you had a thin client that has only
the original factory image. I wanted you test with that to
see if it was a driver that you added that may be causing
problems.

Frequent blue screens are unacceptable. If this were
happening to me I would return the Wyse devices if the issue
was not resolved quickly. One of the *primary* uses of a
thin client is to connect to terminal servers. What value does
it have if it can't even do the most basic/common task of a thin
client without crashing frequently?

You could easily purchase low end PCs running windows XP
that will not blue screen.

-TP

Bill-MT wrote:
> TP
> I was waiting a few days to see if the resolution from Wyse helped or
> not. After 5 days - I'm still not sure. The number of BlueScreens
> may be down. But I'm noticing "data encryption" errors more. This
> might be because of the 'fix' or these could have been masked by the
> more numerus Blue Screens. Either way - errors still occur but
> 'maybe' at a reduced rate.
>
> So - as you requested - here is the recommended fix from Wyse:
> ==========================================
>> If I understand your case, you gets blue screen will you are in RDP
>> session? Can you please try to setup the RDP client from the thin
>> client to disable the bitmap caching and try to increase your
>> ramdisk? a) Disable the bitmap caching
>> b) Increase the ramdisk
>
> If you have any additional comments on this solution, please reply to
> this thread.
 
Re: Wyse Thin Clients "blue screening" at unpredictable times.

Wonderful info. Right to the point.
One more question before I do 'battle' with them...

Could network or power problems cause "blue screen" issues on thin clients?

I don't want them to be able to redirect the issue to something else.

Previously in this stream we've already elminated both Group Policy and
Server issues as potential reasons.

I can see them pointing to the network as the next excuse (especially for
the data encryption errors - these are rare but they do happen).

--
Bill


"TP" wrote:

> Bill,
>
> Under normal circumstances you should get *zero* blue
> screens, not a reduced amount. You should be able to
> work with bitmap caching enabled if desired. I'm not
> saying that you *need* to use bitmap caching in your
> environment, but you should be able to without problems.
>
> Remote Desktop Client is a user-mode program and thus
> on its own has no ability to blue screen the machine. Using
> it may trigger a blue screen, but the root cause would be
> a kernel-mode component like a video driver, for example.
>
> Contact Wyse technical support and be polite but persistent.
> Ask for them to escalate you to the next support level if
> necessary. A knowledgeable tech support representative
> will understand that there is something seriously wrong
> and that blue screens are not normal.
>
> Did they ask you to send them the specific STOP error?
>
> Did they ask you for a crash dump?
>
> I asked you originally if you had a thin client that has only
> the original factory image. I wanted you test with that to
> see if it was a driver that you added that may be causing
> problems.
>
> Frequent blue screens are unacceptable. If this were
> happening to me I would return the Wyse devices if the issue
> was not resolved quickly. One of the *primary* uses of a
> thin client is to connect to terminal servers. What value does
> it have if it can't even do the most basic/common task of a thin
> client without crashing frequently?
>
> You could easily purchase low end PCs running windows XP
> that will not blue screen.
>
> -TP
>
> Bill-MT wrote:
> > TP
> > I was waiting a few days to see if the resolution from Wyse helped or
> > not. After 5 days - I'm still not sure. The number of BlueScreens
> > may be down. But I'm noticing "data encryption" errors more. This
> > might be because of the 'fix' or these could have been masked by the
> > more numerus Blue Screens. Either way - errors still occur but
> > 'maybe' at a reduced rate.
> >
> > So - as you requested - here is the recommended fix from Wyse:
> > ==========================================
> >> If I understand your case, you gets blue screen will you are in RDP
> >> session? Can you please try to setup the RDP client from the thin
> >> client to disable the bitmap caching and try to increase your
> >> ramdisk? a) Disable the bitmap caching
> >> b) Increase the ramdisk
> >
> > If you have any additional comments on this solution, please reply to
> > this thread.
>
 
Re: Wyse Thin Clients "blue screening" at unpredictable times.

Hi,

Power problems can cause all kinds of strange behavior.
Lockups, blue screens, etc. Do you have any reason to
believe you are having pervasive power problems? Go
ahead and hook some of the thin clients to a UPS to be
sure.

Any flickering lights, breakers tripping frequently,
dimming/bright lights, constant-speed fans that speed up
and slow down, surge protectors tripping, etc? If you don't
have any of these symptoms it is not a guarantee that your
power is okay but would be a good sign.

Network problems normally will not cause blue screens
unless the network driver or the physical network card is
faulty. Not to say that it is impossible, but not so likely.

If you are having network issues you will normally have some
symptoms like slowness, lockups, unable to connect, unable
to obtain ip address, warnings regarding the NIC being
disconnected, etc. Check the event logs on the thin clients
and the TS to see if there are any warnings/errors having to
do with the network or network card driver.

Are you having any network-related symptoms? You said
before that you have XP SP2 machines that are working fine.
Are they on the same network segment as the thin clients? Are
they plugged into the same electrical circuit? If not move them
so that they are on the same as a test.

The other thing to look at is the exact crash that is occurring
each time. If you have really bad power issues I would
expect some fluctuation in the nature of the crashes. If you
have a bad driver you are likely to see very similar crashes
each time. Dump analysis will help you figure it out.

-TP

Bill-MT wrote:
> Wonderful info. Right to the point.
> One more question before I do 'battle' with them...
>
> Could network or power problems cause "blue screen" issues on thin
> clients?
>
> I don't want them to be able to redirect the issue to something else.
>
> Previously in this stream we've already elminated both Group Policy
> and Server issues as potential reasons.
>
> I can see them pointing to the network as the next excuse (especially
> for the data encryption errors - these are rare but they do happen).
 
Re: Wyse Thin Clients "blue screening" at unpredictable times.

Thanks again.

We really aren't seeing 'regular' power issues (dips, spikes, etc) but we do
have some power interferrence on the circuit as every now and then the LCDs
look fuzzy (you know the kind of fuzzy you get on VDT, LCD, etc when there is
some motor generating noise on the circuit).

I have put a set of 5 of the 20 on a UPS and apparently (the lab is in a
different building so I get my info from the lab support staff) a couple of
those machines have also blue screened. But I figured I'd ask to get an
opinion anyway.

As far as the network, we have a number of other application servers and
other clients in the same building where that lab is located and I've not
seen any specific issues reguarding any of those network nodes. But again I
figured I'd ask.

All the information you have given me helps me to clarify and reflect on
what is significant here and what isn't. So I very much appreciate you
taking the time to answer. Thanks again, I'll let you know what Wyse says, I
have a new service issues logged since last friday. I'm thinking starting
again with a fresh image might be a good idea - I'll wait to see if they
suggest it.

--
Bill


"TP" wrote:

> Hi,
>
> Power problems can cause all kinds of strange behavior.
> Lockups, blue screens, etc. Do you have any reason to
> believe you are having pervasive power problems? Go
> ahead and hook some of the thin clients to a UPS to be
> sure.
>
> Any flickering lights, breakers tripping frequently,
> dimming/bright lights, constant-speed fans that speed up
> and slow down, surge protectors tripping, etc? If you don't
> have any of these symptoms it is not a guarantee that your
> power is okay but would be a good sign.
>
> Network problems normally will not cause blue screens
> unless the network driver or the physical network card is
> faulty. Not to say that it is impossible, but not so likely.
>
> If you are having network issues you will normally have some
> symptoms like slowness, lockups, unable to connect, unable
> to obtain ip address, warnings regarding the NIC being
> disconnected, etc. Check the event logs on the thin clients
> and the TS to see if there are any warnings/errors having to
> do with the network or network card driver.
>
> Are you having any network-related symptoms? You said
> before that you have XP SP2 machines that are working fine.
> Are they on the same network segment as the thin clients? Are
> they plugged into the same electrical circuit? If not move them
> so that they are on the same as a test.
>
> The other thing to look at is the exact crash that is occurring
> each time. If you have really bad power issues I would
> expect some fluctuation in the nature of the crashes. If you
> have a bad driver you are likely to see very similar crashes
> each time. Dump analysis will help you figure it out.
>
> -TP
>
> Bill-MT wrote:
> > Wonderful info. Right to the point.
> > One more question before I do 'battle' with them...
> >
> > Could network or power problems cause "blue screen" issues on thin
> > clients?
> >
> > I don't want them to be able to redirect the issue to something else.
> >
> > Previously in this stream we've already elminated both Group Policy
> > and Server issues as potential reasons.
> >
> > I can see them pointing to the network as the next excuse (especially
> > for the data encryption errors - these are rare but they do happen).
>
 
Back
Top