Second Task Sequence to collection. Will it auto-deploy?

We have a SCCM 2007 R3 setup with a "All Windows 7 Computers" collection with two sub-collections for Desktop and Mobile computers.
There is a Task Sequence on it with Windows 7+Office 2010, and I now want to add a second Task Sequence which installs Windows 7+Office 2013.
Creating a seperate collection and adding a test computer to it and adding the two Task Sequences (new advertisement for each) works fine when I PXE boot. I can then select between the two Task Sequences.
When I added the computer it showed no sign of wanting to deploy a Task Sequence using the Computer Configuration Manager, but I do wonder (read: need to be damn sure about this) what happens if I add the second Task Sequence to the collection holding all my
other computers.
I can't have all computers suddenly deploying the Windows 7+Office 2013 Task Sequence of course.
Can anyone tell me if this is safe to do or will I get in trouble, loose my job, name and shame, etc?

Is your intention o make it a mandatory advert or not? That's really the key factor. I'm assuming by your statement that its not so just make sure that you don't add a [mandatory] schedule to the advert. Also, if your intention is to only make to available
via PXE for new computer/bare metal scenarios, set the OS requirements criteria on the properties of the TS to be only applicable to Windows Vista or Windows 2000 systems. This criteria is not evaluated during a bare metal WinPE boot but will prevent any non-PXE
(or media) booted systems from seeing the TS.
Jason | http://blog.configmgrftw.com | @jasonsandys

Similar Messages

Failed to run task sequence. Error occurred while starting the task sequence (0x8007000E)

Hi there
Patch Tuesday yesterday (10th June2014). As always we deploy new patches first to a test collection where Windows 7 updates automatically apply.
Upon trying to rebuild any of the machines in this test collection, we were presented with the following error message:
Failed to run task sequence. Error occurred while starting the task sequence (0x8007000E)
After searching about this, I found this page from Niall Brady, which explained the problem:
http://www.niallbrady.com/2013/05/17/after-selecting-a-task-sequence-in-configuration-manager-2012-sp1-you-receive-threadtoresolveandexecutetasksequence-failed-code0x8007000e-in-smsts-log/
So I removed some of the machines from the test Windows update collection, and as per the advice in the above link, the error was gone and those machines could be built successfully.
So the problem is there were too many many policies downloaded (apps, packages and most of all updates) for the task sequence ram to store, hence the error.
Now...
...I have a question.
The next logical step to my mind is to patch our OS image with all missing patches, so these do not have to be downloaded at build time. Niall mentions this as one of the resolutions to this issue.
However there seems to be some confusion over whether this would actually make a difference.
I read through this link:
http://social.technet.microsoft.com/Forums/en-US/7e597b44-2586-4063-b6d0-cec48a7c11c7/sccm-2012-task-sequence-failure-0x8007000e?forum=configmanagerosd
There's seems to be no consensus on this.
Is SCCM 2012 clever enough to - when the task sequence is first started - to download ONLY the updates (policies) it detects as NOT present in the OS image...
or
Will it simply try to download policies for ALL items deployed to it, whether the updates are present in the OS image or not?
I will be disappointed if SCCM 2012 SP1 CU2 isn't clever enough to only download policies at build time for the apps, packages and updates it detects as needed.
I'd be grateful for some clarity on this.
Regards,
John, Glasgow.

Hi Jason
Thank you for replying, I appreciate it.
1) We currently have 15 or 16 software update groups for Office updates, dating back a month or two. The latest software update group contains all the patches in the previous software update groups plus the patches released on 10th June. Do you recommend
deleting all but the latest software update group?
2) I'm almost reluctant to ask this, but based on what you have advised, is it the case that when the task sequence executes, it will download policies for each update in each software update group regardless of whether it has already downloaded a policy
for an update in a previous software update group? So in effect it's downloading policies (for updates) it has already downloaded?
3) I'm not clear on why there would be no policy for an image; in Niall Brady's informative page on the 8007000E error, he writes the following:
"The reason it has run of space could be due to four possibilites: too many applications, too many Windows updates, too many Task Sequence steps, too many referenced packages'.
Can you shed some light on why there isn't a policy for an image?
Thanks again for replying,
John.

