Hotkey install during SCCM task sequence

HI everyone, I'm trying to have the latest version of Hotkey ( version 5.43) install during a window7 OS deployement using SCCM 2012. I think the drivers are installing but the On Screen display feature are not working and if I run the setup.exe manually after the OS deployment is done, it offer me to install Fn incrustation. It's currently working with an older version ( 4.19) using setup.exe /s. I tryed with setup.exe /S /B /H and it is still not working. Anyone manage to make it work ?
Thank you for your help.

I found the problem, it wasn't hotkey, it was me. I forgot to add the type number so the step could detect if it need that software.... I spent to 2 days on this

Similar Messages

Nvidia (Quadro K2000) Driver isn't installed during OSD (Task Sequence succeeded) - HP Z620

Hi everyone,
I have added a driverset (HP Z620) in SCCM for the first time using our internal procedure (Importing Drivers to SCCM, Create Driver package with specific category, apply driver package in TS using WMI to query for the model).
The Task Sequence succeeded, but the NVIDIA K2000 Graphics driver isn't installed (only HD Graphics 4000 driver).
Looking at the drivers in the Driver Package, this should normally apply since the driver is compatible with this specific GPU.
At the forums, I can see that some people have created a seperate package for the GPU driver installation using command line switches.. But looking at the environment at the customer, we have never done this and in the past, we have succesfully installed
the driver for this GPU before.
PS: The driver for the GPU in my new driver package (HP Z620) isn't the same as for previous models (HP Z220, Z230, Z600).
Could you please advise me what to do? Should I have added something in the driver sources before importing the driver to SCCM?
Thanks in advance!
Kind regards

Hi
I m installing Nvidia (Quadro K2000) Driver during OSD (Task Sequence succeeded) - HP Z420
Remove the Graphics driver for NVIDIA from the current driver database
Added below task in the existing task sequence as invidual installation based on the Condition (WMI query)
Command Line
HP_Z420_Graphics_x64\Win64_332_50\setup.exe -s -k -clean -noeula
This will install the desired driver and related configurable components
WMI Query
select * from win32_ComputerSystem where manufacturer like '%hewlett%' and model like '%z420%'
Currently I m looking out for the Errors codes needed to add to this task . Success codes 3010 and 0 already added

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 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

SCCM Task Sequence no longer installs SCCM Client

I am using SCCM 2007 R3 with SP2 and MDT 2010
My task sequences were all working fine until one of the other SCCM admins "Synced all sites" by transferring the site settings of one site to all the other sites. How this broke OSD I don't know.
At this point the best I can tell is that the SCCM client is not being installed in the Task Sequence and so when it reboots to the installed OS there is no longer any communication and the task sequence fails with an error of "Windows could not configure
one or more system components. To install Windows, restart the computer and then restart the installation.
I have run out of ideas to fix it so I am asking for the collective knowledge of the Interwebs for help.

Please post the contents of C:\Windows\ccmsetup\logs\ccmsetup.log in order for us to help you further
Blog: www.danielclasson.com/blog |
LinkedIn:
Daniel Classon | Twitter: @danielclasson

Does 2012 OSD get around requirements to get to the MP during the task sequence?

Currently right now I am working in an environment where we are on SCCM 2007, but will be going to 2012 next year. We are in the process of trying to make it so we can build on a secure network that cannot route to any other network. I am prepared to put
a DP out on this same network, but the problem I am running into is that during the task sequence starting, it downloads the task sequence from the MP, not the DP as it is not associated with the package. The MP is not on the same un-routable network. We will
need to have about 6 or so of these, so we do not want to setup 6 MP because now you are looking at not only 6 primary site licenses, but 6 SQL installs (Our environment will not let me get away with doing SQL express for support reasons) which adds up quickly.
Below is a link to exactly what I am speaking about:
http://blogs.technet.com/b/configurationmgr/archive/2009/04/16/configmgr-2007-primary-site-mp-is-used-for-the-task-sequence-even-when-deploying-osd-images-to-secondary-sites.aspx
What I am wondering is if SCCM 2012 OSD was structured differently in a way that access to the MP is no longer necessary during the task sequence process (say for example the task sequence xml is replicated to DPs too)?
Thanks.

My apologizes. I was meaning to say Primary, Secondary Sites. Not MPs. I brought this up to give reference to idea about the boundaries that I am going to have to use to prevent these clients from contacting DPs they they can't route to.
The idea behind getting off the build network and onto a prod is that security requirements from my companies Infosec require that we limit the amount of traffic on production networks. The idea is that the server be built on the build network, disconnected
and brought into prod. The whole time the MP would be the same, but the DP would switch based on the prod network they were brought into as DP will reside in these prod networks which will get flipped over by the boundary for the prod subnets. Once on the
prod network they would be able to contact the MP.
I would love to do stand-alone media, this is one of the first roads I started looking down as I have done them in the past for offline builds, but I need the machine to auto assign its hostname from a external servers that will script the build. The build
process we are trying to put into place will be started from an external website. My first thought was to have it add the machines to a collection and add a variable that would be turned into a task sequence variable during the TS and use it for the hostname
when it attempt to apply the Windows settings. The only way I think I could get this to work would be to write a script that is executed during the task sequence that would match the MAC address of the machine and assign the hostname by calling on another
share that is written to by the external website with the MAC and hostnames. The only problem that I cannot get around is that this build process needs to be fully automated and this is for both virtual and physical. I have no problems mounting a stand-alone
build ISO using a script for VMWare, but the problem starts when I look at the physical and limitations of scripting for both iLo and iDRAC for performing this step. iLo can be done, but iDRAC is limited.
As for a reverse-proxy I will not be able to look at that. They have specific requirements against using reverse-proxies in only specific situations and this it not allowed. I got turned down on this one. This requirement is created by a federal regulation
my company has to follow.

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

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...

Using a environment variable that was created during the Task Sequence process - SCCM 2012 R2

