Pcanywhere Mac Client Version 12

I am new to mac, switched from windows. Have had no problem so far but need to connect to work machines via pcanywhere. Tried to install following PCA instructions but installer starts and I get error unable to create directory /usr/local/lib. I tried using the unix commands that pca instructions said to use from the command propmt but still get same error.
Love the switch so far but need to get over this hurdle. I know I can use the PCA Web remote which works but would like to get the mac client version working. Any help is appreciated.
TIA

OK.
Now, before we start calling names.
1) The Installer that you're using is probably a program developed by "PC Anywhere". Thus the suggestion to contact the software publisher, or at least look at their website for FAQ's.
2) As far as "can't create the directory", this sounds like an error message that you're getting while using the PCA installer. See point 1.
That folder is a standard directory on Linux systems (and generic UNIX, I think).
It is not a standard directory on OSX.
You may be trying to run this installer as a non-admin account, thus not being able to create a directory in that system directory.
3) in Terminal:
mkdir /usr/local/lib
Good Luck.
Now....no more name calling, OK?

Similar Messages

How to Get Outlook Client Version for MAC from Exchange 2010

Hi,
I want to know how many users in my organization are using Outlook for MAC or Email for MAC. What is the best way to extract this information from Exchange 2010 server. I can read the RPC Client Access logs by running logparser:
logparser.exe "SELECT distinct extract_suffix(client-name,0,'=') as User,client-software,client-software-version as Versio
n,client-mode,client-ip,protocol from 'D:\RPC\EXTC03\RCA_2014*.log' WHERE (operation='Connect') GROUP BY User,client-software,Version,client-mode,client-ip,protocol ORDER BY User" -nSkipLines:4 -i:CSV -rtp:-1 > D:\RPC\EXTC03\EXT
C03.TXT
How to extract Outlook for MAC clients from this command?
Hasan

Hi Hasan,
As far as I know, Outlook for Mac (Office 2011) uses Microsoft's EWS (Exchange Web Service). So you probably need to collect and focus on EWS logs, not RCA.
Anyway, Karl is right that you'd better post your question in our Exchange forum, where you can get more experienced responses:
https://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserver
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Windows 2012 R2 ADRMS domain controller version and Non-domain-joined Mac Client with outlook 2011

Hi,
What is the AD version for Windows 2012R2 ADRMS? Is it possible to have Windows 2003 R2 DC with Windows 2012R2 ADRMS?
Any installation guide Non-domain-joined Mac Client with outlook 2011?
What is the SQL version for Windows 2012R2 ADRMS?
Please advise. Thanks.
Kelvin Teang

Hi Kelvin -
There is no RMS Client for Macs. That functionality is actually provided through the Office for Mac application (this is different compared to the PC). Domain-joined clients will autodiscover the RMS server and should be able to create and consume
protected content. Non-domain-joined clients cannot automatically discover their RMS server. In this scenario, prepare a protected document or email from a domain-joined machine and send it to your non-domain-joined users. They will open
the document or email up and the URLs contained in the publishing license of the document will direct them to the correct RMS server.
I hope that helps!
Micah LaNasa
Synergy Advisors
synergyadvisors.biz

My outgoing mail is not working after the upgrade OS to mavericks. my mail client version is 7.1 . please help me resolve this issue

My outgoing mail is not working after the upgrade OS to the mavericks. my mail client version is 7.1 . please help me out resolve this issue

Please let me know , How we can reinstall apple mail ? .
1 . We updated OS to mavericks few machine in last december and still does't works SMTP (Out going mail) on those MAC.
2. After that most recently we updated OS to mavericks few machine those are working will with SMTP server .
a)Not showing any SMTP connection in TCP trace ,
b) Connection docter every time Says "Connecting to the server "
3, Then we have installed thunderberd (another mail) client on maverick os, which OS related to apple mail client not woking . It seems other mail client is working well with SMTP server .
Please help me .
Thanks,
Ranesh..

Certificate error when using connection broker on Mac client

