[THIN] Re: Hotfix Rollup 3
- From: Evan Mann <emann@xxxxxxxxxxxxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Fri, 2 Mar 2007 08:39:46 -0500
Would I see any adverse effects to running R02+Post R02 fixes on the
majority of my farm servers, and R03 on 1 or 2 others? I need to add
some servers and going straight to R03 would save some hotfix time and
downtime later.
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Tom Monahan
Sent: Friday, March 02, 2007 6:16 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Hotfix Rollup 3
I have not heard anything more than a single post on this list about
printer autocreation failing which apparently was resolved by
reinstalling the rollup. There was a post about the wyse 3200 legacy
devices that have WinCE 2.12. So if you have legacy devices with or old
client I'd make sure those worked before rollout.
If anyone has seen other issues then add to this. I wouldn't just deploy
any hotfix rollout without testing it first. But from the posts/lack of
posts about Rollup 03 after 3 weeks released there doesn't appear to be
too many problems with it.
(I hope I haven't jinxed myself :-) )
Thomas
On 3/1/07, Minero, Hector B CIV NSWCDD, K55 <hector.minero@xxxxxxxx>
wrote:
Since I got no answer for this, let me try again.
I've been reading about problems with Rollup 3, mainly printer
auto creation.
Does Citrix have a fix for this?
Do you recommend just having Rollup 2?
_________________________
Hector Minero
NSWCDD Code K55
Ph: 540.653.8859
Email: hector.minero@xxxxxxxx
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Minero, Hector B CIV
NSWCDD, K55
Sent: Wednesday, February 28, 2007 11:16 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Hotfix Rollup 3
I've been reading about problems with Rollup 3, mainly
printer auto creation.
Does Citrix have a fix for this?
Do you recommend just having Rollup 2?
_________________________
Hector Minero
NSWCDD Code K55
Ph: 540.653.8859
Email: hector.minero@xxxxxxxx
Other related posts:
