This section talks about how to login and the pre-requisites before starting the Lab
2. Horizon Login
Use the Testdrive Credentials provided in the Login Credentials menu on the top right corner to sign-in to VMware Horizon.
- Click the copy icon next to the username to copy
- Paste it on the Horizon username field by clicking on it, followed by pressing CTRL+v (Windows) or Command (⌘) + v (macOS) on your keyboard
- Next, click the copy icon next to the password to copy
- Paste it on the Horizon password field by clicking on it, followed by pressing CTRL+v (Windows) or Command (⌘) + v (macOS) on your keyboard
- Click Login to access
Other pasting options:
- Windows: use right-click on your mouse/ trackpad and select Paste
- macOS: press and hold the control key while you click the Horizon username/password field and select Paste
3. Launch Desktop
Once logged in, search for 'NSX Security' on the Apps Tab and click on the Horizon Desktop to launch it on your Browser.
4. Access NSX Security Desktop
Now you'll be on the NSX Security desktop. At this point you can begin the walkthrough steps listed in the next section.
5. Access NSX-T 3.2 Manager
The console is accessed through a supported web browser Chrome. Login to NSX-T Manager:
- Click on NSX-Mgr AutoLogon shortcut on the Desktop. Shortcut will open the URL to NSX: https://dal-nsxmgr.nsx-sdfw.local/
- Username/Password: Sign-in is automated, so please don't touch the keyboard/mouse during 15s of process. If you do so, please close all Chrome windows and reopen the link again.
- In case you prefer using manual login, please click on NSX icon inside Lab Access folder and enter your Testdrive email@example.com / password.
6. Prerequisites for Ransomware Lab
In the lab, to simulate an enterprise environment, the following VMs have been deployed: a VDI Desktop and a production data base server. These two VMs are connected to NSX-T overlay segments.
7. Prerequisites for Ransomware Lab (contd.)
A supplementary VM has been deployed to play the role of an attacker, an external resource from where the attacks are initiated. This VM is attached to a VLAN type port group to a virtual distributed switch. Agent operating system (OS) type and roles are as shown above.