Hi, I was successful in deploying .msi apps without any issues. Tried deploying a .exe apps, the first app worked without any issues but the second .exe app fails. I tried to perform a manual installation (not using SCCM) it did install but at the end part of the installation an error message appeared but for some reason it still showed up in my taskbar and all components were installed meaning the installation did push thru.

Tried it again in a system where the app is not yet installed via sccm again and it always fails.

Here is my setting:

1. create package

-create a name for the package, create a description, under source folder browsed on my shared folder where the .exe file is located and this shared folder has read/write access.

2. chose Standard program, under Standard program, created a Name, command line selected the .exe file, nothing under startup folder, under run is normal, under program can run: only when a user is logged on, and run mode is: run with admin rights, drive mode is: runs with UNC name

3. Platform requirements: This program can run on any platform, estimated disk space: Unknown MB, maximum allowed run time: 120

4. Deployed to the desired collection, specified distribution points, under purpose selected available, for the schedule, schedule availability is ticked but nothing on the expiry, under the section that says: When the scheduled assignment time is reached: I've ticked Software installation, for deployment options both setup to download content from distribution point and run locally. Finished the wizard, Performed update of distribution points.

FYI, tried a different .exe file and same issue

Another FYI, when app is available under software center, it is successful in ownloading but fails in installing

Thanks in advance!

Jeff

Hi all

When I disable Show new deployments option in SCCM client settings, the application installation experience from the Application catalogue doesn't show the download and software center notification ?

Is it not possible to have it show the download notification but not Show new deployments ?

Does anyone know a way to FORCE a restart of a client machine after deploying and installing software from SCCM 2012?

Jason Smith

Hi,

Now that IE10 has come out for Windows 7 SP1 is there a way do deploy it via Configuration Manager?

Thank in advance.

With the best regards,

Dmsousa

Scenario: 

I have a virutalized SCCM 2012 server that is BSOD when i increase my concurrent sending and Threads per package by 1 (from default of 5 and 3 to 6 and 4). 

it doesn't seem to BSOD straight away, takes awhile for it to crash. i have more than 50 sites, 20 of them have rate limits set on them at 15% and 50% on some of them between 6am and 8pm. If over night i monitor it and it doesn't BSOD, it at least makes the SCCM server hang. i can't RDP into, i can't even go onto the VM console and log in. it just sits there still. i can get to the Management console remotely from another computer to the server. i also can browse to the log file area on the server in which it shows no processing in the distr.log, pkgTransfer.log, schedule.log.

Im migrating my SCCM 2007 to 2012 SP1.  I have migrated and converted all of my 2007 packages to 2012 applications.  I have about 170 applications total.  Im going through them and making sure they all in/unin-stall correctly. I am working with two test systems - one 32bit and the other 64bit.  Im running into a problem where all of my applications dont show up in system center.  Im always missing about 50% +/- of them and they are always different.  I can reimage the system and different applications will show up - some not previously shown, some were.  They are all deployed to a test_workstations collection only and are available. Content is distributed successfully and 98% of them are set to Install for System.  Lastly when I check the deployments tab on the device all of the applications are listed there.  These systems have been on for a few days with no change.  It seems like stuff doesnt get fully updated - ie. the applications that are listed after imaging are the only ones youll get.

Can anybody help me out with this?  Its hard to move forward when this so sporatic.

Thanks-

Rob

Hi,

I have deployed an MSI file as an application in SCCM 2012. Now I need to install updates on a regular basis (each month).

I tried to make a new application with the command : msiexec /p \\server\deploymentshare\sources\update.msp /qbn

Whenever I try to deploy it does not install. The eventviewer shows an error 1602 and a referral to a logfile for more info.

However I don't see any useful information in there. Can anybody tell me what I am doing wrong?

THis is the logfile:

