Mac Client?

Any suggestions on a client for Mac users? Recently upgraded from an Exchange 5.5 environment where Mac users were using Outlook for Mac 2001 which doesn't seem to support an IMAP client. Testing Outlook Express for Mac which does allow connection to an IMAP server with marginal results. Need to support both 9x and OSX.
Using the web portal is another option, but users are not happy about that. Was thinking of taking Eudora for Mac for a test drive setting it up as an IMAP client. Would appreciate any comments.

Gotthard,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://www.novell.com/support and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Forums Team
http://forums.novell.com

Similar Messages

Mac Client Login Window Takes Long Time "Other"

Mac 10.6.x client is successfully joined to the Windows Server 2008 based domain. But it’s taking too much time (approx. 5 to 7 minutes) to shows the “Other” option (using that, log on by AD user) in login window on Mac client.
Has anyone idea, why is it taking that long time.

Are you connected wirelessly or wired?
Which Mac are you using?

Mac Client Certificate not found

Hey all, i'm trying to install the ConfigMgr client on a mac system. The site is 2012 SP1 RTM however since there is no release yet of the mac client i'm using the mac client install from the SP1 beta install folder (Suggested by Microsoft)
I followed the instructions on how to install clients on mac computer from technet. Everything from the install and the enrollment seems to complete fine no errors. After the enrollment when I open System Preferences > Configuration Manager it says "Certificate
not found" If i check the ccmclient log file on the mac it shows the following errors
Failed to Parse MgmtAuthority ServerList
Failed to get server list
Failed to GetProperty Mode from Configuration Provider : 80070490
Requested certificates not available in store
Certificate not found in store. Bailing out!
Failed to validate certificate
The certificate shows up under system in the keychain, the only strange thing is it shows for name the user who enrolled in the certificate. I figured it should have showed the system name. The root ca is also there. Any help would be appreciated, thanks

Okay so figured this out, and i'll post in case this happens to someone else. The certificate will always show under the keychain with a name of whoever the user was that did the enrollment. So if you used Joe Smith, then the certificate will be called
Joe Smith. In my case the account I used to enroll had a active directory display name of two words such as "Joe Smith" Because of this space in between, configuration manager client kept listing the certificate as "Joe". I was then realized that indeed just
like the error said the certificate could not be found because its looking for Joe and the the certificate says Joe Smith. The fix was instead do the enrollment with a normal account with no spacing in the name. This may be a bug or Microsoft may not recommend
creating AD accounts with display names with spaces.

Set Static IP address on Mac clients

Hi,
I'm trying to change the IP address on a mac client at startup time to a different value and to be Static type. I need to do it via the command line. I've researched and found out that 'networksetup -setmanual ...' and 'ipconfig set en0 MANUAL ...' would do it, but the 'networksetup' command is not available unless I have ARD installed and 'ipconfig' is not recommended for use other than testing and debug.
Another option I was looking at is editing /Library/Preferences/SystemConfiguration/preferences.plist and then doing 'changeip ...' command.
Do you know if there are any other commands that will allow me to change an ip address via the command line, set it to Static/Manual and preferably do it without a reboot?
Thank you

Hi Sergey,
when I use static IP in my jwc_properties.ini it is never picked up, it still uses DHCP. The part where I have configured IP looks like this:
# Whether static configuration or DHCP server is used do get IP address. Possible values: dhcp,static
ip.method = static
# IP address,used with static IP configuration only
ip.addr = 10.143.144.97
# Network mask,used with static IP configuration only
ip.netmask = 255.255.252.0
# Network gateway,used with static IP configuration only
ip.gateway = 10.143.144.1
# DNS server,used with static IP configuration only
ip.dns =
# MAC address
mac.addr =

Connect mac client to mac printer share across subnets

I need to share printers from a Mac. I need to connect
Mac clients on different subnets to the Mac shared printers. I installed
a Mac mini, connected to printers via HP JetDirect Socket (port 9100), and
shared them. I was able to print from the Mac mini, and connect Mac
clients on the same subnet to the shared printers with Bonjour and print.
I moved the Mac mini to its intended location on another subnet. I
immediately learned that Bonjour does not publish services across
subnets. I could not find documentation on how to connect to a Mac shared
printer across subnets, but I did find some third party documentation (only some incomplete
documentation from Apple) on how to implement DNS-SD Service Discovery. I
enabled DNS-SD and was able to publish the printer shares across subnets, but I
was still unable to connect to the printer shares from a Mac client. I
found some third party documentation (none from Apple) on how to manually connect to a Mac
printer share by specifying the IP address of the server, specifying the CUPS
default IPP protocol, and the print queue name. I was unable to connect
to the shared printers. I receive ping replies from my Mac mini, and port
scan reveals that port 631 for IPP, CUPS default, is open. Printer
sharing is configured so everyone can print. I am able to connect to the Mac
mini with VNC Screen Sharing. I don’t see how this can be a network
issue.
Macs don’t seem to like to connect to our Windows
shared printers because of our PaperCut software, and connecting Mac clients to
Windows printer shares and authentication is beyond the average user,
exacerbated by Macs not behaving the same as Windows when bound to an Active
Directory domain.
I called Apple support, they escalated to Apple Enterprise
support. Apple Enterprise support said they couldn’t help me beyond a
single network with no subnets, but Apple Engineering might be able to solve
the problem for $695.
Why do I need to pay $695 to learn how to connect Mac
clients to Mac shared printers, something that should be easy and intuitive and
have documentation readily available? Windows printer sharing is easy and
intuitive and documentation is readily available, and services are published
across subnets without have to implement DNS-SD.

