28 replies to this topic

[esgaroth]

I can map a network drive within win7rescuepe but not automatically using a profile in penetwork. I can also open penetwork and map a network drive manually.
Has anyone else used this to map a network drive? What does your penetwork.ini file look like? Here is mine:

[PENetwork]
UseProfileSelect=Yes
UseProfileCountdown=No
ProfileCountdown=0
ProfileDefault=profile.ini
[NetProfiles]
profile.ini=
[profile.ini]
StartSharing=
ShareAll=
NetPath=
NetDrv.Path1=\\desktop\shared
NetDrv.User1=696D6268
NetDrv.Pass1=
NetDrv.Letter1=S:
Desc.Line1=

[esgaroth]

So I take it that this feature isnt used often. Are there any other scripts or methods that I might use to automatically map a network drive?

[patsch]

I think it would be best to ask the author directly (that is Holger) in his thread:
http://www.boot-land...p?showtopic=976

[esgaroth]

I've already read through his thread. Someone had the same problem already and he did not have a solution for them. So I was more interested in finding out if anyone else has been using this successfully and finding out what their ini file looks like. Or any other scripts that would be able to map a network drive.

[pscEx]

Looks like you have a problem now:
You have to be a bit patient.

PENetwork is still in beta phase for the Win7 world.
And Holger currently has not so many time slots for WB development.

So, be happy, that you already can browse in the WEB, and do a lot of things manually, but for some other features, you have to wait until the beta becomes a RC or a released version.

Peter

[esgaroth]

I'm not being impatient, I'm just asking questions.

[pscEx]

I'm not being impatient, I'm just asking questions.

Peter

[esgaroth]

I figured out what was going wrong with penetwork in my build. So for those in the future who search for this thread here is what was going on.
I had created the profile through the profile manager and selected it to be copied instead of the default penetwork.ini. For some reason it was not being copied. No matter if I entered a relative path or the full path or the path beginning wiht %Basedir%. The default ini file in the attached penetwork.7z file would be copied instead.
So the workaround would be to replace the default penetwork.ini file with your own.

[rocketero]

I also have the same problem.

The PENetwork application inside the Win7PE works fine, I can map network drives and work with them in Explorer.

But the issue is that I would like to boot the PE machine and find the mapping already there so I don't have to do it manually every time I boot the machinePE.

I created a PENetwork Profile Prior to creating the ISO, with the PENetwork.script in the Winbuilder App by clicking on "START EDITOR" under the "Network Profiles" heading.

The profile is created and the mappings are placed in the PENetwork.ini file and I selected the only profile I crated as the "Default" Profile.

But when the PE machine boots the default profile is not 'applied', so basically I have to apply it but with the 'inconvenience' the the only thing that does NOT apply is the Network Drive Mappings and I have to painlessly recreated those mappings again.

Here is a look at my PENetwork.ini and the Profile called "CommonWork".

[PENetwork]
ProfileDefault=CommonWork
UseProfileSelect=No
UseProfileCountdown=No
ProfileCountdown=0

[NetProfiles]
CommonWork=

[Schemes]
Default=Silver
Scheme1=Dark
Scheme2=Silver

[CommonWork]
Computername=WIN7RESCUEME
Workgroup=WORKGROUP
NetAdapter1.UseDHCP=1
NetAdapter1.IP=
NetAdapter1.SM=
NetAdapter1.DG=
NetAdapter1.DNS=
NetAdapter1.WINS=
NetAdapter1.MAC=
StartSharing=
ShareAll=
NetPath=
NetDrv.Path1=\\QUEGA-PC\MYApps
NetDrv.User1=5053424F504D4D4724463850646756636461615B
NetDrv.Pass1=425F6F5D2C2C2C19
NetDrv.Letter1=E:
Desc.Line1=IP: By_DHCP
Desc.Line2=Computername: WIN7RESCUEME
Desc.Line3=Workgroup: WORKGROUP

[rocketero]

I have finally got success and the network is fully automated at boot up time, including local network mappings (only minor problem is that I can not map from local network machines to the Win7PE machine). I'm using WIN7PE in this case.

Here is a screen shot of the configuration of PENetwork, v.0.56
I created the penetwork.ini file by clicking on the button: START EDITOR

