Already known and fixed in working branch. Likely 1.5.3 will release today or tomorrow and will contain this fix.
The times that I’ve hard of this the sata operation mode was setup as raid. From what I’m gathering, your sata operation mode is setup for AHCI? So I am really at a loss.
Similarly you could use the $osid variable which determines your OS implicitly rather than relying on the image name.
Assuming you name your images appropriately, you can use the $img variable to direct which files to copy for which image is being applied.
@xenorites please install the working branch. I was made aware of this and have since corrected it I believe.
Unsure how this is a bug.
Essentially the information is saying it cannot reach the destination. So it’s timing out. Not much I can do programmatically to fix this.
I’ve found this problem and have corrected it in the working branch. Thanks for reporting.
This would seem to indicate, to me, a potential hdd problem?
@Szeraax is correct. We do provide Snapin templates for both Powershell and Powershell 64 bit for this reason. Eventually when we allow the client to install as 64 bit on machines, then this problem won’t exist.
Powershell 64 bit
@irfan4701 - @sudburr is correct. Windows server 2012 is based on Windows 8 / is called Windows Server 8. Likewise, Windows server 2016 is based on Windows 10.
Looks like your connection to FOG Project was lost, please wait while we try to reconnect.