Boot Runner VM Boot No Login


#1

I try to boot a VM in Boot Runner and it just shows me the login prompt for MacOS and never logs in.

If I log in with the user I created it does load the VM.

Any ideas the user exists and the username and password is typed correctly but it never tries to login.


#2

Is it possible to share the configuration profile you created? Please send it to support@twocanoes.com and I’ll take a look at it.

tim


#3
<?xml version="1.0" encoding="UTF-8"?> PayloadContent PayloadContent com.twocanoes.bootrunner Forced mcx_preference_settings AutomaticallySelectVolume Windows
            <key>InitiallySelectedVolume</key>
            <string>Windows</string>

            <key>MarqueeTextPosition</key>
            <integer>0</integer>

            <key>ScrollMarquee</key>
            <true />

            <key>SelectSingleMacVolume</key>
            <true />

            <key>ShowRestartButton</key>
            <true />

            <key>ShowShutdownButton</key>
            <true />

            <key>ShowPopoverOnStart</key>
            <false />

            <key>ShowPopover</key>
            <false />

            <key>HideReturnButton</key>
            <false />

            <key>Timeout</key>
            <integer>60</integer>

            <key>LimitTimes</key>
            <false />

            <key>AutoSelectTimeout</key>
            <integer>40</integer>

            <key>DiskLabelFontSize</key>
            <integer>24</integer>

            <key>HideStatusBar</key>
            <false />

            <key>MarqueeOnScreenTime</key>
            <string>10.0</string>

            <key>MarqueeOffScreenTime</key>
            <string>2.0</string>

            <key>LimitDays</key>
            <array><integer>1</integer><integer>1</integer><integer>1</integer><integer>1</integer><integer>1</integer><integer>1</integer><integer>1</integer></array>

            <key>VolumeDescriptions</key>
            <array>
              <dict>
                <key>UseVM</key>
                <string>false</string>

                <key>VolumeName</key>
                <string>disk0s2</string>

                <key>VolumeLabel</key>
                <string>MacOS</string>

                <key>VolumeType</key>
                <string>1</string>

              </dict>
              <dict>
                <key>UseVM</key>
                <string>true</string>

                <key>VolumeName</key>
                <string>Windows</string>

                <key>VolumeLabel</key>
                <string>Windows</string>

                <key>VolumeType</key>
                <string>2</string>

                <key>VMUsername</key>
                <string>vmuser</string>

                <key>VMPath</key>
                <string>VBoxManage startvm "Windows10"</string>

                <key>VMPassword</key>
                <string>aXRzYXZt</string>

              </dict>
            </array>
          </dict>
        </dict>
      </array>
    </dict>
  </dict>
  <key>PayloadEnabled</key>
  <true/>
  <key>PayloadIdentifier</key>
  <string>MCXToProfile.ba979a43-72a0-454c-9d8f-4b9d66ee30e0.alacarte.customsettings.771da400-81ce-45d6-b64a-4e3381118632</string>
  <key>PayloadType</key>
  <string>com.apple.ManagedClient.preferences</string>
  <key>PayloadUUID</key>
  <string>771da400-81ce-45d6-b64a-4e3381118632</string>
  <key>PayloadVersion</key>
  <integer>1</integer>
</dict>
PayloadDescription Included custom settings: com.twocanoes.bootrunner PayloadDisplayName MCXToProfile: com.twocanoes.bootrunner PayloadIdentifier com.twocanoes.bootrunnertest PayloadOrganization PayloadRemovalDisallowed PayloadScope System PayloadType Configuration PayloadUUID ba979a43-72a0-454c-9d8f-4b9d66ee30e0 PayloadVersion 1

#4

When it goes to auto login with this config i get a - for the username and a circle then it fails back to boot runner. Also of note the VMPassword is not the password I typed.


#5

After further review I found that this was old image and something must have been misconfigured. I tried on a new clean OS and it works fine with no issues. So the issue is with our build and not with your software.