and here is the final result. (I was having problems before, and the change that fix my problem was selecting the box: "Use Profiles in PENetwork Start-up" and creating only one default profile.

one profile as default: (click on pic)

hope this helps, as it took me quite some ISO builds (around 25) to finally accomplish this result.

I don't know if anyone has been successful pinging from a local PC to the win7PE by computer name.
I can Not ping either by IP address or Computer Name. On the other direction (from Win7PE to Local Network PC) is OK pinging by Netbios/DNS Name and IP address.

Basically the Win-PE machine is not seen by the Local Network, it's like it doesn't exist. On the other hand the Win-PE machine can see all the network.

Other issue that I have read by other users is that the Network Icon on the desktop is practically useless as it does not show any Network machines and right-clicking on it to try to map a network drive is painful as the browse button does not show any local or domain machines.

[dera]

the browse button does not show any local or domain machines

try the PENetCfg

[rocketero]

try the PENetCfg

ACCESSING WIN7PE FROM OUTSIDE NETWORK

PENetCfg script as I reviewed it it's very basic, the lines that start with "RegWrite" are just a few and all of them are contained in the PENetwork script witch is 5 times bigger in code lines as PENetcfg is.

So I started with the same Win7PE build I had witch contains the PENetwork script, and added or Ran the PENetcfg.exe application after booting the PE machine.

As for you can see in the following screen-shot, the issue is related with "File Sharing" as there is not necessary services running to accomplish this. The "Network Location Awareness" is one of them and even that is setup to run automatically it's not running and if one try to start it it gives the error message as the pop-up located at the bottom of the screen.

The "File Sharing" in both: PENetwork and PENetcfg can not be started, and I guessing here it's due to the lack of the necessary Network services running in SERVICES.MSC Manager. The windows Firewall in the PE Machine is disabled so that it's not the problem.

But this issue only affects pinging from the Outside, as the PE machine works fine accessing the Internet and accessing files/directories/drives on the local network. I'm not sure if printers can be accessed as I have not tested it yet. (click image)

[dera]

i meant PENetCfg for discover shared folder on the network (browse network),
not 100% working,
for me in some case doesn't work,
in some case works fine (e.g. samba share)
screenshot penetcfg netdrives



for sharing local folder in the booted Win7PE\Win7RescuePE additional script needed

[wimb]

As for you can see in the following screen-shot, the issue is related with "File Sharing" as there is not necessary services running to accomplish this. The "Network Location Awareness" is one of them and even that is setup to run automatically it's not running and if one try to start it it gives the error message as the pop-up located at the bottom of the screen.

The "File Sharing" in both: PENetwork and PENetcfg can not be started, and I guessing here it's due to the lack of the necessary Network services running in SERVICES.MSC Manager. The windows Firewall in the PE Machine is disabled so that it's not the problem.

When using Make_PE3.cmd to make improved Windows PE 3.0 then File Sharing is available.
http://www.boot-land...?...=10250&st=7

It is possible to start the Lanman Server and Sharing of drives and folders with existing permission is possible.

Setting new permissions is not yet possible, which might be due to the fact that in my case also
it was not possible to start "Network Location Awareness" yet.

But gradually everything is improving .....

[rocketero]

I incorporated the "Sharing script" and now I can access the win7pe machine From outside another computer in the same local network as the win7pe machine. BUT I can access it only by IP address, not success yet by DNS/Netbios Name but still it's a great improvement. Before I could not even see the Win7PE machine from the local Network. Thanks for the "Sharing Script, it works in general thou still some minor issues.

Also if you see at the following screen-shot, the Yellow folders correspond to the "outside" Machine as I'm running the Win7PE in VMWare.

still there is not way to share individual Win7PE 'folders', Only the "Share All Drives" works. right-clicking on a Drive or Folder gives a context menu for 'share with" but the 'Advanced Sharing' button doesn't do anything).

[wimb]

@rocketero
Can you start now the "Network Location Awareness" Service ?

[dera]

for me both work
i can share individual folder
and i can access by Netbios Name
 S1.png   49.92KB   31 downloads
 S2.png   57.95KB   25 downloads
 S3.png   27.65KB   26 downloads
 S4.png   18.73KB   20 downloads

[dera]

do not know is there any meaning to do this
or is it worth or not
but currently the only way i can find to start the NlaSvc service
replace permission on the registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters
 nlasvc.png   143.32KB   38 downloads
 nlasvc2.png   81.58KB   30 downloads

[wimb]

@dera
Very good

Can you SET now new permissions for Sharing folders ?

Is Advanced Sharing button working ?

[dera]

No
Advanced Sharing button does not work

