Do you find it difficult to keep consistent Skyline configurations to external sources (vCenter, NSX, vROps, etc.)? You can connect to each source individually, but that does not work well when you have 10+ sources
���VCENTER���
CREATE-ROLE
skyline-help.ps1 create-role VCENTER ROLE
ie: skyline-help.ps1 create-role 192.168.222.10 Skyline
CHECK-ROLE
skyline-help.ps1 check-role VCENTER ROLE
ie: skyline-help.ps1 check-rule 192.168.222.10 Skyline
ADD-2-ROLE
skyline-help.ps1 add-2-role VCENTER USER ROLE
ie: skyline-help.ps1 add-2-role 192.168.222.10 sonnyvn Skyline
CHECK-ACCOUNT
skyline-help.ps1 check-account VCENTER USER
ie: skyline-help.ps1 check-account 192.168.222.10 sonnyvn
���SKYLINE���
SKYLINE-PREP (NOTE: install prep locally)
skyline-help.ps1 skyline-prep
CHECK-UPDATE
skyline-help.ps1 check-update SKYLINE-COLLECTOR
ie: skyline-help.ps1 check-update 192.168.222.50
INSTALL-UPDATE
skyline-help.ps1 install-update SKYLINE-COLLECTOR
ie: skyline-help.ps1 install-update 192.168.222.50
CHECK-VERSION
skyline-help.ps1 check-version SKYLINE-COLLECTOR
ie: skyline-help.ps1 check-version 192.168.222.50
���NSX���
NSX-PREP (NOTE: install prep locally)
skyline-help.ps1 nsx-prep
CHECK-NSXACCOUNT (NOTE: use vCenter admin account)
skyline-help.ps1 check-nsxaccount VCENTER USER
ie: skyline-help.ps1 check-nsxaccount 192.168.222.10 Skyline
���VROPS���
...coming soon...
���HORIZON���
...coming soon...
#VMwarePowerCLI#chocolatety#PowerShell#powernsx#skyline#Apache2.0#powercli