Setting up a new Mac Network (Naming, Virtualisation etc!)

[Whistler]

Hi,

 

I'm a complete newbie trying to setup a new Mac Network.

 

I've got a new Mac mini (current generation) along with a 2012 version available to use. We also have a USB-C RAID array available that I intend to use for the newer Mac mini.

 

I'm familiar with virtualisation in a Windows environment however unsure of the best route to go down with regards to setting this new stuff up.

 

Client-wise we've got two iMac 5K's and two MacBook Pro's. The older Mac mini is running Sierra (and due to the server limitations being removed in later versions, I'd like to keep it on that unless there's a legitimately reasonable reason to upgrade it).

 

My head is telling me to install all of the 'Main' stuff such as Open Directory on the newer Mac (and hold the home folders etc), and use the older Mac for things such as Printers & update caching etc. Am I best virtualising this using VMware (which we're licensed for if we want to use it), or just installing stuff straight onto the OS?

 

I'd like to get Home Folders setup, so that the clients logging on save all of their data to the server.

 

We don't have any Windows machines on the network at the minute, so we're strictly Mac however we may have to integrate Open Directory with Active Directory down the linen. Not an issue for now, however.

 

My other interesting question is: 'What do you call Mac Servers?' - In a Windows environment I'd have gone with 'DC01' etc as roles were more split-up - however for an 'all eggs in one basket' approach (i.e only having two physical servers), what's the best name to call the two servers?

 

The network is 10 Gigabit, and we can achieve those speeds on the newer Mac as it has the 10GbE Ethernet NIC, and we could also do similar with the older Mac using Thunderbolt.

 

I think I've covered all bases and we have the server app downloaded and ready.

 

Thanks.

[ozydave]

Hi,

 

I'm a complete newbie trying to setup a new Mac Network.

 

I've got a new Mac mini (current generation) along with a 2012 version available to use. We also have a USB-C RAID array available that I intend to use for the newer Mac mini.

 

I'm familiar with virtualisation in a Windows environment however unsure of the best route to go down with regards to setting this new stuff up.

 

Client-wise we've got two iMac 5K's and two MacBook Pro's. The older Mac mini is running Sierra (and due to the server limitations being removed in later versions, I'd like to keep it on that unless there's a legitimately reasonable reason to upgrade it).

 

My head is telling me to install all of the 'Main' stuff such as Open Directory on the newer Mac (and hold the home folders etc), and use the older Mac for things such as Printers & update caching etc. Am I best virtualising this using VMware (which we're licensed for if we want to use it), or just installing stuff straight onto the OS?

 

I'd like to get Home Folders setup, so that the clients logging on save all of their data to the server.

 

We don't have any Windows machines on the network at the minute, so we're strictly Mac however we may have to integrate Open Directory with Active Directory down the linen. Not an issue for now, however.

 

My other interesting question is: 'What do you call Mac Servers?' - In a Windows environment I'd have gone with 'DC01' etc as roles were more split-up - however for an 'all eggs in one basket' approach (i.e only having two physical servers), what's the best name to call the two servers?

 

The network is 10 Gigabit, and we can achieve those speeds on the newer Mac as it has the 10GbE Ethernet NIC, and we could also do similar with the older Mac using Thunderbolt.

 

I think I've covered all bases and we have the server app downloaded and ready.

 

Thanks.

I'm sure you can't virtualize a Mac OS

[Arthur]

I'm sure you can't virtualize a Mac OS

You can as long as you are doing it on Apple hardware.

 

That said, VMware doesn't officially support running ESXi on the 2018 Mac mini, so that's a moot point.

 

• www.vmware.com/resources/compatibility/search.php?deviceCategory=server&details=1&partner=269&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc
  
• www.virtuallyghetto.com/2018/11/esxi-on-the-new-2018-apple-mac-mini.html
  

[Whistler]

Okay, so I could virtualise on the older one to ensure I'm properly supported. Question now is, what do you call your Mac Server(s)?

[Norphy]

I wouldn’t call them anything special, I’d just follow your current naming convention. No need to reinvent the wheel just because the operating system is different.

[Whistler]

That's true - but at the same time do macOS roles have different 'short' names for roles (i.e on Windows: Domain Controller 01 = DC01), do the roles have 'short' names on Mac? What is the standard naming schemes for Mac servers?

[Norphy]

What roles do you see running on masOS?

 

Apple’s server app is all but deprecated and only has Profile Manager in it these days. You wouldn’t use macOS for DHCP, DNS or as a directory server. You wouldn’t use it as a web server. You might use it as a file server if you’re desperate to use AFP as a file transfer protocol but Macs talk SMB pretty well these days so you don’t really need it for that. About the only Mac specific role these days is the update caching server