Topic: [PENDING] Another Installation Platform perhaps? OPK!
Hey Bashrat,
I love the packs. And I am currently using them for use within a non-profit organization which has 100+ computers over mutiple sites (the organization deals with special needs adults and they are getting into youth and children now too...so I frequently do re-installs and can see myself doing way more real soon ). What I do though is use RIS and via RIS I load up WinPE and then point it back to a shared folder also on the RIS server which contain the OPK images (aka cfgsets).
As it is right now, I apply the packs to the *\x86\ folders that contain the i386es for the corresponding cfgsets. But then I have to move the $oem$ folders to the cfgset\****\**** folders and then manually edit the unattend.txt files with the driverpaths that were placed in the winnt.sif file.
Do you think it might be in the cards that one day there will be an option to choose whether the user wants to use a winn.sif or an unattend.txt file that already exists and choose the location of said file...or even better yet, just have an option in the installation platform choices for OPK and then choose your sku and cfgset?
However, if there is a way someone could point me to a how to so I could implement m2 into a RIS/WinPE/OPK deployment environment that would be great...as I seem to be in the minority for this sort of deployment and m2 doesn't natively work over the network since it expects the packs to be on a cd.
I just like deploying this way because it gives the OOBE (it also make it easier for those not on the domain..ie the "clients" to create users when they get the machine in the group homes), eliminates the need to constantly be creating CDs...as well as it allows me to make sure the corporate keys don't go anywhere by loosing a disc. I worked for a fortune 500 and within a month of us buying a block, MS blacklisted 'em because one of our unattend discs went AWOL.
Like I said though, it could be handy for those who are in a OEM environment...(which any OEM who does not use the OPK is technically not fulfilling their end of the agreement with MS if they are registered as a system builder). I had my own business before doing this and that is how I deployed everything so a customer knew they were 100% legit (they typed in their own key) whether it was a new copy of windows or a service re-install. I never once typed in a customers key. Nor did I ever use a driver cd (thanks to you Bashrat ). This last paragraph was just an enticement to increase the need some might have for this method, though it is true hehe.
If it is in the works great...if not *sniff* guess I gotta figure something else out here.