OSD via SCCM problem AOS 5.10

To image on AHV, you would need to have your wim have the virtIO drivers injected before trying to begin the imaging process so it can see storage. An older version of virtIO should be just fine, though I would confer with support before taking that as gospel.

1. What version of AOS are you using?
2. What version of AHV are you running?
3. What is the error message you're seeing?

The wim does have the virtIO version 1.1.4 drivers injected. I'm running AOS 5.10.1.1, AHV 20170830.185, and the error was just a generic error for the task sequence. On another note, how can I get to the sccm logs that get copied to the vm? (https://about:blank)

Click F8 when the task sequence fails to open up a command prompt navigate to the log you need and then use something like xcopy to move the log to where you need.


Windows PE
(Before the hard disk are formatted)
x:\windows\temp\smstslog\smsts.log

Windows PE
(After the hard disk are formatted)
x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

Windows Operating System
(Before the SCCM client is installed)
c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Windows Operating System

(After the SCCM client is installed)
c:\windows\ccm\logs\Smstslog\smsts.log
Windows Operating System

(When the Task Sequence is complete)
c:\windows\ccm\logs\smsts.log

Without knowing where or why or what the task sequence is trying to do at the moment of failure it's hard to say. If it successfully creates a disk and begins installing stuff, then I doubt this is a Nutanix issue, but more likely an issue with the task sequence itself. If you're unable to format a drive and start installing the OS, then it could be anything from an issue with imaging with EFI versus BIOS. A DHCP option issue not taking into account EFI options (talk to your network team if you're imaging with EFI as your boot option). If you've recently changed from BIOS to EFI, this would be more relevant. Unfortunately without more information, this could be a litany of things.

My go-to OSD troubleshooting steps:

• F8 to open command prompt
• ipconfig - verify drivers loaded for the NIC
• ping the management point and distribution point by DNS name - verifies upstream network connectivity and DNS resolution
• diskpart > list disk - verify drivers loaded for storage
• cmtrace - start digging through the smsts.log

As ddubuque mentioned, there is not much we can tell you without an actual error message, or what step during the task sequence it stopped, etc. You mention that the WIM has the VirtIO drivers, but does the boot image have the VirtIO drivers?

After looking into the logs the first error that comes across is "Partition 1 larger than remaining disk space. Requested partition size: 107374182400, remaining size: 85791741440". "Invalid configuration specified. Please ensure that the task sequence is properly configured. OSDDiskPart.exe failed: 0x8000ffff. Failed to run the action: Format and Partition Disk 6.1. Catastrophic fauilure (err0r: 8000FFFF; Source: Windows)

Yes, the boot image also has the VirtIO drivers as well.

Should the boot image only have the Nutanix VirtIO drivers? Total of only 3? I see a bunch of other VMware related drivers as well.