Installing applications with new application model in task sequence - unstable?

I've heard that installing applications with new application model in task sequence is not as stable, as installing applications as packages in task sequence? What do you think?

The deployment type issue was resolved in R2 CU1 :
http://support.microsoft.com/kb/2938441/en-us
Benoit Lecours | Blog: System Center Dudes

Similar Messages

Installing "Applications" during the task sequence and installation enforcement

Hello,
Kind of a weird question here, so it seems like I'm seeing that if you install an application on a system during its OSD task sequence, then you later manually uninstall that application, that SCCM considers that system now out of compliance?
And then reinstalls the application as indicated in AppEnforce.log? Is this true? If so, how do you get around this behavior? I guess I thought that this application compliance only took effect when you actually deploy an application to a
system, through an actual deployment. I didn't realize that it would enforce compliance even if an application was installed during a task sequence. So if you have hundreds of systems that were imaged with the same task sequence and you have
a small handful of machines that can't have application X on it (so you want to uninstall it), which was installed via the task sequence, how do you disable this compliance enforcement and disable its automatic reinstall?
Thanks for any help you can provide.

Sorry for the delayed response, thank you both for your input. To answer both your questions, no these workstations do not have any required deployments for this application directed at them. I have confirmed that, however, they do have
the OSD task sequence deployment (that contains this application) constantly "available" to them (via only "media and PXE") as this makes it very easy for our technicians to reimage any machine whenever they need to (love that feature
by the way).
I can only assume that because they still have this task sequence deployment pointed at them is why they continue to attempt to reinstall this application when ConfigMgr finds that it's not installed anymore. In fact it does it at the same day/time
each week, which I believe is the same day/time of the week that the machines were imaged. I must have the compliance part of the clients configuration to check every 7 days for stuff like this? Anyway, that's my conclusion for now.
Since even Wally Mead felt that this must be an actual required deployment outside of the task sequence I'm really curious to see if anyone else sees this behavior. It would be fairly simple to attempt to recreate, image a machine with a task sequence
that has "application" installs included, where the deployment for it is just "available" and keep the deployment "available" after the machine is reimaged. Then after that, uninstall one of the apps that was installed
during the task sequence via an "application" and then see if it reinstalls automatically, it may wait a while (may 7 days by default?). You can see the evidence of our application reinstalling itself in the "AppEnforce.log".
Is it even remotely possible that this is a new "feature" or behavior of ConfigMgr 2012 and "Applications"?

Install application step on task sequence - application does not appear in the application list

Hi,
I am trying to create a build and capture task sequence and add some application installation steps in the process.
On Install the following applications step when I click the star to choose which applications I want to install, Office 2010 application is not listed there, even though it is available in software library
and and I've been installing it successfully from application catalog.
I tried changing the setting "Allow this application to be installed from the Install Application task sequence action instead of deploying it manually", but it had no effect.

See http://technet.microsoft.com/en-us/library/hh846237.aspx:
The applications that are installed must meet the following criteria:
It must run under the local system account and not the user account.
It must not interact with the desktop. The program must run silently or in an unattended mode.
It must not initiate a restart on its own
Torsten Meringer | http://www.mssccmfaq.de

Install CS6 Applications via SCCM Task Sequence

Hi
We have an SCCM 2012 R2 infrastructure on our network, and want to deploy Adobe CS6 applications using Windows Installer Packages created with Adobe Application Manager Enterprise Edition 3.1
We created individual packages for each application (for flexibility) following the instructions provided at this address: http://wwwimages.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/AdobeApplication ManagerEnterpriseEditionDeploy…
When we go to install the packages via an SCCM Task Sequence, the following occurs:
1     The application is installed
2     The application is not installed
We have followed the instructions provided by Adobe for the deployment, and cannot get any consistency with the installers. For example, when we run the task sequence, the following applications will be installed:
1     Dreamweaver
2     Fireworks
3     Flash Professional
4     Illustrator
5     InDesign
6     Photoshop
When we run the same task sequence again, the following applications are installed:
1     Dreamweaver
2     Fireworks
3     Illustrator
4     Photoshop
The task sequence first images the computer with Windows 7, and reboots the computer between each application being installed
I have also attempted packaging all the applications together, in a Design and Web Premium style package, with the same, unfortunate results
Please, can you help with this?

