Please help, I've forgotten how to use DISM GUI to change my NAS mapping in "startnet.cmd" file in my boot.wim file
Hi All,
I changed the NAS path for saving my backups files, but I forgot to modify the mapping in my boot.wim file on my custom usb recovery stick. I know you use the DISM GUI utility to modify the "startnet.cmd" file, but I can't remember where I find this utility how do I run it ?
Thank you, I found it in some old postings I had several months ago. Now my specific problem is that I can edit the startnet.cmd with notepad but it won't let me save, saying access denied. I'm going to reboot my pc just in case somethings amiss.
I got it. The file had to be tweaked for permissives. Acronis now boots off the usb stick and finds the backup files on my NAS device.
I must write better notes, I'm amazed how soon I forget. Getting this Dell XPS 15 to work with Acronis was a real beast.
satwar, glad to hear you have resolved this issue - would be great if you could document the process and share it if you feel that would be OK to do. Might help someone else looking to do the same.
Yes, I will, for my own sake.
As for sharing with others, the only problem is that I am not the brains behind the procedure, the site's MVPs had the knowledge. I wouldn't want people asking me for help, as I don't have the depth of knowledge that MPVs have.
The real "trick" behind getting Acronis bare metal restore to handle Dell XPS machines is to recognize that they are configured with RAID drives (even though they are not physically present) and the appropriate drivers must be installed in the restore process.
satware, understand. Please see sticky post: 127281: MVP Tool - CUSTOM ATI WINPE BUILDER that may be an alternative to doing this all yourself if it is mainly a case of adding in the extra RAID drivers.
Ditto to the MVP ATI PE builder - it's a cool tool, but won't help with modifying the startnet.cmd file directly.
You cannot edit the startnet.cmd file directly on the mounted folder because of system only access permissions on some of the mounted files. It is easier to open/edit the file and make your changes, but instead of trying to directly save them there, instead, save startnet.cmd to your desktop (or wherever you like) and then copy it paste it back to the original mounted location. UAC will pop up and ask for admin confirmation to copy the file and then, when you say yes, it will copy your modiifed version into the mounted folder correctly.
Yes indeed that tool looks like a very good step in the right direction.
i also required DISM GUI to define the mapping to my NAS folder where my backups were stored. Not sure if the tool can handle that function as well.
DISM GUI is the easy method for mounting the boot.wim so I'd keep using that to open it up so you can edit the starnet.cmd file, save it to the desktop, copy it back to the moutned Windows/system32 folder, and once copied backup, use DISM GUI to commit the change.
Definitely give the MVP ATI PE Builder "advanced' build a test run and check it out.
Once you have it built, then do what you've been doing to modify startnet.cmd as you've been doing so far. Actually, you can probably just add the same commands to the goodies.bat file in the
MVP_ATIPEBuilder_v70\Other\goodies.bat
and then build the winpe with the tool and won't even have to bother with using DISMGUI anymore :)
My goodness, I didn't remember that bit about copying to desktop, thank you.
My wife has a new Acer E15 laptop with SSD drive. How do I figure if I need to inject drivers ?
Most likely, you won't need to. Just use the MVP ATI PE builder (advanced version - it's only advanced because it adds extra features like a web browser, but the tool itself is exactly the same in looks for both versions).
If you're building your Windows PE with ADK 10 (windows 10 1511 or newer), you'll have great driver support out of the box. Plus, we include the latest Intel Rapid Storage Technology drivers (IRST) in the tool as well for better RAID support and support of NVME PCIE hard drives which should be useful for many newer systems.
Ultimately, if the WinPE boots, screen works, NIC works, and hard drives are detected, WinPE is working as it should. Just be aware that WinPE does not support wireless networking by default so you need to use the NIC or a USB to ethernet adapter if you don't have a built in NIC. There are ways to get wireless workign, but it's more work than most are willing to put in and can be complicated so we'll keep it simple with standard networking since that's what ADK supports.