Nathan C. McGuire

Tag: IT Security

  • From K-12 IT to Healthcare IT: Preparing for a Major Career Shift

    After years in K-12 education IT, I’ve recently accepted a role in healthcare IT. While I haven’t started yet, I’ve been reflecting on what this transition means—what skills carry over, what new challenges I’ll face, and how I can prepare for the shift.

    For those in IT considering a similar move, here’s what I’ve learned so far as I prepare to step into this new world.

    What K-12 IT and Healthcare IT Have in Common

    At first glance, education and healthcare seem like vastly different industries, but IT professionals in both fields share some major responsibilities:

    • Security & Compliance – In schools, we deal with FERPA (protecting student data); in healthcare, it’s HIPAA (protecting patient records). Both demand strict access controls, encryption, and careful handling of sensitive information.

    • Mission-Critical Systems – Whether it’s a school-wide internet outage during state testing or a hospital’s electronic health records (EHR) system going down, IT failures have real-world consequences. Uptime is non-negotiable.

    • Limited Budgets, High Expectations – Schools and healthcare facilities often need to do more with less. Stretching hardware lifespans, optimizing software costs, and making smart infrastructure investments are key skills in both environments.

    Key Differences Between K-12 and Healthcare IT

    1. Always-On Infrastructure

    In K-12, IT can plan maintenance windows around weekends or summer breaks. In healthcare, there’s no downtime—systems need to be available 24/7. Any updates, patches, or changes must be carefully planned to avoid disrupting patient care.

    2. Complexity of Systems

    K-12 IT teams manage student information systems (SIS), Google Workspace, and classroom technology. Healthcare IT involves electronic health records (EHR), medical imaging (PACS), diagnostic equipment, and secure messaging systems—all of which must integrate smoothly to avoid treatment delays.

    3. The Stakes are Higher

    A mistake in education IT might mean a teacher loses access to their lesson plan. In healthcare, an IT failure can delay patient care, disrupt surgeries, or compromise life-saving treatments. The pressure to get things right is significantly greater.

    How I’m Preparing for the Transition

    • Studying Healthcare IT Basics – Learning about EHR systems (like Epic or Cerner), HIPAA compliance, and medical device security before day one.

    • Strengthening Security Knowledge – While security is always a priority, cyberattacks on healthcare organizations are a constant threat. Reviewing best practices for network segmentation, access control, and ransomware defense.

    • Adjusting to 24/7 Operations – Expecting on-call responsibilities and tighter change management procedures compared to the more flexible schedules in K-12 IT.

    Final Thoughts

    Switching industries is always a challenge, but IT fundamentals—security, uptime, and problem-solving—are universal. While I expect a learning curve, I’m confident that my experience in K-12 IT has prepared me for what’s ahead.

    If you’ve made a similar transition (or are considering one), I’d love to hear your thoughts—what was your biggest challenge? What helped the most? Drop a comment or reach out!

  • Enabling Remote Desktop Access on Windows with PowerShell

    When managing a remote network or administering systems across multiple locations, enabling Remote Desktop Protocol (RDP) becomes an essential task. Here’s a quick and efficient way to set up RDP on a Windows machine using PowerShell commands. This method ensures secure connections, including Network Level Authentication (NLA) and the appropriate firewall settings.

    1. Enable Remote Desktop Connections

    First, you’ll need to enable RDP connections on the system. By default, Windows disables Remote Desktop connections for security reasons. You can change this setting using PowerShell.

    Set-ItemProperty'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\'-Name"fDenyTSConnections"-Value0

    This command modifies the registry key that controls RDP access. Setting fDenyTSConnections to 0 ensures that RDP is enabled on the machine.

    2. Enable Network Level Authentication (NLA)

    Network Level Authentication (NLA) adds an additional layer of security by requiring users to authenticate before establishing a full RDP session. This is a recommended best practice to prevent unauthorized access and reduce the risk of exploitation.

    Set-ItemProperty'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\'-Name"UserAuthentication"-Value1

    By setting UserAuthentication to 1, you ensure that NLA is required for all RDP connections, thus enhancing the security of remote desktop access.

    3. Enable Windows Firewall Rules for RDP

    Now, we need to ensure that the Windows firewall allows incoming RDP connections. Windows Firewall typically blocks most incoming traffic unless explicitly allowed. Luckily, you can enable the necessary firewall rules for RDP with this command:

    Enable-NetFirewallRule-DisplayGroup"Remote Desktop"

    This command enables the built-in firewall rules under the “Remote Desktop” group, allowing RDP traffic to pass through the firewall.

    Final Thoughts

    By running these three PowerShell commands, you can quickly and securely enable Remote Desktop access to a Windows machine. The combination of enabling RDP, enforcing NLA, and allowing RDP through the firewall creates a balanced approach to remote access that is both efficient and secure.