HP T410 zero configuration thin client autostart rdp session

Hello,
I have several T410 zero config clients. I am able to sucessfully configure teh RDP session. I would like the thin client to automatically launch the configured rdp session. So that when starting up the client or rebooting. The end user would not have to press the connect button for the session to connect. I have looked at the HP device manager console options and searched the thin client setup and have not found a option to have the rdp session automatically launch

Joe, welcome to the forum.
I believe that you will receive more responses to your questions if you start a thread here. They are the members who know more about your situation.
Please click the "Thumbs up + button" if I have helped you and click "Accept as Solution" if your problem is solved.
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee.

Similar Messages

JDBC THIN CLIENT in V$SESSION inactive

Hello DBA's
I have too many inactive session of JDBC thin client. Please suggest can we kill them?? or any other alternative
SID SERIAL# USERNAME PROGRAM STATUS Inactive_Hours
12 74 APPS JDBC Thin Client INACTIVE 1772.69806
13 31 APPLSYSPUB JDBC Thin Client INACTIVE 1772.69806
18 62 APPS JDBC Thin Client INACTIVE 1772.69806
20 1 APPLSYSPUB JDBC Thin Client INACTIVE 952.465556
22 9 APPS JDBC Thin Client INACTIVE 1772.69806
26 55 APPS JDBC Thin Client INACTIVE 92.1361111
30 2 APPLSYSPUB JDBC Thin Client INACTIVE 1772.61361
31 7 APPS JDBC Thin Client INACTIVE 1772.69667
53 29516 APPS JDBC Thin Client INACTIVE 521.344167
54 35 APPLSYSPUB JDBC Thin Client INACTIVE 1772.69278
69 7 APPLSYSPUB JDBC Thin Client INACTIVE 1772.69278
Can we kill them or any particular check before killing them??

I am not sure how you have computed the "Inactive Time".
You need to know if the middle-tier is configured to re-connect when necessary OR whether the middle-tier process will fail at the next SQL / operation it attempts to execute. So middle-tier processes can handle a kill gracefully, others cannot.
The usernames you list indicate that this is an Oracle EBusiness Suite install. You need to identify the services on the application server that correspond to these sessions and whether they can handle a kill gracefully.
Why do you need to kill sessions ?
Hemant K Chitale

Zero configuration for clients to use WSUS?

Hi all,
Just wondering if it's at all possible to set up WSUS to work without any configuration on the client end of things? Or at least minimal configuration.
We're a tech store, running/working on primarily Macs. We often have client's bring PC machines in, or VMs to install on the Macs, and I'm tired of waiting for updates to download on them.
Ideally, I'd have it like OS X Cache Server, I realize this is quite a bit different than how WSUS works, but I'd like to have the ability to simply connect the client's computer to the network and have it fetch the updates from my WSUS server instead of
re-downloading them all.
Thanks,

Just wondering if it's at all possible to set up WSUS to work without any configuration on the client end of things?
No.
Or at least minimal configuration.
The minimal configuration is that you have to tell it to use WSUS and where the WSUS Server is found. This is done by setting the policy setting
Specify Microsoft intranet update server location.
We often have client's bring PC machines in, or VMs to install on the Macs, and I'm tired of waiting for updates to download on them.
The best approach here is to create two REG files and put 'em on a thumb drive. One REG file SETS the policy to point the client to your WSUS server. The other REG file UNSETS the policy so the client reverts to being what it was before.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Wyse Thin client not connecting to Windows 2008 R2 server

Configuration
SBS 2011 Server
Windows 2008 R2 server with Remote Desktop Services installed, License Manager installed.
WYSE WT3125SE thin clients with Windows CE 5
I setup the Windows 2008 with Remote Desktop Services and was able to successfully connect the Thin client. Then I installed the License Manger and applied my Open license using User Cals. Was able to login. Next day I get the following
error-"Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again" I still can connect fine from other machines even Windows Home Ed.
I remove license server and still was unable to connect. Built a second Windows 2008 R2 server with RDS on it. Was able to connect without issue. Pointed it to the first RDS server license manager and have still been able to connect with
the Thin Client. The thin client can rdp to the SBS server without issue in admin mode, can connect to RDS2 server but not RDS1 with the license manger. So my issue is with the license and so my question is what is it with the license server
running on that server that is keeping thin client from connecting. I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. And then if I uninstall the license, rds, remove
from domain still not able to connect. Any help would be appreciated.

We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it.
The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because
of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again"
After reading all of the postings about this issue and tried the reactivate solution of the license server,
I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server.
What I did, I installed a new license server activate it but did not install licenses on it.
I pointed the defective rds server to the newly installed license server and deleted the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
Certificate
X509 Certificate
X509 Certificate ID
X509 Certificate2
Then reboot.
After the reboot all old terminals can connect fine again. As final step I pointed the rds server to the same license server as the other ones,
reboot and all worked fine.
So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates
that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the
x509 certs so it keeps working.
I hope this helps someone
This issue was driving me crazy so very happy that it is resolved now
Cheers Frits

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.

T410 thin client RDP Client Error Windows XP SP3 issue

