Implement Sun VDI in Sun ray 150, how???

Hi
I want implement Sun VDI software in my sun ray 150, but not find anything document about the implemetation,
my questions are:
Where is the implement, in sun ray 150, in server, where???
how implement sun vdi???
Where I find documents about implement sun vdi?
thanks

here is the documentation
http://wiki.sun-rays.org/index.php/VDA_Cookbook
//Lars

Similar Messages

Are there any information gathering tools or scripts for Sun VDI 3.1.1?

Hi,
Are there any information gathering tools or scripts for Sun VDI 3.1.1?
for problem reporting or service supportting , such as
ut_gather, a ksh based tool to collect all Sun Ray related information from a Sun Ray server.
http://www.sun.com/bigadmin/jsp/descFile.jsp?url=descAll/ut_gather_1_4_6
http://www.sun.com/service/gdd/index.xml
Sun Explorer Data Collector in The Sun Services Tools Bundle (STB)
http://www.sun.com/service/stb/index.jsp
http://www.unix-consultants.co.uk/examples/scripts/linux/linux-explorer/
http://www.slideshare.net/Aeroplane23/information-gathering-2
Windows MPSreports, msinfo32
Redhat sysreport
Suse Siga reportconfig
Any advice would be appreciated.
Thanks,

ut_gather versions are available on MOS under reference #1260464.1

Sun VDI 3.0 patch 2 - linux guest display is laggy/unusable

Hello.
We have setup Sun VDI 3.0 to test out ubuntu desktop images. We have it functionaly setup but the lag/redraw is unusable. For example opening, closing and moving windows around has a horrible lag and takes a second or two to redraw. Just doing an "ls" from the command line is noticeably slow. I couldn't figure out any good way to measure the visual slowness I am seeing so I hope my plain english description makes sense.
The environment is setup as follows
Solaris 10 update 7 on x64 hardware.
Sun VDI 3.0 patch 2 (patch 1 behaved the same)
virtualbox 2.0.10 (version 2.0.8 with patch 1 behaved the same)
Sun 7110 as storage device
Desktop Images tried on the desktop
RedHat 5.3 (32 bit) and Ubuntu 8.04.3 (32 bit)
We installed the Sun VDI software into the all on one host demo mode. Our host is configured with 24GB of memory (24gb of swap as well per requirements). The virtualbox installs were done on the 2.0.8 version of virtualbox and then imported into the vdi solution. We ran between 2 or 3 vm's at one time so the box still had plenty of ram left since we only allocated 512MB to each vm (tried uppping that to 3GB with no perf improvements).
The Sun Ray units we tried is a stand alone 270 and 1 2FS unit. Surely i'm not the only one attempting linux desktops. I loaded up an windows XP desktop for testing purposes and it functioned great. Barely noticeable performance difference. Any ideas on what I'm missing?
Thanks. Deet.

Dirk.
Thanks for the input. I made the changes you mentioned and got an order of magnitude improvement! I was guilty of being a Solaris admin looking for a Solaris problem:)
Deet.

Is it possible to use OpenSolaris for Sun VDI 3.1 core servers?

The documentation states that Sun VDI 3.1 core servers must be Solaris 10 (u7 or u8).
While it is not supported to use OpenSolaris (2009.06 dev_129/130 or SXCE snv_129) for the core servers, is this expected to work at all in practice (i.e. in a single-host demo environment)? Are there any issues regarding bundled recent SRSS and SSGD running on OpenSolaris platforms, in particular?
The problem is that a potential customer wants to evaluate Sun VDI and can spare some old Netra servers for the installation, which were acceptable as Sun Ray servers in previous life. These servers have two "eri" interfaces and a "dgc" interface, and need to connect to several networks (public, ldap, management and new test-sunray vlans). Solaris 10 does not provide drivers for "eri"'s nor "dgc"'s to create VLANs, so the customer wants to try OpenSolaris and CrossBow to spawn VNICs or VLANs. If that goes well indeed, my original question stands up.
If this is known not to work, we'll save some time from pointless tests and push requests for different hardware :)
TIA,
//Jim

I had a similar problem. One of my VDI test systems is from HP and and has a RealTek "RTL81xxx" chipset that is not supported under Solaris 10. But there is this page here:
http://homepage2.nifty.com/mrym3/taiyodo/eng/
Take a look. There are many free Ethernet drivers for Solaris there. You have to compile them yourself, but the process is straightforward (just follow the instructions). I was able to get my Ethernet interface working via the "gani" driver, so my interface got the name "gani0". It may look odd, yes ... but it works. VDI now works tip top on that HP machine. Take a look at that page above ... maybe you can find the right drivers for your cards too?
Regards,
DJ.

