Autocad 2025 issue

The Toolkit General Discussion
1

i am following this guide to package autocad 2025 in intune using psadt. (How to deploy Intune Autocad package)

in deploy-application.ps1, under install section:

# Define the path to the batch file

$batchFilePath = "$PSScriptRoot\Files\install AutoCAD 2025.bat"

# Execute the batch file using PSADT's Execute-Process

 Execute-Process -Path "cmd.exe" -Arguments "/C `"$batchFilePath`"" -Wait

in deploy-application.ps1, under uninstall section:

# Define the path to the batch file

$batchFilePath = "$PSScriptRoot\Files\Uninstall AutoCAD 2025.bat"

# Execute the batch file using PSADT's Execute-Process

Execute-Process -Path "cmd.exe" -Arguments "/C `"$batchFilePath`"" -Wait

i ran manually and everything installed and uninstalled ok.

install command:

deploy-application.exe -deploymenttype “install”

uninstall command:

deploy-application.exe -deploymenttype “uninstall”

however, when i package in intune win32, the install will not complete and only install “autodesk identity manager” and “autodesk access” and it ended with failed.

anyone encountered the same issue and how do you package it to work with psadt?

2

Hi @ngjr,

I personally would change the $batchFilePath variable to use the PSADT $dirfiles variable (see the variables documentation here: Variables · PSAppDeployToolkit), as this will trigger the bat file execution from the correct source path.

Making this change, your script should now look like this:

# === Install Section ===
# Define the path to the batch file
$BatchFilePath = "$($dirfiles)\install AutoCAD 2025.bat"

# Execute the batch file using PSADT's Execute-Process
Execute-Process -Path "cmd.exe" -Arguments "/C `"$BatchFilePath`"" -Wait

...

# === Uninstall Section ===
# Define the path to the batch file
$BatchFilePath = "$($dirfiles)\Uninstall AutoCAD 2025.bat"

# Execute the batch file using PSADT's Execute-Process
Execute-Process -Path "cmd.exe" -Arguments "/C `"$BatchFilePath`"" -Wait

For Win32 packages (i.e. for .intunewin files) Intune will download the package below here:
C:\Program Files (x86)\Microsoft Intune Management Extension\Content\Staged\<App_ID>\
so the installation can then commence.
N.B. The App_ID can be obtained from the URL in your browsers address bar for the app you have packaged, it is the long GUID immediately after the https://intune.microsoft.com/#view/Microsoft_Intune_Apps/SettingsMenu/~/2/appId/ part of the URL.

1 Like
3

Hi,

Just a thought - Maybe there’s an issue of paths in the batch file instead? That would explain why a manual install worked.

… Alex …

4

hmm. this is my installer batch file and folder structure.

image
image1347Ă—681 42.1 KB

this is my collection.xml genenerate from autodesk deployment tool and default folder structure inside image folder.

