Free MustangPE & Free Plugins For True Image Home 2011-2013 & Disk Director 11 Home
Let me try that real quick hold on...
I'll be.... it worked! The winpe_x86.iso is there, and stays there!!! ..till the end of PEBuilder and exit, it's still there.
Let me try this again....
Ran it through, at that Prompt manually deleted all .tmps except boot.wim of course, click next, the wimpe_x86.iso appears and stays!
Nice thought to try Paul, good one!
I would of thought they would have been locked or in use in some way.
This is a good development, that has implications and could mean...?
Just burned to USB and booted - working great with True Image, unlimited.
Good news!
I've uploaded a new version of CreateISO.zip. This version will delete the TMP files for you. If it works, I'll create a new version of MustangPEBuilder that will delete the TMP files and maybe the whole problem will be solved.
Let me test this new CreateISO hold on.
I've got the test bench computer booted to MPE2 at the moment just playing creating an image, but what's strange is instead of just taking 3 minutes to image a 30GB (27GB used thanks to fat ADK less so AIK) OS partition like is always has, it's taking like.... 15 minutes. I did Not check off to do a sector to sector so I don't understand why this is taking so long is my wondering at the moment. It's TIv11 on this test, but its standard bootdisk accomplishes the task in 3 minutes. I'll check your ADK version of this same plugin later to see if it's the same time test.
..just give me a few minutes till it finishes and I'll test CreateISO and come back and edit this post.
edit:
You are one talented person Paul, nice job, it works, it deleted all the temps and put the winpe_x86.iso in the iso folder and it stays there even till exit. Maybe MS should hire you!
I uploaded a new version of debug MustangPEBuilder.zip to http://www.mechrest.com/plugins/MustangPEBuilder/Downloads/Files/Mustan… . It still has the pauses, but you shouldn't need to do anything but click OK at each pause. Let me know if it works.
Okay got it, give me a few and I'll be back...
It worked Perfectly !
OK, download MustangPEBuilder.zip again from the link in post #205. The pauses have been removed and it should be a final version for you that works as intended.
(I hope this can be a final version for Everyone and not just me though, out of the everyone that would try it, it can't just be my setup alone? ..that's why I wanted to help - the many verses the one thing)
Okay I had all the folders opened and so watched it as it did its thing
It worked PERFECTLY !
Thanks Rick,
I'll get a modified version uploaded soon for everyone.
I would have never solved this without your help. Thanks for sticking it out. After all we went through, it only took one simple line of code to solve the issue. Go figure!
It was My Pleasure for sure.
I really enjoy this sort of thing, testing softwares and help solving problems.
You know, I think Acronis is lucky (I know we all are) to have You, such a talented and capable technician on this forum.
A new version of MustangPEBuilder for use with Microsofts' AIK has been uploaded for everyone. There is no need to download it if your current version has been working. The only change is to add a line of code to delete the TMP files talked about in the posts above.
Rick,
I have no idea why this was happening in your current system, but not in your earlier system. Can you compare the version numbers of Microsofts' dism.exe in the two systems to see if by any chance they are different? I'm just happy we found a suitable workaround.
As far as dism.exe in the ....\System32 folder it stays the same from a fresh install right through all WU's till now. v6.1.7600.16385
With WAIK for Windows 7, it installs its own dism.exe in its ....\Servicing folder without touching \System32. Same v6.1.7600.16385
With WADK Win8 that I installed in Win 7, it installs its own dism.exe in it's ....\DISM folder not touching any other. v6.3.9600.17029
Assumption the reason ADK works on my Current Windows 7 install with your Original application is because of its newer dism.exe maybe cleans its tmps better, just guessing though. Anyway, it's all a moot point I guess since your New application does the maintenance for it now. Sure I still have lingering wonderings why for instance your setup only has a few tmps and mine 120 and balks, but yours did to with just a few tmps. The tmp count issue is really only my itch to ponder including back to my fresh install where your Original app works..but fwiw I never checked/counted its tmp file accumulation. Anyway moving onward, question put aside.
Importantly at least you were able to produce the error in your post #156 which is the reason I started these posts to fix it.
I think, well, yes there's not many people building their boot media more than once, but sooner or later if they still have and use your Original to make a new boot media, their's too, like yours did, will/may hang on a .tmp file and get that error, so suggestion is that all current users should use your New version that's now posted to avoid possible issues.
I would suggest, if you want, the new build instead of v2.238 maybe should be v2.239 is warranted for sure.
Your New AIK MustangPEBuilder 2 posted to your website, of course tested, and works Excellent !
Thank you, again, nice work!
I was wrong when I said dism.exe was at fault. I am using dism.exe in the ADK version. We are working with the WAIK version and it is using imagex.exe from C:\Program Files\Windows AIK\Tools\x86 to mount and unmount the image. I did this to maintain backwards compatibility. Older version of the WAIK did not have dism.exe available. Imagex.exe is actually at fault for not cleaning up the TMP files. The version number of imagex.exe I see at that location is 16.1.7600.18385 dated 7/14/2009 and is 471 KB in size. Do you see the same thing?
It is interesting as a side note that I see the two versions of dism.exe you mentioned as having different sizes and dates even though they have the same version number.
Okay understood about dism.exe verses imagex.exe, thanks.
ADK has it's own, but Yes AIK image.exe in the C:\Program Files\Windows AIK\Tools\x86 folder is 16.1.7600.18385 digsig 7/14/2009
However the image.exe in the C:\Program Files\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\x86\DISM folder being 6.3.9600.17029 dig sig @ 1/20/2014
Again but said for image.exe this time, I imagine ADK worked fine for me because its new build of image.exe had better maintenance of those .tmp files, but here too your new code fixes it by cleaning out the tmps first before proceeding; whomever the cause, your new line of code deleting the .tmps lets the iso creation process continue without getting hung up on a past needed .tmp, well is my thought anyway, you're the boss.
Yes absolutely I had noticed that about the two different sizes and creation dates of dism.exe but same version numbers and wondered about that specifically, but didn't want to mention it since for that post would have been TMI on what I had already posted, I just figured that the coder (probably was two different ones different projects) was in a hurry and brushed off changing up version numbers but surly did something to it. Even one has a digsig but the other does not and their dates are 1 day apart. Life isn't perfect is it, or maybe in its imperfection, it is.
Question about the MustangPEBuilder_2_ADK
Working with this checkbox's function
AddDrivers.ini
(I added into it intel raid drivers like this)
[Driver Paths]
driver1=C:\f6flpy-x86\iaAHCIC.inf
driver2=C:\f6flpy-x86\iaStorAC.inf
[Driver Folders]
folder1=C:\f6flpy-x86\
folder2=C:\f6flpy-x86\
~~~~~~~~~~~~~~~
When clicking "Create WinPE ISO" the [Driver Paths] process works fine and goes by prompting successful on both entires, but for the [Driver Folders] additions process I get this cmd box error that comes up:
Cannot find the specified file 'C:\f6flpy-x86" /recurse /ForceUnsigned'
Looking in the DISM log here's a snipit of its corresponding reference
copy/paste
2014-09-21 09:47:42, Error DISM DISM Driver Manager: PID=3500 TID=5512 Error, file not found 'C:\f6flpy-x86" /recurse /ForceUnsigned'. - CDriverManager::ParseCommandLineTokens(hr:0x80070002)
2014-09-21 09:47:42, Error DISM DISM Driver Manager: PID=3500 TID=5512 base\ntsetup\opktools\dism\providers\dmiprovider\dll\drivermanager.cpp:969 - CDriverManager::Internal_DoAddDriverPackage(hr:0x80070002)
Everything works fine so not sure I even needed to fill in the [Driver Folders] path at all since I've already given it the [Driver Paths] info.
If I don't fill in the [Driver Folders] entry though then I get your gui prompt error of, quote:
"Probably no AddDrivers.ini or no [Drivers Folders] section..."
Again everything works fine so not sure this /recurse /ForceUnsigned error is just a formality
Rick,
Take the last backslash away.
[Driver Folders]
folder1=C:\f6flpy-x86
Yes of course, duh, it's self explanatory isn't it, but somehow when I copy/pasted the partial line from the drivers paths I took that \ with it, I see now I wasn't concentrating on what I had really done making it look past the folder, until now. It works fine, thanks.
Hi, just thought I'd drop in a say a hello to you Paul,
I still weekly enjoy using the Mustang TI ''v11'' plug in my TI ''v11'' USB boot AIK or ADK versions.
(...a little tibit I wanted to mention for a while: not that it matters, but I think the AIK may be a slightly faster than the ADK versions for some reason)
(...another little tidbit is that: The stock 2013 usb boot made from the program itself, is Not as fast as the AIK or ADK versions can do it when it comes to imaging or restoring tibs - the AIK/ADK usb boot versions are Much faster by 50% or more - same thing is true for using the old True Image v11 AIK or ADK versions too - which btw nicely v11 is just as fast as v2013)
Anyway the other reason for posting this this morning is to mention I noticed today when I was working within my TrueImage 2013 AIK USB boot that there is no Mount Feature available - have you noticed that too? (and no you can't open a tib by clicking the tib or using via A43 FM to right click on a tib either) The only way to do a similar function is go into restore individual files/folders option and within there you can mimic the explore process.
Is the Mount feature missing in boot environments for v2013?
And on the same subject, for what it's worth I see my old TrueImage v11 USB boot AIK or ADK versions when booted to them Yes They Do Have The Mount Feature and it works, but again just wondering why in the TrueImage 2013 AIK USB boot device - there is no Mount feature?
Hi Rick,
Acronis never offered the mount feature in any version of TI for the WinPE they provided. I was able to get it working in older versions, up until TI 2010, by running the Windows version if TI. That's why you have it in TI v11. After TI 2010, it became way too complicated and I couldn't make it work.
Okay then that explains it thanks for that info. Well then you great job with getting the Mount to work on the v11 plug then!
While I'm here something else I wanted to ask you, that I noticed today while using the USB AIK True Image v2013, or even on v11 too I see, that for whatever reason Network Access or rather will say when I go to restore and image I normally can choose Computers Near Me and pick from any shared partitions on them, but that doesn't show up in the AIK versions, but, that function does show up on the standard TI v2013 program made USB boot disk. I even tried starting PENetCfg but that prompts "unable to start network support" ..perhaps I am missing something how to get access to my Network?
I can always use the regular program made USB stick to do it, actually I just did, but, still would like it to work on the AIK's too.
I just tested the ADK USB too and it's a similar situation, but here I was able to start PENetCfg and it had options, but I still couldn't get TI to see Other Computers on my network but only This PC.
Hmmm, I've long forgotten :( ..but maybe last year when I made the AIK & ADK versions I was suppose to put some other drivers in it or something?
I don't need to use the Network function to get tibs very often, actually rarely but sometimes it's handy like today, but still if the regular program made USB boot gives it, then it would be nice if I could put that on all my AIK and ADK versions of USB boot sticks too.
I think your network controller is not supported by WinPE. You will need to add then driver using the AddDrivers.ini file in MustangPE. When you run PENetGfg in WinPE you should see your network controller listed at the top of the page.
Yes my controller is listed there, I will work on this later
Thank you!
Yes my controller is listed there, and I had added the drivers just fine.
I'm looking at the PENetCfg Network Configurator now and its GUI, and it shows the Intel(R) 82579v Gigabit Network Connection listed there
Then when I click the top left tab of 'Network Drives' there, and then inside there I click the 'Browse Network' tab, and then click the + near the WorkGroup listing, and then it shows listed the 2 other computers in the other rooms of my house (connected via the Lan) but when I click on them nothing happens; I can't expand them to see their shares.
When I'm booted to Windows I can access the 2 computers in our house and access what I have set for shares. Also the standard Acronis program made boot sticks the Network function works fine and I can see and access the tibs in the shared folders I have set on those other computers too, but I have never been able to figure out how when I'm booted to this ADK how to do it, and it's been a few years now and it's time I figure it out :) LoL. ...and so am asking what are the directions how to use this feature on this ADK so I can access my other computers?
Thank you!
You will have the best luck by using the Map a Network Drive feature. Map the network share you are using to store your backups as a drive letter.
I had been already testing that option for an hour today before I had posted, and no matter which way I tried it - I could not get the hang of it.
On WorkGroup I see the other two computers listed, and clicking on one of them auto fills in the Map Network Drive "Network Path" as for instance \\computerA and onto that I put \Network\Sharename - I even tried the hover suggestions of using the IP Address of the other computer which shows as 192.168.1.2 and so I added this in the Network Path box:
\\computerA\192.168.1.2\Network\Sharename
or just:
\\Network\192.168.1.2\Sharename
or
\\computerA\Network\Sharename
(not sure exactly how that should go there) I tried so many different ways, but clicking Map Drive on all my tried combinations, it prompts a user name and password, however I never use any, and have that turned off in windows and in Windows they all just connect since it's all my private network - and so what do you use for 'User Name' and 'Password' in this booted ADK boot case?
I tried just leaving it blank but that won't work either
I'm so close, at least I can see the other computers listed so it's almost there, I just have to figure out this last step,
Are there step by step directions anywhere that explains the procedure?
All my computers have Windows user names and passwords to boot into Windows. In Network Path I enter \\ComputerName\ShareName. Then I enter the Windows user name and password for the computer where the share is located and the drive letter is assigned to the share. If you don't use user names and passwords in Windows, it will probably not work in WinPE.
I just spent an hour trying to change over to homegroup and passwords way and that whole scene for each OS ...I did not finish since it's such a royal p.i.t.a. I just got frustrated with it and threw my hands up. My Standard Program made TI boot flash sticks Easily! can see my network computers and has access to each of their shared tibs folder only. I wish I could do the same network access with my cool Mustang WinPE ADK and/or wAiK boot sticks - they do everything else perfectly except for that. This is a closed network and I tend to all the computers with multiple OS's on them and just want simplicity without this password homegroup crap; its worked well for the last 12 years though all the different OS's still accessing each of them - I prefer the simplicity of it.
I hear you. I've always found networking a royal p.i.t.a. It's been a problem with all versions of Windows, even Windows 10.
I hear you too, and thank you for your programs...!
Every once in a while I try again to get the network access working on my mustang WinPE ADK & wAiK boot sticks...
I just want to be able to click a Network icon on it and have my other computers on my private secure Lan accessible (without using any mapping, passwords, or home group settings if I have it set that way in the first place) ..iow, just like the standard TI program made USB flash boot sticks can easily do
Worth a shot, but you could try WinPENetwork (portable app if you copy the created folders from install and put them on your USB drive) to see if it fairs any better once your WinPE is started up.
https://sourceforge.net/projects/penetwork/
I use it in my custom WinPESE8.1 disk and it fairs pretty well with network shares.
Okay I gave it a go, yes it's a little different maybe more convienient, but in the end the results are the same thing - I see all my network drives listed there, but when I click the + to open them it prompts for a user name & password, and again I don't use or need them on my private Lan as I explained.
Again I just want to be able to click the drives that I see and have the shares available without using any mapping, passwords, or home group settings if I have it set that way on my Network in the first place.
You must of read my previous posts so you must know all that, so I was wondering if you know something that I'm not seeing right off?
How did you have success?
Unfortunately, WinPE is generic and uses a generic admin account for login. Unless your network shares are open without any type of authentication, it's Windows default behavior to prompt for credentials or anyone could navigate there and see, steal, delete or corrupt the data. You probably have 2 options:
1) If the share is on another Windows computer... Control Panel\All Control Panel Items\Network and Sharing Center >>> Change Advanced Settings >>> Expand "all networks" >>> Turn off "password proteced sharing"
2) Assuming you don't want to do that, or the share is not on a Windows computer, but a NAS or some other SMB device... create a batch script using the "net use" commands and add that to your boot.wim\Windows\System32\startnet.cmd file before Acronis launches. I'm not sure if "net use" is available in WinPE though, I haven't personally tried, but if it is, that would be the ideal option and from what I've read, it "should" work.
How to Map Network Drives From the Command Prompt in Windows
Yes the shares are open, and so then to reply specifically to your Option 1,
There are five computers running Win7 in my private local lan network, and each of those 5 computer multiple partition setups have 1 (logical) backup partition set as an open share and yes password protected sharing has always been turned off. Note that on each of those 5 computers the ONLY thing shared is that one backup partition on each computer - and so when working within Windows when the Network icon is clicked on any of the 5 computer setups, all 5 computers show up with that same named logical backup partition available each to the other (no name/pass are needed) there is direct access each to the other. fwiw, Nothing else on all other partitions on all 5 computers are being shared, just that one backup partition on each.
And so as I understand it and have experienced when you boot into a WinPE environment, and there are shares available on my other computers on my lan, and whether password sharing is turned off or not on those other computers, PENetCfg will still prompt for a password on anything it sees.
Now, within WinPE and using the PENetwork.exe you have pointed out (just like PENetDfg can do) I find that yes I can see all my other computers listed, however when I click the + on any of them to expand their shares, I get the same Username Password prompt - and so it does not solve the problem (unless I am using your PENetwork.exe wrong which is very possible)
Again the point of my posts with Paul which he knew what I was saying, that I don't want to use the mapping, username/passwords, etc, and that when I boot my Mustang WinPE I want my TI programs to be able to easily see and have access to the .tib shares on my other private Lan network of computers that are running with the open shares.
In response to the flow of my conversations with Paul, I thought you said your PENetwork.exe faired well with that process? ...and so is that a yes or a no to what I have been asking? If it's a yes, please outline the process. Thank you.
WinPE does not have the networking stucture of a normal Windows system. It also does not use accounts, but runs at a "System" level instead. It will simply not do what you are asking. Microsoft uses it to install Windows systems. They leave it up to the rest of the world to add features that are needed to use it as a recovery environment. I'm sorry, but you are out of luck.
Rick - sorry for my confusion. It "works" for me because of a custom WinPE i've made with WinPESE8.1 which adds a lot of regular functionality back into the WinPE to make it look and feel almost like a Windows machine. With that particular custom WinPE, you can actually create other local account instead of just the default "system". I will have to test netuse commands on it when I have time as well and report back if those work. Pretty sure I did this in the past and it did, but I will verify to be sure. Assuming it does, then in this case with WinPESE8.1 custom WinPE, that is why it is/was working, by may not be working with other versions of WinPE.
OK, I just tested using my custom WinPESE8.1 machine. Success!
I am using homegroup on my main computer where the test share was created. I set "share" permissions and allowed "all users" full access to the new test share to keep it simple.
I booted my second test WinPESE8.1 machine and opened command prompt and mapped the new share with:
net use W: \\192.168.1.68\file_share /user:Test test
The command completed successfully and a new W: drive was automatically mapped and I coud see the existing test file and copy new files into it.
I so no reason why this could not be added to the WinPE init of this system so that it launched first in a batch file. I'm not going to go that far though to modify the .wim and everything though - just wanted to test the capability.
With your version of WinPE, are you able to use "net use" commands or are they not accepted because it's not part of the WinPE package? I honestly don't know how to add that manually if you'd need to - hence why i've used WinPESE8.1 to create the custom WinPE since it was easier. Once I had that working, I then replaced the default .wim files with Windows ADK and had Acronis build the WinPE with that (then went back and removed the winpe init flies from startup.cmd) and love the results of what I'm able to do with this custom win PE
Sorry, one more update - I just tested and net use commands DO work with the default Acronis WinPE media (mine was built with Windows 10.1 ADK if that makes any difference) as well so I'm guessing it will work for any WinPE. I would guess that you only need to update the startnet.cmd to first run your net use command before it calls on the Acronis launcher it launches the Acronis GUI.
I've been trying different combinations to figure out why the command is not showing completed for me, like it does for you, but this is what I get:
____________copy/paste
X:\windows\system32>net use W: \\192.168.1.3\file_share /user:Win7-5/BackUp
System error 67 has occurred.
The network name cannot be found.
__________
...I typed 192.168.1.3 since that's the address of one of the computers on my Lan, and I put Win7-5 since that's the name of it, and I put /BackUp since that's the name of the partition that I have set as shared - but I must be missing something simple here. I tried every which way.
Also don't forget I also want to be able to see the others, and so simply they are Win7-1 through Win7-5 ..of which also each has their own address on the Lan but usually stay within the 192.168.1.1 through 192.168.1.5 range
Its a P.I.T.A LoL, I just want it all to be a simple click click click and no fussing around. Honestly I could just put the tibs on my 5 TB portable HD and plug it in each one via USB, but again and again I just want this to work like the program made TI boot disk, which for instance I boot TI2013 usb flash stick it can easily see and access whatever other of the 5 computers on the network are on!
PS,
Thank you for your time, and btw, nice screenshot
How come Paul does not have his setup the way you do so he does not have to use the Mapping way?
..and fwiw, I'm pretty good with computers, but I must admit Network stuff is not in my wheelhouse
So the username in your code is Win7-5? The username in my code is "test" and then there is a space and the password after that is also "test". Yours has the username as "Win7-5/Backup" and no password
net use W: \\192.168.1.3\file_share /user:Win7-5/BackUp
vs
net use W: \\192.168.1.68\file_share /user:Test test
If you are going to want to map each drive for 5 systems, you'll have to use this command 5 times before Acronis launches and replace "W:" with 4 other letters to get 5 mapped drives, once you have a successful test.
Here is the breakdown of my command....
net use = the beginning of the net use command
W: = the drive letter you want to map the share as - can be anything other than X in most cases as winPE uses X: for the local drive
\\192.168.1.68 = the IP (can also be the computer name if prefered) of the location where the share is hosted on
\file_share = is the complete name of the share on 192.168.1.68 as would be accessed from a standard Windows (non winpe machine)
/user:test = username for the share
test = the password for the account named "test" in my situation
I know that you can map 5 shares with this command, but am not sure if they will all use the correct name/password with this method, I've not tried. If you can get the one connection, then you can test the others and let us know how it goes.
From the help file on Net Use...
The syntax of this command is:
NET USE
[devicename | *] [\\computername\sharename[\volume] [password | *]]
[/USER:[domainname\]username]
[/USER:[dotted domain name\]username]
[/USER:[username@dotted domain name]
[/SMARTCARD]
[/SAVECRED]
[[/DELETE] | [/PERSISTENT:{YES | NO}]]
NET USE {devicename | *} [password | *] /HOME
NET USE [/PERSISTENT:{YES | NO}]
And here is another page with some screenshots and breakdowns of the command
http://www.howtogeek.com/118452/how-to-map-network-drives-from-the-comm…
Rick, Bobbo is doing exactly what I originally told you to do in the first place! He is using the net use command to MAP the network share to the drive letter W: with the user name and password for the computer with the share. You keep saying you don't want to use a user name and password.
Hi Paul,
Yes I see and understand that now, and I thought since I was very clear throughout all of my messages that I did not want to use username/passwords on any of my computers and thought Bobbo understood that, and so thought he was giving me an automatic way around that by incorporating that command would be able to have the WinPE True Image boot stick when starting TI, it would automatically have instant access to all my computer shares showing.
Okay, so then we are back at the user/pass and mapping thing of which we talked about already, and is something that is fine within itself and I am not knocking it, but for me and my network I do not want to have to set username & passwords on any of my computers - and just like when booting to a standard TI usb boot stick it freely and instantly shows access to all computer shares perfectly, and all I ever wanted was for my awesome Mustang WinPE TI boot sticks to do the same easy no fuss process accessing my private network shares.
___________________
Hi Bobbo,
I apologize for any misunderstanding on my part. I thought you understood that by first answering into Paul and My posts about this that you had read them, and that I did not want to use name/pass or mapping, and so when you did reply I thought we were continuing the conversations flow and you were giving me an automatic cmd line to get around that. It was not until your last post #240 that you mention username code - but you see I was always assuming you knew I was talking about my computer name as Win7 and BackUp was the name of my shared Partitions of which I was saying was Win7-5/BackUp ..thinking it was my address entry that We were using.
Listen, I am sorry for any misunderstanding on my part here - I can see you put a lot of effort, time, and work to help the answer, but you were misunderstanding my repeated stated intentions, and I not being Network savvy enough to know the difference of what you were saying - so I will take the blame then! I thank you for your willingness to spend the extra time and effort you did to be a great help - it's commendable really.
___________________
If anyone comes up with a way to get WinPE to have the access like I have stated - please let me know about it.
As it stands right now I'm fine, and so when booted to TI and I want to pull a tib from my others computers shared backup partition I just boot my program made TIv2013 usb boot stick and it has instant access; otherwise when I am working on the images of the computer in front of me I use the Mustang WinPE TI booter for its benefits - and so you see I'm fine using it the way it is as I just use either booter for a purpose - it's just that I wanted to put both abilities all into one booter is all, for convenience.
Thank You Sincerely,
Rick
It seems like not having authentication actually adds an extra layer of complexity? Could you not create a local account on each machine for this purpose and only give it access to the backup locations?
Net use can be used without passwords, but still requires an account
http://serverfault.com/questions/243468/windows-command-net-use-failed-…
To be honest I'm not sure what 'create a local account on each machine' means in that context really.
This is what I have:
When I installed each of the 5 Win7 computers OS on my network, during the very beginning of the installs it prompts for a user name and password. For a username I put Win7-1 (on each successive computer install I put Win7-2, Win7-3, Win7-4, and Win7-5) When next it came to enter in the password, in each case I left that line Blank - and just clicked Enter, and so on purpose have it set so that when you turn on any of the computers it boots straight to Desktop.
For Sharing, I do Not have a Homegroup setup on any one of them nor do I ever want to have that in this particular private network setup of 5 computers.
On each of the 5 computers HD's, they each have a separate partition called BackUp, and it's that complete BackUp partition that is set as being Shared. I simply right clicked on that partition: Share With> Advanced Sharing> Advanced Sharing> ..and put a checkmark on it and clicked Apply.
When I am in Windows on any of the computers I can click on the Network icon that's on each Desktop, and within there immediately comes up listed all the other computers in the Network that are turned on at the moment, and when you click on whichever ones listed inside there, each one has that share listed which is called BackUp ...click that and you are instantly inside of their BackUp partition and have access to whatever is in it. No user/pass - you have instant access, and it was done that way on purpose!
The same is true when I boot the 'program made' True Image v2013 usb boot disk, each booted computer has instant (no-mapping, no user/pass) access to any .tibs within any one of those 1 - 5 computers on the network.
And so again, I'm not sure what 'create a local account on each machine' means in that context to what I have done already, and I will not turn on HomeGroup and have to deal with that; I don't want to make sharing complicated.
The OS setups are perfect the way they are really, the Windows sharing between them is Perfect for what we do; however, imho ..it's the WinPE environment that needs to give share access just like the program made boot disk does.
Ok, that's clear now. I was assuming you had another regular account on those machines with passwords and other permissions for access to the rest of the machine and were looking for away to have another system connect to the share with no credentials. So no, you don't need a second account.
The link I posted above suggest using double quotes where a blank password would be in the netuse command. I have not tried, but perhaps that will work in your situation.
http://serverfault.com/questions/243468/windows-command-net-use-failed-…
net use X: \\PC2\c$ /user:PC2\administrator ""
And this one has more information about adding "anonymous" access to shares as there is an "anonymous" account that can be added to the share, but needs some other Group policy changes first.
http://nikolar.com/2015/03/10/creating-network-share-with-anonymous-acc…
I'm pretty much out of ideas after that.
Thank you Bobbo for you post and last effort
Okay I just spent a hour going over each different link and their directions; I tried last night too. I certainly can't say I did it right but I tried, and now I'm beyond frustrated at 'myself' ...and leads me again to say - whatever needs to be done, needs to be done within WinPE and Not Windows.
fwiw, to add to my previous post to further explain, that each of the 5 computers are all also triple boot, meaning each can boot to 2 other OS's besides Win7. The point is, the same exact sharing scheme mentioned in my previous post is setup the same way within all OS's, and all of them work great within Windows sharing and within the program made TIv2013 usb boot stick all able to easily access all my computers shares. You can understand I'm reluctant to modify 15 Windows setups with all these complicated sharing changes, over the pure simplicity that I have now that works, and so again and again and again, for me, whatever needs to be done - it needs to be done to the WinPE True Image usb boot disks so that, when it comes to sharing, it will work like the program made TI boot disk with network access which btw rocks! when it comes to easily accessing all my shared partitions...of which I simply click the + Network, and when it expands all the other computers are showing each with the shared Backup partition showing and accessible.
Mustang.. Paul
I have a question I always wanted to ask you about your ADK MustangPEBuilder 2 and what drivers that you put into it as default. I was amazed that you had already included so many of them at that time, did you just take a group of the most current driver pack or something and put them in there?
When I boot your ADK MustangPEBuilder 2 it already recognizes my Marvel controller, and it also recognizes my Intel controller. It even picks up my USB "3" Renesas front header jacks on my tower which I was surprised about that. I really did not have to enter in any of my own drivers, and so I always wondered how you did that? ..or as I said did you just enter in the latest (8/22/2013 = time of build) default driver pack or something?
When I have your ADK booted and I open A43 and navigate to Boot (X:) and expand that to the Driver folder, it shows listed from A-Z so many drivers already listed in there, and so is that why?
Here is a screenshot attached showing the the beginning of that folders drivers contents:
I didn't add any drivers. What you see is the default drivers Microsoft has included in WinPE. The later the version is of WinPE the more drivers it will contain by default.
Okay that all makes sense, and thank you for the explanation.
One last question please, for instance when I created mine on Windows 7 with True Image version installed there, besides installing the Setup_MustangPEBuilder_2_ADK.exe, I used ''ADK for WinPE 5.0 Windows 8.1'' since it's the latest version and OS backward compatible to Windows 7.
The question is when I select to install controller drivers via your application, does it make sense even though I was on Windows 7 when I installed it, that since it's a Windows 8 WinPE I'm working with, that I should load Windows 8 drivers into it instead of the Windows 7 drivers? The reason why I say that for instance is, Marvel gives both a Windows 7 driver - but gives a different Windows 8 driver for my controller, and so since it's a Win8 WinPE isn't it logical that I should use the Marvel Windows 8 driver when building my Mustang ADK bootable True Image boot stick?
Paul Larini MustangPE & Plugins