1. Legacy Deployment/Deployment Run props vs. new JSON/YAML Deployment Run props

• Linux’s JSON parsing function, “JQ”, doesn’t allow us to create a variable that makes it easy to call the data within the properties file. It functions in a way that would require us to create a variable for each nested piece of data.

2. You cannot edit Scenarios directly

• You have to make a new one or clone the one you have in order to change it.

3. Asset version control

• If you upload a new asset script, it overwrites the one that is there, which cannot be undone.

4. Connection trouble with NIPR

• NIPR has trouble connecting to Google and foreign repos.

5. Azure has tiny /opt

• Use additional disks.

6. Asset installs on Windows run as a system account, not as an Administrative User account

• If some applications require user login or a user profile, that needs to be coded into the asset’s installation Powershell script

7. Asset imports via ReST API

• You must use the “app” subdomain: https://app.arcus.mil/rest/api

8. Asset Wizard media directory

• When using the Asset Wizard, you can only put one thing in the media directory. If you need multiple files you’ll need to either zip them together or use the asset zip instead. Note: To make a zip file you zip the contents, not the parent folder.

9. VM disk size

• Once a VM is provisioned, you cannot add or change the size of the disks. Be sure to add enough storage on the initial system design.

10. Pipeline jobs that run frequently and are pulling images each time will lock you out

• A solution for this is to keep certain images local, or get a Docker account.

11. To make a custom MAC address in arc1 you will need to do this…

• First 3 octets will be 00:50:56. This is the VMware Organizational Unique Identifier (OUI).

12. When your default user experience is Express Mode you cannot use any direct links (including bookmarks) or you will be redirected back to the Express dashboard.

• Exit Express Mode before using direct links or bookmarks

13. If your Linux VM password expires, new remote access SSH connections may hang

• Try connecting to the VM via direct SSH from another VM in the same Cloudspace. This should allow you to set a new password when prompted. Note: Be sure to update the password on the deployment run host page and remove any existing saved remote access connections.