Jump to CustomersLinton > Linton > PowerOn
Power on procedure
Power on physical servers
Physical NetManager servers:
- proxy
XenServer hosts:
- xenbackup01
- xendesktop01
- xendesktop02
- xendesktop03
- xendesktop04
- xendesktop05
- xenserver01
- xenserver02
- xenserver03
Start VMs on Linton DR pool
The only VMs that need to be started here don't have a dependency on anything else:
- backup
- salt01
Start VMs on the Linton pool
Dependency free VMs
Start any VMs which don't have a dependency on any other service:
- Citrix License Server Virtual Appliance
- Unifi
- NetManager
- stor2rrd
Domain controllers:
Start a single domain controller:
- DC01
Wait for this server to reach the login screen - this is likely to be slow as a single domain controller will be looking for and waiting for other domain controllers
Then start the second domain controller:
- DC02 (avoid the same server as DC01)
Windows Activation server
To try and reduce any Windows activation related issues:
- KMS
File, database, and service servers
i.e. these are likely providing services to other places
- ABTutor
- Applayers
- GADS
- Homeareas
- Oliver
- PVSCore
- Paxton
- Printers2019
- Resources
- SIMS
- Semieta
- Solidworks
- XenCore
- sQuid
Start physical PVS servers
If these were already running for some reason then leaving them running would likely be OK:
- PVS01
- PVS02
Start XenDesktop services
Start delivery controllers:
- XDC01
- XDC02 (avoid the same server as XDC01)
Access to publisher resources
Start NetScaler infrastructure
- NetScaler Virtual Appliance
- nslb01
- nslb02 (avoid the same server as nslb01)
Backend services only
User's wouldn't be able to tell if these are running or not and so these VMs can be started later than the rest:
- AADC
- Collector
- ELM
- Every
- MDT
- MDT7
- ManageEngine
- Management
- Solus
- WDS
- WSUS
Check Windows firewall profile
Any domain joined Windows installation which started before a domain controller was running may be using a firewall profile that isn't the domain one, potentially firewalling itself and preventing connections from other machines for some services.
The most likely candidate for a problem is the first domain controller:
- DC01 (restart it)