Sun VDI 3.1-EA: "Microsoft Remote Desktop" Provider -- Bug?

It seems there is a bug in VDI 3.1:
After having added a VirtualBox desktop provider I also wanted to add a Windows 2003 terminal server as desktop provider, so I go ...
- https://localhost:1801
- Desktop Providers
- Windows Remote Desktop
- New ...
- Step 1 ... Next
- Specify New Host
... And now it asks me for this information:
Host:
SSL Port: 443
User Name:
Password:
SSL Port? For a Windows 2003 server?
I am confused ... So I want to check the "Help" tab. The "Help" tab links to this URL:
https://localhost:1801/vda/faces/jsp/providers/tswizard/NewTSProviderWizard.jsp#
So guessing from that URL ( ... "NewTSProviderWizard" ...) I'd expect to find information regarding Windows TS servers?
But the help text reads ".... Enter the hostname or IP address, and administrator credentials for the *+VirtualBox+* host server ... "
VirtualBox? I wanted to get help with Windows 2003 TS.
So I'd assume that this is a bug?
- the "Add Microsoft Remote Desktop" wizard will get you the one for VirtualBox
- Help text is talking about VirtualBox too
I assume that this will be fixed before the final release?
Regards,
DJ.

What specifically does your customer object to ?The server being +"touched"+. That's already enough for them. I'm ashamed to admit this ... but I too was a Windows admin once. I was young, stupid and I needed the money. ;-)
So having been a Windows admin once myself ages ago in my dark past I can fully understand them. One stupid patch, one stupid incompatible product, one silly addon someone somewhere wrote ... and that server dies in a nice ugly "Bluescreen of Death". Or so they think. Because a typical Windows admin spends 90% of their daily job running from one dying Windows server to another dying Windows server the last thing they want is yet another server that is bound to die because one of us unworthy Penguin worshippers dared to install something on it ....
So NOT having to install anything on that server like with SSGD is perceived as being OK.
Having to install ANYTHING on that server for which the admin doesn't understand the reasons within 1 second simply is a NO GO for them.
+"Why doy ou want to install this BS? My RDP connections work tip top without that thing you want to install ... take your hands off my server ... "+
So ... How do I explain to a very very stressed and hyper-nervous Windows server administrator that I need to install some SSL stuff on his precious Windows 2003 or Windows 2008 installation when SSGD (also from Sun last time I checked ...) didn't need that? And none of his other RDP applications need that?
How do you explain something like that? YOU CAN'T. The discussion is over even before it can begin. And if their Windows administrators are screaming like mad and panicking that you are about to hose their precious Windows systems then soon enough even their managers (who up to that second were on your side) demand an explanation ... "Why does VDI require that when SSGD didn't require that??"
In the end it's easier for me to configure an Windows RDP application via SSGD and deliver it that way to the VDI sessions than argue with the customer and their nervous admins about why in the world I now have to touch their servers with this stuff ...
See what I mean? Yes, I know: I exagerated slightly. Just to give you a feeling of the troubles us people in the frontlines are facing.
SERIOUSLY:* The RDP-Provider in VDI 3.1 is in need of being re-evaluated and re-designed. Like it or not: But it simply is not going to fly the way it is now. Most Windows admins simply don't want any additional stuff installed on their servers. PERIOD. Because only the Gods know what other things such stuff will break one day ...
So the RDP provider in VDI 3.1 should look and feel and act exactly like the one in SSGD. If you want to offer RDP-over-SSL: fine, offer it as an option for the lucky few who don't have to argue with their customer about that.
RIght now it's easier for me to create a Linux VM that auto-boots into a pre-configured "rdesktop" session and then deliver that as a login option to users than to argue with the Windows admins why their precious servers need to be touched ... So yes, I'd say this part of the Sun VDI 3.1 product is in need of a re-design.

Sun VDI - Two Factor Authentication

Dear Colleagues,
The simple way to implement two factor authentication is by replacing the vdaclient.jar. We are working on RSA SecurID authentication with SSO support, by using the Windows password integration feature of RSA SecurID. The RSA Authentication Manager (version 6+) has a field for caching the Windows password, normally used by the Windows Authentication Agent (6.1+). These agent API methods are not available in the JAVA agent API nor the c API for Solaris, but we will work around this for our new RSA Authentication Agent for Sun VDI.
If I understand the broker service correctly, this will not be a solution for direct RDP connections. Users can only be challenged with their AD username and password, the broker will test the credentials using Kerberos and if successful proxy a RDP connection on behalf of the client.
Does anyone know a possible alternative? Does a roadmap exist for full two factor authentication support on the broker?
Best Regards,
Arno Staal
Divider B.V.