image
image736Ă—388 19.8 KB

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Collection version="1.4" xsi:schemaLocation="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <Identity>
        <Name>AutoCAD 2025</Name>
        <UPI2>{3AFE5303-0C1D-4D73-BC55-33CE0174C432}</UPI2>
        <RevisionNumber>0</RevisionNumber>
        <DeploymentImagePath>C:\temp\autocad2025\image</DeploymentImagePath>
        <ImageType>Uncompressed</ImageType>
        <Symlink>false</Symlink>
        <PortalSessionId>bd910d0b-1aa4-48b8-94cb-bfd17d4450f1</PortalSessionId>
        <AnalyticsId>XQHvFJ7/kgxoq6gYU7LxUH1QnUU=</AnalyticsId>
        <ConfigurationID>{B4C1E647-9073-41F4-A5C7-50F15512F622}</ConfigurationID>
        <DownloadId>{F0BD1680-CF22-4EA3-B1D4-33E23D6DB61D}</DownloadId>
    </Identity>
    <CustomProperties>
        <Property name="ADA_INSTALL" value="0"/>
        <Property name="ACCESS_INSTALL" value="1"/>
    </CustomProperties>
    <Configuration>
        <InstallPath>C:\Program Files\Autodesk\</InstallPath>
    </Configuration>
    <InternalConfiguration>
        <ODISPackages>
            <Package name="odis" path="ODIS/pkg.odis.xml" extractParams="--mode unattended --useService 0"/>
        </ODISPackages>
        <ComponentUpdateUrl>https://compsvc.delivery.autodesk.com/compsvc/componentService/component/latest/v1</ComponentUpdateUrl>
        <OdisInstallerUpgradeCode>{BEC01EA1-3942-3A39-9863-47536D7CDEB1}</OdisInstallerUpgradeCode>
        <ManifestDownloadUrl>https://manifest.delivery.autodesk.com/manifest/manifestService/manifestDownload/v1</ManifestDownloadUrl>
        <State>live</State>
        <Env>prd</Env>
    </InternalConfiguration>
    <Eula>
        <Status>Accept</Status>
    </Eula>
    <LoggingSettings>
        <Logging>true</Logging>
        <Path>C:\temp\autocad2025\log\AutoCAD 2025.log</Path>
    </LoggingSettings>
    <URLRoot>https://dds.autodesk.com</URLRoot>
    <InstallType>Deployment</InstallType>
    <Bundles>
        <Bundle SeqNo="0">
            <UPI2>{99E57530-7CC1-31F4-89E9-24175C7690C2}</UPI2>
            <Platforms>
                <Platform name="Windows" architecture="x64" minVersion="10.0.17763"/>
            </Platforms>
            <LangId>en-US</LangId>
            <BundleID>ACD_2025_en-US</BundleID>
            <ProductKey>111A1</ProductKey>
            <Applications>
                <Application>
                    <UPI2>{D9773BD8-BAB3-3B31-A7B8-2764457662B5}</UPI2>
                    <CustomProperties>
                        <Property name="SUPPORT_CONTENT_ROOT" value="[ROAMINGUSERFILESFOLDER]"/>
                        <Property name="SUPPORT_CONTENT_CUSTOM_PATH" value=""/>
                        <Property name="LOCKSECURITYSETTINGS" value="0"/>
                        <Property name="SECURELOAD" value="1"/>
                        <Property name="ACADProfile_TrustedPaths" value=""/>
                        <Property name="LEGACYCODESEARCH" value="0"/>
                        <Property name="ACADLspAsDoc" value="#0"/>
                        <Property name="ACOMP_EXPRESS_TOOLS" value="1"/>
                        <Property name="ACOMP_MIGRATE" value="1"/>
                        <Property name="ACAD_USE_ONLINE_CONTENT" value="#1"/>
                        <Property name="ACAD_ENABLE_SEND_PC_NAME" value="#0"/>
                        <Property name="ACAD_ENABLE_ROUNDTRIP" value="#1"/>
                        <Property name="ADSK_DESKTOPSHORTCUT_1" value="1"/>
                        <Property name="CUSTOM_PROFILE" value=""/>
                        <Property name="ADLM_EULA_COUNTRY" value="US"/>
                        <Property name="NIWSELECTION" value="1"/>
                        <Property name="ACADSTANDALONENETWORKTYPE" value="2"/>
                    </CustomProperties>
                </Application>
            </Applications>
        </Bundle>
    </Bundles>
</Collection>
5

Hi,

I’ve had a look at what my colleagues did. For AutoCAD 2025, they haven’t changed the packaging and it remained with the batch file.
However for Maya, which uses the same delivery mechanism, they copied the content of the image folder into the Files folder, and used the following command:

Execute-Process -Path 'Installer.exe' -Parameters '-i deploy --offline_mode -q -o "Collection.xml" --installer_version "2.6.0.129"'

Worth a shot?

6

tried. no different. what i observe is that during first run, i will encounter this error. i ran again and it just succeeded.

image
image1304Ă—414 98.2 KB

7

I have exactly the same issue; I followed the same procedure as you. My deployment fails on the first attempt and succeeds if I restart the installation. I tried creating a loop in PSADT with 3 attempts that doesn’t exit on exitcode 1, but it doesn’t work. If I follow the procedure without using PSADT, it works fine.

For now, I’ll use the .bat file as in the procedure. I wasted a lot of time trying to get it to work with PSADT without success. If you’ve found a solution, I’d love to hear it!

8

same here. wasted a lot of time and in the end i also use the .bat file procedure without using psadt. :frowning_face: