Multi OEM/Retail Project

We have this already included in the project...same cert (TOSHIBA6) and same key (Win7 Pro edition) that is included so this machine should oem activate with this project.

 

You said it didn't activate which we all know but it didn't install oem wallpaper theme either? This is odd. Did you setup the iso correctly? No branding is odd because even if it doesn't activate it should always brand to the oem manufacturer if present in project which TOSHIBA is. Think I might be on to something here.

 

This logging implementation is such a pain on win 8.x and win 10. It writes what it wants to only. I cant for the life of me figure out why. I even made a test cmd file and only parts write to it still. What a pita!!!

I really don't know if this is worth it or not and this is why I say this...logging will only tell me where the script breaks but if an image didn't copy over correctly then I already know where the problem would lie anyways. lol So this really does nothing for me to help troubleshooting plus end user wont know anyway because of limited access to project files so it is somewhat useless for them.

 

Exactly my issue, deletes previous info written to file when other cmd file runs but my other issue is even in the install cmd file it only writes parts not everything. It only shows about a 1/4 of what it should write to the file. Its puzzling.

Vista and Win7 does logging perfectly....go figure. lol

Think it is a permission issue but everything I have tried made no difference so maybe do two separate log files and then put them together. I will try this and see results later on this evening.

 

@ bitznpcz,
I am waiting to hear from you on my above post to you. I am curious as to your answer.

If the above is correct then it sounds as if the whole project failed for you which is very odd! I tend to believe the iso wasn't setup correctly.

 

Yeppers, my thoughts exactly. Great minds think alike. lol

Back to my logging issues. I will check back later this evening to see if he posted an answer.

 

I agree, no problem with multi oem project. I see NTLite used so it could have corrupted the iso. Another slipstreaming issue. lol Not multi oem project related.

I swear, we need a slipstreaming thread created. I even have a good name for it...slipstreaming 101. lol

 

There are two methods that windows loader uses for activation. One is emulated which yours was not but instead was oem activated using key and cert included in the windows loader which is also in this project. If windows loader activated by oem (not emulated) then the project will as well for they both have the same key and cert included.

Falls back to your iso again I am afraid.

Note: We know NTLite has slipstreaming issues for sure since he mentioned it. Put this app on the list to not use. lol

Updated first post with this info...

This subject is now closed.

 

I have a feeling that most of those that have recently complained about using a slipstreamed iso's and failures of the multi oem project use NTLite since it seems to be with Win 7 mostly. I would recommend testing in VMware any custom slipstreamed iso's end users have created to make sure it fully works before doing any installs on a real machine. Might save you time and a lot of headaches. Oh, then I could go fishing more.

 

This is true but no AV would ever delete the oobe.cmd...decompile.exe possibly but never the oobe.cmd file.

Has anyone tried adding the project to the iso after it was created by a third party app like NTLite and then use UltraISO to add the $oem$ folder to sources folder in the iso, then save it with UltraISO? I use UltraISO to add to all of my original M$ iso's. I wonder if this corrects the issue for those that encounter this problem.