bjhs, I am not an attorney, but I should hope that a moderator will rule on the EULA question. As I read it (found in nLite folder in Program Files), only personal use is allowed. We have seen several posters working for non-profits with this problem and I do not remember the answer. Why don't you PM cluberti and ask his opinion. I should point out that nuhi (nLite author/owner) has not participated here in over a year. Users of nLite are always in some danger (perhaps little) of nLite simply disappearing some day. The support you get in the forum is all you can hope for and may not satisfy management. Please let us know what cluberti has to say. There are other ways (not automated) to accomplish what you are trying just using MS tools. At the bottom of this page is a link to the Unattended Guide and there is an Unattended forum here also. Enjoy, John.
"Program Files" directory problem
#22
Posted 14 August 2010 - 06:33 PM
Done!
When he replies I'll post the answer.
As for the problem I'm having? Any more idea?
Regards
When he replies I'll post the answer.
As for the problem I'm having? Any more idea?
Regards
#23
Posted 14 August 2010 - 10:40 PM
New try.
Just changed the Program Files path, and the Documents and Settings.
Still no luck.
Ideas?
Just changed the Program Files path, and the Documents and Settings.
Still no luck.
Ideas?
Attached File(s)
-
last session.ini (2.15K)
Number of downloads: 4
#24
Posted 15 August 2010 - 12:01 AM
Using this as an image engineering solution via your role as a sysadmin for a college technically would be a violation of the nLite or vLite EULA - the college *may* pass the non-commercial clause depending on whether or not it's for profit, and/or whether or not it's a private enterprise or a public institution, but that is all fairly elementary as this most certainly fails the "personal-use" clause if this is being done on any scale larger than an installation for one singular PC to be used primarily, or only, by that sysadmin; I know this is not the case by reading this thread and noting the following:
It is also worth stating that modification of Windows using nLite or vLite will void any supportability contract you have with Microsoft for that installation of Windows, and if the school is large enough it probably does have a volume license and/or academic licensing scheme for MS software that includes support - doing this would put you in violation of that agreement (and possibly the Windows EULA itself), so it's not just the nLite licensing you and your management should be aware of.
This discussion was taken offline, but the nLite and vLite EULAs are *VERY* specific about this particular point, and I'm just not sure why some folks are having such a hard time with it. It's only legally licensed for use for personal non-commercial purposes and any company or business purposes are explicitly called out as a violation of the license (this is stated explicitly in the EULA itself, I am not taking this out of context or paraphrasing it); you have to pass *both* tests to meet licensing criteria. Just because you are using it for an organization that is non-commercial or not-for-profit does not absolve you of being in compliance with the other 50% of the requirement that the tool only be used for personal use. If you're unsure, ask if this is going to be used to assist you in doing a job for your employer, or if you are going to be using it to create an image that will go somewhere other than *only* your own personal PC. If you answer "yes" to either of those questions, you cannot use nLite or vLite, period, and be in compliance with the EULA. Also, an additional question - if the copies of Windows you're modifying are licensed under any sort of volume licensing deal with Microsoft (whether that be academic, charity, or business), or if you have a support contract with Microsoft for those copies of Windows, you will be violating the agreements for those if you use nLite or vLite to modify the Windows source, so avoid it at that point as well.
bjhs, on 14 August 2010 - 03:21 PM, said:
We have a kinda big computer park and i need to do a universal (sort of) image for all the labs.
It is also worth stating that modification of Windows using nLite or vLite will void any supportability contract you have with Microsoft for that installation of Windows, and if the school is large enough it probably does have a volume license and/or academic licensing scheme for MS software that includes support - doing this would put you in violation of that agreement (and possibly the Windows EULA itself), so it's not just the nLite licensing you and your management should be aware of.
This discussion was taken offline, but the nLite and vLite EULAs are *VERY* specific about this particular point, and I'm just not sure why some folks are having such a hard time with it. It's only legally licensed for use for personal non-commercial purposes and any company or business purposes are explicitly called out as a violation of the license (this is stated explicitly in the EULA itself, I am not taking this out of context or paraphrasing it); you have to pass *both* tests to meet licensing criteria. Just because you are using it for an organization that is non-commercial or not-for-profit does not absolve you of being in compliance with the other 50% of the requirement that the tool only be used for personal use. If you're unsure, ask if this is going to be used to assist you in doing a job for your employer, or if you are going to be using it to create an image that will go somewhere other than *only* your own personal PC. If you answer "yes" to either of those questions, you cannot use nLite or vLite, period, and be in compliance with the EULA. Also, an additional question - if the copies of Windows you're modifying are licensed under any sort of volume licensing deal with Microsoft (whether that be academic, charity, or business), or if you have a support contract with Microsoft for those copies of Windows, you will be violating the agreements for those if you use nLite or vLite to modify the Windows source, so avoid it at that point as well.
#25
Posted 15 August 2010 - 02:00 AM
Thanks for the clarifications.
Nonetheless, as a future reference, nLite program has a problem with the modification of the Program Files path.
Nonetheless, as a future reference, nLite program has a problem with the modification of the Program Files path.
#26
Posted 17 August 2010 - 06:03 PM
bjhs, on 15 August 2010 - 02:00 AM, said:
Thanks for the clarifications.
Nonetheless, as a future reference, nLite program has a problem with the modification of the Program Files path.
Nonetheless, as a future reference, nLite program has a problem with the modification of the Program Files path.
Yes, thanks cluberti for providing a reference argument for all of us.
For future reference, I do not think nLite has a problem with modification of the Program Files path. I have gone to the bottom of the drawer and found an old CD XP Pro from a very old machine and run nLite against it. I used my XP x64 host to run nLite. Changing the Program Files path proved to be no problem (once I remembered how to run VMware Player again). Attached are my Last Session.ini and Last Session_u.ini (expurgated). I only added SP3 and ran the Unattended Task. Please let me know if there are any questions. Have fun, John.



Help


Back to top










