How to deploy Office PlugIns during OSD Task Sequence?

I have two application packages that I need to install after Office 2013. I've tried adding them after Office 2013, but they won't install. I'm getting error 80004005. What's the best practice for installing plugins?

Jeff,
It looks like one of the Addins requires UAC be turned off. I've added that as a command line and setup a restart after that in the TS. Then I added the AddIn application to the TS. It's erroring out with 80004005 while I can see the screen in the background
say "Setup is preparing your computer for the first time." For the reboot I've specified it to use the existing OS.
What's the best way to get UAC turned off, reboot then install the AddIn?
It will not require UAC, if you run your command promt as admin, which will be opened at c:\Windows\System32
Also, code 80004005 is very generic, and does not reveal nothing. You will see at Appenforce.log what´s really happening, also smsts.log. Event viewer is also helpful.

Similar Messages

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

How to prompt for OU during OSD Task with SCCM 2012 R2?

How to prompt for OU during OSD Task with SCCM 2012 R2?

Hi,
Here is an example on how to do it using a Variable prompt in Configuration Manager, It works the same way in SCCM 2007,
http://www.the-d-spot.org/wordpress/2013/04/01/dynamically-join-computer-to-ad-ou-during-osd-with-sccm/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

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

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

How to enable dump file during OSD?

Hello,
I'm having an issue with a line of Dell laptops getting stuck in a reboot loop after the first reboot of our OSD task sequence, which is an SCCM 2012 SP1/MDT 2012 Update 1 Client Task Sequence.
After it lays down the OS and reboots for the first time, we get a BSOD. There is no DMP file at C:\Windows\Minidump. How can I enable the minidump or get the BSOD to stay on the screen if I can't get into the OS to make those changes?
How do I enable these features in WinPE?

First see http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/
The bottom section cites the registry value to update.
You can directly enable this in your image or during the TS using the technique outlined under the
Full Windows OS - Operating System Image section
at
http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2012/01/23/when-deploying-windows-server-2008-using-an-configuration-manager-osd-task-sequence-additional-disks-may-show-as-offline-when-the-task-sequence-completes.aspx (note
the problem discusses there is completely different and has nothing to do with this thread, but the technique of loading the offline registry hive, changing a value, and then unloading the registry hive is valid and applicable).
Jason | http://blog.configmgrftw.com

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.

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

Creative Cloud: "Build" MSI Hangs During SCCM OSD Task Sequence Installation

I wanted to share problem and solution I found when deploying Creative Cloud Packager-created packages/application using SCCM 2012 R2. I encountered this problem packaging this as both a Package and as an Application in SCCM.
When installing the software through SCCM Software Center onto a client, Software Center would close right as the installation of the "Build" folder MSI completed. This is abnormal behavior.
When installing the application as part of an OSD Task Sequence, the software would get installed (as shown by logs) but SCCM would hang forever at the "Installing Application" step.
I tried all sorts of different settings in SCCM and with the MSIEXEC command line and eventually traced it to the Reboot Manager functionality in MSIEXEC that will close and attempt to restart processes using files that the installer needs. Reboot Manager clobbered part of SCCM and in the Task Sequence, the connection between SCCM and the installer was broken.
The solution is to pass the property "MSIRESTARTMANAGERCONTROL=Disable" along the command line when calling MSIEXEC on the Build folder MSI file. This setting disabled Restart Manager so it didn't mess up SCCM. Once I did this, my Software Center installs and OSD Task Sequences ran as intended.
For reference, I used the REBOOT=ReallySuppress property for reboots and let SCCM determine what to do with reboots based on the return code. My testing was done with Windows 8.1 Enterprise x64.

Like said, did you configure my proposal: "Configuration Manager client will force a mandatory device
restart" ? After you've configured that, update your deployment type manually and remove the old revisions of the application and try running the TS again. I'm guessing you're a little bit too fast on your doings so the ConfigMgr doesn't play a long very
nicely...
The TS stops because of your Hard Reboot (exit code 1641), I've seen this before and I configured my application so that ConfigMgr client will force device restart and that fixed my problem. Although, also my application is the last one in the TS, but still,
the TS continues after the reboot.
Btw. have you tried changing your command line to:
msiexec.exe /i cd-ord.msi TRANSFORMS=sv-se.mst MVLICENSE_KEY=xxxxxxxxxxxxxxxxx /L*V "%temp%\cdord.log" /qn
/norestart

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

SCCM 2012 OSD Task Sequence - force Policy and SCEP update?

Hi,
How can I force a policy update to update machine policy and scep definitions at the end of
SCCM 2012 OSD Task Sequence,
Thanks,
Ward.

Hi,
I normally use this solution from Chris Nackers to deploy the latest EP definitions during OSD and deploy a custom EP policy, it works great. The policy will be downloaded when the client is registered.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

UDI OSD Task Sequences started failing with 0x80070002 error in SCCM 2012

