topic Re: Deployment of Single Server License Software via Batch Script in Installation & Licensing Forum

Deployment of Single Server License Software via Batch Script

Anonymous — Tue, 17 Jan 2017 13:19:01 GMT

Good Morning,

I’m deploying Autocad 2017 and the Building Design Suite to a small office via batch script. I have to install other software alongside the Autodesk products and unfortunately group policies are not an option. My trouble lies with the Building Design Suite. I’ve managed to get Autocad to install silently via the batch script (it’s a standalone license) but cannot get the building design suite to install (it’s a single server license). Since the parameters are the same for the most part, I’m thinking my problem is with the following:

ACADSERVERPATH=“<FlexLicenseServer> 000000000000”

Is the FlexLicenseServer parameter the UNC path to the license server ie ‘//OSCO-1’ or is it simply the server name ‘OSCO-1’? Also, what do the zeroes represent? I tried leaving it as is and putting in the ip address of our license server but was just taking a shot in the dark. For reference, here is the entire batch script command.

"F:\Source Files\Navis and Revit 2017\Setup.exe" /t /qb /language en-us /c NW: ACADSERIALPREFIX=xxx ACADSERIALNUMBER=xxxxxxxx ADLM_PRODKEY=766I1 ADLM_EULA_COUNTRY=US InstallLevel=5 ACADSTANDALONENETWORKTYPE="3" ACADLICENSESERVERTYPE="Single Server License" ACADLICENSETYPE="Network License" ACADSERVERPATH="OSCO-1 000000000000" /c RVT: ACADSERIALPREFIX=xxx ACADSERIALNUMBER=xxxxxxxx ADLM_PRODKEY=766I1 ADLM_EULA_COUNTRY=<eula_lang> InstallLevel=5 ACADSTANDALONENETWORKTYPE="3" ACADLICENSESERVERTYPE="Single Server License" ACADLICENSETYPE="Network License" ACADSERVERPATH="OSCO-1 000000000000"

If anyone has any insight to what I'm doing wrong I would appreciate the help.

Thank you

RE: Deployment of Single Server License Software via Batch Script

Otto — Tue, 17 Jan 2017 13:19:24 GMT

Hello cvinciguerra and welcome to the Autodesk community!

If you’re having trouble with the activation email, please note that sometimes the email can be accidentally routed to your spam or junk folder. Please check there.

Also, please note that you should be able to access your download and activation information by logging into Autodesk Accounts.

If you cannot access software in your account and need to download it now, please go to the Virtual Agent.

If none of those items helped, please submit a support request as follows:

Students should request to have the confirmation email resent via this form.

If you are having trouble with your Autodesk Account or an eStore purchase, please visit our order support page where you will be able to chat with a representative or submit a support request.

If this information was helpful, please consider marking it as an Accepted Solution by clicking on the "Accept as Solution" link, below. Taking a moment to do this will help others with similar questions find useful answers. Thank you!

Kudos (click on the link or the "thumbs-up!" icon), are also gratefully received! (Even a bot likes praise.)

If this answer missed the mark, please let us know so that other community members can lend a hand. Any additional details might help, too: consider including relevant screenshots, log files, error messages, or system specs.

Re: Deployment of Single Server License Software via Batch Script

Mark.Lancaster — Tue, 17 Jan 2017 13:24:22 GMT

@Anonymous

Welcome to the community...

I will inform the big guns of this forum and they should be able to assist you...

Paging

@TravisNave

@Darin.Green

Re: Deployment of Single Server License Software via Batch Script

Darin.Green — Tue, 17 Jan 2017 14:43:55 GMT

Thanks for the notification @Mark.Lancaster!

@Anonymous,

The best way to approach this is to build a network deployment onto a network share, then use the following line to install the software from the deployment:

\\SERVER\SHARE\BDSU2017\Img\Setup.exe /qb /I \\SERVER\SHARE\BDSU2017\Img\BDSU2016.ini /language en-us

That one line will install everything it needs for that deployment including prerequisites because it's referencing the INI file that contains the configurations.

---EDIT---

Change SERVER\SHARE\BDSU2017 to the correct location for your deployment.

For assistance with creating network deployment go here

Re: Deployment of Single Server License Software via Batch Script

Anonymous — Tue, 17 Jan 2017 16:55:52 GMT

Thanks for the reply Darin. That's a much cleaner option than writing a block of text for each program in the suite! However, I ran that command and a blank command prompt window opened (I had @Anonymous off) before closing out a few seconds later. No error or feedback of any kind. The silent install should still pop up a box at least that shows the current progress, correct?

-Chris

Re: Deployment of Single Server License Software via Batch Script

TravisNave — Tue, 17 Jan 2017 20:53:05 GMT

That is correct.

Sorry for the delay today. So busy at work. But Darin is right on with his explanation.

Good Luck!

Re: Deployment of Single Server License Software via Batch Script

Anonymous — Wed, 18 Jan 2017 12:22:33 GMT

Thanks Travis. It must be something to do with the computer's connection to the server then since it's still not installing. I'll leave that section of code as Darin said and see if I can narrow the problem down further.

Thanks again for the help guys, I really appreciate it!

-Chris

Re: Deployment of Single Server License Software via Batch Script

Anonymous — Wed, 18 Jan 2017 12:55:26 GMT

For future reference in case anyone else is running into a similar problem, with Darin's code the path to the setup.exe can be in quotes if necessary. However, the path to the ini file should not be in quotes even if there are spaces in the path name. I'm not sure why this is the case but it's how I was able to get things working properly.

Thanks again everyone,

-Chris