SCCM 2012 MDT 2012 UDI Require domain credentials to run task sequence

We are in the process of moving to SCCM 2012 integrated with MDT 2012 for OSD from using MDT 2012 by itself. We're trying out UDI task sequences and have noticed a pretty gaping hole in functionality vs MDT 2012 by itself: password protecting a task sequence.
In MDT 2012 there was a built-in feature that required domain credentials to run a task sequence. If one exists using SCCM/MDT 2012, I haven't been able to find it. I've only found stuff like this http://www.windows-noob.com/forums/index.php?/topic/2336-password-protect-a-task-sequence/ which
would allow you to set a password, but not authenticate against AD. So, I'm wondering if there are any options to protecting a task sequence with domain authentication?
My understanding is that the Refresh and Replace StageGroup only run when you kick off a UDI task sequence in Windows. That means I have to make a task sequence available to the Configuration Manager Client in order for a tech to run a Refresh/Replace. And,
that in turn means that the UDI task sequence will be visible to all users since it needs to be available to their computer. Or, am I completely missing how UDI OSD should flow? If so, then I hope someone can correct me.
I'd appreciate any help or advice you can give. Thanks.

Hi,
I am sorry to say that you are correct in your conclusions. There is no builtin way in ConfigMgr/MDT/UDI to require a domain username/password to run a task sequence, your option from Windows-noob.com is one way of solving it.
Regards,
jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec
Thanks for the info. What about workflow? How do you usually handle UDI in Replace and Refresh scenarios? Do you deploy the task sequence to collections that users can access?

Multitasking in Task Sequence SCCM 2012

Hello,
Is it possible to set Multiple Scheduling in Task Sequence. And if yes what schedule will the system use for deployment.
For example if we are deploying a application using the task sequence by scheduling 2 different schedule (1st. Log on & 2nd Asap). Which is the one will the system use first for the deployment of the application on the Client machine.
Thanks,
Kavin

Hi,
It's possible to set multiple Scheduling when you deploy the Task Sequence. Generally we don't deploy a Task Sequence twice to the same collection with different scheduling, because that makes no sense.
If the Task Sequence is required, the system would use which deployment should be determined by the time we sheduled.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Running a Task Sequence within a Task Sequence

We are running an SCCM 2012 R2 setup for OSD, WSUS, App Deployment and Endpoint Protection.
To simplify the management of drivers across several OSD task sequences, I'd like to have one "master" task sequence containing only Apply Device Drivers with model specific targeting that is referenced from the OSD task sequences.
Why would I want this? With every new computer model that is being added to the environment (We are currently supporting 20 different computer models, and the list keeps growing), I have to update one task sequence with model specific targeting for a driver
package, then copy all the changes to several other task sequences. To try to simplify the administration and reduce the chance of human error and ensure consistency across the board, this would probably be the best way to ensure this.

Out-of-the-box you can't start one task sequence within another task sequence. A few workarounds:
You can make your task sequence put your computer object in a new collection which has a new task sequence targeted, but that probably won't perform that well;
You can target multiple task sequences to the same collection and try to use PowerShell to trigger a new task sequence. For example something like this (I have never tried to use this from a task sequence):
http://powersheller.wordpress.com/2012/05/24/sccm-2012-execute-task-sequence-with-powershell/
You can try to merge your current task sequences.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Since what I'd like to do is to "pause" the current task sequence until the second task sequence has run and then resume the current task sequence (Just the apply drivers step) I don't think either would be great options. I guess the copy paste
option is what is left for me.
Thanks for replying and your suggestions

Image not displaying in the Task Sequence Wizard. SCCM2012

This is my question, so I will post the link here.
http://community.spiceworks.com/topic/925727-image-not-displaying-in-the-task-sequence-wizard-sccm2012
Bryan
I captured an image from a PC that I am preparing to be deployed with Office 365. Once I captured
the image, I went to the software library to add the operating system image. That seemed to go on without any issue, but when I look at the summary, I see the big yellow globe saying "in progress" it has not changed since yesterday afternoon.
I then created the task sequence for this image
to be deployed under Software Library, Task Sequences. When I selected the references tab, everything seemed to be in order with the exception of the "operating system image" under type. It was/is showing 0.0% Compliance.