Hi
Thanks for your response. I don't think I made myself clear. We run UAG 2010 and have not implemented Direct access. We now have many users wishing to access our internal resources. Our internal info security bods have demanded we provide a two factor authentication
methodology. Direct access need at least Windows 7 enterprise on the client. We cannot afford the licencing. Nor can we currently afford windows 2012 cals. What I was after was a method of implementing two factor authentication on our current UAG
portal. I have access to a radius server. I am not an expert on UAG the guy who was has left.
Regards

Sun VDI 3.1.1 error with Sun 7310

Hello,
I'm working on a Sun VDI solution using a 7310 with Sun Storage 2010.Q1.0.0 and am having a provisioning error when importing a template or desktop. It errors about copying disk image to storage. Upon switching to a Solaris ZFS storage server the issue goes away. I'm curious if anyone else has run into this issue and if the Sun Storage OS should be update or if there are specific configuration variables that should be set in the ZFS storage pool being used by the Sun VDI implementation.
Thank you,
Mike

Okay, after some issues with the 7310 that is being used for this pilot I was able to do some more testing to generate logs around the failures. I have been able to get this to work with a regular Solaris 10 iSCSI and NFS server that uses ZFS. In fact it worked perfectly but that isn't the storage array that is meant for this project. The Sun VDI implementation is accessing the 7310 using the 'root' account and is connecting over gigE SAN. We can see Sun VDI logging into the storage array, it creates the '/suspend-data' NFS share right away as it should. When I got to import a template you can see it deploy the iSCSI LUN and the associated Target and IQN.
Here are snippets from the cacao log showing the different failure messages.
Jun 17, 2010 3:42:58 PM com.sun.vda.service.vbox.VBDesktopProvider createDesktops
FINE: thr#22 Created desktop on 10.72.169.169 with volume ec0263c0-eaef-4636-a2ac-96046e4fc81e at IQN iqn.1986-03.com.sun:vdi:kgksyhsior0abizjhg.g:exlbox2mm0szsgnr7ed- of size 17179869184
Jun 17, 2010 3:42:58 PM com.sun.vda.service.persistence.PersistenceImpl commit
FINEST: thr#22 Committing object [id=14] class com.sun.vda.service.persistence.PersistentStorage
Jun 17, 2010 3:42:58 PM com.sun.vda.service.storage.Volume importFromFile
FINEST: thr#22 Copying from /sunvdi/templates/solaris10/solaris10.vdi to ec0263c0-eaef-4636-a2ac-96046e4fc81e on host 10.72.169.169 for user root
Jun 17, 2010 3:42:58 PM com.sun.vda.service.persistence.PersistenceImpl update
FINEST: thr#22 Updating object [id=14] class com.sun.vda.service.persistence.PersistentStorage
Jun 17, 2010 3:42:58 PM com.sun.vda.service.persistence.PersistentJob commit
FINEST: thr#22 Committing object [id=null] class com.sun.vda.service.persistence.PersistentJob
Jun 17, 2010 3:42:58 PM com.sun.vda.service.core.jobs.Job run
INFO: thr#23 Starting Job[192]: STORAGE_ACTION for [Solaris 10, STORAGE_AND_ISCSI_RESSOURCE: INITIATOR:iqn.1986-03.com.sun:01:2a95e6efffff.4beb10d0]
Jun 17, 2010 3:42:58 PM com.sun.vda.service.persistence.PersistenceImpl update
FINEST: thr#23 Updating object [id=192] class com.sun.vda.service.persistence.PersistentJob
Jun 17, 2010 3:42:58 PM com.sun.vda.service.persistence.PersistentJob commit
FINEST: thr#23 Committing object [id=192] class com.sun.vda.service.persistence.PersistentJob
Jun 17, 2010 3:42:58 PM com.sun.vda.service.persistence.PersistenceImpl update
FINEST: thr#23 Updating object [id=14] class com.sun.vda.service.persistence.PersistentStorage
Jun 17, 2010 3:42:58 PM com.sun.vda.service.vbox.SshServer executeCommand
FINEST: thr#23 Executing command script run('cd /') ; run('configuration') ; run('san') ; run('initiators') ; run('iscsi') ; run('create') ; run('set alias=vdi:2a95e6efffff.4beb10d0') ; run('set initiator=iqn.1986-03.com.sun:01:2a95e6efffff.4beb10d0') ; stdout = run('commit') ; print(stdout) on host 10.72.169.169:22 for user root
Jun 17, 2010 3:43:00 PM com.sun.vda.service.vbox.SshServer executeCommand
FINEST: thr#23 executed script run('cd /') ; run('configuration') ; run('san') ; run('initiators') ; run('iscsi') ; run('create') ; run('set alias=vdi:2a95e6efffff.4beb10d0') ; run('set initiator=iqn.1986-03.com.sun:01:2a95e6efffff.4beb10d0') ; stdout = run('commit') ; print(stdout)
Jun 17, 2010 3:43:00 PM com.sun.vda.service.vbox.SshServer executeCommand
FINEST: thr#23 Executing command script run('cd /') ; run('configuration') ; run('san') ; run('initiators') ; run('iscsi') ; run('groups') ; run('create') ; run('set name=vdi:2a95e6efffff.4beb10d0') ; run('set initiators=iqn.1986-03.com.sun:01:2a95e6efffff.4beb10d0') ; stdout = run('commit') ; print(stdout) on host 10.72.169.169:22 for user root
Jun 17, 2010 3:43:01 PM com.sun.vda.service.vbox.SshServer executeCommand
FINEST: thr#23 ...
Jun 17, 2010 3:43:01 PM com.sun.vda.service.storage.Initiator$CommitThis doAction
FINEST: thr#23 Committing initiator com.sun.vda.service.storage.Initiator@16708cc
Jun 17, 2010 3:43:01 PM com.sun.vda.service.persistence.PersistenceImpl commit
FINEST: thr#23 Committing object [id=null] class com.sun.vda.service.persistence.PersistentStorageInitiator
Jun 17, 2010 3:43:01 PM com.sun.vda.service.persistence.PersistentJob commit
FINEST: thr#23 Committing object [id=192] class com.sun.vda.service.persistence.PersistentJob
Jun 17, 2010 3:43:01 PM com.sun.vda.service.core.jobs.Job run
FINE: thr#23 Job[192]: STORAGE_ACTION for [Solaris 10, STORAGE_AND_ISCSI_RESSOURCE: INITIATOR:iqn.1986-03.com.sun:01:2a95e6efffff.4beb10d0] finished.
Jun 17, 2010 3:43:02 PM com.sun.vda.service.persistence.PersistenceImpl update
FINEST: thr#22 Updating object [id=14] class com.sun.vda.service.persistence.PersistentStorage
Jun 17, 2010 3:43:02 PM com.sun.vda.service.persistence.PersistenceImpl update
FINEST: thr#22 Updating object [id=14] class com.sun.vda.service.persistence.PersistentStorage
Jun 17, 2010 3:43:02 PM com.sun.vda.service.storage.Volume$CommitShareData doAction
FINEST: thr#22 Committing target:com.sun.vda.service.storage.Target@65e initiator:com.sun.vda.service.storage.Initiator@6bc lun:-1
Jun 17, 2010 3:43:02 PM com.sun.vda.service.persistence.PersistenceManager retry
FINEST: thr#22 Error committing target: com.sun.vda.service.storage.Target@65e Trying again ...
Jun 17, 2010 3:43:02 PM com.sun.vda.service.persistence.PersistenceImpl update
FINEST: thr#22 Updating object [id=41] class com.sun.vda.service.persistence.PersistentStorageVolume
Jun 17, 2010 3:43:02 PM com.sun.vda.service.storage.Volume$CommitShareData doAction
FINEST: thr#22 Committing target:com.sun.vda.service.storage.Target@65e initiator:com.sun.vda.service.storage.Initiator@6bc lun:-1
Jun 17, 2010 3:43:02 PM com.sun.vda.service.vbox.SshServer executeCommand
FINEST: thr#22 Executing command script run('cd /') ; run('shares') ;run('select sunvdi') ; run('select ec0263c0-eaef-4636-a2ac-96046e4fc81e') ; run('set writecache=true') ; run('set status=online') ; run('set targetgroup=vdi:exlbox2mm0szsgnr7ed-') ; run('set initiatorgroup=vdi:2a95e6efffff.4beb10d0') ; stdout = run('commit') ; print(stdout) on host 10.72.169.169:22 for user root
Jun 17, 2010 3:43:04 PM com.sun.vda.service.vbox.SshServer executeCommand

