For such reasons i dumped those tools and learned here @MDL to use DISM/IMAGEX/WIMLIB-IMAGEX, nothing else needed (ok bcdedit and oscdimg). If one uses properly no problems will appear ... good job MS .
Agreed. Yet I need to do more testing isos... As I said quite a few posts above, I had issues with the last project on Windows 7 x64 ES AIO, but hey! I'm aware is not this project the culprit, something else
Got some members trained seems like. lol Just joking. I don't do slipstreaming myself because of all the variables. The times I did, I used dism to do what I wanted, not a third party app. If untouched iso then I know I will have no problems and never do. School work done so back to my logging issue of win8.x and win10. Go go VMware. lol
Grabbed a beer and put on some tunes and low and behold logging is now working in win8.x and win10. That's a temperamental script. lol Update: Oh my, we have a new tool to add for win 10 that will be added to project as well (thanks to Alphawaves and alexwilson). I need to drink more beer it seems. Good things happen when beer is included. lol
Update on log implementation: I have tested all OS's in VMware and logging works. Even added activation status to log file. The only problem I have now is with Alphawaves new tool to change win 10 login background. Locks up win 10 on reboot. I have to force shutdown in VMware. Nothing I can do tonight so good night all.
I don't use autounattend.xml. I only use NTLite to slipstream updates, not make changes... I had a client with a new Windows 7 laptop last week and WSUS reported 600+ updates! Having a slipstreamed disk can save hours worth of work. Over the summer, I will try and learn the manual methods for slipstreaming so I am not reliant on NTLite. This is a great forum with great members and I apologise again for all the confusion yesterday.
Guardian, I used nlite and used ultraiso with no issues adding the folder. This is my latest ISO now and working great. Takes a few hours to create.
This is what I have for the next release (waiting on Alphawaves to get back with me about the win10 login background tool):
I used ultraiso on my original untouched ISOs to add the $OEM$ folder and use NTLite to keep up to date. I cannot replicate OOBE.cmd being removed, so not sure how that happened, but it was removed from both my x86 and x64 versions of Windows 7 Professional. I've tried the same processes with Windows 7 Home Premium and Windows 7 Ultimate and cannot replicate OOBE.cmd being deleted. I'll check the folder next time before raising a request!!
If you do have more slipstreaming issues please create your own thread since it isn't related to this project. Please and thank you. Glad you finally got it working.
I talked with Alphawaves and I think why it isn't working for me is because I am using an older version of win10, not the new one so I will download it and test in VMware. If it does work for me then I will update first post tomorrow. Thanks goes out to Alphawaves for putting up with me bugging him. lol
Hey old friend. Glad you made it over here. Might find some useful info from members here. Enjoy the site brother.
Update: The tool from Alphawaves is working. I had to old of a version of win10, not the newer one. I did noticed win10 added some new user images that need to be added to the project so I will do that this evening. Have a good day everyone.