diff --git a/admin-guide/deployment/basic_installation.md b/admin-guide/deployment/basic_installation.md
index a47b79bc..d4df9190 100644
--- a/admin-guide/deployment/basic_installation.md
+++ b/admin-guide/deployment/basic_installation.md
@@ -9,6 +9,8 @@ When PXE boot is not an option, e.g. in restricted networks, it is possible to s
 
 The general process for a installation is:
 
+1. (Hardware) Register the machine in Package-Fence: https://enter.psi.ch:1443 to give it access to the PSI network
+1. (Hardware Machine / static ip address) Register a static ip in https://qip.psi.ch/qip (or via request to the Network Team (via ServiceNow)) for the console 
 1. Register and configure the system with sysdb
 2. Tell sysdb to perform an installation on the next boot
 3. Reboot the system and trigger a PXE boot (usually by pressing F12 during
diff --git a/admin-guide/deployment/console_installation.md b/admin-guide/deployment/console_installation.md
index 10fe3137..fc8fe2ac 100644
--- a/admin-guide/deployment/console_installation.md
+++ b/admin-guide/deployment/console_installation.md
@@ -10,7 +10,8 @@ Due to various reasons these systems __must__ have a static IP assigned.
 
 ## Installation Workflow
 
-1. Register a static ip in https://qip.psi.ch/qip for the console
+1. Register the machine in Package-Fence: https://enter.psi.ch:1443 to give it access to the PSI network
+1. Register a static ip in https://qip.psi.ch/qip (or via request to the Network Team (via ServiceNow)) for the console 
 2. Create the necessary bob entries for the machine:
 ```bash
 bob node add <your-console.psi.ch> <hiera environment without "data-"> netboot