So, the problem described in the other forum post does not match the title of this thread. Are you trying to address two different things? These are unrelated btw.
For the issue in the other thread, you'll have to troubleshoot your content distribution to the selected DP. The distmgr.log and pkgxfermgr.log (assuming you chose to distribute the image to a DP directly attached to your primary site) are the places to
start and will show you exactly what's going on.
As for the title of this thread, we'll need a lot more info to help you there.
Finally, I would suggest you copy your questions from other sources into the thread -- this will help other folks in the future that may stumble upon this thread and will prevent any confusion.
Jason | http://blog.configmgrftw.com | @jasonsandys

Maintenance windows applies only to task sequences doesn't work

Problem:
SCCM 2012 R2 CU4
Task sequence deployment run outside maintenance windows when the maintenance windows is set to apply only to task sequences.
When the maintenance windows is set to apply to All deployments, the task sequence deployment run inside maintenance windows as expected.
The maintenance task defined was as:
Name: Maintenance Windows of Collection Coll_A
Time: 10:30am to 06:00am
Date: 20th March 2015
Apply this schedule to: Task Sequences
The task sequence defined was as:
Deployed to Collection Coll_A
Time: Run as soon as possible
The task sequence run at 9:48am on a workstation that is member of Coll_A.
There aren't other maintenances windows on others collections.
Below the workstation's serviceWindowsManager.log:
https://onedrive.live.com/redir?resid=BFBF530F33D996FD!123&authkey=!AI0dFPZ89XCL7xs&ithint=file%2clog

When was the client added to the collection? Was it able to retrieve those MW policies before it received the TS?
Torsten Meringer | http://www.mssccmfaq.de
1_the client was added at the 9:30am.
2_Yes it is.
I have done another test and the result is the same:
_ first setting up the maintenance windows in Coll_A,
_ then insert the client in Coll_A and force a machine policy evaluation
_then deploy the task sequence in collection Coll_A

Create a prompt using MDT 2012 in SCCM 2012 OSD task sequence

Hi Experts,
I need some help with SCCM 2012 Task sequence using MDT 2012.
Here is the scenario:I want to build a task sequence where it will propmt whether the technican want to build a new build or refresh. Based on the technicians choice the task sequence will perform specific actions.
We can create the prompt using HTA or VBScript or some otherways.
But the requiremnt for us is to Use ONLY MDT 2012, not any other ways.
Is it possible to do like the above with UDI?
Please can someone shed some light how to do will be great.
Thanks in advance,

Hi,
UDI may achieve what you want. Take a look at the blogs below.
http://blogs.technet.com/b/anilm/archive/2012/06/01/integrating-mdt-2012-rtm-with-configuration-manager-2012-rtm-part-3-creating-and-deploying-a-udi-task-sequence.aspx
http://heinrichandsccm.blogspot.com/2013/04/how-to-setup-and-configure-sccm-2012.html
Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Juke Chou
TechNet Community Support

Deploying a Task Sequence is stuck at Downloading, 0%

Hi,
I want to deploy a custom task sequence that performs the following Tasks:
Run Program to disable the write filter.
Perform software distribution and software update activities
Run Program to enable the write filter
I did everthing like ist explained here:
System Center Configuration Manager Team Blog
How to Manage Windows Embedded Write Filters Using System Center 2012 Configuration Manager
On the client, in Software Center, the Task Sequence is stuck at "Downloading, 0% complete".
I tried the same with a simple vbs Script which opens a MsgBox, the result is exactly the same...
Which logs can i use to search for errors? What is causing this error?

