@davido38 FYI on that script - it will only remove the apps for the logged in user. There are two different AppX commands for removing from the current user’s profile and removing the app from the machine so it’s never reinstalled for any user.

Remove-AppXPackage = removes app for current user

Remove-AppXProvisionedPackage -Online = removing the app from the machine so it’s not reinstalled

I use these two commands before sysprepping:

Get-AppXPackage -AllUsers | Remove-AppXPackage
Get-AppXProvisionedPackage -Online | Remove-AppXProvisionedPackage -Online

@it_man The svn build is where you need to be if you want UEFI support. While uefi support was in 1.2.0 it worked marginally well (sporadic at best). There has been great efforts to get the uefi/gpt issues ironed out with the recent push of uefi only systems that just hit the market.

If you can tolerate a little instability the trunk has many new features you could take advantage of. If you detect a bug in the trunk build it is usually fixed in 2 days or less.

Quick update since we’re going into the weekend. Network team has confirmed the need for a IP helper to reach the separate VLAN. Will update further on Monday when the change is made. Thanks again for the assist @Wayne-Workman

We do that with a GPO. Even with groups from a trusted domain.

@Wayne-Workman I’m using Trunk, so the group policy method is perfect! Feel free to post the script for the older versions, if other people stumble across this thread.

@Arrowhead-IT Removing the IP_ was exactly the fix. My printer mapped successfully both ways, locally, and via my samba share. This is good stuff.

@apathetic_admin I’m not sure if this helps you or not but creating TCP/IP definitions has been successful for me. The Samba directions via the Wiki were pretty straight forward. I really didn’t like the idea of placing a ton of printer drivers locally on my “master” images, so the Samba share worked great.

Thank you both for the quick responses. 🙂 Very much appreciated.

@mr626 said:

Does the legacy client ‘know about’ these service configuration settings that are available per host in the trunk version’s web interface?

Yes.

Or do I need to update all of my hosts to the new client (which I will do eventually anyway of course)

You don’t have to upgrade to the new one, but I’d really strongly suggest that you do.

For enabling all services on all hosts, throw all your hosts into a group, and then use the group to enable all services on all hosts.

@Wayne-Workman Update. OK I have been able to test further. Capturing, deploying, and auto join to AD is working fine. Thank you everyone for all your help! This is a pretty powerful program. I am having printer setup issues, however I will either start another thread or jump in on an ongoing printer thread. You can set this thread as solved. 👍

@petergalgano et al, just about an hour ago I pushed an update based on a theory of the Windows 10 bcd not being compatible with the windows 7,8 and 8.1 OSs. The current inits in trunk will not attempt to replace the Windows 10 bcd as it has in the past. Please try updating and see if it helps. Also if you’re booting Windows 10 from UEFI, during up and down imaging please turn off secure boot. If the image is uploaded with secure boot on, it doesn’t matter anymore and will not work on any system but POSSIBLY the original uploading system and its not a strong possibly statement.

@jmeyer

Thanks jmeyer this works great!

Thanks all. That is an easy solution! 😃

@FlareImp Possibly the older iPXE version used in FOG 1.2.0 did not send DHCP option 97?!

http://ipxe.org/cfg/uuid (especially the last section ‘Notes’ is interesting I guess)

@elishasmantle said:

Is it possible, If I have all the images created and stored on a server to have it find a specific image to use for imaging that particular system?

I have written scripts that take advantage of the fog postinstall function that will use the OS utility dmidecode to pick up the model number of the target system and then deploy (push) the correct drivers to a known folder on the target computer. For this to work correctly you need to update your reference image before you sysprep to have windows look in this known folder (c:\Drivers) before it looks at the inf folder for the drivers. I have one image that supports 15 different models using this method (i.e. they are all Dell computers).

The only other caveat I have to say is you need to ensure that you have all required F6 boot drivers install on your reference image before you sysprep it. These drivers are required to boot the system, so there is no chance to pick them up from the disk since the drivers are required to connect to the disk.

here is what I use to pick up the Dell model number

machine=`dmidecode -s system-product-name | tr -cd '\60-\176'`;

And here is what I use to pick up the Intel NUC and Lenovo model numbers

machine=`dmidecode -s baseboard-product-name`;

I would recommend non-resizable as well, but if you can afford to, manually shrink the partitions.

As a part of the unattend file (I’m just guessing you’re using one) you can have the unattend set to expand the disk as needed. That would be another method though I don’t know how simple it is to do.

Good to hear!

Thanks for the help Sebastian. Yeah, I meant AHCI 🙂

I followed what some others suggested on the spiceworks forums and upgrading to the Trunk version. I made sure to factory reset my bios settings so it was uniform with my source computer (where I didn’t mess with anything) and it booted up! Everything works great and the windows key applied all by itself like it should. I’m a happy 🙂

Thanks!

@mrayzies said:

you must first have a KMS host running in your deployment

They are actually not too hard to setup. But the steps are easy to forget. I’ve only done it once.