diff --git a/Servers/Automation/Ansible/AWX/AWX Kerberos Implementation.md b/Servers/Automation/Ansible/AWX/AWX Kerberos Implementation.md
index f6e2140..c10fd79 100644
--- a/Servers/Automation/Ansible/AWX/AWX Kerberos Implementation.md	
+++ b/Servers/Automation/Ansible/AWX/AWX Kerberos Implementation.md	
@@ -4,7 +4,7 @@ You may find that you need to be able to run playbooks on domain-joined Windows
 ### Configure Windows Devices
 You will need to prepare the Windows devices to allow them to be remotely controlled by Ansible playbooks.  Run the following powershell script on all of the devices that will be managed by the Ansible AWX environment.
 
-- [WinRM Prerequisite Setup Script](https://docs.bunny-lab.io/Docker%20%26%20Kubernetes/Servers/AWX/AWX%20Operator/Enable%20Kerberos%20WinRM/)
+- [WinRM Prerequisite Setup Script](https://docs.bunny-lab.io/Servers/Automation/Ansible/Enable%20WinRM%20on%20Windows%20Devices/)
 
 ### Create an AWX Instance Group
 At this point, we need to make an "Instance Group" for the AWX Execution Environments that will use both a Keytab file and custom DNS servers defined by configmap files created below.  Reference information was found [here](https://github.com/kurokobo/awx-on-k3s/blob/main/tips/use-kerberos.md#create-container-group).  This group allows for persistence across playbooks/templates, so that if you establish a Kerberos authentication in one playbook, it will persist through the entire job's workflow.