=== Verbose logging started: 21-5-2013  16:01:39  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\Windows\SysWOW64\msiexec.exe ===
MSI (c) (F8:DC) [16:01:39:628]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (F8:DC) [16:01:39:628]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (F8:A8) [16:01:39:635]: Resetting cached policy values
MSI (c) (F8:A8) [16:01:39:635]: Machine policy value 'Debug' is 7
MSI (c) (F8:A8) [16:01:39:635]: ******* RunEngine:
           ******* Product: {FF6054B5-D159-4180-A1E0-56E4253B23BA}
           ******* Action:
           ******* CommandLine:  REBOOTPROMPT=S PATCH="D:\Temp\7C8CEFAC479A7BC74BFE1A88B5AC042F_TempProfitSetup\Update.msp"
MSI (c) (F8:A8) [16:01:39:636]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (F8:A8) [16:01:39:636]: Grabbed execution mutex.
MSI (c) (F8:A8) [16:01:39:750]: Cloaking enabled.
MSI (c) (F8:A8) [16:01:39:750]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (F8:A8) [16:01:39:752]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (8C:F8) [16:01:39:759]: Running installation inside multi-package transaction {FF6054B5-D159-4180-A1E0-56E4253B23BA}
MSI (s) (8C:F8) [16:01:39:759]: Grabbed execution mutex.
MSI (s) (8C:9C) [16:01:39:761]: Resetting cached policy values
MSI (s) (8C:9C) [16:01:39:761]: Machine policy value 'Debug' is 7
MSI (s) (8C:9C) [16:01:39:761]: ******* RunEngine:
           ******* Product: {FF6054B5-D159-4180-A1E0-56E4253B23BA}
           ******* Action:
           ******* CommandLine:  REBOOTPROMPT=S PATCH="D:\Temp\7C8CEFAC479A7BC74BFE1A88B5AC042F_TempProfitSetup\Update.msp" CURRENTDIRECTORY="D:\Temp\7C8CEFAC479A7BC74BFE1A88B5AC042F_TempProfitSetup" CLIENTUILEVEL=2  CLIENTPROCESSID=6904