Thank you for your reply. I followed the instructions in the sybaspot.com site and in some of the included references to set up DNS-SD. DNS-SD worked, but I couldn't connect the Mac client to the Mac shared printers.
I also found http://www.papercut.com/products/ng/manual/ch-mac-printing-10-8-9.html#ch-mac-pr inting-10-8-9-sharing-printers.
I expanded my search and found this: http://support.apple.com/kb/PH13940, last modified May 8, 2014. I started work on my project February 2014. Apple Support could have told me about this document.
PH13940 says: "The computers must be on the same local network as your Mac". Apple must not consider multiple subnets one network.
PH13940 says: "Printer sharing is for printers attached directly to your Mac. You don’t need to share network printers, because they are already shared on the network."
Apple must define "network printers" as any printer with a network interface. Microsoft defines network printers as printers shared by another computer. TCP/IP ports are local ports on a Windows computer, so TCP/IP connected printers are local printers that can be shared. Multiple users on a Mac all see the same connected printers. Multiple users on Windows all see the same local printers, but network printer connections can be different for each user.
Apple must not see any value in accounting for printing and assigning the cost to the user or department. We need to account for printing and cannot have any users bypassing the system by printing directly to printers. I have created Access Control lists on the printers to limit connections to the specific IP addresses of our print servers.
The documents about setting up DNS-SD and IPP connections must have assumed USB connected printers on a Mac. The odd thing is that I was able to share a network printer from the Mac mini when the client Mac was on the same subnet. Is PH13940 wrong?
I am Microsoft Certified Systems Engineer 1999 and Apple Certified Technical Coordinator 2013.

Mac client not showing up in Windows DNS

Hi,
I've got a Windows Server 2003 Active Directory network with DNS, DHCP, etc. all running. I have a Mac OS X Panther client I want to be added to my DNS servers automatically. I can successfully bind the mac to AD, and login to AD just fine. The client gets an address from DHCP, but it never shows up in DNS. I have added the DNS servers and domain in the TCP/IP settings, and double-checked all of the network settings. The mac client and windows servers all have the latest patches and updates.
Any ideas?
Thanks,
Mike

Have you tried removing that client from the computer list and re-adding it? If it won't show up, even via the IP, and of course presuming that you've checked any firewalls or routers to make sure nothing's change that could block ARD from reaching that system, you may need to remove the client and reinstall. Instructions for removing the client can be found here.
Hope this helps.
Message was edited by: Dave Sawyer

Mac Client Enrollment Not Working

I'm trying to enroll a MAC OSX 10.9.2 client. My environment is Server 2012 R2 and Configuration Manager 2012 R2. I get the following error when running the CMEnroll command:
SSL Connection failed. HTTP Response code is 500 and reason is Internal Server Error
Server returned: CertificateRequest Error
These are the errors from the EnrollmentService.log
[3, PID:3596][03/07/2014 12:23:52] :CALayer: Sending CA failure status - ENROLLSRVMSG_CA_FAILURE
[3, PID:3596][03/07/2014 12:23:52] :CALayer: SubmitRequest CA: cauthority.ctl.intranet\CTL Prod Issuing CA Errormessage: Denied by Policy Module 2 ErrorCode: 2
[3, PID:3596][03/07/2014 12:23:52] :Only one CA is specified in profile. Failed to enroll with the specified CA: cauthority.ctl.intranet\CTL Prod Issuing CA
[3, PID:3596][03/07/2014 12:23:52] :EnrollmentRequestController: Enrollment exception Error Code:FailedToIssueCert Message: Submitting cert request and issuing cert failed
[3, PID:3596][03/07/2014 12:23:52] :Microsoft.ConfigurationManagement.Enrollment.EnrollmentServerException: Submitting cert request and issuing cert failed
[3, PID:3596][03/07/2014 12:23:52] :FaultCode is: CertificateRequest and reason is: Failed certificate operations FailedToIssueCert
Does anyone know what's going on?

