Remote desktop login

hello any one plz guide me ....i want to implement desktop to remote login like in windows ,
plz help..what are the API s i should refer
i think that i have to use rmi.....
but what about the screen.....? because when logged in another end desktop is shown in this side and he can access the files how to implement this?
thanking u in advance ..........

Read this and try again.
Good luck.

Similar Messages

Remote Desktop Login events

I am trying to capture through SCOM events when specific accounts RDP into servers. I know it is logon type 3 but the workstation name the session is initiated from is blank. Is there a specific configuration required to log this information?
Thanks
Paul
Paul Glickenhaus

IP addresses or workstations are not captured when Remote Desktop are enabled without Network level Authentication.
Run sysdm.cpl to open system properties, select Remote -> Remote Desktop -> Allow Remote Desktop -> Allow connections only from computers running Remote desktop with Network Level Authentication.
Also you can use
this c# project to log authentication events in sql server

10.5.4 problem, Apple remote desktop - login window

Since the update to 10.5.4 I noticed two problems (probably not related):
1. in system.log, many lines about ARD
Jul 1 14:28:49 ekPB com.apple.launchd[376] (com.apple.RemoteDesktop.agent[1859]): Did not die after sending SIGKILL 2910 seconds ago...
etc. every 5 seconds
Finally ends with
Jul 1 14:30:08 ekPB ReportCrash[2050]: Formulating crash report for process ARDAgent[915]
Jul 1 14:30:09 ekPB com.apple.launchd[376] (com.apple.RemoteDesktop.agent[1859]): Exited abnormally: Bus error
Jul 1 14:30:09 ekPB com.apple.launchd[265] (com.apple.RemoteDesktop.agent[915]): Exited abnormally: Bus error
Jul 1 14:30:09 ekPB ARDAgent [2051]: ******ARDAgent Launched******
Jul 1 14:30:09 ekPB ReportCrash[2050]: Saved crashreport to /Library/Logs/CrashReporter/ARDAgent2008-07-01-143004ekPB.crash using uid: 0 gid: 0, euid: 0 egid: 0
Never had this before 10.5.4
ARD is of course activated...
2. The machine normally operating under my administrator account (and connected to a FireWire disk used by Time Machine), at two different moments, coming back, I find my machine showing the LOGIN window ...
in System.log:
Jul 1 11:16:12 ekPB loginwindow[407]: DEAD_PROCESS: 0 console
Jul 1 11:16:13 ekPB /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[1362]: Login Window Application Started
Jul 1 11:16:17 ekPB loginwindow[1362]: Login Window Started Security Agent
and
Jul 1 13:39:58 ekPB loginwindow[1362]: DEAD_PROCESS: 0 console
Jul 1 13:39:58 ekPB /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[1856]: Login Window Application Started
Jul 1 13:39:59 ekPB loginwindow[1856]: Login Window Started Security Agent
New login is normal and I don't find any reason to justify the end of the sessions of the connected user.
Any Ideas ? Thanks !
MacBook Pro core 2 Duo 2,33 GHZ 3 GB, 160 MB disk, Leopard 10.5.4 connected to ADSL by modem and Airport Extreme (last update 5.3.2 done)

Greetings...
Haven't found a similar thread yet, but if there is, my apologies. I have the same problem with the login, and I can't seem to fix it with a reboot. I have ran disk utilities as well as trying to get in through a remote computer. Any ideas/fixes besides reinstalling to 10.5.3 would be of a huge assistance.
~nathaniel

Solaris Remote Desktop Login to Red Hat 5 Server

We have a number of Sun boxes running Solaris 8 and 9 and we need them to login to a Server running Red Hat 5. Have edited the /etc/hosts file to include the Red Hat hostname and ip address and when I enter the hostname it acts as if it is connecting to it, but then the cursor turns into a watch face and then kicks back to the login screen. Am I missing something minor or major??? Should also state that I can connect no problem to the server using hummingbird from PCs...