Your chance to contribute to the upcoming Sun VDI Software release!

Hi folks,
For those of you that have downloaded the early access of Sun VDI Software 3.1, you can let us know how the product is working out for you by filling out our extremely short survey here:
[http://www.surveymonkey.com/s.aspx?sm=_2bOaIS5LgthO0B125F5_2bVLg_3d_3d]
We'd really appreciate your participation to help us make this release as good as it can be!
And for those of you that haven't downloaded the EA of Sun VDI Software 3.1, you can get it free here:
[http://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SunVDI-3.1-EA-SP-G-F@CDS-CDS_SMI]
Thanks!
-Chris

Hi folks,
For those of you that have downloaded the early access of Sun VDI Software 3.1, you can let us know how the product is working out for you by filling out our extremely short survey here:
[http://www.surveymonkey.com/s.aspx?sm=_2bOaIS5LgthO0B125F5_2bVLg_3d_3d]
We'd really appreciate your participation to help us make this release as good as it can be!
And for those of you that haven't downloaded the EA of Sun VDI Software 3.1, you can get it free here:
[http://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SunVDI-3.1-EA-SP-G-F@CDS-CDS_SMI]
Thanks!
-Chris

Sun ONE Studio 4 aka Forte: How to set the output path for classes ?

Help !
Beginner's question:
Sun ONE Studio 4 aka Forte:
How to set the output path for classes ?
As default, the class files are created in the same directory as the
sources.
In opposite, both JBuilder and Together support that there is a tree
with the sources and another tree with the classes.
The first answer I got was "not possible with Forte, but just if you write your own "ANT Build script" !
a) Please point me to a ready-to-use ANT script for this purpose, if such is available
b) Is using ANT instead of the MAKE as comfortable ? Besides the separation of sourcecode and classes, I would like to keep everything else to be the same, i.e. I don�t want to edit the ANT file if I enlarge the project by directories or files.
Tia
Sincerely
Rolf

You can set S1S's options to place newly created .class files in a specific location.
Identify the compiler that is being used - Open the S1S's Tools/Options window, expand Editing and select Java Sources. Note the Default Compiler value. (If it's one if the Ant options, you use Ant to specify this option, not S1S.)
Open the S1S's Tools/Options window, expand Building/Compiler Types and select the appropriate compiler.
The Properties tab of the compiler has the property Target, which sets the filesystem where the compiler output is directed. If you choose <not set>, the .class files are written to their source directory.
When you set the Target, your change affects all classes that use this compiler.
Very few options can't be set in S1S; the challenge is finding out where they're set!

Sun VDI 3.0 Patch 3 is now available at SunSolve

Hi folks,
we just released a third patch revision for Sun VDI 3.0. The patch binaries are available at SunSolve:
[Patch ID 141481-03 (Solaris 10 sparc) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141481-03-1]
[Patch ID 141482-03 (Solaris 10 x86) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141482-03-1]
Please notice that due to CR 6880209 ("The VirtualBox 2.0.x web service doesn't require clients to authenticate") both patch binaries are flagged as security relevant. This affects customers using VirtualBox as virtualization platform. A corresponding Sun Alert (268328) will be published soon.
This patch is accompanied with a minor update release of VirtualBox (*VirtualBox 2.0.12*). This updated VirtualBox version must be installed after applying the Sun VDI 3.0 patch 3 (see instructions below). The updated VirtualBox installer for Solaris 10 is available from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp]. VirtualBox binaries for other operating systems, for example, for creating desktop templates on your preferred platform, are available here.
- Klaus
The following steps are recommended for updating VirtualBox installations:
1. Login to the Sun VDI administration UI (http://yourserver:1800)
2. Select the affected VirtualBox desktop provider
3. Switch to the "Hosts" tab
4. Select the desired VirtualBox host and click on "Disable"
This ensures that no new desktops/virtual machines will be balanced/started on this host. Please notice, that this will not stop any already running desktops on this host. Thus you either need to ask users to shutdown their desktops or you explicitly trigger the shutdown/power off yourself using the administration UI. After the shutdown, users can immediately request their desktops again - new desktops will automatically be started on the remaining (enabled) VirtualBox hosts (assuming that more than one VirtualBox host is configured in your setup).
5. Download the updated VirtualBox installer from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp] and extract the archive in a temporary location.
6. Un-install the previous VirtualBox version by triggering
# vbox_2.0/vbox-install -u7. Install the new VirtualBox version by executing
# vbox_2.0/vbox-install8. If the installation fails due to an issue with the VirtualBox kernel module, reboot the machine and repeat step 7 again.
The installation of the new VirtualBox version will change the SSL certificate of the web service. Thus you need to re-import the certificate in Sun VDI 3.0 to establish the communication again.
1. In the Sun VDI administration UI select the affected VirtualBox desktop provider.
2. Switch to the "Hosts" tab
3. Select the desired VirtualBox host and click on "Edit"
4. In the host wizard confirm the changed certificate and click on "Finish"
The last step is to enable the VirtualBox host again:
5. On the "Hosts" tab select the disabled VirtualBox host and click on "Enable"
At this point the Sun VDI 3.0 system will again balance desktops to the updated VirtualBox host. You can now update the next VirtualBox host in your setup.