Hi,
The failed requests on the CA might give you some useful information. And here is a similar thread with yours:
http://social.technet.microsoft.com/Forums/en-US/142fc77d-4eed-4f3a-a57c-dcacf8cbbf63/sccm-2012-sp1-mac-client-enroll-problem?forum=configmanagergeneral
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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 Client Log on Window Takes Long Time

Mac 10.6.x client is successfully joined the Windows Server 2008 based domain. But it’s taking too much time (approx. 5 to 10 minutes) to shows the “Others” option (using that log on by AD user) in login window on Mac client. Has anyone idea why it’s taking that long time.

Are you connected wirelessly or wired?
Which Mac are you using?

When i integrate Mac client to the domain open directory, he don't ask me account DirAdmin, Why ?

When i integrate Mac client to the domain open directory, he don't ask me account DirAdmin, Why ?
I don't want all people can integrate mac client to the open directoy without authentification
I want he ask me account diradmin for integrate client mac os x to the domain open directory of Lion Server
I have made a magic triangle
Thanks

Malik-O wrote:
When i integrate Mac client to the domain open directory, he don't ask me account DirAdmin, Why ?
I don't want all people can integrate mac client to the open directoy without authentification
1 ) I want he ask me account diradmin for integrate client mac os x to the domain open directory of Lion Server
Authentication (with open directory admin username & password) is off by default. In Mountain Lion there is no longer a GUI to manage that and some of the other binding options. In Lion, I think you could use Server Admin (or was it Workgroup Manager) -- I can't remember, but there were little checkboxes.
To make authentication mandatory in Mountain Lion, you can use this on the Server:
sudo slapconfig -setmacosxodpolicy -binding required
Use the following to check the binding policies:
slapconfig -getmacosxodpolicy
You might want to check the slapconfig man page, you'll find some of the other options that were in Server Admin in Lion, e.g. disable cleartext, block man-in-middle, etc.
Edit, I just saw you're still using Lion Server, not Mountain Lion. I'm pretty sure the above commands will work on Lion Server as well.

"Use all monitors" option missing in 8.0 Mac Client

I'm using Mac Client 8.0.24091 with a mini display to VGA adapter and I don't see an option for 'Use
all monitors' when I create connections to my work desktop with dual monitors. Can someone help me? Does the mini to VGA not support it?

Hi,
The Remote Desktop Client 8.0.3 for Mac has been released, please install it and see how it works.
8.0.3
https://itunes.apple.com/us/app/microsoft-remote-desktop/id715768417
This is the update note which we show the users in the app store:
•Choose between custom or OS X native full screen mode
•Crash on quit, fixed
•A number of bug fixes
Thanks.
Jeremy Wu
TechNet Community Support

Mac client bc addresses visible to recipients

We're using the Mac client, v8.0.2HP4, and attempting to send messages where the bc field contains a group with internal and external addresses as well as nested groups of external addresses. The message is sent, but here are the problems we're seeing:
1. Internal recipients to whom the message is bc'd can click the "Properties" tab and see listed all the bc addressees.
2. External recipients to whom the message is bc'd see the entire collection of bc'd addressees in the to: field if their received message.
The same message and addressee setup works correctly when sent from the Windows GW 8.0.3 (build 108711) client.
Anyone seen anything like this?

janthenat wrote:
> We've confirmed that the same problem occurs using a separate known clean GW
> install. It does, in fact, appear to be the client but hoping to find a way
> to work around it.
Unfortunately, I don't know of any way to work around this.
Danita
Novell Knowledge Partner
Are you a GroupWise Power Administrator? Join our site.
http://www.caledonia.net/register
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

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.

Deployment error on Mac Client - Office 2011 SP1 would not install

Hi,
I am trying push Service Pack 1 for Office 2011 on mac client but for some reason SCCM does not want to install. Everytime I try to push, it failed with following error. The package starts for few seconds and then throws error below
"Configuration Manager encountered a problem. The software installation or update could not be completed. For more information, contact your help desk"
I have used CMAppUtil to create the package and it was converted to CMMAC format before it deployed to test mac. I have made sure the targeted mac has missing SP1. When I manually tried the DMG for SP1 it works but I did not want to install manually
. Is there anyone have encountered same issue and have resolved it? Or if you have any suggestion where and what to check then it will great!
Thanks

I am still having issues with pushing office SP1 to mac clients. Rebuilt the CMMAC file, redistributed, re-installed Office 2011 but none of these did any trick. Anyone?

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]

Mac Client?

Similar Messages

Maybe you are looking for