1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Visual Studio 2017 Professional

Avatar
Chris Kasprzak

Hello,

I'm wondering if anyone out in the PDQverse has successfully created a VS.NET 2017 Pro Deployment package? 

I keep running into where it starts the installer and it just sits there. Most time PDQ says it was successful even though it wasn't. I've tried application install and powershell, but both produce the same just sitting idle installer.

https://docs.microsoft.com/en-us/visualstudio/install/use-command-line-parameters-to-install-visual-studio

https://svenaelterman.wordpress.com/2017/05/10/silent-offline-install-for-visual-studio-2017-enterprise-with-mdt/

Are the two resources I've used.

I was able to get it to install ONCE using powershell but PDQ deploy immediately said it was successful even though the install was going on. Tried the --wait command and that still didn't help PDQ from stating it was successful immediately.

0

Comments

4 comments
Date Votes
  • Avatar
    Stephen Valdinger

    I deploy enterprise once a semester to a lab for our programming coursework. 

    Note about this package, you'll need to find the right product code for the license application step. You can find information about those codes here: https://msdn.microsoft.com/en-us/library/mt270173.aspx

    For convenience here is the table from that page:

    Here's an XML dump of my package. Save this as an .xml file and use File > Import in Deploy to create the package. You'll need to adjust paths to suit.

    <?xml version="1.0" encoding="utf-8"?>
    <AdminArsenal.Export Code="PDQDeploy" Name="PDQ Deploy" Version="16.1.0.0" MinimumVersion="15.0">
     <Package>
     <CurrentLibraryPackageVersionId value="null" />
     <PackageDefinition name="Definition">
     <Conditions type="list">
     <PackageStepCondition>
     <Architecture>Both</Architecture>
     <Version>All</Version>
     <TypeName>OperatingSystem</TypeName>
     </PackageStepCondition>
     <PackageStepCondition>
     <IsUserLoggedOn>AlwaysRun</IsUserLoggedOn>
     <TypeName>LoggedOnUser</TypeName>
     </PackageStepCondition>
     <PackageStepCondition>
     <ConditionMode>None</ConditionMode>
     <InventoryCollectionId value="null" />
     <InventoryCollectionName></InventoryCollectionName>
     <TypeName>Collection</TypeName>
     </PackageStepCondition>
     </Conditions>
     <CopyMode>Pull</CopyMode>
     <DelayedApprovalTimeSpan>7.00:00:00</DelayedApprovalTimeSpan>
     <DownloadApprovalMode>Manual</DownloadApprovalMode>
     <InventoryScanProfileId value="null" />
     <IsDownloadApprovalModeInherited value="true" />
     <ScanAfterDeployment value="null" />
     <Steps type="list">
     <InstallStep>
     <CustomCommandLine></CustomCommandLine>
     <FileName>\\redacted\path\VS2017\vs_Enterprise.exe</FileName>
     <Files></Files>
     <IncludeDirectory value="true" />
     <LeaveInstallFile value="false" />
     <MsiOperation>Install</MsiOperation>
     <MsiQuiet value="true" />
     <MsiRestart>Never</MsiRestart>
     <Parameters>--quiet --add Microsoft.VisualStudio.Workload.ManagedDesktop</Parameters>
     <SuccessCodes>0,1641,3010,2359302</SuccessCodes>
     <RunAs value="null" />
     <Conditions type="list">
     <PackageStepCondition>
     <Architecture>Both</Architecture>
     <Version>All</Version>
     <TypeName>OperatingSystem</TypeName>
     </PackageStepCondition>
     <PackageStepCondition>
     <IsUserLoggedOn>AlwaysRun</IsUserLoggedOn>
     <TypeName>LoggedOnUser</TypeName>
     </PackageStepCondition>
     <PackageStepCondition>
     <ConditionMode>None</ConditionMode>
     <InventoryCollectionId value="null" />
     <InventoryCollectionName></InventoryCollectionName>
     <TypeName>Collection</TypeName>
     </PackageStepCondition>
     </Conditions>
     <ErrorMode>StopDeploymentFail</ErrorMode>
     <Title>Install Visual Studio Software</Title>
     <TypeName>Install</TypeName>
     <IsEnabled value="true" />
     <IsPostStep value="false" />
     <IsPreStep value="false" />
     </InstallStep>
     <CommandStep>
     <Command>"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\StorePID.exe" <license key> 08860</Command>
     <Files></Files>
     <SuccessCodes>0</SuccessCodes>
     <RunAs value="null" />
     <Conditions type="list">
     <PackageStepCondition>
     <Architecture>Both</Architecture>
     <Version>All</Version>
     <TypeName>OperatingSystem</TypeName>
     </PackageStepCondition>
     <PackageStepCondition>
     <IsUserLoggedOn>AlwaysRun</IsUserLoggedOn>
     <TypeName>LoggedOnUser</TypeName>
     </PackageStepCondition>
     <PackageStepCondition>
     <ConditionMode>None</ConditionMode>
     <InventoryCollectionId value="null" />
     <InventoryCollectionName></InventoryCollectionName>
     <TypeName>Collection</TypeName>
     </PackageStepCondition>
     </Conditions>
     <ErrorMode>StopDeploymentFail</ErrorMode>
     <Title>Apply License</Title>
     <TypeName>Command</TypeName>
     <IsEnabled value="true" />
     <IsPostStep value="false" />
     <IsPreStep value="false" />
     </CommandStep>
     <FileCopyStep>
     <AllowOverwrite value="false" />
     <CopyAllFiles value="false" />
     <FilePatternsText></FilePatternsText>
     <IgnoreOverwriteErrors value="false" />
     <IncludeSubFolders value="false" />
     <Mode>SingleFile</Mode>
     <Source>\\redacted\path\VS2017\Spring18 VB.vssettings</Source>
     <Target>C:\</Target>
     <RunAs value="null" />
     <Conditions type="list">
     <PackageStepCondition>
     <Architecture>Both</Architecture>
     <Version>All</Version>
     <TypeName>OperatingSystem</TypeName>
     </PackageStepCondition>
     <PackageStepCondition>
     <IsUserLoggedOn>AlwaysRun</IsUserLoggedOn>
     <TypeName>LoggedOnUser</TypeName>
     </PackageStepCondition>
     <PackageStepCondition>
     <ConditionMode>None</ConditionMode>
     <InventoryCollectionId value="null" />
     <InventoryCollectionName></InventoryCollectionName>
     <TypeName>Collection</TypeName>
     </PackageStepCondition>
     </Conditions>
     <ErrorMode>StopDeploymentFail</ErrorMode>
     <Title>Copy Settings file to local workstations</Title>
     <TypeName>FileCopy</TypeName>
     <IsEnabled value="true" />
     <IsPostStep value="false" />
     <IsPreStep value="false" />
     </FileCopyStep>
     </Steps>
     <Timeout value="600" />
     <UseCustomTimeout value="true" />
     <RunAs value="null" />
     </PackageDefinition>
     <Description></Description>
     <NewLibraryPackageVersionId value="null" />
     <OriginalId value="null" />
     <Version></Version>
     <IsAutoDownload value="false" />
     <FolderId value="2" />
     <LibraryPackageVersionId value="null" />
     <Name>Visual Studio 2017 Enterprise</Name>
     <Path></Path>
     <PackageDisplaySettings name="DisplaySettings">
     <DisplayType>Normal</DisplayType>
     <IconKey>Icon-Package</IconKey>
     <SortOrder value="7" />
     </PackageDisplaySettings>
     </Package>
    </AdminArsenal.Export>

     

    0
  • Avatar
    Chris Kasprzak

    So I kind of know why it thinks it's successful but the process are still completing the install.

    I'm thinking I need to run a step 2 to watch the process which is what I'm looking into now. I just was looking if someone else has done it differently.

    0
  • Avatar
    Chris Kasprzak

    @Stephen Valdinger

    2017 has gone away with the admin xml file. It has been replaced with a respone.json file. I had a PDQ Deployment for 2015 that was working with out a hitch. 

    It's just the changes on 2017 that are being a pita.

    0
  • Avatar
    Stephen Valdinger

    That XML file is the create a PDQ Deploy package. Has nothing to do with VS 2017's actual install.

    0