Hi,
I'm triyng to use a environment variable that is create in the beginning of the Task Sequence.
1. I'm using a VBScript that get the Exit Code of an application, and create the environment variable "iReturn" with the value of the exit code. (This is working)
2. I add this variable in the CustomSettings.ini, like this "iReturn=%iReturn%
3. After the step that I run the VBScript I put the "Gather" step to get the variables, but looking in the BDD.log the iReturn variable appears the same as the CustomSettings.ini configuration "iReturn=%iReturn%". (But, if I put a "Restart
Computer" step after the VBScript, the BDD.log shows the iReturn variable with the right code.)
Question: How can I update the environment variable of Windonws XP to use in the Task Sequence without restart.
OR
How can I configure autologon in SCCM 2012 (if have no way to update withou restart computer).
I already tried the autologon with registry settings and a specific user, If I starts the process with this user works, but If I starts the process with other user, after the autologon the process doesnt continue, I have to do logoff and login with the user
that I started the process.
PS: All this steps have to be executed before the WinPE phase.

Environment variables must be explicitly set every time a system boots so unless you have a process to repopulate it after the reboot, it won't persist automatically.
Why not store the value in a task sequence variable so that it persists after a reboot?
Jason | http://blog.configmgrftw.com | @jasonsandys

Error installing MBAM client through SCCM task sequence error code 80070005

Hi
I'm getting a weird error when trying to deploy the MBAM 2.0 client through a task sequence, it was working but now keep seeing the below two errors in the AppEnforce log, after it has returned the 3010 soft reboot code.
CoCreateInstance failed on CLSID_ProductSrcUpdateMgr, error 80070005
Failed to update msi source list, error 0x80070005
does anyone have any idea what these mean?
thanks
Mark

What is the silent installation command line for MBAM client you are using. I would suggest to first test the silent installation manually and test whether it is working successfully or not.
Are you using the msi installer or the setup.exe
Command Line for Deploying the MBAM 2.0 Client
MBAMClientSetup.exe /q
Gaurav Ranjan

Whats the best way to apply office updates during OSD task sequence with Software Update Agent disabled?

I am trying to update office via the SCCM 2012 R2 OSD task sequence. I know offline updating only updates the core components in the WIM and I'm trying to figure out how to add office updates as well. I am aware of using powershell to try and kick off
a WU scan as seen here:
http://myitforum.com/myitforumwp/2012/01/24/use-powershell-commands-to-assist-with-patching-during-sccm-image-build/
But the kicker is we don't use SCCM to update the workstations (Solo WSUS install). Is there a way to do this (maybe set the client in the TS to switch on SUP, then off again when it goes off into production) rather than have to build a new image every month?

You could use the ZTI_WindowsUpdates.wsf script from MDT.
http://scriptimus.wordpress.com/2012/03/22/mdt-2012-automating-updates-in-lite-touch-deployments/
How does it work?
The task sequence steps run a script called ZTIWindowsUpdate.wsf. The script uses the
Windows Update Agent API to manage the downloading and installation of updates. All audit information is written to the
ZTIWindowsUpdate.log file. If you find any unusual error codes in your log returned from the API (although I never have) you can compare the codes
here. The script will also check and update the
Windows Update Agent(WUA) as needed at the start.
In its default state, the ZTIWindowsUpdate.wsf script will connect to Microsoft Update then search for and download all available updates including Security Patches, Drivers, Browser Updates and Service Packs. This is essentially the same
as opening the GUI and selecting check for updates.
Daniel Ratliff | http://www.PotentEngineer.com

Deploying 100% of available software updates during a task sequence

Hi,
Can somebody tell me if it actually possible to fully patch a computer via an SCCM 2012 task sequence using the install software updates task? If you have managed this can you shed some light on where I'm going wrong? For me, this behaviour is exactly
the same as ConfigMgr07... It simply doesn't work as it should.
I've integrated IE9 into my image and then added in all available updates via offline servicing. My task sequence installs windows, installs Adobe Reader, Office 2010 and Visio Viewer 2010. I then reboot the machine and perform all my patching via the Install
Software Updates task (with it set to 'all'), then reboot again. I do this four times in total.
It downloads and installs some 24 updates in the first instance. The second, third and fourth time it doesn't download or install anything.
When the task sequence completes and the OS first starts up there are 10 updates waiting to be installed (including updates for Adobe Reader and Flash that I have published to the WSUS server via SCUP). After installing those and rebooting there is a single
hotfix available (KB2533552). After installing that and rebooting, .NET4 Client Profile is waiting for me. After that there another nine more updates are available (mainly .NET4). Reboot, .NET4 Framework, reboot 5x .NET4 framework updates.
Why does the software update task not install 'all' updates when that is what I've selected? I have an automatic deployment rule targeted to my OSD and Unknown Computers collections. The rule is set to include Windows 7, Office 2010 and Adobe products with
all update classification types.

I don't have a pause in my script and have not encountered any issues with the scan not finishing before the Software Update installation step. This is true for my B&C TSs which install in the region of 200 updates, including custom trusted publisher
updates from SCUP 2011. So I can't really comment on that side of things.
With regards to the patching side of things: I tried removing the multiple reboot patches from my Task Sequences by excluding them from the Auto Deployment Rules that target the same containers as the task sequences by adding -KBxxxxxx in the ADR. Unfortunately,
due to me having the multiple reboot updates targeted up 'update' collections that are populated by hardware/software DB queries, any PC that is performing a 'Refresh' TS ends up with the offending patches being targeted for install anyway and the TS fails.
For a long time I was just removing the client record from the DB and recreating it so that the offending updates would not be targeted to the client. Once the client has been refreshed, a hardware inventory is performed, the collections updated daily, the
multiple reboot patches are detected and are scheduled for install for the following Friday afternoon. This used to annoy me as I don't like 'incomplete' clients being delivered to users' desktop.
Recently though I've been toying with offline servicing. At first I attempted to integrate every available update but this just ended up killing things too. A number of the updates that can be installed via offline servicing have a .net 4 pre-requisite
but because .net 4 cannot be slipstreamed, the prerequisite is not satisfied, Windows setup fails and so does the TS. So using this method there is a chance you'll end up installing a patch that will kill your image... Still not ideal.
What I have settled on is slipstreaming specific patches into my installation media using dism and then running a B&C TS to update my image.
This is the batch file I use (you'll need to change to suit):
Dism /mount-wim /wimfile:D:\SCCMContentSources\Applications\Microsoft\Windows\7\Professional\SP1\64-bit\Sources\install.wim /index:1 /mountdir:D:\HotFixIntegration\Offline
Dism /Image:D:\HotFixIntegration\Offline /LogPath:SourceAddPackagex64.log /Add-Package /PackagePath:D:\HotFixIntegration\Hotfixes\64-bit\Updates
Dism /Image:D:\HotFixIntegration\Offline /LogPath:SourceAddPackagex64.log /Add-Package /PackagePath:D:\HotFixIntegration\Hotfixes\64-bit\IE
Dism /unmount-wim /mountdir:D:\HotFixIntegration\Offline /commit
The first line mounts the image.
The second line slipstreams the following .msu updates:
kmdf-1.11, KB2526870, KB2529073, KB2545698, KB2561285, KB2574819-v2, KB2592687, KB2617858, KB2670838, KB2726535, KB2729094-v2, KB2786081, KB2834140-v2, KB2847311, KB2855844, KB2862330-v2, KB2862335, KB2864202, KB2868038, KB2876284, KB2883150, KB2884256,
KB2965788, KB2984976, KB917607, KB971033, KB976399, KB977944, KB981750
These are essentially just the multiple reboot patches and their pre-requisites, IE11 prerequisites, and a few KBs that not published to WSUS.
The third line slipstreams IE11 from the IE11 .cab file.
The fourth line commits the changes to the install media.
After running a B&C TS from this modified installation source there are no updates available to freshly deployed images (until the next patch Tuesday!).
Unfortunately this a manual process as I need to check the multiple reboot KB article each time updates are released but it's the only way I can put out 100% patched PCs and have a PC Refresh task sequence that doesn't fail.

Superseding an application which is installed via OS task sequence

Hi I am using SCCM 2012 SP1 and want to update AppA_version_1 to the AppA_version_2. At the moment AppA_version_1 is a core application and is installed to all machines via OSD when the machines are built. For this reason we don't have any
collections for AppA_version_1.
I have now created a new application for AppA_version_2 and want to test the deployment to a group of machines. As part of the test deployment I want to supersede the AppA_version_1 which we currently have installed.
In the past I have tested supreseding business applications (which are not part of the task sequence and deployed to users not machines) by first creating a test collection, setting the supersedence options and then deploying the superseding (latest) application
to the test collection. When I am happy it works OK I deploy the superseding application to the main collection for that application.
I have not had to supersede an application which is part of the task sequence before but I presume I do it in just the same way ? At the moment I don't want to touch the task sequence. I want to test the deployment of AppA_version_2, then
release it to all production machines, then update the task sequence so it includes AppA_version_2. What I don't want is to deploy it to the test group but have it automatically update on all production machines.
The reason I ask is that I have read that if you update the Task Sequence with the latest version of your software and this supersedes a previous version, then all of your machines in production will receive the latest version even though it has not been
specifically deployed to them.
http://www.windows-noob.com/forums/index.php?/topic/8952-possible-bug-in-sp1-cu1-client-applications-that-supersede-others-may-rollout-unexpectedly/
Even though I am not going to update the task sequence with AppA_version_2 just yet, it has got me questioning the testing of the superseded application.
Am I OK to superseded AppA_version_1 with AppA_version_2 and deploy to a test collection (without it updating all machines in the organisation) even though AppA_version_1 is installed as part of the OSD Task Sequence.
Hope this makes sense
Thanks
G

Thanks Jorgen
What happens if I select the option : automatically upgrade any superseded versions of this application
? Would this ignore the fact that I was deploying to a test collection and automatically update all production machines where the software is installed ?
I haven't actually come across this option before, but I think that is because I usually create my deployments prior to setting the supersedence rules.
Thanks
G

SCCM Task Sequence Fail to Connect Share Folder on SCCM server

those days we have an task sequence issue- can't connect to share folder on the SCCM server
Enviroment
in our network, we have DHCP server, DC server, DNS server. we are trying to bring up an new server to boot from the SCCM server. we have two VLAN in our environment. VLAN 54 and VLAN 200.
the DHCP/DC/SCCM/DNS are all running on VLAN200
Issue
we have those steps in this task sequence
Installing OS
setup windows and configuration manager
connect to an share folder to SCCM(run some sicrpts)
run the scripts
install the sqlserver
1. when the VM running on VLAN 200, no issue on all the task list, we can access the share folder on SCCM server.
and task sequence run ran success.
2. but when VM running on VLAN 54, issue came. when the task sequence run into the [Setup Operation System]/[Connect to network folder]. this step can't get the share folder to sccm server.
then the task sequcne was quit, so we logined to vm have a look. run the ipconfig/all. no IP address get from DHCP server.
but when we run the command ipconfig/renew on this VM, then we can get the IP address from DHCP server.
we have tried an alternative solution like below.
add an step ipconfig/renew before connect to share folder, then the task sequence can connect to share folder, but when the task run into last step- install the SQL from package.
unfortunately, we came cross another issue.
Failed to invoke Execution Manager to Install Software for PackageID='GDL00008' ProgramID='Install SQL 2005 Standard SP4' AdvertID='GDL2001F' hr=0x800706ba InstallSoftware 12/10/2013 11:48:17 PM 1012 (0x03F4)
InstallSoftware failed, hr=0x800706ba InstallSoftware 12/10/2013 11:48:17 PM 1012 (0x03F4)
Quetions
so we suspect there may something to do with network, but the network team said there is no issue on their side. so what i can go to research, how can i fiind the root cause or how to confirm it is an network issue. do you guys have any idea on this issue?

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

MDT 2013 - Install Application in Task Sequence Stuck

I am running an application installation within my task sequence during my deployment. One of the applications prompts a user response to click yes to continue. Otherwise the task is stuck at that step. It appears to be stuck during my Java 7U51
installation running this command. It works on several machines but I get this once in a while on a few workstations when trying to deploy. any ideas?
About to run command: \\xxxxxxxxxxxxxxxxxxx\xxxxxxxxxx\Tools\X64\bddrun.exe jre-7u51-windows-i586.exe /s /v"/norestart /AUTOUPDATE=0 JAVAUPDATE=0 JU=O"

first try to install java with
MDT if any one you are using and then
run the programyou want to post an example
here
http://mdtguy.wordpress.com/2014/02/17/installing-the-latest-java-re-msi-with-mdt-2013/
Freelance-IT http://www.freelance-it.com.mx

Hotkey install during SCCM task sequence

Similar Messages

Maybe you are looking for