cscript.exe is running in the taskmgr, but it's no terminated after the the deployment.
smsts.log: (I've deleted D:\_SMSTaskSequence manually...)
==========[ TsProgressUI started in process 624 ]========== TsProgressUI 5/27/2014 2:01:30 PM 2288 (0x08F0)
Registering COM classes TsProgressUI 5/27/2014 2:01:30 PM 2288 (0x08F0)
sbModulePath = C:\Windows\CCM\TsProgressUI.exe TsProgressUI 5/27/2014 2:01:30 PM 2288 (0x08F0)
Shutdown complete. TsProgressUI 5/27/2014 2:01:30 PM 2288 (0x08F0)
Successfully intialized Logging for TS Manager. TSManager 5/27/2014 2:01:32 PM 3532 (0x0DCC)
Commandline: C:\Windows\CCM\TSManager.exe /service TSManager 5/27/2014 2:01:32 PM 3532 (0x0DCC)
Successfully registered Task Sequencing COM Interface. TSManager 5/27/2014 2:01:32 PM 3532 (0x0DCC)
Executing as a service TSManager 5/27/2014 2:01:32 PM 3532 (0x0DCC)
Started ServiceMain TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Task Sequence Manager executing as service main thread TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Waiting for CcmExec service to be fully operational TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
CcmExec service is up and fully operational TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Remediating TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
NAP is not enabled. Skipping quarantine check. (Code: 80040154) TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Remediation returned 00000000 TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
System is not in quarantine. Continuing with task sequence. TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Parsing task sequence . . . TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Task sequence schema version is 3.00 TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Current supported schema version is 3.10 and 3.00 TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Starting Task Sequence Engine . . . TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
**************************************************************************** TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Set a global environment variable _SMSTSNextInstructionPointer=0 TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Set a global environment variable _SMSTSInstructionTableSize=1 TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Set a global environment variable SMSTSRebootRequested= TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Set a global environment variable SMSTSRebootDelay= TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Set a global environment variable SMSTSRebootMessage= TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Set a global environment variable SMSTSRebootReason= TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Set a global environment variable SMSTSRetryRequested= TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
The task execution engine started execution TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Set authenticator in transport TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Default CSP Type is 24 TSManager 5/27/2014 2:01:32 PM 3900 (0x0F3C)
Start executing an instruction. Instruction name: Run Command Line. Instruction pointer: 0 TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Set a global environment variable _SMSTSCurrentActionName=Run Command Line TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Set a global environment variable _SMSTSNextInstructionPointer=0 TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Set a local default variable SMSTSDisableWow64Redirection TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Set a local default variable _SMSTSRunCommandLineAsUser TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Set a global environment variable _SMSTSLogPath=C:\Windows\CCM\Logs\SMSTSLog TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Expand a string: smsswd.exe /run: cmd.exe /c start "" cscript.exe D:\Test.vbs TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Expand a string: TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Start executing the command line: smsswd.exe /run: cmd.exe /c start "" cscript.exe D:\Test.vbs TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
!--------------------------------------------------------------------------------------------! TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Expand a string: WinPEandFullOS TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Executing command line: smsswd.exe /run: cmd.exe /c start "" cscript.exe D:\Test.vbs TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
[ smsswd.exe ] InstallSoftware 5/27/2014 2:01:34 PM 3968 (0x0F80)
PackageID = '' InstallSoftware 5/27/2014 2:01:34 PM 3968 (0x0F80)
BaseVar = '', ContinueOnError='' InstallSoftware 5/27/2014 2:01:34 PM 3968 (0x0F80)
ProgramName = 'cmd.exe /c start "" cscript.exe D:\Test.vbs' InstallSoftware 5/27/2014 2:01:34 PM 3968 (0x0F80)
SwdAction = '0001' InstallSoftware 5/27/2014 2:01:34 PM 3968 (0x0F80)
Working dir 'not set' InstallSoftware 5/27/2014 2:01:34 PM 3968 (0x0F80)
Executing command line: Run command line InstallSoftware 5/27/2014 2:01:34 PM 3968 (0x0F80)
Process completed with exit code 0 InstallSoftware 5/27/2014 2:01:34 PM 3968 (0x0F80)
Command line returned 0 InstallSoftware 5/27/2014 2:01:34 PM 3968 (0x0F80)
Process completed with exit code 0 TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
!--------------------------------------------------------------------------------------------! TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Successfully completed the action (Run Command Line) with the exit win32 code 0 TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Set authenticator in transport TSManager 5/27/2014 2:01:34 PM 3900 (0x0F3C)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 5/27/2014 2:01:35 PM 3900 (0x0F3C)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 5/27/2014 2:01:35 PM 3900 (0x0F3C)
Clear local default environment TSManager 5/27/2014 2:01:35 PM 3900 (0x0F3C)
Updated security on object D:\_SMSTaskSequence. TSManager 5/27/2014 2:01:35 PM 3900 (0x0F3C)
Set a global environment variable _SMSTSNextInstructionPointer=1 TSManager 5/27/2014 2:01:35 PM 3900 (0x0F3C)
Set a TS execution environment variable _SMSTSNextInstructionPointer=1 TSManager 5/27/2014 2:01:35 PM 3900 (0x0F3C)
Set a global environment variable _SMSTSInstructionStackString= TSManager 5/27/2014 2:01:35 PM 3900 (0x0F3C)
Set a TS execution environment variable _SMSTSInstructionStackString= TSManager 5/27/2014 2:01:35 PM 3900 (0x0F3C)
Save the current environment block TSManager 5/27/2014 2:01:35 PM 3900 (0x0F3C)
The task exeuction engine successfully completed the execution TSManager 5/27/2014 2:01:35 PM 3900 (0x0F3C)
Set authenticator in transport TSManager 5/27/2014 2:01:35 PM 3900 (0x0F3C)
**************************************************************************** TSManager 5/27/2014 2:01:36 PM 3900 (0x0F3C)
Execution engine result code: Success (0) TSManager 5/27/2014 2:01:36 PM 3900 (0x0F3C)
Cleaning Up. TSManager 5/27/2014 2:01:36 PM 3900 (0x0F3C)
Removing Authenticator TSManager 5/27/2014 2:01:36 PM 3900 (0x0F3C)
Cleaning up task sequence folder TSManager 5/27/2014 2:01:36 PM 3900 (0x0F3C)
Unable to delete file D:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
Failed to delete directory 'D:\_SMSTaskSequence' TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
SetNamedSecurityInfo() failed. TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
SetObjectOwner() failed. 0x80070005. TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
RemoveFile() failed for D:\_SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
RemoveDirectoryW failed (0x80070091) for D:\_SMSTaskSequence TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
Executing command line: "C:\Windows\CCM\TsProgressUI.exe" /Unregister TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
==========[ TsProgressUI started in process 2284 ]========== TsProgressUI 5/27/2014 2:01:37 PM 3952 (0x0F70)
Unregistering COM classes TsProgressUI 5/27/2014 2:01:37 PM 3952 (0x0F70)
Shutdown complete. TsProgressUI 5/27/2014 2:01:37 PM 3952 (0x0F70)
Process completed with exit code 0 TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
Successfully unregistered TS Progress UI. TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
Start to cleanup TS policy TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
End TS policy cleanup TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
Task Sequence Manager ServiceMain finished execution. TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
Task Sequence Manager service will be reconfigured TSManager 5/27/2014 2:01:37 PM 3900 (0x0F3C)
Task Sequence Manager service reconfigured successfully TSManager 5/27/2014 2:01:39 PM 3900 (0x0F3C)
Sending success status message TSManager 5/27/2014 2:01:39 PM 3900 (0x0F3C)
Set authenticator in transport TSManager 5/27/2014 2:01:39 PM 3900 (0x0F3C)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 5/27/2014 2:01:40 PM 3900 (0x0F3C)
GetTsRegValue() is unsuccessful. 0x80070002. TSManager 5/27/2014 2:01:40 PM 3900 (0x0F3C)
End program: TSManager 5/27/2014 2:01:40 PM 3900 (0x0F3C)
Successfully finalized logs to SMS client log directory from C:\Windows\CCM\Logs TSManager 5/27/2014 2:01:40 PM 3900 (0x0F3C)

Software Center showing Application Task Sequence as Operating System

I have created a custom task sequence and it includes 2 applications. The first one uninstalls an app using a batch file and the 2nd TS installs a new version. The problem is that software center is showing type Operating System so when I click
on it to install, it gives a message about installing an operating system and it may delete/format the drive.
Is there a setting I need to change so it sees it as an application rather than an OS? I have other application Task Sequences that show as application rather than Operating System...
Thanks
Rick Ray

That's by design. And by design Task Sequences were meant for Operating System Deployment, that's why you also get notified about "Operating System Installation" in the Software Center.
You should use SCCM Applications with supersedence to accomplish what you are trying to do:
Do an application for App 1 (your old app)
Do an application for App 2 (your new app)
Configure App2 to supersede App1 (uninstall the App1)
Deploy App2 to your computers
This way the App1 will be uninstalled before the App2 is installed.

AD Search plus access to task sequence variables via powershell.

Hi,
I would like to an Active Directory search in a SCCM task sequence.
Now there are two ways I can do this run the powershell script
as a domain user - in the task sequence step.
Or do something fancy in the script itself so the task sequence step
runs as system then does a kind of connect as to do the AD search.
The reason I am asking this is I want to know if the task sequence
variables are available of I run the powershell script as user
account from the task sequence UI.
Or can I only get at them if I am running them as the system context.
Thanks,
Ward

First, answer to your question: if you run an action as a different user in a task sequence (which can only be done after you leave WinPE), you lose the ability to read the task sequence variables. You'll get empty strings for every variable you query.
Now there are several ways of getting this accomplished and it all depends on what stage of the task sequence you want to invoke something like this/what you want to do in AD.
If just want to query AD then, by default, you don't need any special rights as any domain user can do it.
If you want to modify something in AD then you need to be a bit more creative.
1. If you want to run this script after the computer has joined the domain, you don't need to mess around with permissions, as any network actions will be run using the computer object on the network. As far as AD is concerned it will use ComputerName$
account. Though obviously you'll only have read rights.
2. Use the network access account credentials, the username/password for the account are saved onto task sequence variables so you can easily read it. The script itself would still run under the system context, but when you establish a connection
to AD you pass the username/password of the user to connect as. Again, you'd only have read rights.
3. If you want to modify something in AD and the task sequence has already left WinPE, then you can use the 'run as a different user' option in the 'run command' action in the SCCM task sequence. This will force the whole script to run under the context
of the user you specified, which obviously gives you whatever rights you want, including ability to modify something in AD, but you completely lose access to task sequence variables. If you try to query any of them you just get an empty string. A way around
this is to make the variables you know you will need as part of your script in parameters. So for example you call your script as: MyScript.ps1 -MP %_SMSTSMP% to pass the variable _SMSTSMP to your script as a parameter. You can only specify 'run as a different
user' if the task sequence is not in WinPE though.
4. You could use a slight variation of option 2 if you need to modify AD. Instead of using the NAA account use the username/password of an account you specify. The action still runs under system context, but the connection to AD runs with the account
you specify. As a result, this also works in WinPE, and you have no problems accessing task sequence variables. The only problem with this one though... is how to safely pass the credentials over, and that's a big tricky problem.
As you can see, there's several ways of getting things done, but they all have caveats :)
Hope this helps.

Install Applications in task sequence - fails if there is no source

I found an odd issue in SCCM 2012 SP1. I have many applications that install perfectly when deployed. There is no source for the application because it is a network based install, and needs to be. If I try to add the application to the
"Install Application" method in a task sequence, it looks successful. But then re-edit the task sequence and it will tell you there is an issue with the "Install Application" method. The app will not install when you run the
task sequence either. If you then add a content folder to the application, it works like a charm.
In the meantime, I am providing a dummy content location for these apps so I can get things running. But has anyone run into this? Seems so odd that task sequences don't like apps without content.

These are Autodesk application installs. When the deployments are built, they are built to a network location and INI files are generated with paths in them. In the past, I manually edited these files to use local relative pathing, so they
could be used as content, downloaded to the system, and executed locally by SMS. I found issues with install Source locations though (yes, even with using SCCM's built in source control), that made me really want to change the INI's back to network locations,
so now there is no more need for content.
I will have to look into the DCR.

MDT 2012 - Task Sequence Not Completing

I'm a complete novice with MDT 2012, but I have had pretty good luck getting a deployment for Server 2008 R2.
I have a reference system, and I do a very vanilla sysprep and capture using the template task sequence with no changes.
My deployment has a few app installs and other configuration items, but nothing too exotic.
My problem is this: during deployment, after applying the system from WinPE, I perform the final reboot. At this point, the expected action is for an autologon to take place, and for the local Administrator account to run c:\Litetouch.vbs, which does some final
cleanup and a few tasks that require the target system to be running.
This isn't happening on my system. And a look at the registry shows that the autologon stuff has not been set up, so it won't ever happen. It's not a matter of having an incorrect account, or a count of 0, none of the autologon registry keys are even present.
In trying to solve this (I believe it worked when I first started!) I've stripped down my deployment to a pair of task sequences that have no customization
at all in either the capture or the deployment task sequences, and still no luck. So I believe that something has changed in my reference system - but I unfortunately can't roll back.
What is driving me a little nuts is that I can't tell when that autologon information is supposed to be inserted in the registry. There is code in Litetouch.wsf that appears to do it, in function PopulateAutoAdminLogon, but I can't come up with a scenario in
which this function gets called. I am guessing that perhaps sysprep does it when creating the WIM, but I can't seem to find good information on that.
I've done a lot of searching on this, and unfortunately the answer space is cluttered with people who have a similar sounding but completely different problem - they want their deployed system to do an autologon, and after deployment their system comes up with
the logon screen instead of doing what they want. I've seen a few people post similar problems to mine, but nobody has received an answer. This one is pretty close, it suggest I might have a group policy item that disables the local admin account, but I don't
think it hits the mark for me.
http://social.technet.microsoft.com/Forums/en-US/mdt/thread/e625aa88-2415-4a2a-9e79-ac6b37119c27
So in a nutshell: when deploying a system using MDT 2012, at what point do the autologon items from unattend.xml stuffed into the registry for use after state restore/reboot in the task sequence? And what can go wrong with that?
- Mark

Same here, can't find any solution though. Did you ever work it out?

Auto deploy a VI onto compactRIO or pop-up a vi on target in main VI

Hello
I have a main program where i have event structure and 2 state machines which do DAQ and Video. in a different project i have a pid controlled heater program that will be deployed on compactRIO. how do i program the main VI to auto deploy the heater program to target and get values from there to the main program. (for graph values can i use global varible between realtime program and normal main program)
I am thinking if i use the shared variable that is update by AI of a module on Compactrio in the main program, will it auto deploy it detecting that shared variables belong to target, but i want only the heater part of the program to get deployed not the event strucute, statemachines on the mian program. please help
If i can put a button on main program that when clicked can pop-up the heater program on compact RIO to adjust the PID parameters and close it and run with new values. is this possible?
Thanks in advance

Hi freemason,
I'm still a bit unclear on what you need. If you are able to develop your project such that all the VIs are located in thier respective locations (i.e. on the cRIO, RT or Windows Host), and you just want to change controls before running the FPGA vi, we can do that. Essentially, you use a read/write control VI before running the FPGA VI using the Run invoke node. You'll have to make sure to change the FPGA open reference options to not run the VI automatically (right click on it and select "Configure Open FPGA VI Reference...", uncheck the run option).
If you want to look at an example involving PID in the LabVIEW example finder, one that might be of particular interest is called "Template Multichannel PID". You can find this in through Help>Find Examples. Navigate to Hardware Input and Output>CompactRIO>FPGA Fundamentals>Analysis and Control.
You can use the execution of your host VI to start and stop the FPGA vi using the Read/Write Control VI and the Run invoke node. Also, you can use an invoke node to Abort the VI if that is necessary, but creating a stop control in the FPGA VI that allows the Host VI to stop using programming flow is usually more desirable.
I hope these suggestions help, but please clarify your question if you're still confused.
Also, Pablo. Try setting the VI to run as a start up application. A guide of how to do that is here.
Message Edited by Verne D on 04-06-2010 01:07 PM
Message Edited by Verne D on 04-06-2010 01:07 PM
Verne D. // LabVIEW & SignalExpress Product Support Engineer // National Instruments

Auto Login as part of OSD Task Sequence

Hi,
I am wondering if there is a way to force a Login with a specified account to Windows as part of an OSD. I have an command in the registry in HKEY Local Machine...../RunOnce that needs to run before the end user uses their computer.
Unfortunatly, it just will not run as part of a "Run Command Line" Task.
I can accomlish this by using the GUIUNATTEND AutoLogon in Sysprep, but that also presents some challenges. If there was a way in the OSD Task Sequence that I could force a login with a specified account and then logout, that would be great.
Thanks
Rosy_55

The code (vb) below would be created into a step as an application installation or package installation as the second to last step, the last step would be to reboot into the default OS.
This will, during OSD set a autologin account to login until rebooted, once done the last step will reboot and log into windows, the runonce section will then run gpupdate, and then restart the machine.
It will only login once. Modify as needed.
Note that you need to modify the sUsername = "domain\user", and sPassword = "domainuserpassword"
variables.
CODE:
'after autologin this sets the computer to run gpupdate one time and then reboot
Set objShell = WScript.CreateObject("WScript.Shell")
strRunOnce = "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce\joinDomain"
objShell.RegWrite strRunOnce, "cmd /k gpupdate "&chr(38)&chr(38)&"shutdown -r -f -t 10", "REG_SZ"
'this configures the autologin
Const HKEY_CLASSES_ROOT = &h80000000
Const HKEY_CURRENT_USER = &h80000001
Const HKEY_LOCAL_MACHINE = &h80000002
Const HKEY_USERS = &h80000003
Const HKEY_CURRENT_CONFIG= &h80000005
Const HKEY_DYN_DATA = &h80000006
sUsername = "domain\user"
sPassword = "domainuserpassword"
Set objNetwork = CreateObject("Wscript.Network")
sComputer = objNetwork.ComputerName
strRegKey = "Software\Microsoft\Windows NT\CurrentVersion\Winlogon\"
Write64BitRegistry "REG_SZ", HKEY_LOCAL_MACHINE, strRegKey, "AutoAdminLogon", "1"
Write64BitRegistry "REG_SZ", HKEY_LOCAL_MACHINE, strRegKey, "DefaultUserName", sUsername
Write64BitRegistry "REG_SZ", HKEY_LOCAL_MACHINE, strRegKey, "DefaultDomainName", strComputer
Write64BitRegistry "REG_SZ", HKEY_LOCAL_MACHINE, strRegKey, "DefaultPassword", sPassword
Write64BitRegistry "REG_SZ", HKEY_LOCAL_MACHINE, strRegKey, "ForceAutoLogon", 1
Write64BitRegistry "REG_DWORD", HKEY_LOCAL_MACHINE, strRegKey, "AutoLogonCount", 1
Sub Write64BitRegistry (strRegType, strRootKey, strKey, strValueName, strValue)
Dim objCtx, objLocator, objReg, intReturnCode
Set objCtx = CreateObject("WbemScripting.SWbemNamedValueSet")
objCtx.Add "__ProviderArchitecture", 64
Set objLocator = CreateObject("Wbemscripting.SWbemLocator")
Set objReg = objLocator.ConnectServer("", "root\default", "", "", , , , objCtx).Get("StdRegProv")
If Ucase(strRegType) = "KEY" Then
intReturnCode = objReg.CreateKey(strRootKey,strKey)
End If
If Ucase(strRegType) = "REG_DWORD" Then
intReturnCode = objReg.SetDWORDValue(strRootKey,strKey,strValueName,strValue)
End If
If Ucase(strRegType) = "REG_SZ" Then
intReturnCode = objReg.SetStringValue(strRootKey,strKey,strValueName,strValue)
End If
If Ucase(strRegType) = "REG_EXPAND_SZ" Then
intReturnCode = objReg.SetExpandedStringValue(strRootKey,strKey,strValueName,strValue)
End If
If Not intReturnCode = 0 Then
End If
End Sub
William Lee

Second Task Sequence to collection. Will it auto-deploy?

Similar Messages

Maybe you are looking for