Hi folks,
we just released a third patch revision for Sun VDI 3.0. The patch binaries are available at SunSolve:
[Patch ID 141481-03 (Solaris 10 sparc) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141481-03-1]
[Patch ID 141482-03 (Solaris 10 x86) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141482-03-1]
Please notice that due to CR 6880209 ("The VirtualBox 2.0.x web service doesn't require clients to authenticate") both patch binaries are flagged as security relevant. This affects customers using VirtualBox as virtualization platform. A corresponding Sun Alert (268328) will be published soon.
This patch is accompanied with a minor update release of VirtualBox (*VirtualBox 2.0.12*). This updated VirtualBox version must be installed after applying the Sun VDI 3.0 patch 3 (see instructions below). The updated VirtualBox installer for Solaris 10 is available from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp]. VirtualBox binaries for other operating systems, for example, for creating desktop templates on your preferred platform, are available here.
- Klaus
The following steps are recommended for updating VirtualBox installations:
1. Login to the Sun VDI administration UI (http://yourserver:1800)
2. Select the affected VirtualBox desktop provider
3. Switch to the "Hosts" tab
4. Select the desired VirtualBox host and click on "Disable"
This ensures that no new desktops/virtual machines will be balanced/started on this host. Please notice, that this will not stop any already running desktops on this host. Thus you either need to ask users to shutdown their desktops or you explicitly trigger the shutdown/power off yourself using the administration UI. After the shutdown, users can immediately request their desktops again - new desktops will automatically be started on the remaining (enabled) VirtualBox hosts (assuming that more than one VirtualBox host is configured in your setup).
5. Download the updated VirtualBox installer from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp] and extract the archive in a temporary location.
6. Un-install the previous VirtualBox version by triggering
# vbox_2.0/vbox-install -u7. Install the new VirtualBox version by executing
# vbox_2.0/vbox-install8. If the installation fails due to an issue with the VirtualBox kernel module, reboot the machine and repeat step 7 again.
The installation of the new VirtualBox version will change the SSL certificate of the web service. Thus you need to re-import the certificate in Sun VDI 3.0 to establish the communication again.
1. In the Sun VDI administration UI select the affected VirtualBox desktop provider.
2. Switch to the "Hosts" tab
3. Select the desired VirtualBox host and click on "Edit"
4. In the host wizard confirm the changed certificate and click on "Finish"
The last step is to enable the VirtualBox host again:
5. On the "Hosts" tab select the disabled VirtualBox host and click on "Enable"
At this point the Sun VDI 3.0 system will again balance desktops to the updated VirtualBox host. You can now update the next VirtualBox host in your setup.

