Change thin client wallpaper

I am looking for a way to change the desktop wallpaper on an hp t5000 thin client.
I have tried copying the image that I want to use to the ram drive and selecting commit in the ewf menu.

Hello techdude101,
I understand that you want to change the wall paper on your thin client.
Here is a link to a document that will walk you through the steps.
Let me know how everything goes.

Similar Messages

  • Changing Connection Settings on Thin Client T410 using HP Device Manager

    Hi All,
    Actually it is not a problem rather than it is an inquiry regarding configuring connection on HP thin clients- t410 remotely using HP Device Manager Tool or any other tool,
    My inquiry is: in our organization we have around 500 t410 thin client or more, and we need to change the remote connection server address or name (connection type is RDP7) on these clients, as currently we have to do it on the remote clients one by one using shadowing option as detailed below steps (which of course is not convenient way).
    Currently we have the HP Device Manager v. 4.6.
    Steps:
    1- Click on “setting” and select “Administrative/User Mode Switch
    2- type admin. password.
    3- Click on setting as below and select “Edit Connection Setting”
    4- Under Conncetion Settings > Network > change the Address to x.x.x.x
    5- press OK then Reboot
    Thanks in advance and let me know if you need more details

    any one has info about this post, please his feedback

  • Database connection encryption and integrity with ColdFusion and Oracle thin client

    As ColdFusion datasource we are using the Oracle thin client to  connect with the database. So, basically we are using a JDBC URL such as  jdbc:oracle:thin:@... and as Driver Class oracle.jdbc.OracleDriver. This works successfully however we would like to set encryption and  integrity parameters as well. In Java this is done similarly by setting a  Properties object prior to getting a connection as follows:
    Properties prop = new Properties();
    prop.put("oracle.net.encryption_client", "REQUIRED");
    prop.put("oracle.net.encryption_types_client", "( DES40 )");
    prop.put("oracle.net.crypto_checksum_client", "REQUESTED");
    prop.put("oracle.net.crypto_checksum_types_client", "( MD5 )");
    OracleDataSource ods = new OracleDataSource();
    ods.setProperties(prop);
    ods.setURL("jdbc:oracle:thin:@localhost:1521:main");
    Connection conn = ods.getConnection();
    Is there a way that I can pass these parameters to the ColdFusion  datasource. Ideally, I would love to do this centrally in such way that a  change to all the cfquery or cfstoredproc is not needed.
    I also know that in application servers such as Oracle AS there is an  option when creating a datasource which says "Add Properties". In there  you can add such properties. So, I was thinking of maybe creating a  JNDI DS in the app. server and then magically connecting to it but this  may have some impacts on the app.
    Besides this I was also thinking of communicating with the CF  datasource through the CF admin API (cfide.adminapi.administrator) and  also the option of extending the Oracle driver so that when CF connects  with it these params are already set.
    I would love to have your professional opinion and suggestions on this.

    I believe the thin driver actually needs the IP address (not the DNS name). Also, is "java" the name of the Oracle instance to which you are trying to connect?
    Try the following:String driver = "jdbc:oracle:thin";
    String dbIP = "W2RZ1NXG01's IP address";
    String dbPort = "1530";
    String dbSid = "java";
    String dbUser = "Admin";
    String dbPswd = "apassword";
    String cnctStr = driver + ":@" + dbIP + ":" + port + ":" + dbSid;
    try
        Class.forName("oracle.jdbc.driver.OracleDriver");
        con = DriverManager.getConnection( cnctStr, dbUser, dbPswd );
        stmt = con.createStatement();
        stmt.executeUpdate(createString);
        stmt.close();
        con.close();
    catch(SQLException ex)
        System.err.println( "The following SQLException occurred: " + ex );
        System.err.println( "Message: " + ex.getMessage() );

  • Problem using Weblogic 6 and Weblogic 8.1 thin clients from same applicatio

    We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
    First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
    Exceptions:
    Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 6.1 SP7?.
         throws following exception while connecting to ?Weblogic 8.1?.
    weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
         at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
         at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
         at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
         at weblogic.kernel.Kernel.initialize(Kernel.java:138)
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    java.lang.InternalError: error initializing kernel
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    Case 2: ?Weblogic 8.1? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 8.1?.
         throws following exception while connecting to ?Weblogic 6.1 SP7?.
    avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more
    Couldn't connect to any host
    Cause: {1}
    javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
    Cause: {1}
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more

    uday naik <> writes:
    The thin-client isn't supported on 6.1, I'm not sure what you are doing.
    andy
    We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
    First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
    Exceptions:
    Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 6.1 SP7?.
         throws following exception while connecting to ?Weblogic 8.1?.
    weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
         at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
         at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
         at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
         at weblogic.kernel.Kernel.initialize(Kernel.java:138)
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    java.lang.InternalError: error initializing kernel
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    Case 2: ?Weblogic 8.1? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 8.1?.
         throws following exception while connecting to ?Weblogic 6.1 SP7?.
    avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more
    Couldn't connect to any host
    Cause: {1}
    javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
    Cause: {1}
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more

  • Installing Adobe Reader on a Thin Client

    I have 27 Thin clients (HP t5639w) to set up in the next day or two... the problem: right out of the box, I am unable to install Adobe Reader on them. I have made room to install by using a flash drive to increase RAM, and Reader appears to have successfully loaded, but each time I try to open after install I get the following error message: "Font Capture: AcroRd32.exe Application Error.... The exception unknown software. Exception (0xc06d007e) occurred in the application at location 0x7c812afb."
    I've tried to contact HP customer support - unfortunately, they refer me to the HP website and tell me to download the version there. It's the same version I've tried to install - no luck. I have installed other software on the Thin Clients successfully, but I'm only having an issue with Reader.
    Anyone else have a similar issue? Any ideas?

    Here's the process:
    ·         Download Adobe to USB drive
    ·         Remove write filter – reboot
    ·         Create temporary TEMP and TMP folders on C: drive
    ·         Change Windows TEMP variables (both TEMP and TMP) to a folder on the “Hard Disk” – Reboot (Make a note of values before changing).
    ·         Install Adobe Reader – Reboot
    ·         Run Adobe Reader – If runs reboot
    ·         Replace TEMP and TMP variable entries (Usually Z:\TEMP and Z:\TMP respectively) – Reboot
    ·         Delete temporary TEMP and TMP folders – reboot
    ·         Re-enable write filter
    This worked for me!

  • Font Smoothing CE 6.0 Thin Clients

    We need to handle Font Smoothing on HP Thin Clients. This is supported on newer Thin Clients with RDP7 and Font Smoothing settings.
    Older Win CE 6.0 do not appear to support Font Smoothing.
    Is there a way to set up Font Smoothothing or can these thin clients be updated with RDP option to support Font Smoothing?
    Thanks Lex

    I too had the same problem just last night. It happened when I was changing the font and font size. It seemed that everytime I switched the font and font size, the text got more and more pixelated and less smooth (identical to the screenshot you just posted).
    I backed up my Torch, did a security wipe and then restored the backup file back onto the device. That didn't work, as the text still looked horrible.
    So what I did next was do a device switch from my Torch back onto my Bold 9000, security wiped the Torch then did a device switch from the Bold 9000 back onto the Torch and the text was back to normal! It was a long process but it seemed to do the trick. So if you have another BlackBerry sitting around it might be worth trying, just remember to back up your Torch before hand.
    My Torch is also running v6.0.0.246, Platform 6.4.0.105 through Rogers. Hope this helps you out.
    Good Luck!
    Ed

  • Printer for Terminal Services / Thin Clients

    Hi, Just checking on what multifunction printer you would suggest for use with a Terminal Services environment? We only require the printer to go through TS. The other features will be used locally (photo copy/fax).
    I am looking at the CM2320, a good choice?
    Terminal Services: Windows 2003
    Thin Client: T5730 using RDP 6.0
    Many thanks

    Hi,
    Thank you for posting in Windows Server Forum.
    A mandatory user profile is a special type of pre-configured roaming user profile that administrators can use to specify settings for users. With mandatory user profiles, a user can modify his or her desktop, but the changes are not saved when the user
    logs off. The next time the user logs on, the mandatory user profile created by the administrator is downloaded. There are two types of mandatory profiles: normal mandatory profiles and super-mandatory profiles.
    User profiles become mandatory profiles when the administrator renames the NTuser.dat file (the registry hive) on the server to NTuser.man. The .man extension causes the user profile to be a read-only profile.
    User profiles become super-mandatory when the folder name of the profile path ends in .man; for example, \\server\share\mandatoryprofile.man\.
    More information:
    Mandatory User Profiles
    http://msdn.microsoft.com/en-us/library/windows/desktop/bb776895(v=vs.85).aspx
    Using User Profiles in Windows Server 2003
    http://technet.microsoft.com/en-us/library/cc776120(v=ws.10).aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • T5325 Thin Clients losing remote desktop connection

    My company just bought about 50 of these thin clients and they are setup to run an automatic remote desktop connection. I have the connection setup to auto start when the thin client is powered on and it just brings the user to a windows login screen. After they have logged in and leave their thin client to go on break sometimes it just brings them to a blank screen with an HP logo and the thin client has to be restarted to get back into the remote desktop, or I have to go into admin and restart the RDP connection. Any idea why this is happening? Is there a setting somewhere I need to change?
    Any help would be great!

    We are having this same issue and it is maddening.  I have contacted HP on several occasions and I don't know if it is the language barrier or simple ignorance, but so far the issue is ongoing.  I have looked high and low on the net and no one seems to be able to tell me why this is happening despite a number of plausible theories.  We have a couple hundred terminals throughout the company which are spread across three servers none of which are close to congested yet..  However, the 10 or so t5325's we have are used specifically for digital signage.  They run automated sessions that launch animated JAVA windows.  They run great for the most part, but seemingly at random they will freeze in their tracks.  The sessions drop from our terminal server and cannot be restarted remotely.  After the units are power cycled they come back up directly and begin their sessions again.  You can shadow these units (VNC) and the moment the display come on the unit closes the RDP session and reopens the same and start running again, odd behavior.  I have tried changing session logout timers, disabling / enabling TCP settings, creating client-side refresh scripts, restarting the sessions at regular intervals via admin script, flashing BIOS and ThinPro OS to the current level, voodoo rituals, and pagan sacrifice.  Yet, they still behave in exactly the same manner with no actions on my part having any apparent affect..  Currently, I am of the mind to purchase small all-in-one pc's to do the job.  If anyone knows of any way to fix this PLEASE respond to this post.

  • ADF panel opening too many JDBC Thin Client database sessions.

    Hi All,
    I have several ADF Panels, which allows the user to run a few simple queries against an Oracle database done using ADF view objects and ADF view links and ADF application module.
    Each ADF panel as I said contains several View Link queries, and links under the form of Jbuttons to other ADF Panels running other ADF View Links.
    Running the ADF Panel as described here opens up to 21 database sessions displaying as “JDBC Thin Client” when I look them up from v$session.
    Why do I end up with that many database sessions.
    Why doesn’t it just use one or two database sessions to run all these View Links? It seems that it is opening one database session for each of these view links.
    How can I change this destructive behavior? I only one to see one or two database sessions for the entire ADF panel no matter how many ADF View Links it contains.
    Your suggestions are most appreciated.
    Thanks.
    Bobby A.

    Thanks for your response.
    I took a quick look at the docs you pointed me to. It seems that I can set some parameters in bc4j.xcfg of each application module Home to control number of database connections that the application module will create. In that case maybe you can recommend which parameters and what value they should be set to.
    Your response will be most helpful as my background is rather in database admin and not java.
    Thanks.
    Bobby A.

  • OS_USER not correct when using JDBC Thin Client on 10G

    Hi Folks,
    We are migrating an application from a 9i database to 10g and have a problem that someone might have come across before.
    The application is a Java applet based application that connects to the database using JDBC Thin client. on 9i the OS_USER comes up as the user running the applet but in 10G it is coming up as the user account that installed 10G on the DB server.
    We tried using a 9i client to identify if it was a client or DB issue but its the same problem with the 9i client connecting to the 10G DB.
    If anyone can help it would be much appreciated.
    Thanks,
    John.

    Could you please provide further details on what do you mean with OS_USER?
    The application is a Java applet based application
    that connects to the database using JDBC Thin client.
    on 9i the OS_USER comes up as the user running the
    applet but in 10G it is coming up as the user account
    that installed 10G on the DB server.
    Are you referring to the user provided to perform authentication against database, i.e. a database user?
    How do you know this user is being changed?
    ~ Madrid

  • How to create mandatory (read-only) profile for Terminal Services user (HP Thin Client) on Server2003... aaarrgghhh!

    I've been tearing my hair out for a couple of days now...
    I'm trying to create a mandatory profile for users logging in from hp thin clients on a 2003 server at a school.
    I've set up a prototype user, then copied the proto user's NTUSER.DAT to NTUSER.MAN and renamed
    NTUSER.DAT to NTUSER.DAT_unused.
    At that point, logging in as the prototype user looks ok.  It was my understanding that renaming NTUSER.DAT to NTUSER.MAN would make it a mandatory profile, and the user (in this case the proto user) would be unable to change it.  However, in this
    case the user can still modify the desktop and those modifications are preserved across logins.  The NTUSER.MAN file is being updated, judging by the timestamp changes.
    What am I missing?  
    I've tried putting the NTUSER.MAN in the user's dir on the server
     (C:\Documents and Settings\ProtoUser),
    in the DefaultUser, and in AllUsers.
    Right now I'm getting a default, unmodifiable profile which I have no idea where it comes from.
    In case it matters, the original user and directory tree from which the NTUSER.MAN I'm trying to use has been deleted, but I wouldn't think that should matter.
    For example, I have the option to not show the security tab set in the group policy, but it is showing up.
    The Start menu is showing as the classic start menu, and I had it set for the "new" (2 column) one.
    I've got hide network places on the desktop set, but it's showing up.
    Is there a way to tell where a profile is coming from?
    I'm pretty confused at this point; any clarifications / tips would be much appreciated.
    Related questions:
      If both an NTUSER.DAT and an NTUSER.MAN exist, which is used?
      If no profile is found for a user in the normal place, what happens?

    Hi,
    Thank you for posting in Windows Server Forum.
    A mandatory user profile is a special type of pre-configured roaming user profile that administrators can use to specify settings for users. With mandatory user profiles, a user can modify his or her desktop, but the changes are not saved when the user
    logs off. The next time the user logs on, the mandatory user profile created by the administrator is downloaded. There are two types of mandatory profiles: normal mandatory profiles and super-mandatory profiles.
    User profiles become mandatory profiles when the administrator renames the NTuser.dat file (the registry hive) on the server to NTuser.man. The .man extension causes the user profile to be a read-only profile.
    User profiles become super-mandatory when the folder name of the profile path ends in .man; for example, \\server\share\mandatoryprofile.man\.
    More information:
    Mandatory User Profiles
    http://msdn.microsoft.com/en-us/library/windows/desktop/bb776895(v=vs.85).aspx
    Using User Profiles in Windows Server 2003
    http://technet.microsoft.com/en-us/library/cc776120(v=ws.10).aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Rich desktop GUI functionality on a thin client

    is it possible to implement a graphical higherarcial tree like GUI representing orgainsation -> teams -> users on a thin client, where by its possible to drill down from an orgainsation down to the user , also to be able to drag and drop users between different teams, with a back end servelt then kicking off the back end processes to update the users association to a different team? the users need to have roles and privalges assoctaied to them with a log in facility?
    there needs to be right click functioanity to add users, delete users , etc...
    also once drilled to an individaul user i need to be able to display all details of the user edit / enter the details of the user allocate privialges for the user , allocate types of work to the user ---all this though i understand as its just simple requests to retrive data from data base or display data from database ---the issue here though is that i need to be able to display this in sepearte panes / frames (ie. smaller windows ) next to the graphical tree structure of the users and have tabs at top to be able to go to the dufferent types of forms (ie. the form to edit the user deitals , form to prsent the types of work to allocate to user, form to set prvilages for user etc...) ie. these all seem like just forms but they need to reside inside tab liknks within there own window / frame.
    my understanding is that i can use web portal here to represent these different forms in there own window but how would they then be linked to the graphical representation of the user. ie as i change the user i need to be able to retrieve all his data etc.. i suppose it can kick off a servlet to get that data - what is the best way to do this functuality.
    is this type of functioanlty possible on a thin client - web browser?
    i have read things on AJAX to do asyncrounous calls to back end processes - but how do i make this transactionallly safe then ie. what if i drag and drop a user and use java script to trigger a back end process to change the user to a different team but the back end process fails but i've already made the change on client side - or maybe i dont quite undersatnd ajax , maybe ajax keeps the rest of the unchanged data static and waits on the transactional change of user to occur before alloing the drag and drop of user to be dedrawn ??
    please i need some advice on types of technology that can be used to implemnet this functionality. i've been told about struts not being good enough and JSF being the new better tech - i need to implement it in weblogic server , using weblogic web portal.
    Thanks - in advance.

    Hi,
    It may causes by Web Proxy with HTTP Authentication. Check if you enable it or not, if yes, please try to disable HTTP Authentication on the Web Proxy and test again.
    Please also refer to the requirements for
    Lync VDI plug-in:
    The following are requirements for the virtual machines running on the data center computer:
    Virtual machines must be configured with Windows 8, Windows 7, or Windows Server 2008 R2 with the latest service packs.
    The following are requirements for the user and the user’s local computer:
    The user must be homed on Lync Server 2013.
    The local computer must be running Windows Embedded Standard 7 with SP1, Windows 7 with SP1, or Windows 8.
    More details:
    http://technet.microsoft.com/en-us/library/jj205304.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Using SBO with Wyse Winterm S30 Thin Clients

    I have a customer who is using Microsoft Terminal Services via Wyse Winterm S30 Thin cllents to access SBO over a VPN.  We are experiencing excessive rolling (redisplay) when screens are refreshed. The problem is compounded if a Marketing Document contains multiple Text lines. We have two terminal servers, each with about 12 thin clients connected.
    I would appreciate feedback from anyone with experience of using thin clients, regardless of brand.

    Hi,
    Thin clients normally have a low memory allocation on the video card (8mb to 16MB) so this can be a problem.  Check to see if you can change this in the BIOS on the WYSE.  If not connect at 256 Colours to reduce this.  If you have pictures linked to products then their resolution will not be good but for SAP itself the difference is small.  Also rename the SAPSS.AVI to .old if you have not already done so so that the splash screen does not come up when logging in.
    In my multimedia testing on thin clients, unrelated to SBO, I found that both memory and processor power made a huge difference, which is contrary to thin client manufacturer claims.  As an example I used a 200MHz/64MB TC for a flash application and sound was about 3 seconds behind the image and the image update would skip 3 to 5 frames when updating.  Moving to a 800Mhz/128MB TC The frame refresh rate was almost perfect and the sound was only about 0.5 seconds behind.  I would therefore test on a more powerful thin client to see if it improves performance.
    The S30 is a 400MHz (rated @ 533 on performance by AMD).   Try a 1GHz TC with the maximum Video memory you can find.
    We are currently using VXL Itona 800Mhz/128MB and do not experience too much rolling but we are using 256 colours.
    Hope this helps.

  • HFM Thin Client and Thick Client

    Hi
    can anyone tell me what is HFM thin client and thick client
    Thanks

    Thick client is the actual application client view. Most administrators limit that view to only them and provide a workspace (the thin client) as a method of accessing hfm. This is because more can be done in terms of metadata and security changes in the thick client than the thin client.

  • Thin clients, labs, and applications

    We have thin clients in some labs and have a specific virtual desktop load specific for that lab.  The issue;  students do NOT have to log into the network and we want to change this.
    Our issue:
    We have 10 licenses for an application in a lab.  The virtual desktop has this application for 10 computers within the specific lab.
    If we have students log onto the network, they will have to option of selecting which virtual desktop to open (multiple courses taken by the student, multiple labs = multiple virtual desktops)
    If a student logs in from the library, they will see all the virtual desktops as well and could use one of the 10 mentioned above, thus using up one of the virtual desktop application licenses.
    This leaves one student in the lab not able to connect.
    Question:
    Is there a way to either limit what the student can select based on location/IP address or is there another way to make sure that virtual desktop is only used within that lab?
    I have been told that virtual desktops are user based and therefore cannot be altered in this way...so, checking here.
    TIA,
    --cdburns

    We have a similar requirement, as we are replacing physical labs with VDI zero and thin clients and want them to behave similarly.  Our physical lab environment had different software setups for different locations (Geology, Audiology, Nursing, etc.).  We have locked down access to the VDI environment (the broker) from on-campus only, and the majority of our zero and thin clients are setup to auto-login to a specific pool - getting rid of the areas where students can select which pool to log into.
    There is one exception where we had to be more harsh because of compliance reasons.  We could only let students log into a specific lab pool if they were using specific thin/zero clients.  You've already mentioned our solution to this as we used VLANs to restrict this access.  The VMs in the pool resides in a VLAN that only allows the PCoIP protocol access from another VLAN where the authorized zero/thin clients reside.  While authorized students would be able to see the pool selection if presented on their own or unrestricted device - they wouldn't be able to fully take control as the PCoIP connection wouldn't work.
    Another option is to use the broker labels.  We abandoned this option as it didn't seem to be scalable and we'd have to potentially setup multiple broker servers in order to accomplish this.
    I'm waiting for vmware to come out with a better solution.  You'd expect there to be a desire to restrict access to various pools based on the client endpoint or location.

Maybe you are looking for