The error means RPC server unavailable. TS needs to invoke Execution Manager by RPC. This may be caused by the issue of RPC starting. I suggest you check the RPC service availability first. Another try is to add a restart computer step before installing
SQL. If still no avail, add a Delay "cmd.exe /c timeout /t 900".
Regarding the connecting network share issue, seems the network services has not been initializing or ready. Another possibility is the DHCP time out. Check the Event log and this may give you some clues of why the network is not ready or DHCP cannot get
IP address. Network Monitor can also be used to monitor the IP helper when the Client try to send DHCP request after reboot.
Juke Chou
TechNet Community Support

Non-Deployed Applications in OSD Task Sequence Are Deployed To Collection Members where OSD TS is deployed

Hello,
I have a situation where an application (which is not deployed) that is part of an OSD Task Sequence is being deployed to computers that are in the same collection my TS for OSD is deployed.
For OSD I have created an application to check the BIOS version and upgrade the BIOS if there is a newer one available. The application has numerous deployment types (13) due to various hardware models and the requirement to go to several intermediary BIOS
versions to reach the current newest version. There are dependencies configured to handle these incremental bumps.
The OSD TS is deployed to a collection that contains all windows desktop class operating systems. What I have seen happen once is that one users workstation somehow discovered and installed the BIOS Upgrade package and their BIOS was upgraded on their workstation.
I've checked the logs on several other machines and this same application has been run as well.
The application is configured "Allow this application to be installed from the Install Applications
task sequence action without being deployed" which allows it to be ran from a TS even though it is not deployed.
I have verified the application is not deployed. I have verified there are no superceedence rules configured. As I stated, there are dependencies, but all dependencies are within this one application.
What I do not understand is, how can an application that is not
deployed and is only referenced in an Operating System Deployment Task Sequence able to be ran outside the task sequence?
This is/has occurred with computers imaged with cm2012 and with computers imaged with cm2007 who have now been migrated to cm2012.
I'm fairly sure that it is due to the task sequence and where it is advertised. Computers that are not in this collection do not show the application being applied in the AppEnforce.log. If it is the TS that is causing this, how can something that is designed
to be a "sequence of tasks", allow something to occur out of that sequence?
Current environment is CM2012R2.
Any thoughts to what might be happening?
Thanks

Hello,
After working with Microsoft Support, we were able to resolve the issue.
Turns out there was something (old policies) "stuck" in the SCCM database that was causing this to be advertised outside the task sequence and not visible on the console. While they didn't call this "a bug" since it has happens with CM2007 as well, it definitely
was not normal behavior. Still not sure how that could happen as I'm 99.99% sure I never deployed this to any collection, but that's what they said.
It took several hours of support rooting through the database to figure out what was going on but after some SQL magic it was fixed. Sorry I don't have more specifics regarding the fix. MS basically said "If it happens again you can do this this and this
in the db and voila its fixed". Since I'm likely to cause more damage (messing with the database) then good if it were to happen again I'd contact them.
Anyway, this odd behavior has spooked me and I've reverted back to deploying the TS to the unknown computer collection. As much as it disappoints me to take a step back and cause more work for the guys doing the imaging, the extra safety this grants (if
something like this or worse were to happen) I think is better than an OSD task sequence gone wild.
Thanks,
Mark

Application Deployment vs Task Sequence for MS Office 2013

Afternoon All,
I'm in the process of Deploying MS Office 2013 onto our fleet of machines using SCCM 2012
Our current fleet has MS Office 2010 installed
I have created a custom .MSP file for my MS Office 2013
I'm currently just deploying MS Office 2013 by just selecting device collections and it seems to work (besides removing sharepoint workspace 2010)
I have been trying to streamline the process to clean up MS Office 2010 - I have been told to create a custom task sequence and set it as below
1. Use Office 2010 Application package set as uninstall
2. Use Office 2013 Application package set to install
They say this makes for a more clean process as it's two individual tasks being completed.
Just want to see how others went from MS Office 2010 to MS Office 2013 using SCCM 2012