MSI (s) (8C:9C) [16:01:39:761]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (8C:9C) [16:01:39:761]: Setting cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:761]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:761]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:761]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:761]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:761]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:761]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:761]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:762]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:779]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:779]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:779]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:779]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:779]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:779]: Machine policy value 'LimitSystemRestoreCheckpointing' is 0
MSI (s) (8C:9C) [16:01:39:779]: SRSetRestorePoint skipped for this transaction.
MSI (s) (8C:9C) [16:01:39:782]: End dialog not enabled
MSI (s) (8C:9C) [16:01:39:782]: Original package ==> C:\Windows\Installer\1590b40.msi
MSI (s) (8C:9C) [16:01:39:782]: Package we're running from ==> C:\Windows\Installer\1590b40.msi
MSI (s) (8C:9C) [16:01:39:798]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:798]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:798]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:798]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:798]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:798]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:798]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:798]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:798]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:798]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (8C:9C) [16:01:39:798]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:799]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (8C:9C) [16:01:39:799]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:799]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (8C:9C) [16:01:39:799]: APPCOMPAT: looking for appcompat database entry with ProductCode '{FF6054B5-D159-4180-A1E0-56E4253B23BA}'.
MSI (s) (8C:9C) [16:01:39:799]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (8C:9C) [16:01:39:799]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:799]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:799]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:799]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:799]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:825]: MSCOREE not loaded loading copy from system32
MSI (s) (8C:9C) [16:01:39:827]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:831]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:831]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:39:835]: File will have security applied from OpCode.
MSI (s) (8C:9C) [16:01:39:964]: Original patch ==> D:\Temp\7C8CEFAC479A7BC74BFE1A88B5AC042F_TempProfitSetup\Update.msp
MSI (s) (8C:9C) [16:01:39:964]: Patch we're running from ==> C:\Windows\Installer\16d3e1f.msp
MSI (s) (8C:9C) [16:01:39:965]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'D:\Temp\7C8CEFAC479A7BC74BFE1A88B5AC042F_TempProfitSetup\Update.msp' against software restriction policy
MSI (s) (8C:9C) [16:01:39:965]: SOFTWARE RESTRICTION POLICY: D:\Temp\7C8CEFAC479A7BC74BFE1A88B5AC042F_TempProfitSetup\Update.msp has a digital signature
MSI (s) (8C:9C) [16:01:40:503]: SOFTWARE RESTRICTION POLICY: D:\Temp\7C8CEFAC479A7BC74BFE1A88B5AC042F_TempProfitSetup\Update.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (8C:9C) [16:01:40:503]: SequencePatches starts. Product code: {FF6054B5-D159-4180-A1E0-56E4253B23BA}, Product version: 2.9.4, Upgrade code: {56FB005A-8B1E-4826-B460-AF7C279F46C5}, Product language 1043
MSI (s) (8C:9C) [16:01:40:503]: Optimizations are not possible in the patch sequencer because there are no applied patches.
MSI (s) (8C:9C) [16:01:40:503]: PATCH SEQUENCER: verifying the applicability of QFE patch D:\Temp\7C8CEFAC479A7BC74BFE1A88B5AC042F_TempProfitSetup\Update.msp against product code: {FF6054B5-D159-4180-A1E0-56E4253B23BA}, product version: 2.9.4, product language 1043 and upgrade code: {56FB005A-8B1E-4826-B460-AF7C279F46C5}
MSI (s) (8C:9C) [16:01:40:503]: Validating transform 'FuncBuildToPU' with validation bits 0x8a2
MSI (s) (8C:9C) [16:01:40:503]: Transform 'FuncBuildToPU' is valid.
MSI (s) (8C:9C) [16:01:40:503]: PATCH SEQUENCER: QFE patch D:\Temp\7C8CEFAC479A7BC74BFE1A88B5AC042F_TempProfitSetup\Update.msp is applicable.
MSI (s) (8C:9C) [16:01:40:503]: The original #_QFESequence table:
MSI (s) (8C:9C) [16:01:40:503]: PatchGUID: {360DA102-4ECA-4E9A-B74E-3ABBC834336C} ResultantVersion: 2.9.4 PatchFamily: Family1 Sequence: 6 Type: QFE
MSI (s) (8C:9C) [16:01:40:503]: The pre-sorted #_QFESequence table: - this is useful to see if patches had been ordered correctly within resultant versions and patch families
MSI (s) (8C:9C) [16:01:40:503]: PatchGUID: {360DA102-4ECA-4E9A-B74E-3ABBC834336C} ResultantVersion: 2.9.4 PatchFamily: Family1 Sequence: 6 VersionOrder: 0 SequenceOrder: 0 Type: QFE
MSI (s) (8C:9C) [16:01:40:503]: PATCH SEQUENCER: The initial #_Predecessor table:
MSI (s) (8C:9C) [16:01:40:503]: PatchFamily: Family1, PatchGUID: {360DA102-4ECA-4E9A-B74E-3ABBC834336C}, Predecessor GUID: NULL
MSI (s) (8C:9C) [16:01:40:503]: PATCH SEQUENCER: Step 1
MSI (s) (8C:9C) [16:01:40:504]: PATCH SEQUENCER: patch {360DA102-4ECA-4E9A-B74E-3ABBC834336C} (PatchFamily Family1) will be sequenced.
MSI (s) (8C:9C) [16:01:40:504]: PATCH SEQUENCER: The resulting #_OrderedGUIDs table:
MSI (s) (8C:9C) [16:01:40:504]: Patch: {360DA102-4ECA-4E9A-B74E-3ABBC834336C} Order: 0 (Family: Family1)
MSI (s) (8C:9C) [16:01:40:504]: The ordered #_QFESequence table: - has the final sequence of QFEs.  It lists each PatchGUID only once.
MSI (s) (8C:9C) [16:01:40:504]: PatchGUID: {360DA102-4ECA-4E9A-B74E-3ABBC834336C} ResultantVersion: 2.9.4 PatchFamily: Family1 Sequence: 6 Order: 0
MSI (s) (8C:9C) [16:01:40:504]: The #_QFESequence table with patches sorted on Sequence within Patch Families:
MSI (s) (8C:9C) [16:01:40:504]: PatchGUID: {360DA102-4ECA-4E9A-B74E-3ABBC834336C} PatchFamily: Family1 Sequence: 6 SequenceOrder: 0 Type: QFE
MSI (s) (8C:9C) [16:01:40:504]: PATCH SEQUENCER: QFE patch {360DA102-4ECA-4E9A-B74E-3ABBC834336C} cannot be superseded because there is no supersedence defined in Family1 family yet for this type
MSI (s) (8C:9C) [16:01:40:504]: PATCH SEQUENCER: QFE patch {360DA102-4ECA-4E9A-B74E-3ABBC834336C} will attempt to supersede in Family1 family, starting from sequence 6
MSI (s) (8C:9C) [16:01:40:504]: SequencePatches returns success.
MSI (s) (8C:9C) [16:01:40:504]: Final Patch Application Order:
MSI (s) (8C:9C) [16:01:40:504]: {360DA102-4ECA-4E9A-B74E-3ABBC834336C} - D:\Temp\7C8CEFAC479A7BC74BFE1A88B5AC042F_TempProfitSetup\Update.msp
MSI (s) (8C:9C) [16:01:40:504]: Machine policy value 'DisablePatch' is 0
MSI (s) (8C:9C) [16:01:40:504]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (8C:9C) [16:01:40:504]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:40:504]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:40:504]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:40:504]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:40:504]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:40:504]: Machine policy value 'DisableMsi' is 0
MSI (s) (8C:9C) [16:01:40:504]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (8C:9C) [16:01:40:504]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (8C:9C) [16:01:40:504]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:40:504]: Product {FF6054B5-D159-4180-A1E0-56E4253B23BA} is admin assigned: LocalSystem owns the publish key.
MSI (s) (8C:9C) [16:01:40:504]: Product {FF6054B5-D159-4180-A1E0-56E4253B23BA} is managed.
MSI (s) (8C:9C) [16:01:40:504]: Running product '{FF6054B5-D159-4180-A1E0-56E4253B23BA}' with elevated privileges: Product is assigned.
MSI (s) (8C:9C) [16:01:40:504]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (8C:9C) [16:01:40:504]: Using cached product context: machine assigned for product: 5B4506FF951D08141A0E654E52B332AB
MSI (s) (8C:9C) [16:01:40:504]: MSI_LUA: Entering Credential Request. hwnd = 7541440, MsiAction = 2, productname = Profit, version = 2.9.4, language = 1043, manufacturer = AFAS Software
MSI (s) (8C:9C) [16:01:40:505]: MSI_LUA:  (continued)... packagepath = C:\Windows\Installer\1590b40.msi, packagesource = C:\Windows\Installer\1590b40.msi, dwUpdates = 1
MSI (s) (8C:9C) [16:01:40:505]: MSI_LUA:  (continued)... update 0 = C:\Windows\Installer\16d3e1f.msp
MSI (s) (8C:9C) [16:01:40:505]: MSI_LUA:  (continued)... update source 0 = D:\Temp\7C8CEFAC479A7BC74BFE1A88B5AC042F_TempProfitSetup\Update.msp
MSI (s) (8C:9C) [16:01:43:858]: MSI_LUA: Credential Request return = 0x800704C7
MSI (s) (8C:9C) [16:01:43:872]: Product: Profit - Update '{360DA102-4ECA-4E9A-B74E-3ABBC834336C}' could not be installed. Error code 1602. Additional information is available in the log file D:\Temp\MSId3d45.LOG.
MSI (s) (8C:9C) [16:01:43:873]: Windows Installer installed an update. Product Name: Profit. Product Version: 2.9.4. Product Language: 1043. Manufacturer: AFAS Software. Update Name: {360DA102-4ECA-4E9A-B74E-3ABBC834336C}. Installation success or error status: 1602.
MSI (s) (8C:9C) [16:01:43:874]: Note: 1: 1708
MSI (s) (8C:9C) [16:01:43:874]: Product: Profit -- De installatie is mislukt.
MSI (s) (8C:9C) [16:01:43:874]: Windows Installer installed the product. Product Name: Profit. Product Version: 2.9.4. Product Language: 1043. Manufacturer: AFAS Software. Installation success or error status: 1602.
MSI (s) (8C:9C) [16:01:43:877]: Attempting to delete file C:\Windows\Installer\16d3e1f.msp
MSI (s) (8C:9C) [16:01:43:895]: MainEngineThread is returning 1602
MSI (s) (8C:F8) [16:01:43:895]: No System Restore sequence number for this installation.
User cancelled installation.
C:\Windows\Installer\1590b40.msi
MSI (s) (8C:F8) [16:01:43:896]: User policy value 'DisableRollback' is 0
MSI (s) (8C:F8) [16:01:43:896]: Machine policy value 'DisableRollback' is 0
MSI (s) (8C:F8) [16:01:43:896]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (8C:F8) [16:01:43:897]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:F8) [16:01:43:897]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:F8) [16:01:43:897]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (8C:F8) [16:01:43:897]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (8C:F8) [16:01:43:897]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (s) (8C:F8) [16:01:43:897]: Restoring environment variables
MSI (c) (F8:A8) [16:01:43:899]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (F8:A8) [16:01:43:900]: MainEngineThread is returning 1602
=== Verbose logging stopped: 21-5-2013  16:01:43 ===