Connecting to Sun VDI service takes 4 minutes

Hi,
I have a Sun VDI 3.1 setup with one virtual primary broker, two physical secondary brokers and 3 additional connection brokers.
I have vmware at the backend as a desktop provider.
When a SunRay connects to one of the additional brokers a RDP session is almost instantly available.
When a SunRay connects to one of the secondary brokers it takes exactly 4 minutes to connect to the desktop.
does anyone have an idea?

Hi,
I have a Sun VDI 3.1 setup with one virtual primary broker, two physical secondary brokers and 3 additional connection brokers.
I have vmware at the backend as a desktop provider.
When a SunRay connects to one of the additional brokers a RDP session is almost instantly available.
When a SunRay connects to one of the secondary brokers it takes exactly 4 minutes to connect to the desktop.
does anyone have an idea?

Sun VDI 3 Patch 2 is now available at SunSolve

Hi folks,
in case you have not noticed it already, we have just released a second patch for Sun VDI 3.0. The patch binaries are available via SunSolve:
[Patch ID 141481-02 (Solaris 10 sparc)|http://sunsolve.sun.com/search/document.do?assetkey=1-21-141481-02-1]
[Patch ID 141482-02 (Solaris 10 x86)|http://sunsolve.sun.com/search/document.do?assetkey=1-21-141482-02-1]
Please notice that due to CR 6856923 ("ESC - Secure authentication disregards the user DN and is actually working as anonymous binding") both patch binaries are flagged as security relevant. This affects customers that use or plan to use secure LDAP authentication for retrieving information from a user directory. A corresponding [Sun Alert (265488)|http://sunsolve.sun.com/search/document.do?assetkey=1-66-265488-1] has been published.
This patch is accompanied with a minor update release of VirtualBox (*VirtualBox 2.0.10*). The updated VirtualBox installer for Solaris 10 is available from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp]. VirtualBox binaries for other operating systems, for example, for creating desktop templates on your preferred platform, are available here.
This updated VirtualBox version specifically addresses the issue around desktop recycling for non-Windows guest OS, filed as CR 6856906 ("Ubuntu/Opensol desktops does not get recycled on logging out the session"). Customers that want to use desktop recycling for Ubuntu/OpenSolaris desktops must also install the corresponding VirtualBox 2.0.10 guest additions.
Regards, Klaus

The following steps are recommended for updating VirtualBox installations:
1. Login to the Sun VDI administration UI (http://yourserver:1800)
2. Select the affected VirtualBox desktop provider
3. Switch to the "Hosts" tab
4. Select the desired VirtualBox host and click on "Disable"
This ensures that no new desktops/virtual machines will be balanced/started on this host. Please notice, that this will not stop any already running desktops on this host. Thus you either need to ask users to shutdown their desktops or you explicitly trigger the shutdown/power off yourself using the administration UI. After the shutdown, users can immediately request their desktops again - new desktops will automatically be started on the remaining (enabled) VirtualBox hosts (assuming that more than one VirtualBox host is configured in your setup).
5. Download the updated VirtualBox installer from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp] and extract the archive in a temporary location.
6. Un-install the previous VirtualBox version by triggering # vbox_2.0/vbox-install -u7. Install the new VirtualBox 2.0.10 version by executing # vbox_2.0/vbox-install8. If the installation fails due to an issue with the VirtualBox kernel module, reboot the machine and repeat step 7 again.
The installation of the new VirtualBox version will change the SSL certificate of the web service. Thus you need to re-import the certificate in Sun VDI 3.0 to establish the communication again.
1. In the Sun VDI administration UI select the affected VirtualBox desktop provider.
2. Switch to the "Hosts" tab
3. Select the desired VirtualBox host and click on "Edit"
4. In the host wizard confirm the changed certificate and click on "Finish"
The last step is to enable the VirtualBox host again:
5. On the "Hosts" tab select the disabled VirtualBox host and click on "Enable"
At this point the Sun VDI 3.0 system will again balance desktops to the updated VirtualBox host. You can now update the next VirtualBox host in your setup.

SUN VDI Configuration Setup.

Hi,
I'm setting up a laptop to demo the SUN VDI Environment.
The only system available to me is an HP laptop running windows 7.
My plan was to install Virtual Box
Create a Solaris 10 virtual install
Install SUN vdi.
But now i've read that this is not supported, Taken from http://wikis.sun.com/display/VDI3dot1/VDI+Demo+(Featuring+Sun+VirtualBox)
You must perform the installation on a physical machine (bare metal). Installing the VDI software in a virtual machine will not work.
I know there is a single system solution to this problem, ive seen SUN demo it!
So will it work? I Know it's not an ideal solution. It's only to be used to demo SunRay technology for sales pitches etc.
Many thanks in advance.

Hi,
Thanks for that. I'd come to that conclusion over night. Currently on with an install of solaris 10 so i can dual boot the laptop. I've seen SUN demo the VDI solution on a mac book but I guess they were dual booting or had solaris installed. Wanted to get it all on one neat box just for demo purposes in sales pitches etc.
Thanks very much for your help
Cheers
Haydn.

Error "java.lang.NoClassDefFoundError: sun/security/provider/Sun" in 10.1.2

Hi,
I developed an ADF UIX application in JDeveloper 10.1.2. It works fine when I run on embedded oc4j in my machine.
I deployed it to Oracle Application Server 10g in AIX. When I run the application from the Application Server and try to open a uix page with data I get the following error:
500 Internal Server Error
java.lang.NoClassDefFoundError: sun/security/provider/Sun at oracle.jbo.common.ampool.PoolMgr.createPool(PoolMgr.java:280) at oracle.jbo.common.ampool.PoolMgr.findPool(PoolMgr.java:482) at oracle.jbo.common.ampool.ContextPoolManager.findPool(ContextPoolManager.java:165) at oracle.adf.model.bc4j.DataControlFactoryImpl.findOrCreateSessionCookie(DataControlFactoryImpl.java(Compiled Code)) at oracle.adf.model.bc4j.DataControlFactoryImpl.createSession(DataControlFactoryImpl.java(Compiled Code)) at oracle.adf.model.binding.DCDataControlReference.getDataControl(DCDataControlReference.java(Compiled Code)) at oracle.adf.model.BindingContext.get(BindingContext.java(Compiled Code)) at oracle.adf.model.binding.DCUtil.findSpelObject(DCUtil.java:228) at oracle.adf.model.binding.DCUtil.findContextObject(DCUtil.java:308) at oracle.adf.model.binding.DCIteratorBinding.<init>(DCIteratorBinding.java:127) at oracle.jbo.uicli.binding.JUIteratorBinding.<init>(JUIteratorBinding.java:59) at oracle.jbo.uicli.binding.JUIteratorDef.createIterBinding(JUIteratorDef.java:58) at oracle.jbo.uicli.binding.JUIteratorDef.createIterBinding(JUIteratorDef.java:47) at oracle.adf.model.binding.DCBindingContainerDef.createIterBindings(DCBindingContainerDef.java(Compiled Code)) at oracle.adf.model.binding.DCBindingContainerDef.createBindingContainer(DCBindingContainerDef.java(Compiled Code)) at oracle.adf.model.binding.DCBindingContainerReference.getBindingContainer(DCBindingContainerReference.java(Inlined Compiled Code)) at oracle.adf.model.BindingContext.get(BindingContext.java(Compiled Code)) at oracle.adf.model.binding.DCUtil.findSpelObject(DCUtil.java:228) at oracle.adf.model.binding.DCUtil.findContextObject(DCUtil.java:308) at oracle.adf.model.binding.DCUtil.findBindingContainer(DCUtil.java:536) at oracle.adf.controller.lifecycle.LifecycleContext.initialize(LifecycleContext.java:121) at oracle.adf.controller.lifecycle.LifecycleContext.initialize(LifecycleContext.java:77) at oracle.adf.controller.struts.actions.DataActionContext.initialize(DataActionContext.java:51) at oracle.adf.controller.struts.actions.DataAction.execute(DataAction.java:150) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java(Compiled Code)) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java(Compiled Code)) at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java(Compiled Code)) at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java(Compiled Code)) at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java(Compiled Code)) at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.AJPRequestHandler.run(AJPRequestHandler.java(Compiled Code)) at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.AJPRequestHandler.run(AJPRequestHandler.java(Compiled Code)) at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java(Compiled Code)) at java.lang.Thread.run(Thread.java:568)
Can anybody tell/help why I am getting this error?
Thanks
Syed