I've switched out the VMs they were connecting to completely and we're still running into this issue. The next step is switching out the thin clients themselves. Bump if anyone's run into this issue before.

I'm having an issue with 2 of my HP Smart Zero t410 thin clients. They each RDP into an XP SP3 virtual machine hosted on a virtual server running VWWare ESXi 5.0.0. Randomly in the morning they'll both disconnect from their virtual machines. Sometimes at the same time, sometimes not. I'm monitoring both the thin clients and the virtual machines with software that pings everything 30 seconds, nothing ever drops a ping. I've tested the wire, the wire is good. I've made sure the thin clients are up to date with the latest firmware. The last thing I've tried is replacing the switch both of these machines are connection. One thin client comes up with an error message "RDP Client Error: Reboot Necessary" then below "The firmware has experienced a critical error. Please reboot this client." After I close the error I can RDP back in. The other thin client also gives an "RDP Client Error" and down below mentions MANTICORE but I did not write down the entire error message. I have 30 other t410's deployed at various locations, all connected via RDP to a Windows Server 2008 R2 terminal with no issue for over a year. These last two have maybe in for three weeks and have continuously thrown this error randomly. Any help is appreciated.

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

Surface pro 3 - using rdp - thin client - display resolution shrink

Hi,
I have a surface pro 3, using a thin client to access and run an application on our server. it is an access based application. the display of the forms and application display in a very small font - through the thin client interface. I
cannot figure out how to enlarge the font - msft tech chat suggested I post this question here as there seems to be no immediate resolution for now. if I plug a USB into the SP3 and open the app it displays wonderfully - any suggestions are welcome.
thank you,
john

