I use a BARE METAL PROFILE to deploy windows 10 x64 bits,
It’s working very well.
I’ve now tested it to deploy on targeted client.
If I need to remotely install a computer, I target is mac address, reboot it, press f2 and boot to network. The profile is going to be installed.
But now I have a question, I wan’t to deploy Windows 10 remotely on a computer without pressing the f12 key.
I know I can change the boot order, and make the pxe on first boot, But if i do that I will have the bigfix console asking to choose a profile to install.
My question is, are we able with bigfix to send a reboot to a computer, and ask him fo boot on pxe after the reboot ?
I ask this because I only have one computer who dont succeed. But If I don’t find a solution I will user a bare metal profile.
Sub-Action Status
Completed Validate Endpoint
Completed Download and Set up MDT Resource Files
Completed Download and Set up OS Resource Files
Completed Download and Set up WIM Image
Completed Create User State Migration Configuration File Waiting Tag Reimaged Computer
Waiting Determine Applicable Drivers
Waiting Download Applicable Drivers and Apply
Waiting Prepare custom settings configuration file
Waiting Initiate Reimage Action
The computer is grayed in the computer list, and If I restart besclient, the action failed.
I have a folder Deploy and MININT
But Deploy has only a Tools folder and MININT a SMSOSD
Is it possible that another action, not part of this baseline, started executing and left the client locked in some way?
Having a copy of the client logs from that time will be helpful. You should open a PMR with IBM as well so they can look at the details of your system.
Ok then so it got as far as “Initiate Reimage Action”. That’s where LiteTouch starts up and BigFix stops. It’s normal to see that error message, because part of what LiteTouch does is reboot the system, stopping the BES client mid-action.
LiteTouch is a part of Microsoft Deployment Toolkit, which is leveraged by BigFix to do the reimage process.
To see what’s going on with LiteTouch, you can check the logs at \MININT\SMSOSD\Logs, or open a PMR with support to check through the logs with you. These logs are in an XML format used by SCCM, it may be useful to find a copy of cmtrace.exe to parse them in a more readable format. cmtrace.exe is available as part of one of the SCCM management packs, but I don’t recall which.
There may also be useful logs at \Windows\Panther\UnattendGC, or \Windows\Temp\Deploymentlogs, or $WinNT.~BT\Panther\UnattendGC, depending on how far into Windows Setup the process made it before failing/rollback.
Yes the \MININT\SMSOSD\OSDLOGS will have duplication.
The “BDD.log” is a log of the whole process from start to end, while there will be separate logs for each subcomponent (Wizard, LiteTouch, Driver, etc.). If there are only BDD and Wizard logs, that implies it never got past the wizard.
I looked this morning on my baseline status and it has progressed…
Completed Validate Endpoint
Completed Download and Set up MDT Resource Files
Completed Download and Set up OS Resource Files
Completed Download and Set up WIM Image
Completed Create User State Migration Configuration File
Completed Tag Reimaged Computer
Completed Determine Applicable Drivers
Completed Download Applicable Drivers and Apply
Completed Prepare custom settings configuration file Failed Initiate Reimage Action
It failed at end of part1
Every line was completed except the last one : “Failed waithidden startLiteTouch.bat”
And I’ve looked on C:\Windows\Temp or Panther but the files are older. the only log files in windows that I found which has the same date as the baseline is setupact.log on windows folder.
Maybe I must try again and see what happen’s ? Because I’ve used this baseline today with on other computer and it has worked well…
I found in google that when setupact.log is in the windows folder it’s step is : (Windows Initializing Setup)
So Maybe it’s something wrong with a driver or something like this ?
