28 replies to this topic

[dera]

in my build both included
also PENetCfg.exe and PENetwork.exe too
and seems there is no conflict with each other

because i start PENetCFG first it tries to start sharing and services and fails

yes, also for me seems the problem with sharing appears in that case when PENetCfg initialize the network and automatically wants to start sharing

i mean if i start PENetCfg simply double-clicking on PENetCfg.exe there is no problem - in this case sharing service is not started
(before i define shared folder i install the LanmanServer sercvice then start the LanmanServer sercvice via my shortcuts)

if i start PENetCfg via shortcut using 'PENetCfg.exe /useprofile:PENetCfg.ini' switch the problem appears
regardless of that in my profile.ini the startsharing is disabled
seems when PENetCfg apply a profile then always wants to start the LanmanServer sercvice too

[rocketero]

for me sharing and change permission on shared folder works fine even if the service 'NlaSvc' is not running

but you can try at your own risk:
try SetACL
(download 'SetACL Cmdline 2.0.3.0' from here)
copy SetACL.exe to the %Tools% folder: '\Projects\Tools\Win7RescuePE\'
try these WB script lines:

RegHiveLoad,wb-system,%RegSystem%ShellExecute,Hide,"%Tools%\SetACL.exe","-on #$qhklm\wb-system\ControlSet001\services\NlaSvc\Parameters#$q -ot reg -actn ace -ace #$qn:SERVICE;p:read_access,query_val,create_subkey,enum_subkeys,notify#$q"RegHiveUnLoad,wb-system

I also don't have a problem sharing and changing permissions on shared folders while NLASVC is not running. I probably brought this up before I applied the "Sharing Script" you wrote as I did not really know what was the problem.But now that you wrote that line of code with SETACL.exe to change permission on HKLM\SYSTEM\CURRENTCONTROLSET\SERVICES\NLASVC\PARAMETERS sub-key, I did run it while building another ISO but after booting the Win7PE and checked on the permissions on that sub-key, there were not changes, there was not a 'user' called SERVICE witch according for what I guessing is this code trying to do. But if the SETACL does not create objects inside the registry then I don't see how it can apply access rights to an object that doesn't exist yet. (I also checked under CONTROLSET001 and was the same)

The permissions on my registry show the following objects: CREATOR OWNER, SYSTEM, Administrators(local) and Users.
For what I have tested in order to be able to start this service, the objects: NETWORK SERVICE or SERVICE have to be present and with the rights you specified on the code.

Any how to do this?

[dera]

i have no idea what can be the problem

tried to build an x86 PE on x86 host
used the SetACL.exe from the 'setacl-cmdline-2.0.3.0-binary-x86.zip'
the above script lines works for me

[rocketero]

i have no idea what can be the problem

tried to build an x86 PE on x86 host
used the SetACL.exe from the 'setacl-cmdline-2.0.3.0-binary-x86.zip'
the above script lines works for me

I apologize for my Ignorance, the code works perfectly, what happens was that I didn't realize that the 1st and 3rd lines in your code were already in the PENetwork.script so I did not have to included them again.

After placing the 2nd line of code (the one with the SetACL), it worked !

thanks for the help.