Windows10 - 21H2 + Master + Fog
-
Hello,
Currently I have to make a Windows10 21H2 master image in a professional environment.
I have some strange problems:
-
1: The OEM key is recovered during the deployment of the image, but does not activate, obliged to put it back in manual and redo the synchro.
-
2: When integrating to the domain, the PC seems to be partially incorporated, it goes up well in the AD, it is possible to connect to it via a company user name, but the GPOs do not apply or only partially (they work perfectly on the Master W10 - 19041).
-
3: Once on the AD, if you remove the PC from the AD and then take it out and put it back on the domain, it does not reappear in the AD
Additional information:
-
The ISO 21H2 which is used as a basis for this Master is retrieved from our “Microsoft Volume Licensing Service Center” space (note that this was also tested on the Dell iso specific to the test machine).
-
The master is done via ADK “deployment tools” in automatic and custom method.
-
The AD is on a Windows Server 2019 version 1809
-
The deployment tool is “Fog Project” stable version 1.5.9
-
No Windows 10 specific ADM and ADMX templates have been added to the AD, the server is left in Windows update.
Any ideas on the possible cause(s) are welcome.
Thank you very much -
-
@M-Gene This is actually the second time we here about fundamental issue with AD joining but I am not really sure this is related. Please read through this topic carefully and let us know how much you think you are seeing the same issue or if it’s a different story: https://forums.fogproject.org/topic/15194/hostname-changer-ad-issues
Please check the fog.log file on the client and maybe post log output here as well so we can have a look too.
The fog-client software has not gotten much attention in the last years. First because there is not enough workforce in the FOG universe to do this but secondly also because not very many people actually report issues and stick around long enough to get things fixed and tested.
So if this is a fundamental problem with Windows 10 21H2 you might need to think about putting some money up to pay someone doing professional .NET coding to fix this issue or find someone else who can do it. We (as the FOG community) are more than happy to help to get this fixed but I can’t see us doing it on our own at the moment.
-
@m-gene As I read this, none of these issues are FOG related. So our input will be of little value.
- You state that you are using OEM keys but VLSC Media from the volume licensing center. If this is the case you will need to use MAK or KMS keys from the VLSC not OEM keys. OEM keys will not activate VLSC media.
- You need to review the event logs on the target computer to understand why GPOs are not applying. Also use the RSOP and gpresult command to see which GPOs are configured to apply.
- I have no clue about why when you remove and add a computer back in AD it doesn’t appear right away. You may have a slow replication scheduled in AD if you have multiple domain controllers.
If you are having Microsoft Windows issues you might want to query other forums that are specifically geared around the Microsoft ecosystem. From a FOG point of view the image is making it to the target computer and Windows is starting so FOG is out of the picture as a root cause of the problem.
-
@M-Gene What do you get in the fog-client log (
C:\fog.log)? We seem to have another user reporting an issue that sounds similar: https://forums.fogproject.org/topic/15978/windows-10-failing-to-join-domain -
@M-Gene We have evidence AD joining is working on Windows 10 21H2: https://forums.fogproject.org/topic/15978/windows-10-failing-to-join-domain
