So to clarify are you creating a script based deployment type in the console 
through the gui? And your app is not working?

Or

Are you scripting the creation of a script based deployment type, and the 
script is failing to correctly create it?

From: [email protected] [mailto:[email protected]] On 
Behalf Of Robert Spinelli
Sent: Friday, March 27, 2015 4:13 PM
To: [email protected]
Subject: RE: [mssms] Powershell Deployment type - Script Installer

I'm probably just entering something wrong in the powershell.

Do you have an example of how you do it?

I'm pretty much having the issue outlined in this thread:

https://social.technet.microsoft.com/Forums/en-US/3a4853f1-675a-4f43-b83a-c6b1b8f98a50/trouble-with-addcmdeploymenttype-and-scriptinstaller-type?forum=configmanagersdk


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Schwan, Phil
Sent: Friday, March 27, 2015 4:02 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Powershell Deployment type - Script Installer

What issue(s) are you encountering?  Typically, you specify Script Installer as 
the type and then put the .exe as the installation program.  They most 
difficult part is usually making sure you have something to use for the 
Detection Method.  You also want to make sure you're running in the appropriate 
platform (x86 vs x64) as this can often cause issues.

Can you give more details on what you're trying to do?

-Phil

_________________________________________________________________
Phil Schwan | Technical Architect, Enterprise Windows Services
Microsoft VTSP ([email protected]<mailto:[email protected]>)
Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 
48075
Lync: 312.756.1626  Mobile: 419.262.5133
www.projectleadership.net<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.projectleadership.net_&d=AwMFAg&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=y5HHJCssYRYZVfsLSe2wt-Ofz-k_j5EH1315KiXkzIM&s=VVgm8GMVEVsE_--iBOdB5RM6dIqoZxlzL7mRj00ZBhc&e=>
 [linkedin_logo-19x20] 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_philschwan&d=AwMFAg&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=y5HHJCssYRYZVfsLSe2wt-Ofz-k_j5EH1315KiXkzIM&s=aTPjQqAHatjg5z2ODUn41-zmgzaVT0wWDPrPuPYKslY&e=>
 [Twitter-Logo1-20x20] 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_philschwan&d=AwMFAg&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=y5HHJCssYRYZVfsLSe2wt-Ofz-k_j5EH1315KiXkzIM&s=OtPGMYU35Q1wwWLJTn83wtrF9aMeSa4zCHu08JLmqbg&e=>
  [wordpress-logo3] 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__myitforum.com_myitforumwp_author_philschwan&d=AwMFAg&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=y5HHJCssYRYZVfsLSe2wt-Ofz-k_j5EH1315KiXkzIM&s=5ivsQVWa2feVgmTfoDVI3gX4LUr03ghNyE_kLO0TxTs&e=>
[Description: Description: Description: Arrow email]Lead with Strategy. 
Leverage Technology. Deliver Results.




From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Robert Spinelli
Sent: Friday, March 27, 2015 3:36 PM
To: mssms
Subject: [mssms] Powershell Deployment type - Script Installer

I can't seem to figure this out, does anyone have an example of how to create a 
deployment for script installer?  Only thing I seem to find on the web is that 
there is a bug and doesn't work, but that seems like old posts.

I'm trying to make a DT using script installer so I can enter in an .exe (ex: 
installer.exe) as the installation program command line.

Thanks




________________________________

CONFIDENTIALITY NOTICE: This email contains information from the sender that 
may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected 
from disclosure. This email is intended for use only by the person or entity to 
whom it is addressed. If you are not the intended recipient, any use, 
disclosure, copying, distribution, printing, or any action taken in reliance on 
the contents of this email, is strictly prohibited. If you received this email 
in error, please contact the sending party by reply email, delete the email 
from your computer system and shred any paper copies.

Note to Patients: There are a number of risks you should consider before using 
e-mail to communicate with us. See our Privacy & Security page on 
www.henryford.com for more detailed information as well as information 
concerning MyChart, our new patient portal. If you do not believe that our 
policy gives you the privacy and security protection you need, do not send 
e-mail or Internet communications to us.



Reply via email to