alharaka

Anyone know how to skip the Windows install detection where that little pop-up in DaRT 6.5 (or previous NT6 versions) where is says "System Recovery Options" and you cannot exit out of it? Is there any shortcut to force it out? Can I permanently disable it by editing a startup script (startnet.cmd or other) in the DaRT wim after creating it in the wizard? Any pointers would be appreciated. Sometimes it is useful, other times it churns for hours without any way to stop it, and it just kicks off a program I can voluntarily execute later if I liked. If I am not clear, I mean the little window that pops up in front of this one in the picture, trying to populate this menu with info. .

Another eye-roll well-deserved of Windows. I was expecting this considering the docs tell you to contact your vendor. I love that since we know their tech support would not understand and then subsequently avoid escalating you.

Ok, ok. I know what the official unattended install documentation says (my bold emphasis added). So, are there any tools for an offline or online system analysis (like ProcessMontior or ProcessExplorer) to figure these things out? It must be associated with ShellNotifyIcon after all. Any thoughts/help? I know no one commented on the only other mention of this on MSFN, so I am thinking I am SOL.

Sorry to get to this topic late. If depends how you want to disable the GPO, from the admin/technician workstation side, which means disabling the GPO for every object to the OU it is applied in, or taking down one troublesome computer. We use link enabled GPO's, so this might be the clincher for you (and why you ought to use them). Check out this Technet document. As for the other way around, well, you do the equivalent of something I would do. I disconnect the computer from the network. I then remove the +H attribute off the %WinDir%\System32\GroupPolicy folder. Then, I just rename the folder, then run gpupdate /force. This obviously is a nasty kludge, but I often in my career had to quickly determine if GP was causing a configuration problem, an admin with button-mashing, a user, or a combo. This was a quick way to tell if GP was a culprit when I exhausted options. Might work for you, might not, and it is certainly not selective.