Silent Install Issue with AutoCAD
Hi, I was trying to run execute Autodesk 2011 silently , I used the below command for execution.
Setup.exe /t /qb /Language en-US /c ACAD: INSTALLDIR="C:\Program Files\Autodesk\AutoCAD 2011" ACADSERIALPREFIX=xxx ACADSERIALNUMBER=xxxxxxxx ADLM_PRODKEY=xxxxx ACADFIRSTNAME="A" ACADLASTNAME="User" ACADORGANIZATION="Users Corporation" InstallLevel=5
I have given the correct serial number and product key but I still get an error saying "Setup is unable to validate your Serial number or Product key"
Please provide solution for this issue if any.
Thanks,
Geetha.
Setup.exe /t /qb /Language en-US /c ACAD: INSTALLDIR="C:\Program Files\Autodesk\AutoCAD 2011" ACADSERIALPREFIX=xxx ACADSERIALNUMBER=xxxxxxxx ADLM_PRODKEY=xxxxx ACADFIRSTNAME="A" ACADLASTNAME="User" ACADORGANIZATION="Users Corporation" InstallLevel=5
I have given the correct serial number and product key but I still get an error saying "Setup is unable to validate your Serial number or Product key"
Please provide solution for this issue if any.
Thanks,
Geetha.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
andemats
12 years ago
Could this have something to do with what type of license you use?
http://docs.autodesk.com/ACD/2011/ENU/pdfs/acad_install.pdf
http://docs.autodesk.com/ACD/2011/ENU/pdfs/acad_install.pdf
Posted by:
andemats
12 years ago
Posted by:
jmaclaurin
12 years ago
Be sure to follow the Network Administration and Deployment section carefully. I'd also suggest you consider copying the files local prior to starting the install. You can do this while still using the a Network deployment by specifying the location that it will be copied locally to instead of a network share. You might have better success.
Another thing to test is whether the install can be used by other users post install. We discovered that the installation (by design) is taylored to properly work ONLY for the user that performs the install. May not sound like much of an issue, unless you are planning a mass deployment using something like SCCM where the account performing the install is likely not the logged in user but rather the System account. You will find that others have posted on this site that this is not the case, but they also don't come out and describe how they were able to overcome this problem. When you dig further, you will see that there is heavy reference to file locations hard coded to the installing user's profile under HKLM, and this is where the problem starts since users don't generally have the ability to write to other user's profiles, and even more so in Windows 7.
Another thing to test is whether the install can be used by other users post install. We discovered that the installation (by design) is taylored to properly work ONLY for the user that performs the install. May not sound like much of an issue, unless you are planning a mass deployment using something like SCCM where the account performing the install is likely not the logged in user but rather the System account. You will find that others have posted on this site that this is not the case, but they also don't come out and describe how they were able to overcome this problem. When you dig further, you will see that there is heavy reference to file locations hard coded to the installing user's profile under HKLM, and this is where the problem starts since users don't generally have the ability to write to other user's profiles, and even more so in Windows 7.
Posted by:
niveknonrev
12 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.