Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
PcAnywhere32
- Thread starter PeterL
- Start date
CitrixEngineer
Technical User
PC Anywhere is not supported on Citrix MetaFrame.
Many technical staff have found issues with running this software, as documented in the support forum at
Many technical staff have found issues with running this software, as documented in the support forum at
Actually, I had a weird problem doing exactly that, but as we were troubleshooting the problem went away so I don't know if it was the exact cause of it. You see, we typically load any computer/server with PCAnywhere and our new TS/Metaframe server was no exception. Then the computer would BSOD on me all the time and the offending process would always be AWHOST32.EXE. So we reloaded the computer without it and all is fine and dandy...
except now I have a similar problem on the other server (we're load balanced) but I think it might be the RAM modules so we're going to try and switch them between the two.
So, yes... I did have a problem with PCAnywhere and Citrix but the answer above was correct... it already has the functionality so why bother.
My question is now: Does anybody have other suggestions for a TS/Metaframe server that likes to BSOD and then reboot back to life on its own? All it says in the system log when that happens is -
"The previous system shutdown at 11:51:21 AM on 11/1/00 was unexpected." Thats about it.
except now I have a similar problem on the other server (we're load balanced) but I think it might be the RAM modules so we're going to try and switch them between the two.
So, yes... I did have a problem with PCAnywhere and Citrix but the answer above was correct... it already has the functionality so why bother.
My question is now: Does anybody have other suggestions for a TS/Metaframe server that likes to BSOD and then reboot back to life on its own? All it says in the system log when that happens is -
"The previous system shutdown at 11:51:21 AM on 11/1/00 was unexpected." Thats about it.
You may be able to glean some information from the top 4 lines on the BSOD (keyword is "may"
.
The system will reboot itself after the stop screen if it is set to do that in what is called "Crashdump". This is available in control panel, in the "System" icon. On the "Startup/Shutdown" tab are the settings for crashdump. The setting for "Write debugging information to" causes the system to create a file with the contents of memory at the time of the crash. This is pretty much useless, takes up time and disk space, unless you plan to send it (and your credit card number) to Micreosoft for analysis.
Uncheck the "Automatically reboot" option to give yourself some time to analyze the blue screen - use TechNet (CD or online) - you may come close to the problem.
. The system will reboot itself after the stop screen if it is set to do that in what is called "Crashdump". This is available in control panel, in the "System" icon. On the "Startup/Shutdown" tab are the settings for crashdump. The setting for "Write debugging information to" causes the system to create a file with the contents of memory at the time of the crash. This is pretty much useless, takes up time and disk space, unless you plan to send it (and your credit card number) to Micreosoft for analysis.
Uncheck the "Automatically reboot" option to give yourself some time to analyze the blue screen - use TechNet (CD or online) - you may come close to the problem.
CitrixEngineer
Technical User
It is known that some device drivers can cause a terminal server to crash. Check that you have the latest drivers for all of your server's hardware, and that all your printer drivers are fully compatible.
Voyager1's suggestion of examining the crash dump files is the best way to find the root cause. The last few, in the list of drivers given, usually indicate where the problem lies.
You will not get a crash dump file if your pagefile is either not partially on the system partition, or at least equal to the amount of RAM in your system + 12Mb, ie if your pagefile is split over multiple partitions, the portion on your system partition must be equal to that formula.
I hope this information is helpful.
Voyager1's suggestion of examining the crash dump files is the best way to find the root cause. The last few, in the list of drivers given, usually indicate where the problem lies.
You will not get a crash dump file if your pagefile is either not partially on the system partition, or at least equal to the amount of RAM in your system + 12Mb, ie if your pagefile is split over multiple partitions, the portion on your system partition must be equal to that formula.
I hope this information is helpful.
- Status