Search results

It seems being reproducable when having having aborted the application process of an image. Steps undertaken donwloaded W10 ISO unpacked ISO in a working directory (\working\w10_untouched) made a copy of that unpacked image \working\w10_untouched -> \working\w10_trimmed mounted that image...

host W10 Pro x_64 1909 b18363.693 target same as host NTL 1.9.0.7330 x_64 Home _____ picking one from the default pallete works however with a custom colour set (69797E) the installtion on the target turns up the standard/default OS blue.

As it just happened again unchecked "verify image files" in the settings and the image loaded, thus it appears related to that check. After rebooting the host the image would mount, with "verify image files" checked/enabled, thence the image would appear in order/ok. The overlay for that...

With an install on a clean (non-dual boot) target the OS got automatically activated (meantime NTL updated to version 1.9.0.7330) despite three auto activation settings to the contrary. But then the target machine been previously activated (and deactivated) and MS may just keep track of the...

added the /log option for the secedit command and the log got created, least the command ran, but the log file turned out empty and the local security template not been applied. I am still not certain whether %windir%\security\database\secedit.sdb is the right db to manipulate but from...

Should have paid better attention to the destination path for the *.pol files. After correction xcopy /Y %SystemDrive%\gpo\pol\u_registry.pol %systemroot%\System32\GroupPolicy\User\registry.pol* xcopy /Y %SystemDrive%\gpo\pol\m_registry.pol...

The issue only happens when the key is present in the Activation section, independent of whether the same key is present in the Setup section. The key is not generic but a real W8.1 retail key (that also works for W10) from my MS Technet subscription (back in the day). What is baffling is that...

I read that thread prior posting in this one. As stated I cannot reproduce it reliably as it just occurs intermittently. On such occasion checked whether more than NTL instance been running but it did not seem to be the case. Rebooted the host and the image directory for which the error...

With an install on a clean (non-dual boot) target the issue still exhibits (meantime NTL updated to version 1.9.0.7330). This seems some sort of bug.

No, Not present on the host.

Gave it another gowith xcopy /Y /I %SystemDrive%\tailor\del\gpo\pol\*.csv "%systemroot%\System32\GroupPolicy\Machine\Microsoft\Windows NT\Audit" xcopy /Y %SystemDrive%\gpo\pol\u_registry.pol %systemroot%\System32\User\registry.pol* xcopy /Y %SystemDrive%\gpo\pol\m_registry.pol...

host W10 Pro x_64 1909 b18363.657 target same as host NTL 1.9.0.7330 x_64 portable mode ______ Trying to deploy/migrate local security policy through Post-Setup with secedit /import /db %windir%\security\database\secedit.sdb /cfg %SystemDrive%\secpol\ba.inf does not pan out - as in once the...

Not sure what is causing this and how to reliably reproduce it, probably some unmount not completed or a previous mount being stuck somewhere, but occasionally being hit with the same issue on: host W10 Pro x_64 1909 b18363.657 NTL 1.9.0.7330 x_64 portable mode

Ah, I was not aware of the correlation between Exchange ActiveSync and that FOD package, though it is clearly mentioned here FOD ... And with Exchange ActiveSync locked from the compatibility settings for Office it makes sense that the FOD package shall remain.

There is a slight difference due to the design of GPEDIT.mmc since it does not actually queries/reads the registry keys/values but only sets/writes to it when changing a value and stores its settings in: %systemroot%\System32\GroupPolicy\User\registry.pol...

host W10 Pro x_64 1909 b18363.657 target same as host NTL 1.9.0.7330 x_64 portable mode ______ Whilst present in the Preset <Feature name="OneCoreUAP.OneSync~~~~0.0.1.0">false</Feature> the NTL UI showing it as set/enabled after having loaded such preset. Is that intended? Also having is...

host W10 Pro x_64 1909 b18363.657 target same as host NTL 1.9.0.7330 x_64 portable mode ______ Having deployed in Post-Setup move /Y "%SystemDrive%\gpo\pol\m\*.csv" "%WINDIR%\System32\GroupPolicy\Machine\Microsoft\Windows NT\Audit" move /Y "%SystemDrive%\\gpo\pol\u_registry.pol"...

for importing Wlan profiles I leverage forfiles /P %SystemDrive%\wlan /M *.xml /C "cmd /q /c netsh wlan add profile @path" but that imports the profiles for all users due to netsh defaulting to user=all but instead I would prefer user=current, e.g. forfiles /P %SystemDrive%\wlan /M *.xml /C...

Weird, even with no product key present in the unattended section and all auto activation been disabled the target still activated. Which might be contributed to the target (testing) being physically on the same machine (same hard drive, different partition) and thus presenting a dual boot...

In the ISO created by NTL the autounattend.xml is present only once, in the root, not sure whether it gets moved/copied during setup to %windir%\Panther or remains in %systemdrive%. Since the target (testing) is physically on the same machine (same hard drive, different partition) and thus...