Also note that using task sequences for application installs is currently not supported by Microsoft. It may still work, but it is not supported.
Daniel Ratliff | http://www.PotentEngineer.com

No Install dvd with new Macbook

Hi I had purchased a new macbook (white) Wasn't I supposed to get a install dvd with it, I checked the box and there was not one in there. Everything I have read is that there is one that comes with it... Thank you Larry.

Yes. It should be in a small white envelope-like package. If you can't find it after looking through all the packaging, call AppleCare and ask them for a replacement.

What does Apple do with new outdated models?

Lightning fried my mom's PC and she's looking for a new computer. She is looking for the cheapest mac laptop available. The new upgrade to the MacBook that was announced today is nice, but wouldn't really benefit her a whole lot. I am wondering what Apple does with all the unsold MacBooks they had on hand yesterday. They are outdated now. Is there a place my mom can find one of these for a discount? What do all the stores do with yesterday's model?

Another option is to go to the Apple retail store nearest to you and see if there are people returning their week-old MBs due to the new model coming out. The returns will be in pristine shape with full warranty, but will be sold as "refreshed" units for 10% of the list price. These are not units with problems that have been fixed, like refurbs (which I like and buy a lot), but are just people who changed their minds. You'll need to ask a sales person for what they have as "refreshed" in the back. That's the magic word.
Good luck!
MacBook w/2GB & 100GB 7200 rpm hd, G5 iMac, 15PB, G4 iMac, Mac OS X (10.4.8) G4 QS, AX, 3G iPod, Shffl, nano.

KB2509007 did not fix problem with Install Updates hanging at 0% during OSD task sequence

Hi everybody. We recently started building our Build & Capture Task Sequence for our Windows 7 gold image. However, I keep running into the problem where the Install Software Updates step keeps hanging at "downloading updates 1 of 164 (0%).
This is a known issue that is supposed to be addressed with hotfix KB2509007. I followed the instructions
here to install the hotfix on my site server. I then added the PATCH= argument to my "Setup windows and ConfigMgr" step in my TS. But still my TS was hanging in the same spot.
Then I found
this page, which says that there is another known issue with KB2509007, and the order in which it is installed along side other hotfixes (such as R3). So I followed those instructions, and confirmed that UpdatesHandler.dll is at version 4.00.6487.2188,
and BOOM, the updates installed and I captured my gold image. This was about a week ago.
Well, since then, we have had a patch Tuesday, and I am trying to run by Build & Capture TS again to integrate the latest updates into my gold image, but now my TS is hanging at 0% again! I have confirmed that UpdatesHandler.dll is at the correct version,
so I am unsure what the issue could be now.
Does anybody have any experience with this issue? Thanks in advance for any help!
UPDATE: I re-ran my TS, and now the updates are installing. I'm not sure why the behaviour is so inconsistent though...

Hi everybody. We recently started building our Build & Capture Task Sequence for our Windows 7 gold image. However, I keep running into the problem where the Install Software Updates step keeps hanging at "downloading updates 1 of 164 (0%).
This is a known issue that is supposed to be addressed with hotfix KB2509007. I followed the instructions
here to install the hotfix on my site server. I then added the PATCH= argument to my "Setup windows and ConfigMgr" step in my TS. But still my TS was hanging in the same spot.
Then I found
this page, which says that there is another known issue with KB2509007, and the order in which it is installed along side other hotfixes (such as R3). So I followed those instructions, and confirmed that UpdatesHandler.dll is at version 4.00.6487.2188,
and BOOM, the updates installed and I captured my gold image. This was about a week ago.
Well, since then, we have had a patch Tuesday, and I am trying to run by Build & Capture TS again to integrate the latest updates into my gold image, but now my TS is hanging at 0% again! I have confirmed that UpdatesHandler.dll is at the correct version,
so I am unsure what the issue could be now.
Does anybody have any experience with this issue? Thanks in advance for any help!
UPDATE: I re-ran my TS, and now the updates are installing. I'm not sure why the behaviour is so inconsistent though...

