![]() ![]() It has costs up front and annual maintenance costs, but there is little to no maintenance setting it up, they do the hard work when it comes to all the drivers. ![]() Your total time investment on each image is about 10 minutes. If you want SIMPLE when it comes to imaging, and I mean so simple you can have an intern do all your imaging, then I recommend Smart Deploy.Īfter you build your 1 image, you simply download the proper platform pack and then image the machine. Either imaging solution will work just fine on their own its working with their security environment that at issue. Just a thought, but what if you skip the PXE route and go with a USB boot to MDT? Would we hit the same roadblock? ![]() The OPs issue is NOT about imaging its about imaging with the port authentication enabled. That booting OS is not a member of AD and/or have an 802.1x supplicant. The same holds true for the MDT/WDS/WinPE environment. If its the latter then the iPXE / FOG environment can never boot because the booting system is not (at the instant that FOG boots) not a member of AD. Depending on how its setup, it can use just mac based authentication -or- mac and the target computer must be a member of AD -or- they are using an 802.1x supplicant. The issue here is with the port based authentication. FOG will allow you to add the target PC to AD during the inventory stage (I normally join/add after OOBE). OJKid wrote:I would have to disagree with that (not saying you are wrong, just saying I have not seen or heard before). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |