User Log On/ICA client issue/XPe

I

Inthae Park

When I create an additional user profile on my XPe SP1
thin client. I give it "limited" permission. When I
create a ICA client, and afterwards try to launch the ICA
session, there is no Window/Video for the Windows log on
screen to Terminal Services. My administrator account
works fine. If I create user account with "computer
administrator" rights, it works fine. Once I
select "limited" permission to my user account, the ICA
windows does not appear when I try to launch it. Any
ideas? The HP t5000 does not have this problem. It
appears in the background the ICA session is active but I
do not see it.
 
I

Inthae Park

Hi KM,

I know I'm missing dependencies or some components, but I
don't know which ones are missing. I included all the
dependencies. I belive I'm missing some components
instead, however reviewing the HP image and mine, I can't
figure out which one is missing.

I tried the Filemon/Regmon tool, however there is too much
data to decipher. Any other ideas?

The component doesn't help either.

To further explain my problem, when you create an ICA
session, and launch it, once connected the Windows user
log on window appears, where you can type in your username
and password to the terminal server. When I use the newly
created user account with "limited" permission, and launch
the ICA session. The ICA session window does not appear
at all.

-----Original Message-----
Inthae ,

I didn't really understand your problem. You may be
missing dependencies or so. Try tools like Filemon/Regmon
to see if anything is
 
K

KM

Inthae,

Sorry I can't help you much with the issue.
When I integrated ICA client in to one of my images (it was a long while ago
and I created my own component that time) it worked almost right away. The
image was pretty heavy (~128M) and I did not pay attention to what
dependencies were for the ICA client.

Could it be a problem on the server side? Have you set enough permission for
the user or the group the user belongs to?
Take a look at this article:
http://www.winnetmag.com/WindowsSecurity/Article/ArticleID/20145/20145.html

I'd still suggest you to use Regmon/Filemon/Dependency Walker tools to find
out what's missing.

Maybe someone else from NG can jump in here and help you more.

KM
 
K

KM

Well... good to know about the limited access to MSLicensing\Store registry key.

Thanks for posting the solution here!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top