Yeah, that's a nice marketing statement. Clean room while technically
true, I will say that we did get a jump on the code by using
Tarantella's clean room implantation as our code base. :) But you'd
never recognize that early code from todays SRWC.
MS recently (very recently in the scheme of RDP) made the spec for RDP
public. Sun has licensed (i.e. paid MS $$$) a spec that includes
support, etc, but zero code (not available even if we wanted). It's
nice that the newer stuff is public though.
We are working on a lot of things in Sun Ray land, mostly windows & VDI
related, hopefully we will meat your needs in the very near future. :)
Datagrupa wrote:
I didn't know that you realy do a clean room implementation of the RDP
client. Our Sun sales rep told us many times that you share the same MS RDP
Client codebase with MS and that Connector is 100% compatible with the MS
RDP Client!
BTW, Specs from MS are changing every quater. I think, there are a lot of
updates or fixes on it (like RDP 7 spesc, session brocker support,
microphone redirection extention etc).
Nik
----- Original Message -----
From: "Craig Bender" <[email protected]>
To: "SunRay-Users mailing list" <[email protected]>
Sent: Friday, May 15, 2009 5:14 PM
Subject: Re: [SunRay-Users] Windows Connector 2.1 Ugly Bug & Missing
Features
I will verify what features are due out in the new version. I did check
the bug id's of the soon to be released patch and none match the
complaints coming (which is why it is critical to open a formal support
call) but that doesn't mean that is all the fixes that go into the
patch. I'll do my best to see if anything there matches up as well and
share it with the list since the patch is due out very shortly.
Bear in mind most of the new features are marketing driven and not
always to be 100% compatible with the MS RDP Client (in certain cases
it's impossible because we are not running a win32 based OS). In the
engineering world we'd love to create the perfect product but in the
real world we've had to do a clean room implementation of the RDP client
(no borrowing allowed from open source projects like RDesktop) that the
only blueprint we have is the RDP spec from MS. Designing software from
a spec, one that often is lacking info (or worse has *wrong* info) can
be a challenge to meet features and parity.
Datagrupa wrote:
Craig,
Sorry for possible offtopic & sarcasm, but I've spent one week calling &
emailing to local support. Then, I wrote about our problems on a Sun
owned
Sun Ray Software Forum
http://forums.sun.com/thread.jspa?threadID=5384158&tstart=0 and had NO
reaction too.
Regards
----- Original Message -----
From: "Craig Bender" <[email protected]>
To: "SunRay-Users mailing list" <[email protected]>
Sent: Friday, May 15, 2009 2:43 PM
Subject: Re: [SunRay-Users] Windows Connector 2.1 Ugly Bug & Missing
Features
Since sarcasm doesn't tend to play well over email, I'd just like to
issue a friendly reminder that is not a Sun owned list and in no way
shape or form does asking a question on this list equal placing a call
to support and having a support contract.
Datagrupa wrote:
OK, I'll suspend SunRay migration project untill the early summer
months.
Thanks.
Nik
----- Original Message -----
From: "Craig Bender" <[email protected]>
To: "SunRay-Users mailing list" <[email protected]>
Sent: Wednesday, May 13, 2009 5:38 PM
Subject: Re: [SunRay-Users] Windows Connector 2.1 Ugly Bug & Missing
Features
You can check the man pages for uttsc to turn on theming and other
user
experience features. Look for the beta in the early summer months,
but
contact your Sun sales rep for a roadmap and possible inclusion in
the
early beta program.
Datagrupa wrote:
SRWC 2.1 supports RDP 5.2 so these are neither bugs or missing
features.
1. User Experience Options Support was inrtoduced with XP
2. Network Level Authentication Support came from 2003 SP1
3. Microsoft Client 5.2 works perfectly with Session Broker.
If RDesktop suits your needs today, feel free to use it.
The problem is that RDesktop doesn't suit our needs. We want to use
supported and certified software, but now we have to use uncertified
RDesktop because it simply works.
We are working on many of these features for the next release.
Any release date? Some beta maybe?
Nik
----- Original Message -----
From: "Craig Bender" <[email protected]>
To: "SunRay-Users mailing list" <[email protected]>
Sent: Wednesday, May 13, 2009 4:53 PM
Subject: Re: [SunRay-Users] Windows Connector 2.1 Ugly Bug & Missing
Features
SRWC 2.1 supports RDP 5.2 so these are neither bugs or missing
features.
MMR supports XP and 2003, same story above. We are working on
many
of
these features for the next release. If RDesktop suits your needs
today, feel free to use it.
Datagrupa wrote:
Hi All!
We had a lot of issues trying to deploy Sun Ray DTU with Windows
2008
farm.
Ugly! No Session Broker Support (new name of Session Directory on
2008)!
Uttsc segfaults (crashes) when Session Broker sends reconnection
information
to a client. So, there is no chance to reconnect disconnected
session
if
Session Brocker is enabled using Sun Windows Connector. Especially
strange,
that old Microsoft Client 5.2.XXXX from XP Embedded based
thinclient
works
great. Temporary solution was using opensource rdesktop 1.6
because
it
doesn't crash (rdesktop 1.6 doesn't support Session Broker too,
but
users
can logon Windows with it).
Missing Features:
1. User Experience Options Support (rdesktop's -x). So there is no
ClearType
fonts support using Sun Windows Connector. Users was very unhappy
to
see
unantialiased font again on DTU.
2. Network Level Authentication Support (Using RDP Compatibility
Mode
Now)
3. 32 bit colors. Not realy missed, but...
4. Multimedia Redirection. If you spent some time to develop this
"really
important" feature against others, make it work with modern OS
like
Windows 2008.
Does somebody know a success story using Windows Connector with
Windows
2008?
Thanks & WBR
Nik
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