We are running SCOM 2012 server and have deployed the agent successfully to a number of Red Hat Linux servers. I am having an issue on about a quarter of the hosts, in that they appear as HEALTHY but are Grayed out and not green. When I look at the /var/opt/microsoft/scx/log/omiserver.log
file I see:
WARNING: wsman: authentication failed for user scom2012
I have verified that the system account is setup with the correct password and the runas account is setup with the correct password (i am able to deploy the agent from the SCOM server using it, so the passwords DO match).
Any ideas?
I've seen this on a few systems here when the agent has been upgraded but the old agent process does not die off. Just to rule it out, pick a node, make sure there are no instances of scxcimserver or scxcimprovagt and then start the agent and
see if the issue goes away. I've also seen wsman authentication failures related to the libssl issue that was fixed in yesterday's release.

Remote desktop connection caused host to lose a monitor and other settings

Hello
After a successful remote desktop login, on the host I can now no longer detect the 2nd monitor. Screen resolution on remaining monitor is off, it's gone over to use Microsoft Basic Display Adapter even though it was using the correct adapter previously.
Both previously working display adapters now show Code 12 error: "this device cannot find enough free resources that it can use". The system has also become very slow, when I right-click the desktop, it takes up to 30 sec for the menu to appear.
Anyone had a problem like this? I have restarted the computer several times, reverted system to a working state last week, done another successful remote desktop login/logout from my laptop to this computer.
Windows 8.1 Pro
Displays: Dell U2412M
Intel R HD Graphics 4600
Thank you in advance for any help/tips to help solve this problem!

This error message can also appear if the BIOS did not allocate enough resources to the device, I want to know how much RAM do you have on your computer, because the Display Adapter calls for extra RAM to run the monitor.
If you don’t have enough RAM to allocate, the monitor won’t start, that’s why the computer becomes very slow.
Here I suggest a possible solution:
Adjust the amount of memory dedicated to video/graphics. You can change that in BIOS. there might be an option in your PC's BIOS that lets you change the amount of system memory used for video/graphics.
You'll just need to find it in the BIOS, the BIOS options in the Advanced settings,
the option varies depends on the BIOS version
you can set the maximum memory that it can take to a lowest value.
Regards
Wade Liu
TechNet Community Support

The RPC server is unavailable while trying to take Remote Desktop of 2003 Server.

Dear All
Recently I am facing remote desktop login problem in on Windows 2003 Server.
While I am enter user name and password server give me logon error.
"The system cannot log you on due to the following error:
The RPC server is unavailable.
Please try again or consult your system administrator.
Kindly help me.........

I just started spontaneously having this problem yesterday. I am not aware of anything having changed that would prompt it, though I did do a Windows Update on all servers AFTER the problem manifested to see if that might fix it. (No such luck) For reasons
unexplained, the system HAS let me in a few times, though it hasn't been consistent, and now it seems to have locked me out entirely (except through the VSphere back door, explained below). I am running Windows 7 on my laptop, and I have received a report
of the same problem from another employee trying to log in from their computer, which I believe is also running Win7.
I am running two VMWare instances of Server 2003 R2, one Domain Controller and another production environment. I can RDP just fine to the DC, but not the production. Also, using the VSphere VMware management client on a separate machine, I CAN log in to
the production environment without a problem.
I have tried the fixes around restarting stopped services, but nothing has helped yet. I've also tried disabling my anti-virus temporarily, with no effect. I tried pinging the various IP addresses, and received timeouts on the 2 images, as well as their
host server. Again, though, I CAN log into the DC without issue.
Could someone please elaborate on how to create this registry key? On which image would I add this key? (I am a novice user, so using regedit is somewhat unfamiliar to me)
Any other thoughts about potential solutions?
Thanks!
Update Dec 15 2011: Just tried restarting the Production image, via VSphere, and then successfully logged in and out 3 times in quick succession by regular RDP. The symptoms have been temporarily soothed, though I wonder if the underlying problem remains?
Still no answer to why this happened in the first place, so I'd appreciate input.
Update Dec 16 2011: The problem came back this morning, and remained all day. I can still access by VSphere, but have other users who need to access by regular RDP. I'd rather not have to reboot the system constantly just to allow access... Any help is much
appreciated!

Can Aussie GP's use a Mac remote desktop to login to works Medical Director

My wife is a GP. Her practice runs Medical Director. The other doctors are able to log in from home over the net from their home windows computers. I rang Medical Director to ask if there was anything stopping her using the remote desktop from our home mac:
http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/ MISC/RDC2.0Public_Betadownload.xml
They gave me a very abrupt no, and said we need to buy a windows machine (something I am loath to do).
Are there any GP's out there using their macs at home to login over the net using a program like this..... or do we really have to do what the Medical Director people say - and use a Windows Machine?
Thanks for your help.

