network a mac

[russdev]

ok not sure best way of doing this got a mac laptop and the user is going to connect to network so obvious can set to login into ad and then if they want to login locall use local login.

right also could we set it up so that on local login desktop there is a shortcut or what ever mac alt is to network location...

advice pros/cons etc

Russ

[Ric_]

Is this not what was demonstrated at the conference?

You need to use that directory connection thingy (after making sure that DNS works prperly, etc.).

You then just use samba (or apple's tools - unsure what these are) to create a shortcut to areas on the network. Homeshare should be mapped following the connector setup.

[kingswood]

Applications > Utilities > Directory Access

You need to configure your Directory Access entry by clicking "Active Directory", click "Configure" and then fill in your AD forest and Domain Name. Change the Computer ID field if you need to make it room centric, and if you like expand the "Show Advanced Options" for things like creating mobile accounts, protocol, default user shell, mappings etc.

When you're finished with the options, just click "Bind". It will ask you to authenticate- so use your Domain Admin account, put your password in and it should be fine.

There's a pretty good article here about it all:

http://www.certmag.com/articles/temp...1269&zoneid=91

HTH

Paul

[russdev]

whated pros and cons to either just creating short cut to folder or gettin mac to login into ad what is best way as to say

Russ

[kingswood]

Sorry- was just answering this: "ok not sure best way of doing this", it was afterwards you asked this- "right also could we set it up so that on local login desktop there is a shortcut or what ever mac alt is to network location..."

Paul

[kingswood]

Sent that before I had finished! lol!

If you can get away with it, just use a local logon with shortcuts to resources on your network. The problem will be that you might need to enter network authentication details each time you access those resources.

Really depends on how many resources the Mac will need access to and how often it will be accessing the AD...if you don't mind typing in a username and password when you mount a directory via SMB, then use that. Of course because you aren't in any way bound to the AD you can't just browse for resources, so the down side is that you really need to know where those resources are and get that path correct.

MS say this:

"On a large network, problems quickly arise. You still need to log in to each and every resource you access. This quickly becomes cumbersome on all but the simplest of networks. In addition, the Mac client is not a domain member, which means that there is no domain login account for it. You cannot map your home directory during login. Browsing for resources is very limited—you can only browse on your local subnet. Security becomes an issue because the Mac can cache the user names and passwords for the resources it uses. Without an Active Directory login, someone could easily gain access to a Mac client and related domain resources with the locally cached login information."

HTH (this time)

Paul