Edterman

so before SP1 you could convert packages (.EXE files) to Applications. was that feature taken out in SP1?

Just added a package and wanted to convert to Application but i don't see that option anymore.

Twitter: @dguilloryjr LinkedIn: http://www.linkedin.com/in/dannyjr Facebook: http://www.facebook.com/#!/dguilloryjr

Hi there

Has anyone created a SCCM 2012 application to deploy both a .msi file which also required some additional batch script commands, such as creating a folder and copying a file?

I have a .msi file I need to deploy, and part of this deployment (not part of the .msi) also involves creating an additional file and folder structure within the folder structure created by the .msi file.

I can do this with a SCCM 2012 package, but I want to know if I can do it with an application.

I've played about with it; getting the .msi to install is of course fairly simple, however I can't a batch script with the file and folder creation/copy commands to run.

Anyone had to do anything like this?

Best regards

John

After capturing a new base image and updating our task sequence, I have discovered machines are getting stuck in provisioning mode when I try to install the App-V5.0 SP1 client during the task sequence. I'm assuming the application is causing a hang up in the TS process, and therefore the machine is getting stuck in provisioning mode, but that is just a guess. Looking at the appenforce.log, there appears to be an issue with our App-V client application and or it's dependencies, but I'm a noob at reading log files, and need some help. We have the application setup with the following dependencies, which has worked fine so far when doing normal collection based deployments.