Anyone?! :(
I think this device is trememdous - and could replace 'everyday business users' - maybe not hardcore IT/coder/developers - hardware - but it surely has the balls to keep Suzy happy while answering emails and buying shoes (so chauvenistic - I know - ok then
think Billy playing solitaire).
Struggling to find ANYone having woe's using a Surface Pro 3 through a VPN & thin-client. The resolution just shrinks to the point it's almost illegible. I downloaded the RDMC - but unsure of how or what to do with it, unfortunately.
Any suggestions are greatly appreciated.
John

Thin client T610 Zero Core admin password reset

I forgot admin password on T610 thinclient.
How can i reset it ?

Hello Hardw,
You are in the HP consumer products forum.
You will also want to ask in the HP Enterprise Business Community.
Here is the specific area for Thin Clients.
http://h30499.www3.hp.com/t5/Workstations-Thin-Clients/bd-p/bsc-635

HP T410 All-In-One (H2W21AA) serious RDP problem with terminal server

Hi there! The scheme is this:
HP T410 All-In-One (H2W21AA)
firmware that was out-of-the-box got some graphical problems with RDP, so i updated the Smart Zero Core Image to the latest Z6A44019 Rev. 1 (11 dec 2013). Graphical problem gone, but new, much more unpleasant problem emerged.
This thin client is connected to Windows Server 2008 R2 SP1, all updates are up-to-date. Terminal Server.
the steps:
- i connect from my machine (W7SP1x64 with latest updates) via RDP (mstsc.exe or tsmmc.mmc - doesn't matter) to the terminal server
- i open up the remote desktop services manager, right click on the user that's connected from the T410
- i hit "remote control" button
- for a moment i see some bits of user's desktop, but in less than a second my RDP session drops with the following error:
Problem signature:
Problem Event Name: APPCRASH
Application Name: mstsc.exe
Application Version: 6.2.9200.16398
Application Timestamp: 5036045e
Fault Module Name: mstscax.dll
Fault Module Version: 6.2.9200.16398
Fault Module Timestamp: 5035e59d
Exception Code: c0000005
Exception Offset: 00000000000f2220
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1049
Additional Information 1: 2328
Additional Information 2: 2328419a4b40d8964e7f792f0ac157d5
Additional Information 3: 3197
Additional Information 4: 319796c94d8825616721d114b3479569
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
the problem is not present for the rest on the terminal users (that are connected from a unix thin clients), i remote control their session without any issues.
Please help me. We are building a new office and planning it for using PoE on every workdesk with your T410 Thin Client. But the fact that i can't manage them remotely brings me a lot of grief.

Hello again! I am sad to tell that my solution was not fully effective - i have got the new problem now
when i remote control session, it connects and works for some time, but at some point (which can be even a second from connection) it disconnects, throws me back to my admin session, and on the client side of t410 the following message appears:

Creating a thin client network in VMWare Workstation

I have recently been informed that many our customers have a thin client network in place using Microsoft RDP, Terminal Services / Remote Desktop Services.
What I would like to do is create a virtual thin client network using Server 2008 | Server 2008 R2 | Server 2012. What I am not certain of is how to emulate the "desktop" environments for the clients and how to configure VMWare to work with this type of network.
Is this possible?
I admit that I have never configured a TS before, so hopefully someone here has done this before and can provide some pointers.
I have been searching Google for information but so far have come up short. Perhaps my search criteria is wrong.
I have VMWare Workstation 10 and access to MSDN for a number of ISOs.
Thank you.
Dan

user12049849 wrote:
I have Oracle VM server release 2.1.5, IPTABLES is disable on both the VM Server host and client. I am able to ping the gateway from the VM Host; but, not from the VM client. I can't even ping the VM Host from the VM client or ViceVersa.
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif2.0vif2.0 is the connection between the bridge and your guest. It is connected to xenbr0
peth0
vif0.0
xenbr1 8000.feffffffffff no peth1
vif0.1
xenbr2 8000.feffffffffff no peth2
vif0.2
xenbr3 8000.feffffffffff no peth3
vif0.3
ethtool -i peth1
driver: e1000
version: 7.6.15.5ora-NAPI
firmware-version: 5.11-2
bus-info: 0000:25:00.1Why are you showing us information about peth1? Did you intend to connect the guest to it / xenbr1?
VM HOST:
# ping 10.1.1.1
PING 10.1.1.1 (10.1.1.1) 56(84) bytes of data.
64 bytes from 10.1.1.1: icmp_seq=1 ttl=255 time=0.812 ms
64 bytes from 10.1.1.1: icmp_seq=2 ttl=255 time=0.765 ms
64 bytes from 10.1.1.1: icmp_seq=3 ttl=255 time=0.885 msWhere is this 10.1.1.1 on your network? What is the relevance of this output?
>
>
The VM Client ifconfig shows eth0 configured correctly IP, MASK and Broadcast, then the loopback... nothing else. Route command shows the correct Gateway. Well, nobody is perfect, so maybe you can post the complete config for review? Maybe you used xenbr1 when you should be using xenbr0, or something like that. Saying that it's correct is not the same as showing us that it is correct.
- ifconfig -a on dom0 and domU
- route -n on dom0 and domU
- vm.cfg of the domU

How i upload a web page named index.html generated by NI Web UI Builder in thin client application on world wide Web

Hello All,
I have an example which use simulated signal with its web service generated by LabVIEW. Then an application of this web service was created using NI web UI builder. And application was build and deployed on NI Cloud Portal, a zip file was downloaded of that project after build and deploying application.
The downloaded file contain a thin client application like :index.html page, readme file etc.
Now problems is this index.html runs easily on http://localhost:8080/appname/index.html or on my computer name like
http://iaa42:8080/appname/index.html web page runs and shows updated values in indicators and graphs but when i use ip address of my system like http://192.168.1.6:8080/appname/index.html , index.html runs but the values in indicator and graphs remains 0 (zero) constantly. how can i get all indicators and graphs updating continously on by using my ip address like same when i use localhost or computer name in url bar. 1st problem is this.
Now 2nd question.
I get a page index.html in a zip file built by NI web UI builder now i want this page to be viewed by every one world wide
where should i upload that code. Should NI Cloud Portal be my hosting server for that web page ? or i have to purchase a domain other than NI cloud portal?
Thanks in Advance
Regards
Waqas

Hi Waqas,
For your first question, my first thoughts turn to your router (which I assume you are using with a 192.168.x.x address). Are you sure you are configuring your ports and firewalls to allow NI services to function? Here is a really good resource on how to check if your ports and firewalls are configured properly:
http://www.ni.com/white-paper/12402/en/
For your second question, when you deploy a web service you are hosting it on your local machine. If you wanted to host it elsewhere (i.e. another server or another domain) you would have to be sure that the server hosting your application has the LabVIEW run-time engine installed.
Rick C.

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

Enable USB redirection on 2012 RDSH running on ESXi for thin client

What I have configured right now is Windows Server 2012 RDSH server installed on a ESXi 5.1 host.
I am going to be purchasing thin client machines that will need to use USB headphone/mic combo units. I need to make sure that the USB redirection will work from the thin client to the RDSH RDP session. I will NOT be using virtual machines
on the server, only a terminal session. Please help me with the following points.
1. Is windows 8 embeded my only option?
2. Does RemoteFX support USB redirection on server 2012 RDSH?
3. I have not been able to find an applicable guide to help me with what I am doing.
Thank you

Hi,
After referring your post, I can understand that you are looking for RemoteFX USB redirection on server 2012. Yes, server 2012 support RemoteFX USB redirection and can able to use the benefit of server. Here providing you the related article for configuration,
please go through beneath article.
1. RemoteFX USB Redirection in Windows Server 2012 and Windows 8
2. Configuring USB Device Redirection with Microsoft RemoteFX Step-by-Step Guide
3. Introducing Microsoft RemoteFX USB Redirection: Part 1
Hope it helps!
Thanks,
Dharmesh

Sun ray thin client printing issue ?

Hi Guys,
i was configured printer to print through sun ray thin client, but when i print its print carbage document, i changed that printer with another printer but still printing same, also i was change driver for that printer but the issue still , anybody advice me what shall i do ?
Thanks in Advance,
Basem

Hi,
Did you get to solve the problem? I was able to print from an RDP session but get continuous pages of garbage preceded by a banner page. Were you able to print from windows to a DTU attached USB printer?
Please advise.
Thank you and
BR,
Senka

HP T410 zero configuration thin client autostart rdp session

Similar Messages

Maybe you are looking for