I believe this counts to be a bug in adf. I met with such errors as well in migration 1012 from NT to AIX platform, and after decompiling adf jar code and tak a look at it, the following code block indicates that In class- oracle.jbo.client.Configuration
, it is hard coded to get secure provider- sun/security/provider/Sun, as listed below...
import sun.security.provider.Sun;
static void checkSecurityProviders()
Provider aprovider[] = Security.getProviders();
boolean flag = false;
for(int i = 0; i < aprovider.length; i++)
if(!aprovider.getName().equals("SUN"))
continue;
flag = true;
break;
if(!flag)
try
Sun sun = new Sun();
Security.addProvider(sun);
catch(Exception exception)
exception.printStackTrace();
Adam

Install Sun ONE Directory Server 5,2 & how to use it for authenticate user

Good afternoon, Excuse, are newbie in the scope I am learning and putting desire to him, this in my situation I am trying to install Sun ONE Directory Server 5,2 since I understand that this it is application LDAP for Solaris, ok I want to install it to authenticate user against the system, that is to say, to be able to acces the server entering with a created user from the data base of LDAP and make think user that his created in the system. But the documentation that I finds indicates the installation of Sun ONE Directory Server 5,2 but it not clearly about how to use it for authentication. Some one have any manual step by step of Sun ONE Directory Server 5,2 installation and how to make it for authentication systems users.
I read the forum seeking for anwser and i get confuse
Thanks for the help and sorry for any inconvenient
Message was edited by:
Aku_28
Message was edited by:
Aku_28

I think that I found the Sun endorsed book locations for using LDAP accounts that don't use authentication besides "crypt". I now can use an account with a "ssha" password. It can be more than 8 characters long.
Chapter 14 System Administration Guide: Naming and Directory Services
Read page 201 which is the pam.conf file pam_ldap setups. I edited my "/etc/pam.conf" file to reflect this
Chapter 7 Directory Server 5.2 2005Q4 - Administration Guide
Read page 316-318 which has a graphical technique to specify password syntax. I set it up and then tried the password by running "su - brahms". It now requires a longer password than 8 characters and it is set up to use "ssha" for that UID entry "brahms".

Implement Sun VDI in Sun ray 150, how???

Similar Messages

Maybe you are looking for