We're using RD Connection Broker using IP address redirection for a couple of years now. Previously Mac client were using iTap RDP without any problems. Clients are connecting using a RD Gateway server.
When trying to connect using the latest Microsoft remote desktop client (version 8.0.24255) a certificate warning is shown saying the IP-address doesn't match the name in the certificate. The client shoudn't match the IP address with the certificate but
should match the farm name. The error occurs when the connection broker redirects the client to a server.
Any help is appreciated
<style type="text/css">p, li { Version 8.0.24255</style>

Hi MatthijsO,
Have you updated it to 8.0.3? Does the issue persist?
Thanks.
Jeremy Wu
TechNet Community Support

802.1x error 23 only on Mac clients

I have been using server 2008 R2 for NPS using 802.1x for about a year or so with my windows clients and it has been working perfectly. Recently however my mac clients cannot authenticate successfully. They get the error posted below. I
cant find the eap log file or at least I dont know what the name of it is. All my Windows clients still work fine, just the couple mac clients cant authenticate even though they have been working fine up until very recently.
Network Policy Server denied access to a user.
Contact the Network Policy Server administrator for more information.
User:
Security ID:
DOMAIN\username
Account Name:
username
Account Domain:
DOMAIN
Fully Qualified Account Name:
DOMAIN\username
Client Machine:
Security ID:
NULL SID
Account Name:
Fully Qualified Account Name:
OS-Version:
Called Station Identifier:
000B866D50A0
Calling Station Identifier:
F0B47923378A
NAS:
NAS IPv4 Address:
172.20.XX.XX
NAS IPv6 Address:
NAS Identifier:
172.20.XX.XX
NAS Port-Type:
Wireless - IEEE 802.11
NAS Port:
7
RADIUS Client:
Client Friendly Name:
Aruba-Master
Client IP Address:
172.20.XX.XX
Authentication Details:
Connection Request Policy Name:
Secure Wireless Connections
Network Policy Name:
Secure Wireless Connections
Authentication Provider:
Windows
Authentication Server:
RADIUS.domain.lan
Authentication Type:
PEAP
EAP Type:
Account Session Identifier:
Logging Results:
Accounting information was written to the local log file.
Reason Code:
23
Reason:
An error occurred during the Network Policy Server use of the Extensible Authentication Protocol (EAP). Check EAP log files for EAP errors.

I don't have a MAC client to test, so it is difficult to answer.
I can tell you that reason code 23 usually occurs when the settings on the client do not match those on the server - one side is set for EAP/TLS and the other is set for PEAP/MSCHAP, for example.
It's also possible that the MAC is doing some kind of server certificate authentication check as part of standard PEAP authentication and this is failing because the required trusted root certificates are expired, or not present. If you can look
at the properties of the certificate store on the MAC it might help.
On a Windows client, and probably on a MAC also a requirement is that the certificate on the RADIUS server be chained to a trusted root certificate on the client. If the client doesn't have this root certificate it will give a generic error like the one
you are seeing. To fix it, you just need to request a certificate on the client.
-Greg

Mac OS Version not reported correctly in ARD

Using ARD admin 3.7.2 the screen displays Mac OS Version as 10.9.2 but on the computer "About this Mac" clearly shows OSX 10.9.3.
Other computers that are running 10.9.3 show correctly. I have re-scanned but no change. Deleted computer from "All Computers" and re-scanned, no change.
Why are certain computers not reporting their current Mac OS Version correctly?

I discovered that if I did the "Upgrade Client Software", the Mac OS Version shows correctly now. The client software was already 3.7.1 but apparently re-installing it fixed the problem.

Problem viewing attachments in Mac client

Hello!
I am currently having a problem with Oracle Calendar on the Mac. I have version 10.1.2.3.0.714 desktop client, and am connecting to a CorporateTime version 5.4 server. When a meeting is created, if there is an attachment to the meeting, I cannot view the attachment. It happens on all meetings, single or recurring. This happens if I set up the attachment on a Windows or Mac client. Windows versions of Oracle Calendar/CorporateTime can see the attachments just fine, even if they are attached from a Mac client. This is happening on multiple machines, and to multiple accounts. Thoughts? My instinct tells me it's because the server is a bit out of date - the upgrade is coming soon - but I'd still like confirmation if that is the case.

When first created my rootCA I did it via Keychain Access and its Certificate Assistant, the second time around I used XCA which is a free GUI front-end to openssl.
See http://sourceforge.net/projects/xca/
I had previously looked at SimpleAuthority another similar tool but XCA was brought to my attention by a contact at Apple.
I am not sure if just changing what I used initially from Certificate Assistant was the fix or the choices I made.
I have set up templates for creating a CA, for creating a VPN server certificate, an ordinary SSL server certificate, a user certificate and also a code-signing certificate.
In terms of flags, I used the following document as a guide as what to include and indeed an interim test setup using certificates created using the StrongSwan tool also worked for Racoon and Mac and iPhone clients.
See http://wiki.strongswan.org/projects/strongswan/wiki/IOS_%28Apple%29#Certificate- requirements-for-iOS-interoperability
I used those requirements as a guide when setting up the templates in XCA.
It is possible with Apple's Certificate Assistant to add SAN records but not CRL records, even with openssl doing either is normally very painful, XCA by comparison makes this extremely easy thanks to its templates.

Incomplete "authentication level" property support on iOS/Mac clients

When “authentication level:i:0" property is present in RDP file, client shouldn't show warnings regarding RDP server identity. Such warnings could appear when untrusted certificate is used on RDP server or when "RDP Security Layer" is used/configured
on the server. With “authentication level:i:0" iOS/Mac clients omit warning only for the first case (untrusted certificate), but still show warning for the second case (RDP Security Layer). Windows client behaves as expected in both cases - no warnings
are shown.
How to reproduce:
1. Configure RDSH server to use “RDP Security Layer” in properties of “RDP-Tcp” connection in Remote Desktop Session Host configuration utility (on Windows 2008).
2. Create an RDP file for this server with “authentication level:i:0” property (it corresponds to "Advanced\Server authentication\Connect and don’t warn me" option in Windows RDP client).
3. Try such RDP file on Mac and there always be “Untrusted Connection” warning (regardless of “authentication level” property). Expected behavior is no warnings.

Hi,
Which version of MRD MAC you are using?
Please try to update the MRD MAC version to 8.0.15 and verify result.
https://itunes.apple.com/in/app/microsoft-remote-desktop/id715768417?mt=12
Please verify the RDP security level setting in the remote PC options is set to Client Compatible. Apart if you can find any error message\log then it is helpful for further process.
Microsoft Remote Desktop>About Microsoft Remote Desktop>Send log via email
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Licensing-Can I use 10 client version for Web server?

I have a client that is looking to move their web servers from IIS and Windows to OSX server.
My question is, how does the licensing shceme work? Can we use a 10 user version of OSX Server for a web server, or do we need the Unlimited version?
Not 100% familiar with the server side of Mac things, so treat me gently

Hi
The licensing only applies to connected AFP users, so you can use a 10 Client version without any problems.

Outlook 2011 SP2 Mac Clients - Mail could not bve received at this time...

After Upgrading to Office SP2 for the Mac, our Mac Clients can no longer Connect to the Exchange server
Server: Version 14.1 (Build 218.15) / 0.1 (8.0.535.0)
Client:14.2.2 (1202421)
The Error we get just after launch is:
Mail could not be received at this time. The server for account "" returned the error "Logon failure: unknown user name or bad password." Your username/password or security setting may be incorrect. Would like to try re-entering your password?
When this happens and you click yes, to try to enter your password again, your account typically gets locked out on the AD Domain after a few attempts.
We have tried the keychain workaround/solution to no avail, we have rebuilt Profiles, Cleaned and Compressed the Identity Database, etc... No Love
I can login to the https://mail.domain.com//EWS/Exchange.asmx url and it comes back with the WSDL file.
The only thing I have found that Might be a possible solution was this:
http://www.exchangeranger.com/2011/03/mac-outlook-2011-clients-getting-bad.html
Basically says to: Removed the EWS VirtualDirectory and recreated the EWS VirtualDirectory
Okay that's fine and all if None of our EWS services were working, though we have several other systems (non Mac) that are talking to the Exchange server via EWS (Web, Custom VB Apps, SQL SSIS, Azure Compute Service and many more) So I really don't want to
Blow away the EWS if everything else is working fine.

Here are the log entries from the IIS web:
I'm guessing these first three entries are from iCal, that is working fine.
2012-09-17 03:50:23 10.1.1.15 POST /EWS/Exchange.asmx - 443 - 10.11.3.9 Mac+OS+X/10.8.1+(12B19)+CalendarAgent/47 401 0 0 15
2012-09-17 03:50:23 10.1.1.15 POST /EWS/Exchange.asmx - 443 - 10.11.3.9 Mac+OS+X/10.8.1+(12B19)+CalendarAgent/47 401 0 0 30
2012-09-17 03:50:23 10.1.1.15 POST /EWS/Exchange.asmx - 443 - 10.11.3.9 Mac+OS+X/10.8.1+(12B19)+CalendarAgent/47 401 0 0 15
This is where I started Outlook:
2012-09-17 03:51:57 10.1.1.16 POST /autodiscover/autodiscover.xml - 443 - 10.11.3.9 MacOutlook/14.2.3.120616+(Intel+Mac+OS+X+10.8.1) 401 0 0 264
2012-09-17 03:51:57 10.1.1.16 POST /autodiscover/autodiscover.xml - 443 - 10.11.3.9 MacOutlook/14.2.3.120616+(Intel+Mac+OS+X+10.8.1) 401 1 2148074254 46
2012-09-17 03:51:58 10.1.1.16 POST /autodiscover/autodiscover.xml - 443 DOMAIN\Username 10.11.3.9 MacOutlook/14.2.3.120616+(Intel+Mac+OS+X+10.8.1) 200 0 0 1025
2012-09-17 03:51:58 10.1.1.16 POST /EWS/Exchange.asmx - 443 - 10.11.3.9 MacOutlook/14.2.3.120616+(Intel+Mac+OS+X+10.8.1) 401 0 0 46
2012-09-17 03:51:58 10.1.1.16 POST /EWS/Exchange.asmx - 443 - 10.11.3.9 MacOutlook/14.2.3.120616+(Intel+Mac+OS+X+10.8.1) 401 0 0 46
2012-09-17 03:51:58 10.1.1.16 POST /EWS/Exchange.asmx - 443 - 10.11.3.9 MacOutlook/14.2.3.120616+(Intel+Mac+OS+X+10.8.1) 401 1 2148074252 77
2012-09-17 03:51:58 10.1.1.16 POST /EWS/Exchange.asmx - 443 DOMAIN\Username 10.11.3.9 MacOutlook/14.2.3.120616+(Intel+Mac+OS+X+10.8.1) 200 0 0 186
2012-09-17 03:51:58 10.1.1.16 POST /EWS/Exchange.asmx - 443 - 10.11.3.9 MacOutlook/14.2.3.120616+(Intel+Mac+OS+X+10.8.1) 401 0 0 15
2012-09-17 03:51:58 10.1.1.16 POST /EWS/Exchange.asmx - 443 - 10.11.3.9 MacOutlook/14.2.3.120616+(Intel+Mac+OS+X+10.8.1) 401 1 2148074252 46
2012-09-17 03:51:58 10.1.1.16 POST /EWS/Exchange.asmx - 443 - 10.11.3.9 MacOutlook/14.2.3.120616+(Intel+Mac+OS+X+10.8.1) 401 1 2148074257 31
Connecting to: https://mail.domain.com/autodiscover/autodiscover.xml
comes back with a Username and Password Prompt, and then displays:
<errorcode style="font-family:Times;font-size:medium;line-height:normal;">600</errorcode> <message style="font-family:Times;font-size:medium;line-height:normal;">Invalid
Request</message>
Connecting to: https://mail.domain.com/EWS/Exchange.asmx
Redirects me to the following URL: https://mail.domain.com/EWS/Services.wsdl
What else do you need?

Any issues with file sharing between Windows and latest Mac client?

We're running Lync 2013. My Windows client is 15.0.4551.1005. Mac client is version 14.0.8.
I open a conversation with a coworker on his Mac. I then try to share a png file. He clicks accept but then my client says the attempt timed out, and his client says that I canceled the file transfer. The coworker then boots the Mac into Windows and we try
again, and the file share works fine. When I jump on my Mac, I can send files to his Mac without issue. When he tries to send from his Mac to my PC it fails, but when he tries to send from Windows on his Mac to my PC, it works.
I can't find anything specific in the logs that would indicate a firewall issue. Is there a bug with file sharing between the Mac and PC clients?
Thanks,
Matt

No, There isn't a bug with file sharing between Mac and Pc client.
2941640 Desktop sharing session stops in Lync 2013 when all screen data is updated
Also you can check below links
http://support.microsoft.com/kb/2952672/en-us
http://support.microsoft.com/kb/2880474/en-gb
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Updating OpenSSL on Mac System version 10.6.8?

Does anyone have successfully updated OpenSSL on Snow Leopard thru the Terminal could post the steps here?
The actual version of open SSL is OpenSSL 1.0.0e 6 Sep 2011
I am attempting to update to the openssl-1.0.1c
I was trying to do the installation on the terminal by
1. CD to the openssl-1.0.1c directory
[rootuser:/install/openssl-1.0.1c] root# /install/openssl-1.0.1c/config
After giving the System information, I have this and now I am in doubt if I should build 64-bit library or just continue with the darwin-i386-cc.
WARNING! If you wish to build 64-bit library, then you have to
invoke './Configure darwin64-x86_64-cc' *manually*.
You have about 5 seconds to press Ctrl-C to abort.
Configuring for darwin-i386-cc
Anyone that had done this before and gone to the same issue, could shine a light here. Many Thanks!
Message was edited by: Eduardo B1

No I did not mess up with any of the original paths. Actually this is my main motto. Everything I am configuring, I am making sure it works in harmony with the apple internal standards. I transformed two mac client in Servers and took me a lots of reading and comparing notes plus hands on tests to make everything work fine and in harmony with web sharing and etc. I am serving 3 domains without any issues. In addition, I am testing php and Mysql but I still have a lot of reading and learning until I get to launch it into production. I could use the terminal alone to manage Bind, Apache, PHP and Mysql but webmin on SSL does such a great job that I decided to use a combination of these two. Right now I just finished configuring my Lion Client Server and everything is working just fine. I just have to research and learn a little more about the new way apple is setting up the httpd conf so I can run it accordng to the new rules. Thanks for the link, I will check it out for sure.
Thanks for the head up;
Eduardo

Mac Client Problems

Our Mac Clients can access the Core Financials on 11i with no problems.
When they attempt to connect to iProcurement or iExpense, however, they go into a sign-in loop, acting like the passwords have expired.
We appear to have all the correct versions of OS's, Runtime for Java, etc.
Does anyone have success doing this out there ?

We have Mac users that have been using the Self-service applications (iProcurement, Internet Expense, and Self-Service Human Resources) since July of last year. We currently running version 11.5.3 of the application and 8.1.6 for the database.
If you have more specific questions let me know.
Thanks,
Kelly

Forms 10g on Mac client hangs

Hi again,
I have a few Forms 10g applications running on a Solaris network, running version 10g of the database. These apps are running okay with Windows xp clients, but as soon as we try and have a Mac client access them they hang. Looking in the Java control panel, they seem to hang when the Forms Applet is started (Normally on Windows machine the servlet loads and the the images jar file is processed).
Can anyone offer some suggestions on what to look for?
Thank you,
Tony Miller
Webster, TX

JRE is 1.6.19. Solution that has been provided is:
Under Safari must first go to Develop and then User Agents and then select IE 7 before trying Application. User MUST do this EACH Time they try and run application, since it is NOT stored in browser for long term.
I am talking with the customer to see if we can just migrate the applications to a more palatable development product...
Thank you,
Tony Miller
Webster, TX

Pcanywhere Mac Client Version 12

Similar Messages

Maybe you are looking for