locked
Server 2016 - Complaining about core count less than 12 but there are 32 cores. RRS feed

  • Question

  • I am following this guide https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-run-powershell-script 

    When I get to deploy the development kit part:

    Deploy the development kit
    Sign in as the Local Administrator to the development kit host. Use the credentials specified in the previous steps.

    It says there are less than 12 cores - How can I make sure it can use all available cores?  Does following this guide make it run as a VM?

    Any help would be appreciated.

    Thank you,

    -Sherwin

    Tuesday, September 5, 2017 3:40 PM

Answers

All replies

  • I should mention the bare metal machine has 32 cores
    Tuesday, September 5, 2017 5:16 PM
  • Hello,

    Could you please run the ASDK Pre-requisite checker script as it may reveal some clues as to what is going wrong.

     

    https://gallery.technet.microsoft.com/Deployment-Checker-for-50e0f51b

     

    Also, to expedite your investigation, please provide the following information:

     

    Build/Version:  

    Get-Content "C:\CloudDeployment\Configuration\Version\version.xml"

     

    Directory type: 

    Azure AD or ADFS

     

    Hardware: 

    How many CPU Cores, RAM, Get-Disk output

     

    Network: 

    Static or DHCP.

     

    The method used to access the Internet:

    NAT, Web Proxy, Transparent  Proxy, DMZ or Closed

     

    BareMetal or Nested Hyper-V:

     

    Deployment parameters used:

     

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.  If you continue experience any issues with ASDK release, feel free to contact us.

      

    PowerShell giving you the Blues? Try my Azure Stack PowerShell Helper scripts

    ASDK: Install/Import Azure Stack Modules 1.2.10 & AzureStack-Tools

    ASDK: Config PowerShell & set AdminStackAdmin/User ARM Endpoints

      

     Thanks,


    Gary Gallanes

    Tuesday, September 5, 2017 5:54 PM
  • PS C:\Users\Administrator\Downloads> .\asdk-prechecker.ps1
    [ 10:42:57 ] Starting Deployment Checker for Microsoft Azure Stack Development Kit (ASDK)...
    [ 10:42:57 ] There are several prerequisites checks to verify that your machine meets all the minimum requirem
    ents for deploying ASDK.
    [ 10:42:57 ] For more details, please refer to the online requirements : https://azure.microsoft.com/en-us/doc
    umentation/articles/azure-stack-deploy/
    [ 10:42:57 ] Checking for Administrator priviledge...
    [ 10:42:59 ] This script can be run on the host where you will be configuring boot from VHD, for example prior
     to downloading the ASDK files. Or it can be run after booting from the provided Cloudbuilder.vhdx file where 
    the ASDK will be installed. In the first case, it will only check for hardware specifications like memory, cor
    es, hard disk configuration, as well as free space for extracting the ASDK files. In the second case, it will 
    run both hardware and software tests, and other items like domain membership, OS version, NIC configuration wi
    ll be checked.
    Are you running this script on the host before booting in the provider VHDX file [1] or after booting into it 
    [2] (any other input will exit the script)?: 1
    [ 10:43:08 ] User chose to run pre-boot from VHD checks (hardware checks only)
    [ 10:43:08 ] Checking for physical/virtual machine status...
    [ 10:43:08 ]  -- This is a physical machine.
    [ 10:43:08 ] Checking system disk capacity...
    [ 10:43:13 ]  -- Check system disk passed successfully.
    [ 10:43:13 ] Checking physical disks...
    [ 10:43:13 ]  -- Listing of all physical disks on this server:
    
    FriendlyName      SerialNumber                     CanPool BusType             OperationalStatus HealthStatus
    ------------      ------------                     ------- -------             ----------------- ------------
    LSI MR9280-16i4e  00e7f585180eeb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  00c1ba68180ceb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  00a85fad1810eb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  00e8ed91180eeb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  006e0c9f180feb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  00ba067b180deb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  00e87771180ceb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  003d00bd1811eb3a21c0562900b26200   False RAID                OK                Healthy     
    Msft Virtual Disk                                    False File Backed Virtual OK                Healthy     
    
    
    
    [ 10:43:14 ]  -- Listing of all physical disks meeting ASDK requirements:
    
    FriendlyName     SerialNumber                     BusType OperationalStatus HealthStatus Usage           Size
    ------------     ------------                     ------- ----------------- ------------ -----           ----
    LSI MR9280-16i4e 00e7f585180eeb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 00c1ba68180ceb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 00a85fad1810eb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 00e8ed91180eeb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 006e0c9f180feb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 00ba067b180deb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 00e87771180ceb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 003d00bd1811eb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    
    
    
    [ 10:43:14 ]  -- Check physical disks passed successfully. Note that ASDK handles situations where there is a 
    pre-existing storage pool, and will delete/recreate it.
    [ 10:43:14 ] Checking Memory...
    [ 10:43:14 ]  -- Memory on this server = 256
    [ 10:43:14 ]  -- System memory check passed successfully. ASDK requires a minimum of 96 GB of RAM, with 128 GB
     recommended.
    [ 10:43:14 ] Checking processor information...
    [ 10:43:19 ]  -- Number of CPU sockets = 4
    [ 10:43:19 ]  -- Number of physical cores =  32
    [ 10:43:19 ]  -- CPU socket count (2) and core count (12) meet the minimum requirements for ASDK.
    [ 10:43:19 ] Checking Hyper-V support on the host...
    [ 10:43:21 ]  -- Hyper-V is already installed. Note that the installer would enable it otherwise.
    [ 10:43:21 ]  Checking free space for extracting the ASDK files...
    [ 10:43:21 ]  -- Listing disks and their free space
    
    DriveLetter FileSystemLabel FileSystem DriveType HealthStatus OperationalStatus SizeRemaining      Size
    ----------- --------------- ---------- --------- ------------ ----------------- -------------      ----
    O           6               ReFS       Fixed     Healthy      OK                    920.13 GB 930.81 GB
    J           1               ReFS       Fixed     Healthy      OK                    920.13 GB 930.81 GB
    K           2               ReFS       Fixed     Healthy      OK                    920.13 GB 930.81 GB
    L           3               ReFS       Fixed     Healthy      OK                    920.13 GB 930.81 GB
    N           5               ReFS       Fixed     Healthy      OK                    920.13 GB 930.81 GB
    M           4               ReFS       Fixed     Healthy      OK                    920.13 GB 930.81 GB
    I                           NTFS       Fixed     Healthy      OK                    741.99 GB 930.98 GB
    C                           NTFS       Fixed     Healthy      OK                     82.55 GB 119.66 GB
    P                           FAT32      Fixed     Healthy      OK                    303.51 MB    346 MB
                                           Fixed     Healthy      Unknown                     0 B       0 B
    E                                      Fixed     Healthy      Unknown                     0 B       0 B
    D                                      Fixed     Healthy      Unknown                     0 B       0 B
    H                                      Fixed     Healthy      Unknown                     0 B       0 B
    G                                      Fixed     Healthy      Unknown                     0 B       0 B
    F                                      Fixed     Healthy      Unknown                     0 B       0 B
    
    
    
    [ 10:43:23 ]  -- Free space check passed successfully.
    [ 10:43:23 ] SUCCESS : All of the prerequisite checks passed.
    [ 10:43:23 ] Deployment Checker has finished checking Azure Stack Development Kit requirements
    
    PS C:\Users\Administrator\Downloads> .\asdk-prechecker.ps1
    [ 10:44:18 ] Starting Deployment Checker for Microsoft Azure Stack Development Kit (ASDK)...
    [ 10:44:18 ] There are several prerequisites checks to verify that your machine meets all the minimum requirem
    ents for deploying ASDK.
    [ 10:44:18 ] For more details, please refer to the online requirements : https://azure.microsoft.com/en-us/doc
    umentation/articles/azure-stack-deploy/
    [ 10:44:18 ] Checking for Administrator priviledge...
    [ 10:44:18 ] This script can be run on the host where you will be configuring boot from VHD, for example prior
     to downloading the ASDK files. Or it can be run after booting from the provided Cloudbuilder.vhdx file where 
    the ASDK will be installed. In the first case, it will only check for hardware specifications like memory, cor
    es, hard disk configuration, as well as free space for extracting the ASDK files. In the second case, it will 
    run both hardware and software tests, and other items like domain membership, OS version, NIC configuration wi
    ll be checked.
    Are you running this script on the host before booting in the provider VHDX file [1] or after booting into it 
    [2] (any other input will exit the script)?: 2
    [ 10:44:24 ] User chose to run post-boot from VHD checks (all checks except free space)
    [ 10:44:24 ] Checking for physical/virtual machine status...
    [ 10:44:25 ]  -- This is a physical machine.
    [ 10:44:25 ] Checking system disk capacity...
    [ 10:44:25 ]  -- Check system disk passed successfully.
    [ 10:44:25 ] Checking physical disks...
    [ 10:44:25 ]  -- Listing of all physical disks on this server:
    
    FriendlyName      SerialNumber                     CanPool BusType             OperationalStatus HealthStatus
    ------------      ------------                     ------- -------             ----------------- ------------
    LSI MR9280-16i4e  00e7f585180eeb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  00c1ba68180ceb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  00a85fad1810eb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  00e8ed91180eeb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  006e0c9f180feb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  00ba067b180deb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  00e87771180ceb3a21c0562900b26200   False RAID                OK                Healthy     
    LSI MR9280-16i4e  003d00bd1811eb3a21c0562900b26200   False RAID                OK                Healthy     
    Msft Virtual Disk                                    False File Backed Virtual OK                Healthy     
    
    
    
    [ 10:44:25 ]  -- Listing of all physical disks meeting ASDK requirements:
    
    FriendlyName     SerialNumber                     BusType OperationalStatus HealthStatus Usage           Size
    ------------     ------------                     ------- ----------------- ------------ -----           ----
    LSI MR9280-16i4e 00e7f585180eeb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 00c1ba68180ceb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 00a85fad1810eb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 00e8ed91180eeb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 006e0c9f180feb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 00ba067b180deb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 00e87771180ceb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    LSI MR9280-16i4e 003d00bd1811eb3a21c0562900b26200 RAID    OK                Healthy      Auto-Select ...38144
    
    
    
    [ 10:44:25 ]  -- Check physical disks passed successfully. Note that ASDK handles situations where there is a 
    pre-existing storage pool, and will delete/recreate it.
    [ 10:44:25 ] Checking Memory...
    [ 10:44:25 ]  -- Memory on this server = 256
    [ 10:44:25 ]  -- System memory check passed successfully. ASDK requires a minimum of 96 GB of RAM, with 128 GB
     recommended.
    [ 10:44:25 ] Checking processor information...
    [ 10:44:29 ]  -- Number of CPU sockets = 4
    [ 10:44:29 ]  -- Number of physical cores =  32
    [ 10:44:29 ]  -- CPU socket count (2) and core count (12) meet the minimum requirements for ASDK.
    [ 10:44:29 ] Checking Hyper-V support on the host...
    [ 10:44:30 ]  -- Hyper-V is already installed. Note that the installer would enable it otherwise.
    [ 10:44:30 ] Checking domain join status...
    [ 10:44:30 ]  -- The host is not domain joined.
    [ 10:44:30 ] Checking Internet access...
    [ 10:44:31 ]  -- This machine has internet access (we tried to contact https://login.windows.net).
    [ 10:44:31 ] Checking Host OS version...
    [ 10:44:31 ]  -- Host OS version: 10.0.14393, SKU: 8
    [ 10:44:31 ]  -- The host OS version matches the requirements for ASDK (10.0.14393).
    [ 10:44:31 ] Checking NIC status...
    [ 10:44:34 ]  -- NIC configuration passed successfully.
    [ 10:44:34 ] Checking NIC requirements...
    [ 10:44:41 ]  -- Network cards requirements are met.
    [ 10:44:41 ] Checking server name...
    [ 10:44:41 ]  -- Server name is AZUREBOX1
    [ 10:44:41 ]  -- Server name does not conflict with future domain name AzureStack.local.
    [ 10:44:41 ] SUCCESS : All of the prerequisite checks passed.
    [ 10:44:41 ] Deployment Checker has finished checking Azure Stack Development Kit requirements

    I ran both 1 and 2 from within the second part

    Get-Content "C:\CloudDeployment\Configuration\Version\version.xml"
    <Version>1.0.170627.1</Version>

    AzureAD (We have azure I'd like to connect this box to it and migrate VMS back and forth)

    32 cores 256 gigs of ram

    DHCP for now 

    NAT

    BareMetal (Installed exactly as the guide dictated onto baremetal server 2016 - though on second bootup is that a VM?

    Thank you for your help so far, looking forward to a solution. 

    Thank you,

    -Sherwin

    Wednesday, September 6, 2017 2:54 PM
  • PS I:\AzureStack_Installer> .\asdk-installer.ps1
    Initialize environment. Please wait...
    VERBOSE: InstallAzureStackPOC.ps1 -Rerun True
    
    VERBOSE: Rerunning deployment. If you receive the same error on rerun it may be necessary to perform a full re
    deployment to address the issue.
    VERBOSE: Starting AzureStack deployment.
    VERBOSE: Loading cloud definition.
    VERBOSE: Progress file: 'Progress.Deployment.xml'
    VERBOSE: Log file: 'C:\CloudDeployment\Logs\Deployment.2017-09-06.10-56-44.0.log'
    VERBOSE: Invoking action: 'Deployment'
    STARTING: Action 'Deployment'
    VERBOSE: Action: Running action plan 'Deployment'. - 9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration' is 800. - 9/6/
    2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step '30' is 700. - 9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step '40' is 600. - 9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step '60' is 500. - 9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step '230' is 400. - 9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step '231' is 300. - 9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step '232' is 200. - 9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step '241' is 100. - 9/6/2017 10:56:44 AM
    VERBOSE: The following steps are currently ready: PhysicalMachineAndInitialConfiguration. - 9/6/2017 10:56:44 
    AM
    VERBOSE: Processing step: PhysicalMachineAndInitialConfiguration. - 9/6/2017 10:56:44 AM
    VERBOSE: Executing step: PhysicalMachineAndInitialConfiguration. - 9/6/2017 10:56:44 AM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently in progress:
     'PhysicalMachineAndInitialConfiguration'. - 9/6/2017 10:56:44 AM
    VERBOSE: The following steps are currently ready: . - 9/6/2017 10:56:44 AM
    VERBOSE: No steps are ready for execution. Waiting for any of the currently-running steps to complete. The fol
    lowing steps are currently in progress: 'PhysicalMachineAndInitialConfiguration'. - 9/6/2017 10:56:44 AM
    STARTING: Step PhysicalMachineAndInitialConfiguration - Phase 0 - Configure physical machine and external netw
    orking
    VERBOSE: Step: Running step PhysicalMachineAndInitialConfiguration - Phase 0 - Configure physical machine and 
    external networking - 9/6/2017 10:56:44 AM
    VERBOSE: Creating action host for action Deployment-Phase0-DeployBareMetalAndBGPAndNAT. - 9/6/2017 10:56:44 AM
    VERBOSE: Found the role 'Cloud' in the current configuration. - 9/6/2017 10:56:44 AM
    VERBOSE: Creating action host for action Deployment-Phase0-DeployBareMetalAndBGPAndNAT. - 9/6/2017 10:56:44 AM
    VERBOSE: Action host for action Deployment-Phase0-DeployBareMetalAndBGPAndNAT has been created. - 9/6/2017 10:
    56:44 AM
    VERBOSE: Add the expanded nested action plan to the actionTask definition for Cloud - Deployment-Phase0-Deploy
    BareMetalAndBGPAndNAT. - 9/6/2017 10:56:44 AM
    STARTING: Task Cloud - Deployment-Phase0-DeployBareMetalAndBGPAndNAT
    VERBOSE: Task: Running action type 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' of role 'Cloud'. - 9/6/2017
     10:56:44 AM
    VERBOSE: Action: Running action Deployment-Phase0-DeployBareMetalAndBGPAndNAT. - 9/6/2017 10:56:44 AM
    STARTING: Action 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT'
    VERBOSE: Action: Running action plan 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT'. - 9/6/2017 10:56:44 AM
    VERBOSE: Skipping step '(DEP) Generate base images for hosts and virtual machines.' with Id 'PhysicalMachineAn
    dInitialConfiguration.10' because it was specified as a skip parameter. - 9/6/2017 10:56:44 AM
    VERBOSE: Skipping step '(DEP) Update Local Host Deployment Artifacts' with Id 'PhysicalMachineAndInitialConfig
    uration.11' because it was specified as a skip parameter. - 9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.10' is 2000. - 
    9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.11' is 1900. - 
    9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.12' is 1800. - 
    9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.13' is 1700. - 
    9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.14' is 1600. - 
    9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.15' is 1500. - 
    9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.16' is 1400. - 
    9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.17' is 1300. - 
    9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.ConfigurePhysic
    alMachines' is 1200. - 9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.18' is 1100. - 
    9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.19' is 1000. - 
    9/6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.20' is 900. - 9
    /6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.21' is 800. - 9
    /6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.22' is 700. - 9
    /6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.23' is 600. - 9
    /6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.24' is 500. - 9
    /6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.25' is 400. - 9
    /6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.26' is 300. - 9
    /6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.27' is 200. - 9
    /6/2017 10:56:44 AM
    VERBOSE: Total time until the end of the plan for step 'PhysicalMachineAndInitialConfiguration.28' is 100. - 9
    /6/2017 10:56:44 AM
    VERBOSE: The following steps are currently ready: PhysicalMachineAndInitialConfiguration.10. - 9/6/2017 10:56:
    44 AM
    VERBOSE: Processing step: PhysicalMachineAndInitialConfiguration.10. - 9/6/2017 10:56:44 AM
    VERBOSE: Skipping step '(DEP) Generate base images for hosts and virtual machines.' with id 'PhysicalMachineAn
    dInitialConfiguration.10' because it was specified to be skipped or is outside the specified bounds. - 9/6/201
    7 10:56:44 AM
    STARTING: Step PhysicalMachineAndInitialConfiguration.10 - (DEP) Generate base images for hosts and virtual ma
    chines.
    VERBOSE: Step: Skipping step PhysicalMachineAndInitialConfiguration.10 - (DEP) Generate base images for hosts 
    and virtual machines. - 9/6/2017 10:56:44 AM
    COMPLETE: Step PhysicalMachineAndInitialConfiguration.10 - (DEP) Generate base images for hosts and virtual ma
    chines.
    VERBOSE: The following steps are currently ready: PhysicalMachineAndInitialConfiguration.11. - 9/6/2017 10:56:
    44 AM
    VERBOSE: Processing step: PhysicalMachineAndInitialConfiguration.11. - 9/6/2017 10:56:44 AM
    VERBOSE: Skipping step '(DEP) Update Local Host Deployment Artifacts' with id 'PhysicalMachineAndInitialConfig
    uration.11' because it was specified to be skipped or is outside the specified bounds. - 9/6/2017 10:56:44 AM
    STARTING: Step PhysicalMachineAndInitialConfiguration.11 - (DEP) Update Local Host Deployment Artifacts
    VERBOSE: Step: Skipping step PhysicalMachineAndInitialConfiguration.11 - (DEP) Update Local Host Deployment Ar
    tifacts - 9/6/2017 10:56:44 AM
    COMPLETE: Step PhysicalMachineAndInitialConfiguration.11 - (DEP) Update Local Host Deployment Artifacts
    VERBOSE: The following steps are currently ready: PhysicalMachineAndInitialConfiguration.12. - 9/6/2017 10:56:
    44 AM
    VERBOSE: Processing step: PhysicalMachineAndInitialConfiguration.12. - 9/6/2017 10:56:44 AM
    VERBOSE: Executing step: PhysicalMachineAndInitialConfiguration.12. - 9/6/2017 10:56:44 AM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently in progress:
     'PhysicalMachineAndInitialConfiguration.12'. - 9/6/2017 10:56:44 AM
    VERBOSE: The following steps are currently ready: . - 9/6/2017 10:56:44 AM
    VERBOSE: No steps are ready for execution. Waiting for any of the currently-running steps to complete. The fol
    lowing steps are currently in progress: 'PhysicalMachineAndInitialConfiguration.12'. - 9/6/2017 10:56:44 AM
    STARTING: Step PhysicalMachineAndInitialConfiguration.12 - (DEP) Validate Physical Machines
    VERBOSE: Step: Running step PhysicalMachineAndInitialConfiguration.12 - (DEP) Validate Physical Machines - 9/6
    /2017 10:56:44 AM
    VERBOSE: Task: Running interface 'Validate' of role 'Cloud\Infrastructure\BareMetal'. Attempt #1.  - 9/6/2017 
    10:56:44 AM
    STARTING: Task Cloud\Infrastructure\BareMetal - Validate
    VERBOSE: Interface: Path to module: C:\CloudDeployment\Classes\BareMetal\BareMetal.psm1 - 9/6/2017 10:56:44 AM
    VERBOSE: Interface: Running interface Validate (Classes\BareMetal\BareMetal.psm1, BareMetal:Validate) - 9/6/20
    17 10:56:44 AM
    VERBOSE: [BareMetal:Validate] Set-MacAndIPAddress: BEGIN on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10
    :57:21 AM
    VERBOSE: [BareMetal:Validate] Setting IP addresses. - 9/6/2017 10:57:21 AM
    VERBOSE: [BareMetal:Validate] Normalizing MAC address '00-30-48-FF-D8-63'. - 9/6/2017 10:57:21 AM
    VERBOSE: [BareMetal:Validate] Choosing an address from 'Management' in range '192.168.200.65/24'. - 9/6/2017 1
    0:57:21 AM
    VERBOSE: [BareMetal:Validate] Set-MacAndIPAddress: END on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10:5
    7:21 AM
    VERBOSE: [BareMetal:Validate] Get-NetworkMap: BEGIN on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10:57:2
    1 AM
    VERBOSE: [BareMetal:Validate] Get Network Map for nodes AZUREBOX1 - 9/6/2017 10:57:21 AM
    VERBOSE: [BareMetal:Validate] Test-NetworkMap: BEGIN on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10:57:
    22 AM
    VERBOSE: [BareMetal:Validate] Find out which NICs are able to connect on each node. - 9/6/2017 10:57:22 AM
    WARNING: [BareMetal:Validate] Ping to 192.168.100.4 failed -- Status: TimedOut - 9/6/2017 10:57:28 AM
    VERBOSE: [BareMetal:Validate] - AZUREBOX1 | Storage1 - 9/6/2017 10:57:45 AM
    VERBOSE: [BareMetal:Validate] + AZUREBOX1 | Deployment - 9/6/2017 10:57:49 AM
    WARNING: [BareMetal:Validate] Ping to 192.168.200.65 failed -- Status: TimedOut - 9/6/2017 10:57:54 AM
    VERBOSE: [BareMetal:Validate] - AZUREBOX1 | Management - 9/6/2017 10:58:04 AM
    VERBOSE: [BareMetal:Validate] Test-NetworkMap: END on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10:58:04
     AM
    VERBOSE: [BareMetal:Validate] Get-NetworkMap: END on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10:58:04 
    AM
    VERBOSE: [BareMetal:Validate] Starting validation test for Role 'BareMetal' on machine 'AZUREBOX1' - 9/6/2017 
    10:58:04 AM
    VERBOSE: [BareMetal:Validate] Querying machine information for machine AZUREBOX1 with address localhost - 9/6/
    2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] Querying Win32_ComputerSystem. - 9/6/2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] Manufacturer reported by Win32_ComputerSystem is Supermicro - 9/6/2017 10:58:11 
    AM
    VERBOSE: [BareMetal:Validate] Total physical memory is 274705584128 - 9/6/2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] PartOfDomain is False - 9/6/2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] Querying Win32_OperatingSystem. - 9/6/2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] OS version is 10.0.14393 - 9/6/2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] OS SKU is 8 - 9/6/2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] DataExecutionPreventionAvailable is True - 9/6/2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] Querying Win32_Service. - 9/6/2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] Hyper-V service was found. - 9/6/2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] State of Hyper-V service is Running - 9/6/2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] Querying processor information. - 9/6/2017 10:58:11 AM
    VERBOSE: [BareMetal:Validate] Found processors with the following properties: - 9/6/2017 10:58:16 AM
    VERBOSE: [BareMetal:Validate] 
    NumberOfEnabledCores HasVMMonitorModeExtensions IsVirtualizationEnabled SupportsSecondLevelAddressTranslation
    -------------------- -------------------------- ----------------------- -------------------------------------
                       1                      False                   False                                 False
                       1                      False                   False                                 False
                       1                      False                   False                                 False
                       1                      False                   False                                 False
    
    
     - 9/6/2017 10:58:16 AM
    VERBOSE: [BareMetal:Validate] Querying disk information. - 9/6/2017 10:58:16 AM
    VERBOSE: [BareMetal:Validate] Found system disk with the following properties: - 9/6/2017 10:58:22 AM
    VERBOSE: [BareMetal:Validate] 
    
    FriendlyName            : 
    SerialNumber            : 
    BusType                 : RAID
    DeviceId                : 
    Manufacturer            : 
    Model                   : 
    MediaType               : 
    HealthStatus            : 
    Size                    : 999653638144
    FirmwareVersion         : 
    IndexWithinSimilarDisks : 0
    
    
    
     - 9/6/2017 10:58:22 AM
    VERBOSE: [BareMetal:Validate] Found non-system disks with the following properties: - 9/6/2017 10:58:22 AM
    VERBOSE: [BareMetal:Validate] 
    
    FriendlyName            : Msft Virtual Disk
    SerialNumber            : 
    BusType                 : File Backed Virtual
    DeviceId                : 8
    Manufacturer            : Msft
    Model                   : Virtual Disk
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 128849018880
    FirmwareVersion         : 1.0
    IndexWithinSimilarDisks : 0
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00e87771180ceb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 1
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 0
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 003d00bd1811eb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 7
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 1
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00e7f585180eeb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 3
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 2
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00ba067b180deb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 2
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 3
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00a85fad1810eb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 6
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 4
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00e8ed91180eeb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 4
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 5
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 006e0c9f180feb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 5
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 6
    
    
    
     - 9/6/2017 10:58:22 AM
    VERBOSE: [BareMetal:Validate] Querying BIOS information. - 9/6/2017 10:58:22 AM
    VERBOSE: [BareMetal:Validate] Querying OEM driver information. - 9/6/2017 10:58:22 AM
    VERBOSE: [BareMetal:Validate] Querying network adapter information. - 9/6/2017 10:58:32 AM
    VERBOSE: [BareMetal:Validate] Found network adapters with the following properties: - 9/6/2017 10:58:32 AM
    VERBOSE: [BareMetal:Validate] 
         Speed IsRdmaEnabled Name      
         ----- ------------- ----      
    1000000000         False Ethernet 2
    
    
     - 9/6/2017 10:58:32 AM
    VERBOSE: [BareMetal:Validate] Completed querying machine information for machine AZUREBOX1 with address Physic
    alMachine - 9/6/2017 10:58:32 AM
    VERBOSE: [BareMetal:Validate] Saving host hardware inventory information at [C:\CloudDeployment\Logs\HostHardw
    areLogs\HostHardwareInventory.json]... - 9/6/2017 10:58:32 AM
    VERBOSE: [BareMetal:Validate] Hardware information for Deployment 80b482ca-fb71-4e6c-b894-2a1d936a799c has bee
    n emitted. - 9/6/2017 10:58:33 AM
    VERBOSE: [BareMetal:Validate] The Hyper-V service is running on physical machine . There is no need to check f
    or virtualization support on this machine. - 9/6/2017 10:58:33 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'MachineNameToIPAddress' should not be null or empty
    . - 9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'Credential' should not be null or empty. - 9/6/2017
     10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'Topology' should not be null or empty. - 9/6/2017 1
    0:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'PhysicalMachinesRole' should not be null or empty. 
    - 9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'DeploymentGuid' should not be null or empty. - 9/6/
    2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that parameters are specified correctly in CustomerConfig.
    xml. - 9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that exactly one physical computer is used. - 9/6/2017 10:
    58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that deployment is running on the physical machine that is
     specified in deployment manifest. - 9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test Connection on machine 'AZUREBOX1' - 9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve computer system information from computer 'AZUREBOX1'. - 9
    /6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve operating system information from computer 'AZUREBOX1'. - 
    9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Check if the Hyper-V service is running on computer 'AZUREBOX1'. - 
    9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve processor information from computer 'AZUREBOX1'. - 9/6/201
    7 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve disk information from computer 'AZUREBOX1'. - 9/6/2017 10:
    58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve BIOS information from computer 'AZUREBOX1'. - 9/6/2017 10:
    58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve OEM driver information from computer 'AZUREBOX1'. - 9/6/20
    17 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve network adapter information from computer 'AZUREBOX1'. - 9
    /6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the computer '' is a physical machine. - 9/6/2017 10:
    58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the operating system version on computer '' meets the
     minimum required version. - 9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the operating system on computer 'AZUREBOX1' is Windo
    ws Server 2016 Datacenter. - 9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the computer name 'AZUREBOX1' is not 'AzureStack', wh
    ich is the name of the domain to be created. - 9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the computer 'AZUREBOX1' is not currently joined to a
     domain. - 9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that at least 96 GB of physical memory is available in com
    puter . - 9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the system disk on computer  is of size 180 GB or lar
    ger. - 9/6/2017 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that at least 3 data disk(s) with a size of at least 135 G
    B are available in computer . - 9/6/2017 10:58:36 AM
    WARNING: Task: Invocation of interface 'Validate' of role 'Cloud\Infrastructure\BareMetal' failed: 
    
    Type 'Validate' of Role 'BareMetal' raised an exception:
    
    One or more validation test failed for Role 'BareMetal' on machine 'AZUREBOX1'
    For detailed test results look at file '\\AZUREBOX1\C$\CloudDeployment\Logs\Tests\TestResults_AZUREBOX1_BareMe
    tal_22d3_2017-09-06-10-58-04.xml'
    Test Failed: Validate that at least 12 cores are available in computer .
    Command            Arguments                                                                                  
              
    -------            ---------                                                                                  
              
    Start-Test         {Parameters=CloudEngine.Configurations.EceInterfaceParameters, Script=System.Collections.Ha
    shtable}  
    Test-BareMetalRole {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=Tr
    ue}       
                       {}                                                                                         
              
    <ScriptBlock>      {CloudEngine.Configurations.EceInterfaceParameters}                                        
              
    <ScriptBlock>      {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters
    , 00000...
    
    
    
    at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 59
    at Start-Test, C:\CloudDeployment\Roles\Common\RoleHelpers.psm1: line 1382
    at Test-BareMetalRole, C:\CloudDeployment\Roles\PhysicalMachines\TestPhysicalMachines.psm1: line 89
    at Validate, C:\CloudDeployment\Classes\BareMetal\BareMetal.psm1: line 59
    at <ScriptBlock>, <No file>: line 18
    at <ScriptBlock>, <No file>: line 16 - 9/6/2017 10:58:36 AM
    WARNING: Task: Retrying interface 'Validate' of role 'Cloud\Infrastructure\BareMetal'... - 9/6/2017 10:58:36 A
    M
    VERBOSE: Task: Running interface 'Validate' of role 'Cloud\Infrastructure\BareMetal'. Attempt #2. (Retry 1 of 
    2.) - 9/6/2017 10:58:36 AM
    STARTING: Task Cloud\Infrastructure\BareMetal - Validate
    VERBOSE: Interface: Path to module: C:\CloudDeployment\Classes\BareMetal\BareMetal.psm1 - 9/6/2017 10:58:36 AM
    VERBOSE: Interface: Running interface Validate (Classes\BareMetal\BareMetal.psm1, BareMetal:Validate) - 9/6/20
    17 10:58:36 AM
    VERBOSE: [BareMetal:Validate] Set-MacAndIPAddress: BEGIN on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10
    :59:05 AM
    VERBOSE: [BareMetal:Validate] Setting IP addresses. - 9/6/2017 10:59:05 AM
    VERBOSE: [BareMetal:Validate] Normalizing MAC address '00-30-48-FF-D8-63'. - 9/6/2017 10:59:05 AM
    VERBOSE: [BareMetal:Validate] Choosing an address from 'Management' in range '192.168.200.65/24'. - 9/6/2017 1
    0:59:05 AM
    VERBOSE: [BareMetal:Validate] Set-MacAndIPAddress: END on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10:5
    9:05 AM
    VERBOSE: [BareMetal:Validate] Get-NetworkMap: BEGIN on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10:59:0
    5 AM
    VERBOSE: [BareMetal:Validate] Get Network Map for nodes AZUREBOX1 - 9/6/2017 10:59:05 AM
    VERBOSE: [BareMetal:Validate] Test-NetworkMap: BEGIN on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10:59:
    05 AM
    VERBOSE: [BareMetal:Validate] Find out which NICs are able to connect on each node. - 9/6/2017 10:59:05 AM
    WARNING: [BareMetal:Validate] Ping to 192.168.100.4 failed -- Status: TimedOut - 9/6/2017 10:59:12 AM
    VERBOSE: [BareMetal:Validate] - AZUREBOX1 | Storage1 - 9/6/2017 10:59:27 AM
    VERBOSE: [BareMetal:Validate] + AZUREBOX1 | Deployment - 9/6/2017 10:59:32 AM
    WARNING: [BareMetal:Validate] Ping to 192.168.200.65 failed -- Status: TimedOut - 9/6/2017 10:59:37 AM
    VERBOSE: [BareMetal:Validate] - AZUREBOX1 | Management - 9/6/2017 10:59:47 AM
    VERBOSE: [BareMetal:Validate] Test-NetworkMap: END on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10:59:47
     AM
    VERBOSE: [BareMetal:Validate] Get-NetworkMap: END on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 10:59:47 
    AM
    VERBOSE: [BareMetal:Validate] Starting validation test for Role 'BareMetal' on machine 'AZUREBOX1' - 9/6/2017 
    10:59:47 AM
    VERBOSE: [BareMetal:Validate] Querying machine information for machine AZUREBOX1 with address localhost - 9/6/
    2017 10:59:53 AM
    VERBOSE: [BareMetal:Validate] Querying Win32_ComputerSystem. - 9/6/2017 10:59:53 AM
    VERBOSE: [BareMetal:Validate] Manufacturer reported by Win32_ComputerSystem is Supermicro - 9/6/2017 10:59:53 
    AM
    VERBOSE: [BareMetal:Validate] Total physical memory is 274705584128 - 9/6/2017 10:59:53 AM
    VERBOSE: [BareMetal:Validate] PartOfDomain is False - 9/6/2017 10:59:53 AM
    VERBOSE: [BareMetal:Validate] Querying Win32_OperatingSystem. - 9/6/2017 10:59:53 AM
    VERBOSE: [BareMetal:Validate] OS version is 10.0.14393 - 9/6/2017 10:59:53 AM
    VERBOSE: [BareMetal:Validate] OS SKU is 8 - 9/6/2017 10:59:54 AM
    VERBOSE: [BareMetal:Validate] DataExecutionPreventionAvailable is True - 9/6/2017 10:59:54 AM
    VERBOSE: [BareMetal:Validate] Querying Win32_Service. - 9/6/2017 10:59:54 AM
    VERBOSE: [BareMetal:Validate] Hyper-V service was found. - 9/6/2017 10:59:54 AM
    VERBOSE: [BareMetal:Validate] State of Hyper-V service is Running - 9/6/2017 10:59:54 AM
    VERBOSE: [BareMetal:Validate] Querying processor information. - 9/6/2017 10:59:54 AM
    VERBOSE: [BareMetal:Validate] Found processors with the following properties: - 9/6/2017 10:59:58 AM
    VERBOSE: [BareMetal:Validate] 
    NumberOfEnabledCores HasVMMonitorModeExtensions IsVirtualizationEnabled SupportsSecondLevelAddressTranslation
    -------------------- -------------------------- ----------------------- -------------------------------------
                       1                      False                   False                                 False
                       1                      False                   False                                 False
                       1                      False                   False                                 False
                       1                      False                   False                                 False
    
    
     - 9/6/2017 10:59:58 AM
    VERBOSE: [BareMetal:Validate] Querying disk information. - 9/6/2017 10:59:58 AM
    VERBOSE: [BareMetal:Validate] Found system disk with the following properties: - 9/6/2017 11:00:03 AM
    VERBOSE: [BareMetal:Validate] 
    
    FriendlyName            : 
    SerialNumber            : 
    BusType                 : RAID
    DeviceId                : 
    Manufacturer            : 
    Model                   : 
    MediaType               : 
    HealthStatus            : 
    Size                    : 999653638144
    FirmwareVersion         : 
    IndexWithinSimilarDisks : 0
    
    
    
     - 9/6/2017 11:00:03 AM
    VERBOSE: [BareMetal:Validate] Found non-system disks with the following properties: - 9/6/2017 11:00:03 AM
    VERBOSE: [BareMetal:Validate] 
    
    FriendlyName            : Msft Virtual Disk
    SerialNumber            : 
    BusType                 : File Backed Virtual
    DeviceId                : 8
    Manufacturer            : Msft
    Model                   : Virtual Disk
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 128849018880
    FirmwareVersion         : 1.0
    IndexWithinSimilarDisks : 0
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00e87771180ceb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 1
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 0
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 003d00bd1811eb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 7
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 1
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00e7f585180eeb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 3
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 2
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00ba067b180deb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 2
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 3
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00a85fad1810eb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 6
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 4
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00e8ed91180eeb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 4
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 5
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 006e0c9f180feb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 5
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 6
    
    
    
     - 9/6/2017 11:00:03 AM
    VERBOSE: [BareMetal:Validate] Querying BIOS information. - 9/6/2017 11:00:03 AM
    VERBOSE: [BareMetal:Validate] Querying OEM driver information. - 9/6/2017 11:00:03 AM
    VERBOSE: [BareMetal:Validate] Querying network adapter information. - 9/6/2017 11:00:12 AM
    VERBOSE: [BareMetal:Validate] Found network adapters with the following properties: - 9/6/2017 11:00:12 AM
    VERBOSE: [BareMetal:Validate] 
         Speed IsRdmaEnabled Name      
         ----- ------------- ----      
    1000000000         False Ethernet 2
    
    
     - 9/6/2017 11:00:12 AM
    VERBOSE: [BareMetal:Validate] Completed querying machine information for machine AZUREBOX1 with address Physic
    alMachine - 9/6/2017 11:00:12 AM
    VERBOSE: [BareMetal:Validate] Saving host hardware inventory information at [C:\CloudDeployment\Logs\HostHardw
    areLogs\HostHardwareInventory.json]... - 9/6/2017 11:00:12 AM
    VERBOSE: [BareMetal:Validate] Hardware information for Deployment 80b482ca-fb71-4e6c-b894-2a1d936a799c has bee
    n emitted. - 9/6/2017 11:00:13 AM
    VERBOSE: [BareMetal:Validate] The Hyper-V service is running on physical machine . There is no need to check f
    or virtualization support on this machine. - 9/6/2017 11:00:13 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'MachineNameToIPAddress' should not be null or empty
    . - 9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'Credential' should not be null or empty. - 9/6/2017
     11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'Topology' should not be null or empty. - 9/6/2017 1
    1:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'PhysicalMachinesRole' should not be null or empty. 
    - 9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'DeploymentGuid' should not be null or empty. - 9/6/
    2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that parameters are specified correctly in CustomerConfig.
    xml. - 9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that exactly one physical computer is used. - 9/6/2017 11:
    00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that deployment is running on the physical machine that is
     specified in deployment manifest. - 9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test Connection on machine 'AZUREBOX1' - 9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve computer system information from computer 'AZUREBOX1'. - 9
    /6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve operating system information from computer 'AZUREBOX1'. - 
    9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Check if the Hyper-V service is running on computer 'AZUREBOX1'. - 
    9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve processor information from computer 'AZUREBOX1'. - 9/6/201
    7 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve disk information from computer 'AZUREBOX1'. - 9/6/2017 11:
    00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve BIOS information from computer 'AZUREBOX1'. - 9/6/2017 11:
    00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve OEM driver information from computer 'AZUREBOX1'. - 9/6/20
    17 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve network adapter information from computer 'AZUREBOX1'. - 9
    /6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the computer '' is a physical machine. - 9/6/2017 11:
    00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the operating system version on computer '' meets the
     minimum required version. - 9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the operating system on computer 'AZUREBOX1' is Windo
    ws Server 2016 Datacenter. - 9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the computer name 'AZUREBOX1' is not 'AzureStack', wh
    ich is the name of the domain to be created. - 9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the computer 'AZUREBOX1' is not currently joined to a
     domain. - 9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that at least 96 GB of physical memory is available in com
    puter . - 9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the system disk on computer  is of size 180 GB or lar
    ger. - 9/6/2017 11:00:15 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that at least 3 data disk(s) with a size of at least 135 G
    B are available in computer . - 9/6/2017 11:00:15 AM
    WARNING: Task: Invocation of interface 'Validate' of role 'Cloud\Infrastructure\BareMetal' failed: 
    
    Type 'Validate' of Role 'BareMetal' raised an exception:
    
    One or more validation test failed for Role 'BareMetal' on machine 'AZUREBOX1'
    For detailed test results look at file '\\AZUREBOX1\C$\CloudDeployment\Logs\Tests\TestResults_AZUREBOX1_BareMe
    tal_9607_2017-09-06-10-59-47.xml'
    Test Failed: Validate that at least 12 cores are available in computer .
    Command            Arguments                                                                                  
              
    -------            ---------                                                                                  
              
    Start-Test         {Parameters=CloudEngine.Configurations.EceInterfaceParameters, Script=System.Collections.Ha
    shtable}  
    Test-BareMetalRole {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=Tr
    ue}       
                       {}                                                                                         
              
    <ScriptBlock>      {CloudEngine.Configurations.EceInterfaceParameters}                                        
              
    <ScriptBlock>      {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters
    , 00000...
    
    
    
    at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 59
    at Start-Test, C:\CloudDeployment\Roles\Common\RoleHelpers.psm1: line 1382
    at Test-BareMetalRole, C:\CloudDeployment\Roles\PhysicalMachines\TestPhysicalMachines.psm1: line 89
    at Validate, C:\CloudDeployment\Classes\BareMetal\BareMetal.psm1: line 59
    at <ScriptBlock>, <No file>: line 18
    at <ScriptBlock>, <No file>: line 16 - 9/6/2017 11:00:16 AM
    WARNING: Task: Retrying interface 'Validate' of role 'Cloud\Infrastructure\BareMetal'... - 9/6/2017 11:00:16 A
    M
    VERBOSE: Task: Running interface 'Validate' of role 'Cloud\Infrastructure\BareMetal'. Attempt #3. (Retry 2 of 
    2.) - 9/6/2017 11:00:16 AM
    STARTING: Task Cloud\Infrastructure\BareMetal - Validate
    VERBOSE: Interface: Path to module: C:\CloudDeployment\Classes\BareMetal\BareMetal.psm1 - 9/6/2017 11:00:16 AM
    VERBOSE: Interface: Running interface Validate (Classes\BareMetal\BareMetal.psm1, BareMetal:Validate) - 9/6/20
    17 11:00:16 AM
    VERBOSE: [BareMetal:Validate] Set-MacAndIPAddress: BEGIN on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 11
    :00:42 AM
    VERBOSE: [BareMetal:Validate] Setting IP addresses. - 9/6/2017 11:00:42 AM
    VERBOSE: [BareMetal:Validate] Normalizing MAC address '00-30-48-FF-D8-63'. - 9/6/2017 11:00:42 AM
    VERBOSE: [BareMetal:Validate] Choosing an address from 'Management' in range '192.168.200.65/24'. - 9/6/2017 1
    1:00:42 AM
    VERBOSE: [BareMetal:Validate] Set-MacAndIPAddress: END on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 11:0
    0:42 AM
    VERBOSE: [BareMetal:Validate] Get-NetworkMap: BEGIN on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 11:00:4
    2 AM
    VERBOSE: [BareMetal:Validate] Get Network Map for nodes AZUREBOX1 - 9/6/2017 11:00:42 AM
    VERBOSE: [BareMetal:Validate] Test-NetworkMap: BEGIN on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 11:00:
    42 AM
    VERBOSE: [BareMetal:Validate] Find out which NICs are able to connect on each node. - 9/6/2017 11:00:42 AM
    WARNING: [BareMetal:Validate] Ping to 192.168.100.4 failed -- Status: TimedOut - 9/6/2017 11:00:48 AM
    VERBOSE: [BareMetal:Validate] - AZUREBOX1 | Storage1 - 9/6/2017 11:01:03 AM
    VERBOSE: [BareMetal:Validate] + AZUREBOX1 | Deployment - 9/6/2017 11:01:08 AM
    WARNING: [BareMetal:Validate] Ping to 192.168.200.65 failed -- Status: TimedOut - 9/6/2017 11:01:12 AM
    VERBOSE: [BareMetal:Validate] - AZUREBOX1 | Management - 9/6/2017 11:01:22 AM
    VERBOSE: [BareMetal:Validate] Test-NetworkMap: END on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 11:01:22
     AM
    VERBOSE: [BareMetal:Validate] Get-NetworkMap: END on AZUREBOX1 as AZUREBOX1\Administrator - 9/6/2017 11:01:22 
    AM
    VERBOSE: [BareMetal:Validate] Starting validation test for Role 'BareMetal' on machine 'AZUREBOX1' - 9/6/2017 
    11:01:22 AM
    VERBOSE: [BareMetal:Validate] Querying machine information for machine AZUREBOX1 with address localhost - 9/6/
    2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] Querying Win32_ComputerSystem. - 9/6/2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] Manufacturer reported by Win32_ComputerSystem is Supermicro - 9/6/2017 11:01:27 
    AM
    VERBOSE: [BareMetal:Validate] Total physical memory is 274705584128 - 9/6/2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] PartOfDomain is False - 9/6/2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] Querying Win32_OperatingSystem. - 9/6/2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] OS version is 10.0.14393 - 9/6/2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] OS SKU is 8 - 9/6/2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] DataExecutionPreventionAvailable is True - 9/6/2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] Querying Win32_Service. - 9/6/2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] Hyper-V service was found. - 9/6/2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] State of Hyper-V service is Running - 9/6/2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] Querying processor information. - 9/6/2017 11:01:27 AM
    VERBOSE: [BareMetal:Validate] Found processors with the following properties: - 9/6/2017 11:01:32 AM
    VERBOSE: [BareMetal:Validate] 
    NumberOfEnabledCores HasVMMonitorModeExtensions IsVirtualizationEnabled SupportsSecondLevelAddressTranslation
    -------------------- -------------------------- ----------------------- -------------------------------------
                       1                      False                   False                                 False
                       1                      False                   False                                 False
                       1                      False                   False                                 False
                       1                      False                   False                                 False
    
    
     - 9/6/2017 11:01:32 AM
    VERBOSE: [BareMetal:Validate] Querying disk information. - 9/6/2017 11:01:32 AM
    VERBOSE: [BareMetal:Validate] Found system disk with the following properties: - 9/6/2017 11:01:37 AM
    VERBOSE: [BareMetal:Validate] 
    
    FriendlyName            : 
    SerialNumber            : 
    BusType                 : RAID
    DeviceId                : 
    Manufacturer            : 
    Model                   : 
    MediaType               : 
    HealthStatus            : 
    Size                    : 999653638144
    FirmwareVersion         : 
    IndexWithinSimilarDisks : 0
    
    
    
     - 9/6/2017 11:01:37 AM
    VERBOSE: [BareMetal:Validate] Found non-system disks with the following properties: - 9/6/2017 11:01:37 AM
    VERBOSE: [BareMetal:Validate] 
    
    FriendlyName            : Msft Virtual Disk
    SerialNumber            : 
    BusType                 : File Backed Virtual
    DeviceId                : 8
    Manufacturer            : Msft
    Model                   : Virtual Disk
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 128849018880
    FirmwareVersion         : 1.0
    IndexWithinSimilarDisks : 0
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00e87771180ceb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 1
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 0
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 003d00bd1811eb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 7
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 1
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00e7f585180eeb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 3
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 2
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00ba067b180deb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 2
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 3
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00a85fad1810eb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 6
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 4
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 00e8ed91180eeb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 4
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 5
    
    FriendlyName            : LSI MR9280-16i4e
    SerialNumber            : 006e0c9f180feb3a21c0562900b26200
    BusType                 : RAID
    DeviceId                : 5
    Manufacturer            : LSI
    Model                   : MR9280-16i4e
    MediaType               : Unspecified
    HealthStatus            : Healthy
    Size                    : 999653638144
    FirmwareVersion         : 2.12
    IndexWithinSimilarDisks : 6
    
    
    
     - 9/6/2017 11:01:37 AM
    VERBOSE: [BareMetal:Validate] Querying BIOS information. - 9/6/2017 11:01:37 AM
    VERBOSE: [BareMetal:Validate] Querying OEM driver information. - 9/6/2017 11:01:37 AM
    VERBOSE: [BareMetal:Validate] Querying network adapter information. - 9/6/2017 11:01:45 AM
    VERBOSE: [BareMetal:Validate] Found network adapters with the following properties: - 9/6/2017 11:01:45 AM
    VERBOSE: [BareMetal:Validate] 
         Speed IsRdmaEnabled Name      
         ----- ------------- ----      
    1000000000         False Ethernet 2
    
    
     - 9/6/2017 11:01:45 AM
    VERBOSE: [BareMetal:Validate] Completed querying machine information for machine AZUREBOX1 with address Physic
    alMachine - 9/6/2017 11:01:45 AM
    VERBOSE: [BareMetal:Validate] Saving host hardware inventory information at [C:\CloudDeployment\Logs\HostHardw
    areLogs\HostHardwareInventory.json]... - 9/6/2017 11:01:45 AM
    VERBOSE: [BareMetal:Validate] Hardware information for Deployment 80b482ca-fb71-4e6c-b894-2a1d936a799c has bee
    n emitted. - 9/6/2017 11:01:46 AM
    VERBOSE: [BareMetal:Validate] The Hyper-V service is running on physical machine . There is no need to check f
    or virtualization support on this machine. - 9/6/2017 11:01:46 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'MachineNameToIPAddress' should not be null or empty
    . - 9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'Credential' should not be null or empty. - 9/6/2017
     11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'Topology' should not be null or empty. - 9/6/2017 1
    1:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'PhysicalMachinesRole' should not be null or empty. 
    - 9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test parameter 'DeploymentGuid' should not be null or empty. - 9/6/
    2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that parameters are specified correctly in CustomerConfig.
    xml. - 9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that exactly one physical computer is used. - 9/6/2017 11:
    01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that deployment is running on the physical machine that is
     specified in deployment manifest. - 9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Test Connection on machine 'AZUREBOX1' - 9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve computer system information from computer 'AZUREBOX1'. - 9
    /6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve operating system information from computer 'AZUREBOX1'. - 
    9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Check if the Hyper-V service is running on computer 'AZUREBOX1'. - 
    9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve processor information from computer 'AZUREBOX1'. - 9/6/201
    7 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve disk information from computer 'AZUREBOX1'. - 9/6/2017 11:
    01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve BIOS information from computer 'AZUREBOX1'. - 9/6/2017 11:
    01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve OEM driver information from computer 'AZUREBOX1'. - 9/6/20
    17 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Retrieve network adapter information from computer 'AZUREBOX1'. - 9
    /6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the computer '' is a physical machine. - 9/6/2017 11:
    01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the operating system version on computer '' meets the
     minimum required version. - 9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the operating system on computer 'AZUREBOX1' is Windo
    ws Server 2016 Datacenter. - 9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the computer name 'AZUREBOX1' is not 'AzureStack', wh
    ich is the name of the domain to be created. - 9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the computer 'AZUREBOX1' is not currently joined to a
     domain. - 9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that at least 96 GB of physical memory is available in com
    puter . - 9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that the system disk on computer  is of size 180 GB or lar
    ger. - 9/6/2017 11:01:49 AM
    VERBOSE: [BareMetal:Validate] Test Passed: Validate that at least 3 data disk(s) with a size of at least 135 G
    B are available in computer . - 9/6/2017 11:01:49 AM
    WARNING: Task: Invocation of interface 'Validate' of role 'Cloud\Infrastructure\BareMetal' failed: 
    
    Type 'Validate' of Role 'BareMetal' raised an exception:
    
    One or more validation test failed for Role 'BareMetal' on machine 'AZUREBOX1'
    For detailed test results look at file '\\AZUREBOX1\C$\CloudDeployment\Logs\Tests\TestResults_AZUREBOX1_BareMe
    tal_1a2c_2017-09-06-11-01-22.xml'
    Test Failed: Validate that at least 12 cores are available in computer .
    Command            Arguments                                                                                  
              
    -------            ---------                                                                                  
              
    Start-Test         {Parameters=CloudEngine.Configurations.EceInterfaceParameters, Script=System.Collections.Ha
    shtable}  
    Test-BareMetalRole {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=Tr
    ue}       
                       {}                                                                                         
              
    <ScriptBlock>      {CloudEngine.Configurations.EceInterfaceParameters}                                        
              
    <ScriptBlock>      {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters
    , 00000...
    
    
    
    at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 59
    at Start-Test, C:\CloudDeployment\Roles\Common\RoleHelpers.psm1: line 1382
    at Test-BareMetalRole, C:\CloudDeployment\Roles\PhysicalMachines\TestPhysicalMachines.psm1: line 89
    at Validate, C:\CloudDeployment\Classes\BareMetal\BareMetal.psm1: line 59
    at <ScriptBlock>, <No file>: line 18
    at <ScriptBlock>, <No file>: line 16 - 9/6/2017 11:01:49 AM
    Invoke-EceAction : Task: Invocation of interface 'Validate' of role 'Cloud\Infrastructure\BareMetal' failed: 
    Type 'Validate' of Role 'BareMetal' raised an exception:
    One or more validation test failed for Role 'BareMetal' on machine 'AZUREBOX1'
    For detailed test results look at file 
    '\\AZUREBOX1\C$\CloudDeployment\Logs\Tests\TestResults_AZUREBOX1_BareMetal_1a2c_2017-09-06-11-01-22.xml'
    Test Failed: Validate that at least 12 cores are available in computer .
    Command            Arguments                                                                                 
               
    -------            ---------                                                                                 
               
    Start-Test         {Parameters=CloudEngine.Configurations.EceInterfaceParameters, 
    Script=System.Collections.Hashtable}  
    Test-BareMetalRole {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, 
    Verbose=True}       
                       {}                                                                                        
               
    <ScriptBlock>      {CloudEngine.Configurations.EceInterfaceParameters}                                       
               
    <ScriptBlock>      {C:\CloudDeployment\CloudDeployment.psd1, 
    CloudEngine.Configurations.EceInterfaceParameters, 00000...
    at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 59
    at Start-Test, C:\CloudDeployment\Roles\Common\RoleHelpers.psm1: line 1382
    at Test-BareMetalRole, C:\CloudDeployment\Roles\PhysicalMachines\TestPhysicalMachines.psm1: line 89
    at Validate, C:\CloudDeployment\Classes\BareMetal\BareMetal.psm1: line 59
    at <ScriptBlock>, <No file>: line 18
    at <ScriptBlock>, <No file>: line 16 - 9/6/2017 11:01:49 AM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:579 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OperationStopped: (One or more val... 00000...
    :String) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : One or more validation test failed for Role 'BareMetal' on machine 'AZUREBOX1' 
       
        For detailed test results look at file '\\AZUREBOX1\C$\CloudDeployment\Logs\Tests\TestResults_AZUREBOX1_ 
       BareMetal_1a2c_2017-09-06-11-01-22.xml'
    Test Failed: Validate that at least 12 cores are available in computer .
        Command            Arguments                                                                             
                       
        -------            ---------                                                                             
                       
        Start-Test         {Parameters=CloudEngine.Configurations.EceInterfaceParameters, Script=System.Collecti 
       ons.Hashtable}  
        Test-BareMetalRole {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verb 
       ose=True}       
                           {}                                                                                    
                       
        <ScriptBlock>      {CloudEngine.Configurations.EceInterfaceParameters}                                   
                       
        <ScriptBlock>      {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceInterfacePara 
       meters, 00000...
    ,CloudEngine.Cmdlets.InvokeCmdlet
     
    VERBOSE: Step: Status of step 'PhysicalMachineAndInitialConfiguration.12 - (DEP) Validate Physical Machines' i
    s 'Error'. - 9/6/2017 11:01:49 AM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently in progress:
     'PhysicalMachineAndInitialConfiguration.12'. - 9/6/2017 11:01:49 AM
    VERBOSE: Action: Action plan 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' failed. Finish running all steps 
    that are currently in progress before exiting. - 9/6/2017 11:01:49 AM
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress or just comp
    leted: 'PhysicalMachineAndInitialConfiguration.12'. - 9/6/2017 11:01:49 AM
    VERBOSE: Action: Action plan 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' failed. - 9/6/2017 11:01:49 AM
    Invoke-EceAction : Action: Invocation of step PhysicalMachineAndInitialConfiguration.12 failed. Stopping 
    invocation of action plan. - 9/6/2017 11:01:49 AM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:579 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet
     
    VERBOSE: Action: Status of 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' is 'Error'. - 9/6/2017 11:01:49 AM
    COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetalAndBGPAndNAT
    VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' of role 'Cloud' is 'Error'. - 
    9/6/2017 11:01:49 AM
    VERBOSE: Step: Status of step 'PhysicalMachineAndInitialConfiguration - Phase 0 - Configure physical machine a
    nd external networking' is 'Error'. - 9/6/2017 11:01:49 AM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently in progress:
     'PhysicalMachineAndInitialConfiguration'. - 9/6/2017 11:01:49 AM
    VERBOSE: Action: Action plan 'Deployment' failed. Finish running all steps that are currently in progress befo
    re exiting. - 9/6/2017 11:01:49 AM
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress or just comp
    leted: 'PhysicalMachineAndInitialConfiguration'. - 9/6/2017 11:01:49 AM
    VERBOSE: Action: Action plan 'Deployment' failed. - 9/6/2017 11:01:49 AM
    Invoke-EceAction : Action: Invocation of step PhysicalMachineAndInitialConfiguration failed. Stopping 
    invocation of action plan. - 9/6/2017 11:01:49 AM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:579 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    If this helps I re-ran the command again so you could see everything and then finally the error.

    Thank you,

    -Sherwin

    Wednesday, September 6, 2017 3:06 PM
  • Hello Sherwin,

    There looks to be an issue with the asdk-installer prerequisite checker as the output shows your Baremetal server does meet or exceed all requirements.

     

    I'm working on reproducing your issue and will reply with a 'Workaround" or "Next Steps" ASAP. 

     

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

    If you continue experience any issues with ASDK release, feel free to contact us.

       

    PowerShell giving you the Blues? Try my Azure Stack PowerShell Helper scripts

    ASDK: Install/Import Azure Stack Modules 1.2.10 & AzureStack-Tools

    ASDK: Config PowerShell & set AdminStackAdmin/User ARM Endpoints

    ASDK: AzureStack Automation: Register ADFS ASDK for Azure Marketplace Syndication

    ASDK: AzureStack Automation: Register ASDK for Azure Marketplace Syndication

     

     Thanks,

     


    Gary Gallanes

    Thursday, September 7, 2017 5:51 PM
  • Thank you! I look forward to your reply, If you would like we could talk on the phone/skype if you want to poke around in the box itself.
    Thursday, September 7, 2017 8:04 PM
  • Hello Sherwin,

    Can you provide the output to \\AZUREBOX1\C$\CloudDeployment\Logs\Tests\TestResults_AZUREBOX1_
       BareMetal_1a2c_2017-09-06-11-01-22.xml'  

    I'm actually cutting a bug for this issue and working with my engineering team to provide you a workaround to get you deployed.  A quick Skype meeting could help speed things up. We may also need you to upload a log or two to help us track down the issue. For now, please email ascustfeedback@microsoft.com to get a Skype Meeting and or Workspace setup in case we needs some logs.   

    Make sure to use a Work, Organizational or Student address when contacting ascustfeedback@microsoft.com and include the thread URL in the subject. 

     

    We look forward to providing you a fix for this issue.   

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

    If you continue experience any issues with ASDK release, feel free to contact us.

        

     Thanks, 


    Gary Gallanes


    Thursday, September 7, 2017 11:21 PM
  • <?xml version="1.0" encoding="UTF-8"?>
    
    -<test-results time="11:01:48" date="2017-09-06" invalid="0" skipped="0" ignored="0" inconclusive="0" not-run="0" failures="1" errors="0" total="26" name="Pester" xsi:noNamespaceSchemaLocation="nunit_schema_2.5.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    
    <environment clr-version="4.0.30319.42000" os-version="10.0.14393" nunit-version="2.5.8.0" platform="Microsoft Windows Server 2016 Datacenter|C:\Windows|\Device\Harddisk8\Partition2" user-domain="AZUREBOX1" cwd="C:\Users\Administrator\Documents" machine-name="AZUREBOX1" user="Administrator"/>
    
    <culture-info current-uiculture="en-US" current-culture="en-US"/>
    
    
    -<test-suite time="22.126" name="Pester" asserts="0" success="False" result="Failure" executed="True" type="Powershell">
    
    
    -<results>
    
    
    -<test-suite time="22.126" name="Validate-Role" asserts="0" success="False" result="Failure" executed="True" type="TestFixture" description="Validate-Role">
    
    
    -<results>
    
    <test-case time="1.8253" name="Validate-Role.Test parameter 'MachineNameToIPAddress' should not be null or empty." asserts="0" success="True" result="Success" executed="True" description="Test parameter 'MachineNameToIPAddress' should not be null or empty."/>
    
    <test-case time="0.3079" name="Validate-Role.Test parameter 'Credential' should not be null or empty." asserts="0" success="True" result="Success" executed="True" description="Test parameter 'Credential' should not be null or empty."/>
    
    <test-case time="0.0737" name="Validate-Role.Test parameter 'Topology' should not be null or empty." asserts="0" success="True" result="Success" executed="True" description="Test parameter 'Topology' should not be null or empty."/>
    
    <test-case time="0.0489" name="Validate-Role.Test parameter 'PhysicalMachinesRole' should not be null or empty." asserts="0" success="True" result="Success" executed="True" description="Test parameter 'PhysicalMachinesRole' should not be null or empty."/>
    
    <test-case time="0.0327" name="Validate-Role.Test parameter 'DeploymentGuid' should not be null or empty." asserts="0" success="True" result="Success" executed="True" description="Test parameter 'DeploymentGuid' should not be null or empty."/>
    
    <test-case time="0.1103" name="Validate-Role.Validate that parameters are specified correctly in CustomerConfig.xml." asserts="0" success="True" result="Success" executed="True" description="Validate that parameters are specified correctly in CustomerConfig.xml."/>
    
    <test-case time="0.0619" name="Validate-Role.Validate that exactly one physical computer is used." asserts="0" success="True" result="Success" executed="True" description="Validate that exactly one physical computer is used."/>
    
    <test-case time="0.0353" name="Validate-Role.Validate that deployment is running on the physical machine that is specified in deployment manifest." asserts="0" success="True" result="Success" executed="True" description="Validate that deployment is running on the physical machine that is specified in deployment manifest."/>
    
    <test-case time="0.07" name="Validate-Role.Test Connection on machine 'AZUREBOX1'" asserts="0" success="True" result="Success" executed="True" description="Test Connection on machine 'AZUREBOX1'"/>
    
    <test-case time="0.1515" name="Validate-Role.Retrieve computer system information from computer 'AZUREBOX1'." asserts="0" success="True" result="Success" executed="True" description="Retrieve computer system information from computer 'AZUREBOX1'."/>
    
    <test-case time="0.1034" name="Validate-Role.Retrieve operating system information from computer 'AZUREBOX1'." asserts="0" success="True" result="Success" executed="True" description="Retrieve operating system information from computer 'AZUREBOX1'."/>
    
    <test-case time="0.1332" name="Validate-Role.Check if the Hyper-V service is running on computer 'AZUREBOX1'." asserts="0" success="True" result="Success" executed="True" description="Check if the Hyper-V service is running on computer 'AZUREBOX1'."/>
    
    <test-case time="4.3451" name="Validate-Role.Retrieve processor information from computer 'AZUREBOX1'." asserts="0" success="True" result="Success" executed="True" description="Retrieve processor information from computer 'AZUREBOX1'."/>
    
    <test-case time="5.5674" name="Validate-Role.Retrieve disk information from computer 'AZUREBOX1'." asserts="0" success="True" result="Success" executed="True" description="Retrieve disk information from computer 'AZUREBOX1'."/>
    
    <test-case time="0.0951" name="Validate-Role.Retrieve BIOS information from computer 'AZUREBOX1'." asserts="0" success="True" result="Success" executed="True" description="Retrieve BIOS information from computer 'AZUREBOX1'."/>
    
    <test-case time="7.3762" name="Validate-Role.Retrieve OEM driver information from computer 'AZUREBOX1'." asserts="0" success="True" result="Success" executed="True" description="Retrieve OEM driver information from computer 'AZUREBOX1'."/>
    
    <test-case time="0.2304" name="Validate-Role.Retrieve network adapter information from computer 'AZUREBOX1'." asserts="0" success="True" result="Success" executed="True" description="Retrieve network adapter information from computer 'AZUREBOX1'."/>
    
    <test-case time="0.7792" name="Validate-Role.Validate that the computer '' is a physical machine." asserts="0" success="True" result="Success" executed="True" description="Validate that the computer '' is a physical machine."/>
    
    <test-case time="0.0672" name="Validate-Role.Validate that the operating system version on computer '' meets the minimum required version." asserts="0" success="True" result="Success" executed="True" description="Validate that the operating system version on computer '' meets the minimum required version."/>
    
    <test-case time="0.0423" name="Validate-Role.Validate that the operating system on computer 'AZUREBOX1' is Windows Server 2016 Datacenter." asserts="0" success="True" result="Success" executed="True" description="Validate that the operating system on computer 'AZUREBOX1' is Windows Server 2016 Datacenter."/>
    
    <test-case time="0.0323" name="Validate-Role.Validate that the computer name 'AZUREBOX1' is not 'AzureStack', which is the name of the domain to be created." asserts="0" success="True" result="Success" executed="True" description="Validate that the computer name 'AZUREBOX1' is not 'AzureStack', which is the name of the domain to be created."/>
    
    <test-case time="0.0507" name="Validate-Role.Validate that the computer 'AZUREBOX1' is not currently joined to a domain." asserts="0" success="True" result="Success" executed="True" description="Validate that the computer 'AZUREBOX1' is not currently joined to a domain."/>
    
    
    -<test-case time="0.2076" name="Validate-Role.Validate that at least 12 cores are available in computer ." asserts="0" success="False" result="Failure" executed="True" description="Validate that at least 12 cores are available in computer .">
    
    
    -<failure>
    
    <message>Expected {4} to be greater than or equal to {12}</message>
    
    <stack-trace>at line: 598 in C:\CloudDeployment\Roles\PhysicalMachines\Tests\BareMetal.Tests.ps1 598: ($physicalMachine.Processors.NumberOfEnabledCores | Measure-Object -Sum).Sum | Should Not BeLessThan $minimumNumberOfCoresPerMachine </stack-trace>
    
    </failure>
    
    </test-case>
    
    <test-case time="0.2672" name="Validate-Role.Validate that at least 96 GB of physical memory is available in computer ." asserts="0" success="True" result="Success" executed="True" description="Validate that at least 96 GB of physical memory is available in computer ."/>
    
    <test-case time="0.031" name="Validate-Role.Validate that the system disk on computer is of size 180 GB or larger." asserts="0" success="True" result="Success" executed="True" description="Validate that the system disk on computer is of size 180 GB or larger."/>
    
    <test-case time="0.0801" name="Validate-Role.Validate that at least 3 data disk(s) with a size of at least 135 GB are available in computer ." asserts="0" success="True" result="Success" executed="True" description="Validate that at least 3 data disk(s) with a size of at least 135 GB are available in computer ."/>
    
    </results>
    
    </test-suite>
    
    </results>
    
    </test-suite>
    
    </test-results>

    Friday, September 8, 2017 3:18 PM
  • Unfortunately whitespace is removed - I have sent a message to ascustfeedback@microsoft.com
    Friday, September 8, 2017 3:21 PM
  • Hello Sherwin,

    We've tracked down the root cause and currently testing the workaround.  I'll respond via email and reply back to the thread when we have it ready.

     Thanks,


    Gary Gallanes

    Friday, September 8, 2017 5:39 PM
  • Hello Sherwin,

    When the deployment runs the CPU tests and totals the Number of Enabled Cores, it also checks for VM Monitor Mode Extensions, Virtualization enabled and supports Second Level Address Translation. 

     

    If any of the following are not found the deployment will Fail at the ‘CPU’ test stage.

     

    On your ASDK-Host:

    Enter into the BIOS setup and verify the above components are enabled and redeploy.

     

    If your deployment still fails running CPU validation, I’ve sent email with instructions on hacking the deployment script to skip CPU validation.

     

    Let us know how it goes.

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

    If you continue experience any issues with ASDK release, feel free to contact us.

       

    PowerShell giving you the Blues? Try my Azure Stack PowerShell Helper scripts

    ASDK: Install/Import Azure Stack Modules 1.2.10 & AzureStack-Tools

    ASDK: Config PowerShell & set AdminStackAdmin/User ARM Endpoints

    ASDK: AzureStack Automation: Register ADFS ASDK for Azure Marketplace Syndication

    ASDK: AzureStack Automation: Register ASDK for Azure Marketplace Syndication

     

     Thanks,


    Gary Gallanes

    Friday, September 8, 2017 10:43 PM
  • This didn't solve the issue I emailed your team but haven't received a response yet - could we set up a call to step through the issue? 

    Thursday, September 14, 2017 3:40 PM
  •  

    Hello Sherwin,

    I'm glad the fix you were provided got you past CPU validation. 

     

    I understand you are now getting a ‘Storage’ validation error even though your Baremetal server runs the Deployment Checker for Azure Stack successfully.

     

    Type 'Deployment' of Role 'Storage' raised an exception:

    On one-node setup, at least 3 disks are required. Actual number of available disks: 0

      

    We are currently analyzing the disk output you emailed us and look forward to working with you on Thursday 9/21/2017 @ 11:30 am PST. 

     

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

    If you continue experience any issues with ASDK release, feel free to contact us.

       

    PowerShell giving you the Blues? Try my Azure Stack PowerShell Helper scripts

    ASDK: Install/Import Azure Stack Modules 1.2.10 & AzureStack-Tools

    ASDK: Config PowerShell & set AdminStackAdmin/User ARM Endpoints

    ASDK: AzureStack Automation: Register ADFS ASDK for Azure Marketplace Syndication

    ASDK: AzureStack Automation: Register ASDK for Azure Marketplace Syndication

     

     Thanks,


    Gary Gallanes


    Tuesday, September 19, 2017 9:18 PM
  • Hi Gary,I am also facing the same issue with the script not detecting my processor properly. How do I send you my logs for analysis?

    As per coreinfo details:

    Intel(R) Xeon(R) CPU E7- 4830  @ 2.13GHz
    Intel64 Family 6 Model 47 Stepping 2, GenuineIntel
    Microcode signature: 00000037
    HYPERVISOR    -    Hypervisor is present
    VMX           *    Supports Intel hardware-assisted virtualization
    EPT           *    Supports Intel extended page tables (SLAT)

    Wednesday, September 26, 2018 9:25 AM
  • Wednesday, September 26, 2018 9:37 PM