Chances are the director is full of it, and doesn't know what he/she is talking about. Find out what software the other doctors are using from home and perhaps we can find you a Mac version of it.

Novell login not available with remote desktop on windows 7

Installed Novell Client 2 SP3 for Windows Server 2012 on my terminal server. When I log in from Windows XP to that terminal server I am getting an option to login with Novell Client. On Windows 7 however I only can logon to the server. What am I missing here?

djaquays <[email protected]> wrote:
> Mostly, that MS RDP for Mac ignores the authentication level:i:0 option
> in an RDP file and there's no GUI equivalent to force legacy
> authentication.
Microsoft's Network Level Authentication (NLA) feature is supported in
Windows Server 2008 and later terminal servers, and supported by
Remote Desktop Connection (MSTSC) 6.x and later terminal clients.
Windows XP did not ship with a MSTSC 6.x terminal client, but it is
available optionally through Windows Update.
The NLA authentication is essentially requiring that valid Windows
user account credentials for the Windows Server machine must be
provided /before/ the RDP-level terminal session connection is even
attempted or permitted. If the Windows user credentials you're logged
in with on the client workstation do not already satisfy this
requirement, the NLA-aware MSTSC clients will prompt you for valid NLA
credentials before even attempting to open the terminal session.
In other words, NLA doesn't directly have anything to do with whom you
will become authenticated as within the terminal session, or whether
you'll reconnect to some other already-running terminal session; it's
a new default mechanism which requires Windows credentials for
authorizing you to create an RDP connection to the Windows Server
machine "at all."
Unfortunately Windows Server 2008 and later don't permit you to turn
NLA completely off. You can configure the Windows Server to always
require NLA, which means pre-MSTSC 6.x terminal clients will be unable
to connect. Or you can configure the Windows Server to "not require
NLA" ("Allow connections from computers running any version or Remote
Desktop"), but this still means Windows Server will use NLA if the
workstation's MSTSC client supports NLA.
The only option which has been available to "disable NLA" even when a
Windows Server 2008 or later terminal server and a MSTSC 6.x or later
terminal client are involved is to configure the
"enablecredsspsupport:i:0" setting in the MSTSC client's .RDP file
(e.g. default.rdp in the My Documents folder), in addition to
configuring the terminal server to "not require NLA."
Once you have "Allow connections from computers running any version or
Remote Desktop" set on the Windows Server, and
"enablecredsspsupport:i:0" set in the MSTSC client, now you're back to
the Windows XP & Windows Server 2003 behavior where an RDP terminal
connection can be established without first having to supply NLA
credentials, and the first thing the MSTSC client user will experience
is the full normal credential provider-based login experience just
like you see at the physical console of the terminal server.
Note that if you do leave NLA enabled and supply NLA credentials
during the MSTSC connection attempt, after successfully using those
credentials to authorize creation of the RDP connection, the MSTSC
client will /also/ default to using the NLA credentials as default
credentials to attempt logging on with within the terminal session
itself. In other words, if you successfully supply NLA credentials,
by default you also become logged in on the terminal session and go
straight to the desktop of the Windows user account specified in the
NLA credentials. So even though "NLA credentials" and "whom I will
logon as within the terminal session" are two separate things, by
default the MSTSC client tries to use the same credentials for both.
But it's not that the NLA credentials "must" be used for logging in on
the terminal session; that's simply the default behavior. If you
leave NLA enabled on the Server 2008 or later terminal server, after
NLA credentials are successfully used to authorize creation of an RDP
connection, if you wanted to instead be prompted within the terminal
session with the normal credential provider login experience, enable
the "Always prompt for password" on the Windows Server 2008 or later
terminal server.
(On the Server 2008 or later machine, under "Administrative Tools"
find the "Remote Desktop Services" group and launch the "Remote
Desktop Session Host Configuration" console. Highlight/select the
"RDP-Tcp" connection, right-click and select "Properties". On the "Log
On Settings" tab elect "Always prompt for password".)
That sounds like probably the scenario which fits best for the "I have
a Macintosh-based client which doesn't allow enablecredsspsupport:i:0
/ authentication level:i:0." You would leave NLA enabled on the
Server 2012 machine, but enable "Always prompt for password" in the
RPC-Tcp connection properties on the Server 2012 machine. Such that
after NLA authentication was performed and Windows allowed creation of
the terminal session, instead of immediately also attempting to login
within the terminal session as the Windows account specified in the
NLA credentials, Windows will instead present the normal interactive
credential provider login experience to allow the user to specify whom
they want to login as.
Finally, note that everything described above applies even to a
Windows Server and Windows client workstation that do /not/ have the
Novell Client for Windows installed. The same mechanisms remain in
effect even once the Novell Client is installed; the presence of the
Novell Client just changes what credential providers would be used or
presented within the terminal session once the terminal session was
allowed to be created. The fact that NLA is required by default and
requires valid Windows credentials in order to authorize an RDP
connection is still the same, regardless of whether the Novell Client
is present or not.
Alan Adams
Novell Client CPR Group
[email protected]
Novell
Making IT Work As One
www.novell.com
Upgrade to OES Community
http://www.novell.com/communities/co.../upgradetooes/

Possible to login into Win7 machine via Remote Desktop?

hey guys, i've been trying to find a solution to be able to write to NTFS drives. i've read that using exFAT is a good way to go. the other thing i wanted to try was to login to a Windows machine that's connected to the NTFS drive and write to it that way. how can i do this?
thanks

If you want to write to the NTFS drive via the Windows system, then you want to have Windows share the drive, so that you can use Mac OS X:
Finder -> Go -> Connect to Server -> smb://windows.machine.address/share_name
This would mount the shared NTFS file system on your Mac OS X system and allow you to read and write to it.
If you need to access the Windows Desktop, then use the above mentioned Microsoft RDC software, or download CoRD from MacUpdate.com. Both good Windows Remote Desktop Clients.

Remote Desktop Connection can't login to restarted PC

I can access my XP Pro PC using Remote Desktop Connection after I have logged in locally but if I attempt to access it after a restart, or after a startup from shutdown, I get a error message:
The client could not connect to the remote computer.
And then a list of reasons why it may not be working (non of which - as usual - apply).
I can access the PC with it's local keyboard and mouse and login in locally, then connect using Remote Desktop Connection on my mac just fine, but if I shut the PC down, restart it and try logging in from the Mac I get that error message.
BTW I tried finding info about this on the msft site but it's really useless.

Basically you can't login as the PC is not connected to the network.
Use the XP PowerToys to automate the login process.
http://www.microsoft.com/windowsxp/downloads/powertoys/default.mspx

Group Policy to clear down MRU lists and to clear or to prevent user login details for programs such as Remote Desktop from being recorded

Hi there,
Please can anyone instruct me on how to set up Group Policy to clear down MRU lists and to clear or to prevent user login details for programs such as Remote Desktop from being recorded. Your help would be much appreciated.
Kind regards,
RocknRollTim
P.S. I was redirected by a forum user off the Microsoft Community forum.

Hi RocknRollTim,
Agree with Jason. Using a script will be a better option.
Just addition, for history of RDP Connections, please open Registry Editor and follow the path:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default. Please check if find MRU registry items where the name (or the IP address) of the terminal server is kept in.
Please also follow the path: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Servers. It contains
the list of all RDC (remote desktop client) connections that have ever been established from this computer.
When expand Server folder and select a node, you will see the UsernameHint key that show the name of the user connected by rdp.
Please back up registry items to avoid unexpected issues before any operation.
If any update, please feel free to let us know.
Hope this helps.
Best regards,
Justin Gu
Thank you for responding back Justin Gu and I agree with both you and Jason Miller that a script can easily achieve this task. Thank you all for your help.
Many thanks,
RocknRollTim

Remote desktop - background login with unique resolution

Is it possible to use a Mac remote desktop Client with a separate desktop and resolution?
With windows rdp the client you have a background login with a unique resolution.
The resolution on my iMac server is a lot greater than that of the client.
I would prefer tologin without scaling and/or scrolling

Fixed
Ran - delete_ObjectSid_user.sh
This created new un-duplicated SIDS for all the users - This removed
all duplicating conflicts
Steve Babcock wrote:
> I found that all my problem users have Duplicate Sids (as do a number
> of PCs)
>
> How do I fix this ?
>
>
>
>
>
> Steve Babcock wrote:
>
> > I run both 2003 and 2008 Terminal Services
> >
> > Users can log into either server
> >
> > BUT, as of about 2 months ago, all NEW users that I create either
> > through iManager or MMC cannot log into the 2008 server
> >
> > I get the message on the Windows login "Welcome" screen after about
> > 10 seconds : X - "More Data is Available"
> >
> > Other symptoms :
> >
> > Using MMC and selecting the "Remote Control", "Sessions", or "Remote
> > Desktop Server Profile" tab, I get the message:
> >
> > Could not load the Remote DEsktop SErvices properties for this user
> > because: More data is available
> >
> >
> > This error only occurs on newly created users - all my old users
> > work fine
> >
> >
> > Any ideas would be welcome
> >
> > Steve

Remote App and Desktop Login Does NOT work

Hello there,
I have an easy one for you all. I am running Windows Server 2012 R2 Datacenter off a server at a university. This server is only intended to be shared with ~10 people doing various tasks like using programs installed and storing data. As
of now, I only have been able to do RDP from home with it. Having tried to setup remote app and desktop, it only works on the server itself and not on other computers, both on the same subnet and a completely different IP address altogether. Let
me break down my questions:
1. Though the security certificate is installed in Trusted Root Authorities, but the site is only trusted on the server and not on any of the other computers. How do I get the others to trust it?
2. Number 1 except this occurs in the Remote Desktop and App window as well.
3. Adding users would be under active directory administrative center-->[my server]-->Users-->Add right? I guess I cannot play with 'User Accounts' in control panel anymore.
Any help would be appreciated. Also, if anyone thinks I am better off doing other things like virtual desktop, then I am all ears. I just want to keep things as simple as possible.
Regards,
Ben

Hi,
Firstly, how to you reach the server from Internet, via host name, public IP address or VPN?
If you need to remote to the server via host name, can you nslookup the host name and get the correct public IP address of it?
Do you install the AD DS role on the server? Please let us know if you need the active directory environment.
Thanks.
Jeremy Wu
TechNet Community Support

Wireless disconnect after login with Remote desktop with wpa2

We have 5508 wireless controller with 1142 aironet acess points.... we configured Radius authentication on ACS 5.3 for wireless users
when we take remote desktop connection of wireless client ... it disconnects after 10 sec.
and when we logged in to client ... connectivity was lossed .. I have to reconnect Manually to client..
It's really frustrating for all our service engineers to work remotly ....... Please Help

Hi Santosh,
which vesrion of sw u r running on WLC ?
Open Caveats on 7.4.100.0, CSCuc78713 could be related to this;
CSCuc78713
Symptom: Wireless client cannot receive broadcast packets after broadcast key rotation.
Conditions: Dynamic WEP; 7.0.235.0, 7.2.110.0, and 7.3.101.0 controller software releases.
Workaround:
• Executes the config advanced eap bcast-key-interval 86400 in the middle of the night
• Change security setting to WPA2, and so on.
Regards

IOS Remote Desktop app and computers connected to SBS 2008--can't get it to work

I can connect directly to the server without a remote resource in the IOS app.
But I'd like to be able to connect to computers in the office like we can through RWW. RWW works fine, but not from my phone. (Yes I can connect to the server and take over computers from the phone but I don't want other people in the office to log
into the server first!).
I can never get the remote resources section in the app to connect. I usually get "Unable to locate any remote resources for the URL". error in the resources section. I've tried a simple "https://remote.domain.com", "https://remote.domain.com:987",
etc.
We have a self-signed certificate. I can't think of anything in the server setup that is anything other than normal.
I can do direct connect using "Remote Desktop Connection" in windows 7. In the remote desktop server settings I just put remote.domain.com and "Ask for password (NTLM)" for the login method. Then on the general tab I have just the
simple computer name and the domain\username. That's all I had to setup to get that to work.
Any suggestions?

Hi Michael,
Thank you for posting in Windows Server Forum.
Have you setup RD Gateway server in your environment? Are you trying to access the RWW through it?
On server side you can choose “Bypass RD Gateway server for local addresses” under RemoteApp manager and check the result.
For more information, you can check below links for detail.
Remote Desktop Client on iOS: FAQ
http://technet.microsoft.com/en-us/library/dn473015.aspx
Getting Started with Remote Desktop Client on iOS
http://technet.microsoft.com/en-us/library/dn473013.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Remote desktop login

Similar Messages

Maybe you are looking for