@FlowLive Well you have touched on requests I’ve asked for… for a while.
- Being able to access host specific data during imaging.
- Having persistent groups.
They are on the developers request list, but not very high right now.
I think I almost have a hack for the persistent groups part figured out. I have a need to attach clients to specific OU based on their location. So I have a location for each site. I also have a requirement at each site to place workstations into different OUs based on the function of that device at the sites. So it is rather complex on how I need my OU structure setup. The static OU structure that FOG has is find for a single site, but falls down in a bit more complex environment.
I do have a path forward for me if I can’t get the persistent groups worked out.
Post image deployment FOG can be setup to run a bash script. With that bash script I determine the location of the deployed device based on its IP address and subnet. Also based on the image deployed I can tell the function of the device, so I can predict the OU where the device will reside. Through a little calculation I can build the proper OU for the device on the fly post image deployment. And with a short (but complex) sed function I can set the correct OU in the unattend.xml file on the target computer. When the computer goes through the oobe process upon setup it connects it self to the proper OU in AD. The only drawback I found is that if the device already exists in AD but in a different OU, winsetup will not move the device only reactivate its account. So I created a small vbs program (on the target that gets run during the first login process) that moves the computer to the proper OU. There is a lot of moving parts, but it does work well.
My point is there are ways to get done what needs to be if the system doesn’t support it out of the box. Do you have a unique key that you can use to calculate the proper OU for your target machines?