FitnessOgre

While you can install Exchange on the Same server as an Active Directory Domain Controller, for basic testing and learning it will be fine, but aside from that its not recommended. Frankly on my home server I run Vmware and have multiple guest servers running on my host. I have a Active Directory Domain Controller, a File Server, and plenty of space for test servers such as Exchange, SQL, Web and Application servers. Having a virtualization host is a whole other rabbit hole. 

When you create a domain controller for your active directory domain, you will also install DNS and a few other Directory Services components that will be needed for Exchange Servers Setup to even start. The Exchange 2019 install will tell you what your pre-requisites are and will help you install them. 

Some other gotcha's that I have learned.

Disk space. Make sure you have a reasonable amount of disk to allow Exchange to "Breath". With the release of 2013 and later Microsoft has increased the amount of diagnostic logging that the server does. All these logs will be located in the install directory for exchange, so if you notice that you are running out of disk space chances are its full of logs. The IIS inetpub directory will also fill with logs so you may want to look for a log cleanup PowerShell command to run or manually go in and clear the logs... Recommend a script of some sort as this can be very tedious. 

Exchange Databases need to be backed up or have Circular Logging enabled, otherwise the Exchange Transaction logs are going to fill up the disk, with circular logging the logs will be committed to the mailbox database regularly. For what you are doing circular logging will suffice as this isn't an production deployment. This will keep your disk usage under control. 

Exchange server is a disk hungry application. If those disks fill up, Exchange stops working. 

Try to install Exchange on a separate disk from your OS. At least of the Install drive fills up your sever won't completely crap out. 

Use powershell as much as you can to do exchange tasks. This really helps you to learn how to administer the server. Yes the Web Console is functional and frankly easier for some tasks. However I find that Powershell is more "verbose" about issues, learn to use the exchange management shell. Its helped me do a lot of things that the Console and ECP just don't do. 

If you decide to remove it and still want your Active Directory to work after, make sure you uninstall it properly. Otherwise there is all kinds of leftover bits and issues left behind. This was my experience with 2003 and 2010 version of Exchange. 2016 and 2019 seem pretty solid, though I haven't had to uninstall either of those. 
 
Seriously there is so many little things that Exchange needs to function. Good luck with your learning.  

 

Ubiquiti Nanobeams are great for this type of application. 500+ Meter range, good speed. Easy to setup, and once in place generally maintenance free. I use Nanobeam devices on a number of outbuildings connecting back to a larger sector style antenna. No issues. 

Though if the distance is less than say 100M you could also just mount an outdoor grade Access Point on your exterior of your house and likely reach your garage with a much simpler installation. My Wireless AP reaches my garage no problem, and I have mine in my basement, not ideal I know but it hits the garage with full signal. 

I use the Ubiquiti UAP-AC-LR Access point. The only real downside is that you need the Controller software to configure and secure the AP properly. I have it running on my home server and it works fine. I had it on my personal desktop as well without issue. 

There are other Access Points on the market so shop around. I just happen to like the Ubiquiti equipment a lot and it hasn't let me down yet. 
 

Also you need Active Directory. Exchange will not work without it.
 

Its an Access Point, plug it into your network, configure the security and it will broadcast sweet sweet wifi for your phone, laptop, xbox, whatever you want to connect to it.
 

A couple of things you could check;
 
Things I would look for;
 
1) Exchange Setup Logs. There is a log file generated in a folder on the C:\ that will have detailed information as to why you may be having an issue.
 
2) Make sure that you are installing the latest RU of Exchange Server. You can download this direct from Microsoft. 
 
3) Make sure that the version of Windows you are installing on is up to date. 
 
4) Without knowing more about the environment its hard to troubleshoot further. There are a number of variables that can impact the successful install of Exchange Server.

Cat5 can be used for phone lines. Done all the time. Its not pretty but it works. Just don't use all the pairs. 

 

Fiber cables aren't crimped... They are cut, polished and terminated. People go to school to work with Fiber Optic Cabling. Its not like ethernet where if you mess up the end you just cut it off and try again, its a bit more involving.

If you can just buy pre-made patch cords, I would go with Multimode - LC standard. Easy to work with, SFP's are readily available. Plus for the distances we are talking about you don't need the long distance offered by Single mode. I use Single mode between buildings that are further than 500m from one another. I can push Multi-Mode further but the quality of the connection degrades the farther you go. 

Switching is going to be somewhat expensive as you will need switches for each floor that have multi-purpose ports to install the SFP into, or get a line converter that allows you to convert to a copper ethernet cable. Not a fan of these as they are typically unmanaged, require additional power, and if they fail they don't always show as failed. I have tons of these things across multiple locations and I have been replacing them with Cisco fiber switches in my core and using SFPs.

As cool as this idea may be there really isn't a benefit unless you are really pushing data between the floors of your house. Most people get away with GbE, or even 10GbE over copper. 

If you are going to go this way my suggestion is to pay someone to do the fiber work... 
 
 

If you are set on a fiber connection - MM will get the job done, but SM will give you more speed options over a longer range. The problem I have noticed with SM though is that the SFP Modules tend to be more expensive at least in Cisco and HP Switches. If you go with a Copper to Fiber converter, SM ones from black box aren't horribly priced though they introduce another point of failure into your network. A managed switch with Muli-use network ports would be ideal on each end, and corresponding SFP SM modules. More expensive but you get more options. 

If you plan on pushing the cable through the ground in a conduit or whatever, pre-terminated cables will require a bit more care so as to not damage the end. Wrapping the end before feeding it into the conduit would be necessary. Other wise you could hire someone to terminate for you if you aren't sure how... A skill I wish I had. 

Frankly for what you are describing a P2P Wireless Bridge (assuming you have relative line of sight) would give you the best bang for your buck. You can get decent speeds from UBNT Wireless Bridges over greater distances for about $125 US per side. Easy to mount, easy to configure, and generally pain free.  

Sounds like a fun project. Enjoy!

You may need to set the HP Smart Array as the Boot Device in the BIOS. 
 

You don't have to join a server to the domain, however it makes using that server easier in a domain environment. Security and access rights and all the benefits of AD. Is there a reason why you don't want to join the server to the domain?

You don't have to join a server to the domain, however it makes using that server easier in a domain environment. Security and access rights and all the benefits of AD. Is there a reason why you don't want to join the server to the domain?

DIY Solutions for the workplace are not ideal unless you are willing to support this box. QNAP or Synology offer business class NAS devices that will meet your needs. While neither are intended for the enterprise level, the QNAP's I find are pretty solid. We have some in our fleet that are over 6 years old and still running no problem. 

As a long time server admin, my advice to you is especially with HP is to talk to your sales guy. Don't be afraid to ask these guys questions, they know what their kit can do. However the server you are looking for is probably going to cost more than $10K for those spec's. 

A few recommendations;

1) If your company is on HP the DL380 Gen 9 2U server will give you the most options in terms of disk and space. Lots of room for extra NICs and or FC or whatever if you ever need to connect it to a SAN. 

2) 128GB of RAM would be a minimum. Always get more RAM when you can.
 
3) To get the 5TB RAID 10 you will need either 10 x 1TB SAS disks for the RAID 10. Or 6 1.8TB SAS disks. I would also suggest that you get a separate pair of disks for your OS running a RAID1. 300GB seems to be standard small size for basic disks. 
 
Good luck!