This is kind of long, but here goes...
We built a UDI task sequence in SCCM 2012 (with MDT integration) that we were testing for deployment of a couple of different Win7 images. We customized the UDI experience thru the UDI wizard and XML file and OS deployment worked as expected
thru the task sequence (testing on Hyper-V VMs). Recently, this UDI TS started failing with error 0x80070002 during what appears to be the "Use Toolkit Package" step. This is after the OS image has already been laid down and after the ConfigMgr
client has been installed/configured. The SMSTS.log reports "Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x8007002" Among other errors...I will post the entire log below...
After the error during deployment, Win7 will boot normally, however, you have no network connectivity and it appears the proper network driver didn't get loaded in the OS. Combine this with the fact that the TS should have joined the machine to our domain,
but you can't login because no network.. Im not sure if the network issue is a product of the TS failing early or the actual cause of the TS failure.
Anyway, I attempted to build another UDI task sequence using the same boot image and toolkit/settings packages, but am experiencing the same error during deployment. We have a few OSD task sequences built without UDI and those all still work just fine.
So, I am at a loss for where the root problem lies. Any suggestions or assistance would be greatly appreciated.
Here is the entire SMSTS.log and BDD.log...
https://skydrive.live.com/redir?resid=D65B1C4362892A26!110&authkey=!AKu5mOvDsXaEgvc
Thanks
Richie Tenhet

your failure does appear to be network (driver or otherwise) or dns related and it cannot contact the management point FQDN just around the time where it should download and execute the
Use Toolkit Package step...
"Starting Task Sequence Engine . . . "
"Non fatal error 0x80072ee7 in sending task sequence execution status message to MP"
"Start executing an instruciton. Instruction name: Use Toolkit Package. Instruction pointer: 83"
"unknown host (gethostbyname failed)"
"sending with winhttp failed; 80072ee7"
"Tried all the available http based locations. SMB based locations will be attempted now."
"Failed to resolve the source for SMS PKGID=P0100015, hr=0x80070002"
"Failed to run the action: Use Toolkit Package.
The system cannot find the file specified. (Error: 80070002; Source: Windows)"
that said, check that the package referenced above actually exists and is the correct source version on your distribution points, also verify (press F8 and check can you ping the FQDN of your management point) that you have network connectivity
around the time of the failure.
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady

Client not installing completing via OSD Task Sequence - Standalone Media

Dear All,
Facing this issue that i have made Standalone media for OS Deployment but after installing OS, SCCM Client doesn't install completely but when try to install from network with same Task Sequence Client installed successfully.
One more thing while installing from media, machine is connected on LAN.
For Further Reference Snapshots are attached.
As in log its stat that installation was processed but there was no ccmsetup.exe in process neither its installed correctly
======>Begin Processing request: "2097152793", machine name: "WIN7VERIFY"
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
10472 (0x28E8)
Execute query exec [sp_IsMPAvailable] N'KHI'
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
10472 (0x28E8)
---> Trying each entry in the SMS Client Remote Installation account list
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
10472 (0x28E8)
---> Attempting to connect to administrative share '\\WIN7VERIFY\admin$' using account ''
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
10472 (0x28E8)
---> Connected to administrative share on machine WIN7VERIFY using account 'uead\'
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
10472 (0x28E8)
---> Attempting to make IPC connection to share <\\WIN7VERIFY\IPC$>
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
10472 (0x28E8)
---> Searching for SMSClientInstall.* under '\\WIN7VERIFY\admin$\'
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
10472 (0x28E8)
---> System OS version string "6.1.7601" converted to 6.10
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
10472 (0x28E8)
---> Mobile client on the target machine has the same version, and 'forced' flag is not turned on. Not processing this CCR
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
10472 (0x28E8)
---> Deleting SMS Client Install Lock File '\\WIN7VERIFY\admin$\SMSClientInstall.KHI'
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
10472 (0x28E8)
Execute query exec [sp_CP_SetLastErrorCode] 2097152793, 120
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
10472 (0x28E8)
---> Skipped request "2097152793", machine name "WIN7VERIFY".
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
10472 (0x28E8)
Deleted request "2097152793", machine name "WIN7VERIFY"
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
10472 (0x28E8)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152793, 3
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
10472 (0x28E8)
Execute query exec [sp_CP_SetLatest] 2097152793, N'11/10/2014 10:52:22', 1
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
10472 (0x28E8)
<======End request: "2097152793", machine name: "WIN7VERIFY".
SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
10472 (0x28E8)
REGARDS DANISH DANIE

The attached log file is related to a client push, I'm not sure how that is related to your problem. When you're having problems with the client installation during a task sequence deployment, please check the smsts log file and, if available, the ccmsetup
log file (these log files should be available on the client itself).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Prompt for AD Description OSD Task Sequence

Hello,
I want to be prompted for AD Description while OSD Task Sequence, tried couple of scripts from different blogs but couldn't got any result. Need help from your side.
Thanks
REGARDS DANISH DANIE

The setting which are described in this blog i have deployed on Test Task Sequence but that didnt work for me in that sense that its doesnt Prompt for Description while installation.
"http://ccmexec.com/2012/01/set-computer-description-during-osd/"
While in the second blog writer already said that "description does not filter back to AD it only remains local to the machine" So i want that description in AD.
What i want... a script that prompt for description are changes made on AD in computer account description.
Hope you have got my point?
REGARDS DANISH DANIE

How to deploy Office PlugIns during OSD Task Sequence?

Similar Messages

Maybe you are looking for