Unable to name computer and join it to domain during post-deployment tasks
We are having an issue trying to do the naming and joining in our unattended.xml. See below: Beginning of XML: <?xml version="1.0" encoding="utf-8"?><unattend...
View ArticleRe: OS Provisioning on UEFI-Dell Latitude 5490/5590
Have you reviewed this document? Are you using ImageW or ImageX? https://community.ivanti.com/docs/DOC-69453
View ArticleRe: Unable to name computer and join it to domain during post-deployment tasks
Hi Mednax, first question, what is the exact issue you have...:-) Now to my suggestiobns; there are actions in the Pre-OS part, called "Device Name Prompter". How you can use this is described here:...
View ArticleRe: Unable to name computer and join it to domain during post-deployment tasks
Hi Christian, I appreciate your response. The exact issue we're having is that the computer will not name the one we give it, instead it's giving it a default name during sysprep. Also the computer...
View ArticleClik here to view.
Re: Unable to name computer and join it to domain during post-deployment tasks
And how did you Name the devices? With the naming action? Did you check the logs? Did you create a bare metal device, if so, the devicename should already be the correct one...Where did you set the...
View ArticleClik here to view.
Re: winpe usb type c network boot
Hi Nilay, I just discovered a curious thing with the Precision 5520 series. First, you have to activate the support for USB-C adaptors in the BIOS in the Thunderbolt section. This gives you TWO devices...
View ArticleRe: Unable to name computer and join it to domain during post-deployment tasks
HEy, in your unattend.xml is nothing mentioned about naming the device.We have this section<settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup"...
View ArticleClik here to view.
Re: Unable to name computer and join it to domain during post-deployment tasks
Thanks for the response. This is how we added it: Now we get the error: Windows could not parse or process unattend file for pass specialize. The answer file is invalid. Any help would be greatly...
View ArticleRe: Cannot Join Domain or install Agent in Windows 10
Common things that may help:Give the system some additional reboot(s) -- that tends to help flushing out any "PendingFileRename" type issues and some / certain drivers tend to work better that way.......
View ArticleClik here to view.
Re: Cannot Join Domain or install Agent in Windows 10
Have you solve this problem? We have the same behavior, but only on some computer models (Dell Precision T3600) using Windows 10 Pro 1803. Thanks! Edit:To be exact I do not have a domjoin problem - we...
View ArticleRe: Unable to name computer and join it to domain during post-deployment tasks
Your <settings pass="specialize"> is incomplete or even wrong. First there is a "-" before the <settings pass="specialize"> and the reference to the xml-Version (...
View ArticleClik here to view.
Re: Unable to name computer and join it to domain during post-deployment tasks
Hello, I appreciate your feedback on this one, but we are able to get it resolved.
View ArticleClik here to view.
Re: Dell Driver download
There is currently no way to limit HII Driver downloads for a specific OS in Patch Manager.
View ArticleClik here to view.
Re: ldprovison.exe This app can't run on your PC
The 32 vs 64 is the problem, I noticed that even when I was loading the wim64 the app was a 32 bit. I swapped the app for the 64 bit and then everything worked.Tnx.
View ArticleIvanti 2018.1 Bugs
I don't know where to report this as a bug, however, it is a pretty big one. So we use conditions (If/Else) to determine if software gets installed on a machine. What I have found is if you put one...
View ArticleRe: Ivanti 2018.1 Bugs
Hi Jared, When using operators to find bigger than or less than the provisioning template is expecting a purely numerical value, not a string value. It does not have the necessary logic to parse the...
View ArticleClik here to view.
Re: Ivanti 2018.1 Bugs
so then my confusion is if it is not designed to work that way, why is it even an option?
View ArticleSecond pass of HII
Are USB 3.0 drivers the only reason that a second pass of HII is necessary during the System Configuration phase of Provisioning? Will injecting USB 3 drivers into our WinPE boot image eliminate the...
View ArticleClik here to view.
Re: Second pass of HII
If WINPE has all of the drivers required to see all of the devices on the computer then you should not need to have a second HII action. The most common problem with this is WINPE is missing the USB...
View ArticleClik here to view.
Re: Second pass of HII
If you're mostly on Windows 10 you really don't need USB 3.0 drivers as they are built into Windows 10. For Windows 7 another work around I've used to get USB 3.0 drivers to work is to assign the...
View Article