but fsmgmt.msc works
 fsmgmt.png   49.46KB   21 downloads

[rocketero]

No
Advanced Sharing button does not work

but fsmgmt.msc works
 fsmgmt.png   49.46KB   21 downloads

That is nice to see how to share a particular folder through the command line. One kinda forget to use them as many prefer using the GUI. In the 'Local Sharing' window right-clicking on the right and selecting 'New Share' from the menu will accomplish the same final Renault.

So Now Sharing Individual Folders does work using the command line, PENetwork window or the "Local Sharing" window in 'Computer Management'. When I was referring before was to sharing folders by using windows explorer witch is not supported.

But Something interesting I just realize is that for all this time I have not realized that the NLASVC (Network Location Awareness Service) was not started, it just shows as 'automatic' but was not started and even like that I was able to ping the win7pe machine from the outside and access the File shares in it.

After I saw your post I followed the registry editing and the NLASVC started with not problem. by the way, how did you figure out that adding the "NETWORK SERVICE" user was the right one (I am not sure if you had already that user in the list of permissions and just changed the final permissions or you added that user. In my case I added it because it was not listed), as I checked my Real Machine Running Windows 7 and that 'user' is not even listed. As for the list of permissions I did saw they were similar to the real win7.

Is there any way to adjust the "Sharing Script" to make it change the permissions on the "PARAMETERS" sub-key in the NLASVC key ?

And probably when the PENetwork v.6.0 comes out that scripting inside the Sharing script will be incorporated to it.

[dera]

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

[PaPeuser]

I was confused about a few things so I check it out

When you build Win7PE
If you have in 1-Copy Files script - Some recovery tools (requesting MS Win7 DVD) Checked
I found that when I open PENetCfg and
Set computer name
Set workgroup
File Sharing is already started in PENetCfg
Shared folders says all drives are shared
But Shared folders are not accessible across the network.
File Sharing does not work, Mapping of drives does work
I tried disabling Quest account and Firewall with deras script
Still did not work.

For me to use deras File Sharing script and PENetCfg
Uncheck (Some recovery tools (requesting MS Win7 DVD)) in 1-Copy Files script
Build - boot
Make sure net card is installed
Start PENetCfg
Set computer name
Set Workgroup
Disable Quest account – sharing script
Stop fire wall or disable - sharing script
Start, install LanmanServer – sharing script
Use Create a Share Folder wiz – sharing script
Start Sharing….

So to use deras Share files script
Do not have Some recovery tools (requesting MS Win7 DVD) checked

Mapping to any share on the network is possible
Share any file, folder or drive works in Win7PE

When TC/IP configuration is accessed thro Dart 6.5
IPv6 and IPv4 are Enabled
NetBIOS over TCPIP Enabled

Tested a with a few builds and I think I have this right

[dera]

to disable the 'guest' account needed only to get the pop-up dialog box ask for username and password on the remote computer,
maybe in different language the 'guest' called something else (e.g. in hungarian it is 'vendég'), beware the 'guest' is hardcoded in my shortcut,
on remote computer mapping the Win7PE share to drive letter using different credentials works even if the 'guest' account is active on the Win7PE

personally i prefer PENetwork over PENetCfg
(but for me this sharing script works also in the Win7PE project adding the 'Some recovery tools' too - and without including Holger's PENetwork script,
note: tcpipreg.sys and related reg entries need for PENetCfg)

really in some case there is problem with sharing using PENetCfg
in this case try to remove the shared folder, stop the LanmanServer service, initialize the network, install the service, start the service, define share

[PaPeuser]

Hello dera
Well it would be nice if PENetCfg and PENetwork got together some how
PeNetCfg browes the network
PENetwork has wireless support

It looks to me that yahoouk tried to auto start some network services with copy files and PEnetCfg
when the tool option is selected in the copy files, PENetCfg (should-would) start sharing right away

For me useing your shared files script will not work if CopyFile.script - Some recovery tools option is selected

because i start PENetCFG first it tries to start sharing and services and fails
if the CopyFiles - Some tools option is selected
then your script would fail also.

If Some recovery tools is not selected, then your tool and PENetCfg work fine,

This may work if i would use PENetwork first to start services when the Some recovery tools options is selected

I also wanted to Thank you again for the Shared files script
Yes there is alot to do to get shared to work, But sharing is not a everday need for me,, it is nice to have for some recovery

I am happy now and i wanted to point out what i found if someone else tries this.