Jump to content


Robert Nilsson

Established Members
  • Posts

    4
  • Joined

  • Last visited

Robert Nilsson's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi I have question regarding some OS installations that are stuck in the running state long after the installation has finished. This is a problem for us because other software will not get installed unless the OSD has finished successfully. The final step in our OSD task sequence installs all software updates that are advertised. And I have selected to ignore errors in case they do occur. Because software updates will get install later on anyway (not preferred). But the problem is that when we are advertising more updates to a computer than are available on the DP. Reason might be that the updates are currently being staged or we have forgotten to stage them. And the installation waits until they are available. Is there a way to change the installation status from running to succeeded? Either by a registry hack or an sql query? Or to have a time out in the task sequence causing it to "fail" which is ok because it's the last step. I have found the following key in the registry and someone here pointed out that if you want to rerun an advertisement that has the option rerun failed advertisements you can change it from succeeded or exit code 0 to exit 1 or whatever and the installation will restart next policy refresh. HKLM>Software>Microsoft>SMS>Mobile Client>Software Distribution>Execution History>System>"advID".
  2. Thanks for your tips. I'll keep you posted of any progress.
  3. I was wondering if it's possible to merge all three installation scenarios into the same task sequence? Just to make it event more simple for our helpdesk staff. I know all the basic concepts regarding USMT and hard linking and I have made them work standalone but it would be very neat in my environment to accomplish this in the same task sequence. Suggested task sequence layout would be: Install Scenario: At top of the task sequence there should be a capture state group that does only run if task sequence variable _SMSTSInWinPE not equals true. And after that the OS installation should proceed as normal but skip the Resore state at the end since there was no capture being made. (I'm not sure how to make this happen). Reinstall Scenario: Since Win XP or Win 7 already is installed and the SCCM agents has been deployed then the task sequence should start with the capture state (since _SMSTSInWinPE not equals true). But since the computer does not have a computer association with a different computer the task sequence should assume that it's a reinstall migration and should therefore perform a hard linking capture. After that the installation should proceed as normal but without the reformat hard drive step since this would wipe the hard link store. And lastly a restore state sequence. Replace Scenario: First we must do a computer association between the source computer (old) and the destination computer (new). Then place the old computer in a collection where we have advertised a capture to state migration point task sequence. Wait for the sequence to finish then boot the new computer via PXE and and let it install the OS and lastly restore the user state from the state migration point. Looking forward for any tips!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.