How to create ArchLinux install CD (with new kernel+extra tools)?

I am planning to buy a HP nx6325 notebook. Unfortunately, it has some ACPI issues (thermal) which I think are solved in the git kernel version (they're not even in 2.6.20.1 I think). The problem is quite serious as it seems to be causing thermal problems.
I'd like to create a new ArchLinux install CD with the latest (git) kernel + some extra packages. I plan to backup the entire HDD (100GB) over network and I need something efficient to read NTFS partitions (=ntfsclone)
Unfortunately, the default ArchLinux install CD does not have this package. (as a request: maybe the ArchLinux install CD could also serve as a rescue Live CD.)
I found the "archboot" package - apparently, creating an install CD is straight-forward. I have looked for documentation on how to
* add tools to the ArchLinux install CD (available directly, without install) - I'd like to add "ntfsclone"+dependencies
* change the kernel (using archboot)
* (for the future) add packages available for install
I couldn't find anything. Does anybody know where I could find such information?
Many thanks.
Last edited by IceRAM (2007-02-20 21:56:06)

The up-to-date versions of both squashfs and unionfs can no longer be built as external modules - they exist only as kernel patches. Unionfs will be merged in to vanilla at some point (it just made it into -mm last month), but that won't be for another while - at the moment, it's looking like 2.6.22 or after.

Deploying the SCCM 2012 Client to WES 7 devices that are locked down with the FBWF using 2007 task sequence via WEDM.

I'm wondering how people are migrating their embedded devices that are using the FBWF. I've done some googling and it seems like most people are just re-imaging the devices and after migrating a single device i see why. Its not a pretty process. This will
be a long description but ultimately my question stems more from trying to find a better way to execute the device migration from 2007 to 2012.
Some back ground on my situation might be in order here. I'm in the process of wrapping up our 2007 to 2012 migration. We have a 2007 infrastructure that was a central server with 2 primaries and 286 secondary site servers. I've consolidated that to a single
2012 primary site server that hosts all the main roles. There are 2 more servers in the data centers both operating solely as push distribution points I'll refer to them as 2012 01 02 and 03. I'm over half way through the migration and so far haven't needed
to offload any site roles. There are almost 10,000 clients now reporting to the 2012 site server and almost a 100 field servers pulling content from 2012 02 as their source dp as pull dp is the only way forward for this many devices. I've read the horror stories
of trying spin up 200 plus push dps. We are running PKI. I'm at the point now where i need to start migrating the Windows Embedded Seven Standard clients that have the 2007 sccm client on them with WEDM for write filter handling.
What i'm wondering is if anyone has any pointers for me regarding migrating the WES 7 devices. My plan that i've come up with is to somehow script the process using a 2007 WEDM Task Sequence to try and migrate them over to 2012. Things are complicated as
I need to somehow script the install, the policy checkin, hardware inventory, software inventory, and validate the SCEP client installs before I reboot the device one last time to enable the FBWF. How I handled the SCCM 2007 client install on these devices
when they were provisioned was to just create a batch file that would sleep for ten minutes then check to see if the inventoryagent.log file had been created yet. I realize now that is inefficient as i can kick off the inventory using a WMI method once the
client has installed. Also I need to make sure the machine gets its first policy as that is how it creates the communication using PKI through that first policy transfer and that also finalizes the client install. The biggest piece i'm uncertain about in this
regard is the SCEP client.
I had to change the SCEP client install from yes to no in the default client settings as we have some Mcaffee servers that can't have the SCEP client on them. I have incremental updates enabled on the collection that has the policy that installs the SCEP
client but this will take an unknown amount of time unless i force the environment to update as the device starts in 2012 install, or if I could kick off the SCEP isntall... IDK. I'm also wondering if i should keep the device in the migration process until
i validate it has its proper scep policy applied which I believe can be validated by a registry key somewhere.
Once the 2012 client gets installed will that cause it to lose its place within the 2007 Task Sequence? Considering its going to take a minimum of 2 reboots I'd normally use the task sequence to handle its progression through the process.
I'm also considering trying to use an Orchestrator runbook, as that would be a good way to keep track of the migration process as each device migrates. Especially since this might take several seperate scripts.
I'm going to take a stab at scripting the migration process, but if anyone has any pointers that might make this a less complicated I'd really appreciate it as I've got about 3000 of these devices that need to be migrated over. The other things i've learned
the hard way is any time you have something this complicated over the course of 3000 devices you will run into unknowns and the failure rate increases. I'm in the precarious position of having to not only build this process out but in some situations have
it complete in the shortest amount of time possible as we have sites running 24x7. I know the end users behavior all to well and they will just keep hitting the power button sometimes even though their not supposed to so they can get their device functional
again. In those situations i'd end up, if i'm lucky with a device that no longer has a healthy SCCM client in either environment and the write filter disabled.
So like i said any pointers anyone could throw my way i'd really appreciate. I manually went through the migration process on a single device for proof of concept and ended up with almost 2 pages of pseudo code for my migration script/scripts.
Thanks,
-K.R.

Hi,
In R2 there are some new variables you can use to solve this,
http://ccmexec.com/2014/12/smstsmplistrequesttimeout-value-in-milliseconds/
In Sp1 though adding a step to sleep for 2-5 minuter after reboot and before the application install step is a common workaround.. a powershell command with "Start-Sleep
-s 120" should do it.
/Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Service Pack for Proliant installing successfully but returning failure in OSD task sequence

Building bare metal servers with SCCM 2012 SP1 CU2 OSD and running into an issue with HPs where they attempt to install the Service Pack for Proliant 2013.02.0. I am using a package with a program. Here is the program command line:
Hpsum.exe /use_latest /allow_non_bundle_components /current_credential /silent
The application installs successfully but there is a distinct delay and then errors thrown that fails the TS. Setting 'continue on error' is a work around but not what I want to have in the production environment. How can I get around this issue?
This is the same exact package and program that ran perfectly fine in SCCM 2007, but we are seeing this as a new issue since the migration to SCCM 2012.
I'd like to solve this issue as well as get rid of the "Waiting for job status notification....InstallSoftware"
Any suggestions?
SMSTS.LOG
Invoking Execution Manager to install software InstallSoftware
12/3/2013 9:59:49 AM 1568 (0x0620)
Installing software for PackageID='WCD002D2' ProgramID='Silent install' AdvertID='WC120008' has started, jobID='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 9:59:50 AM
1568 (0x0620)
Setting TSEnv variable 'SMSTSInstallSoftwareJobID_WCD002D2_WC120008_Silent install'='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 9:59:50 AM
1568 (0x0620)
Waiting for installation job to complete.. InstallSoftware
12/3/2013 9:59:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:00:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:00:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:01:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:01:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:02:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:02:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:03:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:03:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:04:20 AM 1568 (0x0620)
Launching command shell. OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
Windows station: WinSta0 OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
Desk"Apple-tab-span" style="white-space:pre;"> OSDSetupHook
12/3/2013 10:04:25 AM 2696 (0x0A88)
executing command: C:\WINDOWS\system32\cmd.exe /k
OSDSetupHook 12/3/2013 10:04:25 AM
2696 (0x0A88)
executed command: C:\WINDOWS\system32\cmd.exe /k
OSDSetupHook 12/3/2013 10:04:25 AM
2696 (0x0A88)
Waiting for job status notification... InstallSoftware
12/3/2013 10:04:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:05:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:05:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:06:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:06:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:07:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:07:50 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:08:20 AM 1568 (0x0620)
Waiting for job status notification... InstallSoftware
12/3/2013 10:08:50 AM 1568 (0x0620)
CompleteExecution received InstallSoftware
12/3/2013 10:09:00 AM 3320 (0x0CF8)
CompleteExecution processed InstallSoftware
12/3/2013 10:09:00 AM 3320 (0x0CF8)
Received job completion notification from Execution Manager
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Installation completed with exit code 0x80070001
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Installation failed with error (0x80070001)
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Setting TSEnv variable 'SMSTSInstallSoftwareJobID_WCD002D2_WC120008_Silent install'=''
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
GetExecRequestMgrInterface successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Releasing job request, jobID='{8B4082A9-9477-4D1F-9DEC-6A3F19EC3F6F}'
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Releasing of Job Request successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
CompleteJob successful InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Entering ReleaseSource() for D:\_SMSTaskSequence\Packages\WCD002D2
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
reference count 1 for the source D:\_SMSTaskSequence\Packages\WCD002D2 before releasing
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Released the resolved source D:\_SMSTaskSequence\Packages\WCD002D2
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
pInstall->Install(sPackageID, sProgramName), HRESULT=80070001 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)
InstallSoftware 12/3/2013 10:09:00 AM
1568 (0x0620)
Install Software failed, hr=0x80070001 InstallSoftware
12/3/2013 10:09:00 AM 1568 (0x0620)
Process completed with exit code 2147942401
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Failed to run the action: HP Server Pack for ProLiant 2013.02.
Incorrect function. (Error: 80070001; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
MP server http://MP_server.company.com. Ports 80,443. CRL=false.
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Setting authenticator TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Set authenticator in transport TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Sending StatusMessage TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Setting message signatures. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Setting the authenticator. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
CLibSMSMessageWinHttpTransport::Send: URL: MP_server.company.com:80 CCM_POST /ccm_system/request
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Request was succesful. TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Set a global environment variable _SMSTSLastActionRetCode=-2147024895
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Set a global environment variable _SMSTSLastActionSucceeded=false
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Clear local default environment TSManager
12/3/2013 10:09:00 AM 3372 (0x0D2C)
Let the parent group (System Management Install) decides whether to continue execution
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
The execution of the group (System Management Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)
Failed to run the last action: HP Server Pack for ProLiant 2013.02. Execution of task sequence failed.
Incorrect function. (Error: 80070001; Source: Windows)
TSManager 12/3/2013 10:09:00 AM
3372 (0x0D2C)

Hello Guys!
HP ProLiant Support Pack / Service Pack uses different Exit Codes, due to that this software support other operating systems than Windows. Therefore HP has standardized to use other Exit Codes, which Windows Detect as failures.
HPSum Exit Codes:
ExitCode 1 = "Installation Successful"
ExitCode 2 = "Installation Successful, but a reboot is required"
ExitCode 3 = "Installation was canceled, or no components were updated"
EcitCode 9009 = "Installation did not complete. Check the path and make sure that the Installation exists at the specified location"
HP recommends to use following Batch File to workaround this issue for SCCM:
=======================START_BatchFile=============================
:Init
@Echo Off
Cls
:Main
Echo HP Proliant Service Pack Setup
Echo Source : %~dp0
Echo ===============================================================================
Echo Installing the HP Proliant Service Pack Setup
Echo Command: "%~dp0hpsum.exe" /use_latest /target:%COMPUTERNAME% /force /Use_WMI /s
"%~dp0hpsum.exe" /use_latest /target:%COMPUTERNAME% /force /Use_WMI /s
:CheckForErrors
Echo HP Proliant Service Pack Stauts:
If "%errorlevel%"=="0" (
     Echo *******************************************************************************
Echo                            INSTALLATION FAILED!
Echo *******************************************************************************
exit 1
If "%errorlevel%"=="1" (
     Echo Installation Successful!
     exit 0
If "%errorlevel%"=="2" (
     Echo Installation Successful, but a reboot is required.
     exit 3010
If "%errorlevel%"=="3" (
     Echo Installation was canceled, or no components were updated
     exit 0
If "%errorlevel%"=="9009" (
     Echo Installation did not complete. Check the path and make sure that the
Echo Installation exists at the specified location:
Echo Path: %~dp0
Exit 1
:End
Echo An unknown status code was returned from the PSP.
Echo This status code is [%errorlevel%]. This will be treated as a success,
Echo but please check the installation to make sure it completedly properly!
Exit 0
=======================STOP_BatchFile=============================
God Luck!
Best Regards Anders Horgen

Install Software Updates fails (timeouts) during OSD Task Sequence

Hi
As one of the lasts steps in our OSD Task Sequence we have an "Install Software Update" step where "Mandatory Software Updates" is choosen. It worked a week ago, but now the step fails with error code 0x800705B4
(This operation returned because the timeout period expired.)
When examining the WindowsUpdate.log I see an error followed by several minutes without log activity:
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:999
1632 4e4
COMAPI - Updates found = 260
2014-02-18 10:39:13:999
1632 4e4
COMAPI ---------
2014-02-18 10:39:13:999
1632 4e4
COMAPI -- END -- COMAPI: Search [ClientId = CcmExec]
2014-02-18 10:39:13:999
1632 4e4
COMAPI -------------
2014-02-18 10:39:18:835
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 11:08:12:225
416 4dc
AU AU received policy change subscription event
2014-02-18 11:08:12:334
416 4dc
AU AU Options changed from policy.
2014-02-18 11:08:12:334
416 4dc
AU Successfully wrote event for AU health state:0
2014-02-18 11:08:12:334
416 4dc
AU ########### AU: Policy change processed ###########
When examining the WUAHadler.log - again there is no log activity during the Software Update step.
Its a WSUS Update Source type ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}), adding it.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Existing WUA Managed server was already set (http://<servername>:8530), skipping Group Policy registration.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Added Update Source ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}) of content type: 2
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Scan results will include all superseded updates.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Async searching of updates using WUAgent started.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Async searching completed. WUAHandler
18-02-2014 10:39:13 1108 (0x0454)
Successfully completed scan. WUAHandler
18-02-2014 10:39:15 2016 (0x07E0)
Removed Update Source ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}) of content type: 2
WUAHandler 18-02-2014 11:06:25
1160 (0x0488)
CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3;
for bundles WUAHandler
18-02-2014 11:09:25 2232 (0x08B8)
The Software Update Step started at 10:27 and the timeout came at 11:05.
Any ideas why the step times out? Or which logs I should look at?
Regards,
FC

PolicyEvaluator.log:
No errors. The last event is:
Received notification that Local policy has changed.
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:11
1692 (0x069C)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:C2E937AA-CF24-420F-AD81-E8CEADBD7649";
DateTime = "20140219095123.565000+000";
PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 1748;
ThreadID = 1768;
PolicyAgent_PolicyEvaluator
19-02-2014 10:51:23 1768 (0x06E8)
Forcing settings update for local policy change.
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:23
2900 (0x0B54)
Updating settings in \\.\root\ccm\policy\machine\actualconfig
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:33
2900 (0x0B54)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:C2E937AA-CF24-420F-AD81-E8CEADBD7649";
DateTime = "20140219095144.641000+000";
PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 1748;
ThreadID = 2900;
PolicyAgent_PolicyEvaluator
19-02-2014 10:51:44 2900 (0x0B54)
UpdatesHandler.log:
No errors. A couple of lines:
Successfully initiated scan. UpdatesHandler
19-02-2014 10:54:10 1768 (0x06E8)
Updates scan completion received, result = 0x0.
UpdatesHandler 19-02-2014 10:55:23
3572 (0x0DF4)
UpdatesStore.log
No errors. Just quering updates, and the last line:
Querying update status completed successfully.
UpdatesStore 19-02-2014 10:56:27
3300 (0x0CE4)
In the smsts.log I found an interesting thing:
Successfully initiated RefreshUpdates operation
InstallSWUpdate 19-02-2014 10:51:37
3424 (0x0D60)
Waiting for RefreshUpdates complete notification from Updates Deployment Agent
InstallSWUpdate 19-02-2014 10:51:37
3424 (0x0D60)
FALSE, HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1273)
InstallSWUpdate 19-02-2014 11:21:37
3424 (0x0D60)
Timedout waiting for updates refresh complete notification
InstallSWUpdate 19-02-2014 11:21:37
3424 (0x0D60)
It times out after exactly 30 minutes. Does 2012 have the same "feature" as 2007? (http://support.microsoft.com/kb/2009754/da)
Still the last event in windowsupdate.log is:
2014-02-19 10:55:37:251
324 dd0
Report CWERReporter finishing event handling. (00000000)
Regards,
FC

Not able to push batch script for installing IIS all features using SCCM 2012 task sequence

Hey Guys, I am working for this from a long time but not able to make it work, I am using following batch script for installing IIS using SCCM 2012 task sequence:
Dism.exe /online /Enable-Feature /FeatureName:IIS-WebServerRole /FeatureName:IIS-WebServerRole /FeatureName:IIS-WebServer /FeatureName:IIS-ApplicationDevelopment /FeatureName:IIS-Security /FeatureName:IIS RequestFiltering /FeatureName:IIS-NetFxExtensibility
/FeatureName:WAS-WindowsActivationService /FeatureName:WAS-ProcessModel /FeatureName:WAS-NetFxEnvironment /FeatureName:WAS-ConfigurationAPI /FeatureName:NetFx3 /FeatureName:WCF-HTTP-Activation /FeatureName:WCF-NonHTTP-Activation /FeatureName:IIS-WebServerManagementTools
/FeatureName:IIS-ManagementConsole /FeatureName:IIS-ManagementScriptingTools /FeatureName:IISIIS6ManagementCompatibility /FeatureName:IIS-ManagementService /FeatureName:IIS-Metabase /FeatureName:IIS-WMICompatibility
When I run this script as admin by right click on it and select "run as a administrator" the script works fine but when I pushed the script as a software package or a step in OSD task sequence, nothing happens. I also tried
run command line option but no luck. Please help me with this.
Thanks,
VST

1. When I used "run command line" option I found following errors in smsts.log:
Remediation failed. Code 8027000C TSManager 1/2/2014 2:32:12 PM 2720 (0x0AA0)
Remediation failed with error code 8027000C TSManager 1/2/2014 2:32:12 PM 2720 (0x0AA0)
Remediation failed. Code 8027000C TSManager 1/2/2014 2:34:16 PM 2092 (0x082C)
Remediation failed with error code 8027000C TSManager 1/2/2014 2:34:16 PM 2092 (0x082C)
Failed to run the action: Run Command Line.
Unknown error (Error: 800F080C; Source: Unknown) TSManager 1/2/2014 2:34:32 PM 2092 (0x082C)
Failed to delete directory 'C:\_SMSTaskSequence' TSManager 1/2/2014 2:34:33 PM 2092 (0x082C)
SetNamedSecurityInfo() failed. TSManager 1/2/2014 2:34:33 PM 2092 (0x082C)
SetObjectOwner() failed. 0x80070005. TSManager 1/2/2014 2:34:33 PM 2092 (0x082C)
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 1/2/2014 2:34:33 PM 2092 (0x082C)
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence TSManager 1/2/2014 2:34:33 PM 2092 (0x082C)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 TSManager 1/2/2014 2:34:33 PM 2092 (0x082C)
RegQueryValueExW failed for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 1/2/2014 2:34:34 PM 2092 (0x082C)
GetTsRegValue() failed. 0x80070002. TSManager 1/2/2014 2:34:34 PM 2092 (0x082C)
ReleaseRequest failed with error code 0x80004005 TSManager 1/2/2014 2:34:34 PM 2092 (0x082C)
RegQueryValueExW failed for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram OSDSetupHook 1/2/2014 2:34:35 PM 360 (0x0168)
GetTsRegValue() failed. 0x80070002. OSDSetupHook 1/2/2014 2:34:35 PM 360 (0x0168)
2. We are not using MDT in our environment so I ant use add features and roles option.
3. The script is running fine when we run it manually.

Installed Aperture with new Snow Leopard and it won't open

I just got Aperture 2.0 and it installed fine but when I tried to open the application, its says it does not work with this version of Leopard. Is there a fix for this?

ScharadL wrote:
So essentially, you'd have to purchase the 2.14 update from the mac store?
No. He's saying he used the serial number that came with 2.x when he bought it, and it will work with the 2.14 download.
There seems to be a catch 22: Aperture 2.1 won't work with Snow Leopard, and the 2.14 update won't work because it can't find 2.1. The work around Daniel found is to download the 2.14 trial then authorize it with the 2.1 serial number.
See if it works for you ,and let us know.
DLS

Installing applications with new application model in task sequence - unstable?

Similar Messages

Maybe you are looking for