.Net Framework 4.5 or 4.0

WMF 3.0 (KB2506143)

Microsoft Visual C++ 2010

----------------------------------------------------------------------------------------------------------------

Here's a look at the appenforce.log:

I should mention, the App-V client is installing and functional when the task sequence completes, but the problem is client certificate = none, and Provisioning mode=True in registry.

Hello forum,

Can someone confirm, if SCCM2012 is working as intended when considering the following:

I created MS Lync 2013 as an application (A), superseding an existing application of MS Lync 2010 (B). This in itself works fine when application A is being deployed to a collection of computers. (Lync 2010 is being uninstalled, and 2013 installed)

What baffles me is if I put application A into a task sequence which is only available to PXE (e.g. my OSD task sequence), I will see computers evaluating the application and start uninstall/install Lync inside the OS. (AppEnforce.log, AppIntentEval.log)

Is this really as intended? The TS itself is only available to PXE, but yet will applications in the TS still be evaluated by the OS, and cause Lync (and other application if not present on the client) to be uninstalled/installed (when software inventory is run).

Thanks in advance

Martin

Martin Bengtsson | Blog: www.imab.dk

Hi all,

I'm trying to deploy SysCtr Endpoint Protection on Mac OS X using ConfigMgr. The CMAppUtil outputs 2 packages and 2 applications:

