[PERTnet]

Yes, it’s still exceptionally handy to have installed, and there is no other 3rd party or Apple integrated solution that I’ve heard mentioned.

And, frankly, I don’t expect that Snow Leopard is going to accommodate…

Darrin

[PERTnet]

We have four DC’s, two virtual and two physical, all represented properly (as far as I can tell) in the Service Records. Using the FQDN or IP as the prefered DC while binding does no good. This AD was just implemented as an ‘upgrade’ from an NT domain.

One Site and using AD DNS…

[PERTnet]

Looks like Management is considering opening a case with Apple Engineering ($$$) to figure this out… 😡

Other ideas, Anyone?

D.

[PERTnet]

Chris,

I would advise using whatever scheme your windows computers use. Doing so will preserve continuity in your AD administration and be one less reason to make special Macintosh exceptions. Your Windows admins will appreciate that. No solution is prefect, and yes, there are pros/cons in every case.

Where I’m at now, we set the Sharing > Computer Name to an abbreviation of the department (ADV for Advertising) and then a sequential number, 001 and up. That then becomes the AD Computer name ADV-001. Hopefully the machine stays in Advertising. If it moves to Sales, I gotta change the name and rebind with new name.

If you go even more generic like MAC address, serial number or asset tag number, you don’t need to worry about it again.

I use the Sharing > ARD Info fields 1-4 for things like user name, location etc., that’s easy to see and report from in ARD.

Darrin

[PERTnet]

I’ve got a slight clue to resolving my problem…

Installing ADmitMac on a 10.4 machine configures and binds no problem what so ever. However, it’s not really a solution for us.

So what in the world is the Thursby Plug-in doing that the Apple’s is not?

Grrrrr. 👿

[Author]

Posts