Ivanti User Community: Message List - OS Deployment and Provisioning

My images are set up with OOBE. Do you use Device Name Prompter in your template?

I'm guessing in my case if a computer is not in Landesk already it ignores what I type into the Device name Prompter. actually it could be ignoreing it wether its in the Landesk database or not. When I reimage a computer that is in Landesk we always name it the same so if it ignores what I type in and uses the name already in the database I wouldn't know it.

Think i'll test that. We did not have this prior to upgrading to version 2016.3 which uses a different interface for Device Name prompter.

Just reimaged a computer that was already in Landesk database and named it something different and it took the new name.

I always delete computers out of the management console before I image them. I use the device name prompter and it inserts the correct name into the unattend and then injects it into the image. That's why I'm wondering about Windows only processing the oobe part of the unattend. I'm on the 2017 build of Endpoint manager.

Well I have found a nice little utility that seems t be doing the job well.

There are lot of updates to apply to a Server 2012 R2 base image and this tool seems to do a pretty good job of it.

Thanks for your suggestion.

Glad to hear you found a solution.

It's gotten worse now. HP EliteBook 850 G4 doesn't work at all Domain Accession. I tried all the tricks. It concerns only the latest models e. g. HP ProBook 650 G3, HP 400 G3.

Hey guys,

Just wondering how everyone else does their one touch computer imaging. I'm getting started with this and would like to get to the point where the base image is laid down, drivers, then packages installed, name machine, join domain, add user account, wifi, printers, etc etc. Been searching for a bit and not really seeing anything that points to these.

For the time being the OS is Windows 10 running on Dell Latitude hardware. Anyone have links or tips on where to start would be much appreciated!

Thanks,

Start with the following articles:

How to Provision Windows 10

How to capture a Windows 10 image using IMAGEW.EXE.

And go through the HOW TO documents below:

OS Deployment and Provisioning

So I recreated the image using then sysprepped using this command: Sysprep /generalize /oobe

It was based on this note: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/boot-windows-to-audit-mode-or-oobe

Note

If you install Windows images by using the Sysprep /generalize /oobe command, the user experience will not be ideal. On the next reboot after you run the Sysprep /generalize /oobe command, Windows runs the specialize configuration pass, Plug and Play, and other Setup tasks before Windows starts OOBE. This process can take additional time and can delay a customer's first logon.

I needed to make sure the specialize pass was processed, and this command facilitated that. Using the GUI didn't seem to do the same thing.

The entire article is here.

Boot Windows to Audit Mode or OOBE | Microsoft Docs

Hi,

I am running on weird situation I never saw before. The Windows PE is loaded successfully and the startnet.cmd script is running until it reaches the step "A subdirectory or file \ldprovision already exist". Normally the provisionin GUI should start now but it is not the case. It will take too much time (more than 10 minutes) before it is displayed and the problem is it shown no provisioning actions.

I made a dummy template on which I have added just 1 provisioning action which is wait(xx). and I tried on the same device and I got the same behavior. I deleted the device and import it again and I am still seeing the same weird behavior.

I don't think that it is a general problem since some other devices were able to finish successfully provisioning tasks!!

From the core server I checked the follwing log files :

provisioning.log

VERBOSE ProvisioningWebService 3/12/2018 11:12:07 AM : Identifiers to use - Mac Address: True, Serial Number: True, AMT GUID: True

VERBOSE ProvisioningWebService 3/12/2018 11:12:07 AM : Identifiers:

VERBOSE ProvisioningWebService 3/12/2018 11:12:07 AM : MACAddress: XXXXXXXXXXXX

VERBOSE ProvisioningWebService 3/12/2018 11:12:07 AM : SerialNumber: XXXXXXX

VERBOSE ProvisioningWebService 3/12/2018 11:12:08 AM : Returning task XML

TemplateFinder.log

DEBUGGING TemplateFinder 3/12/2018 11:12:07 AM : GetProvisioningTaskForComputer.computerIdn 11334

VERBOSE TemplateFinder 3/12/2018 11:12:07 AM : info.taskId 7255.info.templateId 226

==> since it is the right task ID and the right template ID I presume that the provisioing task (with the provisioning action wait(xx) was successfully retrieved by the core server).

From the client I can see that all prerequisite files were succesfully downloaded:

ldprovision.log

2018-03-12 20:12:28(1696-1704) ldProvision:Using [CORESERVER] for Core

2018-03-12 20:12:28(1696-1704) ldProvision:Getting server identifiers

2018-03-12 20:12:28(1696-1704) ldProvision:Getting BIOS Serial number by WMI.

2018-03-12 20:12:28(1696-1704) ldProvision:Serial Number by WMI: XXXXXXX

2018-03-12 20:12:28(1696-1704) ldProvision:Serial Number: XXXXXXX

2018-03-12 20:12:28(1696-1704) ldProvision:ldProvision started