Recent content by BadHellie

I found nowhere mentioned of any dependency of Backup and WFEP. As I said, by now the only way I found to get rid of this literal pack of bloats was deleting the WFEP update in the builtin updates list, to generate a new intermediate ISO as starting point (since update removals cannot be stored...

Ps. I sent him a message thru the apposite form, still no replies, I hope he received it...

I didn't know of that, thanks VM. But now that I have discovered the trick, I don't need it anymore... at least, NOT for this component ;)

UPDATE ! Actually, it turns out Remote Desktop IS WORKING even without Firewall and with the respective switch in Settings panel turned OFF !!! It was enough to set the two reg values as you suggested: reg add "HKLM\System\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t...

Thank you Garlin. So it turns out one really cannot remove the Windows Firewall for RDP to work. Oh well, I will restore it. Btw yes I can confirm, even here, there is no need to change anything in firewall config for RDP to work. On a fresh install with Firewall not removed, it is enough to...

Just to reply to the OP, it is my recent experience that removing the Firewall doesn't allow activation of the Remote Desktop, and likely nothing else (Internet works, file sharing works, everything else seems working BUT mine is a very streamlined ISO without OOBE, Store, a lot of M$ stuff...

Hi, I just wanted to report that I found Remote Desktop not working in my ISO, i.e it could not be enabled in the Settings (error message "Remote desktop is blocked by your firewall" plus "Open port 3389 to let Remote Desktop through your firewall"). In my ISO I had removed Windows Firewall and...

Thanks Garlin, very helpful !!!

Thanks Garlin, what a mess ! Oh you mean 'PM' Nuhi I suppose lol... surely I will Thanks for your explanation btw

I was talking in general. Since in the Updates page there is a menu to Remove every update, and since NTL pretty stores every operation in Presets except this one, I simply judged more logical that even any removal of builtin updates could be stored in a Preset. For example, I found the hard...

I got your points. My idea was simply to avoid maintaining too many separate files for a single project. The solution including all Registry tweaks inside an xml Preset would have resulted more "centralized" and compact, closer to how I would have done things. I understand the need of inspecting...

I think that it would be very convenient if NTL offered a list of Registry operations to integrate, which will be saved in the current preset. Such list will use the same format of standard .reg files (addition or deletion of keys or values). This way, one can avoid maintaining separate .reg...

I think it would be nice if any removal of builtin Updates could be stored in the current Preset, so one can avoid to repeat the same operation manually every time. Only if feasible and without side effects of course. Thanks.

Thanks, I wasn't aware of these details, I tried, it works magnificently :)

Oh I apologize. I read just now that passive files are simply deleted. Ignore this post.