u/unsung-hiro

I need to replace an existing 2019 server DC that has ADCS (CA root) and NPS (Wi-Fi RADIUS) roles with a new 2025 server having the same roles, but with a new hostname. (I realize reusing the same name would be easier, but this is not an option.) My initial research shows the general steps would be to install/configure ADCS for the new CA root, do something with Group Policy for the clients to trust the new server, then install/configure NPS to use the new CA root, and finally have the Wi-Fi APs/controller use the new NPS/RADIUS. My desire is to run both environments in parallel as I migrate any clients/dependencies piecemeal. As the single IT resource in my org, I'm not a dedicated server admin so I was hoping any experts here might be able to corroborate my understanding above and maybe provide more detailed steps as to what needs to be done. I will of course do my due diligence and am happy to get into the weeds on learning the process, but would very much appreciate any guidance to get things started.

Thank you for reading 😄

I have a standalone Windows server (VM) hosted at a third-party data center that is shared/used by multiple orgs. As a shared server, maintaining the server will be a collaborative effort by select IT staff from some of the orgs. The server is running a single, very specific service and is pretty much set-it-and-forget-it, so the remote access is mainly for periodic maintenance such as Windows updates, disk clean-up, etc.

I'm looking for a solution for these IT folks to be able to securely connect to this server over the internet preferably without setting up a complicated VPN infrastructure. The data center operator is willing accommodate requests (opening up ports and such) to a certain degree but installing additional equipment (VPN appliances, etc.) is probably a no-go.

One-time costs would be acceptable but we'd like to avoid subscription-based solutions as it's difficult to split the bill among the organizations for administrative reasons.

Within my org, we are using RemotePC to access certain isolated machines that can't be part of our RMM. I thought this might work as adding one more machine to our account costs nothing, but it requires adding collaborators as users in an existing RemotePC account which creates a dependency on a single org. If my org dies, so too does the account, and access for all provisioned users.

Does anyone have any suggestions in this scenario?

Thank you in advance for any advice and insight.

I have a TS-464 running QuTS hero w/ SSD caching and 4x 4TB spinning disks. I am creating a shared folder to house Virtualization Station VM files - nothing too crazy, mainly Linux-based "appliances". There are so many settings and I am not sure the best way to configure them if this folder is to be used only for VM storage. Can anyone share any experiences or recommendations?

• Space Allocation: Thick or Thin?
• Data Reduction: Enable or disable compression and deduplication?
• Performance: Enable or disable SSD read cache and Fast clone?
• Performance profile (block size): 4K/8K/16K/32K/64K/128K?

Any other tips would also be appreciated.

Thank you!