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

Similar Messages

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

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

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

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

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

I installed a NVIDIA QUADRO K2000 card and downloaded the most current drivers. AE does not accept

Can anyone offer a solution for this? I installed a NVIDIA QUADRO K2000 graphics card. I downloaded the latest drivers for the card. AE reports that this GPU is incompatible. This is one of recommended listed cards for CS6. Any suggestions?

> This is one of recommended listed cards for CS6.
Where did you get that information? That card is not on this list:
http://www.adobe.com/products/aftereffects/tech-specs.html
What is the exact message that you're referring to when you say that After Effects "reports that this GPU is incompatible"? Is it just saying that it won't use this GPU for the CUDA acceleration of the ray-traced 3D renderer? If so, the only thing that you'd be missing is GPU acceleration of one feature.
See this page for details of how the GPU is used in After Effects:
http://blogs.adobe.com/aftereffects/2012/05/gpu-cuda-opengl-features-in-after-effects-cs6. html

NVIDIA QUADRO NOTEBOOK DRIVER RELEASE 304 - Version: 305.93 WHQL

Has anyone tried the NVIDIA QUADRO NOTEBOOK DRIVER RELEASE 304 - Version: 305.93 WHQL (released Sep 5 2012) yet?
http://www.nvidia.com/object/quadro-notebook-win7-winvista-64bit-305.93-whql-driver.html
(Windows Hardware Quality Labs testing or WHQL Testing is Microsoft's testing process which involves running a series of tests on third-party hardware or software, and then submitting the log files from these tests to Microsoft for review. The procedure may also include Microsoft running their own tests on a wide range of equipment, such as different hardware and different Microsoft Windows editions.)
Anything one needs to pay attention to?
EDIT: I just installed it. It seems to work fine.
W520 4270CTO i7-2820QM Quadro2000M 1920x1080 Display 16GB RAM 2x240GB Intel 510 SSDs (RAID 0) - BIOS 1.42 - PCMark7:4,568
Samsung Series 9 15-inch NP900X4C-A03US - PCMark7: 4674

I've been running 301.42 for a while now. I'm going to install 305.93 tonight.
Update: This driver appears to work for Windows 8 as well as Windows 7. I'm not seeing much difference between 301.42 and 305.93.
W520, i7-2820QM, BIOS 1.42, 1920x1080 FHD, 32 GB RAM, 2000M NVIDIA GPU, Samsung 850 Pro 1TB SSD, Crucial M550 mSata 512GB, WD 2TB USB 3.0, eSata Plextor PX-LB950UE BluRay
W520, i7-2760QM, BIOS 1.42 1920x1080 FHD, 32 GB RAM, 1000M NVIDIA GPU, Crucial M500 480GB mSata SSD, Hitachi 500GB HDD, WD 2TB USB 3.0

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

Dell Driver Packages breaks OSD Task Sequences?

I'm completely stumped here... I had an OSD Task Sequence that was working perfectly. Then I imported some Dell Driver Packages with the Dell Client Integration Pack and suddenly, OSD doesn't work anymore.. I made no changes to the Task Sequence itself (steps
are listed below).
The weird thing is, when the OSD is actually running, the progress bar goes through all of the steps and the Monitoring space on the deployment shows each step completing successfully, but every step after "Apply Operating System" doesn't actually
take effect. When rebooted, I find the computer has not joined the domain, has not applied any drivers, has not installed the SCCM client, didn't install any of the applications, and didn't install the updates. It's like the task sequence just
stopped actually writing to the hard drive and just pretended to go through the motions.
Does anyone have any idea what could have happened? This same task sequence used to work just fine. Could just having driver packages available on the DPs break the OSD even though they're not even referenced in the task sequence?
-Install Operating System
-Restart in Windows PE
-Partition Disk 0
-Apply Data image 1
-Apply Operating System
-Apply Windows Settings
-Apply Network Drivers
-Apply Device Drivers
-Setup Operating System
-Setup Windows and Configuration Manager
-Install Java
-Install Adobe Acrobat Reader XI
-... install a few more applications
-Install Updates

As Torsten said, yes, you will need to examine the logs. Post the contents of smsts.log here if you don't know what to look for
Here's a reference to help you find the location of the logs:
http://richardbalsley.com/location-of-smsts-log-when-using-configuration-manager-operating-system-deployment
Also:
What OS are you trying to apply?
What version of WinPE are you using?
Are you using Auto Apply Drivers or Apply Driver Package steps to install drivers? If Auto Apply Drivers, do you have them limited by category?

OSD Task Sequence fails to install SCCM client

Hello,
Our OSD task sequence fails to install the SCCM client with certain images.
The TS gets to the "Setup Windows and Configuration" step, during which it downloads all the necessary SCCM client files (silverlight, C++ redistributable, client.msi....etc.). At this point computer restarts and in never loads back into the
task sequence, instead it enters the minisetup (setup is starting services, setup is installing devices, setup is applying system settings...preparing computer for first use), after which the computer restarts and you are back at the CTR+ALT+Del screen.
The computer has joined the domain and has run all other steps but it has failed to install SCCM client. I can also see the leftovers of an incomplete TS under c:\_SMSTaskSequence
If we change the image specified under "Apply Operating System" step, everything works ok.
It appears there is something wrong with this particular image. Any ideas?
Logs show no errors. Let me know which logs you'd like me to post (and from which location)
There is no ccm folder under c:\windows

Hoping you are using ConfigMgr 2012 R2. If a client machine Join to Domain and doesn't proceed with other steps and not installing the CCM client, then problem seems to be with the Image.Do you have any RunOnce registry setting specified in the Image? You
can mount the Image and check those settings.
RunOnce Key Reference :
https://msdn.microsoft.com/en-us/library/windows/desktop/aa376977(v=vs.85).aspx
If the above key is present in the Image, TS Engine won't resume after the reboot.
You need to use a new variable "SMSTSPostAction" at the end of the Task Sequence, to add your custom actions.
The above variable is applicable in CM 2012 SP1 and R2.
Thanks, Senthil. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Click on "vote as Helpful" if you feel this post helpful to you. This
can be beneficial to other community members reading the thread.

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

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

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.

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

Similar Messages

Maybe you are looking for