HT5422 Different versions of Remote Desktop Admin 3.6.1

How do Remote Desktop Admin 3.6.1 from 24 Sept with Download ID SL1595 and 14.73 MB in size and another from 3 Dec labelled DL1570 and 14.75 MB in size differ?  Perhaps this is a version labelling problem, the one from 3 Dec perhaps is actually 3.6.2?  There's two separate support pages for the separate downloads, the titles are a little different with some juxtapositioning, "Apple Remote Desktop 3.6.1 Admin" and "Apple Remote Desktop Admin 3.6.1", respectively. My existing copy of Admin 3.6.1 only offers to update clients to Client 3.6.1; I installed Client 3.6.2 manually on the clients via downloading from the download page for it. Gonna wait on the Admin to see if Apple fixes this soon.

There's nothing to fix here. The newer 3.6.1 Admin updater only includes the latest 3.6.2 client software. This updates someone's system properly when they're coming from and Admin version prior to 3.6.1. If you already had Admin version 3.6.1 installed then then you'll be offered the 3.6.2 update on Lion systems. The update is not necessary for 10.8 - 10.8.2 as the only bug fixed was with iChat on Lion. Of course you can manually install the 3.6.2 client update on your Mountain Lion systems if you'd like.

Similar Messages

  • Remote Desktop Admin 3.4

    Hello
    When upgrading my admin computer, I'd to buy a license of compatible version of Remote Desktop Admin, I mean 3.4.
    I connect wo problem, however my remote keyboard is seen as a Qwerty keyboard.
    Although I found many threads  complaining with this, I haven't found any solution.
    I cannot imagine to work like this ; passwords are impossible to enter.
    Please, tell me someone know how to fix this ?

    Probably get a reasoned response posting to the ARD forum: http://discussions.apple.com/forum.jspa?forumID=1007

  • Software Update on New MBA lists Remote Desktop Admin 2.2 but fails

    Using my new MacBook Air running Lion, when I run Software Update, it comes up with one item, Remote Desktop Admin Update 2.2, which is old software.  I don't have any version of Remote Desktop Admin installed.  If I try to do the update, it fails.  Any idea what's causing this or how to resolve it?  Thanks!

    Several places to look for crude that may fool ur mac into thinking it's installed outside of the /applications dir which I assume you checked already, right?
    in user/library/application support
    in system/library/preferences
    in system/library/applcation support/apple
    Outside of cleaning up the files, you could try the ARD support forum also here.

  • Apple Remote Desktop Admin 3.7.2 Yosemite wake issue

    Another serious problems is.... Apple Remote Desktop Admin 3.7.2 in Yosemite cannot wake up clients Mac remotely. Control has no problem after waking up.
    On 10.9.x I can wake up remote Mac clients if sleeping. Now I have to do it on the other Mac running older OS version.

    I have a different issue.
    Just updated s classroom full of computers and desktop client will no longer observe more than on computer at a time. I can no longer observe groups of computers. Any thoughts on this issue guys? Mac OSX Yosemite 10.10

  • HT201068 Updated Remote Desktop Admin 3.8 and now my Time Capsule wireless connection is slow

    I recently updated to Remote Desktop Admin 3.8 and since then, I have had issues with the wireless connection from my Time Capsule.
    1) I reset modem and had no change. 2) I then plugged the ethernet directly into my Mac and the connection was great so it's not the service or modem.
    3) I hard reset the TC and when it came back, the speed was good but went back down after a few minutes. 4) Plugged ethernet directly into Mac and again, the speed was great so it is definitely the TC.
    Would love some help resolving this. Hoping I don't have to get a new wireless router. Maybe the TC is too old? I purchased it in 2009 or 2010/ Current version 7.6.4

    Most home routers running 24/7 are good for about 3years.. your TC has now managed to survive 6 years.. it is well and truly time for a replacement. Simple fact is, it should be dead by now.. so you are living on borrowed time whatever happens.
    Why RDA would slow the wireless I am not sure..
    Are you running Yosemite.. ?? I tend to point the finger at the OS rather than an application.. mind you if the amount of data going back and forth has increased.. what appears to be slower wireless might actually be something else.
    Apple has reasonable wireless analyser built into the OS since mountain lion.. it is well worth using.
    http://osxdaily.com/2012/07/31/wi-fi-scanner-mac-os-x-mountain-lion/
    I recommend doing a few things like short names, no spaces pure alphanumeric for everything in networks. Passwords also must comply. Apple made changes to network protocols since Mavericks but did not fix the names being recommended in the airport utility.. and still haven't which break their own rules.
    And fix names for bands differently so you can force the connection.. plus setting channels.
    However in a unit of that age.. it will have pretty weak 5ghz and that is what is important for high speed wireless.. Apple have hindered 2.4ghz since forever.

  • Apple Remote Desktop admin update now won't open 3.5.1

    So a few days ago I updated Apple Remote Desktop admin and now the program won't launch. It says that the admin version is not compatible with the client. I went to apple's software updater and it doesn't show that anything needs to be updated on the client side. Any suggestions?
    Running on:
    Mac Pro
    Snow Leopard 10.6.8

    Okay thanks,  dragging the old app to the trash and logging into the app store did it.  What threw me a bit is that it was asking for my credit card info in order to process the download.  Evidently it only was doing this because it had an old card stored in the system.  I don't THINK it charged me to download again .

  • Remote desktop admin 3.8

    Is remote desktop admin for accessing my desktop from another device?

    This update (1.1 and earlier currently) breaks screen sharing on OSX computers other than Yosemite.  There is a bug in the software update.
    They should have only updated Yosemite computers and not those still running earlier OSX versions. 
    There is an explanation on how to downgrade to 3.7 in another thread by UM-LinuxGuru:
    "UM-LinuxGuruMar 24, 2015 1:09 PM Re: mavericks messages not screen sharing
    Re: mavericks messages not screen sharingin response to David Vrooman
    I happened to stumble across this issue. I loaded a test machine with a Mavericks 10.9.0 installer, then selected upgrades to see what would break it. It is RDC Update 3.8.2 v1.1. After spending time with AppleCare, they told me I might see a fix in a week. Right. I need a fix right now.
    So, I used my 15 years of Linux diagnostic skills, and came up with a quick fix, which I will test further. I downloaded Apple Remote Desktop 3.7 Client . If you try to install it now, it will say, "Can't, newer already installed." Fine. goto /Library/CoreServices/, archive RemoteManagement, then put RemoteManagement in the trash (as admin), and empty the trash. Now run the 3.7 installer. I now have screen sharing again, while I wait for Apple's fix.
    I will test updates 3.7.1 and 3.7.2 if I can find them."
    Robert had a correction to this instruction:
    "One correction: the path to the Remote Management folder is: /System/Library/CoreServices/  (not /Library/CoreServices/)"
    Yosemite Messages Screen Sharing Broken? 
    The ARD client 3.7 solves screen sharing problems on non-Yosemite computers until they make the upgrade.

  • HT201068 I updated Remote Desktop Admin 3.8 and now my Time Capsule wireless connection is having.

    I recently updated to Remote Desktop Admin 3.8 and since then, I have had issues with the wireless connection from my Time Capsule.
    1) I reset modem and had no change. 2) I then plugged the ethernet directly into my Mac and the connection was great so it's not the service or modem.
    3) I hard reset the TC and when it came back, the speed was good but went back down after a few minutes. 4) Plugged ethernet directly into Mac and again, the speed was great so it is definitely the TC.
    Would love some help resolving this. Hoping I don't have to get a new wireless router. Maybe the TC is too old? I purchased it in 2009 or 2010/ Current version 7.6.4

    Hey evebutterflies,
    I see that you are having some connection issues with your Time Capsule. Are these issues only present when using Remote Desktop Admin 3.8? If so, you may need to review the information in the following article and see if this sheds some light on the issue:
    Apple Remote Desktop: Troubleshooting Connection to Client Behind NAT Router
    http://support.apple.com/kb/TA20780
    Thanks for coming to the Apple Support Communities!
    Cheers,
    Braden

  • Using Remote Desktop Admin app in more than one user account.

    Is possible to have the ARD admin app use the same database and settings over more than one user account?
    eg. I have ARD setup on my Mac as I am in charge of our organisations Macs. However if I am away for a few weeks, one of our other techs would be able to turn on my Mac, log in to a generic account, open ARD and it would be set up exactly as I have it in my user account.
    I know that I could manually set up ARD in the other account, but with the number of machines we have I would rather not have to re-enter all those admin passwords all over again, and then have to remember to update ARD in the other account everytime we get a new machine or make other changes.

    In theory, you could simply copy the com.apple.RemoteDesktop.plist into the preferences folder of the other user. Then they would simply have to know the Remote Desktop Password (which is probably stored in your KeyChain.)
    I've never tried this, but it seems like it would work.

  • Remote Desktop Admin - Scanner can't see clients.

    Hello,
    I have a couple of copies of Remote Desktop UNL admin packages that are used in a education environment. Remote desktop has been working great in all but one lab, where the scanner has trouble finding any machines. It may sporadically find a random machine, but most of the time only shows the machine it is on. I can ping the other machines from the admin station, and the network setup is simple - 24 computers plugged into two 12 port 10/100/1000 D-Link switches, along with a G5 server running only AFS and DHCP.
    I've re-installed Remote Desktop, double checked my client settings, and to no avail. Anything I may be missing or should look at?
    Thank you!

    Hello,
    I have a couple of copies of Remote Desktop UNL admin packages that are used in a education environment. Remote desktop has been working great in all but one lab, where the scanner has trouble finding any machines. It may sporadically find a random machine, but most of the time only shows the machine it is on. I can ping the other machines from the admin station, and the network setup is simple - 24 computers plugged into two 12 port 10/100/1000 D-Link switches, along with a G5 server running only AFS and DHCP.
    I've re-installed Remote Desktop, double checked my client settings, and to no avail. Anything I may be missing or should look at?
    Thank you!

  • Remote Desktop Admin 3.2 Freezes with Spinning Wheel

    I have an Intel MacBook and Intel iMac, both with 10.5.1 installed. I use them to admin a classroom full of iMacs. After logging onto the computers today I noticed that I can not get Remote Desktop to function. Every time I open it I get the spinning color wheel that never stops. I can not do anything with it. I made sure I had the latest updates to the software. Still nothing. I reset my PRAM and Power manager. No Luck. I reinstalled the application. No luck. I manually removed everything emote desktop related and then reinstalled and still no luck. Anyone have any solution advice.

    I am also having the same issue on 2 machines. A MacBook Pro and a MacPro. When I look in the console, this is what I see :
    Dec 10 10:57:35 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: error connecting 61 Connection refused
    Dec 10 10:57:35 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: unable to connect to agent - try again
    Dec 10 10:57:36 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: AgentListenerThread messageSize bad 3892510720 67108864
    Dec 10 10:57:36 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: AgentListenerThread messageSize bad 134217728 3892510720
    Dec 10 10:57:36 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: AgentListenerThread messageSize bad 67108864 134217728
    Dec 10 10:57:36 Hercule /Applications/Remote Desktop.app/Contents/MacOS/Remote Desktop: AgentListenerThread messageSize bad 3892510720 67108864
    I have tried to do a clean install of the app in the MacPro, but I still get the same message. Lovely.
    Mack

  • Hotsync two different Palms that use a different version of Palm Desktop

    What I need to know is I have a Palm IIIe & a Palm Zire 31 both of which use a different version of Palm Destop can a install both versions of Palm Desktop on a single computer and then be able to hotsync both devices. Or will both of them hotsync with the same version of Palm Desktop.
    Palm Desktop 4.1.4e for the Palm Zire 31
    Palm Desktop 4.1.4 for the Palm IIIe
    Post relates to: Zire 31
    This question was solved.
    View Solution.

    Hello obsolete.
     I haven't tried your specific combination of devices before, but I think it should work.  I would install Palm Desktop 4.1.4 and then sync the Palm IIIe first.  Once you know that the Palm IIIe is syncing normally, I would then install Palm Desktop 4.1.4e on top of 4.1.4, upgrading it.  Then sync the Palm IIIe to make sure it is still working.  If it is, then attempt to sync your Zire 31.
    Since you will be syncing two devices to the same computer, I recommend that each device have it's own unique HotSync ID to prevent things from going bad on you.
    Alan G

  • About Remote Desktop Admin 3.8

    why all time i need to make the actualization of this? i all ready do 8 times and continue with the same problem

    This is a recurring issue. Others have already posted problem like yours. Apple might solve this in the next update.

  • Windows server 2012 and windows xp remote desktop connection loss

    I am having this problem for a month now, and i am stumped with trying to find an answer . I have talked with several network admins in my area and with no luck i have not found a solution. I have a windows server 2012 placed with 5 pcs that are connected
    on a local network , those 5 pc's connect to the server via remote desktop. List of pc's:
    1x Windows 7
    4x Windows XP SP3
    All have the latests network drivers, all have the latest version of remote desktop installed. All have been scanned for viruses. All have antivirus software.
    Problem is the 4 XP machines lose connection on when connected via remote desktop. If one starts losing connection the other 3 start to lose the connection aswell. The windows 7 machine is not affected by this it works fine.
    What have I tried:
    Scanning for viruses.
    Disabling Firewall and antivirus software.
    Updating all drivers.
    Did many changes to group policy like keepalives etc.
    Turning off SMBv2 SMBv3.
    Turning off network adapter Offload settings.
    Changed some registry settings like keepalive, smb etc.
    Updating every pc and server with all windows updates.
    Changed the router and switch.
    Port forwarded needed ports like 3389.
    Updating remote desktop to 7.0.
    I might be forgetting some stuff i will add as i remember anything.
    So the thing is this. I use a Windows XP machine from my office I remotely connect to the server via the Internet and I DO NOT experience any connection loss. BUT the XP machines on the local network constantly experience connection loss via remote desktop.
    I pinged every Machine from the server via CMD command PING. So when they lose connection the Packets get time outs . Packets get dropped between 1-10 packets when a connection is lost. This packet drop does not occur when using the internet or anything else.
    ONLY when connected to the server via remote desktop. The packets get dropped at random intervals.
    Problem is I use an XP machine and I am not experiencing any loss of connection , while the XP machines on the local network experience it , but not the windows 7 machine.
    Router is ASUS RT-N53 , and switch is Dlink DES-1008D. Server is a Dell PowerEdge T110 II.
    Can someone please tell me what can i do to solve this problem?

    So today got some word from their office. They were using RDP from 8AM until 12PM all was working fine. Then got back after lunch about 1PM and got a few connection lost errors when they tried using RDP again. Its weird since they didn't have disconnects
    in the morning, and started having them after lunch.
    Also noticed, that two pc were not using RDP and were disconnected as shown in task manager. And they still got request timeouts.
    Maybe this is not a remote desktop issue?
    TASK MANAGER
    The 2 disconnected pc's ping screens:

  • Cannot get Remote Desktop to work on Windows 7

    Ok. I am having issues trying to connect remotely using RDP. From what I know, the network was pre-configured from another IT group and was able to get it up and running. My company was commissioned to migrate his old PC (WINXP) to Windows 7. I have gone
    through the steps of allowing remote desktop and following instructions:
    To configure remote access, follow these steps:
    1. In Control Panel, click System And Security, and then click System.
    2. On the System page, click Remote Settings in the left pane. This opens the System Properties dialog box to the Remote tab.
    3. To disable Remote Desktop, select Don’t Allow Connections To This Com¬puter, and then click OK.Skip the remaining steps.
    4. To enable Remote Desktop, you have two options. You can:
    Select Allow Connections From Computers Running Any Version Of Remote Desktop to allow connections from any version of Windows.
    Select Allow Connections Only From Computers Running Remote Desktop With Network Level Authentication to allow connections only from Windows 7 or later computers (and computers with secure network authentication).
    5. Click Select Users. This displays the Remote Desktop Users dialog box.
    6. To grant Remote Desktop access to a user, click Add. This opens the Select Users dialog box. In the Select Users dialog box, click Locations to select the computer or domain in which the users you want to work with are located. Type the
    name of a user you want to work with in the Enter The Object Names To Select field, and then click Check Names. If matches are found, select the account you want to use and then click OK. If no matches are found, update the name you entered and try searching
    again. Repeat this step as necessary, and then click OK.
    7. To revoke remote access permissions for a user account, select the account and then click Remove.
    8. Click OK twice when you have finished.
    One thing that I found odd when he launched Remote Desktop from his home laptop is the IP entry:
    Computer> [Public Router IP]:49250
    Login> Domain\Admin
    Password> *****
    From the odd port number I would assume that was for port forwarding so I logged into his router and found exactly that. In port forwarding, he had the in/out as 49250 TCP to 192.168.30. I went into the firewall and enabled Remote Desktop in the inbound
    rules. 
    As of right now, I can use Remote Desktop to remote into the server, and withing their server, I cam use Remote Desktop to remote into the workstation. I just can't remote into the workstation directly using the port 49250. Any suggestions on this, something
    I have missing?
    He has Norton Security installed on this computer and I tried adding Inbound/Outbound rules to its 'Smart Firewall' to allow remote desktop and the port.

    Thanks for the reply.
    When I use Remote Desktop and use the Public IP of the router without the port number (49250), I am able to get into the server. However, when I try to use RDP with the [Public IP]:49250, it will not connect to the 192.168.0.30 workstation.
    Right now the router is program to forward port 49250 requests to the 0.30 workstation.
    I am going to work on the Inbound/Outbound Firewall settings today and see if this will resolve the issue.

Maybe you are looking for