- Install.pkg 1KB

- Installer.app 165 KB

- Installer.pkg 55 MB

- Uninstaller.app 792 KB

Now the only one that seems to install SCEP is the Installer.pkg, but this way SCEP is locked down with many settings unavailable (grayed out), if I install SCEP interactively the installation is fully functional.

Anyone has gone through this process? Is there a way to massively deploy SCEP for Mac OS X via ConfigMgr? Is there a way to automate the SCEP for Mac import settings task?

Thx

Daniele

- Daniele
Microsoft MVP System Center Cloud and Datacenter Management

Unisciti alla community italiana per System Center http://www.ugisystemcenter.org

We have a VDI(virtual desktop) environment. Each session a user gets, is a non-persistent session. So every time a user logs in, he will get a clean desktop, a new Windows 7 session.

Appv packages are streamed from the Appv 4.6 Full Infrastructure solution from Microsoft. If we could do this from SCCM2012, we would have 1 tool to manage FAT clients and stream to VDI client.

I know SCCM can do this in theory but how well does it work in "real life"? What are the advantages and disadventages if we move from Appv Full Infrastructure to SCCM2012?

How quickly after logging on to a VDI session, does a user get his shortcuts in the Start Menu of the streaming applications groups he belongs to? Immediately, after 1 minute, after 10 minutes?

Anybody with experience in this situation?

Regards, Bob

Hi, I've have a question around converting packages which have been migrated from SCCM 2007 to SCCM 2012 into applications.

Assuming these packages have been deployed to sccm 2007 clients, what happens after converting the package to an application and the 2007 clients get migrated to sccm 2012?

Is the execution history on the clients for the original package, somehow carried over to the converted application i.e. if you have a package with a mandatory deployment to 10 machines in 2007 and you convert this to an application after migrating it to 2012, do those 10 clients (after being migrated to sccm 2012) rerun the new application?

Thanks for your help.

Hi, 

Is this message in the execmgr.log default behaviour? For some reason I having problems deploying software to the client and I am wondering what "Auto Install is set to false. Do nothing" means: 

Best regards,

Kenny

Hi, 

I've imported some Applications in my ConfigMgr 2012 SP1 environment and all the wizards, distmgr.log, pkgXfer.log and content validation gives med green light. 

But none of the Applications are present in Software Center at my testklient. Nothing is wrong with the ConfigMgrClient, when i create new Application it pops up normally in Software Center. 

This issue is also the same for Packages. 

I've never used the Import part of ConfigMgr yet, so I'm guessing it could be something easy that I'm missing? Or maybe not...

Thanks in advance!

Kenny

I have deployed an application through SCCM 2012 (vbscript install) which writes to the HKCU key.  The script runs successfully with no errors and I can see the entries in the registry.  However, the detection rules fail when a clause is setup to look for the registry entry under the HKCU key.  The User Experiece is set to Install for User.  Detection rules for other applications work fine when looking the HKLM.  Is there something I am missing?

Hello Anybody,

the default App-V 5.0 Streaming (SharedContentStoreMode = on) Deployment over SCCM belongs to a HTTP-Streaming over http:\\SCCM-Server\... . The whole content flows from SCCM to the App-V-Client. Is it possible to create there a high availability solution?

Yes, we can set a second distribution point. But in th App-V-Client are always only one Distribution Source.

Is it possible to set there an clustered adress of an other IIS? Is it possible to change the publishing Distribution Source with an SMB-Path to File-Cluster? Is there a trick with Source-Root-Parameter in App-V-Client? Or are ther anything else to create a high availibility App-V-Streaming-Solution?

Yes, with App-V-Management-Server there is a high availability solution. - But we have only SCCM-Infrastruktur for App-V-Distribution.

Thank you, best regards

Daniel