AFP548 Changing the world one server at a time.

Best practices?

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #365505
    ComputerX
    Participant

    Hi all,

    Sorry for a vague request. I am being a bit more rushed than I would like.

    I was a Mac guy a long time ago. The last few years have been very PC with a little Linux and BSD around the edges. I have recently taken back a old client. They have had a series of frightening consultants since I left them. Their network is a disaster but I thought we could fix things slowly.

    Tonight I found pretty solid evidence that their OS X server has been rooted. I hope it is just a script sending spam but I feel a need to be safe and rebuild. The problem is I have built a OS X server other than the original OS 10. Remember that one? Before all this fancy “X” branding? I told you it had been a while.

    Where would I find good best practices for building a OS X server?

    Anything in particular I should pay attention to?

    The client is now 50/50 Mac and Windows. They do not have a domain for their Windows machines. Neither are the Macs managed by the server. I would like to get a single sign in system going. How does Open Directory and Active Directory play together these days? What is the best way to build it? Can I have them talking to each other or should I build a Mac directory and a Windows directory? Two authentication sources is still better than what they have now. Namely a local account for each person on every machine.

    I will read the AD-OD-2.1 paper tomorrow. I have spent the last 5 hours chasing possible rootkits and I am too burned to make sense of it now. What else should I read?

    Thanks in advance. I thought I would have a few weeks to get up to speed on this. I’m not even scheduled to be on site for another week but this has popped up unexpectedly.

    Dan

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.